13:31:50 RRSAgent has joined #dap 13:31:50 logging to http://www.w3.org/2015/06/25-dap-irc 13:31:52 RRSAgent, make logs world 13:31:52 Zakim has joined #dap 13:31:54 Zakim, this will be DAP 13:31:55 Meeting: Device APIs Working Group Teleconference 13:31:55 Date: 25 June 2015 13:31:56 ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 29 minutes 13:32:15 fjh has changed the topic to: dap agenda https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0161.html webex dap 13:32:20 Agenda: https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0161.html 13:32:42 Chair: Frederick_Hirsch 13:32:44 Present+ Frederick_Hirsch 13:33:17 Regrets+ Tobie_Langel 13:51:19 dom_ has joined #dap 13:58:25 can you hear me? 14:00:43 Topic: Welcome, scribe selection, agenda review, announcements 14:00:48 ScribeNick: fjh 14:01:02 Present+ Anssi_Kostiainen 14:01:21 CfC to shelve Permissions API ends today, https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0159.html 14:01:28 TPAC,http://www.w3.org/2015/10/TPAC/ 14:02:38 anssik has joined #dap 14:06:02 s;today.*;today, https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0150.html; 14:06:47 fjh: looks like we can go ahead with publication tomorrow, if no concerns. I've prepared draft for publication Tue 2 July 14:06:54 dom: I can make the publication request 14:06:55 fjh: thanks 14:07:22 fjh: TPAC breakout sounds good, thanks 14:07:36 Topic: Minutes approval 14:07:44 fjh: Approve minutes from 11 June 2015 14:07:50 RESOLUTION: Minutes from 11June 2015 are approved, https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/att-0104/minutes-2015-06-11.html 14:07:57 Topic: Battery 14:08:05 https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0156.html 14:08:30 https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0163.html 14:09:42 fjh: battery testing still in progress thanks to Intel, need work on Mozilla to progress 14:09:52 anssik: person working on it in private branch 14:10:12 Topic: HTML Media Capture 14:10:19 https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0157.html 14:11:35 fjh: do we know which browsers based on webkit are offering this HTML Media Capture and can provide test results 14:11:44 dom: code is in webkit, but work required for browser to use it 14:11:56 s/dom/anssik/ 14:12:15 anssik: we had blackberry browser, but that status of Blackberry OS is now unknown 14:12:24 ... there are some forks 14:12:32 fjh: so we have an issue related to two implementations 14:12:39 anssik: is on chrome in android 14:13:42 anssik: webkit places - apple, mozilla ok with accept attributes, similar but not exact, microsoft not clea 14:13:52 ... maybe we should check with microsoft 14:13:57 s/clea/clear/ 14:14:23 anssik: small amount of work with WebIDL to tie into platform 14:15:00 dom: should we stop having only one implementation or try to get others; question of whether to continue with this 14:15:03 ... is it useful 14:15:22 anssik: can review use cases that are not addressed by accept attribute, 14:15:27 s/attribute,/attribute/ 14:15:34 rssagent, generate minutes 14:15:55 rrsagent, generate minutes 14:15:55 I have made the request to generate http://www.w3.org/2015/06/25-dap-minutes.html fjh 14:16:05 s/rssagent, generate minutes// 14:16:29 dom: if using instagram don't want to use photo gallery, part of rationale 14:18:14 action: anssik to contact Mozilla and Microsoft re interest in implementing HTML Media Capture vs shelving 14:18:14 Created ACTION-734 - Contact mozilla and microsoft re interest in implementing html media capture vs shelving [on Anssi Kostiainen - due 2015-07-02]. 14:18:43 anssik: taking photo still hard on web platform if you need to use getUserMedia, so HTML Media Capture should be relevant 14:19:32 https://bugzilla.mozilla.org/show_bug.cgi?id=741393 14:19:39 fjh: if we do not have interest then I will send a CfC to shelve, resulting in it being published as a Note and work stopped 14:20:32 Topic: Wake Lock API 14:20:40 https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0158.html 14:20:47 fjh: looks like this work is progress 14:21:21 response, https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/att-0168/00-part 14:21:30 https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0169.html 14:21:53 Topic: Way forward on Proximity Events and Ambient Light APIs 14:22:03 https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0159.html 14:22:14 fjh: we have choice, I think a lot depends on timing 14:22:24 fjh: have not gotten much response to my question on the list 14:22:59 anssik: we need better idea by having generic api better developed and then seeing fit 14:23:06 dom: not sure if either in high deman 14:23:21 s/deman/demand, so can wait for a few months to decide/ 14:23:35 dom: most logical might be to build on generic sensor API 14:25:28 dom: I haven't heard concern about these two APIs being delayed or strong desire for them to move forward 14:25:38 dom: what is status of microsoft on these 14:25:57 anssik: ambient light under development accroding to microsoft web page, shared this with Adrian and Travis 14:26:18 anssik: they are aware that we are working on the generic sensor API 14:28:09 fjh: summary - continue on generic sensor api path, with view toward moving Proximity and Ambient toward Generic Sensor API 14:28:25 dom: know no strong interest in current APIs, concerns from Mozilla, possibility of confusion 14:28:57 ... suggest we make clear that we don't expect to continue these in the current approach 14:29:18 ... current consensus of group is toward generic sensor 14:29:26 fjh: have only seen one response to my message, from Tobie 14:31:57 proposed RESOLUTION: CfC to return Proximity and Ambient light to WD noting that approach will be generic sensor API based 14:32:32 dom: suggest we publish with strong note that being based on Generic Sensor API 14:32:46 dom: not sure we should remove technical content 14:33:07 anssik: add notes to editors draft, not sure we need to publish 14:33:30 dom: it is important, some people are confused if TR does not match what is on our roadmap 14:33:56 dom: don't want announcement 14:34:21 dom: can publish using github 14:34:31 anssik: moved ambient light, will do for proximity 14:34:37 s/github/echidna (the new pub system) 14:36:41 action: anssik to create editor drafts for Ambient LIght and Proximity indicating new approach toward generic sensor API, also drafts for publication to TR space 14:36:41 Created ACTION-735 - Create editor drafts for ambient light and proximity indicating new approach toward generic sensor api, also drafts for publication to tr space [on Anssi Kostiainen - due 2015-07-02]. 14:37:09 action: fjh to send CfC for WD publication for Ambient Light and Proximity once drafts available 14:37:09 Created ACTION-736 - Send cfc for wd publication for ambient light and proximity once drafts available [on Frederick Hirsch - due 2015-07-02]. 14:37:45 Topic: Generic Sensor API 14:38:07 anssi: what is up with device orientation spec, no progress in 15 months 14:38:36 dom: in May AC meeting disussed with Giri, unclear whether work will progress 14:38:45 http://w3c.github.io/deviceorientation/spec-source-orientation.html 14:38:53 dom: we need to decide whether to continue or not, Giri will bring back to group 14:38:56 https://github.com/w3c/deviceorientation 14:39:07 dom: also checking with staff contact for that group, have not heard 14:39:17 DeviceOrientation Event Specification Editor's Draft 12 March 2014 14:39:21 dom: need to bring this up on geolocation mailing list 14:39:46 anssik: concern over use of Dom Events 14:39:54 s/Dom/DOM/ 14:40:18 anssik: do we need a task force for sensor related specifications 14:40:37 fjh: why not a specific WG? 14:41:22 dom: difference ambient light/proximity and device orientation is that device orientation is widely deployed and implemented 14:41:25 dom: should ask geolocation to finish standarization of current API 14:41:35 s/standarization/standardization/ 14:41:56 dom: then how and why to develop API on top of sensor API 14:42:15 ... could do in DAP if agreed with geolocation wg 14:42:37 +1 14:42:55 ... reason is that not mcuh interest in that group, and also developing generic sensor API, also rechartering 14:43:18 s/why not a specific WG?// 14:46:39 ACTION: Dom to chat with Geo Chair and Staff contact on future of device orientaiton 14:46:40 Created ACTION-737 - Chat with geo chair and staff contact on future of device orientaiton [on Dominique Hazaël-Massieux - due 2015-07-02]. 14:47:10 Topic: DAP Rechartering 14:47:19 request for comments, input: https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0149.html 14:47:38 dom: asks for review of proposal 14:50:25 discussion of webapps and HTML re-arrangement, media likely to be separate 14:50:36 s/discussion of /dom:/ 14:50:40 rrsagent, generate minutes 14:50:40 I have made the request to generate http://www.w3.org/2015/06/25-dap-minutes.html fjh 14:51:22 Present+ Dominique_Hazael-Massieux 14:51:23 s/can you hear me?/ 14:51:24 s/can you hear me?// 14:52:16 i;ends today;CfC to shelve Permissions API ends today, https://lists.w3.org/Archives/Public/public-device-apis/2015Jun/0150.html; 14:52:31 Topic: Adjourn 14:54:44 rrsagent, generate minutes 14:54:44 I have made the request to generate http://www.w3.org/2015/06/25-dap-minutes.html fjh 14:58:55 Andrey_Logvinov has joined #dap 15:38:06 Zakim has left #dap 15:57:35 fjh has joined #dap 17:50:59 fjh has joined #dap 18:20:46 mats has joined #dap