[minutes] Sep 7 teleconference

Hi,

The draft minutes of our call today are available at:
  https://www.w3.org/2017/09/07-dap-minutes.html

and copied as text below.

Dom


                    DAS Working Group teleconference

07 Sep 2017

   See also: [2]IRC log

      [2] http://www.w3.org/2017/09/07-dap-irc

Attendees

   Present
          Andrey_Logvinov, Fuqiao_Xue, Dominique_Hazael-Massieux,
          Anssi_Kostiainen, Alexander_Shalamov, Wanming_Lin,
          Kenneth_Christiansen

   Regrets
          Frederick_Hirsch

   Chair
          Dom

   Scribe
          anssik, xfq

Contents

     * [3]Topics
         1. [4]agenda review, announcements
         2. [5]Minutes approval
         3. [6]Sensor APIs
         4. [7]Wake Lock
         5. [8]Battery
         6. [9]Rechartering
     * [10]Summary of Action Items
     * [11]Summary of Resolutions
     __________________________________________________________

   <dom> ScribeNick: anssik

agenda review, announcements

   <scribe> New Staff Contact: Fuqiao Xue

   <xfq> hi

   xfq: recently joined W3C Staff
   ... you can find me from GH as xfq

   dom: introductions

   anssik: from Intel, editor of specifications in this group and
   elsewhere, chair of Second Screen WG & Web NFC CG

   kenneth: from Intel, editor of Web NFC, Web App Manifest, some
   sensor specs, working on Chrome and web standards

   mikhail: from Intel, editor of Generic Sensor API and concrete
   sensors, working on Chrome too

   shalamov: Alex from Intel, working on Web NFC and the Generic
   Sensor API, located in Finland with Mikhail and Anssi

   Andrey_Logvinov: from Yandex, editor of the Wake Lock API
   specification

   Wanming_Lin: from Intel, test facilitator in this group

   dom: need to discuss with Frederick if we can find a new time
   for the call, since key contributors are EU based
   ... announcement: HTML Media Capture published as revised CR

   [12]https://lists.w3.org/Archives/Public/public-device-apis/201
   7Aug/0018.html

     [12]
https://lists.w3.org/Archives/Public/public-device-apis/2017Aug/0018.html

   [13]https://www.irccloud.com/pastebin/uccigfMg/

     [13] https://www.irccloud.com/pastebin/uccigfMg/

Minutes approval

   PROPOSED RESOLUTION: Approve minutes from 29 June 2017

   [14]https://lists.w3.org/Archives/Public/public-device-apis/201
   7Jun/att-0017/minutes-2017-06-29.html

     [14]
https://lists.w3.org/Archives/Public/public-device-apis/2017Jun/att-0017/minutes-2017-06-29.html

   RESOLUTION: Approve minutes from 29 June 2017

   17: 10
   [15]https://lists.w3.org/Archives/Public/public-device-apis/201
   7Jun/att-0017/minutes-2017-06-29.html

     [15]
https://lists.w3.org/Archives/Public/public-device-apis/2017Jun/att-0017/minutes-2017-06-29.html

Sensor APIs

   dom: good activity over summer, publication on TR
   ... overview of the work and status, and roadmap to completion
   ... for Level 1, and wide review

   <dom> anssik: over the summer we have addressed all level 1
   issues that impact the implementation

   <dom> ... which requried normative changes ot the spec

   <dom> ... we have stabilized the implementation and have
   agreement to start origin trial in Chrome 62

   We intend to experiment with the Accelerometer,
   LinearAccelerationSensor, Gyroscope, AbsoluteOrientationSensor
   and RelativeOrientationSensor interfaces

   <dom> ... the list was chosen because these APIs don't expose
   new features

   <dom> ... they are replacement for DeviceMotion and
   DeviceOrientation

   <dom> ... for the first phase of the origin trial we want to
   get feedback from developers on the API shape and ergonomics

   <dom> ... based on tha tfeedback, we might adjust the API and
   expand the scope

   <dom> ... we're starting outreach on the API toward developers

   <dom> ... the origin trial will run over the course over 3
   major releases

   <dom> ... by EOY we should get a good amount of feedback from
   web developers

   <dom> ... I have 2 proposals: A - with the current spec, we
   could publish a CR soonish, and if the feedback from Web
   developers motivate change, we might need to revise it

   <dom> ... B - we wait until we get that feedback, and only then
   publish CR

   <dom> dom: either plan sound fine - main question is whether we
   want to signal we're done or not - I think we're kind in the
   middle

   <dom> ... to go to CR, we need to get our wide reviews done,
   and get our issues closed

   <xfq> scribenick: xfq

   dom: privacy and security issues

   <anssik> dom: if we go to CR, we need to ensure a) we have
   completed all wide reviews, and b) agree on scope i.e. Generic
   Sensor API only or Generic Sensor API + some set of concrete
   sensor specs

   <dom>
   [16]https://lists.w3.org/Archives/Public/public-device-apis/201
   7Aug/att-0017/das-review.pdf

     [16]
https://lists.w3.org/Archives/Public/public-device-apis/2017Aug/att-0017/das-review.pdf

   dom: we need to do wide reviews
   ... we did wide reviews for generic sensors and ambient light

   anssik: it's kind of better to review the sensor API specs as a
   set

   <anssik> anssik: prefer to do wide review for Generic Sensor
   API, Ambient Light Sensor, Accelerometer, Gyroscope,
   Magnetometer, Orientation Sensor together

   dom: I suggest we call the attention of the WebVR CG

   <inserted> ScribeNick: anssik

   dom: should reach out to WebVR CG too since the work is of
   interest to them

   [17]https://github.com/w3c/webvr/issues/249

     [17] https://github.com/w3c/webvr/issues/249

   [18]https://github.com/w3c/webvr/issues/250

     [18] https://github.com/w3c/webvr/issues/250

   dom: per the wide review process the chair to do the wide
   review requests to all horizontal groups

   <dom> ACTION: Dom to work with Frederick on getting a wide
   review question on sensor specs (- proximity), pointing out
   motion sensors explainer [recorded in
   [19]http://www.w3.org/2017/09/07-dap-minutes.html#action01]

     [19] http://www.w3.org/2017/09/07-dap-minutes.html#action01

   <trackbot> Created ACTION-805 - Work with frederick on getting
   a wide review question on sensor specs (- proximity), pointing
   out motion sensors explainer [on Dominique Hazaël-Massieux -
   due 2017-09-14].

   kenneth_: should include also the Motion Explainer in the
   review

   dom: how should we approach the WebVG CG

   <dom> ACTION: Anssi to get in touch with WebVR CG on wide
   review of motion sensor specs [recorded in
   [20]http://www.w3.org/2017/09/07-dap-minutes.html#action02]

     [20] http://www.w3.org/2017/09/07-dap-minutes.html#action02

   anssik: I can take an action on it

   <trackbot> Created ACTION-806 - Get in touch with webvr cg on
   wide review of motion sensor specs [on Anssi Kostiainen - due
   2017-09-14].

   dom: could transition to CR around October assuming wide review
   feedback is addressed

   <dom> [21]https://github.com/w3c/sensors/issues/155

     [21] https://github.com/w3c/sensors/issues/155

   <dom> [22]https://w3ctag.github.io/security-questionnaire/

     [22] https://w3ctag.github.io/security-questionnaire/

   [23]https://w3c.github.io/ambient-light/#security-and-privacy

     [23] https://w3c.github.io/ambient-light/#security-and-privacy

   [24]https://w3c.github.io/sensors/#mitigation-strategies

     [24] https://w3c.github.io/sensors/#mitigation-strategies

   dom: it might be that completing the questionnaire for Generic
   Sensor API will address most security and privacy concerns, but
   still need to double check the concrete specs adhere too

   <dom> ACTION-805: For TAG, create a bundle issue for all
   sensors preferably

   <trackbot> Notes added to ACTION-805 Work with frederick on
   getting a wide review question on sensor specs (- proximity),
   pointing out motion sensors explainer.

   <dom> ACTION: Alexander to run self-review questionnaire on
   sensor specs [recorded in
   [25]http://www.w3.org/2017/09/07-dap-minutes.html#action03]

     [25] http://www.w3.org/2017/09/07-dap-minutes.html#action03

   <trackbot> Created ACTION-807 - Run self-review questionnaire
   on sensor specs [on Alexander Shalamov - due 2017-09-14].

Wake Lock

   dom: started wide review for Wake Lock API
   ... if we don't get new blocking issues we advance to CR next
   month

   Andrey_Logvinov: spec in its current state not implemented
   anywhere

   dom: the spec is in good shape, so now ready for implementation

Battery

   [26]https://github.com/w3c/battery/pull/13

     [26] https://github.com/w3c/battery/pull/13

   anssik: PR #13 in review, after landed and implemented in
   Chrome, can publish revised CR

   <dom> dom: do we need another review from WebAppSec/PING before
   revising CR?

   <dom> anssik: not sure if that's needed/useful

   <dom> ACTION: Dom to look into the need to get wide review of
   revised battery [recorded in
   [27]http://www.w3.org/2017/09/07-dap-minutes.html#action04]

     [27] http://www.w3.org/2017/09/07-dap-minutes.html#action04

   <trackbot> Created ACTION-808 - Look into the need to get wide
   review of revised battery [on Dominique Hazaël-Massieux - due
   2017-09-14].

Rechartering

   dom: our charter expires EOY, we have work to complete beyond
   that date
   ... talked to Jeffrey asking if WebBT would like to migrate to
   WG
   ... Jeffrey prefers to stay in incubation until another
   implementer is interested

   <dom> [28]https://github.com/w3c/dap-charter/issues/29

     [28] https://github.com/w3c/dap-charter/issues/29

   <dom> [29]https://github.com/w3c/dap-charter/issues/30

     [29] https://github.com/w3c/dap-charter/issues/30

   dom: another issue, whether to bring WebNFC to this WG, the
   same for WebUSB
   ... also proposal to stop joint work on Media Capture TF
   ... this will minimize admin overhead
   ... adding more sensors to the DAS WG scope, in particular
   enviromental sensors
   ... also recast Geolocation API on top of Generic Sensor, and
   adopt old DeviceOrientation API maintenance

   <dom> [30]https://github.com/w3c/dap-charter/issues

     [30] https://github.com/w3c/dap-charter/issues

   dom: next call in two weeks

Summary of Action Items

   [NEW] ACTION: Alexander to run self-review questionnaire on
   sensor specs [recorded in
   [31]http://www.w3.org/2017/09/07-dap-minutes.html#action03]
   [NEW] ACTION: Anssi to get in touch with WebVR CG on wide
   review of motion sensor specs [recorded in
   [32]http://www.w3.org/2017/09/07-dap-minutes.html#action02]
   [NEW] ACTION: Dom to look into the need to get wide review of
   revised battery [recorded in
   [33]http://www.w3.org/2017/09/07-dap-minutes.html#action04]
   [NEW] ACTION: Dom to work with Frederick on getting a wide
   review question on sensor specs (- proximity), pointing out
   motion sensors explainer [recorded in
   [34]http://www.w3.org/2017/09/07-dap-minutes.html#action01]

     [31] http://www.w3.org/2017/09/07-dap-minutes.html#action03
     [32] http://www.w3.org/2017/09/07-dap-minutes.html#action02
     [33] http://www.w3.org/2017/09/07-dap-minutes.html#action04
     [34] http://www.w3.org/2017/09/07-dap-minutes.html#action01

Summary of Resolutions

    1. [35]Approve minutes from 29 June 2017

   [End of minutes]

Received on Thursday, 7 September 2017 15:06:51 UTC