Features draft - next steps

At the London F2F the WG decided to work on a Features draft as a next step on Device API policies [1]. The intent is that this would be applicable to various contexts, including device APIs policy, the widget feature element, and possibly the checkPermissions proposal [2] and installable applications manifest suggestion [3] from the privacy workshop.

We also discussed the value of understanding approaches already in use, for example in Android [4].

We have a draft "Device API Features" document that includes feature URIs from the BONDI contribution to the WG. The draft is at http://dev.w3.org/2009/dap/features/ .  There are also some open actions related to this document.

Please share any proposals for text and content related to features on the DAP mailing list.  

By default I'd expect we'd refine the material from the BONDI contribution to correspond to the various API drafts in progress.

If you are able to help please let Robin and myself know.

Thanks

regards, Frederick

Frederick Hirsch, Nokia
Co-Chair, W3C DAP Working Group

[1] http://www.w3.org/2010/07/14-dap-minutes.html#action13

[2] http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0279.html and thread, 
http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/att-0343/minutes-2010-06-30.html#item03

[3] section 5, http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-24.pdf

[4] http://developer.android.com/guide/topics/security/security.html

(For tracker, this completes ACTION-244)

Received on Monday, 9 August 2010 18:00:20 UTC