12:52:57 RRSAgent has joined #dap 12:52:57 logging to http://www.w3.org/2017/10/05-dap-irc 12:52:59 RRSAgent, make logs world 12:52:59 Zakim has joined #dap 12:53:01 Meeting: Device and Sensors Working Group Teleconference 12:53:01 Date: 05 October 2017 12:54:42 anssik has joined #dap 12:57:54 Present+ 13:01:15 Present+ Anssi, Michail 13:01:36 s/Michail/Mikhail 13:02:08 Present+ Alex 13:04:24 Agenda: https://lists.w3.org/Archives/Public/public-device-apis/2017Oct/0006.html 13:04:37 Chair: Anssi 13:04:44 Present+ Andrey_Logvinov 13:05:01 ScribeNick: dom 13:05:06 Regrets: Fuqiao 13:05:31 Topic: Welcome, scribe selection, agenda review, announcements 13:05:49 Anssi: I'm your new chair 13:06:03 ... since last Friday - would like to thank Frederick for his chairing over the past 8years! 13:06:20 ... I'm humbled to continue from the excellent position where Frederick left the group 13:06:37 ... The challenge as a group moving forward is attracting a more diverse community, incl. more implementors 13:07:05 ... lots of good work and progress happening, looking forward to even more success 13:07:24 Anssi: currently we're running this call on a biweekly basis 13:07:37 we've adjusted the time somewhat (1 hour ealier) 13:07:40 s/ea/ear/ 13:07:48 ... I'm interested in hearing feedback on the schedule 13:08:10 ... is it too often or not? should we move the call even earlier in the day given that we don't have US-based participants on the calls? 13:08:37 Michail: we could take a more event-driven approach to scheduling - only schedule a meeting if there are specific topics to be discussed 13:08:49 s/chai/khai/ 13:09:51 Anssi: we could use github issues to track items worthy of discussion 13:09:58 ... I want to make sure we use our time productively 13:10:06 ... Alex, Andrey, what are your thoughts? 13:10:25 Alex: agree with Mikhail on the agenda policy 13:10:32 ... current time works for me 13:10:39 I agree on the agenda policy, current time is fine 13:11:06 ... we don't have to wait for meetings to assign action points e.g. to do review of external specs 13:12:05 Andrey: I agree on the agenda policy, current time is fine 13:12:50 ... let's have meetings only when there are clear topics for discussion 13:14:18 dom: I'm ok with an event-driven approach, but we need to be careful that calls have also a social function, not just a technical one 13:14:27 Anssi: let's keep the slot open in our agendas 13:14:43 ... but I'll take a more aggressive approach in canceling meetings 13:14:55 ... I'll also think about how to make sure people can bring input to the agenda 13:15:27 Alex: significant updates to the spec might be a trigger for having a call as well 13:15:57 -> http://www.w3.org/mid/120B74A8-66C3-4332-BE91-57204B07A722@lab.ntt.co.jp Web Based BG proposal 13:16:12 Anssi: the Web Based BG has approached us to bring two new deliverables to our next charter 13:16:21 ... I responded based on offline discussions 13:16:31 ... feel free to chime in if you have further feedback 13:16:47 ... otherwise, we'll wait to hear back from them with responses and a possible timing for a call 13:18:08 response sent to Web-based BG https://lists.w3.org/Archives/Public/public-device-apis/2017Oct/0005.html 13:18:56 dom: the BG has been trying to bring their work to standardization, and identified DAS as one likely target 13:19:37 ... I've invited them to send details to our list - please review their suggested specs and give feedback 13:19:45 ACTION-809? 13:19:45 ACTION-809 -- Alexander Shalamov to Review automotive specifications with regards to generic sensor api -- due 2017-09-28 -- CLOSED 13:19:45 http://www.w3.org/2009/dap/track/actions/809 13:20:03 Anssi: Alex unfortunately reviewed a spec that wasn't the latest one 13:20:06 https://github.com/w3c/automotive/issues/239 13:20:48 Anssi: can you give us a high level overview of the results of your review? 13:20:55 ... how relevant is it to our work? 13:21:17 Alex: I was a bit upset by having been misled by the WG home page on which specs are relevant 13:21:57 ... the latest specs (VISS and VIAS), which are clients to a Web Socket protocol, may have synergy in the future, but not just at the moment 13:22:21 ... e.g. a user agent requesting an increase of the light on the back seat 13:22:43 ... their approach to sensors is different - it assumes always-running sensors 13:28:51 https://www.w3.org/Submission/2016/SUBM-viwi-service-car-20161213/ 13:30:23 https://github.com/GENIVI/vehicle_signal_specification 13:31:01 https://w3c.github.io/automotive/vehicle_data/vehicle_information_service.html 13:32:16 Dom: sorry for the confusion; I think comparison with VISS in terms of interaction model might still be useful 13:32:23 reopen ACTION-809 13:32:23 Re-opened ACTION-809. 13:32:44 Topic: Minutes approval 13:32:47 proposed RESOLUTION: Minutes from 21 September 2017 are approved 13:33:13 RESOLUTION: Minutes from 21 September 2017 are approved https://lists.w3.org/Archives/Public/public-device-apis/2017Sep/0024.html 13:33:19 RESOLUTION: Minutes from 21 September 2017 are approved 13:33:30 Topic: Generic Sensors 13:33:42 -> https://lists.w3.org/Archives/Public/public-device-apis/2017Oct/0002.html Generic Sensor API Level 1 issues addressed 13:33:49 Anssi: congrats on this milestone! 13:34:03 -> https://lists.w3.org/Archives/Public/public-device-apis/2017Oct/0004.html Generic Sensor API revised Working Draft published 13:34:33 -> https://github.com/w3c/sensors/issues/299 Wide review tracker 13:34:44 Anssi: Wide review is requried prior to entering to CR 13:34:58 ... and needs enough time for people to review, and time to integrate feedback 13:35:32 ... the bug is to help us track what we need for the wide review 13:37:03 https://lists.w3.org/Archives/Public/public-device-apis/2017Aug/att-0017/das-review.pdf 13:39:29 Anssi: last year we got TAG review on Generic Sensors & ALS 13:40:01 ... I think we have addressed their feedback, but it would be great if the editors could double check 13:41:07 https://github.com/w3ctag/design-reviews/issues/110 13:41:14 https://github.com/w3ctag/design-reviews/issues/115 13:41:38 Anssi: we should highlight the significant differences since the last review; the HTML diff is useless from that perspective 13:43:06 ACTION: Alex to review TAG feedback for Generic Sensor / ALS and prepare list of changes for next review with Mikhail 13:43:06 Error finding 'Alex'. You can review and register nicknames at . 13:48:23 Dom: I don't think we need to go through the I18N questionnaire given the scope of our spec 13:48:42 ... likewise A11Y told us last year they didn't see intersection of ALS & Generic sensor 13:48:58 ... so we may want to notify them, butI don't think we need to go through their questionnaire 13:49:05 ACTION: Alexander to review TAG feedback for Generic Sensor / ALS and prepare list of changes for next review with Mikhail 13:49:06 Created ACTION-812 - Review tag feedback for generic sensor / als and prepare list of changes for next review with mikhail [on Alexander Shalamov - due 2017-10-12]. 13:49:26 Anssi: quick update on implementations and getting feedback on the spec 13:49:51 Mikhail: Origin trial will start with Chrome M63 13:49:55 ... it should reach Chrome beta in November 13:50:06 ... Origin trial lasts for 3 releases in a row, can be extended if needed 13:50:25 ... so we expect it to be at least until M65 13:50:43 Alex: which means spring next year 13:51:12 Anssi: there is a questionnaire built into the origin trial 13:51:14 q+ 13:51:37 Alex: there is Web fundamentals article from which we already got some feedback 13:52:18 ... one of the feedback was the difficulty in getting examples of concrete sensors - which we fixed in the explainers 13:53:22 dom: looking at organizing an interview with Kenneth on the specs fyi 13:53:50 Anssi: moving on to level 2 issues (not addressed in the implementation of origin trial) 13:54:39 Alex: the level 2 issues are mostly extension of current functionalities - they shouldn't change the API shape 13:54:54 ... two main features under discussion: service worker support and discovery 13:57:12 s/Alex/Mikhail/ 13:57:23 Topic: Wake Lock 13:57:33 Dom: are we ready to transition Wake Lock to CR? 13:57:35 Andrey: yes 13:57:48 ACTION: Dom to work with Anssi on requesting transition of Wake Lock to CR 13:57:48 Created ACTION-813 - Work with anssi on requesting transition of wake lock to cr [on Dominique Hazaël-Massieux - due 2017-10-12]. 13:58:58 Dom: implementation plans? 13:59:21 Andrey: haven't started yet - will recontact my Google contacts to see if they still want to do it themselves or not 13:59:44 Toipc: Rechartering 13:59:55 -> http://w3c.github.io/dap-charter/DeviceAPICharter.html Draft new charter 14:00:02 Anssi: charter expires by the end of the year 14:00:22 ... new charter adds new deliverables (geo v2, finishing up device orientation) 14:00:50 ... plan would be to extend the charter until Jan so that we can get feedback at TPAC before starting the review process 14:01:39 ... please bring up issues and discuss 14:01:59 Dom: plan would be to go for a one-year charter to demonstrate take up of our work 14:03:43 Anssi: we MAY have a call in two weeks 14:03:51 RRSAgent, draft minutes 14:03:51 I have made the request to generate http://www.w3.org/2017/10/05-dap-minutes.html dom 15:56:30 Zakim has left #dap 17:53:49 zkis has joined #dap 19:23:19 zkis has joined #dap