Three recommendations to enable Annotations on the Web
23 February 2017 | Archive
The Web Annotation Working Group has just published a Recommendation for Web Annotation in the form three documents:
- Web Annotation Data Model—specification describes a structured model and format, in JSON, to enable annotations to be shared and reused across different hardware and software platforms. Common use cases can be modeled in a manner that is simple and convenient, while at the same time enabling more complex requirements, including linking arbitrary content to a particular data point or to segments of timed multimedia resources.
- Web Annotation Vocabulary—specifies the set of RDF classes, predicates and named entities that are used by the Web Annotation Data Model. It also lists recommended terms from other ontologies that are used in the model, and provides the JSON-LD Context and profile definitions needed to use the Web Annotation JSON serialization in a Linked Data context.
- Web Annotation Protocol—describes the transport mechanisms for creating and managing annotations in a method that is consistent with the Web Architecture and REST best practices.
The group has also produced two additional Working Group Notes:
- Embedding Web Annotations in HTML—describes and illustrates potential approaches for including annotations within HTML documents. Examples also are included illustrating the use within an HTML document of annotation Selectors as fragment identifiers.
- Selectors and States—selecting part of a resource on the Web is an ubiquitous action. This document does not define any new approach to selection; instead, it relies on the formal specification and the semantics in the Web Annotation Data Model. The current document only “extracts” Selectors and States from that data model; by doing so, it makes their usage easier for applications developers whose concerns are not related to annotations.

W3C Workshop Report: Smart Descriptions and Smarter Vocabularies (SDSVoc)
20 February 2017 | Archive
W3C published today the report from the W3C “Smart Descriptions & Smarter Vocabularies (SDSVoc)” workshop, held on 30 November – 1 December 2016 in Amsterdam.
The report contains an executive summary and conclusions, as well as a brief summary and visual report of each session, with links to all presentation slides. The event’s agenda also links to the papers received and the rough notes taken throughout the event. The clear conclusion from the well attended workshop was that a new Working Group is needed to achieve two goals:
- Revise and expand the Data Catalog Vocabulary, DCAT to cover versioning, data series, APIs and more.
- Develop the concepts of data profiles (cardinality constraints and enumerated allowed values) and, from that, the mechanisms for content negotiation by those profiles. Following a careful analysis of the current state of the art, presented at the workshop, an Internet Draft is already in preparation on this topic. The WG’s role will be to put this in context and explain how fallback mechanisms can be used.
We’ve shared advance notice today that the W3C team is working on a draft charter for a new Data Exchange Working Group, and encourage public comments and suggestions on the draft charter in the dxwg GitHub issue repository.
We thank our Workshop sponsors: the EU-funded VRE4EIC project and Informatie Vlaanderen, the Flemish government’s digital agency, as well as our host, CWI, for making this event possible.

W3C Invites Implementations of XSL Transformations (XSLT) Version 3.0
7 February 2017 | Archive
The XSLT Working Group invites implementations of the Candidate Recommendation of XSL Transformations (XSLT) Version 3.0 . This specification defines the syntax and semantics of XSLT 3.0, a language designed primarily for transforming XML documents into other XML documents. XSLT 3.0 is a revised version of the XSLT 2.0 Recommendation XSLT 2.0 published on 23 January 2007.
The primary purpose of the changes in this version of the language is to enable transformations to be performed in streaming mode, where neither the source document nor the result document is ever held in memory in its entirety. Another important aim is to improve the modularity of large stylesheets, allowing stylesheets to be developed from independently-developed components with a high level of software engineering robustness.
