# Device APIs and Policy Working Group Teleconference ## 23 Feb 2011 [Agenda][3] See also: [IRC log][4] ## Attendees Present Frederick_Hirsch, jerome_giraud, Dominique_Hazael-Massieux, Kyung-Tak_Lee, Anssi_Kostiainen, Harald_alvestrand, John_Morris, Suresh_Chitturi, Dzung_Tran, Cathy_Chan, bryan_sullivan Regrets Robin_Berjon, Maria_Oteo, Claes_Nilsson Chair Frederick_Hirsch Scribe Suresh ## Contents * [Topics][5] 1. [Seoul F2F and workshop planning][6] 2. [Subsequent F2F planning][7] 3. [Minutes approval][8] 4. [Rechartering][9] 5. [System Information][10] 6. [Messaging][11] 7. [Other API status][12] 8. [Adjourn][13] * [Summary of Action Items][14] * * * Date: 23 February 2011 ScribeNick: Suresh ### Seoul F2F and workshop planning Seoul F2F , please complete registration page, [http://www.w3.org/2002/09/wbs/43696/seoul-f2f-reg/][15] fjh: what about dial-in? Dom: Will look into to it **ACTION:** dom to reserve zakim line for f2f [recorded in [http://www.w3.org/2011/02/23-dap-minutes.html#action01][16]] Created ACTION-341 - Reserve zakim line for f2f [on Dominique Hazaël-Massieux - due 2011-03-02]. **ACTION:** Dom to reserve zakim bridge for DAP F2F [recorded in [http://www.w3.org/2011/02/23-dap-minutes.html#action02][17]] Created ACTION-342 - Reserve zakim bridge for DAP F2F [on Dominique Hazaël-Massieux - due 2011-03-02]. close ACTION-342 ACTION-342 Reserve zakim bridge for DAP F2F closed [http://www.w3.or.kr/DAP2011/][18] workshop planning: [http://lists.w3.org/Archives/Public/public-device- apis/2011Feb/0099.html][19] ### Subsequent F2F planning fjh: F2F after Seoul will be possibly June or July. We were planning on Europe, but need a host. If you can offer please let us know. ### Minutes approval Approve 16 February minutes [http://lists.w3.org/Archives/Public/public-device- apis/2011Feb/att-0097/minutes-2011-02-16.html][20] **RESOLUTION: Minutes from 16 February 2011 approved** fjh: we need hosting offers in Europe for our next F2F, in June/July timeframe ### Rechartering [http://www.w3.org/2010/11/DeviceAPICharter.html][21] Privacy, security deliverables? fjh: reminder to everyone to provide comments to the charter ### System Information [http://lists.w3.org/Archives/Public/public-device-apis/2011Feb/0091.html][22] how should this be chartered? +1 on need to rework sysinfo richt: the feedback is that is not ideal for implementers [http://www.w3.org/2010/11/DeviceAPICharter.html][21] richt: it needs to be simpler than the current model richt: need clarity that won't deliver specification as is, but simpler approach, in charter dom: sys info needs to more work e.g. define how network information is made available richt: not able to edit, would need an editor for a new spec Suresh: It is not clear what needs to be changed, is it the set of the properties or the model richt: it is deep, and more complex...probably making it small for easy implementations Suresh: one way is to cut down the properties that are non-controversial such as battery, codecs, etc.. summary - rather than create a framework for all possibilities, start with simpler spec for specific purposes, then grow as needed this approach makes privacy concern easier **ACTION:** Richard to propose better wording for System information and events api [recorded in [http://www.w3.org/2011/02/23-dap- minutes.html#action03][23]] Created ACTION-343 - Propose better wording for System information and events api [on Richard Tibbett - due 2011-03-02]. should the charter be more specific than "System Information" Suresh: we need to be explicit if we believe something should not be in scope, but not sure if we should be too specific on the supported properties Bryan: not against generic property access bryan agrees that if change in approach should have different new spec with different name fjh: should we have a new spec instead of the current spec, to be clear on scope etc? ### Messaging ### Other API status Suresh: We had the timezone issue? ACTION-333? ACTION-333 -- Richard Tibbett to draft a proposal for utcOffset based on mailing list feedback (re ISSUE-106) -- due 2011-02-16 -- OPEN [http://www.w3.org/2009/dap/track/actions/333][24] Richt: prefer to talk about it over the list Wait, I sent a message asking Rich about System Info, but I got no response I rather discuss System Info, before doing anything drastic to it I don't mind editing it, if I know what are the specifics No, I am not on the call - only on IRC today To clarify my earlier comments on sysinfo: if the intent is to focus on discrete APIs for sensors and property access than that is fine, but I would propose to drop the current sysinfo spec so that as it evolves, it does not conflict with similar implementations in the market, i.e. we need to avoid fragmentation in APIs for the same purpose, which will br brought to W3C as work in the near future. +1 from me bryan fjh: we should probably discuss this on the list ... we should try to reuse the work already done hta: do we have defintion of success? fjh: adoption and implementation the draft new charter says "To advance to Proposed Recommendation, each specification is expected to have two independent implementations of all features defined in the specification. APIs that cannot be demonstrated to be implementable securely within the default browser context will not be released." as part of the success criteria I guess we need to define "default browser context" .... ### Adjourn ## Summary of Action Items **[NEW]** **ACTION:** Dom to reserve zakim bridge for DAP F2F [recorded in [http://www.w3.org/2011/02/23-dap-minutes.html#action02][17]] **[NEW]** **ACTION:** dom to reserve zakim line for f2f [recorded in [http://www.w3.org/2011/02/23-dap-minutes.html#action01][16]] **[NEW]** **ACTION:** Richard to propose better wording for System information and events api [recorded in [http://www.w3.org/2011/02/23-dap- minutes.html#action03][23]] [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][25] version 1.135 ([CVS log][26]) $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/2011Feb/0101.html [4]: http://www.w3.org/2011/02/23-dap-irc [5]: #agenda [6]: #item01 [7]: #item02 [8]: #item03 [9]: #item04 [10]: #item05 [11]: #item06 [12]: #item07 [13]: #item08 [14]: #ActionSummary [15]: http://www.w3.org/2002/09/wbs/43696/seoul-f2f-reg/ [16]: http://www.w3.org/2011/02/23-dap-minutes.html#action01 [17]: http://www.w3.org/2011/02/23-dap-minutes.html#action02 [18]: http://www.w3.or.kr/DAP2011/ [19]: http://lists.w3.org/Archives/Public/public-device- apis/2011Feb/0099.html [20]: http://lists.w3.org/Archives/Public/public-device- apis/2011Feb/att-0097/minutes-2011-02-16.html [21]: http://www.w3.org/2010/11/DeviceAPICharter.html [22]: http://lists.w3.org/Archives/Public/public-device- apis/2011Feb/0091.html [23]: http://www.w3.org/2011/02/23-dap-minutes.html#action03 [24]: http://www.w3.org/2009/dap/track/actions/333 [25]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [26]: http://dev.w3.org/cvsweb/2002/scribe/