W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2017

Device and Sensors WG bi-weekly status

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Wed, 15 Nov 2017 11:27:17 +0000
To: W3C Devices and Sensors WG <public-device-apis@w3.org>
Message-ID: <7CB510D3-52DE-4C79-8FF7-E6F2EAF5C836@intel.com>
Hi,

[I will send this type of bi-weekly status in place of a teleconference as needed.]


---+ Weekly GitHub digests

No huge activity over the last two weeks thanks to the v1 specs being feature completed and shipping and TPAC last week:

https://lists.w3.org/Archives/Public/public-device-apis/2017Nov/0002.html
https://lists.w3.org/Archives/Public/public-device-apis/2017Oct/0032.html


---+ Generic Sensors shipping in Chrome as an Origin Trial

The v1 specifications are implemented in Chrome 63. You can experiment with the APIs either by enabling the following flag(s):

To enable motion sensors:
chrome://flags/#enable-generic-sensor 

To enable environmental sensors:
chrome://flags/#enable-generic-sensor-extra-classes

To enable motion sensors on your site for *all* Chrome 63+ users regardless of whether they've flipped the flag or not, get your free token at:

http://bit.ly/OriginTrialSignup

And see the developer documentation for help on how to bind the token with your origin:

https://developers.google.com/web/updates/2017/09/sensors-for-the-web


---+ TPAC Device APIs breakout

TPAC was last week, and we had a Device APIs breakout session there.

Agenda:
https://www.w3.org/wiki/TPAC/2017/SessionIdeas#Device_APIs_session

Minutes:
https://www.w3.org/2017/11/08-device-api-minutes.html

We spent most of the time discussing whether Web Bluetooth should advance to standards track and be adopted by this WG. The sentiment seemed to be the API should stay in its Community Group for the time being. Further feedback on the topic welcome in the respective issue:

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

(Please note the present list in minutes is not complete, we had ~30 people in the room, including representatives from Google, Microsoft, Apple, Mozilla, Intel, others.)


---+ Generic Sensors wide review

* Privacy

Alex attended Privacy Interest Group (PING) call on 2 Nov and I attended PING TPAC F2F on 9 Nov. PING is generally happy with the specs and will submit some editorial suggestions to acknowledge their review has been completed.

PING TPAC F2F Generic Sensors minutes:
https://www.w3.org/2017/11/09-privacy-minutes.html#item05

Wide review tracker:
https://github.com/w3c/sensors/issues/299

* i18n

Also i18n folks got in touch with us, and we informed them these specifications do not have i18n implications, and as such the group is not seeking explicit i18n review.

https://lists.w3.org/Archives/Public/public-device-apis/2017Oct/0033.html


---+ Rechartering

We expect to submit the Device and Sensors Charter for AC review around mid-Dec. Please review the draft charter and let us know if you have any comments or concerns. Pay attention to the open issues.

Draft charter:
https://w3c.github.io/dap-charter/DeviceAPICharter.html

Open issues:
https://github.com/w3c/dap-charter/issues


---+ HTML Media Capture PR

CfC passed and we'll publish a Proposed Recommendation of HTML Media Capture at earliest opportunity, but no earlier than 16 Nov.

CfC: transition HTML Media Capture to Proposed Recommendation:
https://lists.w3.org/Archives/Public/public-device-apis/2017Oct/0028.html

Staged PR snapshot:
https://rawgit.com/w3c/html-media-capture/pr/index.html


Thanks,

-Anssi (Device and Sensors WG Chair)
Received on Wednesday, 15 November 2017 11:27:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 15 November 2017 11:27:43 UTC