# Device APIs and Policy Working Group Teleconference ## 12 Jan 2011 [Agenda][3] See also: [IRC log][4] ## Attendees Present Frederick_Hirsch, Robin_Berjon, Rich_Tibbett, Cecile_Marc, Dong-Young_Lee, Kyung-Tak_Lee, Suresh_Chitturi, jerome_giraud, Claes_Nilsson, arun_prasath, Maria_Oteo, Anssi_Kostiainen, Dzung_Tran, Daniel_Coloma, Dom Regrets John_Morris, Thomas_Roessler Chair Frederick_Hirsch, Robin_Berjon Scribe claes ## Contents * [Topics][5] 1. [Administrative][6] 2. [Minutes][7] 3. [Access Control Requirements][8] 4. [Web Introducer][9] 5. [Messaging][10] 6. [Contacts][11] 7. [Calendar][12] 8. [Adjourn][13] * [Summary of Action Items][14] * * * Date: 12 January 2011 trackbot-ng, start telecon Meeting: Device APIs and Policy Working Group Teleconference Date: 12 January 2011 [http://lists.w3.org/Archives/Member/member-device- apis/2011Jan/0002.html][15] seoul logistics avaiable ScribeNick: claes ### Administrative ### Minutes Approve 5 January minutes [http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/att-0014/minutes-2011-01-05.html][16] **RESOLUTION: 5 January minutes approved** ### Access Control Requirements update, [http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0020.html][17] PROPOSED RESOLUTION: Publish Access Control Requirements **RESOLUTION: Publish Access Control Requirements** ### Web Introducer Services Discovery and Permissions - "Web Introducer" [http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0016.html][18] (Tyler) prototyping, [http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0021.html][19] Encourage people to read the Web Introducer specification and check the web site ### Messaging dom notes that messaging could be layer on URI schemes, thus changing the scope of messaging dom notes however that change in scope not yet clear we need a concrete proposal on the list dom notes can defer uri scheme aspect, but update direction 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 **ACTION:** fjh to prepare access reqmts for publishing, pubrules etc [recorded in [http://www.w3.org/2011/01/12-dap-minutes.html#action01][20]] Created ACTION-324 - Prepare access reqmts for publishing, pubrules etc [on Frederick Hirsch - due 2011-01-19]. ok with publishing early and often +1 to Rich's proposal Rich: Prefere not to publish until clearer rich would like not to publish, remove dependency on permissions Rich: we can publish but prefer a better specification before this 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 **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][21]] 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** ### Contacts updates, [http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0018.html][22] message from Anssi, [http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0031.html][23] Rich: Have difficulties interpreting Rich suresh is concerned about not having a clear javascript api Rich: so missed to document discussion richt notes that can use other approaches beyond javascript api richt suggests using existing web framework Rich: IRC problems but back again 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 ...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. ### Calendar richt: updated draft suresh has additional changes, will work with Rich to merge and update draft ### Adjourn ## Summary of Action Items **[NEW]** **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][21]] **[NEW]** **ACTION:** fjh to prepare access reqmts for publishing, pubrules etc [recorded in [http://www.w3.org/2011/01/12-dap-minutes.html#action01][20]] [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][24] version 1.135 ([CVS log][25]) $Date: 2009-03-02 03:52:20 $ [1]: http://www.w3.org/Icons/w3c_home [2]: http://www.w3.org/ [3]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0022.html [4]: http://www.w3.org/2011/01/12-dap-irc [5]: #agenda [6]: #item01 [7]: #item02 [8]: #item03 [9]: #item04 [10]: #item05 [11]: #item06 [12]: #item07 [13]: #item08 [14]: #ActionSummary [15]: http://lists.w3.org/Archives/Member/member-device- apis/2011Jan/0002.html [16]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/att-0014/minutes-2011-01-05.html [17]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0020.html [18]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0016.html [19]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0021.html [20]: http://www.w3.org/2011/01/12-dap-minutes.html#action01 [21]: http://www.w3.org/2011/01/12-dap-minutes.html#action02 [22]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0018.html [23]: http://lists.w3.org/Archives/Public/public-device- apis/2011Jan/0031.html [24]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [25]: http://dev.w3.org/cvsweb/2002/scribe/