[![W3C][1]][2]

# Device and Sensors Working Group Teleconference

## 15 Dec 2016

[Agenda][3]

See also: [IRC log][4]

## Attendees

Present

    Frederick_Hirsch, Andrey_Logvinov, Tobie_Langel

Regrets

    Dominique_Hazael-Massieux, Anssi_Kostiainen

Chair

    Frederick_Hirsch

Scribe

    fjh

## Contents

  * [Topics][5]

    1. [Welcome, scribe selection, agenda review, announcements][6]

    2. [Minutes approval][7]

    3. [Generic Sensor API][8]

    4. [Concrete Sensors][9]

    5. [Wake Lock API][10]

    6. [Adjourn][11]

  * [Summary of Action Items][12]

  * [Summary of Resolutions][13]

* * *

<scribe> ScribeNick: fjh

### Welcome, scribe selection, agenda review, announcements

fjh: Publication Moratorium (old publication process) 16 Dec - 3 Jan;
[https://lists.w3.org/Archives/Public/public-device-
apis/2016Dec/0004.html][14]

### Minutes approval

Approve minutes from 1 December 2016

[https://lists.w3.org/Archives/Public/public-device-
apis/2016Dec/att-0000/minutes-2016-12-01.html][15]

**RESOLUTION: Minutes from 1 December 2016 are approved**

### Generic Sensor API

[https://w3c.github.io/sensors/][16]

[https://github.com/w3c/sensors/milestone/2][17]

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

### Concrete Sensors

tobie: not working on those right now, apart from light level sensor that
doesn't have these issues

### Wake Lock API

<Andrey_Logvinov> [https://github.com/w3c/wake-lock/pull/88][18]

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]][19]

<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!

### Adjourn

## Summary of Action Items

**[NEW]** **ACTION:** dom to review pull request for wake lock API [recorded
in [http://www.w3.org/2016/12/15-dap-minutes.html#action01][20]]


## Summary of Resolutions

  1. [Minutes from 1 December 2016 are approved][21]

[End of minutes]

* * *

Minutes formatted by David Booth's [scribe.perl][22] version 1.144 ([CVS
log][23])

$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/2016Dec/0005.html

   [4]: http://www.w3.org/2016/12/15-dap-irc

   [5]: #agenda

   [6]: #item01

   [7]: #item02

   [8]: #item03

   [9]: #item04

   [10]: #item05

   [11]: #item06

   [12]: #ActionSummary

   [13]: #ResolutionSummary

   [14]: https://lists.w3.org/Archives/Public/public-device-
apis/2016Dec/0004.html

   [15]: https://lists.w3.org/Archives/Public/public-device-
apis/2016Dec/att-0000/minutes-2016-12-01.html

   [16]: https://w3c.github.io/sensors/

   [17]: https://github.com/w3c/sensors/milestone/2

   [18]: https://github.com/w3c/wake-lock/pull/88

   [19]: http://www.w3.org/2016/12/15-dap-minutes.html#action01]

   [20]: http://www.w3.org/2016/12/15-dap-minutes.html#action01

   [21]: #resolution01

   [22]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm

   [23]: http://dev.w3.org/cvsweb/2002/scribe/