Affected spec section
- MappingAssertion
Motivation
The spec already treats target_kind as optional and non-normative: validators MUST NOT key behaviour off it, and the IRI in identifier is authoritative. If the field carries no normative weight, maintaining an enumerated list of known schemes (Appendix B) becomes avoidable upkeep without a clear payoff.
Proposed change
Drop the scheme hint and rely on a dereferenceable IRI, expressing conformance to the relevant identifier scheme/standard via dct:conformsTo in the JSON. This mirrors how Linked Art models e.g. IIIF integration through conforms_to (see https://linked.art/model/digital/), keeps the model open-ended, and removes the need to keep a registry of scheme labels current.
Alternatives considered
No response
Compatibility impact
additive (no breaking change)
Target spec version
V1
Affected spec section
Motivation
The spec already treats
target_kindas optional and non-normative: validators MUST NOT key behaviour off it, and the IRI inidentifieris authoritative. If the field carries no normative weight, maintaining an enumerated list of known schemes (Appendix B) becomes avoidable upkeep without a clear payoff.Proposed change
Drop the scheme hint and rely on a dereferenceable IRI, expressing conformance to the relevant identifier scheme/standard via
dct:conformsToin the JSON. This mirrors how Linked Art models e.g. IIIF integration throughconforms_to(see https://linked.art/model/digital/), keeps the model open-ended, and removes the need to keep a registry of scheme labels current.Alternatives considered
No response
Compatibility impact
additive (no breaking change)
Target spec version
V1