# Device APIs Working Group Teleconference ## 09 Jan 2014 [Agenda][3] See also: [IRC log][4] ## Attendees Present Frederick_Hirsch, Mats_Wichmann, Anssi_Kostiainen, Dominique_Hazael- Massieux, Lisa_DeLuca Regrets Chair Frederick_Hirsch Scribe fjh ## Contents * [Topics][5] 1. [Welcome, agenda review, scribe selection, announcements][6] 2. [Minutes approval][7] 3. [Shelving Notes][8] 4. [Vibration][9] 5. [Ambient Light][10] 6. [Network Information API][11] 7. [Testing][12] 8. [Roadmap planning][13] 9. [Issue Review][14] 10. [Action Review][15] 11. [Other Business][16] 12. [Adjourn][17] * [Summary of Action Items][18] * * * Date: 09 January 2014 trackbot, start telecon Meeting: Device APIs Working Group Teleconference Date: 09 January 2014 ### Welcome, agenda review, scribe selection, announcements ScribeNick: fjh proposed RESOLUTION: Cancel 23 January 2014 teleconference. proposed RESOLUTION: Cancel 24 April 2014 teleconference. +1 on cancelling both **RESOLUTION: Cancel 23 January 2014 teleconference** fjh: and **RESOLUTION: Cancel 24 April 2014 teleconference.** fjh: will update minutes page, which has upcoming meetings [http://www.w3.org/2009/dap/minutes.html#upcoming-teleconferences][19] ### Minutes approval Approve minutes from12 December 2013 [http://lists.w3.org/Archives/Public/public-device- apis/2013Dec/att-0027/minutes-2013-12-12.html][20] **RESOLUTION: Minutes from 12 December 2013 are approved** ### Shelving Notes fjh: Drafts updated, publication request submitted. Planned publication date 14 January 2014 Links to drafts: [http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/0009.html][21] dom: we agreed not to have home page news fjh: yes dom: need to contact Comm team fjh: I can do that ### Vibration Issue status summary: [http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/0005.html][22] Issue-149? Issue-149 -- handling of long vibration list - truncate or no vibration at all -- open [http://www.w3.org/2009/dap/track/issues/149][23] proposed change is here: [http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/0012.html][24] second change here: [http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/0112.html][25] [http://dev.w3.org/cvsweb/2009/dap/vibration/Overview.src.html.diff?r 1=1.7;r2=1.8;f=h][26] [http://dev.w3.org/cvsweb/2009/dap/vibration/Overview.src.html][27] fjh: believe we need new LC and CR for the normative algorithm change anssik: ok, can add note then as well, agree for need for publication [http://dev.w3.org/cvsweb/2009/dap/vibration/Overview.src.html.diff?r 1=1.6;r2=1.7;f=h][28] allow concurrent invocations in different browsing contexts (ACTION-652) anssik: this is another change **ACTION:** anssik to update Vibration spec with note related o ISSUE-149 and update status section to list changes since last CR publication [recorded in [http://www.w3.org/2014/01/09-dap-minutes.html#action01][29]] Created ACTION-673 - Update vibration spec with note related o issue-149 and update status section to list changes since last cr publication [on Anssi Kostiainen - due 2014-01-16]. **ACTION:** fjh to open CfC for LC publication of Vibration [recorded in [http://www.w3.org/2014/01/09-dap-minutes.html#action02][30]] Created ACTION-674 - Open cfc for lc publication of vibration [on Frederick Hirsch - due 2014-01-16]. ### Ambient Light fjh: Do we have a resolution of question whether to merge light level event into LightEvent and rename, [http://lists.w3.org/Archives/Public/public- device-apis/2013Apr/0043.html][31] ? ... is this resolved? anssik: working on implementation and then can send in feedback in next few months fjh: can we publish update now or wait for implementation anssik: should wait for implementation feedback fjh: ok, this will impact the schedule, makes sense, but does move the schedule out anssik: yes, will double check on implementation plans ### Network Information API Marcos has proposal, [http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/0013.html][32] fjh: I suggest we should have further list discussion on this, but wanted to bring to your attention anssi: having connection type is useful … this proposal could accommodate different levels of abstraction, so this might work fjh: we have a detailed issue yet are discussing higher level concerns, thus suggest closing the issue ISSUE-128? ISSUE-128 -- Need more description on how bandwidth should be estimated -- open [http://www.w3.org/2009/dap/track/issues/128][33] fjh: once we have a detailed proposal we could raise new issues dom: maybe wait until we decide to move to Marcos proposal, if we do. If we do change to that proposal then this can be closed ### Testing fjh: any updates? 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][34] anssik: test suites have been updated fjh: if there are any significant changes please send a summary to the DAP list anssik: Pull request for HTML Media Capture test is waiting for review **ACTION:** anssik to send update on test status, pull requests on the DAP public list [recorded in [http://www.w3.org/2014/01/09-dap- minutes.html#action03][35]] Created ACTION-675 - Send update on test status, pull requests on the dap public list [on Anssi Kostiainen - due 2014-01-16]. fjh: it would be very helpful to summarize the status, what is missing, and which pull requests need review ### Roadmap planning fjh: good to understand what we are trying to do and when Review of plans for DAP WG and specifications on home page fjh: roadmap on home page: [http://www.w3.org/2009/dap/#roadmap][36] ... we have six specs not in TF: battery, html media capture, network information, light, proximity, vibration, network service discovery ... stable CR with test work: battery, html media capture, proximity ... revisions requiring LC/CR: light, vibration ... new - network information ... new - network service discovery anssik: battery implementation has work in chromium so this is helpful fjh: not sure of timing but perhaps we can move Battery to REC by summer? anssik, re battery in Chromium, could you add a ref in [http://www.w3.org/2009/dap/wiki/ImplementationStatus#Battery_Status_API][37] ? fjh: html media capture, proximity need test cases and implementation ... Note - Network Service Discovery overview (with Rich) for Privacy Interest Group (PING) scheduled at next PING teleconference, 30 January 2014 9 am PT/noon ET, see [http://lists.w3.org/Archives/Public/public- privacy/2013OctDec/0036.html][38] WebAppSec call to be scheduled for Network Service Discovery [http://www.w3.org/2011/webappsec/][39] Intent to Implement: Battery Status API in Chromium -> [https://groups.google.com/a/chromium.org/forum/#!topic/blink- dev/fzoG6Phr09k][40] fjh: for network service discovery PING call will be to give an overview, then we can expect privacy feedback subsequently ... expect we need to publish an updated WD of Network Service discovery once RIch is available, maybe end Jan//Feb ... network information has active discussion on list, new proposal from Marcos, please review and join in ... plan is to persistently work to drive this work forward, but we have limited control over implementations so cannot accurately predict a schedule dom: we need to think ahead about implementation reports and test reports and to get test results from implementations ... we also need to make sure we review implementation results to determine if problems are bugs in implementations or spec problems updated [http://www.w3.org/2009/dap/wiki/ImplementationStatus#Battery_Status_API][37] fjh: we don't have completed test cases for most, but for battery we do so we should focus on battery first to see have this right ### Issue Review fjh: trying to get focus and reduce number of open issues anssik: once we have implementations we can get more tests and feedback fjh: most issues are Network Service Discovery, will defer discussion ... Postponed issues are deferred until a subsequent v.next publication (e.g. after the upcoming REC) dom: "postponed" can mean whatever we want (since that's not a w3c process defined term) ... but I agree this is how I would interpret it fjh: yes, I want to be clear how i am using it - to defer to next release. please review postponed issues and note on list if any concern/disagreement: [http://www.w3.org/2009/dap/track/issues/postponed][41] fjh: most are contacts or messaging, so no longer relevant. A number of vibration issues however ### 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][34] 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][42] fjh: actions from today: ACTION-673? ACTION-673 -- Anssi Kostiainen to Update vibration spec with note related o issue-149 and update status section to list changes since last cr publication -- due 2014-01-16 -- OPEN [http://www.w3.org/2009/dap/track/actions/673][43] ACTION-674? ACTION-674 -- Frederick Hirsch to Open cfc for lc publication of vibration -- due 2014-01-16 -- OPEN [http://www.w3.org/2009/dap/track/actions/674][44] ACTION-675? ACTION-675 -- Anssi Kostiainen to Send update on test status, pull requests on the dap public list -- due 2014-01-16 -- OPEN [http://www.w3.org/2009/dap/track/actions/675][45] **ACTION:** fjh to contact W3C Comm team regarding sharing status of shelved documents without news item [recorded in [http://www.w3.org/2014/01/09 -dap-minutes.html#action04][46]] Created ACTION-676 - Contact w3c comm team regarding sharing status of shelved documents without news item [on Frederick Hirsch - due 2014-01-16]. Closed pending ACTIONS ACTION-671: Anssi Kostiainen to Prepare shelved note publications after tpac [http://lists.w3.org/Archives/Public/public-device-apis/2013Nov/0010.html][47] ACTION-672: Frederick Hirsch to Review status of vibration issues ### Other Business none ### Adjourn ## Summary of Action Items **[NEW]** **ACTION:** anssik to send update on test status, pull requests on the DAP public list [recorded in [http://www.w3.org/2014/01/09-dap- minutes.html#action03][35]] **[NEW]** **ACTION:** anssik to update Vibration spec with note related o ISSUE-149 and update status section to list changes since last CR publication [recorded in [http://www.w3.org/2014/01/09-dap-minutes.html#action01][29]] **[NEW]** **ACTION:** fjh to contact W3C Comm team regarding sharing status of shelved documents without news item [recorded in [http://www.w3.org/2014/01/09 -dap-minutes.html#action04][46]] **[NEW]** **ACTION:** fjh to open CfC for LC publication of Vibration [recorded in [http://www.w3.org/2014/01/09-dap-minutes.html#action02][30]] [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][48] version 1.135 ([CVS log][49]) $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/2014Jan/0011.html [4]: http://www.w3.org/2014/01/09-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]: #item11 [17]: #item12 [18]: #ActionSummary [19]: http://www.w3.org/2009/dap/minutes.html#upcoming-teleconferences [20]: http://lists.w3.org/Archives/Public/public-device- apis/2013Dec/att-0027/minutes-2013-12-12.html [21]: http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/0009.html [22]: http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/0005.html [23]: http://www.w3.org/2009/dap/track/issues/149 [24]: http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/0012.html [25]: http://lists.w3.org/Archives/Public/public-device- apis/2013Oct/0112.html [26]: http://dev.w3.org/cvsweb/2009/dap/vibration/Overview.src.html.diff?r1 =1.7;r2=1.8;f=h [27]: http://dev.w3.org/cvsweb/2009/dap/vibration/Overview.src.html [28]: http://dev.w3.org/cvsweb/2009/dap/vibration/Overview.src.html.diff?r1 =1.6;r2=1.7;f=h [29]: http://www.w3.org/2014/01/09-dap-minutes.html#action01 [30]: http://www.w3.org/2014/01/09-dap-minutes.html#action02 [31]: http://lists.w3.org/Archives/Public/public-device- apis/2013Apr/0043.html [32]: http://lists.w3.org/Archives/Public/public-device- apis/2014Jan/0013.html [33]: http://www.w3.org/2009/dap/track/issues/128 [34]: http://www.w3.org/2009/dap/track/actions/523 [35]: http://www.w3.org/2014/01/09-dap-minutes.html#action03 [36]: http://www.w3.org/2009/dap/#roadmap [37]: http://www.w3.org/2009/dap/wiki/ImplementationStatus#Battery_Status_API [38]: http://lists.w3.org/Archives/Public/public- privacy/2013OctDec/0036.html [39]: http://www.w3.org/2011/webappsec/ [40]: https://groups.google.com/a/chromium.org/forum/#!topic/blink- dev/fzoG6Phr09k [41]: http://www.w3.org/2009/dap/track/issues/postponed [42]: http://www.w3.org/2009/dap/track/actions/666 [43]: http://www.w3.org/2009/dap/track/actions/673 [44]: http://www.w3.org/2009/dap/track/actions/674 [45]: http://www.w3.org/2009/dap/track/actions/675 [46]: http://www.w3.org/2014/01/09-dap-minutes.html#action04 [47]: http://lists.w3.org/Archives/Public/public-device- apis/2013Nov/0010.html [48]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [49]: http://dev.w3.org/cvsweb/2002/scribe/