13:43:33 RRSAgent has joined #dap 13:43:33 logging to http://www.w3.org/2015/10/15-dap-irc 13:43:35 RRSAgent, make logs world 13:43:35 Zakim has joined #dap 13:43:37 Zakim, this will be DAP 13:43:37 I do not see a conference matching that name scheduled within the next hour, trackbot 13:43:38 Meeting: Device APIs Working Group Teleconference 13:43:38 Date: 15 October 2015 13:47:12 Agenda: https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/0023.html 13:47:25 fjh has changed the topic to: dap agenda https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/0023.html webex passwd "dap" 13:47:54 Chair: Frederick_Hirsch 13:47:57 Present+ Frederick_Hirsch 13:48:10 Topic: Welcome, scribe selection, agenda review, announcements 13:59:06 Good morning. 14:01:49 yes, sorry (I realized this) 14:01:57 Present+ Lukasz_Olejnik 14:02:07 Present+ Dominique_Hazael-Massieux 14:02:20 anssik has joined #dap 14:02:33 Present+ Anssi_Kostiainen 14:02:40 zakim, who's on the call 14:02:40 I don't understand 'who's on the call', anssik 14:02:46 zakim, who is on the call? 14:02:46 Present: Frederick_Hirsch, Lukasz_Olejnik, Dominique_Hazael-Massieux, Anssi_Kostiainen 14:03:48 scribeNick: anssik 14:03:58 Results of Vote on Media Capture and Streams Constraints Registry - https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/0021.html 14:03:58 Web Platform WG replaces WebApps WG, http://www.w3.org/2015/10/webplatform-charter.html 14:04:11 fjh: vote on the mediacapture-main went through 14:04:18 ... Web Platform WG is the new WebApps WG 14:04:31 Topic: Minutes approval 14:04:33 Approve minutes from 1 Oct 2015 14:04:34 proposed RESOLUTION: Minutes from 1 Oct 2015 are approved, https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/att-0000/minutes-2015-10-01.html 14:04:48 RESOLUTION: Minutes from 1 Oct 2015 are approved, https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/att-0000/minutes-2015-10-01.html 14:04:55 Topic: Charter 14:04:59 https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/0022.html 14:05:27 dom: integrated changes to the charter drafy 14:05:34 s/drafy/draft/ 14:05:58 ... going through renewal process, W3C mgmt approval, AC review, before that three week CfC 14:06:09 ... some changes may be controversial: 14:06:23 ... 1) New Document and Software License enabling forking 14:06:39 ... 2) Expedited process for adding new deliverables to the charter 14:07:18 ... 3) Streamlining the existing deliverables list, remove inactive work, only exception being NetInfo API which has implementations 14:07:54 ... 4) Use of asynchronous decision policy 14:08:04 fjh: does 4 mean we do not need to do CfCs? 14:08:24 dom: formally speaking we could do that, but better do explicit CfCs 14:09:10 Present+ Tobie_Langel 14:10:07 dom: expedited process means we can update the charter with a new deliverable, and the W3C mgmt and AC review only 14:11:38 zakim, slap dom 14:11:38 I don't understand 'slap dom', fjh 14:11:43 just continue here. 14:14:00 (I am not in WebEx) 14:14:32 s/(I am not in WebEx)// 14:15:20 fjh: propose a two week CfC for the new charter 14:15:56 proposed RESOLUTION: proceed with two week CfC for WG to approve proceeding with draft Charter distributed by Dom 14:16:27 RESOLUTION: proceed with two week CfC for WG to approve proceeding with draft Charter distributed by Dom 14:17:52 two questions I raised privately re charter - 1) should group name change, eg Device APIs and Sensors (DAS) 14:20:16 changing name can reflect change of the scope of the work of the group, a new focus, help others understand where this work is done 14:20:27 makes it easier to market what is done 14:21:12 dom: bluetooth won't move here, question about NFC still 14:23:49 Sensors and media - SAM 14:24:37 it should have the word Sensor in it 14:24:51 suggest CfC is with understanding with group name could change 14:25:19 Device Platform 14:26:24 Device Sensor Platform 14:28:24 Device APIs and Sensors Working Group (DAS WG) 14:28:57 why not "Device and Sensors Working Group" 14:29:57 proposed RESOLUTION: use "Device and Sensors Working Group" in propose charter 14:30:32 s/propose/proposed/ 14:30:43 RESOLUTION: use "Device and Sensors Working Group" in proposed charter 14:30:49 will include that in CfC 14:31:48 Topic: Web Intents Task Force 14:31:50 Status and plans for Web Intents Task Force (was joint with WebApps but not mentioned in Web Platform charter) 14:31:58 [on the topic of Web Intents like discussion, it's restarting again :) http://www.backalleycoder.com/2015/10/13/app-to-app-interaction-apis/ ] 14:32:00 fjh: suggest we close the TF 14:32:06 ... not on the Web Platform WG charter 14:33:27 dom: some blog posts on the topic published recently, regardless should pursue with closing 14:33:37 action: fjh to send CfC for 2 week approval of progressing with charter and name change 14:33:37 Created ACTION-739 - Send cfc for 2 week approval of progressing with charter and name change [on Frederick Hirsch - due 2015-10-22]. 14:33:51 action: fjh to send CfC to close Web Intents TF 14:33:51 Created ACTION-740 - Send cfc to close web intents tf [on Frederick Hirsch - due 2015-10-22]. 14:33:55 +1 14:34:02 Topic: Generic Sensor API 14:34:13 fjh: FPWD published today, thanks Tobie 14:34:18 WebI2C and WebGPIO https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/0015.html 14:34:59 tobie: would like to talk to Rick re the WebI2C and WebGPIO 14:35:41 ... Rick seems to be opposing this low-level APIs, and prefers to see Bluetooth and Serial APIs for the Web instead 14:36:55 ... a major issue is the security model that is different from the Web's 14:37:13 ... nevertheless, an interesting area to explore 14:37:54 breakout session 14:38:35 http://www.w3.org/wiki/TPAC/2015/SessionIdeas#WebGPIO.2C_WebI2C_API 14:39:39 fjh: would be interesting to see the proceedings from the breakout session, please report back 14:40:06 tobie: I was starting to work on the proximity API to see if I can rewrite it on top of Generic Sensor API 14:40:23 ... some sensors would like to get data out at regular intervals 14:40:34 ... for some sensors, only when the change happens 14:40:46 ... e.g. geolocation 14:41:03 ... for device location will want to get low latency 14:41:24 ... in Android, different API for different type of sensors 14:41:33 ... wondering how to handle that in the Generic Sensor API 14:41:58 ... should we have two different Generic Sensor APIs to cater for both cases? 14:42:00 q+ 14:42:05 q+ 14:42:23 ack anssik 14:42:45 anssik: ambient light might be better one to start with for modeling on top of generic sensor API 14:43:09 anssik: we have code 14:43:20 anssik: many platforms use ambient light to implement proximity 14:43:50 q- 14:44:14 q+ to mention that both use cases are important, regular reporting and exception reporting, how to design open 14:44:38 tobie: this is like a higher level sensor then 14:44:55 i/ambient light might/ScribeNick: fjh 14:45:10 ScribeNick: anssik 14:45:20 https://w3c.github.io/ambient-light/ 14:46:05 I'm currently in the process of writing a little doc on possible privacy issues in a bunch of APIs, starting to arrive on possibly interesting constructs/arguments [still I keep it at a far side in order not to interfer with the group's work/jeopardize anything] - hopefully will be of use 14:46:35 https://w3c.github.io/proximity/ 14:47:05 I will try to minimize noise and report only when it has taken shape, then possibly ask for input, CC with PING group as well - perhaps a blueprint for privacy considerations will emerge + other avenues of work 14:47:07 s/code/experimental/ 14:47:10 q? 14:47:12 ack fjh 14:47:12 fjh, you wanted to mention that both use cases are important, regular reporting and exception reporting, how to design open 14:47:25 scribeNick: anssik 14:47:40 fjh: both use cases are important, regular reporting and exception reporting, how to design open 14:48:00 fjh: propose both should be in the same spec 14:48:18 tobie: solved a bunch of issues, some issues still open 14:48:26 ... that need to be added to the spec 14:48:38 ... want to have issues triaged by TPAC 14:49:03 +1 14:49:09 +1 for echidna 14:49:36 dom: I can help setup echidna at TPAC 14:49:44 support using auto-WD publication for generic sensor API 14:51:11 Topic: Upcoming meetings 14:51:19 fjh: no meeting at TPAC 14:51:23 http://www.w3.org/2009/dap/minutes.html#upcoming-teleconferences 14:51:28 s/at and during/ 14:51:50 Upcoming Teleconferences 14:51:50 15 October 2015, agenda 14:51:50 29 October 2015, cancelled (TPAC) 14:51:50 12 November 2015, agenda 14:51:50 26 November 2015, Cancelled (US Thanksgiving) 14:51:50 10 December 2015, agenda 14:51:50 24 December 2015, Cancelled (Christmas) 14:51:52 7 January 2015, agenda 14:53:20 can we move the 10th Dec to the 3rd Dec 14:53:26 everyone on call ok with it 14:53:32 me lukasz ? 14:53:50 +1 14:54:33 proposed RESOLUTION: Cancel call on 10th Dec, schedule call 3 De 14:54:44 s/De/Dec/ 14:54:53 RESOLUTION: Cancel call on 10th Dec, schedule call 3 Dec 14:55:35 Topic: Other Business 14:55:36 none 14:55:40 Topic: Adjourn 14:55:45 rrsagent, generate minutes 14:55:45 I have made the request to generate http://www.w3.org/2015/10/15-dap-minutes.html fjh 14:58:32 s/yes, sorry (I realized this)// 14:58:55 s/Good morning.// 14:59:41 s/experimental/experimental code/ 15:00:25 s/triaged by TPAC/triaged by TPAC; can we use the auto WD publication mechanism for generic sensor API/ 15:00:41 s/support using/I support using/ 15:00:58 s/me lukasz ?// 15:01:08 rrsagent, generate minutes 15:01:08 I have made the request to generate http://www.w3.org/2015/10/15-dap-minutes.html fjh 15:02:44 s/no meeting at TPAC/no DAP meeting at TPAC, but there will be related ad hoc and break out sessions/ 15:03:10 rrsagent, generate minutes 15:03:10 I have made the request to generate http://www.w3.org/2015/10/15-dap-minutes.html fjh 15:04:09 s/just continue here./ 15:04:31 rrsagent, generate minutes 15:04:31 I have made the request to generate http://www.w3.org/2015/10/15-dap-minutes.html fjh 15:07:53 http://www.w3.org/2008/xmlsec/Group/Scribe-Instructions.html 16:03:56 mats has joined #dap 17:01:15 Zakim has left #dap