14:48:23 RRSAgent has joined #dap 14:48:23 logging to http://www.w3.org/2013/03/06-dap-irc 14:48:25 RRSAgent, make logs world 14:48:25 Zakim has joined #dap 14:48:27 Zakim, this will be DAP 14:48:27 ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 12 minutes 14:48:28 Meeting: Device APIs Working Group Teleconference 14:48:29 Date: 06 March 2013 14:48:44 Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2013Mar/0004.html 14:48:56 fjh has changed the topic to: dap 3279 ; agenda http://lists.w3.org/Archives/Public/public-device-apis/2013Mar/0004.html 14:49:12 Chair: Frederick_Hirsch 14:49:20 Present+ Frederick_Hirsch 14:50:46 Regrets+ Milan_Patel 14:54:51 Regrets+ Bryan_Sullivan 14:58:01 UW_DAP()10:00AM has now started 14:58:09 +[IPcaller] 14:58:16 zakim, [IPCaller] is me 14:58:16 +fjh; got it 14:59:21 +Josh_Soref 15:00:20 AnssiK has joined #dap 15:00:36 dcheng3 has joined #dap 15:00:38 zakim, mute josh_soref 15:00:38 Josh_Soref should now be muted 15:00:58 zakim, unmute josh_soref 15:00:59 Josh_Soref should no longer be muted 15:01:09 +??P11 15:01:15 zakim, ??P11 is me 15:01:15 +AnssiK; got it 15:01:21 Present+ Anssi_Kostiainen 15:02:25 +dcheng3 15:02:33 Present+ Diana_Cheng 15:02:52 + +1.858.750.aaaa 15:03:02 Cathy has joined #dap 15:03:03 +??P1 15:03:09 Zakim, ??P1 is me 15:03:09 +dom; got it 15:03:30 gmandyam has joined #dap 15:03:31 zakim, where is 858? 15:03:31 North American dialing code 1.858 is California 15:03:51 Scribe: Josh_Soref 15:03:52 Zakim, aaaa is gmandyam 15:03:52 +gmandyam; got it 15:04:34 +[IPcaller] 15:04:35 + +1.720.934.aabb 15:04:46 zakim, IPcaller is me 15:04:46 +richt; got it 15:04:53 Present+ Rich_Tibbett 15:04:56 zakim, where is 720? 15:04:56 North American dialing code 1.720 is Colorado 15:04:58 + +1.781.362.aacc 15:05:03 zakim, aacc is me 15:05:03 +Cathy; got it 15:05:05 Zakim, aabb is ClarkeSteven 15:05:05 +ClarkeSteven; got it 15:05:07 Present+ Cathy_Chan 15:05:53 Topic: Administrative 15:05:55 Clarke has joined #dap 15:06:16 Please use this link to update phone number mapping for zakim https://www.w3.org/1998/12/bridge/info/name.php3 15:06:41 Note: Next meeting is regular ET time; this makes it an hour earlier in Europe due to different in daylight savings time, see https://lists.w3.org/Archives/Member/member-device-apis/2013Mar/0001.html 15:07:16 Josh_Soref: i'm unlikely to call in on the 27th (PassoveR) 15:07:22 s/PassoveR/Passover/ 15:07:41 Topic: Minutes Approval 15:07:46 Approve minutes from 27 February 2013 15:07:46 http://lists.w3.org/Archives/Public/public-device-apis/2013Feb/att-0093/minutes-2013-02-27.html 15:07:47 Approve (revised) minutes from 20 February 2013 15:07:47 http://lists.w3.org/Archives/Public/public-device-apis/2013Feb/att-0098/minutes-2013-02-20.html 15:07:47 proposed RESOLUTION: Minutes from 20 Feb (revised) and 27 February 2013 are approved 15:07:56 RESOLUTION: Minutes from 20 Feb (revised) and 27 February 2013 are approved 15:08:08 Topic: F2F Planning 15:08:15 F2F Planning 15:08:15 Questionnaire completes 12 March, https://www.w3.org/2002/09/wbs/43696/2013-06-f2f/ 15:08:20 https://www.w3.org/2002/09/wbs/43696/2013-06-f2f/results 15:08:26 s/F2F Planning// 15:08:44 dtran has joined #dap 15:08:52 dcheng3: i still have both reserved 15:08:55 Present+ Dzung_Tran 15:09:09 Deadline for deciding on TPAC 2013? ( Nov 18-22 in Shenzhen - http://lists.w3.org/Archives/Public/public-device-apis/2013Jan/0095.html ) 15:09:23 fjh: i think we need to know way in advance to decide, because of Visas 15:09:40 Present+ Clarke_Stevens 15:10:02 dom: usually WGs are asked in March/April if they want to participate in TPAC 15:10:25 fjh: the June F2F was questionable, i think we can lock that down 15:10:38 ... if we don't progress on Web Intents, we might not need TPAC 15:10:48 dom: i don't know that there's a schedule on this question 15:10:55 ... but it would probably be asked in April 15:11:01 Zakim, mute me 15:11:01 Josh_Soref should now be muted 15:11:14 ... intending to meet isn't necessarily a strong commitment 15:11:18 ... we could cancel later 15:11:32 fjh: i mentioned that the Intents/Activity people were supposed to discuss shortly 15:11:43 ... i'd assume we'll know by the first week of April if we'd want to meet 15:12:03 fjh: i'm assuming Dusseldorf will work out well 15:12:10 topic: Network Service Discovery 15:12:15 Status on updates and publication of WD? 15:12:15 additional discussion: 15:12:15 http://lists.w3.org/Archives/Public/public-device-apis/2013Feb/0097.html 15:12:15 http://lists.w3.org/Archives/Public/public-device-apis/2013Mar/0003.html 15:13:22 richt: i'm traveling until Friday 15:13:25 ... back Monday 15:13:31 ... i have a backlog of changes 15:13:53 Cathy: re: XXX comments earlier 15:14:01 ... discovering UPnP device types v. Service types 15:14:01 s/XXX/Guisseppi/ 15:14:21 ... w/ device types, controllers typically are more interested in devices as opposed to services 15:14:31 ... but that would be a significant change to the UPnP mechanism in the spec 15:14:36 ... we need to consider implications 15:14:40 richt: i agree 15:14:58 ... Cathy, based on your experience, it might be a good idea for you to edit that in 15:15:03 Cathy: i'll work with you on that 15:15:15 richt: it'd be cool to get you involved in editing 15:15:24 fjh: the change offers simplifications/solves problems 15:15:40 ... Cathy, there's no need for you to get extra permissions, since we're using git 15:15:48 richt: we're using overview-src. 15:16:00 fjh: Cathy, do you need an action? 15:16:02 Cathy: no 15:16:10 richt: i'd prefer discussing on list before we make changes? 15:16:14 Cathy: sure 15:16:32 +1 to proposal on list before editing document, thanks Cathy for volunteering 15:17:06 fjh: Cathy will make progress on device-types/service-types 15:17:06 I think you captured it well, Josh_Soref. 15:17:11 ... and richt will work on the backlog 15:17:17 Topic: Contacts 15:17:20 Sys Apps draft - http://www.w3.org/2012/sysapps/drafts/contacts-manager-api/ 15:17:31 Pick Contacts Implementation status, original DAP Contacts implementation status? 15:17:39 fjh: marcos asked about implementation 15:17:45 Zakim, unmute me 15:17:45 Josh_Soref should no longer be muted 15:17:54 dom: afaik it was never implemented by anyone 15:18:08 Josh_Soref: it's implemented in the original form by Cordova 15:18:15 http://www.w3.org/2009/dap/wiki/ImplementationStatus#Contacts_API 15:18:19 fjh: we don't have any record of this 15:18:42 dom: we do, thanks to AnssiK 15:18:53 ok, thanks Dom for the pointer, and AnssiK for the wiki work 15:18:54 richt: which are we talking about? 15:19:00 richt: we have a mozilla implementation 15:19:04 dom: but that was an addon 15:19:34 [ Josh_Soref summarizes concerns about SysApps doc ] 15:20:13 Clarke has joined #dap 15:20:20 Josh_Soref: thanks fjh for getting them to rename their spec 15:20:48 fjh: i'm not sure if we can give feedback 15:20:56 Josh_Soref: some WGs will be asked to give feedback 15:21:04 ... but all WGs can give unsolicited feedback 15:21:10 Topic: HTML Media Capture 15:21:16 resolving LC comments, http://lists.w3.org/Archives/Public/public-device-apis/2013Mar/0002.html 15:21:39 fjh: i gave shepazu a 2 week time window this time, i should have done that last time 15:21:47 dom: yes, that's good 15:21:51 AnssiK: thanks fjh for pushing Tracker 15:22:00 ... i'll update the draft after we close shepazu's issues 15:22:08 ... i'll add a status section about Exit criteria 15:22:15 ... i'll give shepazu a couple of days 15:22:48 fjh: i think we made a mistake in our publications in not including Exit Criteria/At Risk in our documents 15:22:55 ... i don't think we need to update the status retroactively 15:23:05 ... we won't go back to CR, we'll just go to PR 15:23:12 AnssiK: you gave Mar 18 as the deadline to shepazu 15:23:16 ... i won't touch it before then 15:23:36 fjh: dom, can go to PR w/o having that section in the document, as it's documented elsewhere 15:23:41 dom: that shouldn't be a problem 15:23:45 Zakim, mute me 15:23:45 Josh_Soref should now be muted 15:23:55 dom: you're mixing Battery and Vibration 15:24:03 ... but AnssiK is talking about HTML Media Capture 15:24:29 i/mistake/Topic: Transition Request process/ 15:24:39 fjh: when we do transitions 15:24:45 ... we need to include status/at risk 15:24:52 ... we need to guess when we're done w/ LC comments 15:25:02 ... we need to add Exit Criteria to the Status section 15:25:15 ... and then having seen that, we publish as CR w/ transition request 15:25:25 ... i just wanted to confirm w/ dom that we don't need to republish 15:25:35 ... going forward, every doc should have status when we go to CR 15:25:41 dom: that's correct 15:26:02 dom: do we have any visibility on who is going to implement the spec? 15:26:14 ... i know chrome has an impl based on the old spec 15:26:19 ... i'm unclear about BlackBerry 15:26:27 ... i know Firefox does accept attribute as well 15:26:39 AnssiK: we have discussion in the html bug tracker 15:26:46 ... mounir doesn't say they will implement 15:26:56 ... but says that the spec is simple and efficient and they like it 15:27:02 ... Josh_Soref could comment on BlackBerry 15:27:15 Zakim, unmute me 15:27:15 Josh_Soref should no longer be muted 15:27:27 josh_soref: need to check with our implementers 15:28:03 dom: anyone know about Chromium/Opera ? 15:28:11 AnssiK: i think Tizen implements 15:28:13 Zakim, mute me 15:28:13 Josh_Soref should now be muted 15:28:21 fjh: i thought I saw that as well 15:28:32 http://www.w3.org/2009/dap/wiki/ImplementationStatus#HTML_Media_Capture 15:28:37 s/fjh/scribe 15:28:37 s/fjh/scribe 15:28:43 s/scribe:/fjh:/ 15:29:17 fjh: AnssiK, how hard would it be to indicate if it's an implementation 15:29:22 ... or just a note 15:29:26 AnssiK: yeah yeah 15:29:44 ... when i notice someone is mentioning it, i try to include 15:29:53 ... perhaps this should be more like caniuse.com 15:30:02 fjh: when i look at the list, i don't know if we're good to go 15:30:15 ... maybe you can add text to the wiki 15:30:35 AnssiK: i haven't always looked at the source code 15:30:37 q+ to ask about testing 15:30:45 ... and without the product in my hand, it's hard to know what is the level 15:30:52 ... i'll try to dig deeper 15:30:59 fjh: just trying to understand what the wiki is saying 15:31:11 AnssiK: the wiki is pointers to implementations that claim to support these specs 15:31:18 ... but levels and spec version is missing 15:31:57 fjh: so this isn't a list of vetted implementations 15:32:05 " 15:32:06 Implementations cited in this document may or may not implement the latest version of the related specification. " 15:32:06 ... it's a list where somewhere someone mentioned they might 15:32:36 "Implementations cited in this document may or may not implement the latest version of the related specification." 15:32:52 fjh: when you have more details, it'd be helpful if you add them to the wiki 15:33:10 AnssiK: Josh_Soref, what is the status of BlackBerry on Media Capture 15:33:15 Zakim, unmute me 15:33:15 Josh_Soref should no longer be muted 15:33:57 AnssiK: I received a BB10 device 15:34:51 q? 15:34:58 ack dom 15:34:58 dom, you wanted to ask about testing 15:35:05 Josh_Soref: i'm hoping to talk to devrel guys tomorrow 15:35:14 dom: for that spec, we probably want to do some testing 15:35:20 ... has anyone done any work on testing? 15:35:26 ... are there existing testcases? 15:35:52 AnssiK: i'm going to use the BlackBerry Dev Alpha device to see if it has anything 15:36:05 ... i have the Vibration test suite to do 15:36:12 ... dom, do you have ideas for the interactive tests? 15:36:21 ... how to craft interactive tests for these specs 15:36:29 ... there are implementation details that you're unable to test 15:36:35 dom: i see two kinds of tests 15:36:37 ... IDL level 15:36:43 ... parsing/handling 15:36:50 ... interaction between Accept and Capture 15:36:56 ... and then there's an interactive part 15:37:03 ... i'd simply say in the test itself 15:37:13 ... when you press the button, you should be offered to get a picture from your camera 15:37:18 ... and then maybe testing the file type 15:37:33 AnssiK: thanks, that matches what i was thinking about 15:37:49 ... the idl is simple, so idlharness or manual tests 15:37:56 ... and for interactive, something like you described 15:38:21 dom: i think separate actions for separate test suites is more actionable 15:38:27 action: anssik to create test cases for battery and vibration 15:38:27 Created ACTION-620 - Create test cases for battery and vibration [on Anssi Kostiainen - due 2013-03-13]. 15:38:31 AnssiK: let's do another action 15:39:06 close ACTION-620 15:39:06 Closed ACTION-620 Create test cases for battery and vibration. 15:39:32 ACTION: AnssiK to create test cases for HTML Media Capture 15:39:33 Created ACTION-621 - Create test cases for HTML Media Capture [on Anssi Kostiainen - due 2013-03-13]. 15:40:07 dom: the HTML WG is making a change to their test suite 15:40:13 ... giving up the submitted/approved structure 15:40:28 ... have we discussed migrating this group's tests? 15:40:34 fjh: i was thinking of wait-and-see 15:40:42 dom: i think it's working reasonably well for them 15:41:03 Josh_Soref: vibration is stuck because it's submitted but not accepted 15:41:19 would like to see focus on actual work rather than logistics unless it is low effort to make the changes 15:41:25 ... AnssiK now has a bb10 with it 15:41:36 AnssiK: i'm testing it, but it seems to indeed be implemented 15:41:38 ... it is buzzing 15:41:43 ... good work guys 15:42:20 i/is stuck/Topic: Vibration test progress/ 15:42:36 Topic: OMA Liaison 15:42:41 ACTION-613? 15:42:41 ACTION-613 -- Frederick Hirsch to draft proposed OMA liaison response -- due 2013-02-13 -- OPEN 15:42:41 http://www.w3.org/2009/dap/track/actions/613 15:42:59 fjh: dom said it was inappropriate for me to close w/o a comment 15:43:04 ... i'll draft a response 15:43:05 Regarding the HTML Media Capture, there is a problem regarding the ability for the user to opt-out from the capture device and use its stored pictures instead. I believe that should be allowed but I'm not sure how much we should make this a requirement for specifications. 15:43:31 Josh_Soref: mounir: i thought that we designed the spec to specifically allow for that! 15:43:37 s/said it was inappropriate for me to close w/o a comment/ reminded me that it might be appropriate to respond formally/ 15:43:50 Topic: Privacy 15:43:56 PING feedback : http://lists.w3.org/Archives/Public/public-device-apis/2013Feb/0095.html 15:44:17 Possible updates to Proximity and Ambient Light Event specs 15:44:22 fjh: i believe this message captures their feedback accurately 15:44:43 ... specs aren't used in isolation 15:44:48 ... npdoty offered to help 15:44:58 Clarke has joined #dap 15:45:01 ... The ability to fingerprint based on timing might not be the easiest way 15:45:54 Josh_Soref: actually, if the user must have to use a capture device, that could work too (i guess) but a common behaviour would be better. I'm not sure what is the specification wording regarding this. 15:46:14 Josh_Soref: there is another advantage re privacy timings 15:46:25 ... if an application is written to a single implementation 15:46:33 ... it could break if another implementation has different timings 15:46:39 ... if the sepc encouraged a single timing behavior 15:46:45 s/sepc/spec/ 15:47:06 ... then an application could be less likely to break when it interacts with a different implementation 15:47:26 fjh: in GeoLocation there's an idea of lying 15:47:37 ... that might also apply to these other apis 15:47:45 Josh_Soref: it should apply to these apis as well 15:47:59 ... capture being an example 15:48:18 ... -- letting the user select an already available object 15:48:26 fjh: the other concept from GeoLocation is Fuzzing 15:48:30 ... giving a less accurate value 15:48:38 ... we did that with ambient light 15:49:45 in HTML Media Capture you could opt out by defaulting to file picker instead of using camera device 15:50:08 "When the http://dev.w3.org/2009/dap/camera/#dfn-capture-1 attribute is specified, the http://dev.w3.org/2009/dap/camera/#dfn-user-agent should invoke a file picker of the specific http://dev.w3.org/2009/dap/camera/#dfn-capture-control-type." 15:50:35 "When the capture attribute is specified, the user agent should invoke a file picker of the specific capture control type." 15:50:36 s|"When the http://dev.w3.org/2009/dap/camera/#dfn-capture-1 attribute is specified, the http://dev.w3.org/2009/dap/camera/#dfn-user-agent should invoke a file picker of the specific http://dev.w3.org/2009/dap/camera/#dfn-capture-control-type."|| 15:50:40 -richt 15:50:52 s/should/SHOULD/ 15:51:06 Josh_Soref: note that it's a "File Picker" of a "Capture Type" 15:51:28 richt has joined #dap 15:51:31 ... certainly BlackBerry systems where the file picker gives access to both Gallery and Camera/Mic does this :) 15:51:49 fjh: we received Feedback from PING about Proximity/Ambient light 15:51:56 ... with specific approaches we should take 15:52:08 ... should we try to take a pass through the spec to see if we can incorporate that before moving forward? 15:53:13 "there should be an indication to the user when the sensors are used" 15:53:18 Josh_Soref: Ambient could have been designed as a Media Query 15:53:27 ... but you can certainly detect Media Query states 15:53:34 "disable sharing proximity information" 15:54:18 Josh_Soref: browsers have spent 20 years trying to design the lock icon 15:54:34 ... and some low level specs have UI requirements which were *never* implemented 15:54:47 dom: we generally avoid putting normative text in about UI 15:54:56 fjh: but we put in consideration sections? 15:55:11 dom: do we put an indication in to suggest to the user that it's in use? 15:55:30 dom: we claim that these are generally QOI 15:55:35 s/QOI/QoI/ 15:56:41 Josh_Soref: we could point to implementations which have done something for indications 15:56:54 I suggest we should take the PING input and see what changes we should make to the specs, such as the privacy considerations 15:56:56 ... e.g. the current Chrome (Canary) shows you what's allowed/has been used if you click the Lock Icon 15:57:09 also need to follow up with nick on general considerations 15:57:25 action: fjh to follow up on concrete actions based on PING input 15:57:25 Created ACTION-622 - Follow up on concrete actions based on PING input [on Frederick Hirsch - due 2013-03-13]. 15:57:41 - > http://www.digitallanding.com/wp-content/uploads/2012/12/Chrome-Permissions.jpg Chrome permissions 15:57:43 -> http://www.digitallanding.com/wp-content/uploads/2012/12/Chrome-Permissions.jpg Chrome permissions 15:57:50 s|- > http://www.digitallanding.com/wp-content/uploads/2012/12/Chrome-Permissions.jpg Chrome permissions|| 15:58:11 RRSAgent, draft minutes 15:58:11 I have made the request to generate http://www.w3.org/2013/03/06-dap-minutes.html Josh_Soref 15:58:14 RRSAgent, make logs public 15:58:22 AnssiK: i think we should be concrete 15:58:37 fjh: i'd appreciate if people could respond to the message on the list 15:59:16 -ClarkeSteven 15:59:19 Topic: Action Review 16:00:11 ACTION-617: https://www.w3.org/2002/09/wbs/43696/2013-06-f2f/ 16:00:11 Notes added to ACTION-617 Set up f2f questionnaire. 16:00:15 close ACTION-617 16:00:15 Closed ACTION-617 Set up f2f questionnaire. 16:00:32 ACTION-618: http://lists.w3.org/Archives/Public/public-device-apis/2013Mar/0001.html 16:00:32 Notes added to ACTION-618 Provide sotd text for battery, vibration status updates. 16:00:39 -gmandyam 16:00:42 close ACTION-618 16:00:42 Closed ACTION-618 Provide sotd text for battery, vibration status updates. 16:00:44 -dom 16:00:47 -Cathy 16:01:17 ACTION-619: http://lists.w3.org/Archives/Public/public-device-apis/2013Mar/0002.html 16:01:17 Notes added to ACTION-619 Follow up with Doug re closing HTML Media Capture LC Comments. 16:01:30 close ACTION-619 16:01:30 Closed ACTION-619 Follow up with Doug re closing HTML Media Capture LC Comments. 16:01:37 Topic: Other Business 16:01:38 no e 16:01:42 s/no e/none 16:01:46 Topic: Adjourn 16:01:52 trackbot, end meeting 16:01:52 Zakim, list attendees 16:01:52 As of this point the attendees have been fjh, Josh_Soref, AnssiK, dcheng3, +1.858.750.aaaa, dom, gmandyam, +1.720.934.aabb, richt, +1.781.362.aacc, Cathy, ClarkeSteven 16:01:58 -dcheng3 16:02:00 RRSAgent, please draft minutes 16:02:00 I have made the request to generate http://www.w3.org/2013/03/06-dap-minutes.html trackbot 16:02:01 RRSAgent, bye 16:02:01 I see 3 open action items saved in http://www.w3.org/2013/03/06-dap-actions.rdf : 16:02:01 ACTION: anssik to create test cases for battery and vibration [1] 16:02:01 recorded in http://www.w3.org/2013/03/06-dap-irc#T15-38-27 16:02:01 ACTION: AnssiK to create test cases for HTML Media Capture [2] 16:02:01 recorded in http://www.w3.org/2013/03/06-dap-irc#T15-39-32 16:02:01 ACTION: fjh to follow up on concrete actions based on PING input [3] 16:02:01 recorded in http://www.w3.org/2013/03/06-dap-irc#T15-57-25 16:02:05 zakim, who is here? 16:02:07 On the phone I see fjh, Josh_Soref, AnssiK 16:02:07 On IRC I see Cathy, dcheng3, AnssiK, Zakim, RRSAgent, fjh, slightlyoff, dom, tobie, lgombos, Josh_Soref, mounir, trackbot