# Device APIs and Policy Working Group Teleconference ## 19 May 2010 [Agenda][3] See also: [IRC log][4] ## Attendees Present Robin_Berjon, Frederick_Hirsch, Soonho_Lee, Alissa_Cooper, Max_Froumentin, Dominique_Hazael-Massieux, Suresh_Chitturi, Ilkka_Oksanen, Maria_Oteo, Claes_Nilsson, Richard_Tibbett, Maria, Angeles, Oteo, Dzung_Tran, John_Morris Regrets Erica_Newland, Laura_Arribas, Thomas_Roessler Chair Robin_Berjon, Frederick_Hirsch Scribe arve ## Contents * [Topics][5] 1. [Administrative][6] 2. [Minutes approval][7] 3. [Policy requirements][8] 4. [APIs][9] 5. [Filereader][10] * [Summary of Action Items][11] * * * Date: 19 May 2010 scribenick: arve ### Administrative ### Minutes approval 12 May 2010 [http://lists.w3.org/Archives/Public/public-device- apis/2010May/att-0054/minutes-2010-05-12.html][12] **RESOLUTION: 12 may 2010 minutes approved** ### Policy requirements [http://lists.w3.org/Archives/Public/public-device- apis/2010May/0083.html][13] **RESOLUTION: Regrouping requirements OK** ### APIs max status summary [http://lists.w3.org/Archives/Public/public-device- apis/2010May/0063.html][14] maxf: one outstanding issue remaining ISSUE-64? ISSUE-64 -- "Generic" sensors may permit discovering sensitive information -- RAISED [http://www.w3.org/2009/dap/track/issues/64][15] privacy [http://lists.w3.org/Archives/Public/public-device- apis/2010May/0072.html][16] suresh [http://lists.w3.org/Archives/Public/public-device- apis/2010May/0073.html][17] [Alissa's comments][18] maxf will implement changes as suggested **ACTION:** maxf to implement privacy changes noted by alissa, see [http://lists.w3.org/Archives/Public/public-device-apis/2010May/0072.html][16] [recorded in [http://www.w3.org/2010/05/19-dap-minutes.html#action01][19]] Created ACTION-173 - Implement privacy changes noted by alissa, see [http://lists.w3.org/Archives/Public/public-device-apis/2010May/0072.html][16] [on Max Froumentin - due 2010-05-26]. action-173: target is sysinfo ACTION-173 Implement privacy changes noted by alissa, see [http://lists.w3.org/Archives/Public/public-device-apis/2010May/0072.html][16] notes added suresh asks about 4.7, naming +1 on a complete table suresh talking about table in annex portion of his comments maxf: will be responding to suresh's concerns one by one on mailing list rberjon: primary non-editorial concern is the synchronicity of getters ... some sensors might be slow to respond, hence use of async for get suresh: are we optimizing for corner cases with use of callbacks? ... sysinfo is information you have readily available suresh proposes should use monitor function instead of get in this kind of case arve: should we really increase API complexity by adding another method for synchronous getters prefer consistency in using async methods, reducing complexity of number of choices arve: implementors complexity increases by adding synchronous getters [I tend to agree with arve and max, developers are used to using async nowadays] the same argument could be made for Contacts API [privacy and security] Arve: some properties like SSID are static. Privacy sensitive APIs which will ask the user for consent will need asynchronous we agreed on general async approach to avoid blocking, enable privacy consent etc darobin: will not want to block on modal dialogs webworkers might help, but they wouldn't prevent authors to make blocking dialogs if they wanted. +1 to consistent model, uniformity and enabling flexibility in changing which need consent or dialogs **RESOLUTION: will keep getters asynchronous** fjh, you wanted to ask about minimization, [http://lists.w3.org/Archives/Public/public-device-apis/2010May/0076.html][20] [http://lists.w3.org/Archives/Public/public-device- apis/2010May/0076.html][20] alissa: in terms of the network property network properties minimization alissa: provide only information about the active connection? [on mobiles, it is common to have 3G and MMS :)] arve: how common are multiple active connections? e.g. wired and wireless at once etc [in general, I think it makes sense to only expose active connections] it's a reality that devices have more than one connection, but no one seems to know whether it's worth supporting in the API. That's noted in the specification. alissa: wants to discuss use cases for multiple active connections also want to know use cases more broadly, for MAC address, SSID, etc. alissa: do you need to know the sensitive information from particular active or inactive connections maxf, you wanted to say more maxf: no proper discussion on the properties in the network interfaces have taken place +1 on proper discussion maxf: this would be a good opportunity to initialize this discussion can we use alissa's email as a starting point? +1 on doing discussion on list **ACTION:** alissa will provide an initial analysis of properties [recorded in [http://www.w3.org/2010/05/19-dap-minutes.html#action02][21]] Created ACTION-174 - Will provide an initial analysis of properties [on Alissa Cooper - due 2010-05-26]. fjh: do we remove speculation on when we go to CR? ... (on the DAP home page) ### Filereader darobin: discussion about FileReader (by WebApps) ... please provide feedback to that WG, as it is of some importance to this group s/scribenick arve// ## Summary of Action Items **[NEW]** **ACTION:** alissa will provide an initial analysis of properties [recorded in [http://www.w3.org/2010/05/19-dap-minutes.html#action02][21]] **[NEW]** **ACTION:** maxf to implement privacy changes noted by alissa, see [http://lists.w3.org/Archives/Public/public-device-apis/2010May/0072.html][16] [recorded in [http://www.w3.org/2010/05/19-dap-minutes.html#action01][19]] [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][22] version 1.135 ([CVS log][23]) $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/2010May/0084.html [4]: http://www.w3.org/2010/05/19-dap-irc [5]: #agenda [6]: #item01 [7]: #item02 [8]: #item03 [9]: #item04 [10]: #item05 [11]: #ActionSummary [12]: http://lists.w3.org/Archives/Public/public-device- apis/2010May/att-0054/minutes-2010-05-12.html [13]: http://lists.w3.org/Archives/Public/public-device- apis/2010May/0083.html [14]: http://lists.w3.org/Archives/Public/public-device- apis/2010May/0063.html [15]: http://www.w3.org/2009/dap/track/issues/64 [16]: http://lists.w3.org/Archives/Public/public-device- apis/2010May/0072.html [17]: http://lists.w3.org/Archives/Public/public-device- apis/2010May/0073.html [18]: http://lists.w3.org/Archives/Public/public-device- apis/2010May/0071.html [19]: http://www.w3.org/2010/05/19-dap-minutes.html#action01 [20]: http://lists.w3.org/Archives/Public/public-device- apis/2010May/0076.html [21]: http://www.w3.org/2010/05/19-dap-minutes.html#action02 [22]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [23]: http://dev.w3.org/cvsweb/2002/scribe/