Open Annotation Data Model

IRI:
http://www.w3.org/ns/oa#
Version IRI:
http://www.openannotation.org/spec/core/20130208/oa.owl
Current version:
0.9.20130208
Authors:
Herbert Van de Sompel
Paolo Ciccarese
Robert Sanderson
Contributors:
Stian Soiland-Reyes
Imported Ontologies:
http://www.w3.org/1999/02/22-rdf-syntax-ns#
http://www.w3.org/2000/01/rdf-schema# (visualise it with LODE)
http://www.w3.org/2004/02/skos/core (visualise it with LODE)
http://www.w3.org/ns/prov-o# (visualise it with LODE)
Other visualisation:
Ontology source

Abstract

The Open Annotation Core Data Model specifies an interoperable framework for creating associations between related resources, annotations, using a methodology that conforms to the Architecture of the World Wide Web.

This ontology is a non-normative OWL formalization of the textual OA specification at http://www.openannotation.org/spec/core/20130208/index.html.

You may also want to download the OWL ontology in one of these formats:

To import this ontology from other OWL ontologies, use:

  owl:imports <http://www.w3.org/ns/oa#> .

Note that dependent OWL imports are disabled in the published versions above in order to reduce external implications, improve OWL 2 Profile conformity and increase interoperability. Some OWL tools might thus misleadingly show this ontology as (re)defining properties like skos:prefLabel.

Table of Content

  1. Introduction
  2. Classes
  3. Object Properties
  4. Data Properties
  5. Named Individuals
  6. Namespace Declarations

Introduction

The Open Annotation Core Data Model specifies an interoperable framework for creating associations between related resources, annotations, using a methodology that conforms to the Architecture of the World Wide Web. Open Annotations can easily be shared between platforms, with sufficient richness of expression to satisfy complex requirements while remaining simple enough to also allow for the most common use cases, such as attaching a piece of text to a single web resource.

An Annotation is considered to be a set of connected resources, typically including a body and target, where the body is somehow about the target. The full model supports additional functionality, enabling semantic annotations, embedding content, selecting segments of resources, choosing the appropriate representation of a resource and providing styling hints for consuming clients.

Classes

Annotationc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#Annotation

is defined by
http://www.w3.org/ns/oa#

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.

is in domain of
annotatedAtdp, annotatedByop, hasBodyop, hasTargetop, motivatedByop, serializedAtdp, serializedByop, styledByop

Choicec back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#Choice

is defined by
http://www.w3.org/ns/oa#

A multiplicity construct that conveys to a consuming application that it should select one of the constituent resources to display to the user, and not render/use all of them.

oa:Choice can be used as the object of the object of the oa:hasBody, oa:hasTarget, oa:hasSelector, oa:hasState, oa:styledBy and oa:hasScope relationships,

There MUST be 1 or more oa:item relationships for each oa:Choice.

There SHOULD be exactly 1 default relationship for each Choice.

has super-classes
  • rdf:Alt
is in domain of
defaultop

Compositec back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#Composite

is defined by
http://www.w3.org/ns/oa#

A multiplicity construct that conveys to a consuming application that all of the constituent resources are required for the Annotation to be correctly interpreted.

oa:Composite can be used as the object of the object of the oa:hasBody, oa:hasTarget, oa:hasSelector, oa:hasState, oa:styledBy and oa:hasScope relationships,

There MUST be 2 or more oa:item relationships for each oa:Composite.

has super-classes
  • rdf:Bag
has sub-classes
Listc

CssStylec back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#CssStyle

is defined by
http://www.w3.org/ns/oa#

A resource which describes styles for resources participating in the Annotation using CSS.

Specific Resources MAY be assigned a CSS style class using oa:styleClass.

The CSS resource MAY have its own dereferencable URI that provides the information. For example, "Style1" in the diagram below might actually have the URI "http://www.example.com/styles/annotations.css". It MAY be embedded within the Annotation using the inline constructions described in Embedding Resources.

has super-classes

DataPositionSelectorc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#DataPositionSelector

is defined by
http://www.w3.org/ns/oa#

A Selector which describes a range of data based on its start and end positions within the byte stream of the representation.

Each DataPositionSelector MUST have exactly 1 oa:start property.

Each TextPositionSelector MUST have exactly 1 oa:end property.

See oa:TextPositionSelector for selection at normalized character level rather than bytestream level.

has super-classes

FragmentSelectorc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#FragmentSelector

is defined by
http://www.w3.org/ns/oa#

A Selector which describes the segment of interest in a representation, through the use of the fragment identifier component of a URI.

It is RECOMMENDED to use oa:FragmentSelector as the selector on a Specific Resource rather than annotating the fragment URI directly, in order to improve discoverability of annotation on the Source.

The oa:FragmentSelector MUST have exactly 1 rdf:value property, containing the fragment identifier component of a URI that describes the segment of interest in the resource, excluding the initial "#".

The Fragment Selector SHOULD have a dcterms:conformsTo relationship with the object being the specification that defines the syntax of the fragment, for instance <http://tools.ietf.org/rfc/rfc3236> for HTML fragments.

has super-classes

HttpRequestStatec back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#HttpRequestState

is defined by
http://www.w3.org/ns/oa#

A resource which describes how to retrieve an appropriate representation of the Source resource for the Annotation, based on the HTTP Request headers to send to the server.

There MUST be exactly 1 rdf:value property per HttpRequestState, containing HTTP request headers as a single, complete string, exactly as they would appear in an HTTP request.

has super-classes

Listc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#List

is defined by
http://www.w3.org/ns/oa#

A multiplicity construct that conveys to a consuming application that all of the constituent resources are required for the Annotation to be correctly interpreted, and in a particular order.

oa:List can be used as the object of the object of the oa:hasBody, oa:hasTarget, oa:hasSelector, oa:hasState, oa:styledBy and oa:hasScope relationships,

There MUST be 2 or more oa:item relationships for each oa:List, with their order defined using the rdf:List construct of rdf:first/rdf:rest/rdf:nil.

All the elements of the list should also be declared using oa:item, and each of the oa:items should appear at least once in the list.

has super-classes

Motivationc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#Motivation

is defined by
http://www.w3.org/ns/oa#

The Motivation for creating an Annotation, indicated with oa:motivatedBy, is a reason for its creation, and might include things like oa:replying to another annotation, oa:commenting on a resource, or oa:linking to a related resource.

Each Annotation SHOULD have at least one oa:motivatedBy relationship to an instance of oa:Motivation, which is a subClass of skos:Concept.

has super-classes
  • skos:Concept
is in range of
motivatedByop
has members
oa:bookmarkingni, oa:classifyingni, oa:commentingni, oa:describingni, oa:editingni, oa:highlightingni, oa:identifyingni, oa:linkingni, oa:moderatingni, oa:questioningni, oa:replyingni, oa:taggingni

Selectorc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#Selector

is defined by
http://www.w3.org/ns/oa#

A resource which describes the segment of interest in a representation of a Source resource, indicated with oa:hasSelector from the Specific Resource.

This class is not used directly in Annotations, only its subclasses are.

The nature of the Selector will be dependent on the type of the representation for which the segment is conveyed. The specific type of selector should be indicated using a subclass of oa:Selector.

The Specifier's description MAY be conveyed as an external or embedded resource (cnt:Content), or as RDF properties within the graph. The description SHOULD use existing standards whenever possible. If the Specifier has an HTTP URI, then its description, and only its description, MUST be returned when the URI is dereferenced.

has sub-classes
DataPositionSelectorc, FragmentSelectorc, SvgSelectorc, TextPositionSelectorc, TextQuoteSelectorc
is in domain of
enddp, exactdp, prefixdp, startdp, suffixdp
is in range of
hasSelectorop

SemanticTagc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#SemanticTag

is defined by
http://www.w3.org/ns/oa#

A class assigned to the Body when it is a semantic tagging resource; a URI that identifies a concept, rather than an embedded string, frequently a term from a controlled vocabulary.

It is NOT RECOMMENDED to use the URI of a document as a Semantic Tag, as it might also be used as a regular Body in other Annotations which would inherit the oa:SemanticTag class assignment. Instead it is more appropriate to create a new URI and link it to the document, using the foaf:page predicate.

has super-classes

SpecificResourcec back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#SpecificResource

is defined by
http://www.w3.org/ns/oa#

A resource identifies part of another Source resource, a particular representation of a resource, a resource with styling hints for renders, or any combination of these.

The Specific Resource takes the role of oa:hasBody or oa:hasTarget in an oa:Annotation instead of the Source resource.

There MUST be exactly 1 oa:hasSource relationship associated with a Specific Resource.

There MUST be exactly 0 or 1 oa:hasSelector relationship associated with a Specific Resource.

There MAY be 0 or 1 oa:hasState relationship for each Specific Resource.

If the Specific Resource has an HTTP URI, then the exact segment of the Source resource that it identifies, and only the segment, MUST be returned when the URI is dereferenced. For example, if the segment of interest is a region of an image and the Specific Resource has an HTTP URI, then dereferencing it MUST return the selected region of the image as it was at the time when the annotation was created. Typically this would be a burden to support, and thus the Specific Resource SHOULD be identified by a globally unique URI, such as a UUID URN. If it is not considered important to allow other Annotations or systems to refer to the Specific Resource, then a blank node MAY be used instead.

is in domain of
styleClassdp, hasScopeop, hasSelectorop, hasSourceop, hasStateop

Statec back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#State

is defined by
http://www.w3.org/ns/oa#

A resource which describes how to retrieve an appropriate representation of the Source resource, indicated with oa:hasState from the Specific Resource.

This class is not used directly in Annotations, only its subclasses are.

The Specifier's description MAY be conveyed as an external or embedded resource (cnt:Content), or as RDF properties within the graph. The description SHOULD use existing standards whenever possible. If the Specifier has an HTTP URI, then its description, and only its description, MUST be returned when the URI is dereferenced.

has sub-classes
HttpRequestStatec, TimeStatec
is in range of
hasStateop

Stylec back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#Style

is defined by
http://www.w3.org/ns/oa#

A resource which describes the style in which the selection or resource should be rendered, indicated with oa:styledBy from an oa:Annotation.

This class is not used directly in Annotations, only its subclasses are.

The content of the resource provides the rendering hints about the Annotation's constituent resources.

The Specifier's description MAY be conveyed as an external or embedded resource (cnt:Content), or as RDF properties within the graph. The description SHOULD use existing standards whenever possible. If the Specifier has an HTTP URI, then its description, and only its description, MUST be returned when the URI is dereferenced.

has sub-classes
CssStylec
is in range of
styledByop

SvgSelectorc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#SvgSelector

is defined by
http://www.w3.org/ns/oa#

A Selector which selects an area specified as an SVG shape.

The SVG document should either be retrievable by resolving the URI of this resource, or be included as an Embedded Resource using cnt:Content.

It is RECOMMENDED that the document contain only a single shape element and that element SHOULD be one of: path, rect, circle, ellipse, polyline, polygon or g. The g element SHOULD ONLY be used to construct a multi-element group, for example to define a donut shape requiring an outer circle and a clipped inner circle.

The dimensions of both the shape and the SVG canvas MUST be relative to the dimensions of the Source resource. For example, given an image which is 600 pixels by 400 pixels, and the desired section is a circle of 100 pixel radius at the center of the image, then the SVG element would be: <circle cx="300" cy="200" r="100"/>

It is NOT RECOMMENDED to include style information within the SVG element, nor Javascript, animation, text or other non shape oriented information. Clients SHOULD ignore such information if present.

has super-classes

Tagc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#Tag

is defined by
http://www.w3.org/ns/oa#

A class assigned to the Body when it is a tag, such as a embedded text string with cnt:chars.

Tags are typically keywords or labels, and used for organization, description or discovery of the resource being tagged. In the Semantic Web, URIs are used instead of strings to avoid the issue of polysemy where one word has multiple meanings, such usage MUST be indicated using the subclass oa:SemanticTag.

Annotations that tag resources, either with text or semantic tags, SHOULD also have the oa:tagging motivation to make the reason for the Annotation more clear to applications, and MAY have other motivations as well.

has sub-classes
SemanticTagc

TextPositionSelectorc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#TextPositionSelector

is defined by
http://www.w3.org/ns/oa#

An oa:Selector which describes a range of text based on its start and end positions.

The text MUST be normalized before counting characters. For a Selector that works from the bitstream rather than the rendered characters, see oa:DataPositionSelector.

Each oa:TextPositionSelector MUST have exactly 1 oa:start property.

Each oa:TextPositionSelector MUST have exactly 1 oa:end property.

has super-classes

TextQuoteSelectorc back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#TextQuoteSelector

is defined by
http://www.w3.org/ns/oa#

A Selector that describes a textual segment by means of quoting it, plus passages before or after it.

For example, if the document were "abcdefghijklmnopqrstuvwxyz", one could select "efg" by a oa:prefix of "abcd", the quotation of oa:exact "efg" and a oa:suffix of "hijk".

The text MUST be normalized before recording.

Each TextQuoteSelector MUST have exactly 1 oa:exact property.

Each TextQuoteSelector SHOULD have exactly 1 oa:prefix property, and MUST NOT have more than 1.

Each TextQuoteSelector SHOULD have exactly 1 oa:suffix property, and MUST NOT have more than 1.

has super-classes

TimeStatec back to ToC or Class ToC

IRI: http://www.w3.org/ns/oa#TimeState

is defined by
http://www.w3.org/ns/oa#

A resource which describes how to retrieve a representation of the Source resource that is temporally appropriate for the Annotation.

There MUST be at least one of oa:cachedSource or oa:when specified. If there is more than 1, each gives an alternative copy of the representation.

has super-classes
is in domain of
cachedSourceop, whendp

Object Properties

annotatedByop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#annotatedBy

is defined by
http://www.w3.org/ns/oa#

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

has super-properties
  • prov:wasAttributedTo
has domain

cachedSourceop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#cachedSource

is defined by
http://www.w3.org/ns/oa#

A link to a copy of the Source resource's representation appropriate for the Annotation, typically a copy of the original at the time that the Annotation was created

has domain

defaultop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#default

is defined by
http://www.w3.org/ns/oa#

The constituent resource of a oa:Choice to use as a default option, if there is no other means to determine which would be most appropriate.

There SHOULD be exactly 1 default relationship for each Choice.

has super-properties
has domain

equivalentToop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#equivalentTo

is defined by
http://www.w3.org/ns/oa#

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.

has super-properties
  • prov:alternateOf

hasBodyop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#hasBody

is defined by
http://www.w3.org/ns/oa#

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.

has domain

hasScopeop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#hasScope

is defined by
http://www.w3.org/ns/oa#

The relationship between a Specific Resource and the resource that provides the scope or context for it in this Annotation.

There MAY be 0 or more hasScope relationships for each Specific Resource.

has domain

hasSelectorop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#hasSelector

is defined by
http://www.w3.org/ns/oa#

The relationship between a oa:SpecificResource and a oa:Selector.

There MUST be exactly 0 or 1 oa:hasSelector relationship associated with a

Specific Resource.

If multiple Selectors are required, either to express a choice between different optional, equivalent selectors, or a chain of selectors that should all be processed, it is necessary to use oa:Choice, oa:Composite or oa:List as a selector.

has domain
has range

hasSourceop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#hasSource

is defined by
http://www.w3.org/ns/oa#

The relationship between a oa:SpecificResource and the resource that it is a more specific representation of.

There MUST be exactly 1 oa:hasSource relationship associated with a Specific Resource.

has domain

hasStateop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#hasState

is defined by
http://www.w3.org/ns/oa#

The relationship between a oa:SpecificResource and a oa:State resource.

There MAY be 0 or 1 oa:hasState relationship for each SpecificResource.

If there are multiple State resources that must be associated with the specific resource, then the use of the Multiplicity Constructs oa:Choice, oa:Composite or oa:List is RECOMMENDED.

has domain
has range

hasTargetop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#hasTarget

is defined by
http://www.w3.org/ns/oa#

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.

has domain

itemop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#item

is defined by
http://www.w3.org/ns/oa#

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.

has super-properties
  • rdfs:member
has sub-properties
defaultop

motivatedByop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#motivatedBy

is defined by
http://www.w3.org/ns/oa#

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.

has domain
has range

serializedByop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#serializedBy

is defined by
http://www.w3.org/ns/oa#

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.

has super-properties
  • prov:wasAttributedTo
has domain

styledByop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/oa#styledBy

is defined by
http://www.w3.org/ns/oa#

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.

has domain
has range

Data Properties

annotatedAtdp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/oa#annotatedAt

is defined by
http://www.w3.org/ns/oa#

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.

has domain
has range
  • xsd:dateTimeStamp

styleClassdp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/oa#styleClass

is defined by
http://www.w3.org/ns/oa#

The string name of the class used in the CSS description that should be applied to the Specific Resource.

There MAY be 0 or more styleClass properties on a Specific Resource.

See oa:CssStyle.

has domain

enddp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/oa#end

is defined by
http://www.w3.org/ns/oa#

The end position of the segment of text or bytes. The first character/byte in the full text/stream is position 0. The character/byte indicated at position oa:end is NOT included within the selected segment.

See oa:DataPositionSelector and oa:oa:TextPositionSelector.

has domain
has range
  • xsd:nonNegativeInteger

exactdp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/oa#exact

is defined by
http://www.w3.org/ns/oa#

A copy of the text which is being selected, after normalization.

See oa:TextQuoteSelector.

has domain

prefixdp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/oa#prefix

is defined by
http://www.w3.org/ns/oa#

A snippet of text that occurs immediately before the text which is being selected.

See oa:TextQuoteSelector.

has domain

serializedAtdp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/oa#serializedAt

is defined by
http://www.w3.org/ns/oa#

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.

has domain
has range
  • xsd:dateTimeStamp

startdp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/oa#start

is defined by
http://www.w3.org/ns/oa#

The starting position of the segment of text or bytes. The first character/byte in the full text/stream is position 0. The character/byte indicated at position oa:start is included within the selected segment.

See oa:DataPositionSelector and oa:TextPositionSelector.

has domain
has range
  • xsd:nonNegativeInteger

suffixdp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/oa#suffix

is defined by
http://www.w3.org/ns/oa#

The snippet of text that occurs immediately after the text which is being selected.

See oa:TextQuoteSelector.

has domain

whendp back to ToC or Data Property ToC

IRI: http://www.w3.org/ns/oa#when

is defined by
http://www.w3.org/ns/oa#

The timestamp at which the Source resource should be interpreted for the Annotation, typically the time that the Annotation was created.

has domain
has range
  • xsd:dateTimeStamp

Named Individuals

motivationSchemeni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#motivationScheme

The concept scheme for Open Annotation Motivations

belongs to
  • skos:ConceptScheme

oa:bookmarkingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#bookmarking

The motivation that represents the creation of a bookmark to the target resources or recorded point or points within one or more resources. For example, an Annotation that bookmarks the point in a text where the reader finished reading. Bookmark Annotations may or may not have a Body resource.

belongs to

oa:classifyingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#classifying

The motivation that represents the assignment of a classification type, typically from a controlled vocabulary, to the target resource(s). For example to classify an Image resource as a Portrait.

belongs to

oa:commentingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#commenting

The motivation that represents a commentary about or review of the target resource(s). For example to provide a commentary about a particular PDF.

belongs to

oa:describingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#describing

The motivation that represents a description of the target resource(s), as opposed to a comment about them. For example describing the above PDF's contents, rather than commenting on their accuracy.

belongs to

oa:editingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#editing

The motivation that represents a request for a modification or edit to the target resource. For example, an Annotation that requests a typo to be corrected.

belongs to

oa:highlightingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#highlighting

The motivation that represents a highlighted section of the target resource or segment. For example to draw attention to the selected text that the annotator disagrees with. A Highlight may or may not have a Body resource

belongs to

oa:identifyingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#identifying

The motivation that represents the assignment of an identity to the target resource(s). For example, annotating the name of a city in a string of text with the URI that identifies it.

belongs to

oa:linkingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#linking

The motivation that represents an untyped link to a resource related to the target.

belongs to

oa:moderatingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#moderating

The motivation that represents an assignment of value or quality to the target resource(s). For example annotating an Annotation to moderate it up in a trust network or threaded discussion.

belongs to

oa:questioningni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#questioning

The motivation that represents asking a question about the target resource(s). For example to ask for assistance with a particular section of text, or question its veracity.

belongs to

oa:replyingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#replying

The motivation that represents a reply to a previous statement, either an Annotation or another resource. For example providing the assistance requested in the above.

belongs to

oa:taggingni back to ToC or Named Individual ToC

IRI: http://www.w3.org/ns/oa#tagging

The motivation that represents adding a Tag on the target resource(s). One or more of the bodies of the annotation should be typed as a oa:Tag or oa:SemanticTag.

belongs to

Namespace Declarations back to ToC

default namespace
http://www.w3.org/ns/oa
cnt
http://www.w3.org/2011/content#
dc
http://purl.org/dc/elements/1.1/
dcterms
http://purl.org/dc/terms/
dctypes
http://purl.org/dc/dcmitype/
foaf
http://xmlns.com/foaf/0.1/
oa
http://www.w3.org/ns/oa#
owl
http://www.w3.org/2002/07/owl#
prov
http://www.w3.org/ns/prov#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
skos
http://www.w3.org/2004/02/skos/core#
trig
http://www.w3.org/2004/03/trix/rdfg-1/
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code throughLODE, Live OWL Documentation Environment, developed bySilvio Peroni.