# Device APIs Working Group Teleconference ## 31 Oct 2013 [Agenda][3] See also: [IRC log][4] ## Attendees Present Frederick_Hirsch, Lisa_DeLuca, Giri_Mandyam, Tatsuya_Igarashi, Cathy_Chan Regrets Jean-Claude_Dufourd, Anssi_Kostiainen, Dominique_Hazael-Massieux Chair Frederick_Hirsch Scribe fjh ## Contents * [Topics][5] 1. [Welcome, agenda review, scribe selection, announcements][6] 2. [Minutes approval][7] 3. [Vibration][8] 4. [Network Service Discovery][9] 5. [Proximity, Light Test update][10] 6. [Note publication][11] 7. [Issue Review][12] 8. [Action review][13] 9. [Other Business][14] 10. [Adjourn][15] * [Summary of Action Items][16] * * * Date: 31 October 2013 ScribeNick: fjh ### Welcome, agenda review, scribe selection, announcements RfC: Updates of the Technical Reports process; deadline November 27, [http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0158.html][17] fjh: more information on git is available, see [http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0174.html][18] ### Minutes approval Approve minutes from 17 October 2013 [http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/att-0141/minutes-2013-10-17.html][19] **RESOLUTION: Minutes from 17 October 2013 are approved** ### Vibration ISSUE-156? ISSUE-156 -- add the [Clamp] attribute to the argument of the vibrate method -- open [http://www.w3.org/2009/dap/track/issues/156][20] fjh: I think this is a good idea to add to our specification, suggest Anssi add this **ACTION:** anssik to review ISSUE-156 and add Clamp to vibration specification [recorded in [http://www.w3.org/2013/10/31-dap- minutes.html#action01][21]] Created ACTION-670 - Review issue-156 and add clamp to vibration specification [on Anssi Kostiainen - due 2013-11-07]. ### Network Service Discovery Updated draft, [https://dvcs.w3.org/hg/dap/raw-file/default/discovery- api/Overview.html][22] fjh: Rich summarized Mitigating router compromise, [http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0152.html][23] ... proposed text for ISSUE-130, as part of ACTION-654: Propose text for network service discovery to define wildcard api and feature detection ; [http://lists.w3.org/Archives/Public/public-device-apis/2013Oct/0157.html][24] (Jean-Claude) cathy: jean-claude enables wild card search, a good idea ... independent of the other discussion ... other discussion is to support UPnP devices rather than at service level … initially I proposed adding search string for UPnP device type … but we might want to change data model to device model, support UPnP devices naturally, problem is that in mDns there is no device concept fjh: not sure it makes sense to create a dummy model when abstracting to obtain uniformity cathy: works if we make device for each service in mdns, thus we can achieve device level for UPnP naturally, but also have it work for others … need opinion from Rich for this fjh: looks like we are near reaching a conclusion and consensus ... i would like to schedule a security review with WebAppSec and also a privacy review with PING but am waiting until the specification stabiliizes … this change wouldn't be ready for TPAC (and WebAppSec is not meeting then anyway) … so once we get the data model updated then I think we can start reviews cathy: this should be a fairly big change fjh: we have a scheduled slot for the privacy review in January with PING so it would be good to get these changes done in November if possible ... no more to discuss, need feedback from Rich ### Proximity, Light Test update no new information ### Note publication Updated CfC (ended 29 Oct): [http://lists.w3.org/Archives/Public/public- device-apis/2013Oct/0130.html][25] fjh: we had agreement on call, no disagreement on list ... The CfC has concluded successfully so we can make these changes ### Issue Review ISSUE-151? ISSUE-151 -- USN should not be used as device identifier -- open [http://www.w3.org/2009/dap/track/issues/151][26] fjh: this issue includes a proposal, status? cathy: this needs to be looked at and agreed fjh: need to revive this on the list ### Action review ACTION-666? ACTION-666 -- Giridhar Mandyam to Check with internal implementers whether vibration api is consistent with chip capabilities -- due 2013-10-17 -- OPEN [http://www.w3.org/2009/dap/track/actions/666][27] gmandyam: still working on this ### Other Business no other business fjh: Upcoming calls: next week (7 Nov), week after TPAC (21 Nov), 5 Dec, 12 Dec, 19 Dec ... No call week of TPAC, 14 Nov, no call US Thanksgiving week (28 Nov) ### Adjourn ## Summary of Action Items **[NEW]** **ACTION:** anssik to review ISSUE-156 and add Clamp to vibration specification [recorded in [http://www.w3.org/2013/10/31-dap- minutes.html#action01][21]] [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][28] version 1.135 ([CVS log][29]) $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/2013Oct/0161.html [4]: http://www.w3.org/2013/10/31-dap-irc [5]: #agenda [6]: #item01 [7]: #item02 [8]: #item03 [9]: #item04 [10]: #item05 [11]: #item06 [12]: #item07 [13]: #item08 [14]: #item09 [15]: #item10 [16]: #ActionSummary [17]: http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/0158.html [18]: http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/0174.html [19]: http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/att-0141/minutes-2013-10-17.html [20]: http://www.w3.org/2009/dap/track/issues/156 [21]: http://www.w3.org/2013/10/31-dap-minutes.html#action01 [22]: https://dvcs.w3.org/hg/dap/raw-file/default/discovery- api/Overview.html [23]: http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/0152.html [24]: http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/0157.html [25]: http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/0130.html [26]: http://www.w3.org/2009/dap/track/issues/151 [27]: http://www.w3.org/2009/dap/track/actions/666 [28]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [29]: http://dev.w3.org/cvsweb/2002/scribe/