W3C

The Web Cryptography Working Group invites implementation of the Candidate Recommendation of Web Cryptography API. This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications. Learn more about the Security Activity.

The Web Annotation Working Group has published a First Public Working Draft of Web Annotation Data Model. Annotations are typically used to convey information about a resource or associations between resources. Simple examples include a comment or tag on a single web page or image, or a blog post about a news article. The Web Annotation Data Model specification describes a structured model and format to enable annotations to be shared and reused across different hardware and software platforms. Learn more about the Digital Publishing Activity.

The Protocols and Formats Working Group today published a First Public Working Draft of Accessible Name and Description: Computation and API Mappings 1.1 (AccName-AAM) and updated Working Drafts of Accessible Rich Internet Applications (WAI-ARIA) 1.1 and Core Accessibility API Mappings (Core-AAM) 1.1. 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).

The Timed Text Working Group invites implementation of the Candidate Recommendation of TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0. This document specifies two profiles of Timed Text Markup Language 1: 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. The text profile is a superset of TTML Simple Delivery Profile for Closed Captions (US). Learn more about the Video in the Web Activity.

The Web Applications Working Group has published two Working Drafts today:

• URL. The URL Standard defines URLs, domains, IP addresses, the application/x-www-form-urlencoded format, and their API.
• Clipboard API and events. This document describes APIs for clipboard operations such as copy, cut and paste in web applications.

Learn more about the Rich Web Client Activity.

The Device APIs Working Group invites implementation of the Candidate Recommendation of Battery Status API. This specification defines an API that provides information about the battery status of the hosting device. Learn more about the Ubiquitous Web Applications Activity.

The Device APIs Working Group has published a Proposed Recommendation of Vibration API. This specification defines an API that provides access to the vibration mechanism of the hosting device. Vibration is a form of tactile feedback. Comments are welcome through 20 January 2015. Learn more about the Ubiquitous Web Applications Activity.