W3C Web Annotation WG Update (I Annotate 2016)
2 likes1,172 views
The document provides an update from the W3C Web Annotation Working Group, detailing the history and mission of web annotation interoperability. It outlines the working group's charter, significant changes, and new features, as well as presenting examples in JSON-LD. Future steps include testing and implementation requests for developers.
W3C Web Annotation WG Update (I Annotate 2016)
- 1. @azaroth42 Web Annotation WG Update Rob Sanderson [email protected] W3C Web Annotation Working Group Update
- 2. @azaroth42 Web Annotation WG Update Brief History of Annotation at W3C • 2001 Annotea • 2009 Open Annotation Collaboration & Annotation Ontology • 2011 Open Annotation Community Group • 2014 Web Annotation Working Group • 2016 Technical Recommendations?
- 3. @azaroth42 Web Annotation WG Update Community Group Mission Interoperabilitybetween Annotation systems & platforms by …following the Architecture of the Web …reusing existing web standards …providing a single, coherent model to implement …which is orthogonal to the domain of interest …without requiring adoption of specific platforms …while maintaining low implementation costs
- 4. @azaroth42 Web Annotation WG Update Working Group Charter 1. Model Working Draft towards TR 2. Vocabulary Working Draft towards TR 3. Serialization Merged with Model 4. Protocol Working Draft towards TR 5. Client API Working Draft 6. Robust Linking No formal output http://w3.org/TR/annotation-‐model …/annotation-‐vocab …/annotation-‐protocol
- 5. @azaroth42 Web Annotation WG Update Annotation? A set of connected resources, typically including a body and target, where the body is related to the target. Users annotate in order to … Provide an aide-‐memoire bookmarking … Share and inform commenting … Improve discovery tagging … Organize resources identifying … Interact with others replying “ ”
- 6. @azaroth42 Web Annotation WG Update Annotation Ecosystem
- 7. @azaroth42 Web Annotation WG Update Annotation Ecosystem
- 8. @azaroth42 Web Annotation WG Update Annotation Ecosystem
- 9. @azaroth42 Web Annotation WG Update Annotation Ecosystem
- 10. @azaroth42 Web Annotation WG Update Annotation Ecosystem
- 11. @azaroth42 Web Annotation WG Update Annotation Ecosystem
- 12. @azaroth42 Web Annotation WG Update Annotation Ecosystem
- 13. @azaroth42 Web Annotation WG Update Annotation Ecosystem
- 14. @azaroth42 Web Annotation WG Update Annotation Ecosystem
- 15. @azaroth42 Web Annotation WG Update Annotation Ecosystem
- 16. @azaroth42 Web Annotation WG Update Data Model
- 17. @azaroth42 Web Annotation WG Update Data Model
- 18. @azaroth42 Web Annotation WG Update Data Model
- 19. @azaroth42 Web Annotation WG Update Data Model
- 20. @azaroth42 Web Annotation WG Update Data Model
- 21. @azaroth42 Web Annotation WG Update Specific Resource Model
- 22. @azaroth42 Web Annotation WG Update Specific Resource Model
- 23. @azaroth42 Web Annotation WG Update Specific Resource Model
- 24. @azaroth42 Web Annotation WG Update Specific Resource Model
- 25. @azaroth42 Web Annotation WG Update Significant Changes • Use developer-‐friendly names for JSON keys • Replace embedded content (ContentAsText) construction • Allow a string literal body (bodyValue) • Ordered list of options for Choice • Use structure of JSON for chains of selectors • Clearer cardinality and data type constraints • Intend to change namespace URI
- 26. @azaroth42 Web Annotation WG Update New Features • New properties: • Rights • Audience • Other Identities (canonical, via) • Rendering Software • Allow motivation for Body & Target • New Selectors: CSS, XPath, Range • Collections of Annotations
- 27. @azaroth42 Web Annotation WG Update JSON-‐LD { "@context": "http://www.w3.org/ns/anno.jsonld", "id": "http://example.org/anno20", "type": "Annotation", "body": "http://example.net/note1", "target": { "source": "http://example.com/page1.html", "selector": { "type": "CssSelector", "value": "#elemid > .elemclass + p" } } }
- 28. @azaroth42 Web Annotation WG Update Annotation Protocol • Based on Linked Data Platform (LDP) specification • Containers for Annotation management • Follows REST and Linked Data • Discovery of Annotation Containers via Link headers/elements • Paging mechanism based on Social Web WG's ActivityStreams • JSON-‐LD required, content negotiation for other RDF formats • Server will return created annotation on PUT/POST
- 29. @azaroth42 Web Annotation WG Update Next Steps • Testing! • Have a testing plan based on Web Platform • JSON-‐Schema to describe tests • Need Implementations • Need two implementations for every feature • Please let us know about your implementations! • Please test them with the tests, and contribute the results!
- 30. @azaroth42 Web Annotation WG Update Thank You! References: http://www.w3.org/TR/annotation-‐model/ http://www.w3.org/TR/annotation-‐vocab/ http://www.w3.org/TR/annotation-‐protocol/ Rob Sanderson, co-‐chair of Web Annotation WG [email protected]