13:20:44 RRSAgent has joined #dap 13:20:44 logging to http://www.w3.org/2013/09/04-dap-irc 13:20:46 RRSAgent, make logs world 13:20:46 Zakim has joined #dap 13:20:48 Zakim, this will be DAP 13:20:48 ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 40 minutes 13:20:49 Meeting: Device APIs Working Group Teleconference 13:20:49 Date: 04 September 2013 13:20:57 Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0000.html 13:21:15 fjh has changed the topic to: dap 3279 ; http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0000.html 13:21:39 Chair: Frederick_Hirsch 13:21:54 Present+ Frederick_Hirsch 13:23:53 Regrets+ Dom 13:58:42 UW_DAP()10:00AM has now started 13:58:44 +[IPcaller] 13:58:54 zakim, IPcaller isme 13:58:55 I don't understand 'IPcaller isme', fjh 13:58:59 zakim, IPcaller is me 13:58:59 +fjh; got it 13:59:08 rrsagent, generate minutes 13:59:08 I have made the request to generate http://www.w3.org/2013/09/04-dap-minutes.html fjh 13:59:44 Topic: Welcome, agenda review, scribe selection, announcements 13:59:54 Clarke has joined #dap 14:00:31 + +1.303.661.aaaa 14:00:31 - +1.303.661.aaaa 14:00:33 + +1.303.661.aaaa 14:00:41 zakim, aaaa is me 14:00:41 zakim, where is 303? 14:00:42 +Clarke; got it 14:00:42 North American dialing code 1.303 is Colorado 14:01:35 Present+ Clarke_Stevens 14:04:15 Cathy has joined #dap 14:04:26 +??P41 14:04:35 zakim, ??P41 is me 14:04:35 +anssik; got it 14:04:42 Present+ Anssi_Kostiainen 14:05:49 ScribeNick: fjh 14:07:27 zakim, what is the code? 14:07:27 the conference code is 3279 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), fjh 14:07:53 + +33.6.77.84.aabb 14:08:18 zakim, aabb is jcdufourd 14:08:18 +jcdufourd; got it 14:08:27 zakim, who is here? 14:08:27 On the phone I see fjh, Clarke, anssik, jcdufourd 14:08:28 On IRC I see Cathy, Clarke, Zakim, RRSAgent, fjh, jcdufourd, lgombos, dom, richt, mounir, slightlyoff, Josh_Soref, anssik, trackbot 14:09:07 Present+ Jean-Claude_Dufourd 14:10:09 Reminder: No DAP F2F at TPAC, but there will be the Media Capture TF meeting, please attend that. 14:10:35 fjh: if you are attending TPAC please remember to register and make arrangements soon 14:10:54 a new Working Draft of Media Capture and Streams has just been published: http://www.w3.org/TR/2013/WD-mediacapture-streams-20130903/ ; http://www.w3.org/TR/mediacapture-streams/ 14:11:25 Topic: Minutes approval 14:11:36 Approve minutes from 21 August 2013 14:11:37 http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/att-0048/minutes-2013-08-21.html 14:11:49 RESOLUTION: Minutes from 21 August 2013 are approved 14:12:01 Topic: Proximity and Light 14:12:24 LC-2739 http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0055.html 14:12:25 Proximity CR CfC (5 Sept deadline) http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0054.html 14:12:26 Light CR CfC (5 Sept deadline) http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0056.html 14:12:27 using WebIDL's "conforming IDL fragment" conformance class (Barstow, http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0059.html) 14:12:42 fjh: CfC deadline is tomorrow, +1 on list would be useful 14:13:27 fjh: Dom responded to Art that what we are doing makes sense 14:13:39 s/Dom/dom/ 14:14:09 anssik: will look at this 14:15:17 http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0061.html 14:15:40 Topic: Vibration 14:15:54 Remaining questions/comments: 14:15:54 Question/Comment on CR draft: http://lists.w3.org/Archives/Public/public-device-apis/2013Jul/0050.html 14:15:55 Question Vibration and iframes, http://lists.w3.org/Archives/Public/public-device-apis/2013Jul/0055.html 14:15:56 Question: Vibration strength http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0040.html 14:15:57 Supporting strength (Marcos) http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0062.html 14:16:10 fjh: anssik, can you please review these and respond on the list. 14:16:15 fjh: I think most are editorial 14:16:37 fjh: I believe the WG is deciding to defer vibration strenght 14:16:44 s/trenght/strength/ 14:16:49 + +1.781.362.aacc 14:16:55 zakim, aacc is me 14:16:55 +Cathy; got it 14:17:27 fjh: I would think vibration would only be active for the active window 14:17:44 anssik: fix would be to say top level browsing context 14:18:07 fjh: that makes sense to me, thought you already made that change 14:18:15 anssik: did it for proximity 14:18:22 fjh: I think we should be consistent 14:18:31 anssik: this is a generic issue 14:19:13 fjh: I think we should make this change in the editors draft, pull it in in PR 14:19:37 anssik: walks through choices, looking at mail http://lists.w3.org/Archives/Public/public-device-apis/2013Jul/0055.html 14:19:47 fjh: clarification needed 14:20:06 fjh: would relate to the other strength issues 14:20:55 fjh: hey, vibrating ads in hidden iframes.... 14:21:00 s/hidden// 14:21:37 action: anssik to make proposal on list regarding multiple vibration API invocations in frames for Vibration 14:21:39 Created ACTION-652 - Make proposal on list regarding multiple vibration api invocations in frames for vibration [on Anssi Kostiainen - due 2013-09-11]. 14:22:26 fjh: re vibration strength, Marcos suggested in next version, http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0062.html 14:22:41 anssik: do we have a concrete proposal 14:22:59 Present+ Cathy_Chan 14:23:10 fjh: no 14:23:35 RESOLUTION: defer Vibration strength to next version of Vibration API 14:23:56 anssik: ask for discussion on list, most implementations currently do not support strength 14:24:23 another clarification issue http://lists.w3.org/Archives/Public/public-device-apis/2013Jul/0050.html 14:24:47 action: fjh to create issues for Vibration questions 14:24:48 Created ACTION-653 - Create issues for vibration questions [on Frederick Hirsch - due 2013-09-11]. 14:25:00 Topic: Network Discovery 14:25:29 fjh: WD for publication in progress, Rich created draft, I had some comments, awaiting resolution before publication 14:25:35 dom has joined #dap 14:25:50 Web & TV IG review, http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0063.html 14:25:58 fjh: want to have published WD for review 14:26:28 fjh: reopened issue, difficult to resolve without everyone on call 14:26:36 Re-Opened ISSUE-130, see http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0053.html (discuss next week 4 Sept) 14:26:42 ISSUE-131 comment, http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0066.html (Tatsuya Igarashi ) 14:27:00 ISSUE-148? 14:27:00 ISSUE-148 -- NetworkService.name definition in 8.2.2.4 incoherent with definition in 7.1 (a human-readable title for the service) -- raised 14:27:00 http://www.w3.org/2009/dap/track/issues/148 14:27:48 jcdufound: regarding ISSUE-148, agreed between Jean-Claude and Cathy but Rich might have missed part of this discussion 14:28:05 … service type for SDP is not human-readable at all 14:28:32 … agree with Cathy that should change to something with friendly name of the device, believe Rich disagrees due to possible fingerprinting issue 14:28:48 … not a fingerprinting issue, since only exposed after authorization step 14:29:00 fjh: could still be fingerprinting despite authorization 14:30:07 jcdufound: should make this change once we have agreement with Rich 14:30:27 s/jcdufound/jcdufourd/ 14:30:32 ISSUE-130? 14:30:32 ISSUE-130 -- Enable variety of protocols (e.g. UPnP, Bonour) with protocol independent developer code -- open 14:30:32 http://www.w3.org/2009/dap/track/issues/130 14:31:07 Zakim, code? 14:31:07 the conference code is 3279 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), Josh_Soref 14:31:24 jcdufourd: need answer to my argument on the list from richt 14:31:48 … need to determine what is appropriate in the use case I presented, which would require large number of discovery requests 14:32:40 + +1.650.733.aadd 14:32:48 … I implemented current state of spec, others implemented services 14:32:52 Zakim, aadd is me 14:32:52 +Josh_Soref; got it 14:33:02 Zakim, mute me 14:33:02 Josh_Soref should now be muted 14:33:12 … they didn't want to use complete name each time, wanted one search regardless of the protocol 14:33:33 … didn't care about underlying discovery protocol 14:33:38 … so search with fragments 14:33:48 … requests from authors to simply API 14:34:10 … that is the main point to make it use simpler for authors 14:34:28 cathy: issue with doing that, web app might not be able to handle all the responses that come back 14:34:41 … different types of media renderers 14:34:59 … so get everything and filter on what you can use versus ask for what you can get 14:35:27 … I think it might make sense to ask what you can process 14:35:33 … I think rich agrees 14:35:42 igarashi has joined #dap 14:36:06 … for media renders can have same service name with different domain and protocol, so can get services you cannot handle 14:36:32 +??P3 14:36:49 fjh: can this be done with a wrapper, convenience function? 14:37:02 jcdufourd: tried this first with adaptation layer, but could not do it 14:37:14 … however could modify my implementation to allow for it 14:37:17 Zakim p3 is Igarashi 14:37:18 … with small change 14:37:26 zakim, p3 is Igarashi 14:37:26 sorry, fjh, I do not recognize a party named 'p3' 14:37:38 zakim, ??p3 is Igarashi 14:37:38 +Igarashi; got it 14:38:32 +Josh_Soref.a 14:38:37 fjh: why not offer both options 14:38:43 Zakim, drop Josh_Soref 14:38:43 Josh_Soref is being disconnected 14:38:45 -Josh_Soref 14:38:55 jcdufourd: ok with me 14:38:56 Zakim, who is on the call? 14:38:56 On the phone I see fjh, Clarke, anssik, jcdufourd, Cathy, Igarashi, Josh_Soref.a 14:39:08 cathy: first need to decide what we want 14:39:12 Zakim, drop Josh_Soref.a 14:39:12 Josh_Soref.a is being disconnected 14:39:13 -Josh_Soref.a 14:39:26 … if UA does not continuously monitor then problem 14:39:36 … UpNP does not allow wild card services 14:40:10 fjh: why didn't jclaude have this problem 14:40:32 cathy: monitors network, doesn't do search 14:40:32 fjh: issue search vs continues monitored 14:40:33 +Josh_Soref 14:41:42 s/UpNP/UPnP/ 14:43:17 fjh: wonder if we can allow support for implementation that can handle it but not for implementation that cannot 14:43:20 Zakim, mute me 14:43:20 Josh_Soref should now be muted 14:44:19 fjh: e.g. allow for usability where it makes sense and can be supported in underlying implementation but otherwise not 14:44:22 http://www.w3.org/2009/dap/track/issues/130 14:44:39 fjh: this way we do not create an artificial limitation where not needed 14:44:44 cathy: might be hard to spec 14:45:03 jcdufourd: we could have an exception if implementation does not support 14:45:08 s/support/support it/ 14:46:26 i'm not in favor of this 14:46:48 Zakim, unmute me 14:46:48 Josh_Soref should no longer be muted 14:47:18 fjh: is it possible or necessary to have a different wildcard api method so developer knows what to expect 14:47:37 fjh: summary, trying to enable usability where implementation supports it yet not get into difficulty where implementation does not 14:48:14 josh_soref: do not want same API used for both, will work in test environment but not in another case, will have interop problem 14:48:20 fjh: have two APIs 14:49:02 josh_soref: would only use wildcard api if you know you really want to, have fallback path 14:49:10 … so don't see this as a big problem for developers 14:49:35 jcdufourd: developer needs feature detection to see if can use wildcard api, otherwise fallback 14:49:49 josh_soref: one way is to not have function present if not implemented 14:50:53 Zakim, mute me 14:50:53 Josh_Soref should now be muted 14:51:45 fjh: i think the next step is to draft some specification text and use that to drive some more discussion 14:52:25 action: jcdufourd to propose text for Network Service Discovery to define wildcard API and feature detection 14:52:25 Error finding 'jcdufourd'. You can review and register nicknames at . 14:52:29 q? 14:53:37 action Dufourd to propose text for Network Service Discovery to define wildcard API and feature detection 14:53:37 Created ACTION-654 - Propose text for network service discovery to define wildcard api and feature detection [on Jean-Claude Dufourd - due 2013-09-11]. 14:53:48 RRSAgent, draft minutes 14:53:48 I have made the request to generate http://www.w3.org/2013/09/04-dap-minutes.html Josh_Soref 14:53:49 ISSUE-131? 14:53:49 ISSUE-131 -- Support UPnP device discovery by Device Type? -- open 14:53:49 http://www.w3.org/2009/dap/track/issues/131 14:54:12 s/action Dufourd/ACTION: Dufourd/ 14:54:14 RRSAgent, draft minutes 14:54:14 I have made the request to generate http://www.w3.org/2013/09/04-dap-minutes.html Josh_Soref 14:54:26 email message http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0002.html 14:55:34 cathy: general concern is about complexity added to spec 14:56:07 … if device string is UPnP specific so we lose generic aspec 14:56:23 igarashi: won't be too complicated, similar api 14:56:37 … device type is more important than service type 14:56:54 fjh: why more important 14:57:10 igarashi: based on UPnP architecture, first find by device then subtype 14:57:20 s/subtype/service type/ 14:57:58 fjh: seems to be another issue related to trying to make underlying discovery mechanism transparent 14:59:01 igarashi: cannot be agnostic to underlying discovery mechanism, not a goal 15:00:13 clarke: one goal was to be agnostic, approach is to use parameters to allow UA to deal with specifics, customization 15:00:13 Zakim, drop me 15:00:13 Josh_Soref is being disconnected 15:00:14 -Josh_Soref 15:00:41 +Josh_Soref 15:00:52 Zakim, mute me 15:00:52 Josh_Soref should now be muted 15:02:50 fjh: what is the minimal set of changes we can make to the spec, then we can discuss 15:02:58 cathy: it is in the issue text 15:03:03 fjh: not sure that is the minimum 15:03:08 -Clarke 15:03:15 igarashi: we can offer a proposal on the list 15:03:47 fjh: anything more on this topic? 15:04:04 Topic: HTML Media Capture 15:04:11 Update on testing, http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0065.html 15:04:19 thanks for this work to Intel 15:04:42 Topic: Teleconference schedule 15:04:51 Proposal: Changing meeting time from Wed to Thur (same time), https://lists.w3.org/Archives/Member/member-device-apis/2013Aug/0000.html 15:05:18 Thu is ok for me 15:06:35 earlier is better 15:06:46 conflict on Tue 15:07:32 fjh: I think I'll do a doodle poll 15:07:38 thursday is good for me, i've already moved my schedule around for it to fit 15:08:02 Zakim, drop me 15:08:02 Josh_Soref is being disconnected 15:08:03 -Josh_Soref 15:08:30 RESOLUTION: Recurring meeting moved to Thursdays, same time (10 am ET) 15:08:50 RESOLUTION: cancel 24 Oct, 28 Nov and 26 Dec 15:09:02 +Josh_Soref 15:09:04 s/I think I'll do a doodle poll// 15:09:21 Topic: Action Review 15:09:37 Zakim, mute me 15:09:37 Josh_Soref should now be muted 15:09:52 regrets for Thursday September 19 and September 26 :) 15:09:54 -jcdufourd 15:09:55 ... Sukkot 15:10:15 ACTION-621? 15:10:15 ACTION-621 -- Anssi Kostiainen to Create test cases for HTML Media Capture -- due 2013-03-13 -- PENDINGREVIEW 15:10:15 http://www.w3.org/2009/dap/track/actions/621 15:10:37 ACTION-621: resolved with http://lists.w3.org/Archives/Public/public-device-apis/2013Aug/0065.html 15:10:37 Notes added to ACTION-621 Create test cases for HTML Media Capture. 15:10:46 close ACTION-621 15:10:46 Closed ACTION-621. 15:10:59 ACTION-643? 15:10:59 ACTION-643 -- Anssi Kostiainen to Review Ambient Light and Proximity test cases by Sept -- due 2013-07-10 -- OPEN 15:10:59 http://www.w3.org/2009/dap/track/actions/643 15:11:12 anssik: done 15:11:17 close ACTION-643 15:11:17 Closed ACTION-643. 15:12:02 https://dvcs.w3.org/hg/dap/rev/916dbd5920d8 15:12:29 action: anssik to update test for light :https://dvcs.w3.org/hg/dap/rev/916dbd5920d8 15:12:29 Created ACTION-655 - Update test for light :https://dvcs.w3.org/hg/dap/rev/916dbd5920d8 [on Anssi Kostiainen - due 2013-09-11]. 15:12:32 https://dvcs.w3.org/hg/dap/rev/a6ad49819c41 15:12:54 action: anssik to update proximity test for https://dvcs.w3.org/hg/dap/rev/a6ad49819c41 15:12:54 Created ACTION-656 - Update proximity test for https://dvcs.w3.org/hg/dap/rev/a6ad49819c41 [on Anssi Kostiainen - due 2013-09-11]. 15:13:11 action-649? 15:13:11 action-649 -- Anssi Kostiainen to Review todo items associated with battery test cases -- due 2013-08-21 -- OPEN 15:13:11 http://www.w3.org/2009/dap/track/actions/649 15:13:24 fjh: todo items were removed 15:13:31 close ACTION-649 15:13:31 Closed ACTION-649. 15:13:48 action-621? 15:13:48 action-621 -- Anssi Kostiainen to Create test cases for HTML Media Capture -- due 2013-03-13 -- CLOSED 15:13:48 http://www.w3.org/2009/dap/track/actions/621 15:14:00 action-647? 15:14:00 action-647 -- Frederick Hirsch to Send cfc to progress light to cr, two week cfc -- due 2013-08-21 -- PENDINGREVIEW 15:14:00 http://www.w3.org/2009/dap/track/actions/647 15:14:06 close ACTION-647 15:14:06 Closed ACTION-647. 15:14:11 close ACTION-648 15:14:11 Closed ACTION-648. 15:14:25 anssik: may need updates for IDLharness tests for battery 15:15:10 action: anssik to revise battery tests for IDLharness, find QA person to help 15:15:11 Created ACTION-657 - Revise battery tests for idlharness, find qa person to help [on Anssi Kostiainen - due 2013-09-11]. 15:15:37 Topic: Issues Review 15:15:48 reviewed network service discovery during call 15:16:07 Topic: Other Business 15:16:14 New editors draft of getUserMedia, http://dev.w3.org/2011/webrtc/editor/archives/20130824/getusermedia.html 15:16:29 fjh: is there any relevant news from sys apps f2f relevant to dap 15:16:39 anssik: no dap relevant discussions 15:16:54 zakim, who is here? 15:16:54 On the phone I see fjh, anssik, Cathy, Igarashi, Josh_Soref (muted) 15:16:55 On IRC I see igarashi, dom, Cathy, Clarke, Zakim, RRSAgent, fjh, lgombos, richt, mounir, slightlyoff, Josh_Soref, anssik, trackbot 15:16:58 Zakim, unmute me 15:16:58 Josh_Soref should no longer be muted 15:17:46 SysApps asked to change their TPAC F2F dates 15:18:00 ... because they were initially avoiding DAP 15:18:08 ... but w/o DAP, they're now trying to avoid WebApps instead 15:18:13 ... it's unclear if they'll succeed 15:18:30 -anssik 15:18:31 -Cathy 15:18:36 Zakim, drop me 15:18:36 Josh_Soref is being disconnected 15:18:37 -Josh_Soref 15:18:51 Next week we will meet at new meeting day, Thursday, please remember to update your calendars. 15:18:59 Topic: Adjourn 15:19:01 -Igarashi 15:19:04 rrsagent, generate minutes 15:19:04 I have made the request to generate http://www.w3.org/2013/09/04-dap-minutes.html fjh 15:19:20 s/Josh_Soref.a/Josh_Soref/G 15:20:32 Present+ Josh_Soref, Igarashi_Tatsuya 15:21:38 s/hey, vibrating ads in iframes// 15:22:01 s/Zakim p3 is Igarashi// 15:22:47 i/cancel/and also/ 15:22:54 rrsagent, generate minutes 15:22:54 I have made the request to generate http://www.w3.org/2013/09/04-dap-minutes.html fjh 15:23:25 s/inserted/fjh/ 15:23:50 s/reviewed network service discovery /reviewed network service discovery issues/ 15:24:22 s/hey, vibrating ads in iframes....// 15:24:35 s|s/hey, vibrating ads in iframes//|| 15:24:38 rrsagent, generate minutes 15:24:38 I have made the request to generate http://www.w3.org/2013/09/04-dap-minutes.html fjh 15:25:20 s/issuesduring/issues during/ 15:25:31 rrsagent, generate minutes 15:25:31 I have made the request to generate http://www.w3.org/2013/09/04-dap-minutes.html fjh 15:25:46 -fjh 15:25:48 UW_DAP()10:00AM has ended 15:25:48 Attendees were fjh, +1.303.661.aaaa, Clarke, anssik, +33.6.77.84.aabb, jcdufourd, +1.781.362.aacc, Cathy, +1.650.733.aadd, Josh_Soref, Igarashi 15:54:58 lgombos has joined #dap 16:24:55 lgombos has joined #dap 16:43:52 lgombos has joined #dap 17:36:12 Zakim has left #dap