This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title links to the most recent version of a document.
W3C Recommendations have been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and are endorsed by the Director as Web Standards. Learn more about the W3C Recommendation Track.
Group Notes are not standards and do not have the same level of W3C endorsement.
This specification defines an API that provides Web pages scripted access to geographical location information associated with the hosting device.
This document specifies best practices for the development and delivery of Web applications on mobile devices.
This document defines requirements for controlling access to device APIs, illustrated by corresponding use cases.
This document provides definitions, use cases, and requirements for making device APIs more privacy-friendly.
These are the requirements intended to be met in the development of client-side APIs that enable the creation of Web Applications and Web Widgets that interact with devices services such as Calendar, Contacts, Camera, etc.
Offline Web Applications highlights the features in HTML 5 that address the challenge of building Web applications that work while offline.
Below are draft documents: Proposed Recommendations, Candidate Recommendations, Last Call Drafts, other Working Drafts . Some of these may become Web Standards through the W3C Recommendation Track process. Others may be published as Group Notes or become obsolete specifications.
This specification defines a client-side API to access metadata information related to media resources on the Web.
This document defines APIs for a database of records holding simple values and hierarchical objects.
This specification defines HTML form enhancements that provide access to the audio, image and video capture capabilities of the device.
This specification defines an API that enables Web pages to use the Web Sockets protocol for two-way communication with a remote host.
This specification defines an API that allows Web application authors to spawn background workers running scripts in parallel to their main page. This allows for thread-like operation with message-passing as the coordination mechanism.
This specification provides an API for representing file objects in web applications, as well as programmatically selecting them and accessing their data.
This specification adds the ability to retrieve a civic address, rather than coordinates, to the Geolocation API.
A system level API for managing the user's contacts that are stored in the system's address book.
The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server, one of the core components of “AJAX”.
This specification defines an API that provides access to a user’s unified address book.
This specification defines an API that provides access to messaging functionality in the device, including SMS, MMS and email.
This document identifies the permissions that are needed to use specific client-side APIs which grant access to sensitive data and operations.
This specification defines an API to provide Web applications with access to various hardware properties of the system which they are running on, including battery status, current network bandwidth.
These specifications have either been superseded by others, or have been abandoned. They remain available for archival purposes, but are not intended to be used.