13:44:15 RRSAgent has joined #dap 13:44:15 logging to http://www.w3.org/2011/06/01-dap-irc 13:44:17 RRSAgent, make logs world 13:44:17 Zakim has joined #dap 13:44:19 Zakim, this will be DAP 13:44:19 ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 16 minutes 13:44:20 Meeting: Device APIs and Policy Working Group Teleconference 13:44:20 Date: 01 June 2011 13:44:45 Regrets+ Claes_Nilsson 13:45:34 Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2011May/0069.html 13:46:19 Chair: Robin_Berjon, Frederick_Hirsch 13:46:23 Present+ Robin_Berjon, Frederick_Hirsch 13:49:42 darobin has joined #dap 13:50:52 DKA has joined #dap 13:52:42 Regrets+ Niklas_Widell 13:53:44 zakim, code? 13:53:44 the conference code is 3279 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), fjh 13:56:09 UW_DAP()10:00AM has now started 13:56:16 + +1.425.214.aaaa 13:57:15 +??P2 13:57:55 zakim, ?? is me 13:57:55 +fjh; got it 13:58:33 zakim, aaaa is bryan 13:58:33 +bryan; got it 13:59:33 Topic: Administrative 14:00:02 lgombos has joined #dap 14:00:39 +DKA 14:00:47 Kyungtak has joined #dap 14:00:54 zakim, mute me 14:00:54 DKA should now be muted 14:00:57 +Dom 14:00:57 +Laszlo_Gombos 14:00:59 zakim, unmute me 14:00:59 DKA should no longer be muted 14:01:05 zakim, mute me 14:01:05 DKA should now be muted 14:01:14 Present+ Dominique_Hazael-Massieux 14:01:15 +??P7 14:01:24 Zakim, ??P7 is me 14:01:24 +darobin; got it 14:01:24 Present+ Laszlo_Gombos 14:01:38 Present+ Daniel_Appelquist 14:01:42 AnssiK has joined #dap 14:01:47 Present+ Kyung-Tak_Lee 14:01:53 +??P15 14:02:05 zakim, ??P15 is me 14:02:05 +AnssiK; got it 14:02:14 Present+ Anssi_Kostiainen 14:02:31 zakim, who's on the call 14:02:31 I don't understand 'who's on the call', AnssiK 14:02:46 zakim, who is here? 14:02:46 On the phone I see bryan, fjh, DKA (muted), Dom, Laszlo_Gombos, darobin, AnssiK 14:02:46 zakim, who's here 14:02:49 On IRC I see AnssiK, Kyungtak, lgombos, DKA, darobin, Zakim, RRSAgent, fjh_, fjh, richt, ilkka, ingmar, wmaslowski, dom, trackbot 14:02:51 AnssiK, you need to end that query with '?' 14:03:40 + +82.31.27.9.aabb 14:04:09 Dzung_Tran has joined #dap 14:04:11 zakim, aabb is wonsuk 14:04:11 +wonsuk; got it 14:04:14 Present+ Dzung_Tran 14:04:33 Zakim, aabb is wonsuk_lee 14:04:33 sorry, dom, I do not recognize a party named 'aabb' 14:04:34 Cathy has joined #dap 14:04:38 ScribeNick: AnssiK 14:04:48 RESOLUTION: Anssi rocks 14:04:49 Present+ Wonsuk_Lee 14:04:52 +1 14:04:52 zakim, wonsuk is wonsuk_lee 14:04:52 +wonsuk_lee; got it 14:04:53 +richt 14:05:00 zakim, who is here? 14:05:00 On the phone I see bryan, fjh, DKA (muted), Dom, Laszlo_Gombos, darobin, AnssiK, wonsuk_lee, richt 14:05:01 Present+ Rich_Tibbett 14:05:02 On IRC I see Cathy, Dzung_Tran, AnssiK, Kyungtak, lgombos, DKA, darobin, Zakim, RRSAgent, fjh_, fjh, richt, ilkka, ingmar, wmaslowski, dom, trackbot 14:05:17 Present+ Cathy_Chan 14:05:24 TOPIC: Welcome, agenda review, scribe selection, announcements 14:05:25 wonsuk has joined #dap 14:05:27 19-21 July F2F logistics, http://lists.w3.org/Archives/Member/member-device-apis/2011Apr/0000.html 14:05:34 fjh: F2F is in July, please register 14:05:34 Please register - http://www.w3.org/2002/09/wbs/43696/paris-2011/ 14:05:46 Chartering 14:05:46 see http://www.w3.org/2010/11/DeviceAPICharter.html 14:05:46 http://lists.w3.org/Archives/Member/w3c-ac-members/2011AprJun/0041.html 14:05:48 ... chartering is on its way 14:05:55 ... AC reps are looking at it as we speak 14:05:58 DAP and Web RTC 14:05:58 http://lists.w3.org/Archives/Public/public-device-apis/2011May/0059.html 14:06:05 ... WebRTC and DAP chairs met recently 14:06:29 Dom: WebRTC will be dealing with the media streaming, DAP will handle the media recording 14:06:35 +Cathy_Chan 14:06:39 ... we could get inspiration from them 14:06:43 2nd Last Call DOM Events, end 28 June 14:06:43 http://lists.w3.org/Archives/Public/public-device-apis/2011May/0055.html 14:06:45 fjh: DOM3 Events LC 14:06:53 ... any other announcements? 14:07:07 + 14:07:29 darobin: web perf WG is about to release couple of things 14:07:43 TOPIC: Minutes approval 14:07:47 http://lists.w3.org/Archives/Public/public-device-apis/2011May/att-0048/minutes-2011-05-25.html 14:08:02 RESOLUTION: Minutes from 25 May 2011 are approved 14:08:08 TOPIC: TAG minimization draft 14:08:18 zakim, unmute me 14:08:18 DKA should no longer be muted 14:08:27 fjh: I sent some comments 14:08:34 http://lists.w3.org/Archives/Public/public-device-apis/2011May/0004.html 14:08:46 Zakim, mute me 14:08:46 Dom should now be muted 14:08:50 comments, http://lists.w3.org/Archives/Public/public-device-apis/2011May/0070.html 14:08:54 DKA: thanks for inviting me to call in 14:09:27 http://www.w3.org/2001/tag/doc/APIMinimization.html 14:09:56 ... I discussed the draft with people in this group and in Geolocation WG and WebApps WG as well last your at the TPAC meeting 14:10:16 ... Web App Data Minimization is a working title 14:10:23 ... it's about data minimization really 14:10:29 "Data minimization in Web APIs" 14:10:44 ... the topic spun off of the privacy workshop held in London last year 14:11:24 ... we were trying to figure out what TAG could do to help in this space 14:11:50 ... another WS in Boston was held between IAD? and W3C where we pondered the Privacy by Design concept 14:12:10 ... it is more concrete concept if applied to (web) services 14:12:44 ... I took an action to talk about the general principles, and how it applied to API design on the Web 14:13:35 ... it is one concrete essential thing we can do, from TAG perspective 14:14:00 ... any feedback is useful, schedule: will deliver the next draft by the end of this week 14:14:14 ... will discuss the draft at the TAG F2F next week in Boston 14:14:29 ... any feedback sent asap will likely make it into the TAG F2F meeting 14:14:48 ... that's all folks 14:15:11 q+ 14:15:13 fjh: promoting best practices like this is a good idea 14:15:20 ack me 14:15:21 ... any comments? 14:15:22 ack dom 14:15:49 DKA: the doc will become a TAG finding 14:15:54 ... or a TAG Note 14:16:03 ... preference: TAG finding 14:16:10 ... personal preference 14:16:25 +1 to promoting data minimization within W3C and broader community 14:16:25 ... would like it to be a checklist to check against 14:16:54 q+ to explain things a bit 14:17:04 Zakim, mute me 14:17:04 Dom should now be muted 14:17:28 fjh: I think creating something around data minimization is useful, but creating a bigger framework would easily get complex 14:17:45 DKA: agreed, will start small and let it grow organically 14:17:50 ack me 14:17:50 darobin, you wanted to explain things a bit 14:18:21 DKA: diff TAG Note TAG Finding 14:18:44 ... I think it could be said that TAG Finding represents something that's part of the Web Arch 14:18:54 ... more substantial than TAG Notes 14:19:03 ... like WG Notes 14:19:30 ... TAG FIndings are not RECs 14:19:47 ack me 14:20:30 Dom: one of the open questions for me is, which APIs would be affected by this 14:20:49 ... would this apply to Geoloc WG deliverables 14:21:01 ... data from sensors vs. user data 14:21:21 DKA: cannot diff between data from sensors v. private data 14:21:33 reminder of fingerprinting based on sensor and other information makes most information private in that sense 14:21:42 ... any data that may interact with UAs 14:21:58 Dom: how this principle would apply to accel or battery, for example 14:22:20 DKA: accel case: the app should only request info it needs 14:22:27 s/accel/accelerometer/ 14:22:32 ... the API should not return all the information it has 14:22:42 s/accel/accelerometer/ 14:22:47 -> http://dev.w3.org/geo/api/spec-source-orientation.html Device Orientation spec 14:23:02 Dong-Young_Lee has joined #dap 14:23:06 ... the could be sensitive info in that info, e.g. your accelerating might imply you are in a train 14:23:18 s/the// 14:23:25 s/in that info// 14:23:30 Present+ Dong-Young_Lee 14:23:40 ... also data related to health info is very sensitive 14:23:45 The major issue is combining information, e.g. sensor information along with other information, impact on insurance tec 14:23:50 s/tec/etc 14:23:50 ... e.g. blood pressure sensors 14:24:04 [I think that the core issue is to think before you spec] 14:24:26 ... more and more sensitive sensors are added, so it is good to get these principles nailed down soon 14:24:34 +??P5 14:24:53 darobin: battery status obviously is not privacy sensitive, but each sensor would need to be evaluated against these principles 14:24:54 zakim, +??P5 is me 14:24:54 sorry, Dong-Young_Lee, I do not recognize a party named '+??P5' 14:25:08 Zakim, ??P5 is Dong-Young_Lee 14:25:08 +Dong-Young_Lee; got it 14:25:10 darobin: any other questions for Dan? 14:25:16 zakim, ?? is dong-young_lee 14:25:16 sorry, fjh, I do not recognize a party named '??' 14:25:41 zakim, ??P5 is me 14:25:41 I already had ??P5 as Dong-Young_Lee, Dong-Young_Lee 14:26:18 darobin: should other WGs be informed of the work? 14:26:49 DKA: e.g. Geolocation WG has privacy on their radar 14:27:19 darobin: mention geopriv and Geoloc WG freaks out 14:27:48 DKA: thanks for your feedback DAP WG! 14:27:52 -DKA 14:28:04 TOPIC: Contacts 14:28:20 Comments before Last Call, http://lists.w3.org/Archives/Public/public-device-apis/2011May/0061.html (Suresh) 14:29:02 (my comment on using URLs for ContactField.value is still pending I think too) 14:29:13 richt: Suresh's comments haven't yet been baked in, other comments are in 14:30:06 suresh suggests propose to drop the fields 'revision', 'gender' and 'timezone' 14:30:13 darobin: going though fields to be removed, see the discussion on the ML 14:31:07 darobin: Suresh feedback: normative language in non-normative section 14:31:15 proposed RESOLUTION: remove fields revision, gender and timezone from contact interface 14:31:19 richt: will fix 14:31:31 RESOLUTION: remove fields revision, gender and timezone from contact interface 14:32:13 richt: much based on vCard and PoCo, not so for CAB 14:32:46 an informative reference is not an endorsement is it 14:32:47 to be clear, it's not a place to endorse other specifications. 14:32:58 darobin: PoCo needs to be in there, some fields reference it 14:33:19 ack me 14:33:20 fjh: having a reference is not an endorsement, harmless to have extra references 14:33:33 "All properties included in this interface have a corresponding 14:33:35 definition in [POCO-SCHEMA], [IETF vCard], and [OMA CAB], thereby 14:33:36 allowing the API to be supported across implementations supporting these 14:33:38 various contact formats." 14:34:11 s/ is it// 14:34:14 Dom: reference needs to be bound to the actual text to be meaninful in the context of a spec 14:34:21 will add Suresh's proposed text to the spec 14:34:33 darobin: Suresh's feedback processes 14:34:54 will drop updatedSince as agreed on mailing list. 14:34:58 s/processes/processed/ 14:35:07 ContactField.value as URLs? 14:35:08 rrsagent, generate minutes 14:35:08 I have made the request to generate http://www.w3.org/2011/06/01-dap-minutes.html fjh 14:36:17 Dom: value prop on a contact fields should be URLs instead of free-form DOMString 14:36:25 ... UA has to normalize the data 14:36:50 s/prop/props/ 14:37:00 s/a contact/contact/ 14:37:28 richt: would like to keep it as a DOMString, based on implementation experiences so far 14:37:54 dom: having a field which may be free-form or and URL does not help IOP 14:38:03 s/and/an/ 14:38:18 dom: maybe we should have both .url and .value properties 14:38:36 darobin: looking at the tel: URI scheme 14:38:40 bryan has joined #dap 14:38:49 ... to find out if it could work 14:38:59 1-800-HELLO 14:39:01 present+ bryan_sullivan 14:39:10 ... e.g. people who might enter phone numbers like above 14:40:16 dom: a picture can be either an URL reference or a base64-encoded data: URI 14:41:12 ... if you *can* use URLs then you do use them 14:41:22 darobin: saving back to vCard? 14:41:26 ... how does that work out? 14:41:49 dom: we don't have functions for creating contacts 14:42:02 darobin: there's no spec to reference for normalization 14:42:03 uri = tel:1234;phone-context=munich.example.com 14:43:00 dom: this is a case we need implementors' feedback 14:43:07 ... but this would be the Right Thing to do 14:43:16 DKA has joined #dap 14:43:35 [are we turning email into mailto: as well?] 14:43:43 richt: personal opinion is this may add too much burden on implementers 14:43:56 ... and complexity 14:44:08 ... saving back case is an issue too 14:44:13 [I see the value in having URIs handy, but it seems like convenience that can be done in script and could be added transparently in v2] 14:44:20 ... cannot put restrictions on the fields 14:44:43 ... at this stage the non-URL way is preferred 14:45:18 dom: picture field can take an URL of the pic, or a base64'd version of it as a data: URI 14:45:23 darobin: I'm fine with pictures 14:45:37 current = "a URL to an image resource or base64 encoded string of the image data." 14:45:40 richt: for pictures makes sense, absolutely 14:45:44 emails? 14:45:50 new = "a URL to an image resource which may be a data: URL." 14:45:55 ... need to handle this on case by case basis 14:45:56 and urls? 14:46:26 ... but for tel it is harder 14:47:22 dom: not sure the proposed new URL JS object is doing normalization as discussed above 14:47:47 richt: two ways: keep DOMString 14:48:01 ... base the field on URL, which enforces URL behaviour 14:48:31 we can base the field on a URL constructor or enforce it on DOMStrings. Both have different implications. 14:49:31 -> http://lists.w3.org/Archives/Public/public-device-apis/2011May/0045.html feedback on contactfield as urls 14:50:01 darobin: return this to the list 14:50:16 ... no decision time now it seems 14:50:33 -Dom 14:50:59 I was about to say: we're already relying on HTML5, Web IDL, which have schedule problems of their own 14:51:09 Agreed upon = 1) dropping gender, timezone, revision; 2) AppB all informative; 3) add Suresh's sentence with OMA CAB; 4) remove updatedSince 14:51:19 +Dom 14:51:21 richt: pending for a proposal for backwards compatibility? 14:51:26 ... delay publishing? 14:51:51 darobin: the URL "spec" is not scheduled for publishing? 14:52:04 ACTION: Dom to figure status of URL object in JavaScript in Web Apps 14:52:04 Created ACTION-402 - Figure status of URL object in JavaScript in Web Apps [on Dominique Hazaƫl-Massieux - due 2011-06-08]. 14:52:13 ... thought WebApps wanted to take it but they couldn't (too many deliverables already) 14:53:26 darobin: TODOs: resolve URL thing, once done LC ready 14:53:43 richt: good for me 14:53:46 :) 14:54:02 TOPIC: Battery Status 14:54:04 Editors draft updated, http://lists.w3.org/Archives/Public/public-device-apis/2011May/0057.html (Anssi) 14:54:05 http://lists.w3.org/Archives/Public/public-device-apis/2011May/0058.html 14:54:05 coordination, http://lists.w3.org/Archives/Public/public-device-apis/2011May/0052.html (Robin) 14:54:27 [that coordination link belongs to Contacts actually!] 14:54:32 AnssiK: I have baked in all the changes 14:54:39 http://lists.w3.org/Archives/Public/public-device-apis/2011May/0057.html 14:54:57 AnssiK: if you read this and dislike something, please simply send me email 14:55:03 s/coordination.*// 14:55:05 http://lists.w3.org/Archives/Public/public-device-apis/2011May/0058.html 14:55:12 s/[that coordination.*// 14:55:20 rrsagent, generate minutes 14:55:20 I have made the request to generate http://www.w3.org/2011/06/01-dap-minutes.html fjh 14:55:37 robin: new WD? 14:55:41 AnssiK: agreed 14:55:59 +1 to updated wd 14:56:23 +1 for republish updated wd 14:57:03 -Cathy_Chan 14:57:11 ISSUE: Should (some of the) ContactField objects use URLs rather than free-form strings? 14:57:11 Created ISSUE-111 - Should (some of the) ContactField objects use URLs rather than free-form strings? ; please complete additional details at http://www.w3.org/2009/dap/track/issues/111/edit . 14:57:14 AnssiK: need to define how events are triggered in such a way that they are testable; express [???] in IDL; and define "immediately" properly 14:57:43 RESOLUTION: New WD heartbeat for Battery, and start preparing for LC afterwards 14:57:55 ACTION: publish Battery heartbeat 14:57:55 Sorry, couldn't find user - publish 14:57:56 s/???/onbatterystatus event handler/ 14:58:00 ACTION: Robin to publish Battery heartbeat 14:58:00 Created ACTION-403 - Publish Battery heartbeat [on Robin Berjon - due 2011-06-08]. 14:58:16 http://dev.w3.org/2009/dap/system-info/battery-status.html 14:58:21 there's the latest ED 14:58:30 coordination email to Geo: http://lists.w3.org/Archives/Public/public-device-apis/2011May/0052.html 14:58:57 darobin: not a blocker for LC 14:59:07 TOPIC: Network Information 14:59:30 darobin: we could publish it right away 14:59:40 ... would like people to take a look at it and send their +1s 14:59:53 +1 on publishing 15:00:06 darobin: if no issues, we'll go to FPWD 15:00:08 http://lists.w3.org/Archives/Public/public-device-apis/2011May/0066.html 15:00:18 +1 to publish 15:00:26 dom: only issue, privacy sensitive network name 15:00:36 No SSID 15:00:38 darobin: should we keep it or remove it? 15:00:55 +1 to Dom, removing the privacy sensitive item 15:01:07 dom: prefer to remove networkName 15:01:13 ACTION: Robin to remove networkName from Netinfo 15:01:14 Created ACTION-404 - Remove networkName from Netinfo [on Robin Berjon - due 2011-06-08]. 15:01:17 darobin: happy to remove it 15:01:24 -Dom 15:01:30 ACTION: Robin to move NetInfo to FPWD 15:01:30 Created ACTION-405 - Move NetInfo to FPWD [on Robin Berjon - due 2011-06-08]. 15:01:38 TOPIC: Feature Request Access Containers 15:01:44 http://lists.w3.org/Archives/Public/public-device-apis/2011May/0069.html 15:01:48 darobin: heads up 15:01:52 ... no feedback so far 15:01:57 q+ 15:02:03 ack AnssiK 15:02:08 action: fjh to review feature request access containers 15:02:08 Created ACTION-406 - Review feature request access containers [on Frederick Hirsch - due 2011-06-08]. 15:02:45 AnssiK: any discussion on moz labs? 15:02:52 http://lists.w3.org/Archives/Public/public-web-security/2011May/0029.html 15:02:57 darobin: not much in public, some private 15:03:13 ... also in web security 15:03:46 TOPIC: HTML Media Capture 15:03:59 http://lists.w3.org/Archives/Public/public-device-apis/2011May/0064.html (Dom) 15:03:59 http://lists.w3.org/Archives/Public/public-device-apis/2011May/0065.html (Wonsuk) 15:04:05 darobin: discussed in HTML WG 15:04:14 ... also feedback / questions from Wonsuk 15:04:53 s/also in/also discussed in/ 15:05:31 Wonsuk: the scope of the capture would need to be clarified 15:05:35 ... will come back later 15:05:42 TOPIC: Other 15:05:54 darobin: any other specs? 15:06:10 -Laszlo_Gombos 15:06:17 Topic: Adjourn 15:06:26 rrsagent, generate minutes 15:06:26 I have made the request to generate http://www.w3.org/2011/06/01-dap-minutes.html fjh 15:06:29 -bryan 15:06:31 -darobin 15:06:35 -richt 15:06:41 -fjh 15:06:43 RRSAgent: stop