14:02:35 RRSAgent has joined #dap 14:02:35 logging to https://www.w3.org/2018/01/11-dap-irc 14:02:39 Present+ Wanming_Lin 14:02:50 RRSAgent, make log public 14:04:36 xfq_ has joined #dap 14:04:44 Present+ Anssi_Kostiainen 14:04:48 present+ Fuqiao_Xue 14:04:59 RRSAgent, make minutes 14:04:59 I have made the request to generate https://www.w3.org/2018/01/11-dap-minutes.html xfq_ 14:04:59 Present+ Alexander_Shalamov 14:05:18 Present+ Mikhail_Podnyakov 14:05:47 ScribeNick: xfq 14:05:51 ScribeNick: xfq_ 14:06:00 Meeting: DAS Working Group teleconference 14:06:13 Chair: Anssi_Kostiainen 14:06:35 agenda: https://lists.w3.org/Archives/Public/public-device-apis/2018Jan/0002.html 14:06:41 RRSAgent, make minutes 14:06:41 I have made the request to generate https://www.w3.org/2018/01/11-dap-minutes.html xfq_ 14:07:10 Topic: Welcome, agenda review, announcements 14:07:47 anssik: Last time we met was before TPAC 14:07:59 ... the wide review period ended at the end of last year 14:08:17 ... let's plan on the following actions 14:08:42 ... we have informal feedback from TAG, Security IG, and PING 14:09:26 ... we can look at usage stats of Battery Status API 14:09:36 ... also recharting of DAS 14:09:43 ... any other agenda items? 14:10:16 ... Generic Sensor API Level 2 feature cherry picking 14:10:36 Topic: Sensor APIs wide review 14:10:56 https://github.com/w3c/sensors/issues/299 14:11:17 anssik: We have this meta-issue (see link on IRC) 14:11:33 https://github.com/w3ctag/design-reviews/issues/207 14:11:43 ... all horizontal groups except i18n and a11y groups were asked for feedback 14:12:01 ... let's go through them one-by-one 14:12:42 ... in the TAG review, I'm happy that Mozilla is looking into the new sensor APIs 14:13:56 ... I think all feedback in the issue can be addressed as clarifications in specs 14:13:59 ... there's no real blockers 14:16:00 https://cryptpad.w3ctag.org/code/#/1/view/wWjGyJj9JsQEXugZaB9juA/sLQghIPquNLW5dOftFYcttHFvcZFlNCYWbYa14Trgn8/ 14:16:31 Alexander: we don't have formal response from TAG yet 14:16:39 https://github.com/w3ctag/design-reviews/issues/207#issuecomment-351557619 14:17:39 anssik: Tom Ritter is a security researcher from Mozilla, and I'm happy we can have his feedback. 14:17:42 https://github.com/w3c/accelerometer/issues/30 14:17:48 https://github.com/w3c/gyroscope/issues/27 14:18:23 ... see links on IRC for PING's feedback for Accelerometer and Gyroscope 14:19:33 ... we decided to skip i18n/a11y wide review because it's mostly out-of-scope 14:20:37 ... see other groups' feedback in the issue 14:20:42 RRSAgent, make minutes 14:20:42 I have made the request to generate https://www.w3.org/2018/01/11-dap-minutes.html xfq_ 14:20:48 Topic: Generic Sensor API Level 2 feature cherry picking 14:21:44 anssik: The Generic Sensor API is considered feature complete, and implemented in Chrome 14:22:22 https://github.com/w3c/sensors/issues/257 14:22:22 ... the Generic Sensor API is a dependency of the WebVR API on Chrome, in some devices 14:22:54 ... I'll let Alexander briefly summrize the issue linked above. 14:24:22 Alexander: sometimes the window manager @@ X / Y 14:24:24 ... @@ from one coordinate system to another coordinate system 14:24:36 ... @@ developer can use this API instead of do it manually 14:25:44 anssik: @@4 14:25:47 In order to make it happen developers have to use the Screen Orientation API to do this manually 14:26:00 s/In order to make it happen developers have to use the Screen Orientation API to do this manually/... In order to make it happen developers have to use the Screen Orientation API to do this manually/ 14:27:12 PROPOSED SOLUTION: #257 will be made level 1 14:27:25 s/SOLUTION/RESOLUTION/ 14:27:53 https://github.com/w3c/sensors/issues/63 14:29:12 anssik: the way to change frequency setable 14:29:12 ... one use case is to save resources of the UIs 14:29:22 ... there are other use cases as well 14:30:12 ... I propose we cherry-pick it into level 1 to get it in CR 14:30:45 PROPOSED RESOLUTION: #63 will be added to level 1 14:31:42 https://github.com/w3c/sensors/projects/5 14:31:49 anssik: we still need more use cases, and think more about security/privicy considerations 14:32:33 ... see all level 2 issues in the link above 14:33:00 Topic: Battery Status API privacy enhancements 14:33:35 https://github.com/w3c/battery/pull/13#issuecomment-356590244 14:34:47 anssik: a couple of months ago, we looked at cross-origin usage and insecure origin usage of the Battery Status API 14:34:48 ... they are 1.1% and 0.7% respectively 14:36:39 ... as Mounir said in that issue, security/privacy restrictions will block much usage of the API 14:36:43 ... please take a look at the issue 14:38:32 http://w3c.github.io/dap-charter/DeviceAPICharter.html 14:38:37 ... let us know in this PR if you have a good proposal 14:38:49 s/in that issue/in that PR/ 14:38:56 Topic: Rechartering 14:39:03 https://github.com/w3c/dap-charter/ 14:39:28 https://wicg.github.io/geolocation-sensor/ 14:39:31 anssik: If you have feedback for the draft charter, please go to the GitHub repo and file a new issue 14:39:53 https://w3c.github.io/deviceorientation/spec-source-orientation.html 14:40:39 ... we added Geolocation Sensor 14:40:42 ... we also added DeviceOrientation Event specification, because the Geolocation WG was closed 14:41:34 ... we'll get the Wake Lock API impl aligned 14:41:36 ... Thanks everyone! 14:41:43 rrsagent, draft minutes v2 14:41:43 I have made the request to generate https://www.w3.org/2018/01/11-dap-minutes.html anssik 14:44:23 wanming has left #dap 14:49:58 xfq has joined #dap 14:50:46 Present+ Andrey_Logvinov 14:50:48 rrsagent, draft minutes v2 14:50:48 I have made the request to generate https://www.w3.org/2018/01/11-dap-minutes.html xfq