W3C DAP Introduction<br />for HTML5 KIG<br />BJ Kim , 2011/07/11<br />
Contents<br />APIs <br />Requirement<br />Interface<br />Code example <br />Milestones<br />
List of APIs<br />@http://www.w3.org/2010/11/DeviceAPICharter.html<br />Calendar<br />Contacts<br />Capture<br />Messaging...
Calendar - Requirement<br />High-level interfaces required to obtain read access to a user’s calendaring service.<br />W3C...
Calendar - Interface<br />
Calendar – Code Example<br />
Contact - Requirement<br />High-level interfaces required to obtain read access to a user’s unified address book.<br />W3C...
Contact - Interface<br />
Contact – Code Example<br />
Capture - Requirement<br />HTML form enhancements that provide access to the audio, image and video capture capabilities o...
Capture - Interface<br />
Capture – Code Example<br />
Messaging - Requirement<br />Provides access to messaging functionality in the device, including SMS, MMS and e-mail.<br /...
Messaging - Interface<br />
Messaging – Code Example<br />
Network Information - Requirement<br />An interface for Web Applications to access the underlying network information (con...
Network Information - Interface<br />
Network Information – Code Example<br />
Battery Status Event - Requirement<br />A new DOM event type that provides information about the battery status of the hos...
Battery Status Event - Interface<br />
Battery Status Event – Code Example<br />
Generic Sensors - Requirement<br />General interface for sensor values.<br />W3C Editor’s Draft 16 March 2011 <br />http:/...
Generic Sensors - Interface<br />
Generic Sensors – Code Example<br />
Audio Volume Level - Requirement<br />The volume level of a speaker, on a 0 to 100 scale.<br />W3C Editor’s Draft 16 March...
Audio Volume Level - Interface<br />
Audio Volume Level – Code Example<br />
Web Introducer - Requirement<br />Enables Web content to discover a user’s personal resources, no matter where they are ho...
Web Introducer - Interface<br />
Web Introducer – Code Example<br />
Gallery - Requirement<br />API that provides access to media gallery located on the device.<br />W3C Editor’s Draft 04 Nov...
Gallery - Interface<br />
Gallery – Code Example<br />
Discovery devices and services - Requirement<br />APIs for the web page scripts to discover devices and services on local ...
Discovery devices and services - Interface<br />
Discovery devices and services – Code Example<br />
Feature Permission - Requirement<br />APIs for web pages to request permission to use privileged user agent features.<br /...
Feature Permission - Interface<br />
Feature Permission – Code Example<br />
Privacy mechanism - Requirement<br />Provides definitions, use cases, and requirements for making device APIs more privacy...
Privacy mechanism – Code Example<br />
Milestones<br />@http://www.w3.org/2010/11/DeviceAPICharter.html<br /><ul><li>2011Q3
Working Group starts work under new charter and calls for proposals for new deliverables
Upcoming SlideShare
Loading in …5
×

W3C DAP APIs Overview for HTML5 KIG

2,122 views

Published on

Quick overview about W3C Device APIs.
Presented in HTML5 Korea Interest Group 7th.

Published in: Technology
1 Comment
3 Likes
Statistics
Notes
  • 20110712 W3C DAP Introduction
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
2,122
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

W3C DAP APIs Overview for HTML5 KIG

  1. 1. W3C DAP Introduction<br />for HTML5 KIG<br />BJ Kim , 2011/07/11<br />
  2. 2. Contents<br />APIs <br />Requirement<br />Interface<br />Code example <br />Milestones<br />
  3. 3. List of APIs<br />@http://www.w3.org/2010/11/DeviceAPICharter.html<br />Calendar<br />Contacts<br />Capture<br />Messaging<br />Network Information<br />Battery status event<br />Generic sensors<br />Audio volume level<br />Web Introducer<br />Gallery<br />Discovery devices and services<br />Feature permission<br />Privacy mechanism<br />
  4. 4. Calendar - Requirement<br />High-level interfaces required to obtain read access to a user’s calendaring service.<br />W3C Working Draft 19 April 2011<br />http://www.w3.org/TR/2011/WD-calendar-api-20110419/<br />Use cases<br />A web application would like to access the device calendar<br />A user would like to create/modify/delete a Calendar appointment<br />A user would like to enter a birthday of his friend with a recurrence event<br />A user would like to set a reminder for upcoming events<br />
  5. 5. Calendar - Interface<br />
  6. 6. Calendar – Code Example<br />
  7. 7. Contact - Requirement<br />High-level interfaces required to obtain read access to a user’s unified address book.<br />W3C Working Draft 16 June 2011<br />http://www.w3.org/TR/contacts-api/<br />Use cases<br />A website requests access to a user's address book<br />
  8. 8. Contact - Interface<br />
  9. 9. Contact – Code Example<br />
  10. 10. Capture - Requirement<br />HTML form enhancements that provide access to the audio, image and video capture capabilities of the device.<br />W3C Working Draft 14 April 2011<br />http://dev.w3.org/2009/dap/camera/<br />Use cases<br />A media capture file picker might render <br />
  11. 11. Capture - Interface<br />
  12. 12. Capture – Code Example<br />
  13. 13. Messaging - Requirement<br />Provides access to messaging functionality in the device, including SMS, MMS and e-mail.<br />W3C Working Draft 14 April 2011<br />http://www.w3.org/TR/messaging-api/<br />W3C Editor's Draft 04 July 2011<br />http://dev.w3.org/2009/dap/messaging/<br />Use cases<br />User can send sms, mms and email.<br />
  14. 14. Messaging - Interface<br />
  15. 15. Messaging – Code Example<br />
  16. 16. Network Information - Requirement<br />An interface for Web Applications to access the underlying network information (connection info) of the device.<br />W3C Working Draft 07 June 2011<br />http://www.w3.org/TR/netinfo-api/<br />W3C Editor's Draft 07 June 2011<br />http://dev.w3.org/2009/dap/netinfo/<br />Use cases<br />Canget information about network<br />Can decide whether network is free or not (Wifi or 3G/4G?)<br />
  17. 17. Network Information - Interface<br />
  18. 18. Network Information – Code Example<br />
  19. 19. Battery Status Event - Requirement<br />A new DOM event type that provides information about the battery status of the hosting device and associated auxiliary devices.<br />W3C Working Draft 02 June 2011<br />http://www.w3.org/TR/battery-status/<br />W3C Editor's Draft 01 July 2011<br />http://dev.w3.org/2009/dap/system-info/battery-status.html<br />Use cases<br />Using battery now?<br />Is charging now?<br />Batter remaining percentage<br />Time for batter life<br />
  20. 20. Battery Status Event - Interface<br />
  21. 21. Battery Status Event – Code Example<br />
  22. 22. Generic Sensors - Requirement<br />General interface for sensor values.<br />W3C Editor’s Draft 16 March 2011 <br />http://dev.w3.org/2009/dap/system-info/#sensors<br />For now, part of System information API rather than separate spec<br />Use cases<br />Automatically adjust the UI colors if the ambient light gets too bright<br />
  23. 23. Generic Sensors - Interface<br />
  24. 24. Generic Sensors – Code Example<br />
  25. 25. Audio Volume Level - Requirement<br />The volume level of a speaker, on a 0 to 100 scale.<br />W3C Editor’s Draft 16 March 2011 <br />http://dev.w3.org/2009/dap/system-info/#output-devices<br />For now, part of System information API rather than separate spec<br />Use cases<br />Count audio devices.<br />Get the volume of speaker on the device.<br />
  26. 26. Audio Volume Level - Interface<br />
  27. 27. Audio Volume Level – Code Example<br />
  28. 28. Web Introducer - Requirement<br />Enables Web content to discover a user’s personal resources, no matter where they are hosted, and gain permission to interact with them via a one-click user interaction.<br />Editor's Draft 4 May 2011<br />http://web-send.org/introducer/<br />Use cases<br />Link sharing<br />SMS events<br />File chooser<br />
  29. 29. Web Introducer - Interface<br />
  30. 30. Web Introducer – Code Example<br />
  31. 31. Gallery - Requirement<br />API that provides access to media gallery located on the device.<br />W3C Editor’s Draft 04 November 2010<br />http://dev.w3.org/2009/dap/gallery/<br />Use cases<br />Web application can select local image when uploading a photo to a web site.<br />User would like to sort local image (+external and online) by the specific metadata property like title, created date, location, etc<br />
  32. 32. Gallery - Interface<br />
  33. 33. Gallery – Code Example<br />
  34. 34. Discovery devices and services - Requirement<br />APIs for the web page scripts to discover devices and services on local networks, Bluetooth, USB and so on.<br />No W3C spec yet<br />http://www.w3.org/2011/04/discovery.html<br />Early demo level in WebInOS project<br />Use cases<br />Search USB, Bluetooth, Printer connectable with device<br />
  35. 35. Discovery devices and services - Interface<br />
  36. 36. Discovery devices and services – Code Example<br />
  37. 37. Feature Permission - Requirement<br />APIs for web pages to request permission to use privileged user agent features.<br />Latest published version<br />http://www.w3.org/TR/perms/ <br />BUT, “DOCUMENT NOT FOUND”<br />W3C Editor's Draft 31 May 2011<br />http://dev.w3.org/2006/webapi/WebNotifications/publish/FeaturePermissions.html<br />Use cases<br />When access to contact information is ‘Default_Denied’, can request a permission to ‘User_Allowed’.<br />
  38. 38. Feature Permission - Interface<br />
  39. 39. Feature Permission – Code Example<br />
  40. 40. Privacy mechanism - Requirement<br />Provides definitions, use cases, and requirements for making device APIs more privacy-friendly.<br />W3C Editor’s Draft 23 June 2010<br />http://dev.w3.org/2009/dap/privacy-reqs/<br />W3C Working Group Note 29 June 2010<br />http://www.w3.org/TR/dap-privacy-reqs/<br />Use cases<br />Privacy Considerations for API Usage<br />Privacy Considerations for Device Property Access<br />
  41. 41. Privacy mechanism – Code Example<br />
  42. 42. Milestones<br />@http://www.w3.org/2010/11/DeviceAPICharter.html<br /><ul><li>2011Q3
  43. 43. Working Group starts work under new charter and calls for proposals for new deliverables
  44. 44. 2011Q4
  45. 45. Contacts API becomes a Candidate Recommendation
  46. 46. All deliverables have assigned editors
  47. 47. 2012Q1
  48. 48. HTML Media Capture, Battery and Network APIs becomes Candidate Recommendations
  49. 49. 2012Q2
  50. 50. All deliverables have reached First Public Working Draft status
  51. 51. 2012Q4
  52. 52. All deliverables have reached Last Call status
  53. 53. 2013Q2
  54. 54. All deliverables have reached Proposed Recommendation.</li></li></ul><li>Thank You<br />For me -twitter : obigo / fb : byungjung.kim / g+ : gplus.to/bjkim / linkedin : http://www.linkedin.com/pub/byungjung-kim/1b/6bb/6ab<br />

×