The Web Annotation Vocabulary provides the terms and definitions which underpin the related [Web Annotation Data Model](https://www.w3.org/TR/annotation-model/).
The terminology (and specifications) can make the underlying concepts seem a bit obtuse, but fundamentally a Web [Annotation](anno:Annotation) is a (typically purposeful) object which [has a target](anno:hasTarget) and associates it with zero or more [bodies](anno:hasBody).
If you can get past all the language, this is fundamentally a very simple model which is broadly applicable.
-
, as it merely offers a discovery endpoint for the Web Annotation Protocol, which this ontology makes no claims to support.
-
, as it defines what is in essence a rendering detail.
If two bodies are, for example, equivalent but in different languages, it would be better to provide that information via relationships between the bodies themselves, and leave it to renderers to determine whether to display both or choose between them.
-
, , , and , as these are rendering details which ought to be left to applications.
-
is underspecified, and its [value](rdf:value) is generally described as a string, not the more appropriate .
-
follows an undesirable pattern of recommending a plaintext string [value](rdf:value), with its language and media type specified thru other properties.
For plaintext strings, it is better for language to be provided via the mechanism, and it is better that X·M·L values be provided as s.
Because these things complicate the processing model and it is unlikely that existing Web Annotation tools would support them, this ontology chose not to complicate .
Instead, should be used.
-
, for the same reasons as .
-
is semantically muddled; [Time States](anno:TimeState) don¦t generally [have sources](anno:hasSource), so how can they have cached ones?
This would have been better modelled as a property of the enclosing [Resource Selection](anno:ResourceSelection).
-
, while providing interesting and potentially meaningful provenance information, adds additional complexity to the model without any known practical use·cases.
This ontology may choose to define it at a later time if practical use·cases are found.
-
Properties originally defined by other vocabularies, when those vocabularies are not otherwise defined in this ontology.