# Device APIs Working Group Teleconference ## 13 Feb 2014 [Agenda][3] See also: [IRC log][4] ## Attendees Present Anssi_Kostiainen, Frederick_Hirsch, Giri_Mandyam, Mats_Wichmann, Alexander_Adolf_(IRC) Regrets Cathy_Chan, Dominique_Hazael-Massieux Chair Frederick_Hirsch Scribe fjh ## Contents * [Topics][5] 1. [Welcome, agenda review, scribe selection, announcements][6] 2. [Minutes approval][7] 3. [Network Service Discovery][8] 4. [Vibration][9] 5. [Network Information][10] 6. [Action Review][11] 7. [HTML Media Capture][12] 8. [Issues][13] 9. [Other Business][14] 10. [Adjourn][15] * [Summary of Action Items][16] * * * Date: 13 February 2014 ScribeNick: fjh ### Welcome, agenda review, scribe selection, announcements alexander from LG, sent mail to list couple of days ago [http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0022.html][17] fjh: Thanks, not clear on participation status ### Minutes approval Approve minutes from 6 February 2014 [http://lists.w3.org/Archives/Public/public-device- apis/2014Feb/att-0020/minutes-2014-02-06.html][18] **RESOLUTION: Minutes from 6 February 2014 are approved** ### Network Service Discovery Discussion held with WebAppSec WG, 12 Feb, [http://lists.w3.org/Archives/Public/public-webappsec/2014Feb/0029.html][19] raw minutes [http://www.w3.org/2014/02/12-webappsec-minutes.html#item03][20] Proposal: Publish updated WD: [http://lists.w3.org/Archives/Public/public- device-apis/2014Feb/0026.html][21] fjh: rationale for publishing is that addition of CORs is a meaningful addition gmandyam: does Chromium team know about CORs change, they filed bug, do they know about change **ACTION:** fjh to follow up on letting Chromium team know about CORS addition to Network Service Discovery [recorded in [http://www.w3.org/2014/02/13-dap-minutes.html#action01][22]] Created ACTION-681 - Follow up on letting chromium team know about cors addition to network service discovery [on Frederick Hirsch - due 2014-02-20]. Chromium discussion on NSD: [https://groups.google.com/a/chromium.org/forum/#!topic/blink- dev/HT0KZKuTLxM][23] fjh: changes can happen after publishing WD but want to be consistent with current state ... feedback on list [http://lists.w3.org/Archives/Public/public-device- apis/2014Feb/0022.html][17] , [http://lists.w3.org/Archives/Public/public- device-apis/2014Feb/0024.html][24] ... defer discussion to list, want to include Rich ... plan to go ahead with publishing WD after talking with Rich, editor. No CfC needed. ### Vibration LC 3 published, see [http://www.w3.org/TR/2014/WD-vibration-20140211/][25] ends 4 March 2014 thread on public-web-mobile, [http://lists.w3.org/Archives/Public/public-web- mobile/2014Feb/0016.html][26] anssik: seen this, nothing we need to do … can emulate strength with existing API … so no need to add such a feature … have already replied so this thread is finished fjh: sent message to chairs list, included HTML and WebApps WG for review, included Anne in cc list … if anyone else needs notice please share information with them … assume we will go to CR after LC ### Network Information fjh: Publish as Note? I would prefer to first update as we’ve discussed for a publication even as a Note, since it has more agreement than previously published version thoughts? [http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0023.html][27] anssik: need to capture status fjh: right, but want to update the draft ... will respond to Mounir about updating the draft before publishing it as a Note ### Action Review ACTION-523? ACTION-523 -- Anssi Kostiainen to Work on test cases for battery, vibration, and HTML Media Capture -- due 2012-08-31 -- OPEN [http://www.w3.org/2009/dap/track/actions/523][28] fjh: pending actions to close close ACTION-679 Closed ACTION-679. close ACTION-680 Closed ACTION-680. ### HTML Media Capture [https://www.w3.org/2009/dap/wiki/ImplementationStatus#HTML_Media_Capture][29] fjh: example interop report [http://www.w3.org/2007/xmlsec/interop/xmldsig/report.html][30] ... more recent example [http://www.w3.org/TR/2012/NOTE-xmldsig- core1-interop-20121113/][31] ... we might want to check with Dom for other examples, also thoughts on how to deal with tests involving UI interaction ... benefit of publishing a Note is that there is a clear record that is easy to share, not required to publish a Note ... another approach in web apps, [http://dev.w3.org/2006/waf/widgets/imp- report/][32] ... approach depends on situation, number of tests, need for clarity etc ... usability matters so we should try to help there ... older example of web page, [http://www.w3.org/Signature/2001/04/05 -xmldsig-interop.html][33] ... checked on our CR exit criterion - "verified two interoperable deployed implementations" [https://github.com/w3c/web-platform-tests/pull/306][34] anssik: we have two implementations, test suite pending review fjh: so this is work we might be able to move forward beyond CR soon? anssik: we should work on progressing this one ... status update [http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/0028.html][35] … we can progress this one, also learn in process anssik: perhaps we should take best practice from WebApps for going to PR fjh: or we can take other approach, might be different. maybe we should get ideas from Dom as well anssik: how does group end fjh: when WG is no longer working on deliverables (we still have a number) then it can shut down or stay alive for maintenance, there will be choices but this is premature now ### Issues fjh: open issues relate to network service discovery, see agenda or tracker for details [http://www.w3.org/2009/dap/track/issues/open][36] … also one for Network Information ISSUE-128 ISSUE-128 -- Need more description on how bandwidth should be estimated -- open [http://www.w3.org/2009/dap/track/issues/128][37] ### Other Business None ### Adjourn ## Summary of Action Items **[NEW]** **ACTION:** fjh to follow up on letting Chromium team know about CORS addition to Network Service Discovery [recorded in [http://www.w3.org/2014/02/13-dap-minutes.html#action01][22]] [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][38] version 1.135 ([CVS log][39]) $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/2014Feb/0028.html [4]: http://www.w3.org/2014/02/13-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/2014Feb/0022.html [18]: http://lists.w3.org/Archives/Public/public-device- apis/2014Feb/att-0020/minutes-2014-02-06.html [19]: http://lists.w3.org/Archives/Public/public- webappsec/2014Feb/0029.html [20]: http://www.w3.org/2014/02/12-webappsec-minutes.html#item03 [21]: http://lists.w3.org/Archives/Public/public-device- apis/2014Feb/0026.html [22]: http://www.w3.org/2014/02/13-dap-minutes.html#action01 [23]: https://groups.google.com/a/chromium.org/forum/#!topic/blink- dev/HT0KZKuTLxM [24]: http://lists.w3.org/Archives/Public/public-device- apis/2014Feb/0024.html [25]: http://www.w3.org/TR/2014/WD-vibration-20140211/ [26]: http://lists.w3.org/Archives/Public/public-web- mobile/2014Feb/0016.html [27]: http://lists.w3.org/Archives/Public/public-device- apis/2014Feb/0023.html [28]: http://www.w3.org/2009/dap/track/actions/523 [29]: https://www.w3.org/2009/dap/wiki/ImplementationStatus#HTML_Media_Capture [30]: http://www.w3.org/2007/xmlsec/interop/xmldsig/report.html [31]: http://www.w3.org/TR/2012/NOTE-xmldsig-core1-interop-20121113/ [32]: http://dev.w3.org/2006/waf/widgets/imp-report/ [33]: http://www.w3.org/Signature/2001/04/05-xmldsig-interop.html [34]: https://github.com/w3c/web-platform-tests/pull/306 [35]: http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/0028.html [36]: http://www.w3.org/2009/dap/track/issues/open [37]: http://www.w3.org/2009/dap/track/issues/128 [38]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [39]: http://dev.w3.org/cvsweb/2002/scribe/