See also: IRC log
<trackbot> Date: 12 January 2011
<fjh> trackbot-ng, start telecon
<trackbot> Meeting: Device APIs and Policy Working Group Teleconference
<trackbot> Date: 12 January 2011
<fjh> http://lists.w3.org/Archives/Member/member-device-apis/2011Jan/0002.html
<fjh> seoul logistics avaiable
<fjh> ScribeNick: claes
<fjh> Approve 5 January minutes
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/att-0014/minutes-2011-01-05.html
RESOLUTION: 5 January minutes approved
<fjh> update, http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0020.html
PROPOSED RESOLUTION: Publish Access Control Requirements
RESOLUTION: Publish Access Control Requirements
<fjh> Services Discovery and Permissions - "Web Introducer"
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0016.html (Tyler)
<fjh> prototyping, http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0021.html
Encourage people to read the Web Introducer specification and check the web site
<fjh> dom notes that messaging could be layer on URI schemes, thus changing the scope of messaging
<fjh> dom notes however that change in scope not yet clear
<fjh> we need a concrete proposal on the list
<fjh> dom notes can defer uri scheme aspect, but update direction
<fjh> can that be sotd
Dom: 2 aspects, how to tie with URI schemes? send clear message where we are going
Dom proposes not to publish until document it clearer in terms of our direction with this API
<fjh> ACTION: fjh to prepare access reqmts for publishing, pubrules etc [recorded in http://www.w3.org/2011/01/12-dap-minutes.html#action01]
<trackbot> Created ACTION-324 - Prepare access reqmts for publishing, pubrules etc [on Frederick Hirsch - due 2011-01-19].
<fjh> ok with publishing early and often
<AnssiK> +1 to Rich's proposal
Rich: Prefere not to publish until clearer
<fjh> rich would like not to publish, remove dependency on permissions
Rich: we can publish but prefer a better specification before this
<fjh> dom offers to make changes over the next week, allowing publication next week
Dom: Give another week to give time for scope etc clarifications
... wants to clarify security considerations in relation to URI schemes
Daniel: Agree with Suresh.
Suresh: Clarify scope ok but not major changes
<fjh> ACTION: dom to update Messaging to clarify security considerations and URI schemes [recorded in http://www.w3.org/2011/01/12-dap-minutes.html#action02]
<trackbot> Created ACTION-325 - Update Messaging to clarify security considerations and URI schemes [on Dominique Hazaël-Massieux - due 2011-01-19].
RESOLUTION: Dom updates on scope etc and postpone publication until next week
<fjh> updates, http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0018.html
<fjh> message from Anssi, http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0031.html
Rich: Have difficulties interpreting Rich
<fjh> suresh is concerned about not having a clear javascript api
Rich: so missed to document discussion
<fjh> richt notes that can use other approaches beyond javascript api
<fjh> richt suggests using existing web framework
Rich:
IRC problems but back again
<richt> Suresh, my key question is: for adding and updating contacts, why do we need a programmatic API rather than reusing the existing web platform?
Fjh: Suresh, please docuemnt your issues in the chat or in a mail
<richt> ...we need new content on this subject. We've got a JS API. It kills the user experience. Please assume policy and permissioning is not possible.
richt: updated draft
<fjh> suresh has additional changes, will work with Rich to merge and update draft