Web Applications Working Group Deliverables (Draft)

Recommendation-Track Deliverables

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

Widgets

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.

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.

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.

The XMLHttpRequest Object

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

Other Deliverables

Other non-normative documents may be created such as:

Milestones

Notes:

• The actual production of some of the deliverables may follow a different timeline. The group will document any schedule changes on the group home page.
• Although XBL2 became a Candidate Recommendation in March 2007, to address issues already identified, it will return to Working Draft in approximately 2009 and Last Call in 2010. Two of the group's members have expressed their intent to implement XBL2 but the earliest completion date for these implementations is not expected until 2011. The public is encouraged to contribute to the implementation work and/or the extensive test suite that will be required as such contributions could accelerate meeting some of the milestones.

Milestones

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