- On this page:
- Mission | Roadmap | Future Work | Submissions | Participate | Meetings | Minutes | Communications | Documents | History
- Nearby:
- Information on Implementations | WG Notes and Checklists | DAP wiki | WebApps WG | HTML WG
- Administrative:
- Draft and Approved Minutes | "My Actions" | "My Questionnaires" | Participants | Patent Policy Status | Open Issues | Open Actions | Public email list | Member email list | LC Tracker
Mission
As defined in its charter, the mission of the Device APIs Working Group is to create client-side APIs that enable the development of Web Applications and Web Widgets that interact with devices services such as Calendar, Contacts, Camera, etc.
Roadmap
As every Working Group, the Device APIs Working Group aims at gathering consensus on its specifications, both within the Working Group and with the community at large, working through an iterative process with implementors to ensure that the specifications are implementable and implemented.
The most recent working draft is highlighted as follows in the table below (it may be a working draft that was updated following a Last Call, for example).
| Example of highlighted most-recent version |
Recommendation Track Deliverables
NB: the dates marked with a question mark have not been approved by the Working Group yet.
| Specification | Internal draft | Public Working draft | Stable draft (Last Call) | Implementors feedback (CR) | Proposed Standard(PR) | Standard (Rec) | Test Suite | Notes |
|---|---|---|---|---|---|---|---|---|
| Active work | ||||||||
| Vibration API | 03 Dec 2014 | 17 Nov 2011 | 19 Jun 2014 | 9 Sep 2014 | 9 Dec 2014 | 10 Feb 2015 | approved | |
| Battery Status API | 14 Nov 2014 | 15 Sep 2011 | 28 Aug 2014 | 9 Dec 2014 | approved | |||
| HTML Media Capture (HTML form extensions for media capture) | 14 Oct 2014 | 13 Dec 2012 | 19 Jun 2014 | 9 Sep 2014 | approved | |||
| Proximity Events | 28 Apr 2014 | 12 July 2012 | 6 Dec 2012 | 1 Oct 2013 | reviewed, but incomplete | Will change based on the current work towards a generic pattern for sensor APIs | ||
| Ambient Light Events | 29 Sep 2014 | 2 August 2012 | 19 Jun 2014 | 1 Oct 2013 | reviewed, but incomplete | Will change based on the current work towards a generic pattern for sensor APIs | ||
| Media Capture and Streams (programmatic access to media streams, aka getUserMedia) | 05 Dec 2014 | 12 Feb 2015 | Feb 2015? | draft | Joint deliverable with the Web RTC Working Group through the Media Capture Task Force | |||
| MediaStream Recording (recording camera/microphone's streams) |
maintained on github
|
27 Jan 2015 | Joint deliverable with the Web RTC Working Group through the Media Capture Task Force | |||||
| MediaStream Image Capture (taking still images from a camera streams) |
maintained on github
|
27 Jan 2015 | Joint deliverable with the Web RTC Working Group through the Media Capture Task Force | |||||
| Media Capture Depth Stream Extensions (capturing streams from 3D cameras) |
maintained on github
|
29 Jan 2015 | Joint deliverable with the Web RTC Working Group through the Media Capture Task Force | |||||
| Network Service Discovery (HTTP-based services advertised via common discovery protocols within the current network.) | 18 Feb 2014 | 20 Feb 2014 | Waiting for implementors input on intents to implement | |||||
| Wake Lock API | 10 November 2014 | 12 Feb 2015 | ||||||
| Other | ||||||||
| Menu API | ||||||||
| Permissions for Device API Access | 30 Sep 2010 | 5 Oct 2010 | New proposal under discussion as of Dec 2014 | |||||
Informative documents
| Specification | Internal draft | W3C Working Group Note | Notes |
|---|---|---|---|
| MediaStream Capture Scenarios | 04 Jan 2013 | 6 Mar 2012 | Joint deliverable with the Web RTC Working Group through the Media Capture Task Force |
| Device API Access Control Use Cases and Requirements | 16 Mar 2011 | 17 March 2011 | |
| Privacy Requirements | 23 Jun 2010 | 29 Jun 2010 | |
| Web Application Privacy Best Practices | 28 Jun 2012 | 3 July 2012 | |
| Web Intents (service discovery and light-weight RPC mechanism for web apps) | 4 Sep 2012 | 23 May 2013 | Work happens in the Web Intents task force |
Exploratory work
| Specification | Internal draft | Note |
|---|---|---|
| Privacy Ruleset | 6 Oct 2010 | |
| Ambient Temperature Events | 16 Jul 2012 | |
| Ambient Humidity Events | 13 Jul 2012 | |
| Atmospheric Pressure Events | 13 Jul 2012 |
See also the list of the Device APIs published Technical Reports.
As part of its technical work, the group ensures that its APIs are reviewed according to a checklist of good practices for APIs.
The history and past revisions of the documents drafts are available in the W3C public CVS server.
We use the W3C Github Web Platform Tests repository to manage our test suites, whose latest versions are available on W3C Test Server, w3c-test.org.
The Working Group has currently shelved the following work items, waiting for a better overall approach to emerge:
- Calendar API (Previously published as a WD on 19 Apr 2011) Note, Dependency on TZDate.
- Messaging API
- Network Information API
- Sensor API
- System Information API
- Tasks API (may get merged into Calendar API)
- Pick Media Intent (access to a user's media gallery from inside a Web application), (Previously published as a FPWD on 12 July 2012).
- Pick Contacts Intent (access to a user's contacts from inside a Web application). (Previously published as a FPWD on 12 Jul 2012).
- Web Intents Addendum - Local Services (how Web Intents enabled User Agents can discover and communicate with local Web Intents Services.) (Previously published as a FPWD on 04 Oct 2012.)
The Working Group is not planning to work on the following items:
- Application configuration: already possible through
localStorage, and with theWidgetinterface APIs - Orientation / Acceleration: taken over by the Geolocation Working Group
- Notification and Feature Permissions: see the Web Notification Working Group
- File Writing and Filesystems have been moved to the Web Applications Working Group in June 2010
- A Communication Log API, due to lack of direct interest in that feature
- Audio Volume (read only) and Beep, WG Not planning to work on these
APIs that have been suggested as worth consideration for the group but not currently prioritised (and therefore not up for discussion) are kept in the FutureWork page on the group's wiki.
See also coordination points with the Web Applications Working Group.
Media Capture Task Force
This is a joint activity of the Device APIs
Working Group and the Web Real-Time
Communications Working Group. The work on the media capture
API getUserMedia is done on the publicly
archived mailing list: <public-media-capture@w3.org>.
Additional information is available on the Media Capture
Wiki.
Web Intents Task Force
This is a joint activity of the Device APIs
Working Group and the Web Applications Working
Group. The aim is to review the Web Intents proposal and to
see whether it can be adapted to support additional use cases
for service discovery, e.g. those of the Web & TV Interest
Group. The work on Web Intents is done in the Web Intents
task force on the publicly
archived mailing list: <public-web-intents@w3.org>.
Additional information is available on the Web Intents Wiki.
Participate
If you are employed by a W3C Member and want to join this group, please ask your Advisory Committee Representative to nominate you to the group as explained in the relevant instructions.
If you are not employed by W3C Member and have specific expertise to bring to this group, the said instructions explain how to get Invited Expert status.
See the list of current participants.
Meetings
Weekly 90 minute teleconference Thursdays, at
10am US Eastern Time on Zakim teleconference
bridge: +1.617.761.6200
(VoIP:
sip:zakim@voip.w3.org)
code 3279 IRC channel
#dap on irc.w3.org port 6665
(Web IRC
client).
Please note that attendance of DAP WG teleconferences is restricted to registered WG participants and persons invited by the chairs.
On each call please register attendance in IRC using
Present+ firstName_lastName
and please update the information on which caller you are. For example, if you are noted as +1-781-555-aaaa, usezakim, aaaa is yourHandle
if you are ??P5 then usezakim, ??P5 is yourHandle
You can obtain agenda and bridge information with /Topic at any time from within IRC.
We're tracking issues and action items using Tracker. You may see your actions using MyTracker.
Upon completing actions, please move them to the Pending status, and inform the WG with a summary of the action results, (including ACTION-# in the body of the message so it is linked to the action record). Text lists of pending actions and open actions are also available.
Face to face meetings
None currently scheduled.
Minutes
Minutes are taken in rotation, please consult the list of scribes for further details.
Minutes are posted to the public list and once approved are linked from the meetings page, which also includes links to draft minutes.
Communications
The main communication channel for this group is the
publicly archived mailing list <public-device-apis@w3.org>.
Member-confidential messages and logistical discussions can
be addressed to the member-only
archived mailing list <member-device-apis@w3.org>
Documents
Here are some documents of interest to participants in the WG:
- Workshop Report and Position Papers from the W3C Workshop on Security for Access to Device APIs from the Web
- Recommended reading
- Editorial resources
- Internal process
- Editorial pool
Patent Policy
This group operates under the W3C Patent Policy - see its Patent Policy status for more details.
History
The Working Group was first chartered in July 2009 as the “Device APIs & Policy Working Group”, as a follow-up to the workshop on Security for Access to Device APIs from the Web held in December 2008, and then rechartered in August 2011 under the name “Device APIs Working Group”.
The group used to work on the following documents, but their development has been stopped:
The following were submitted as starting points for this group's deliverables:
- Nokia's Calendar API
- Nokia's Camera API
- Nokia's Contacts API
- Nokia's Messaging API
- Nokia's System Info API
- Nokia's DeviceException Interface
- BONDI 1.1 APIs (including Application Launcher, Messaging, User Interaction, File System, Gallery, Device Status, Application Configuration Camera, Communication Log, Contact, Calendar, Task)
- BONDI Architecture and Security 1.11 Approved Release (same as 1.1; see also 1.01, 1.0)
- BONDI 1.11 Specifications (and also BONDI 1.1 and BONDI 1.01 and BONDI 1.0 specifications)
Also relevant are the following:
- Policy Based Device Access Security. (earlier workshop paper: Web Runtime Policy Based Security)
The following documents are obsolete and should not be referenced:
| Specification | Internal draft | Public Working draft | Stable draft (Last Call) | Implementors feedback (CR) | Standard (Rec) | Test Suite | Notes |
|---|---|---|---|---|---|---|---|
| APIs Design Patterns | 05 Jul 2011 | ||||||