The Device and Sensors Working Group has published 3 First Public Working Drafts of new sensor APIs to read data from accelerometers, gyroscopes
These APIs, based on the group’s Generic Sensor API, give access to the low-level sensors needed to build higher-level APIs such as the Device Orientation API, but also open up new use cases so far unavailable to the Web Platform, e.g. via innovative use of the magnetometer.
The Web Application Security Working Group has published 3 Notes:
Content Security Policy: Cookie Controls: This Note provides a historical reference for a proposed set of mechanisms by which web developers can limit the ways in which cookies may be set in the context of their sites and applications.
Content Security Policy: Pinning: This Note provides a historical reference for a proposed mechanism to allow authors to instruct user agents to remember (“pin”) and enforce a Content Security Policy for a set of hosts for a period of time.
Entry Point Regulation: This Note provides a historical reference for a proposed mechansim to mitigate the risk of reflected cross-site scripting (XSS), cross-site script inclusion (XSSI), and cross-site request forgery (CSRF) attacks by demarcating the areas of an application which are intended to be externally referencable. A specified policy is applied on external requests for all non-demarcated resources.
Today, W3Cx reopens registration for the HTML5 Part MOOC course in
self-paced mode. Entitled “Advanced Techniques for Designing HTML5
Apps”, the HTML5 Part 2 course covers advanced topics to help
developers design and deliver innovative services on the Web. As part of
the “HTML5 from W3C” XSeries, it follows the HTML5 Introduction and the HTML5 Part 1 course both available in self-paced mode.
Read this course great reviews, register and enhance your resume by purchasing a Verified Certificate. Learn lots and
The Internationalization Working Group has published a First Public Working Draft of Ethiopic Layout Requirements. This document describes requirements for the layout and presentation of text in languages that use the Ethiopic script when they are used by Web standards and technologies, such as HTML, CSS, Mobile Web, and Digital Publications. By publishing this first Working Draft we invite feedback and participation from interested parties. Learn more about other layout requirements initiatives in progress.
The Accessible Rich Internet Applications Working Group and SVG Working Group have published a First Public Working Draft of Graphics Accessibility API Mappings, along with updated Working Drafts of WAI-ARIA Graphics Module and SVG Accessibility API Mappings.
The WAI-ARIA Graphics Module defines core roles specific to web graphics that allow an author to express the logical structure of the graphic to assistive technologies. Graphics Accessibility API Mappings defines how user agents map roles in this module to the features of accessibility APIs. SVG Accessibility API Mappings provides additional mappings specific to Scalable Vector Graphics (SVG). When supported by user agents, these specifications will enable authors to create more accessible rich internet applications and graphics, including charts, graphs, and other drawings. Please send comments by 30 September 2016. Read about the Web Accessibility Initiative (WAI).
The Social Web Working Group invites implementation of two Candidate Recommendations:
- Activity Streams 2.0: This specification details a model for representing potential and completed activities using the JSON format. It is the goal of this specification to provide a JSON-based syntax that is sufficient to express metadata about activities in a rich, human-friendly but machine-processable and extensible manner. This can include constructing natural-language descriptions or visual representations about the activity, associating actionable information with various types of objects, communicating or recording activity logs, or delegation of potential actions to other applications.
- Activity Vocabulary: The Activity Streams 2.0 Vocabulary defines a set of abstract classes and properties that describe past, present and future Activities. This document defines the Activity vocabulary and its properties.
The Web Annotation Working Group has published a Candidate Recommendation for three documents:
- Web Annotation Data Model: This 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: This document describes the transport mechanisms for creating and managing annotations in a method that is consistent with the Web Architecture and REST best practices.
This is a re-publication, without substantial change, of the Candidate Recommendation published on the 5th of July for the Data Model and Vocabulary, and on the 12th of July for the Protocol. The only significant change (beyond some minor editorial clarifications and changes) is that the respective exit criteria for the Candidate Recommendation phase is now documented in the publications themselves.
Candidate Recommendation means that the Working Group considers the technical design to be complete, and is seeking implementation feedbacks on the documents. There is a separate document 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 firstname.lastname@example.org.
The group expects to satisfy the implementation goals (i.e., at least two, independent implementation for each of the test cases) by September 30, 2016.
The W3C Wiki and the W3C specifications are now accessible using the Memento “Time Travel for the Web” protocol. This is the result of a collaboration with with W3C Member Los Alamos National Laboratory, W3C Systems Team and others.
The Memento protocol is a straightforward extension of HTTP that adds a time dimension to the Web. It supports integrating live web resources, resources in versioning systems, and archived resources in web archives into an interoperable, distributed, machine-accessible versioning system for the entire web. W3C finds Memento work with online reversion history extremely useful for the Web in general and practical application on its own standards to be able to illustrate how they evolve over time. We applaud the effort in this area and are pleased to join the notable ranks of sites deploying it. For more details about this project, please read Herbert Van De Sompel’s guest W3C Blog post Memento at the W3C.
The Device and Sensors Working Group has published a Working Draft of the Generic Sensor API, a framework to bring support for any kind of sensors to the Open Web Platform. An updated Working Draft of the Ambient Light API illustrates a concrete sensor API based on this framework.
The Working Group has determined that these APIs are now advanced enough that they would benefit from getting wide review from the broader community and welcome feedback from implementors and developers on both
The Web Platform Working Group has published a Working Draft of Input Events. This specification defines additions to events for text and related input to allow for the monitoring and manipulation of default browser behavior in the context of text editor applications and other applications that deal with text input and text formatting. It builds on the UI events spec.