W3C

W3C News

First Public Working Draft: Identifiers for WebRTC’s Statistics API

The Web Real-Time Communications Working Group has published a Working Draft of Identifiers for WebRTC’s Statistics API. Audio, video, or data packets transmitted over a peer-connection can be lost, and experience varying amounts of network delay. A web application implementing WebRTC expects to monitor the performance of the underlying network and media pipeline. This document defines the APIs and statistic identifiers used by the web application to extract metrics from the user agent. Learn more about the Ubiquitous Web Applications Activity.

First Public Working Draft: Resource Hints

The Web Performance Working Group has published a First Public Working Draft of Resource Hints. This specification defines ‘preconnect’ and ‘preload’ hints that the developer, or the server generating or delivering the resources, can use in an interoperable way to assist the user agent in the decision process of which origins it should connect to, and which resources it should fetch to improve page performance. Learn more about the Rich Web Client Activity.

W3C Launches Web Payments Initiative

W3C announced today a new Web Payments Initiative to integrate payments seamlessly into the Open Web Platform. W3C calls upon all industry stakeholders –banks, credit card companies, governments, mobile network operators, payment solution providers, technology companies, retailers, and content creators– to join the new Payments Interest Group and leverage the unique ability of the Web to bridge ecosystem diversity and reach users everywhere, on any device. The result will be new business opportunities, an improved user experience for online transactions, reduced fraud, and increased interoperability among traditional solutions and future payment innovations. Read the full press release and testimonials from W3C Members, including Bloomberg, Gemalto, GRIN Technologies, Ingenico Group, NACS, Rabobank, and Yandex.

Seven Group Notes Published by the CSS Working Group

The Cascading Style Sheets (CSS) Working Group has published seven Group Notes today, on specifications that at this time, the group does not envisage further work on.

  • CSS TV Profile 1.0. This specification defines a subset of Cascading Style Sheets Level 2 and CSS3 module: Color specifications tailored to the needs and constraints of TV devices.
  • CSS Presentation Levels Module. Presentation levels are integer values attached to elements in a document. Elements that are below, at, or above a certain threshold can be styled differently. This feature has two compelling use cases. First, slide presentations with transition effects can be described. For example, list items can be progressively revealed by sliding in from the side. Second, outline views of documents, where only the headings to a certain level are visible, can be generated.
  • CSS Mobile Profile 2.0. This specification defines in general a subset of CSS 2.1 that is to be considered a baseline for interoperability between implementations of CSS on constrained devices (e.g. mobile phones). Its intent is not to produce a profile of CSS incompatible with the complete specification, but rather to ensure that implementations that due to platform limitations cannot support the entire specification implement a common subset that is interoperable not only amongst constrained implementations but also with complete ones. Additionally, this specification aligns itself as much as possible with the OMA Wireless CSS 1.1 specification. At the same time, OMA is doing alignment work in OMA Wireless CSS 1.2. It is aimed at aligning the mandatory compliance items between CSS Mobile Profile 2.0 and OMA Wireless CSS 1.2.
  • CSS Marquee Module Level 3. This Note replaces a draft specification for CSS features relating to a “marquee” effect.
  • Behavioral Extensions to CSS. This Note replaces a proposal for features in CSS that allow to bind “behaviors” to the elements of a document. A “behavior” is defined by a URL and typically points to an object (in a language such as XBL) that defines its own appearance and user interaction. Such a binding allows, e.g. to replace an element by a complex user interface control.
  • CSS3 Hyperlink Presentation Module. This note replaces a draft specification for CSS features related to different ways of presenting hypertext.
  • The CSS ‘Reader’ Media Type. This note replaces a draft specification for a media type called ‘reader’, for targeting style sheets at devices that are able to synchronously speak and display text.

Learn more about the Style Activity.

Data on the Web Best Practices Use Cases & Requirements Draft Published

The Data on the Web Best Practices Working Group has published a Working Draft of Data on the Web Best Practices Use Cases & Requirements. This document lists use cases, compiled by the Data on the Web Best Practices Working Group, that represent scenarios of how data is commonly published on the Web and how it is used. This document also provides a set of requirements derived from these use cases that will be used to guide the development of the set of Data on the Web Best Practices and the development of two new vocabularies: Quality and Granularity Description Vocabulary and Data Usage Description Vocabulary. Learn more about the Data Activity.

CSS Regions Module Level 1 Draft Published

The Cascading Style Sheets (CSS) Working Group has published a Working Draft of CSS Regions Module Level 1. The CSS Regions module allows content from one or more elements to flow through one or more boxes called CSS Regions, fragmented as defined in CSS3-BREAK. This module also defines CSSOM to expose both the inputs and outputs of this fragmentation. 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.

Last Call: XQuery 3.1 and XQueryX 3.1; and additional supporting documents

Today the XQuery Working Group published a Last Call Working Draft of XQuery 3.1 and XQueryX 3.1. Additional supporting documents were published jointly with the XSLT Working Group: a Last Call Working Draft of XPath 3.1, together with XPath Functions and Operators, XQuery and XPath Data Model, and XSLT and XQuery Serialization. XQuery 3.1 and XPath 3.1 introduce improved support for working with JSON data with map and array data structures as well as loading and serializing JSON; additional support for HTML class attributes, HTTP dates, scientific notation, cross-scaling between XSLT and XQuery and more. Comments are welcome through 7 November 2014. Learn more about the XML Activity.

Selection API First Public Draft Published; Push API Draft Published

The Web Applications Working Group has published two documents today:

  • A First Public Working Draft of Selection API. This document is a preliminary draft of a specification for the Selection API and selection related functionality. It replaces a couple of old sections of the HTML specification, the selection part of the old DOM Range specification.
  • A Working Draft of Push API. The Push API provides webapps with scripted access to server-sent messages, for simplicity referred to here as push messages, as delivered by push services. A push service allows a webapp server to send messages to a webapp, regardless of whether the webapp is currently active on the user agent. The push message will be delivered to a Service Worker, which could then store the message’s data or display a notification to the user. This specification is designed to promote compatibility with any delivery method for push messages from push services to user agents.

Learn more about the Rich Web Client Activity.

Last Call: XSL Transformations (XSLT) Version 3.0

The XSLT Working Group has published a Last Call Working Draft of XSL Transformations (XSLT) Version 3.0. This specification defines the syntax and semantics of XSLT 3.0, a language for transforming XML documents into other XML documents. A transformation in the XSLT language is expressed in the form of a stylesheet. A stylesheet is made up of one or more well-formed XML documents conforming to the Namespaces in XML Recommendation. Comments are welcome through 26 November. Learn more about the Extensible Markup Language (XML) Activity.