Web Applications Working Group Deliverables

Note: This document is maintained for archival purposes, and is no longer being maintained. For an updated list of deliverables, please see the WebApps WG wiki.

For each specification, the WebApps WG must maintain an active editor, as well as authors test suites and primers or tutorials where appropriate. In order to inform our Members of our needs and requirements, a future version of this document will supply resource requirements for each specification, in the following format:

Resource Requirements

Recommendation-Track Deliverables

The current list of deliverables can be found on the WebApps WG wiki.

The working group will deliver at least the following:

Access Control for Cross-site Requests

The Access Control for Cross-site Requests specification defines a mechanism to selectively provide cross-site access to data on the Web, in circumstances in which such access is currently not available, e.g. for cross-site XMLHttpRequests.


Editors: Anne van Kesteren (Opera Software); ?

Element Traversal

Element Traversal is an ancillary specification to DOM 3 Core which allow for DOM navigation exclusively among element nodes, ignoring other content like text nodes and comments.


Editor: Doug Schepers (W3C)

Document Object Model (DOM)

The DOM specifications are one of the central aspects of Web development, defining how markup is represented in an object tree; this includes properties, methods, interfaces, and events available on a node-specific level.

DOM Level 3 Events

This specification defines the Document Object Model Events Level 3, a generic platform- and language-neutral event system which allows registration of event handlers, describes event flow through a tree structure, and provides basic contextual information for each event. The Document Object Model Events Level 3 builds on the Document Object Model Events Level 2 [DOM Level 2 Events]. This is the specification in which dynamic document interactivity and timing is described.


Editor: Andrew Emmons (Invited Expert); Doug Schepers (W3C)

DOM Level 3 Core bis

DOM 3 Core bis is intended as a maintenance release of the current DOM 3 Core specification.

DOM Level 4

To extend the functionality of DOM, and to better serve the needs of implementors and developers, this Working Group may publish a set of specifications targeting different classes of User Agents; for example, DOM 4 Server and DOM 4 Client (comprising DOM Core and DOM Events).

Clipboard Operations for the Web 1.0: Copy, Paste, Drag and Drop.

The ClipOps specification describes how common operations such as copy-and-paste and drag-and-drop work within a Web context.


Editors: Charles McCathieNevile (Opera Software); Doug Schepers (W3C); ?

File Upload

This specification provides an API used to prompt the user with a file selection dialogue and obtain the data contained in files on the user's file system in a secure way. Note: This specification may be superseded by a more general mechanism for File I/O.


Editor: none

Web Interface Definition Language (WebIDL)

This specification, formerly called "Language Bindings for DOM", defines an Interface Definition Language (IDL) to be used by specifications that define a Document Object Model (DOM). How interfaces described with this IDL correspond to constructs within ECMAScript and Java execution environments is also detailed.


Editor: Cameron McCormack (Invited Expert)

Metadata Access and Extensible Information for Media 1.0

The MAXIM specification defines methods and interfaces for reading and writing metadata to various types of media. The Media object interface does not provide any information about the DOM properties associated with a file, but rather exposes information encoded in the native file format and provides information about the source and state of the file.


Editor: Doug Schepers (W3C); ?

Network Communication API 1.0

The Network API specification defines socket connections. To enable Web applications to communicate using TCP this specification introduces the TCPSocket interface and a corresponding optional security model. This permits the implementation of an IRC client in a Web page, enables "push" content update, and other such use cases.


Editors: Gorm Haug Eriksen (Opera Software); Charles McCathieNevile (Opera Software); ?

Progress Events 1.0

This document describes event types that can be used for monitoring the progress of an operation. It is primarily intended for contexts such as data transfer operations specified by XMLHttpRequest, or Media Access Events. This covers both uploading and downloading.


Editor: Charles McCathieNevile (Opera Software); ?

Selectors API

Selectors, which are widely used in CSS, are patterns that match against elements in a tree structure. The Selectors API specification defines methods for retrieving Element nodes from the DOM by matching against a group of selectors. It is often desirable to perform DOM operations on a specific set of elements in a document. These methods simplify the process of acquiring specific elements, especially compared with the more verbose techniques defined and used in the past.


Editors: Lachlan Hunt (Opera Software); Anne van Kesteren (Opera Software)

Web Signing Profile

The Web Signing Profile specification describes a mechanism for discovering detached XML Signatures for HTML, XHTML 1, and SVG documents, and their dependent content. This specification also profiles XML Signature for use on the Web, and defines a validity model for such signatures.


Editors: Thomas Roessler (W3C); Rigo Wenning (W3C)

This profile may also be used for appropriate web packaging formats such as the Widgets specification, and for Compound Documents such as WICD.


Widgets are a class of client-side web application for displaying and/or updating local or remote data, packaged in a way to allow a single download and installation on a client machine or device. Examples include clocks, stock tickers, news casters, games and weather forecasters. As such, the Widgets specification(s) is expected to specify functionality such as: an interoperable packaging format to encapsulate and compress resources used by their widgets; an XML-based configuration format and processing model, to allow authors to declare metadata about a widget; a model to allow a user-agent to automatically locate and start the main resource of a widget; a DOM widget API; security considerations for trusted operation; widget signing; and other relevant details.

OS-specific APIs and device-specific APIs are not in scope for Widgets.


Editor: Marcos Caceres (QUT); Arve Bersvendsen (Opera Software)

Window Object 1.0

This specification defines the Window object, which provides the global namespace for web scripting languages, access to other documents in a compound document by reference, navigation to other locations, and timers. The Window object is a long-standing de facto standard for HTML user agents. However, it should not be assumed based on this or the name "Window" that it is limited to HTML or to visual user agents.


Editor: none

XML Binding Language (XBL2)

The XML Binding Language (XBL) describes the ability to associate elements in a document with script, event handlers, CSS, and more complex content models, which can be stored in another document. This can be used to re-order and wrap content so that, for instance, simple HTML or XHTML markup can have complex CSS styles applied without requiring that the markup be polluted with multiple semantically neutral div elements. It can also be used to implement new DOM interfaces, and, in conjunction with other specifications, enables arbitrary tag sets to be implemented as custom UI controls. For example, XBL could be used to implement the form controls in XForms or HTML.


Editor: Ian Hickson (Google)

The XMLHttpRequest Object

The XMLHttpRequest Object specification defines an API that provides scripted client functionality for transferring data between a client and a server.


Editor: Anne van Kesteren (Opera Software)

Other Deliverables

Other non-normative documents may be created such as:

  • Test suites for each specification
  • Primers for each specification
  • Requirements document for new specifications
  • Non-normative schemas for language formats
  • Non-normative group notes

Given sufficient resources, the Web Application Working Group should review other working groups' deliverables that are identified as being relevant to Web Applications Working Group mission.



Specification FPWD LC CR PR Rec
Access Control spec 2006-Q2 2008-Q3 2008-Q4 2009-Q4 2010
ClipOps spec 2007-Q2 2008-Q4 2009-Q2 2009-Q4 2010
DOM 3 Core 2ed spec
DOM 3 Events spec 2007-Q2 2008-Q2 2008-Q4 2009-Q4 2010
Element Traversal spec 2007-Q2 2008-Q1 2008-Q2 2008-Q4 2008
File Upload spec 2007-Q2 2008-Q2 2008-Q4 2009-Q4 2010
WebIDL spec 2007-Q2 2008-Q2 2008-Q4 2009-Q4 2010
MAXIM spec 2008-Q2 2008-Q3 2008-Q4 2009-Q2 2009
Network API spec 2008-Q2 2009-Q1 2009-Q3 2010-Q2 2010
Progress Events spec 2007-Q2 2008-Q2 2008-Q3 2009-Q2 2009
Selectors API spec 2007-Q2 2007-Q4 2008-Q2 2008-Q4 2008
Web Signing Profile spec 2007-Q4 2007-Q3 2008-Q1 2008-Q4 2009-Q4
Widgets spec 2006-Q4 2008-Q4 2009-Q1 2009-Q3 2009-Q4
Widgets Requirements 2006-Q3 2008-Q4 2009-Q1 2009-Q3 2009-Q4
Window Object spec 2007-Q2 2008-Q2 2008-Q4 2009-Q4 2010
XBL2 spec 2006-Q2 2010 2011 2013 2013
XBL2 Primer 2007-Q3 2010 2011 2013 2013
XHR Object spec 2007-Q2 2008-Q2 2008-Q4 2009-Q4 2010

Doug Schepers, <schepers@w3.org>, Proposed Team Contact
Michael(tm) Smith, <mike@w3.org>, Proposed Team Contact
Art Barstow, Nokia, Proposed Chair
Charles McCathieNevile, Opera, Proposed Chair

$Date: 2008/09/25 19:06:51 $