index.html
25.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<title>Device APIs Working Group - W3C</title>
<link rel="stylesheet" href="http://www.w3.org/2007/08/video/style.css" type="text/css" media="all" />
<style type="text/css" media="screen and (max-width:800px)">
body { margin:0;}
</style>
<link rel="stylesheet" href="http://www.w3.org/2007/08/video/print.css" type="text/css" media="print" />
<style type="text/css" media="screen">
dl.items {margin: 1em 2em;}
dl.items dt {margin: 1.5em 0 0 1em;}
dl.items dt a {font-weight: bold;}
dl.items dd {margin: 0.5em 0 0 1em;}
acronym { border-bottom: black dashed 1px }
div#navigation li.current { color: white;
font-weight: bold;
}
div#page { background-image:none;}
td.tbody_title {text-align:center;font-weight:bold;}
td.current { background-color: #afa; font-weight: bold; color: black; }
td.editor { background-color: #ffa; color: black; }
td { color: #777;}
table { border-collapse:collapse;}
th, td { border-left:thin solid black; border-right: thin solid black; text-align:left;}
th[scope=row] { font-weight: normal;}
</style>
</head>
<body>
<div id="page">
<h1>Device APIs Working Group</h1>
</div>
<!--
<div id="navigation">
<ul>
</ul>
</div>
-->
<div id="main">
<p class="logo"><a href="/"><img alt="W3C" src="/Icons/w3c_home" /></a></p>
<dl>
<dt>On this page:</dt>
<dd><a href="#mission">Mission</a>
| <a href="#roadmap">Roadmap</a>
| <a href="#devicestatus">Device Status APIs Task Force </a>
| <a href="#future">Future Work</a>
| <a href="#inputs">Submissions</a>
| <a href="#participate">Participate</a>
| <a href="#meetings">Meetings</a>
| <a href="minutes">Minutes</a>
| <a href="#comm">Communications</a>
| <a href="#docs">Documents</a>
| <a href="#history">History</a>
</dd>
<dt>Nearby:</dt>
<dd> <a href="http://www.w3.org/2009/dap/wiki/ImplementationStatus">Information
on Implementations</a>
| <a href="http://www.w3.org/2009/dap/wiki/Main_Page#Work_Documentation">WG
Notes
and Checklists</a>
| <a href="http://www.w3.org/2009/dap/wiki/Main_Page">DAP wiki</a>
| <a href="http://www.w3.org/2008/webapps/wiki/Main_Page">WebApps
WG</a>
| <a href="http://www.w3.org/html/wg/">HTML WG</a>
</dd>
<dt>Administrative:</dt>
<dd> <a href="minutes">Draft and Approved Minutes</a>
| <a href="http://www.w3.org/2005/06/tracker/users/my">"My
Actions"</a>
| <a href="http://www.w3.org/2002/09/wbs/myQuestionnaires">"My Questionnaires"</a>
| <a href="http://www.w3.org/2000/09/dbwg/details?group=43696&public=1">Participants</a>
| <a href="http://www.w3.org/2004/01/pp-impl/43696/status">Patent
Policy Status</a>
| <a href="http://www.w3.org/2009/dap/track/issues/open">Open
Issues</a>
| <a href="http://www.w3.org/2009/dap/track/actions/open">Open
Actions</a>
| <a href="http://lists.w3.org/Archives/Public/public-device-apis/">Public email list</a>
| <a href="http://lists.w3.org/Archives/Member/member-device-apis/">Member
email list</a>
| <a href="http://www.w3.org/2006/02/lc-comments-tracker/43696/">LC
Tracker</a>
</dd>
</dl>
<!-- content beg -->
<h2 id="mission">Mission</h2>
<p>As defined in its <a href="http://www.w3.org/2011/07/DeviceAPICharter">charter</a>, 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.</p>
<!-- content end -->
<!-- footer beg -->
<h2 id="roadmap">Roadmap</h2>
<p>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.</p>
<p>NB: the dates marked with a question mark have not been approved by the Working Group yet.</p>
<table id="schedule">
<thead><tr><th>Specification</th><th>Internal draft</th><th>Public Working draft</th><th>Stable draft (Last Call)</th><th>Implementors feedback (<abbr title="Candidate Recommendation">CR</abbr>)</th><th>Standard (<abbr title="Recommendation">Rec</abbr>)</th><th>Test Suite</th><th>Notes</th></tr></thead>
<tbody>
<tr><td colspan="8" class="tbody_title"><a href="http://lists.w3.org/Archives/Public/public-device-apis/2009Sep/att-0050/Device_APIs_and_Policy_Working_Group_Teleconference_--_16_Sep_2009.htm#item07">Priority APIs</a></td></tr>
<tr><th scope="row"><strong>Battery status</strong></th>
<td><a href="http://dev.w3.org/2009/dap/system-info/battery-status.html">04
Nov
2011</a></td><td class="current"><a href="http://www.w3.org/TR/2011/WD-battery-status-20110915/">15
Sep 2011</a></td><td class="current"><a href="http://www.w3.org/TR/2011/WD-battery-status-20111129/">29 Nov 2011</a></td><td colspan="3"></td><td>Managed by the <a href="#devicestatus">Device Status API task force</a></td></tr>
<tr><th scope="row"><strong>Contacts</strong> (reading from addressbook)</th><td><a href="http://w3c-test.org/dap/contacts/">31 Aug 2011</a></td><td><a href="http://www.w3.org/TR/2010/WD-contacts-api-20101209/">9 Dec 2010</a></td><td class="current"><a href="http://www.w3.org/TR/contacts-api/">16 Jun 2011</a></td><td></td><td></td><td><a href="http://w3c-test.org/dap/contacts/tests/">draft</a></td><td></td></tr>
<tr><th scope="row"><strong>HTML Media Capture</strong> (camera/microphone interactions through HTML forms)</th><td><a href="http://dev.w3.org/2009/dap/camera/">06 Apr 2011</a></td><td class="current"><a href="http://www.w3.org/TR/2011/WD-html-media-capture-20110414/">14 Apr 2011</a></td><td colspan="4"></td><td>Waiting for implementation/UX experience<br />Relation to HTML5?</td></tr>
<tr><th scope="row"><strong>Messaging</strong> (SMS, MMS, emails)</th><td><a href="http://dev.w3.org/2009/dap/messaging/">04 Jul 2011</a></td><td class="current"><a href="http://www.w3.org/TR/2011/WD-messaging-api-20110414/">14 Apr 2011</a></td><td colspan="4"></td><td></td></tr>
<tr><th scope="row"><strong>Network Information API</strong></th><td><a href="http://dev.w3.org/2009/dap/netinfo/">04 Nov 2011</a></td><td class="current"><a href="http://www.w3.org/TR/2011/WD-netinfo-api-20110607/">7 June 2011</a></td><td colspan="4"></td><td>Managed by the <a href="#devicestatus">Device Status API task force</a></td></tr>
<tr><th scope="row"><strong>Sensor API</strong></th><td class="editor"><a href="http://dev.w3.org/2009/dap/system-info/Sensors.html">11 Nov 2011</a></td><td colspan="6"></td></tr>
<tr><th scope="row"><strong>Vibration API</strong></th><td><a href="http://dev.w3.org/2009/dap/vibration/">17 Nov 2011</a></td><td class="current"><a href="http://www.w3.org/TR/2011/WD-vibration-20111117/">17 Nov 2011</a><td colspan="5"></td><td></td></tr>
<tr><th scope="row"><strong>Media Capture API</strong> (programmatic access to camera/microphone)</th><td class="editor"><a href="http://dev.w3.org/2011/webrtc/editor/getusermedia.html">30 Nov 2011</a></td><td><a href="http://www.w3.org/TR/2010/WD-media-capture-api-20100928/">28 Sep 2010</a> (but completely outdated)</td><td colspan="4"></td><td>Programmatic API that completes the form based approach.<br />Joint deliverable with the <a href="http://www.w3.org/2011/04/webrtc/">Web RTC Working Group</a> through the <a href="#mediacapture">Media Capture Task Force</a></td></tr>
</tbody>
<tbody>
<tr><td colspan="8" class="tbody_title">Other</td></tr>
<tr><th scope="row"><strong>Application Registration</strong></th><td colspan="6"></td><td>Work happens in the <a href="#webintents">Web Intents task force</a></td></tr>
<tr><th scope="row"><strong>Calendar</strong></th><td><a href="http://dev.w3.org/2009/dap/calendar/">05 May 2011</a></td><td class="current"><a href="http://www.w3.org/TR/2011/WD-calendar-api-20110419/">19 Apr 2011</a></td><td></td><td colspan="3"></td><td>Dependency on TZDate</td></tr>
<tr><th scope="row"><strong>Feature Permissions</strong></th><td class="editor"><a href="http://dev.w3.org/2009/dap/perms/FeaturePermissions.html">31 Oct 2011</a></td><td colspan="5"></td><td>Originally developed by Web Notifications WG</td></tr>
<tr><th scope="row"><strong>Menu API</strong></th><td colspan="6"></td><td></td></tr>
<tr><th scope="row"><strong>Permissions for Device API
Access</strong></th><td><a href="http://dev.w3.org/2009/dap/api-perms/">30
Sep
2010</a></td><td class="current"><a href="http://www.w3.org/TR/2010/WD-api-perms-20101005/">5
Oct 2010</a></td><td colspan="4"></td><td></td></tr>
<tr><td colspan="8" class="tbody_title">At risk</td></tr>
<tr><th scope="row">Audio
Volume (read only)</th><td colspan="6"></td><td><a href="http://lists.w3.org/Archives/Public/public-device-apis/2011Jul/att-0100/minutes-2011-07-21.html#item01">WG
Not
planning to
work on this</a></td></tr>
<tr><th scope="row">Beep</th><td colspan="6"></td><td><a href="http://lists.w3.org/Archives/Public/public-device-apis/2011Jul/att-0098/minutes-2011-07-20.html#item09">WG
Not planning to
work on this</a></td></tr>
<tr><th scope="row"><strong>Gallery</strong> (stored media interactions)</th><td class="editor"><a href="http://dev.w3.org/2009/dap/gallery/">04 Nov 2010</a></td><td colspan="5"></td><td>Relates to <a href="http://www.w3.org/TR/mediaont-api-1.0/">API for Media Resource</a>?</td></tr>
<tr><th scope="row"><strong>Systems info and events</strong> (CPU, network, etc.)</th><td><a href="http://dev.w3.org/2009/dap/system-info/">16 Mar 2011</a></td><td class="current"><a href="http://www.w3.org/TR/2010/WD-system-info-api-20100202/">2 Feb 2010</a></td><td colspan="4"></td><td><strong>Will likely need to be vastly reworked</strong></td></tr>
<tr><th scope="row">Tasks</th><td colspan="6"></td><td>No editor
— currently at risk, probably to be merged into calendar
API</td></tr>
</tbody>
<tbody>
<tr><td colspan="8" class="tbody_title">Informative documents</td></tr>
<tr><th>MediaStream Capture Scenarios</th><td class="editor"><a href="https://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/scenarios.html">6 Dec 2011</a></td><td colspan="5"></td><td>Joint deliverable with the <a href="http://www.w3.org/2011/04/webrtc/">Web RTC Working Group</a> through the <a href="#mediacapture">Media Capture Task Force</a></td></tr>
<tr><th scope="row">APIs Requirements</th><td><a href="http://dev.w3.org/2009/dap/api-reqs/">05 Jan 2011</a></td><td class="current"><a href="http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/">15 Oct 2009</a></td><td colspan="4"></td><td></td></tr>
<tr><th scope="row">Device API Access Control Use Cases and
Requirements</th><td><a href="http://dev.w3.org/2009/dap/policy-reqs/">16 Mar 2011</a></td><td class="current"><a href="http://www.w3.org/TR/2011/NOTE-dap-policy-reqs-20110317/">17 March 2011</a></td><td colspan="4"></td><td></td></tr>
<tr><th scope="row">Privacy Requirements</th><td><a href="http://dev.w3.org/2009/dap/privacy-reqs/">23 Jun 2010</a></td><td class="current"><a href="http://www.w3.org/TR/2010/NOTE-dap-privacy-reqs-20100629/">29 Jun 2010</a></td><td colspan="4"></td></tr>
<tr><th scope="row">Web Application Privacy Best
Practices</th><td><a href="http://dev.w3.org/2009/dap/privacy-practices/">27 Oct 2011</a></td><td class="current"><a href="http://www.w3.org/TR/2011/WD-app-privacy-bp-20110804/">4
August 2011</a></td><td colspan="4"></td></tr>
</tbody>
<tbody>
<tr><td colspan="8" class="tbody_title">Exploratory work</td></tr>
<tr><th scope="row">Discovery</th><td colspan="6"></td><td></td></tr>
<tr><th scope="row">Privacy Ruleset</th><td><a href="http://dev.w3.org/2009/dap/privacy-rulesets/">6 Oct 2010</a></td><td colspan="6"></td></tr>
</tbody>
</table>
<p>See also the <a href="http://www.w3.org/TR/tr-groups-all#tr_Device_APIs_Working_Group">list of the Device APIs published Technical Reports</a>.</p>
<p>As part of its technical work, the group ensures that its APIs are reviewed according to a <a href="http://www.w3.org/2009/dap/wiki/ApiCheckList">checklist of good practices for APIs</a>.</p>
<p>The history and past revisions of the documents drafts are available in the <a href="http://dev.w3.org/cvsweb/2009/dap/">W3C public CVS server</a>.</p>
<p>We use a <a href="http://www.w3.org/2006/tools/wiki/Mercurial">Mercurial repository</a> on <a href="http://dvcs.w3.org/hg/dap/file/tip">dvcs.w3.org</a>, clonable with <kbd>hg clone <a href="https://dvcs.w3.org/hg/dap">https://dvcs.w3.org/hg/dap</a></kbd>, to manage our test suites, whose latest versions are available on <a href="http://w3c-test.org/dap/">W3C Test Server, w3c-test.org</a> (<a href="http://lists.w3.org/Archives/Public/public-device-apis/2011May/0037.html">more info</a>).</p>
<p>The Working Group is <strong>not planning</strong> to work on the following items:</p>
<ul>
<li>Application configuration: already possible through <code>localStorage</code>, and with the <code>Widget</code> interface APIs</li>
<li>Orientation / Acceleration: <a href="http://lists.w3.org/Archives/Public/public-device-apis/2009Nov/0026.html">taken over by the Geolocation Working Group</a></li>
<li>Notification: see the <a href="http://www.w3.org/2010/web-notifications/">Web Notification Working Group</a></li>
<li><a href="http://dev.w3.org/2009/dap/file-system/file-writer.html">File Writing</a> and <a href="http://dev.w3.org/2009/dap/file-system/file-dir-sys.html">Filesystems</a> have been <a href="http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0180.html">moved to the Web Applications Working Group</a> in June 2010</li>
<li>A Communication Log API, due to lack of direct interest in that feature</li>
</ul>
<p id="future">
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
<a href="http://www.w3.org/2009/dap/wiki/FutureWork">FutureWork page</a> on the group's wiki.
</p>
<p>See also <a href="http://www.w3.org/2008/webapps/wiki/Coordination">coordination points with the Web Applications Working Group</a>.</p>
<h2 id="devicestatus">Device Status APIs Task Force</h2>
<p>The work on the <a href="http://dev.w3.org/2009/dap/netinfo/">Network information API</a> and the <a href="http://dev.w3.org/2009/dap/system-info/battery-status.html">Battery Status API</a> are done as part of a task force in the group, the Device Status APIs Task Force, whose discussions happen on the <a href="http://lists.w3.org/Archives/Public/public-device-status/">public-device-status@w3.org mailing list</a>. To join the task force, simply subscribe to the list.</p>
<p>The participants to the task force have the same IPR obligations as for participation in the whole group.</p>
<h2 id="mediacapture">Media Capture Task Force</h2>
<p>This is a joint activity of the <a href="#">Device APIs Working Group</a> and the <a href="http://www.w3.org/2011/04/webrtc/">Web Real-Time Communications Working Group</a>.
The work on the media capture API <code>getUserMedia</code> is done on the <a href="http://lists.w3.org/Archives/Public/public-media-capture/">publicly archived mailing list</a>: <code><<a href="mailto:public-media-capture@w3.org">public-media-capture@w3.org</a>></code>.</p>
<h2 id="webintents">Web Intents Task Force</h2>
<p>This is a joint activity of the <a href="#">Device APIs Working Group</a> and the <a href="http://www.w3.org/2008/webapps/">Web Applications Working Group</a>. 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 <a href="www.w3.org/2011/webtv/">Web & TV Interest Group</a>. The work on Web Intents is done in the Web Intents task force on the <a href="http://lists.w3.org/Archives/Public/public-web-intents/">publicly archived mailing list</a>: <code><<a href="mailto:public-web-intents@w3.org">public-web-intents@w3.org</a>></code>. Additional information is available on the <a href="http://www.w3.org/wiki/WebIntents">Web Intents Wiki</a>.</p>
<h2 id="participate">Participate</h2>
<p>If you are employed by a <a href="http://www.w3.org/Consortium/Member/List">W3C Member</a> and want to join this group, please ask your <a href="http://www.w3.org/Member/ACList">Advisory Committee Representative</a> to nominate you to the group as <a href="http://www.w3.org/2004/01/pp-impl/43696/instructions">explained in the relevant instructions</a>.</p>
<p>If you are not employed by <a href="http://www.w3.org/Consortium/Member/List">W3C Member</a> and have specific expertise to bring to this group, the <a href="http://www.w3.org/2004/01/pp-impl/43696/instructions">said instructions</a> explain how to get Invited Expert status.</p>
<p>See the list of <a href="http://www.w3.org/2000/09/dbwg/details?group=43696&public=1">current participants</a>.</p>
<h2 id="meetings">Meetings</h2>
<p>Weekly 90 minute teleconference <strong>Wednesdays,
at <a href="http://timeanddate.com/worldclock/fixedtime.html?hour=10&min=0&sec=0&p1=43">10am
US Eastern Time</a></strong>
on <a href="http://www.w3.org/2002/01/UsingZakim">Zakim
teleconference</a> bridge: <a href="tel:+1.617.761.6200">+1.617.761.6200</a> (<a href="http://www.w3.org/2006/tools/wiki/Zakim-SIP">VoIP</a>: <a href="sip:zakim@voip.w3.org">sip:zakim@voip.w3.org</a>) <strong>code
3279</strong> <a href="http://www.w3.org/Project/IRC/">IRC</a>
channel <code>#dap</code> on <code>irc.w3.org</code> port 6665
(<a href="http://irc.w3.org/?channels=#dap">Web IRC
client</a>).</p>
<ul>
<li><a href="http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=18&year=2009&hour=15&min=00&sec=0&p1=0">See time in your
time zone</a>.</li>
<li><a href="http://www.w3.org/Guide/1998/08/teleconference-calendar.html#s_3738">W3C
Calendar entry</a></li>
</ul>
<p>
Please note that attendance of DAP WG teleconferences is
restricted to registered WG participants and persons invited by the
chairs.
</p>
<p>On each call please register attendance in IRC using
</p>
<p>
<strong>Present+ firstName_lastName</strong>
</p>
and please update the information on which caller you are.
For example, if you are noted as <strong>+1-781-555-aaaa</strong>, use
<p>
<strong>zakim, aaaa is yourHandle</strong>
</p>
Cheers,
Kenny
if you are <strong>??P5</strong> then use
<p>
<strong>zakim, ??P5 is yourHandle</strong>
</p>
<p>
You can obtain agenda and bridge information
with <strong>/Topic</strong> at any time
from within IRC.
</p>
<p>We're <a href="track/">tracking issues and action items</a>
using <a href="/2005/06/tracker/">Tracker</a>. You may see your
actions
using <a href="http://www.w3.org/2005/06/tracker/users/my">MyTracker</a>. </p>
<p>
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 <a href="http://www.w3.org/2009/dap/actions-
Cheers,
Kenny
pending.html">pending
actions</a>
and <a href="http://www.w3.org/2009/dap/actions-open.html">open
actions</a> are also available .
</p>
<h3 id="f2f">Face to face meetings</h3>
<p>Our next F2F meeting is scheduled for March 20-22, in Shenzhen, China, hosted by Huawei: <a href="http://www.w3.org/2009/dap/wiki/ShenzhenF2F20011">Logistics</a>.</p>
<h2 id="minutes">Minutes</h2>
<p>
Minutes are taken in rotation, please consult
the <a href="victims-list.html">list of scribes</a> for further
details.
</p>
<p>Minutes are posted to the public list and once approved are linked
from the <a href="minutes">meetings</a> page, which also includes
links to draft minutes.</p>
<h2 id="comm">Communications</h2>
<p>The main communication channel for this group is the <a href="http://lists.w3.org/Archives/Public/public-device-apis/">publicly
archived mailing list</a> <code><<a href="mailto:public-device-apis@w3.org">public-device-apis@w3.org</a>></code>.</p>
<p>Member-confidential messages and logistical discussions can be
addressed to the
<a href="http://lists.w3.org/Archives/Member/member-device-apis/">
member-only archived mailing list</a> <code><<a href="mailto:member-device-apis@w3.org">member-device-apis@w3.org</a>></code></p>
<h2 id="docs">Documents</h2>
<p>
Here are some documents of interest to participants in the WG:
</p>
<ul>
<li><a href="http://www.w3.org/2008/security-ws/report">Workshop
Report</a> and <a href="http://www.w3.org/2008/security-ws/papers/">Position
Papers</a> from the W3C <a href="http://www.w3.org/2008/security-ws/">Workshop</a>
on Security for Access to Device APIs from the
Web</li>
<li><a href="rec-reading.html">Recommended reading</a></li>
<li><a href="editor-res.html">Editorial resources</a></li>
<li><a href="process.html">Internal process</a></li>
<li><a href="editor-pool.html">Editorial pool</a></li>
</ul>
<h2 id="ipr">Patent Policy</h2>
<p>This group operates under the W3C Patent Policy - see its <a href="http://www.w3.org/2004/01/pp-impl/43696/status">Patent Policy status</a> for more details.</p>
<h2 id="history">History</h2>
<p>The Working Group was first <a href="http://www.w3.org/2009/05/DeviceAPICharter">chartered in July 2009</a> as the “Device APIs & Policy Working Group”, as a follow-up to the <a href="http://www.w3.org/2008/security-ws/">workshop on Security for Access to Device APIs from the Web</a> held in December 2008, and then <a href="http://www.w3.org/2011/07/DeviceAPICharter">rechartered in August 2011</a> under the name “Device APIs Working Group”.</p>
<p id="policy-history">The group used to work on the following documents, but their development has been stopped:</p>
<ul>
<li><a href="http://dev.w3.org/2009/dap/policy/Framework.html"><cite>Policy Framework</cite> last editors draft</a></li>
<li><a href="http://dev.w3.org/2009/dap/policy/Profile.html"><cite>Policy Markup for Device APIs</cite> last editors draft</a></li>
</ul>
<p>The following were submitted as starting points for this group's deliverables:</p>
<ul>
<li><a href="http://lists.w3.org/Archives/Public/public-device-apis/2009Apr/att-0001/calendar.html">Nokia's calendar API</a></li>
<li><a href="http://lists.w3.org/Archives/Public/public-device-apis/2009Apr/att-0001/camera.html">Nokia's camera API</a></li>
<li><a href="http://lists.w3.org/Archives/Public/public-device-apis/2009Apr/att-0001/contacts.html">Nokia's contacts API</a></li>
<li><a href="http://lists.w3.org/Archives/Public/public-device-apis/2009Apr/att-0001/messaging.html">Nokia's messaging API</a></li>
<li><a href="http://lists.w3.org/Archives/Publi
Cheers,
Kenny
c/public-device-apis/2009Apr/att-0001/sysinfo.html">Nokia's System Info API</a></li>
<li><a href="http://lists.w3.org/Archives/Public/public-device-apis/2009Apr/att-0001/appendixa.html">Nokia's DeviceException Interface</a></li>
<li><a href="http://bondi.omtp.org/1.1/apis/index.html">BONDI 1.1 APIs</a>
(including Application Launcher, Messaging, User Interaction, File
System, Gallery, Device Status, Application Configuration Camera,
Communication Log, Contact, Calendar, Task)</li>
<li><a href="http://bondi.omtp.org/1.11/security/BONDI_Architecture_and_Security_v1.1.pdf">BONDI
Architecture and Security 1.11 Approved Release</a>
(same as 1.1; see also
<a href="http://bondi.omtp.org/1.01/security/BONDI_Architecture_and_Security_v1_01.pdf">1.01</a>, <a href="http://bondi.omtp.org/1.0/security/BONDI_Architecture_and_Security_v1.0.pdf">1.0</a>)</li>
<li><a href="http://bondi.omtp.org/1.11/">BONDI 1.11
Specifications</a> (and
also <a href="http://bondi.omtp.org/1.1/">BONDI 1.1</a> and
<a href="http://bondi.omtp.org/1.01/">BONDI 1.01
</a> and <a href="http://bondi.omtp.org/1.0/">BONDI 1.0</a>
specifications)</li>
</ul>
<p>
Also relevant are the following:
</p>
<ul>
<li><a href="http://lists.w3.org/Archives/Public/public-device-apis/2009Nov/att-0012/SecurityPolicy_09.pdf">Policy
Based Device Access Security</a>. (earlier workshop paper: <a href="http://www.w3.org/2008/security-ws/papers/SecurityPolicyNokia.pdf">Web
Runtime Policy Based Security</a>)</li>
</ul>
<p>The following documents are obsolete and should not be
referenced:</p>
<table id="obsolete">
<thead><tr><th>Specification</th><th>Internal draft</th><th>Public Working draft</th><th>Stable draft (Last Call)</th><th>Implementors feedback (<abbr title="Candidate Recommendation">CR</abbr>)</th><th>Standard (<abbr title="Recommendation">Rec</abbr>)</th><th>Test Suite</th><th>Notes</th></tr></thead>
<tbody>
<tr><th scope="row">APIs Design Patterns</th><td><a href="http://dev.w3.org/2009/dap/design-patterns/">05 Jul 2011</a></td><td colspan="6"></td></tr>
</tbody>
</table>
<div id="footer">
<address>
Robin Berjon, Frederick Hirsch, co-Chairs<br />
<a href="mailto:dsr@w3.org">Dave Raggett</a>, <span class="vcard"><a class="url fn" rel="author" href="http://www.w3.org/People/Dom/">Dominique Hazaël-Massieux</a>, Staff
Contacts</span><br />
<small>$Date: 2011/12/16 08:14:15 $</small>
</address>
</div>
<!-- footer end -->
</div>
</body>
</html>