Open Annotation, Specifiers and Specific Resources tutorial

  • 2,891 views
Uploaded on

2nd part of the west coast Open Annotation rollout: …

2nd part of the west coast Open Annotation rollout:
- Open Annotation Core Model http://www.slideshare.net/azaroth42/open-annotation-core-data-model-tutorial

More in: Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,891
On Slideshare
0
From Embeds
0
Number of Embeds
6

Actions

Shares
Downloads
18
Comments
0
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Cambridge Semantic Web MeetupMay 14th 20131Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Open Annotation Data Model:Specifiers and Specific ResourcesPaolo Ciccaresepaolo.ciccarese@gmail.comHarvard Medical School@paolociccareseRobert Sandersonazaroth42@gmail.comLos Alamos National Laboratory@azaroth42(Community Group Co-Chairs)Massachusetts General Hospital
  • 2. Cambridge Semantic Web MeetupMay 14th 20132Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiersand Specific ResourcesThis module addresses several issues:• Advanced Segmentation• Fragments are not expressive enough for use cases• Some media types do not have fragment definition at all• Time and the Dynamic Web• Representations change and keep the same URI• Annotation may only apply to specific negotiated format• Styling Annotation• Style is vehicle for human-only semantics (eg red strike-through)• Style may be referenced in comments (the green highlight)• Scoping• Eg. the web page being viewed while an image was annotated
  • 3. Cambridge Semantic Web MeetupMay 14th 20133Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Core Data ModelAnnotation: The conceptual linkage between body and targetBody: The comment or resource which is “about” the TargetTarget: The resource which is being discussed
  • 4. Cambridge Semantic Web MeetupMay 14th 20134Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specific ResourcesSpecific Resource: A resource that is somehow more specific or moreprecisely defined than the “source” resourceSource: The resource as identified by its URI
  • 5. Cambridge Semantic Web MeetupMay 14th 20135Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specific Resources
  • 6. Cambridge Semantic Web MeetupMay 14th 20136Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specific Resources also for the Body
  • 7. Cambridge Semantic Web MeetupMay 14th 20137Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specific Resources also for the Body
  • 8. Cambridge Semantic Web MeetupMay 14th 20138Open Annotation Community Grouphttp://www.w3.org/community/openannotation/SpecifiersThere are four types of Specifier that describe how the Specific Resourceis different to the Source resource:• Selector• Describes a segment of the resource• State• Describes a state that the resource was in, via time or HTTP• Style• Describes a Style (using CSS) for the Annotation• Scope• References a resource which was being used for the Annotation
  • 9. Cambridge Semantic Web MeetupMay 14th 20139Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: SelectorsSelectors describe the segment of interest of a resourceSelectors are needed for several reasons:• Many media types do not have fragment specifications• Those that do often are not sufficiently precise in terms of description• Without knowing the media type, it is not possible to know how tointerpret a fragment• URIs are opaque strings, and systems normally do not try to lookwithin them for searching• Combinations of segment plus State, Style or ScopeThe specification defines some general, cross-community selectorsCommunities may also define their own
  • 10. Cambridge Semantic Web MeetupMay 14th 201310Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Selectors
  • 11. Cambridge Semantic Web MeetupMay 14th 201311Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Selectors
  • 12. Cambridge Semantic Web MeetupMay 14th 201312Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: SelectorsSelectors defined:• Fragment Selector• Range Selectors:• Text Position Selector• Text Quote Selector• Data Position Selector• Area Selectors• SVG Selector
  • 13. Cambridge Semantic Web MeetupMay 14th 201313Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Core Data Model: Fragment URIs
  • 14. Cambridge Semantic Web MeetupMay 14th 201314Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Fragment SelectorFragment Selector uses the fragment specifications to describe thesegment:• Useful in combination with other Specifiers• No need to reinvent the wheel!• Allows Specific Resource URI to be reused• Allows additional information to be attached, such as the specificationused to define the fragmentCurrent Fragment specifications include:• HTML, XML, RDF/XML• PDF• Plain Text• SVG• Media Fragments
  • 15. Cambridge Semantic Web MeetupMay 14th 201315Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Fragment Selector
  • 16. Cambridge Semantic Web MeetupMay 14th 201316Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Fragment Selector
  • 17. Cambridge Semantic Web MeetupMay 14th 201317Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: SVG SelectorMedia Fragments can only describe rectangles.SVG Selector allows arbitrary paths, circles, and so forth.
  • 18. Cambridge Semantic Web MeetupMay 14th 201318Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: SVG SelectorNote that the client downloads the SVG resource in this case
  • 19. Cambridge Semantic Web MeetupMay 14th 201319Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Text SelectorsSeveral intersecting issues require text based selectors:• HTML, PDF and Plain Text have fragment specifications, but onlyPlain Text allows arbitrary spans of text• Other formats don’t have a specification at all• One text selector could be reused across formats of the same text• Quotations in Annotations allow otherwise protected texts to bereproduced• Without the quotation and instead using characterposition, changes to the text will invalidate the selectorWe introduce two selectors:• Text Quote Selector• Text Position Selector
  • 20. Cambridge Semantic Web MeetupMay 14th 201320Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Text Quote Selector
  • 21. Cambridge Semantic Web MeetupMay 14th 201321Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Text Quote Selector
  • 22. Cambridge Semantic Web MeetupMay 14th 201322Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Text Position Selector
  • 23. Cambridge Semantic Web MeetupMay 14th 201323Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Text Position Selector
  • 24. Cambridge Semantic Web MeetupMay 14th 201324Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: StatesSelectors describe segments, but the URI of the Source identifies thegeneric web resource, not a particular representation.The web is dynamic, representations change based on many factors;States allow us to record some of the factors to get back to the rightrepresentation.We introduce two States:• TimeState:• Time as a universal versioning mechanism,and pointing to archived copies of the resource• HttpRequestState• Capture HTTP headers for content negotiation (etc)
  • 25. Cambridge Semantic Web MeetupMay 14th 201325Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Time State
  • 26. Cambridge Semantic Web MeetupMay 14th 201326Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Time State
  • 27. Cambridge Semantic Web MeetupMay 14th 201327Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: HTTP Request State
  • 28. Cambridge Semantic Web MeetupMay 14th 201328Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: HTTP Request State
  • 29. Cambridge Semantic Web MeetupMay 14th 201329Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: CSS StyleSome Annotations should maintain the style choices of the creator,for example to not draw a black rectangle on an image of the night sky
  • 30. Cambridge Semantic Web MeetupMay 14th 201330Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: CSS Style
  • 31. Cambridge Semantic Web MeetupMay 14th 201331Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: ScopeIt is often useful to know in which context a resource was annotated.This is recorded as a Scope of the Specific Resource
  • 32. Cambridge Semantic Web MeetupMay 14th 201332Open Annotation Community Grouphttp://www.w3.org/community/openannotation/Specifiers: Scope