W3C News

Two Automotive First Public Working Drafts Published

The Automotive Working Group has published a Working Draft of Vehicle Data. This specification defines a standard for Vehicle Data which might be available in a vehicle. It is designed to be used in conjunction with the Vehicle API Specification.

The group also published a Working Draft of Vehicle Information Access API. The W3C Vehicle Information API aims to enable connectivity through in-vehicle infotainment systems and vehicle data access protocols. This API can also be leveraged by web applications running on mobile devices that access the data resources of a connected passenger vehicle.

Learn more about the Ubiquitous Web Applications Activity.

Discovery and Registration of Multimodal Modality Components: State Handling Draft Published

The Multimodal Interaction Working Group has published a Working Draft of Discovery & Registration of Multimodal Modality Components: State Handling. This document is addressed to people who want either 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, the system must discover and register its Modality Components in order to preserve the overall state of the distributed elements. In this way, Modality Components can be composed with automation mechanisms in order to adapt the Application to the state of the surrounding environment. Learn more about the Multimodal Interaction Activity.

W3C Invites Implementations of CSS Values and Units Module Level 3 and CSS Counter Styles Level 3

The Cascading Style Sheets (CSS) Working Group invites implementation of two Candidate Recommendations:

  • CSS Values and Units Module Level 3. This CSS3 module describes the common values and units that CSS properties accept and the syntax used for describing them in CSS property definitions.
  • CSS Counter Styles Level 3. This module introduces the counter-style rule, which allows authors to define their own custom counter styles for use with CSS list-marker and generated-content counters CSS3LIST. It also predefines a set of common counter styles, including the ones present in CSS2 and CSS2.1.

CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. Learn more about the Style Activity.

Entry Point Regulation Draft Published

The Web Application Security Working Group has published a Working Draft of Entry Point Regulation. Entry Point Regulation aims 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. Learn more about the Security Activity.

W3C Adopts new Software and Document License

W3C today adopted a new Software and Document License, an update to the W3C Software License, as the default permissive license in cases such as relicensing of unfinished specs where W3C has decided to use a permissive license. The Software and Document License, compatible with the GPL, permits copying and modification with attribution (by inclusion of a reference to the original W3C document), and can be used in W3C Community Groups, among other venues. All work that W3C has previously made available under the prior W3C Software License is also made available under the new Software and Document License.

ATAG 2.0 CR updated with simplified exit criteria

Authoring Tool Accessibility Guidelines (ATAG) 2.0 Candidate Recommendation (CR) has been updated with simplified exit criteria to bring it more in line with common W3C practices for CR exit criteria. There are no substantive changes to ATAG 2.0 itself, only to the CR exit criteria. Implementing ATAG 2.0 is also updated to keep cross-linking between the two documents in sync. The ATAG CR exit criteria have been simplified to demonstrate two implementations of each success criteria, which will reduce the testing burden. This update to the exit criteria will allow ATAG 2.0 to be completed more quickly. Learn more from the ATAG Overview and about the Web Accessibility Initiative (WAI).