[![W3C][1]][2] # Device APIs Working Group Teleconference ## 21 Jan 2016 [Agenda][3] See also: [IRC log][4] ## Attendees Present Frederick_Hirsch, Tobie_Langel, Andrey_Logvinov, Dominique_Hazael-Massieux Regrets Chair Frederick_Hirsch Scribe fjh ## Contents * [Topics][5] 1. [Generic Sensor API][6] 2. [Wake Lock][7] 3. [Battery][8] 4. [Minutes][9] 5. [Other Business][10] 6. [Adjourn][11] * [Summary of Action Items][12] * [Summary of Resolutions][13] * * * ### Generic Sensor API scribeNick: fjh tobie: working on ambient light spec, plan to have something tomorrow ... pull request for ambient light sensor ... also cleaning up generic sensor API ... had conversation with Chromium implementer about it ... looking into Android and IOS, what is exposed to implementations, need to simplfiy some things as a result ... remove what cannot expose properly ... removing everything that is 'nice to have' ... still have questions around sensors that send data on change versus those where pulling data ... not because of hw implementations, but due to how exposed to browser, SDK etc ... have opened issues on these topics, will open some more ... will have up to date WD once ongoing updates are set up by Dom ... question of when to release new version of ambient light ... first get feedback on documents, then consider publishing new WD fjh: are there multiple issues in the event based versus polling tobie: will write up more about it, then discuss ### Wake Lock fjh: not enough implementations dom: only have one implementation ... but only 1 year old, so not too bad fjh: right ... no need for special draft, like LC [http://lists.w3.org/Archives/Public/public-review-announce/][14] dom: announce to chairs list, public review announce list, update SOTD first ... need to figure which groups to ask specially, web platform, web app sec fjh: privacy group dom: Andrey what do you think of starting wide review andrey: review would be good [https://github.com/w3c/wake-lock/issues][15] dom: what is the plan for the open issues on wakelock? andrey: need to review them dom: yes, please ... many are probably out of date fjh: andrey when might you be able to complete this andrey: in a week ### Battery fjh: there has been progress on this dom: waiting for updated implementation report from Zhiqiang, should get report in a few days ... close to requesting PR for that one ... need implementation report and detailed summary, then send transition request fjh: do we need a call dom: not sure, otherwise wait until March ### Minutes **RESOLUTION: Minutes from 7 Jan 2016 are approved, [https://lists.w3.org/Archives/Public/public-device- apis/2016Jan/att-0011/minutes-2016-01-07.html][16]** ### Other Business none ### Adjourn ## Summary of Action Items ## Summary of Resolutions 1. [Minutes from 7 Jan 2016 are approved, https://lists.w3.org/Archives/Public/public-device- apis/2016Jan/att-0011/minutes-2016-01-07.html][17] [End of minutes] * * * Minutes formatted by David Booth's [scribe.perl][18] version 1.144 ([CVS log][19]) $Date: 2015/11/17 08:39:34 $ [1]: https://www.w3.org/Icons/w3c_home [2]: http://www.w3.org/ [3]: https://lists.w3.org/Archives/Public/public-device- apis/2016Jan/0048.html [4]: http://www.w3.org/2016/01/21-dap-irc [5]: #agenda [6]: #item01 [7]: #item02 [8]: #item03 [9]: #item04 [10]: #item05 [11]: #item06 [12]: #ActionSummary [13]: #ResolutionSummary [14]: http://lists.w3.org/Archives/Public/public-review-announce/ [15]: https://github.com/w3c/wake-lock/issues [16]: https://lists.w3.org/Archives/Public/public-device- apis/2016Jan/att-0011/minutes-2016-01-07.html [17]: #resolution01 [18]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [19]: http://dev.w3.org/cvsweb/2002/scribe/