13:58:41 RRSAgent has joined #dap 13:58:41 logging to http://www.w3.org/2017/09/21-dap-irc 13:58:43 RRSAgent, make logs world 13:58:43 Zakim has joined #dap 13:58:45 Meeting: Device and Sensors Working Group Teleconference 13:58:45 Date: 21 September 2017 14:02:08 fjh has joined #dap 14:02:17 Present+ Anssi_Kostiainen 14:02:18 anssik has joined #dap 14:02:32 Present+ Mikhail_Pozdnyakov 14:02:42 trackbot, start telecon 14:02:45 RRSAgent, make logs world 14:02:48 Meeting: Device and Sensors Working Group Teleconference 14:02:48 Date: 21 September 2017 14:02:51 Present+ Dominique_Hazael-Massieux 14:02:52 Present+ Alexander_Shalamov 14:03:03 rrsagent, generate minutes 14:03:03 I have made the request to generate http://www.w3.org/2017/09/21-dap-minutes.html fjh 14:03:45 Agenda: https://lists.w3.org/Archives/Public/public-device-apis/2017Sep/0003.html 14:03:51 fjh has changed the topic to: das https://lists.w3.org/Archives/Public/public-device-apis/2017Sep/0003.html 14:04:03 Chair: Frederick_Hirsch 14:04:12 Present+ Frederick_Hirsch 14:05:02 rrsagent, generate minutes 14:05:02 I have made the request to generate http://www.w3.org/2017/09/21-dap-minutes.html fjh 14:05:43 Present+ Wanming_Lin 14:06:32 Agenda: https://lists.w3.org/Archives/Public/public-device-apis/2017Sep/0020.html 14:07:00 Topic: Welcome, scribe selection, agenda review, announcements 14:07:06 ScribeNick: anssik 14:07:09 GitHub digests 14:07:09 https://lists.w3.org/Archives/Public/public-device-apis/2017Sep/0016.html 14:07:10 https://lists.w3.org/Archives/Public/public-device-apis/2017Sep/0019.html 14:07:11 review request, Vehicle Information Service Specification, Vehicle Information API Specification 14:07:12 https://lists.w3.org/Archives/Public/public-device-apis/2017Sep/0018.html 14:07:20 TOPIC: Welcome, scribe selection, agenda review, announcements 14:07:23 q+ 14:07:44 fjh: there was a review request for Vehicle Information Service Specification, Vehicle Information API Specification 14:08:02 dom: Web Auto WG is bringing these specs to CR soon 14:08:36 ... two work items, i) API which is a wrapped for the ii) protocol 14:10:01 ... would be interesting for someone with Generic Sensor expertise to review the Web Auto WG specs, but not spend excess time on it 14:11:01 anssik: early thought from Tobie was that they could use Generic Sensor approach 14:11:20 dom: TAG suggested alternate approach to use protocol; wrapper can be an issue 14:11:27 s/wrapper/API wrapper/ 14:11:30 Present+ Fuqiao_Xue 14:11:36 ... TAG review feedback caused Web Auto WG to reorientate their work, started working on a protocol-level spec 14:12:01 anssik: any implementations available for these specs? 14:12:09 dom: only experimental, but no clear on details 14:16:40 alexander: we'd like to review 14:17:09 action: alexander to review Automotive specifications with regards to Generic Sensor API 14:17:10 Created ACTION-809 - Review automotive specifications with regards to generic sensor api [on Alexander Shalamov - due 2017-09-28]. 14:17:11 ... they may have some requirements that might motivate new features in Generic Sensor v.next 14:17:32 s/... they/anssik: they/ 14:17:35 dom: we should be able to learn from this 14:17:50 TOPIC: Minutes approval 14:17:56 Approve minutes from 7 Sept 2017 14:17:56 https://www.w3.org/2017/09/07-dap-minutes.html 14:17:57 proposed RESOLUTION: Minutes from 7 Sept 2017 are approved 14:18:07 RESOLUTION: Minutes from 7 Sept 2017 are approved 14:18:18 TOPIC: Media Capture Task Force 14:18:26 Call for Consensus: discontinue joint ownership of Media Capture Task Force, leaving to WebRTC Working Group; respond by 20 Sept 2017 14:18:26 https://lists.w3.org/Archives/Public/public-device-apis/2017Sep/0017.html 14:18:28 Call for Consensus: discontinue joint ownership of Media Capture Task Force, leaving to WebRTC Working Group; respond by 20 Sept 2017 14:18:44 fjh: no concerns raised to separate the two 14:18:54 dom: that's my interpretation too 14:19:19 action: fjh to send email confirming CfC conclusion 14:19:20 Created ACTION-810 - Send email confirming cfc conclusion [on Frederick Hirsch - due 2017-09-28]. 14:19:35 TOPIC: TPAC 2017 14:19:38 1 hour Wed Session? Vincent to chair? 14:19:39 https://www.w3.org/wiki/TPAC/2017/SessionIdeas#Device 14:19:39 https://lists.w3.org/Archives/Public/public-device-apis/2017Sep/0014.html 14:22:40 fjh: breakout will be pretty ad-hoc 14:23:36 TOPIC: Sensor APIs 14:23:43 2 proposals: 14:23:43 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 14:23:44 B - we wait until we get that feedback, and only then publish CR 14:23:53 fjh: two CR publication plans 14:24:42 no decision yet on A or B 14:24:52 wide review for Generic Sensor API, Ambient Light Sensor, Accelerometer, Gyroscope, Magnetometer, Orientation Sensor together 14:25:02 ACTION-805? 14:25:02 ACTION-805 -- Dominique Hazaël-Massieux to Work with frederick on getting a wide review question on sensor specs (- proximity), pointing out motion sensors explainer -- due 2017-09-14 -- OPEN 14:25:02 http://www.w3.org/2009/dap/track/actions/805 14:25:09 dom: need to do wide review prior to thinking of CR publication 14:25:57 https://github.com/w3c/sensors/blob/master/security-questionnaire.md 14:26:07 security and privacy questionnaire results 14:26:49 alexander: I agree with dom, we should split those to separate repos 14:27:21 ... can do that tomorrow 14:27:35 dom: will work with fjh on wide review logistics 14:28:26 dom: will work with fjh next week, after split complete 14:28:58 fjh: why not include proximity in the wide review? 14:29:22 dom: too many documents in review, will probably mean less focus on specs that are further down the process 14:29:36 https://www.w3.org/2009/dap/#roadmap 14:30:40 fjh: who'd be the usual suspects to review this work 14:30:56 dom: we discussed this on last call, so we have a list of groups to target 14:31:25 ACTION-806? 14:31:25 ACTION-806 -- Anssi Kostiainen to Get in touch with webvr cg on wide review of motion sensor specs -- due 2017-09-14 -- OPEN 14:31:25 http://www.w3.org/2009/dap/track/actions/806 14:31:59 anssik: please include explainer in the review, good background 14:32:58 https://intel.github.io/generic-sensor-demos/vr-button/build/bundled/ 14:33:07 https://github.com/intel/generic-sensor-demos/tree/master/vr-button/build/bundled 14:34:04 anssik: also WebVR polyfill could benefit from the low-level sensors 14:34:20 community group, anssik will send informal request 14:34:27 ... one concrete use case would be to enable magnetic input in WebVR using Magnetometer 14:36:01 fjh: we're ready for wide review 14:36:12 ... status of the open issues? 14:36:33 ... after wide review completed, go to CR, how to deal with open issues 14:36:44 ... assess where we are in terms of open issues 14:37:06 ... going to wide review equals last call in the old process 14:37:55 Topic: Wake Lock 14:37:56 Plan: wide review before transition to CR, deadline 30 Sept, then CR 14:37:56 https://lists.w3.org/Archives/Member/chairs/2017JulSep/0104.html 14:38:12 wait until review period ends then progress 14:38:20 Topic: Battery 14:38:35 status? PR #13 in review, after landed and implemented in Chrome, can publish revised CR 14:38:41 fjh: current status? 14:38:50 ACTION-808? 14:38:50 ACTION-808 -- Dominique Hazaël-Massieux to Look into the need to get wide review of revised battery -- due 2017-09-14 -- OPEN 14:38:50 http://www.w3.org/2009/dap/track/actions/808 14:39:41 mounir looking to see how often cross iframe battery cases are used 14:39:47 others are ok with it 14:40:02 s/mounir/anssik: mounir/ 14:40:03 That is, in an A->B->A embedding scenario, both the top-level and the innermost frame would be able to use the battery API. With feature policy, the inner frame wouldn't be allowed to use it, unless the top-level doc granted it to the middle frame, which then further granted it to the inner one. 14:40:10 s/others/anssik: others/ 14:40:43 anssik: have integrated spec with feature poicy 14:40:55 s/poicy/policy 14:41:05 anssik: will wait a week or two for feedback, then merge 14:41:22 anssik: then go to CR and await additional browser implementations 14:41:45 ScribeNick: fjh 14:42:08 -> https://www.chromestatus.com/feature/5694225681219584 Feature Policy status in Chrome platform status - indicates public support from Edge 14:42:17 go to CR end Oct 14:42:33 -> https://github.com/WICG/feature-policy/issues/62 Microsoft stance on the spec 14:44:26 TOPIC: Rechartering 14:44:42 ScribeNick: anssik 14:44:43 https://github.com/w3c/dap-charter/ 14:44:50 http://w3c.github.io/dap-charter/DeviceAPICharter.html 14:45:11 https://github.com/w3c/dap-charter/issues 14:45:25 3, 30, 29 issues of scope are substantive 14:45:38 dom: substantial issue: 1) scope, whether to integrate WebNFC, WebUSB, environmental sensors 14:45:45 dom suggests answer should be no 14:47:23 anssi: NFC is higher level api than last time 14:47:48 dom: I asked Vincent about his breakout session at TPAC, and whether that would have impact on the rechartering i.e. whether to do more work in DAS or not 14:48:03 action: fjh to review charter 14:48:03 Created ACTION-811 - Review charter [on Frederick Hirsch - due 2017-09-28]. 14:48:15 ... apart from that the charter is ready for W3M review 14:48:31 ... heads up, if there are issues that need further discussion, good time to raise now 14:48:54 fjh: I'm looking track whether W3C wants megagroups or smaller focused 14:49:06 dom: there's no policy on that 14:49:24 fjh: how does the chair selection work 14:49:39 dom: in general, charters are reviewed with expected chair 14:50:22 ... plan, work next week on admin tasks, early October bring to W3M 14:51:42 https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2F2016%2F03%2Fdevice-sensors-wg-charter.html&doc2=http%3A%2F%2Fw3c.github.io%2Fdap-charter%2FDeviceAPICharter.html 14:54:39 TOPIC: HTML Media Capture 14:54:48 -> https://www.w3.org/TR/html-media-capture/ HTML Media Capture "This Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than 30 October 2017. " 14:58:17 sorry, the line is very noise, I can't hear clearly. 15:00:19 we discussed moving the call an hour earlier, any concern? 15:00:36 +1 15:00:49 no, it's great 15:01:06 RESOLUTION: move DAS call 1 hour earlier, e.g. 9am ET, on same schedule 15:01:19 Topic: Other Business 15:01:22 none 15:01:27 Topic: Adjourn 15:01:49 rrsagent, generate minuites 15:01:49 I'm logging. I don't understand 'generate minuites', fjh. Try /msg RRSAgent help 15:01:57 rrsagent, generate minutes 15:01:57 I have made the request to generate http://www.w3.org/2017/09/21-dap-minutes.html fjh 15:49:06 fjh has left #dap 15:51:27 zkis has joined #dap 16:17:54 Zakim has left #dap