Coordination

From WEBAPPS

Jump to: navigation, search

This wiki contains information about the relationships and coordination points between the Web Applications WG (aka WebApps) and other Working Groups such as the Device API and Policy WG (aka DAP). For example, this document identifies WebApps specifications that are referenced by DAP specifications, related specifications being produced by WebApps and DAP, etc.

WebApps' Charter and DAP's Charter formally define each WG's scope, deliverables, related groups, etc. The information in this document is superseded by the WGs' Charters.

The information is this page subject to change at any time. Members of the WGs mentioned here are encouraged to update this document. Change requests should be submitted to public-webapps@w3.org.

The WebApps and DAP WGs do all of their technical work on Public mail lists. See WebApps WorkMode wiki and DAP' home page for the names and archives of these mail lists.

For the latest publication status of all of WebApps' specs, see WebApps PubStatus. WebApps' specifications are divided into two separate tables. The first table is titled the APIs specifications and is often referred to as the group's Web APIs. Some of the Web APIs (e.g. Web Storage, Web Sockets, Server-sent Events), originated in the HTML5 specification but have since been placed in separated specifications within the Charter of the WebApps WG. The second table is dedicated to WebApps' Widgets specifications.

Contents

Widgets and DAP APIs

Currently, none of WebApps' Widgets specifications have any normative references for any of DAP's specs and none of DAP's specifications have any normative references for WebApps' widgets specifications.

However, some specifications are related, and those specifications are:

  • Widgets 1.0: Access Request Policy (aka WARP spec). Currently, the WARP specification has no normative references for any of DAP's policy specs. However, there is an expectation that as the DAP's Policy work proceeds, some type of relationship/reference may be created.

Web APIs and DAP APIs

None of WebApps' API specifications have any normative references for any of DAP's specifications.

One or more of DAP's specifications have a normative reference for the following Web APIs:

  • Web IDL - referenced by several of DAP's specs.
  • File API - MAY be referenced by DAP's FileSystem API -> currently this is a TBD

Currently, none of DAP's specifications includes a non-normative i.e informative for WebApps' API specifications.

The following specifications are related but currently do not have any normative references between WebApps' API specs and DAP's API specs:

  • Media Object (WebApps), Gallery API (DAP), API for Media Resource 1.0 (Media Annotations WG) - WebApps is not actively working on its Media Object specification because its requirements are being met by the Media Resource API being specified by the Media Annotations WG.
  • Web Notifications (WebAps) - this is related to DAP's @@@@ API

DAP Policy and WebApps Specs

Currently, DAP's policy work does not reference any of WebApps specifications. Conversely, none of WebApps' specifications reference any of DAP's policy specifications. However, that may change as DAP's policy work matures.

Web APIs and HTML WG

The following specifications were part of HTML5 but were removed from HTML5 and placed in separate specifications that are now within WebApps' Charter. Naturally, these specifications are a coordination point for the HTML WG and some of them are of interest to other WGs in W3C and/or other standards organizations:

In addition to the above specifications, the HTML WG is also interested in at least the following Web API specifications:

Widgets and HTML5

One or more of the Widgets specs include a normative reference to the following HTML5 specifications:

Additionally, a widget instance based on HTML5 may use HTML5's AppCache capability. None of the widget specifications specify application cache functionality.

Retrieved from "http://www.w3.org/2008/webapps/wiki/Coordination"