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.
For related introductory information, see: JavaScript Web APIs.
Completed Work
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.
Standards
|
2012-06-19
|
translations
·
errata
This specification defines a media feature to match the different visual presentation modes that can be applied to web applications and thereby apply different styling based on these different modes using CSS Media Queries.
|
|
2012-02-07
|
translations
·
errata
This specification defines the security model controlling network access from within a widget, as well as a method for widget authors to request that the user agent grant access to certain network resources or sets thereof.
|
|
2011-09-27
|
translations
·
errata
A more recent draft may replace this Recommendation.
This specification standardizes a general purpose packaging format for installable client-side Web applications (widgets). Widgets can be authored with Web standards, such as HTML, CSS, and JavaScript, and have many use cases: this format has been successfully used as the container format for web browser extensions, as standalone applications on devices, and even as server-side applications that get embedded into Web pages.
|
Group Notes
|
2012-03-13
|
This specification defines the widget URI scheme that is used to
address resources inside a widget package.
|
|
2011-09-27
|
This document lists the design goals and requirements that were used by the Web Applications Working Group to standardize installable client-side Web applications (widgets).
|
|
2011-03-17
|
This document defines requirements for controlling access to device APIs, illustrated by corresponding use cases.
|
|
2010-06-29
|
This document provides definitions, use cases, and requirements for making device APIs more privacy-friendly.
|
|
2009-10-15
|
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.
|
Drafts
Below are draft documents:
Proposed Recommendations, Proposed Edited 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.
Proposed Recommendations
|
2012-05-22
|
This specification defines an application programming interface (API) for widgets that provides, amongst other things, functionality for accessing a widget’s metadata and persistently storing data.
|
|
2011-08-11
|
This document defines a profile of the XML-Signature Syntax and
Processing specification to allow a widget resource to be
digitally signed.
|
Proposed Edited Recommendations
|
2012-09-25
|
This specification standardizes a Zip-based packaging format for software known as widgets. Widgets are client-side applications that are authored using Web standards, but whose content can also be embedded into Web documents.
|
Last Call Drafts
|
2012-03-22
|
This specification defines a process and a document format to allow a user agent to update an installed widget package with different version of a widget package.
|
Other Working Drafts
|
2008-04-14
|
This document surveys a group of market-leading widget user agents with the aim to
inform the requirements of the Widgets 1.0: Requirements document. The
survey exposes commonalities and fragmentation across widget user agents, and discusses
how fragmentation currently affects, amongst other things, authoring, security,
distribution and deployment, internationalisation and the device-independence of widgets.
The document concludes by making a set of recommendations on what aspects of widgets
require standardization to reduce fragmentation to ultimately standardize a
cross-platform widget solution.
|
W3C
