http://www.w3.org/ns/oa#Annotation
Typically an Annotation has a single Body (oa:hasBody), which is the comment or other descriptive resource, and a single Target (oa:hasTarget) that the Body is somehow "about". The Body provides the information which is annotating the Target.
This "aboutness" may be further clarified or extended to notions such as classifying or identifying with oa:motivatedBy.
Instances of oa:#Annotation can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class oa:#Annotation | |||
| oa:#annotatedAt | owl:DatatypeProperty | The time at which the Annotation was created. There SHOULD be exactly 1 oa:annotatedAt property per Annotation, and MUST NOT be more than 1. The datetime MUST be expressed in the xsd:dateTime format, and SHOULD have a timezone specified. | xsd:dateTimeStamp |
| oa:#serializedAt | owl:DatatypeProperty | The time at which the agent referenced by oa:serializedBy generated the first serialization of the Annotation, and any subsequent substantially different one. The annotation graph MUST have changed for this property to be updated, and as such represents the last modified datestamp for the Annotation. This might be used to determine if it should be re-imported into a triplestore when discovered. There MAY be exactly 1 oa:serializedAt property per Annotation, and MUST NOT be more than 1. The datetime MUST be expressed in the xsd:dateTime format, and SHOULD have a timezone specified. | xsd:dateTimeStamp |
| oa:#annotatedBy | owl:ObjectProperty | The object of the relationship is a resource that identifies the agent responsible for creating the Annotation. This may be either a human or software agent. There SHOULD be exactly 1 oa:annotatedBy relationship per Annotation, but MAY be 0 or more than 1, as the Annotation may be anonymous, or multiple agents may have worked together on it. It is RECOMMENDED to use these and other FOAF terms to describe agents: foaf:Person, prov:SoftwareAgent, foaf:Organization, foaf:name, foaf:mbox, foaf:openid, foaf:homepage | owl:Thing |
| oa:#hasBody | owl:ObjectProperty | The relationship between oa:Annotation and body. The body is somehow "about" the oa:hasTarget of the annotation. The Body may be of any media type, and contain any type of content. The Body SHOULD be identified by HTTP URIs unless they are embedded within the Annotation. Embedded bodies SHOULD be instances of cnt:ContentAsText and embed their content with cnt:chars. They SHOULD declare their media type with dc:format, and MAY indicate their language using dc:language and a RFC-3066 language tag. There is no OA class provided for "Body" as a body might be a target of a different annotation. However, there SHOULD be 1 or more content-based classes associated with the body resources of an Annotation, and the dctypes: vocabulary is recommended for this purpose, for instance dctypes:Text to declare textual content. | owl:Thing |
| oa:#hasTarget | owl:ObjectProperty | The relationship between oa:Annotation and target. The target resource is what the oa:hasBody is somewhat "about". The target may be of any media type, and contain any type of content. The target SHOULD be identified by HTTP URIs unless they are embedded within the Annotation. Embedded targets SHOULD be instances of cnt:ContentAsText and embed their content with cnt:chars. They SHOULD declare their media type with dc:format, and MAY indicate their language using dc:language and a RFC-3066 language tag. There is no OA class provided for "Target" as a target might be a body in a different annotation. However, there SHOULD be 1 or more content-based classes associated with the target resources of an Annotation, and the dctypes: vocabulary is recommended for this purpose, for instance dctypes:Text to declare textual content. | owl:Thing |
| oa:#motivatedBy | owl:ObjectProperty | The relationship between an Annotation and a Motivation, indicating the reasons why the Annotation was created. Each Annotation SHOULD have at least one oa:motivatedBy relationship, and MAY be more than 1. | oa:#Motivation |
| oa:#serializedBy | owl:ObjectProperty | The object of the relationship is the agent, likely software, responsible for generating the serialization of the Annotation's serialization. It is RECOMMENDED to use these and other FOAF terms to describe agents: foaf:Person, prov:SoftwareAgent, foaf:Organization, foaf:name, foaf:mbox, foaf:openid, foaf:homepage There MAY be 0 or more oa:serializedBy relationships per Annotation. | owl:Thing |
| oa:#styledBy | owl:ObjectProperty | The relationship between a oa:Annotation and a oa:Style. There MAY be 0 or 1 styledBy relationships for each Annotation. If there are multiple Style resources that must be associated with the Annotation, then the use of the Multiplicity Constructs oa:Choice, oa:Composite or oa:List is RECOMMENDED. | oa:#Style |
| From class owl:Thing | |||
| oa:#equivalentTo | owl:ObjectProperty | The subject and object resources of the oa:equivalentTo relationship represent the same resource, but potentially have different metadata such as oa:serializedBy, oa:serializedAt and serialization format. oa:equivalentTo is a symmetrical and transitive relationship; if A oa:equivalentTo B, then it is also true that B oa:equivalent A; and that if B oa:equivalentTo C, then it is also true that A oa:equivalentTo C. The Annotation MAY include 0 or more instances of the oa:equivalentTo relationship between copies of the Annotation or other resources, and SHOULD include as many as are available. If a system publishes an embedded resource (a cnt:Content) at a new HTTP URI, then it SHOULD express the oa:equivalentTo relationship between the resource's URN and the new URI from which it is available. | owl:Thing |
| oa:#item | owl:ObjectProperty | The relationship between a multiplicity construct node and its constituent resources. There MUST be 1 or more item relationships for each multiplicity construct oa:Choice, oa:Composite and oa:List. | owl:Thing |
@prefix oa: <http://www.w3.org/ns/oa#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
oa:Annotation a owl:Class ;
rdfs:label "Annotation"@en ;
rdfs:comment """Typically an Annotation has a single Body (oa:hasBody), which is the comment or other descriptive resource, and a single Target (oa:hasTarget) that the Body is somehow "about". The Body provides the information which is annotating the Target.
This "aboutness" may be further clarified or extended to notions such as classifying or identifying with oa:motivatedBy."""@en ;
rdfs:isDefinedBy oa: .