Compatibility matrixstable
§3 The 1.0.1 example edits (5)
The corrected example validates under both schemas — the golden example must never be the artifact that forces a consumer upgrade. Edit letters (a)–(e) are the annex §2.2 labels.
| # | Pointer | Change | Class | Record-level impact |
|---|---|---|---|---|
| X1 (a) | /identity/perceptual/0/value | 96 hex → f8f8f0ce…4e9c9b22 (64 hex, recovered as value[:64]) | patch-compatible correction | The published value was never a legal pdq/1.0 digest. Valid under 1.0.0 and 1.0.1 |
| X2 (b) | /metadata/raw/0/sha256 | placeholder (sha256("password")) → a106fd0f…0a5c6e7a, the real SHA-256 of the segment's own bytes | patch-compatible correction | Makes the example self-consistent (EX-01). The digest covers the 602 octets edit (e) installs; annex §2.2 carries the reproduction script |
| X3 (c) | /metadata/normalized/@context | bare XMP namespace URI → inline context defining dc and Iptc4xmpExt | patch-compatible correction | The example's JSON-LD now defines the prefix it uses (EX-02). No schema constraint involved |
| X4 (d) | /provenance/chain | four events → five; a second embed event, one per embedding | patch-compatible correction | The chain now accounts for both embeddings (EX-04). Additive within an existing array |
| X5 (e) | /metadata/raw/0/bytes | the elided 30-octet ICC illustration → a real, complete 602-octet JPEG APP2 ICC payload: ICC_PROFILE\0, the two sequence octets 01 01, then a complete 588-octet sRGB profile, base64-encoded | patch-compatible correction | Makes the example genuinely satisfy annex E11 (a preserved JPEG APP segment is the payload including its identifier prefix and sequence octets) and E26 (no elided segments at the L3 the example declares). raw[0].sha256 is recomputed over exactly these bytes. The profile's creation-date header field is zeroed so the artifact is byte-reproducible |
Not repaired, deliberately. Every other digest in the example remains a trivial-preimage placeholder, and the normalized view still asserts a description with no in-asset source (EX-03). Repairing them requires shipping real content-addressed artifacts; until then annex E26 labels the whole example illustrative. Do not use it as a golden conformance artifact — use conformance/.