W3C

The CSV on the Web Working Group has published a Candidate Recommendation for four documents:

• Model for Tabular Data and Metadata on the Web—an abstract model for tabular data, and how to locate metadata that enables users to better understand what the data holds; this specification also contains non-normative guidance on how to parse CSV files
• Metadata Vocabulary for Tabular Data—a JSON-based format for expressing metadata about tabular data to inform validation, conversion, display and data entry for tabular data
• Generating JSON from Tabular Data on the Web—how to convert tabular data into JSON
• Generating RDF from Tabular Data on the Web—how to convert tabular data into RDF

Candidate Recommendation means that the Working Group considers the technical design to be complete, and is seeking implementation feedbacks on the documents. There are over 600 test cases and a separate document on how to use them and report on implementation results. The group is keen to get comments and implementation experiences on these specifications, either as issues on the Group’s GitHub repository or by posting to public-csv-wg-comments@w3.org.

The group expects to satisfy the implementation goals (i.e., at least two, independent implementations for each of the test cases) by October 30, 2015.

Learn more about the Data Activity.

The Web Performance Working Group has published a Working Draft of Performance Timeline Level 2. This specification extends the High Resolution Time specification HR-TIME-2 by providing methods to store and retrieve high resolution performance metric data. Learn more about the Rich Web Client Activity.

The Web Performance Working Group has published a Working Draft of High Resolution Time Level 2. This specification defines an API that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments. Learn more about the Rich Web Client Activity.

The Tracking Protection Working Group has published a Last Call Working Draft of Tracking Compliance and Scope. This specification defines a set of practices for compliance with a user’s Do Not Track (DNT) tracking preference to which a server may claim adherence. Comments are welcome through 07 October. Learn more about the Privacy Activity.

The Device APIs Working Group has published a Group Note of Permissions for Device API Access. This document notes that work on this version of the specification has been discontinued and that further development of this specification is being performed by the Web Application Security Working Group which has published an updated version of the Permissions API.

The Protocols and Formats Working Group has published Updated Working Drafts of Accessible Rich Internet Applications (WAI-ARIA) 1.1, Core Accessibility API Mappings (Core-AAM) 1.1, and Accessible Name and Description: Computation and API Mappings 1.1 (AccName-AAM).

WAI-ARIA provides an ontology of roles, states, and properties that define accessible user interface elements. It is designed to improve the accessibility and interoperability of web content, particularly web applications.

Core-AAM describes how user agents should expose semantics of content languages to accessibility APIs across multiple content technologies (including much of WAI-ARIA), and serves as the basis for other specifications to extend the mappings to specific technologies.

AccName-AAM describes how user agents determine names and descriptions of accessible objects from web content languages and expose them in accessibility APIs.

Learn more from the call for review e-mail and read about the Web Accessibility Initiative (WAI).