[DRAFT] Device APIs and Policy Working Group Charter

Deliverables

Recommendation-Track Deliverables

The working group will deliver at least the following specifications:

a set of Personal Information Management (PIM) APIs that includes:
• Calendar API API, an API to access a calendar service (e.g. to add an entry, to edit an entry, to delete an entry, etc.) entry)
• Tasks API API, an API to access a personal task management / organizer service (e.g. to add, edit, delete a task, etc.) task)
• Contacts API API, an API to access a contacts or address book service (e.g. to add an entry, to edit an entry, to delete an entry, etc.) entry)
• Camera API Capture API, an API to manage a device's device’s camera and microphone, e.g. to take a picture or record a sound
• Messaging API API, an API to access a message service (e.g. to create a message, to and send a message, to delete a message, etc.). message. The API is agnostic to the underlying messaging service (e.g. e-mail, SMS, MMS, etc.). MMS).
System Information and Events API an
• An API to access various system services e.g. battery level, discover the current network status, etc. characteristics
FileSystem API, an
• An API to access the file system and perform basic operations (Create, Read, Update, Delete) and more complex operations (e.g. mount, unmount) - this react to a device power status
• An API should be developed in coordination with the Web Applications Working Group File Upload specification to retrieve data generically from sensors
• Application Launcher API, an An API that allows web applications to discover, identify register themselves as handlers/providers based on data string identifiers and launch the platform's native applications Application Configuration API, an API that enables other web applications to manage application settings discover these handlers/providers and user preferences User Interaction API, a set of APIs that gives a widget or website far better control of how it manifests itself on different platforms. This would include minimise/maximise functions, window size, alerting mechanisms etc. Communication Log API, an API gain permission to access information about past communication events, such as sent emails, SMS, MMS, call events. interact with them.
• Gallery API, an API to manage the local media file storage
Security Policy Framework,
• An API to express security policies that govern access of Web Applications and widgets manage vibration
• An API to security-critical APIs, including work on Identification of APIs manage systems beeps
Identification of Web Applications and Widgets
• An API to manage application menus
Definition
• An API to read the current audio volume level of a policy description language for security policies device
Expression of security policies that govern access of Web Applications
• An API for requesting and Widgets managing user permissions to security-critical APIs use device features
• An API to discover devices and services on the same device, on the local network, or directly connected, e.g. by USB and Bluetooth.
• Privacy Mechanism for Device APIs

Where practical, the API specifications should use the Web IDL formalism.

The Working Group may also enter into joint Task Forces with other groups (in particular with the Web Applications Working Group), to collaborate on specifications that cross group boundaries.

Other Deliverables

A comprehensive test suite for all features of a specification is necessary to ensure the specification's 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.

The Working Group will may also document in a Working Group Note the useful design patterns shared by the APIs it is developing.

The Working Group is also planning to work on Best Practices for Privacy-sensitive Web applications, as well as documenting Privacy Use Cases and Requirements in Working Group Notes.

Other non-normative documents may be created such as:

Milestones

Note: The actual production of some of the deliverables may follow a different timeline. The group will document documents any schedule changes on the group home page .

2009Q3 2011Q3

The Working Group reviews starts work under new charter and compares existing starting points calls for the various deliverables, and establishes a detailed roadmap. proposals for new deliverables

2009Q4-2010Q1 2011Q4

Deliverables with Contacts API becomes a Candidate Recommendation

All deliverables have assigned editors progress along Recommendation track.

2010Q2-2010Q3 2012Q1

HTML Media Capture, Battery and Network APIs becomes Candidate Recommendations

2012Q2

All deliverables are on Recommendation track. have reached First Public Working Draft status

2011Q2 2012Q4

All deliverables have reached Last Call status

2013Q2

All deliverables have reached Proposed Recommendation.