Lady’s Gitweb - Vocab/blob - data/named_individuals/_ANNO_

   1 <?xml version="1.0"?>
   2 <!--
   3 SPDX-FileCopyrightText: 2024 Lady <https://www.ladys.computer/about/#lady>
   4 SPDX-License-Identifier: CC0-1.0
   5 -->
   6 <!DOCTYPE NamedIndividual SYSTEM "../../DTD">
   7 <NamedIndividual name="https://www.w3.org/TR/annotation-vocab/">
   8         <label xml:lang="en">Web Annotation Vocabulary</label>
   9         <comment xml:lang="en">
  10                 <p>
  11                         The Web Annotation Vocabulary provides the terms and definitions which underpin the related <ref target="https://www.w3.org/TR/annotation-model/">Web Annotation Data Model</ref>.
  12                         The terminology (and specifications) can make the underlying concepts seem a bit obtuse, but fundamentally a Web <ref target="anno:Annotation">Annotation</ref> is a (typically purposeful) object which <ref target="anno:hasTarget">has a target</ref> and associates it with zero or more <ref target="anno:hasBody">bodies</ref>.
  13                         If you can get past all the language, this is fundamentally a very simple model which is broadly applicable.
  14                 </p>
  15                 <p>
  16                         This ontology does not define <em>every</em> term in the Web Annotation Vocabulary, but it does define most of them.
  17                         Terms it excludes include :⁠—
  18                 </p>
  19                 <list>
  20                         <item>
  21                                 <p>
  22                                         <resource name="anno:annotationService"/>, as it merely offers a discovery endpoint for the Web Annotation Protocol, which this ontology makes no claims to support.
  23                                 </p>
  24                         </item>
  25                         <item>
  26                                 <p>
  27                                         <resource name="anno:Choice"/>, as it defines what is in essence a rendering detail.
  28                                         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.
  29                                 </p>
  30                         </item>
  31                         <item>
  32                                 <p>
  33                                         <resource name="anno:Style"/>, <resource name="anno:CssStyle"/>, <resource name="anno:styledBy"/>, and <resource name="anno:styleClass"/>, as these are rendering details which ought to be left to applications.
  34                                 </p>
  35                         </item>
  36                         <item>
  37                                 <p>
  38                                         <resource name="anno:SvgSelector"/> is underspecified, and its <ref target="rdf:value">value</ref> is generally described as a string, not the more appropriate <resource name="rdf:XMLLiteral"/>.
  39                                 </p>
  40                         </item>
  41                         <item>
  42                                 <p>
  43                                         <resource name="anno:TextualBody"/> follows an undesirable pattern of recommending a plaintext string <ref target="rdf:value">value</ref>, with its language and media type specified thru other properties.
  44                                         For plaintext strings, it is better for language to be provided via the <resource name="rdf:langString"/> mechanism, and it is better that X·M·L values be provided as <resource name="rdf:XMLLiteral"/>s.
  45                                         Because these things complicate the processing model and it is unlikely that existing Web Annotation tools would support them, this ontology chose <em>not</em> to complicate <resource name="anno:TextualBody"/>.
  46                                         Instead, <ptr target="awol:Content"/> should be used.
  47                                 </p>
  48                         </item>
  49                         <item>
  50                                 <p>
  51                                         <resource name="anno:bodyValue"/>, for the same reasons as <resource name="anno:TextualBody"/>.
  52                                 </p>
  53                         </item>
  54                         <item>
  55                                 <p>
  56                                         <resource name="anno:cachedSource"/> is semantically muddled; <ref target="anno:TimeState">Time States</ref> don¦t generally <ref target="anno:hasSource">have sources</ref>, so how can they have cached ones?
  57                                         This would have been better modelled as a property of the enclosing <ref target="anno:ResourceSelection">Resource Selection</ref>.
  58                                 </p>
  59                         </item>
  60                         <item>
  61                                 <p>
  62                                         <resource name="anno:renderedVia"/>, while providing interesting and potentially meaningful provenance information, adds additional complexity to the model without any known practical use·cases.
  63                                         This ontology may choose to define it at a later time if practical use·cases are found.
  64                                 </p>
  65                         </item>
  66                         <item>
  67                                 <p>
  68                                         Properties originally defined by other vocabularies, when those vocabularies are not otherwise defined in this ontology.
  69                                 </p>
  70                         </item>
  71                 </list>
  72         </comment>
  73         <type>
  74                 <resource name="dcterms:BibliographicResource"/>
  75         </type>
  76         <type>
  77                 <resource name="dcterms:Standard"/>
  78         </type>
  79         <type>
  80                 <resource name="foaf:Document"/>
  81         </type>
  82 </NamedIndividual>