W3C

W3C News

W3C Invites Implementations of Tracking Compliance and Scope

The Tracking Protection Working Group invites implementation of the Candidate Recommendation of Tracking Compliance and Scope. Do Not Track is designed to provide users with a simple mechanism to express a preference to allow or limit online tracking. Complying with the user’s preference includes limits on the collection, retention and use of data collected as a third party to user actions and the sharing of data not permanently de-identified. 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.

First Public Working Draft of Payment Request API Specifications

The Web Payments Working Group has published First Public Working Drafts of the following specifications. These are the first of a suite of specifications to make payments on the Web easier and more secure.

  • Payment Request API, which describes a web API to allow merchants (i.e., web sites selling physical or digital goods) to easily accept payments through different payment methods with minimal integration.
  • Basic Card Payment describes the data formats used by the Payment Request API to support payment by payment cards such as credit or debit cards.
  • Payment Method Identifiers defines payment method identifier strings so that components in the payment ecosystem can determine which parties support which payment methods.

The Working Group published a FAQ and welcomes feedback on these early drafts.

TTML Profiles for Internet Media Subtitles and Captions 1.0 (IMSC1) is a W3C Recommendation

The Timed Text Working Group has published a W3C Recommendation of TTML Profiles for Internet Media Subtitles and Captions 1.0 (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.

Tim Berners-Lee to Keynote IDPF’s DigiCon event 10 May 2016 in Chicago

W3C is pleased to announce that Tim Berners-Lee, Web Inventor and W3C Director, will deliver a keynote address on Tuesday, 10 May 2016 at IDPF DigiCon, the annual digital publishing conference hosted by the International Digital Publishing Forum (IDPF) and co-located with Book Expo America (BEA) at McCormick Place in Chicago, Illinois, USA. In his talk, “Realizing the Vision of Publishing Technology with Web Technology” Berners-Lee will preview potential new ways of reading, authoring and publishing in the future that are being made possible by the new rich media environment for publishing.

For the past three years W3C’s Digital Publishing Activity has been collaborating with the IDPF and other publishing industry groups to bring key requirements of the publishing industry to the Web. For more information, see the Media Advisory. To register for the DigiCon event, see registration form.

Web Storage (Second Edition) is a W3C Recommendation

The Web Platform Working Group has published a W3C Recommendation of Web Storage (Second Edition). This specification defines an API for persistent data storage of key-value pair data in Web clients. It introduces two related mechanisms, similar to HTTP session cookies, for storing name-value pairs on the client side. The first mechanism is designed for scenarios where the user is carrying out a single transaction, but could be carrying out multiple transactions in different windows at the same time. The second mechanism is designed for storage that spans multiple windows, and lasts beyond the current session.

First Public Working Draft: Cascading Style Sheets Level 2 Revision 2 (CSS 2.2) Specification

The Cascading Style Sheets (CSS) Working Group has published a Working Draft of Cascading Style Sheets Level 2 Revision 2 (CSS 2.2) Specification. This specification defines Cascading Style Sheets level 2. CSS is a style sheet language that allows authors and users to attach style (e.g. fonts and spacing) to structured documents (e.g. HTML documents and XML applications). By separating the presentation style of documents from the content of documents, CSS simplifies Web authoring and site maintenance.

First Public Working Draft: Reporting API 1

The Web Performance Working Group has published a Working Draft of Reporting API 1. This document defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.

W3Cx and Intel open HTML5 Introduction MOOC course

html 5 logo next to introW3C is pleased to launch today a new course: HTML5 Introduction. Taught by Intel and W3C experts, this course presents the basic building blocks of Web design and style, using basics of HTML5 and a few CSS features. We encourage future Web developers to enroll soon to learn how to build Web sites that look great. This introductory 6-week course nicely completes the “Learn HTML5 from W3C” XSeries group of three courses – all are open for registration.

WebCrypto Key Discovery Note Published

The Web Cryptography Working Group has published a Group Note of WebCrypto Key Discovery. This note describes a JavaScript API for discovering named, origin-specific pre-provisioned cryptographic keys for use with the Web Cryptography API. Pre-provisioned keys are keys which have been made available to the UA by means other than the generation, derivation, importation and unwrapping functions of the Web Cryptography API. Origin-specific keys are keys that are available only to a specified origin. Named keys are identified by a name assumed to be known to the origin in question and provisioned with the key itself. This note concerns only keys which have all three of these properties.

Call for Review: Battery Status API Proposed Recommendation Published

The Device APIs Working Group has published a Proposed Recommendation of Battery Status API. The Battery Status API specification defines a means for web developers to programmatically determine the battery status of the hosting device. Without knowing the battery status of a device, a web developer must design the web application with an assumption of sufficient battery level for the task at hand. This means the battery of a device may exhaust faster than desired because web developers are unable to make decisions based on the battery status. This specification defines an API that provides information about the battery status of the hosting device. Comments are welcome through 29 April.