13:35:17 RRSAgent has joined #dap 13:35:17 logging to http://www.w3.org/2015/05/14-dap-irc 13:35:19 RRSAgent, make logs world 13:35:19 Zakim has joined #dap 13:35:21 Zakim, this will be DAP 13:35:21 ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 25 minutes 13:35:22 Meeting: Device APIs Working Group Teleconference 13:35:22 Date: 14 May 2015 13:35:55 Agenda: https://lists.w3.org/Archives/Public/public-device-apis/2015May/0038.html 13:36:09 fjh has changed the topic to: dap agenda https://lists.w3.org/Archives/Public/public-device-apis/2015May/0038.html code 3279 13:36:30 Regrets+ Dominique_Hazael-Massieux 13:36:47 Chair: Frederick_Hirsch 13:36:55 Present+ Frederick_Hirsch 13:37:32 Topic: Welcome, scribe selection, agenda review, announcements 13:41:09 anssik has joined #dap 13:56:53 fjh_ has joined #dap 13:57:16 fjh_ has joined #dap 13:57:22 Claes has joined #dap 13:57:48 UW_DAP()10:00AM has now started 13:57:55 +[IPcaller] 13:57:56 +[IPcaller.a] 13:57:58 zakim, ipcaller is me 13:57:58 +fjh; got it 13:58:03 zakim, who is here? 13:58:03 On the phone I see [IPcaller.a], fjh 13:58:05 On IRC I see Claes, fjh_, anssik, Zakim, RRSAgent, fjh, mounir, richt, slightlyoff, tobie, Josh_Soref, trackbot 13:58:14 zakim, IPcaller.a is anssi 13:58:14 +anssi; got it 13:58:35 Present+ Anssi_Kostiainen 14:00:30 + +46.7.03.79.aaaa 14:00:48 zakim, aaaa is Claes 14:00:48 +Claes; got it 14:00:58 Present+ Claes_Nilsson 14:01:36 I'm having a hard time joining the call. Please bear with me. 14:02:11 zakim, code? 14:02:11 the conference code is 3279 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), fjh 14:05:32 +[IPcaller] 14:05:44 [ is me 14:05:50 Zakim, [ is me 14:05:50 +tobie; got it 14:06:14 -tobie 14:06:25 arg 14:07:16 Present+ Tobie_Langel 14:08:30 ScribeNick: anssik 14:08:42 TOPIC: Welcome, scribe selection, agenda review, announcements 14:08:58 fjh: new members joined the group, welcome 14:09:00 Welcome to new members 14:09:00 Alexis, Intel https://lists.w3.org/Archives/Public/public-device-apis/2015Mar/0006.html 14:09:01 Yong Ding, Huawei https://lists.w3.org/Archives/Public/public-device-apis/2015Apr/0026.html 14:09:02 Tobie, Intel https://lists.w3.org/Archives/Public/public-device-apis/2015May/0002.html 14:09:37 anssi: alexis has been working on webkit, chromium, working on sensor prototypes 14:09:57 anssik: is based in brussels may not be able to join calls 14:10:04 s/anssi:/anssik:/ 14:10:11 s/brussels/Brazil/ 14:10:21 Media Capture and Streams" transitioned to Last Call. 14:10:29 Feedback on /TR styles requested https://lists.w3.org/Archives/Public/public-device-apis/2015Apr/0036.html 14:10:45 continuous change in the planning 14:10:59 +[IPcaller] 14:11:06 Zakim, [ is me 14:11:06 +tobie; got it 14:12:05 TOPIC: Minutes approval 14:12:21 Approve minutes from 5 March 2015 14:12:21 Topic: Minutes approval 14:12:31 proposed RESOLUTION: Minutes from 5 March 2015 are approved, https://lists.w3.org/Archives/Public/public-device-apis/2015Mar/att-0003/minutes-2015-03-05.html 14:12:42 RESOLUTION: Minutes from 5 March 2015 are approved, https://lists.w3.org/Archives/Public/public-device-apis/2015Mar/att-0003/minutes-2015-03-05.html 14:12:50 Topic: Zakim to WebEx change 14:12:52 Discuss change to WebEx and timing 14:12:53 https://lists.w3.org/Archives/Public/public-device-apis/2015May/0037.html 14:13:41 will use webex for voice only, not chat or screen sharing, will send info, plan to use it instead of zakim for next call 14:13:46 Topic: Web Payments Use Cases 14:13:54 Request for review before June 16: https://lists.w3.org/Archives/Public/public-device-apis/2015Apr/0038.html 14:14:17 Would it be ok to take the topic "TCP/UDP Socket API to Community Group" now? 14:14:40 Topic: TCP/UDP Socket API to Community Group 14:14:45 https://lists.w3.org/Archives/Public/public-device-apis/2015Apr/0000.html and https://lists.w3.org/Archives/Public/public-device-apis/2015Apr/0022.html 14:16:20 from http://www.w3.org/2011/07/DeviceAPICharter: "... based on the current Web browser security model" 14:18:31 I’ve reviewed this and the community group seems like a good approach for now, if the situation changes we can consider moving this into DAP if it makes sense 14:18:51 Topic: Ambient Light 14:18:58 Anssi msg to Microsoft team https://lists.w3.org/Archives/Public/public-device-apis/2015Apr/0028.html 14:19:17 Adrian acknowledged 14:19:30 Topic: Generic Sensor API 14:19:41 issues: https://github.com/w3c/sensors/ 14:20:19 tobie: I was expecting people to contribute via GH issues 14:20:40 ... I'm happy to go through the high level bits 14:20:59 q+ 14:21:03 q- 14:21:07 ... can work on a FPWD too 14:21:34 ... we started working on the GH repo around Nov 2014 14:21:42 ... a lot of activity within a week or so 14:21:57 ... the high level goals 14:22:47 ... has been working with Rick Waldron who contributed the initial spec blueprint 14:23:16 ... that can be applied to specific sensors being worked on in this group 14:23:59 q? 14:24:01 ... issues: understand performance issues, how much the browser is aware of existing sensors 14:24:46 q+ 14:24:50 q+ 14:25:27 ... would like to talk to implementers with regard the issues around performance in particular 14:25:32 ack anssik 14:25:51 anssik: should connect you with our browser people that work on chromium 14:26:23 anssik: you need to reach out to Google 14:26:46 anssik: ?? has implemented device orientation, motion 14:26:52 anssik: also Mounir 14:27:16 Tim Volodine is working on sensors in Chromium 14:27:32 s/??/Tim Volodine/ 14:27:50 ... also Riju from Intel has implemented Ambient Light 14:28:19 ScribeNick: fjh 14:28:29 anssik: issues are performance and discovery 14:28:48 tobie: need to know which sensors are available and what is cost, do it sync or async 14:29:08 anssiK; not just entry point issue 14:29:27 tobie: does presence of api imply that sensor exists? 14:29:31 s/api/API/ 14:30:04 tobie: all same question, need to inderstand life cycle of sensor vs lifecycle of page 14:30:16 s/inderstand/understand/ 14:30:29 tobie: main issue is knowing whether sensor is there or not 14:30:40 anssik: generic sensor api designed from node.js perspectaive 14:30:49 q+ 14:30:52 s/perspectaive/perspective/ 14:31:12 tobie: simple API vs performance 14:31:57 ack Claes 14:32:37 Claes: in web of things interest group, what is connection to that group 14:32:48 q+ on IoT 14:32:48 … using REST APIs 14:32:58 ack tobie 14:32:58 tobie, you wanted to comment on IoT 14:33:27 tobie: Raggett shared presentation with me from his Munich, will look at it 14:33:43 s/Raggett/Dave Raggett dsr 14:35:06 Claes: might help mapping concrete Javascript APIs to generic sensor apis 14:35:11 tobie: can you please open github issue 14:35:14 Claes: yes 14:36:01 fjh: producing a draft spec sounds like a good next step 14:36:09 Need to drop off now. Bye 14:36:14 ... allows us to get feedback from people now on calls 14:36:36 -Claes 14:38:28 will have calls as needed but expect much work will be async, on list 14:38:54 tobie: expect ot have a draft end May 14:38:55 tobie: targeting end of May for the draft spec 14:39:04 s/tobie: expect ot have a draft end May// 14:39:21 rrsagent, generate minutes 14:39:21 I have made the request to generate http://www.w3.org/2015/05/14-dap-minutes.html fjh 14:39:59 s/ [ is me// 14:40:06 s/arg// 14:40:22 s/I'm having a hard time joining the call. Please bear with me.// 14:41:05 s/dsr/(dsr)/ 14:42:06 anssik: feedback from both Node/io.js and browser implementers would be very welcome early in the process 14:43:13 anssik: tobie if you have list of issues related to performance I could share with our internal team 14:44:42 -tobie 14:44:45 anssik: issue #9 re event targets is performance consideration 14:45:03 +[IPcaller] 14:45:05 … what are other issues on critical 14:46:21 suggest you ask about issues on list anssik, tobie can answer on list 14:47:13 Topic: Battery 14:47:18 fjh: anything new? 14:47:50 anssik: update from Intel QA re tests - looking at root cause for test failures, will report to the list 14:48:14 … not sure if issue is with test harness or test cases, so need to look into it. 14:48:29 … still pending mozilla implementation update as well, no apparent activity 14:54:49 -[IPcaller] 14:55:07 I suggest that on a call we review github decisions and resolve them in conjunction with discussing the draft, thus avoiding a purely administrative discussion and linking with real work 14:55:12 zakim, who is here? 14:55:12 On the phone I see anssi, fjh 14:55:14 On IRC I see anssik, Zakim, RRSAgent, fjh, mounir, richt, slightlyoff, tobie, Josh_Soref, trackbot 15:16:48 -fjh 15:16:54 -anssi 15:16:55 UW_DAP()10:00AM has ended 15:16:55 Attendees were fjh, anssi, +46.7.03.79.aaaa, Claes, [IPcaller], tobie 15:17:15 rrsagent, generate minutes 15:17:15 I have made the request to generate http://www.w3.org/2015/05/14-dap-minutes.html fjh 15:33:00 fjh_ has joined #dap 15:36:18 Regrets+ Giri_Mandyam 15:37:04 rrsagent, generate minutes 15:37:04 I have made the request to generate http://www.w3.org/2015/05/14-dap-minutes.html fjh_ 15:41:07 fjh_ has joined #dap 15:41:40 s/\[ is me// 16:02:52 fjh_ has joined #dap 16:58:17 Zakim has left #dap