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.
The CSS Working Group has published two First Public Working Drafts today:
- CSS Timing Functions Level 1, a module that describes a way for authors to define a transformation to be applied to the time of an animation. This can be used to produce animations that mimic physical phenomena such as momentum or to cause the animation to move in discrete steps producing robot-like movement.
- CSS Containment Module Level 1, a module which describes the ‘contain’ property, which indicates that the element’s subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.
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.
The Spatial Data on the Web Working Group has published a Group Note of Spatial Data on the Web Best Practices. This document advises on best practices related to the publication and usage of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices are intended for practitioners, including Web developers and geospatial experts, and are compiled based on evidence of real-world application. These best practices suggest a significant change of emphasis from traditional Spatial Data Infrastructures by adopting a Linked Data approach. As location is often the common factor across multiple datasets, spatial data is an especially useful addition to the Linked Data cloud; the 5 Stars of Linked Data paradigm is promoted where relevant.
The Internationalization Working Group has published a Working Group Note that contains templates for counter styles used by various cultures around the world. It can be used as a reference for those wishing to add user-defined counter styles in their CSS style sheets. The content of this document was originally part of the CSS Lists and Counters specification, but is now published as a standalone document. It is expected that the document will be updated from time to time to include new counter styles.
The Internationalization Working Group has published a First Public Working Draft of International text layout and typography index. This document points browser implementers and specification developers to information about how to support typographic features of scripts or writing systems from around the world, and also points to relevant information in specifications, to tests, and to useful articles and papers. It is not exhaustive, and will be added to from time to time.
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.
The Timed Text Working Group has published a Working Draft of TTML Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1). This document specifies two profiles of TTML1: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and conversion to other subtitling and captioning formats.
The Multimodal Interaction Working Group has published two Group Notes:
- Discovery & Registration of Multimodal Modality Components: This document is addressed to people who want to develop Modality Components for Multimodal Applications distributed over a local network or “in the cloud”. With this goal, in a multimodal system implemented according to the Multimodal Architecture Specification, over a network, to configure the technical conditions needed for the interaction, the system must discover and register its Modality Components in order to monitor and preserve the overall state of the distributed elements. Therefore, Modality Components can be composed with automation mechanisms in order to adapt the Application to the state of the surrounding environment.
- EMMA: Extensible MultiModal Annotation markup language Version 2.0: The W3C Multimodal Interaction Working Group aims to develop specifications to enable access to the Web using multimodal interaction. This document is part of a set of specifications for multimodal systems, and provides details of an XML markup language for containing and annotating the interpretation of user input and production of system output.
The Evaluation and Repairs Tool Working Group has published seven Group Notes:
- Requirements for the Evaluation and Report Language 1.0: This document describes the requirements for the scope, design, and features of the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, and that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format. It also provides reusable terms for generic quality assurance and validation purposes.
- Evaluation and Report Language 1.0 Schema describes the formal schema of the Evaluation and Report Language 1.0. The Evaluation and Report Language defines a vocabulary for expressing test results. It enables any person, software application, or organization to assert test results for any test subject tested against any set of criteria. The test subject might be a website, an authoring tool, a user agent, or some other entity. The set of criteria may be accessibility guidelines, formal grammars, or other types of quality assurance requirements. Thus, EARL is flexible with regard to the contexts in which it can be applied.
- Developer Guide for Evaluation and Report Language 1.0: This is a guide to the Evaluation and Report Language 1.0 for developers of software tools and processes. It provides an introduction to EARL and its uses, defines conformance requirements for tools supporting EARL, and describes approaches for serializing EARL data in different formats.
- Developers’ Guide to Features of Web Accessibility Evaluation Tools: This document describes features that web authoring and quality assurance tools can incorporate, so that they support the evaluation of accessibility requirements, such as those defined by the Web Content Accessibility Guidelines (WCAG) 2.0. The main purpose of this document is to promote awareness of such tool features and to provide introductory guidance for tool developers on what kind of features they could provide in future implementations of their tools.
- HTTP Vocabulary in RDF 1.0: The identification of resources on the Web by a Uniform Resource Identifier (URI) alone may not be sufficient, as other factors such as HTTP content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL). It provides a representation of the HTTP vocabulary in the Resource Description Framework (RDF), to allow quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. The RDF terms defined by this document represent the core HTTP specification defined by RFC 2616, as well as additional HTTP headers registered by the Internet Assigned Numbers Authority (IANA). These terms can also be used to record HTTPS exchanges.
- Representing Content in RDF 1.0: This document is a specification for a vocabulary to represent content in the Resource Description Framework (RDF). This vocabulary is intended to provide a flexible framework within different usage scenarios to semantically represent any type of content, be it on the Web or in local storage media. For example, it can be used by web quality assurance tools such as web accessibility evaluation tools to record a representation of the assessed web content, including text, images, or other types of formats. In many cases, it can be used together with HTTP Vocabulary in RDF 1.0, which allows quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. This is particularly useful for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language.
- Pointer Methods in RDF 1.0: This specification contains a framework for representing pointers – entities that permit identifying a portion or segment of a piece of content – making use of the Resource Description Framework (RDF). It also describes a number of specific types of pointers that permit portions of a document to be referred to in different ways. When referring to a specific part of, say, a piece of web content, it is useful to be able to have a consistent manner by which to refer to a particular segment of a web document, to have a variety of ways by which to refer to that same segment, and to make the reference robust in the face of changes to that document. This specification is part of the Evaluation And Report Language (EARL) but can be reused in other contexts too.