The mission of the Device API Working Group is to create specifications that enable client-side application development on the Web. In particular, the specifications in scope for this Working Group are APIs for device services such as Calendar, Contacts, Camera, etc. These APIs can be used by Web pages and Widgets to create useful applications.
|End date||31 July 2011|
|Confidentiality||Proceedings are Public|
(FTE %: TBD)
|Usual Meeting Schedule||Teleconferences: 1 per week
Face-to-face: 3-4 per year (only as needed)
In December 2008, the W3C held a Security for Access to Device APIs from the Web - W3C Workshop. The goal of this workshop was to gather information and experiences in the device API space, to start building community consensus about possible standardization work within W3C, and to gather requirements to guide such work. At the end of this workshop, the participants discussed potential areas for new standardization (see the Workshop Report for more details). Among the high priority work items identified for new standardization work was Concrete APIs such as Contacts API and Messaging API.
The primary goal of this Working Group is to create specifications for concrete APIs.
The scope of this Working Group is this creation of API specifications for a device's services. Devices in this context include desktop computers, laptop computers, mobile internet devices (MIDs), cellular phones, etc.
All of the specifications will use Web IDL to describe the API.
This Working Group's deliverables must address issues of accessibility, internationalization, mobility, and security.
Additionally, comprehensive test suites will be developed for each specification to ensure interoperability, and the group will create interoperability reports. The group will also maintain errata as required for the continued relevance and usefulness of the specifications it produces.
To advance to Proposed Recommendation, each specification is expected to have two independent implementations of each of feature defined in the specification.
The working group will deliver at least the following specifications:
Th Working Group may also enter into joint Task Forces with other groups, to collaborate on specifications that cross group boundaries.
A comprehensive test suite for all features of a specification is necessary to ensure the specification's robustness, consistency, and implementability, and to promote interoperability between User Agents. Therefore, each specification must have a companion test suite, which should be completed by the end of the Last Call phase, and must be completed, with an implementation report, before transition from Candidate Recommendation to Proposed Recommendation. Additional tests may be added to the test suite at any stage of the Recommendation track, and the maintenance of a implementation report is encouraged.
Other non-normative documents may be created such as:
Given sufficient resources, this Working Group should review other working groups' deliverables that are identified as being relevant to the Working Group's mission.
|System Information API||2010-Q1||2010-Q3||2011-Q1||2011-Q2||2011-Q3|
This Working Group's specifications will depend upon some specifications being developed by other Working Groups for example the Web Applications Working Group's Web IDL specification.
This Working Group is not aware of any dependencies other Working Groups' specification have on this Working Group's specifications.
This Working Group expects to maintain contacts with at least the following groups and Activities within W3C (in alphabetical order):
Furthermore, this Working Group expects to follow the following W3C Recommendations, Guidelines and Notes and, if necessary, to liaise with the communities behind the following documents:
The following is a tentative list of external bodies the Working Group should collaborate with:
To be successful, this Working Group is expected to have 10 or more active participants for its duration, and to have the participation of the industry leaders in fields relevant to the specifications it produces.
The Chair(s) and specification Editors are expected to contribute one to two days per week towards the Working Group. There is no minimum requirement for other Participants.
This Working Group will also allocate the necessary resources for building Test Suites for each specification.
This Working Group welcomes participation from non-Members. The group encourages questions and comments on its public mailing list, email@example.com, which is publicly archived and for which there is no formal requirement for participation. The group also welcomes non-Members to contribute technical submissions for consideration, with the agreement from each participant to Royalty-Free licensing of those submissions under the W3C Patent Policy.
The Working Group's Teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis. At least one teleconference per week is expected.
Most of the technical work of the group will be done through discussions on the firstname.lastname@example.org, the group's public mailing list. Editors within the group will use the W3C's public CVS repository to maintain Editor's Draft of specifications. The group's action and issue tracking data will also be public, as will the Member-approved minutes from all teleconferences and meetings.
The group will use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a particular member requests such a discussion.
Information about the group (for example, details about deliverables, issues, actions, status, participants) will be available from the Device API Working Group home page.
As explained in the W3C Process Document (section 3.3), this group will seek to make decisions when there is consensus and with due process. The expectation is that typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required. However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs should put a question out for voting within the group (allowing for remote asynchronous participation -- using, for example, email and/or web-based survey techniques) and record a decision, along with any objections. The matter should then be considered resolved unless and until new information becomes available.
This charter is written in accordance with Section 3.4, Votes of the W3C Process Document and includes no voting procedures beyond what the Process Document requires.
This Working Group operates under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.
This charter for this Working Group has been created according to section 6.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
Art Barstow; 23-Apr-2009