|
| 1 | +> |
| 2 | +<html xmlns="http://www.w3.org/1999/xhtml" lang="en"> |
| 3 | + <head> |
| 4 | + <title>Making it Easier to Share Annotations on the Webtitle> |
| 5 | + <style> |
| 6 | + .title{ |
| 7 | + font-family: "Helvetica, Arial, Verdana, Geneva, sans-serif; |
| 8 | + font-size: 200%; |
| 9 | + font-weight: normal; |
| 10 | + padding: 10px 20px; |
| 11 | + background: #dbe7f0; |
| 12 | + color: #000; |
| 13 | + text-transform: uppercase; |
| 14 | + } |
| 15 | + .entry-meta{ |
| 16 | + font-family: "Helvetica, Arial, Verdana, Geneva, sans-serif; |
| 17 | + font-size: 90%; |
| 18 | + line-height: 1.41667; |
| 19 | + margin: 0; |
| 20 | + padding: 0; |
| 21 | + color: #333; |
| 22 | + } |
| 23 | + .entry-content{ |
| 24 | + font-family: "Helvetica, Arial, Verdana, Geneva, sans-serif; |
| 25 | + font-size: 108%; |
| 26 | + line-height: 1.41667; |
| 27 | + margin: 0; |
| 28 | + padding: 0; |
| 29 | + color: #333; |
| 30 | + }style> |
| 31 | + head> |
| 32 | + <body> |
| 33 | + <h1 class="title">Making it Easier to Share Annotations on the Webh1> |
| 34 | + <header class="entry-header"> |
| 35 | + <div class="entry-meta"> |
| 36 | + <p> |
| 37 | + <span class="date"><time class="entry-date" datetime="2017-02-22T12:00:00+00:00" |
| 38 | + >22 February 2017time>span> by <span class="author vcard"><a |
| 39 | + class="url fn n" href="https://www.w3.org/blog/author/tcole/" |
| 40 | + title="View all posts by Timothy Cole" rel="author">Timothy |
| 41 | + Colea>span> | Posted in: <span class="categories-links"> |
| 42 | + <a href="https://www.w3.org/blog/category/technology/annotation/" |
| 43 | + rel="category tag">Annotationa>, <a |
| 44 | + href="https://www.w3.org/blog/category/digital-publishing/" |
| 45 | + rel="category tag">Digital Publishinga>span> |
| 46 | + |
| 47 | + p> |
| 48 | + div> |
| 49 | + |
| 50 | + header> |
| 51 | + <div class="entry-content"> |
| 52 | + <p>The W3C has announced the <a href="">publicationa> of three new standards aimed to |
| 53 | + enable an ecosystem of interoperable products that let the world comment on, |
| 54 | + describe, tag, and link any resource on the Web. Many websites already allow |
| 55 | + comments, but current annotation systems rely on unique, usually proprietary |
| 56 | + technologies chosen and provided by publishers. Notes cannot be shared easily across |
| 57 | + the Web and comments about a Web page can only be saved and viewed via a single |
| 58 | + website. Readers cannot select their own tools, choose their own service providers |
| 59 | + or bring their own communities. The adoption of the Web Annotation standards will |
| 60 | + spell the end of the phrase "Don't read the comments!", returning power to the |
| 61 | + readers decide where and how they provide and consume such feedback. p> |
| 62 | + <h2>What the Web Annotation Standards Doh2> |
| 63 | + <p>The three new standards describe how to precisely identify the target of an |
| 64 | + annotation within a Web resource. They provide a basic data structure and protocol |
| 65 | + to ensure interoperability among annotation systems, but they do not dictate how |
| 66 | + annotation tools and services are realized in terms of user interface features and |
| 67 | + functionality. Each of the standards serves a specific purpose: p> |
| 68 | + <ul> |
| 69 | + <li>The <a href="https://www.w3.org/TR/annotation-model/">Annotation Data Modela> |
| 70 | + provides the structure and details for any web developer to quickly build out |
| 71 | + compatible tools and content. It gives use cases and examples for the JSON |
| 72 | + structures to create and consume.li> |
| 73 | + <li>The <a href="https://www.w3.org/TR/annotation-vocab/">Annotation Vocabularya> |
| 74 | + projects the data model into Linked Data, providing a solid and future-proof |
| 75 | + foundation to enable extension and semantic understanding. In fact, the JSON |
| 76 | + structures of the Data Model are already semantic as well as easy to implement, |
| 77 | + via the magic of the <a href="https://www.w3.org/TR/json-ld/">JSON-LDa> |
| 78 | + specification.li> |
| 79 | + <li>The <a href="https://www.w3.org/TR/annotation-protocol/">Annotation Protocola> |
| 80 | + provides a simple RESTful HTTP API for communicating among annotation clients |
| 81 | + and servers, and builds upon the <a href="https://www.w3.org/TR/ldp/">Linked |
| 82 | + Data Platforma> specification. li> |
| 83 | + ul> |
| 84 | + <p>These specifications provide the foundational material for a new generation of |
| 85 | + annotation tools on the Web while still leaving developers free to address specific |
| 86 | + use cases with tailored interfaces and services. This will encourage new innovations |
| 87 | + and the emergence of community-based best practices. For example, The W3C Working |
| 88 | + Group Note on <a href="https://www.w3.org/TR/annotation-html/">Embedding Web |
| 89 | + Annotations in HTMLa>, published concurrently with the 3 Web Annotation |
| 90 | + Recommendations, describes and illustrates just a few of the potential approaches |
| 91 | + for including annotations within HTML documents and is intended to serve as a |
| 92 | + starting point for further discussion, experimentation and development. p> |
| 93 | + <h2>Getting This Far and What's Aheadh2> |
| 94 | + <p>The work on the annotation specifications started in 2009 with two independent |
| 95 | + groups, the <a href="https://code.google.com/archive/p/annotation-ontology/" |
| 96 | + >Annotation Ontologya> and the <a href="http://www.openannotation.org/">Open |
| 97 | + Annotation Collaborationa> (both of which built upon the early W3C project: <a |
| 98 | + href="https://www.w3.org/2001/Annotea/">Annoteaa>). In 2011, the two groups |
| 99 | + joined forces to help found the <a |
| 100 | + href="https://www.w3.org/community/openannotation/">W3C Open Annotation |
| 101 | + Community Groupa>. In 2013 this Community Group published a series of <a |
| 102 | + href="https://www.w3.org/community/openannotation/#group-reports">initial draft |
| 103 | + specificationsa>. 2014 saw the creation of the Web Annotation Working Group to |
| 104 | + take the work through the standardization process and further the engagement with |
| 105 | + the web community, resulting in the specifications published on February 21st, 2017. p> |
| 106 | + <p>As a diverse group of Web developers, publishers, and content creators note below, |
| 107 | + this work is and will be increasingly important as the volume and speed of |
| 108 | + information publishing continue to grow. The world has seen a dramatic increase in |
| 109 | + the spread of misinformation and "fake news", and the web previously lacked a |
| 110 | + decentralized, trustworthy mechanism for fact checking and public discussion. Cory |
| 111 | + Doctorow, of the Electronic Frontier Foundation and the award-winning <a |
| 112 | + href="http://boingboing.net/">boingboing.neta>, describes the importance of |
| 113 | + annotation in this space: p> |
| 114 | + <blockquote>We are absolutely delighted to see these recommendations land and endorse |
| 115 | + them in full. Though much hard work remains to be done, a formal standard for a |
| 116 | + universal web annotation layer is a critical step in the development of this |
| 117 | + promising new paradigm.blockquote> |
| 118 | + <p>The potential breadth of Web annotation tools and services magnifies the impact of |
| 119 | + these specifications. As Dan Whaley, of Hypothes.is and the <a |
| 120 | + href="https://hypothes.is/annotating-all-knowledge/"> Annotating All |
| 121 | + Knowledgea> coalition, notes, the publication of these Recommendations means |
| 122 | + that:p> |
| 123 | + <blockquote>Annotation has now become a formal part of the Web —-- the importance of |
| 124 | + which cannot be overstated. Over seventy major publishers and platforms under the |
| 125 | + Annotating All Knowledge coalition have pledged to include interoperable annotations |
| 126 | + as a collaborative framework over their content, and these implementations can now |
| 127 | + move forward with confidence. More importantly, browsers can now consider enabling |
| 128 | + users to listen for conversations on every page on the Web as a native capability. blockquote> |
| 129 | + <p>Another domain that directly benefits from these standards is the |
| 130 | + multi-billion-dollar e-book publishing sector. Sharing annotations from your ePub |
| 131 | + reader — whether on your phone, computer, or dedicated device — and interacting with |
| 132 | + others regardless of their particular platform, enables massive and rapid |
| 133 | + improvements in teaching and learning at all levels. Patrick Johnson, Director of |
| 134 | + Information Modelling, at the publisher John Wiley & Sons, Inc. describes the |
| 135 | + importance of the work: p> |
| 136 | + <blockquote>We've used the Open Annotation Community Group’s Data Model at Wiley for |
| 137 | + some time. The Web Annotation specifications provide some needed improvements and |
| 138 | + additional guidance we're working to implement and look forward to continued |
| 139 | + collaboration around annotation in digital publishing.blockquote> |
| 140 | + <p>The traditions of scholarly discourse in sharing comments, annotations, etc., is a |
| 141 | + significant use case which can now be brought into the digital age of scholarly |
| 142 | + publishing. The same is true in areas like digital cultural heritage. Sheila Rabun |
| 143 | + is the Community and Communications Officer for the <a href="http://iiif.io/">IIIF |
| 144 | + Consortiuma> (International Image Interoperability Framework), currently |
| 145 | + consisting of 40 primarily academic and cultural heritage organizations including |
| 146 | + the national libraries of Britain, France, Israel, Norway, and Poland, and |
| 147 | + universities such as Stanford, Harvard, Cornell, Yale, Princeton, MIT, Oxford, |
| 148 | + Cambridge, and Tokyo. She describes the standards' importance in that community:p> |
| 149 | + <blockquote>The work done in IIIF could not happen without the groundbreaking |
| 150 | + specifications coming from the Open Annotation and Web Annotation groups. Annotation |
| 151 | + is a fundamental part of the IIIF model, and our most asked-for and discussed |
| 152 | + feature in implementations. It increases the visibility of digital cultural heritage |
| 153 | + and enables distributed online scholarship. blockquote> |
| 154 | + <p>We would like to thank everyone that has been involved throughout the process. In |
| 155 | + particular the previous co-chair, Frederick Hirsch; the W3C staff contacts, Ivan |
| 156 | + Herman and Doug Schepers; the other editors of the specifications, Benjamin Young |
| 157 | + and Paolo Ciccarese; the members of the Web Annotation Working Group, and the |
| 158 | + members of the Open Annotation Community Group. It has always been a community |
| 159 | + effort. We are grateful for the past, present, and future work underway around these |
| 160 | + specifications. p> |
| 161 | + <p>For further information please contact the Chairs of the Web Annotation Working |
| 162 | + Group, Dr. Robert Sanderson (J. Paul Getty Trust) and Prof. Timothy Cole (University |
| 163 | + of Illinois at Urbana-Champaign). To discuss uses of the Web Annotation |
| 164 | + Recommendations or to participate in the creation of implementations based on these |
| 165 | + Specifications, please join the Open Annotation W3C Community Groupp> |
| 166 | + div> |
| 167 | + body> |
| 168 | +html> |
0 commit comments