See also: IRC log
<scribe> ScribeNick: fjh
fjh: Publication Moratorium (old publication process) 16 Dec - 3 Jan; https://lists.w3.org/Archives/Public/public-device-apis/2016Dec/0004.html
Approve minutes from 1 December 2016
https://lists.w3.org/Archives/Public/public-device-apis/2016Dec/att-0000/minutes-2016-12-01.html
RESOLUTION: Minutes from 1 December 2016 are approved
https://w3c.github.io/sensors/
https://github.com/w3c/sensors/milestone/2
tobie: issues require thought; implementation feedback is impacting design
... on sensor versus on events
... new issue regarding garbage collection requires major changes, will update spec to drop sensor reading interface, have readings reflected directly on main sensor interface
... big issue
... better to know this now than later, despite delay
... another issue - motion sensors, requirements for doing work, need really good performance, high sampling rate and regular
... need quality data
... on windows devices motion sensors don't provide data on every poll, only changes if delta in OS is big enough
... also these sensors may not be very accurate, not so good sensors
... so get not so good data not very often
fjh: question whether API should be designed around platform that is not suitable?
tobie: implementers ask that frequency be a hint, not a requirement
... if platform does not support use cases, does it make sense that API can be implemented on that platform
fjh: that is my question
... depends on broader ecosystem, what trends are etc
tobie: sensors on non-mobile devices are less common
fjh: what about Internet of Things
tobie: need better understanding of how applications will use these sensors on the web; better understanding of gaming
... performance tests first to see if hardware meets requirements
... then adjust for platform capabilities
... may need to do something similar for sensors when performance matters
... hence can maybe go with making frequency a hint
fjh: lets revisit on 12 Jan
tobie: looking for feedback
fjh: webrtc had issue of knowing capabilities as well, so common issue
tobie: have to run tests regardless, even if know about hardware
tobie: not working on those right now, apart from light level sensor that doesn't have these issues
<Andrey_Logvinov> https://github.com/w3c/wake-lock/pull/88
andrey: have new version that should resolve most of the issues
... have review?
<scribe> ACTION: dom to review pull request for wake lock API [recorded in http://www.w3.org/2016/12/15-dap-minutes.html#action01]
<trackbot> Created ACTION-782 - Review pull request for wake lock api [on Dominique Hazaël-Massieux - due 2016-12-22].
dom, are you ok with reviewing the Wake Lock pull request? Assuming yes, gave you action
<dom> will try, thx
thank you dom, thanks Andrey
fjh: will revisit on our next call, 12 Jan, merge before if ok
... Next call is 12 Jan
... Merry Christmas, happy holidays and Happy New Year to all!