the open annotation collaboration (oac) model
Post on 11-May-2015
1.161 Views
Preview:
TRANSCRIPT
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
The Open Annotation Collaboration (OAC) ModelBernhard Haslhofer | Cornell University / University of Vienna
Rainer Simon | Austrian Institute of Technology
Robert Sanderson | Los Alamos National Laboratory
Herbert van de Sompel | Los Alamos National Laboratory
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Overview
• Motivation and Goals
• The Open Annotation Data Model
• Status and Next Steps
(c) Andy Ashton, Brown Digital Repository (http://www.openannotation.org/documents/AndyAshtonOACWorkshop.pdf)
Annotation Supporting Collaborative Development of Scholarly EditionsAnna Gerber, Jane Hunter
!"#$%&'()!"%&#*#+,-.)/,+')0)1'%&.
(c) Anna Gerber, Jane Hunter, Univ. Queensland (http://www.openannotation.org/documents/GerberHunterOAC.pdf)
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
“Annotation”
“An annotation associates one piece of information with one (or more) otherpiece(s) of information.”
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Current Annotations
• are stuck in silos
• consumable only by a single client
• not sharable beyond original environment
• are repository-centric, not Web-centric
• no first class resources
• no global identifiers
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
OAC Goals
• Enable sharing of annotations across clients, platforms and content collections
• Re-think annotations in terms of the Web
• Adopt Linked Data ideas for annotations
• Primary focus on scholarly annotations
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Why not Annotea?
• Annotea (2001)
• designed for the annotation of Web pages not for multimedia Web resources
• defines an Annotea-specific protocol
• no time dimension
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Why not Annotea?
• Various Annotea extensions were defined throughout the years
• OAC tries to pull together various extensions of Annotea into a cohesive whole
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Overview
• Motivation and Goals
• The Open Annotation Data Model
• Status and Next Steps
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Baseline ModelAn Annotation is a document identified by an HTTP URI and describes an association created between a Body resource and a Target resource. The Body must be somehow about the target.
B-1 T-1
A-1
oac:hasBody oac:hasTarget
oac:Annotation
rdf:type
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Baseline Model
ex:Anno
oac:hasBody oac:hasTarget
oac:Annotation
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
SerializationDereferencing the Annotation HTTP URI results in an RDF serialization of an instance of this data model.
ex:Anno
oac:hasBody oac:hasTarget
(rdf)HTTP GET
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Additional Information
B-1 T-1
A-1
oac:hasBody oac:hasTarget
datetime dcterms:created
dcterms:creatorU-1
stringdc:titlestring
foaf:name
string
foaf:mbox
Additional properties and relationships can be associated with an Annotation.
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Annotation Types
S-1 T-1
A-1
oac:hasBody oac:hasTarget
S-2
A-2
oac:hasBody oac:hasTarget
oac:Reply
oac:Annotation
rdf:type
rdf:type
oac:Annotation is the base class for Annotations. There can be more specialized types.
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Inline Information
ex:Anno
oac:hasBody oac:hasTarget
This image is very
impressive!
ex:HDFI-1
UTF-8
cnt:charscnt:characterEncoding
ex:uuid
cnt:ContentAs
Text
rdf:type
Bodies can be embedded into the Annotation document by assigning a unique non-resolvable URN as identifier to the Body.
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Fragment URIsThe user agent must be able to select part of the resource as the Body or Target for an Annotation, not just the entire resource.
http://www.example.net/foo.html#namedSectionhttp://www.example.net/foo.pdf#page=10&viewrect=20,100,50,60http://www.example.org/foo.txt#line=1,5http://www.example.net/foo.xml#xpointer(/a/b/c)
B-1 T-1#xy
A-1
oac:hasBody oac:hasTarget
T-1
dcterms:isPartOf
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Media Fragment URIsThe W3C Media Fragment URI specification allows the creation of a URI that identifies a segment of image, video and audio resources.
ex:Anno
oac:hasBody oac:hasTarget
ex:HDFI-1#xywh=50,100,640,480tw:6312261983
dcterms:isPartOf
ex:HDFI-1
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Constrained TargetsFor resource segments which cannot be described by (media) fragment URIs, we introduce ConstrainedTarget resources.
uu1
ex:Anno
oac:hasBody oac:hasTarget
describes
ex:svgc
ex:HDFI-1
tw:6312261983
image/svg+xml
dc:format
oac:constrainsoac:constrainedBy
(svg)
HTTP GET
oac:SvgConstraint
rdf:type
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Time Dependent Annotations
• Resource representations change over time
• Three types of time dependent annotations
• Timeless Annotations
• Uniform Time Annotations
• Varied Time Annotations
• Distinction through use of oac:when
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Uniform Time Annotation
ex:Anno
oac:hasBody oac:hasTargettw:11002497449
2010-03-2215:05:00 GMT
oac:when
ex:cnn
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Overview
• Motivation and Goals
• The Open Annotation Data Model
• Status and Next Steps
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Demonstration Experiments
• Annotation Supporting Collaborative Development of Scholarly Editions (AustLit)
• Annotation of Digitized Medieval Manuscripts (Stanford)
• Annotation of Subscription Streaming Video Content (Alexander Street Press)
• Annotation of Digital Emblematica (Emblematica Online)
• Annotation of Historic Maps (Cornell)
• ....
MMWeb 2011 Workshop | Graz, Austria | Sept. 8th, 2011
Further Infos / Resources
http://www.openannotation.org/
http://dme.ait.ac.at/annotation/
http://code.google.com/p/oac-js/
https://github.com/yuma-annotation/
top related