13:53:17 RRSAgent has joined #dap 13:53:17 logging to http://www.w3.org/2017/06/15-dap-irc 13:53:19 RRSAgent, make logs world 13:53:19 Zakim has joined #dap 13:53:21 Zakim, this will be DAP 13:53:21 ok, trackbot 13:53:22 Meeting: Device and Sensors Working Group Teleconference 13:53:22 Date: 15 June 2017 13:53:45 Agenda: https://lists.w3.org/Archives/Public/public-device-apis/2017Jun/0002.html 13:53:47 Chair: Dom 13:53:54 Regrets: Frederick 13:59:23 kenneth_ has joined #dap 14:00:01 +Present KennethRohdeChristiansen 14:00:30 shalamov has joined #dap 14:02:24 anssik has joined #dap 14:02:43 TOPIC: Minutes approval 14:02:46 ScribeNick: anssik 14:02:58 Proposed RESOLUTION: Minutes from 18 May 2017 are approved https://lists.w3.org/Archives/Public/public-device-apis/2017May/att-0024/minutes-2017-05-18.html 14:02:58 proposed RESOLUTION: Minutes from 18 May 2017 are approved 14:03:12 RESOLUTION: Minutes from 18 May 2017 are approved 14:03:32 TOPIC: HTML Media Capture 14:03:48 dom: checking if we can go to PR next month 14:03:51 ... is that correct? 14:04:09 http://w3c.github.io/test-results/html-media-capture/20170428.html 14:04:11 -> http://w3c.github.io/test-results/html-media-capture/20170428.html HTML Media Capture Test Results 14:04:16 Present+ Alexander_Shalamov 14:05:05 dom: the 1 failing test case could be not applicable as well 14:05:19 ... have to wait for couple of weeks before entering PR 14:05:34 TOPIC: Sensors API 14:05:45 dom: what is our vision to bring the work to CR? 14:05:54 ... what needs to be update re wide reviews 14:06:20 anssik: we want to get closure on open pull requests 14:06:25 ... then we should triage open issues 14:06:43 ... I would like to have level 1 issues marking what we want to get in our CR 14:06:50 ... the rest would be for later versions 14:06:59 ... goal is to go to CR this year 14:07:28 ... [this is for generic sensor, but we would also want to go to CR with some of the most-baked concrete sensors] 14:08:05 dom: what's your feeling on the actual timeline? 14:08:10 Present+ Wanming_Lin 14:08:19 Andrey_Logvinov has joined #dap 14:08:32 anssik: timeline will depend on editorship situation 14:09:11 ... assuming dedicated full time editorship, this would need addressing level 1 issues (~30) 14:09:29 kenneth: there is also the F2F to take into account in the picture 14:09:39 ... it helps with getting a broad overview of the status 14:10:04 alex: closing issues can be fast, but some of them have dependencies to other groups / specs 14:10:43 anssik: plan is to have outside TPAC F2F; but we can still have an unofficial session at TPAC 14:10:54 kenneth: but for coordination, TPAC remains nice even if DAS is not meeting formally 14:12:24 anssik: chrome origin trial starting in the near future 14:12:33 ... we would want to include that feedback in the spec prior to CR 14:13:09 ... CR this year is optimistic - but that should be our target 14:13:19 ... which means we should have a CR-worthy spec by the time of TPAC 14:13:55 mikhail: it would be nice to align spec / implementation prior to origin trial 14:14:22 dom: the chair is looking at the editorship issue 14:14:30 ... after that we can get clarify on the timeline 14:17:09 ACTION: Alexander to take a stab a level-1 issue classification 14:17:10 Created ACTION-800 - Take a stab a level-1 issue classification [on Alexander Shalamov - due 2017-06-22]. 14:18:35 TOPIC: Wake lock 14:18:51 [the editor not on the call] 14:19:00 dom: new activity, suggestions from Microsoft 14:19:07 ... hoping to be able to take this to CR 14:19:11 TOPIC: Battery Status API 14:19:24 dom: two things: new activity on issue #10 14:19:43 ... and secondly, revised CR plan 14:20:01 https://github.com/w3c/battery/issues/10 14:20:05 anssi: mounir noticed the security change in issue 10 14:20:18 https://github.com/w3c/battery/issues/5#issuecomment-257554180 14:24:05 sounds like another case where we might want to rely on https://wicg.github.io/feature-policy/ too 14:24:09 dom: perhaps iframed content that shares the origin with the top-level should not be restricted 14:25:39 " The Battery API can be used by third party content for valid reasons." https://github.com/w3c/battery/issues/10#issuecomment-308107841 14:26:39 dom: do we want to reopen issue #10? 14:26:47 ... or do research first? 14:26:59 anssik: maybe reopening is the right thing to do 14:27:46 anssik: just reopened https://github.com/w3c/battery/issues/10 14:28:04 dom: should be feedback from people who chimed in on issue #5 14:32:09 dom: also, worth noting that mounir is pointing at real-world usage of the battery api for a/b testing - probably worth highlighting to get interest from more implementors 14:32:32 TOPIC: Rechartering 14:33:02 dom: current charter expiring by the end of this year, assume we want to continue beyond this year to finish the current work and possibly adopt new work 14:33:27 possible candidates for inclusion in this group: 14:33:30 https://www.w3.org/TR/orientation-event/ 14:33:30 * taking over device orientation v1? 14:33:30 * geo v2? 14:33:30 * webbluetooth? 14:33:30 * webusb? 14:33:30 * webnfc? 14:33:58 dom: Geolocation WG closed, had Geolocation API and Device Orientation API in scope 14:34:21 ... Device Orientation API was not finished, suggestion for DAS to take the spec to REC 14:34:54 ... also Geolocation API "v2" a possibility, e.g. background operation 14:35:16 ... WebBT, WebNFC, WebUSB also would be natural extensions to the DAS group 14:36:17 anssi: DAS WG is probably the best fit for all of these work items in terms of scope 14:36:30 ... Device Orientation would benefit from the sensor expertise of this group 14:36:39 ... geo could remodeled after generic sensor 14:37:02 ... the 3 incubation specs (bluetooth, nfc, usb) would benefit from more common interactions 14:37:14 ... incl in F2F and/or calls 14:37:29 ... they share a lot in common (e.g. permission model, API shape) - we could learn from each other 14:38:01 ... WebBluetooth is enabled by default in Chrome 14:38:12 ... WebUSB is in intent to ship 14:38:24 https://www.chromestatus.com/features/5651917954875392 14:38:45 -> https://www.chromestatus.com/features/6261030015467520 WebNFC Chrome status 14:38:59 ... WebNFC will go to origin trial in the near future 14:39:08 ... would be good to transition to WG 14:39:29 ... adding these to this group would also help diversify participation which would be good 14:39:56 dom: that's the first level of support for extending the group 14:40:20 ... if we do this, we'd expect the CG participants from the related CGs to join this WG 14:40:31 ... will take this discussion to the list 14:40:46 TOPIC: Other Business 14:47:18 RRSAgent, draft minutes 14:47:18 I have made the request to generate http://www.w3.org/2017/06/15-dap-minutes.html dom 14:48:37 i/ anssik:/ScribeNick: dom 14:48:40 RRSAgent, draft minutes 14:48:40 I have made the request to generate http://www.w3.org/2017/06/15-dap-minutes.html dom 14:50:17 i/ anssik: we/ScribeNick: dom 14:50:23 RRSAgent, draft minutes 14:50:23 I have made the request to generate http://www.w3.org/2017/06/15-dap-minutes.html dom 14:50:58 Present+ Dom 14:51:04 Present+ Anssi 14:51:04 Present+ Kenneth 14:51:09 Present+ MIkhail 14:51:14 RRSAgent, draft minutes 14:51:14 I have made the request to generate http://www.w3.org/2017/06/15-dap-minutes.html dom 14:51:49 i/ dom: the /ScribeNick: anssik 14:52:37 RRSAgent, draft minutes 14:52:37 I have made the request to generate http://www.w3.org/2017/06/15-dap-minutes.html dom 14:53:15 i/ anssi: DAS/ScribeNick: dom 14:53:17 RRSAgent, draft minutes v2 14:53:17 I have made the request to generate http://www.w3.org/2017/06/15-dap-minutes.html dom 14:54:14 RRSAgent, draft minutes 14:54:14 I have made the request to generate http://www.w3.org/2017/06/15-dap-minutes.html dom 16:56:33 shalamov has joined #dap 17:07:28 youenn has joined #dap 17:26:47 Zakim has left #dap 19:56:50 zkis has joined #dap