Issue document concept

Requirement

There is unresolved discussion regarding the decision not to distinguish the Annotation Concept from the Document that describes it explicitly.

See the editor's note in [1]

Issue

There is currently only one URI that identifies the annotation, which is also the URL for the annotation's serialization. There may be multiple serializations of the same conceptual annotation available at multiple locations, and thus the introduction of oa:equivalentTo [2]

If there was only ever one URI that identified the annotation's concept, with a reference to the prefered or current serialization (see IANA's rel="self" and ORE's ResourceMap vs Aggregation distinction), then equivalence would not be necessary but the model would become more complex.

Dependencies

• None

Proposal

Remove editor's note and keep equivalence of annotations as the means of linking multiple copies together. Most implementers will think in terms of documents, not abstract concepts.