13:48:17 RRSAgent has joined #dap 13:48:17 logging to http://www.w3.org/2010/09/29-dap-irc 13:48:19 RRSAgent, make logs world 13:48:19 Zakim has joined #dap 13:48:21 Zakim, this will be DAP 13:48:21 ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 12 minutes 13:48:22 Meeting: Device APIs and Policy Working Group Teleconference 13:48:22 Date: 29 September 2010 13:48:47 Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/0138.html 13:53:19 bryan has joined #dap 13:53:53 Present+ Bryan_Sullivan 13:55:30 Present+ Mohammed_Dadas 13:58:52 Suresh has joined #dap 13:59:04 Present+ Suresh_Chitturi 13:59:13 Regrets+ Claes_Nilsson, Marco_Marengo 13:59:23 Chair: Robin_Berjon, Frederick_Hirsch 13:59:32 Present+ Robin_Berjon, Frederick_Hirsch 14:00:10 Regrets+ Thomas_Roessler 14:00:17 UW_DAP()10:00AM has now started 14:00:24 +Bryan 14:00:57 +darobin 14:01:12 +Roger 14:01:27 +dom 14:01:32 enewland has joined #dap 14:01:38 Present+ Dominique_Hazael-Massieux 14:01:41 zakim, who is here? 14:01:41 On the phone I see Bryan, darobin, Roger, dom 14:01:42 On IRC I see enewland, Suresh, bryan, Zakim, RRSAgent, fjh, Mohammed, darobin, Marcos, arve, wmaslowski, lgombos, shepazu, ingmar, ilkka, dom, trackbot 14:01:44 Dzung_Tran has joined #dap 14:01:44 Present+ erica_newland 14:01:54 Present+ Dzung_Tran 14:01:58 + +1.972.373.aaaa 14:02:09 zakim, aaaa is Suresh 14:02:09 +Suresh; got it 14:02:15 zakim, who is here? 14:02:15 On the phone I see Bryan, darobin, Roger, dom, Suresh 14:02:21 On IRC I see Dzung_Tran, enewland, Suresh, bryan, Zakim, RRSAgent, fjh, Mohammed, darobin, Marcos, arve, wmaslowski, lgombos, shepazu, ingmar, ilkka, dom, trackbot 14:02:28 +enewland 14:02:28 Zakim, you missed Frederick 14:02:30 I don't understand 'you missed Frederick', dom 14:02:35 zakim, you missed me 14:02:36 I don't understand 'you missed me', fjh 14:02:46 zakim, who is here? 14:02:46 On the phone I see Bryan, darobin, Roger, dom, Suresh, enewland 14:02:47 On IRC I see Dzung_Tran, enewland, Suresh, bryan, Zakim, RRSAgent, fjh, Mohammed, darobin, Marcos, arve, wmaslowski, lgombos, shepazu, ingmar, ilkka, dom, trackbot 14:03:39 zakim, who is making noise? 14:03:48 AnssiK has joined #dap 14:03:50 fjh, listening for 10 seconds I heard sound from the following: 6 (23%), Roger (75%), dom (4%) 14:03:58 zakim, 6 is me 14:03:58 sorry, fjh, I do not recognize a party named '6' 14:04:08 zakim, is 6 on the call? 14:04:08 darobin, I do not see 6 anywhere 14:04:13 zakim, is fjh on the call? 14:04:13 darobin, I do not see Fjh anywhere 14:04:18 zakim, is Frederick on the call? 14:04:18 darobin, I do not see Frederick anywhere 14:04:31 Zakim, you're hurting Frederick's feeling :) 14:04:31 I'm glad that smiley is there, dom 14:04:56 +AnssiK 14:05:05 Present+ Anssi_Kostiainen 14:05:19 +ilkka 14:05:34 Present+ Ilkka_Oksanen 14:06:02 zakim, mute Roger 14:06:02 Roger should now be muted 14:06:07 Zakim, unmute Roger 14:06:07 Roger should no longer be muted 14:06:13 Zakim, Roger is really Frederick 14:06:13 +Frederick; got it 14:06:19 richt has joined #dap 14:06:56 + +1.760.705.aabb - is perhaps pchampin 14:06:59 zakim, who is here? 14:06:59 On the phone I see Bryan, darobin, Frederick, dom, Suresh, enewland, AnssiK, ilkka, pchampin 14:07:01 On IRC I see richt, AnssiK, Dzung_Tran, enewland, Suresh, bryan, Zakim, RRSAgent, fjh, Mohammed, darobin, Marcos, arve, wmaslowski, lgombos, shepazu, ingmar, ilkka, dom, trackbot 14:07:19 Zakim, aabb is richt 14:07:19 sorry, dom, I do not recognize a party named 'aabb' 14:07:23 soonho has joined #dap 14:07:30 Scribe: Rich 14:07:34 ScribeNick: richt 14:07:40 Zakim, pchampin is really richt 14:07:40 +richt; got it 14:07:43 Present+ Soonho_Lee 14:07:46 Present+ Richard_Tibbett 14:07:47 Topic: Administrative 14:08:00 fjh: TPAC coming up with registration. 14:08:02 next F2F WG questionnaire and TPAC registration and information 14:08:02 WG questionnaire (for all), http://www.w3.org/2002/09/wbs/43696/tpac2010dap/ 14:08:04 TPAC registration (for in-person attendees) http://www.w3.org/2002/09/wbs/35125/TPAC2010reg/ 14:08:09 fjh: now would be a good time to register. 14:08:14 "Media Capture API" published as First Public Working Draft, updated draft of “HTML Media Capture” published 14:08:21 fjh: Media Capture FPWD and HTML Media Capture published. 14:08:25 http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/0136.html 14:08:37 Manyoung Cho, Opera joined 14:09:01 TOPIC: Minutes Approval 14:09:03 Approve 22 September minutes 14:09:03 http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/att-0127/minutes-2010-09-22.html 14:09:15 proposed RESOLUTION: Minutes from 22 Sept 2010 approved 14:09:20 RESOLUTION: Minutes 22/09 approved 14:09:43 TOPIC: Permission Draft 14:10:05 FPWD CfC http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/0128.html 14:10:12 q+ 14:10:16 fjh: don't have any objection to publication. Suresh, we have things to consider. 14:10:17 ack suresh 14:10:29 http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/0137.html 14:10:33 Suresh: no objection. just trying to clarify a few aspects and comments for consideration. 14:10:36 zakim, who is here? 14:10:36 On the phone I see Bryan, darobin, Frederick, dom, Suresh, enewland, AnssiK, ilkka, richt 14:10:38 On IRC I see soonho, richt, AnssiK, Dzung_Tran, enewland, Suresh, bryan, Zakim, RRSAgent, fjh, Mohammed, darobin, Marcos, wmaslowski, lgombos, shepazu, ingmar, ilkka, dom, trackbot 14:11:04 ...how do we create identifiers. Per operation or blanket access. Similar discussions could be had on other APIs. 14:11:27 fjh: WARP is not a dependency to progress our specs? 14:12:12 q+ to note that WARP doesn't allow to tailor API access per domain at this time, only network access 14:12:19 Suresh: We talk about identifiers for use as features. WARP is indicating which domains can access which APIs. 14:12:23 Robin: That's not correct 14:12:35 ack me 14:12:35 dom, you wanted to note that WARP doesn't allow to tailor API access per domain at this time, only network access 14:12:40 ...WARP defines the domains which a widget can access. It's network protection not Device API protection. 14:12:56 I suggest we remove WARP from this discussion 14:13:09 Suresh: No relation between DAP feature and WARP access? 14:13:12 Robin: None at all. 14:13:29 fjh: Suggest not to include WARP in discussion. 14:13:54 q+ 14:14:02 fjh: Do we want to publish this now? We need to work out the details but with the change in direction it might be worth publishing. 14:14:05 (note that the draft already covers somewhat the one short/duration aspect) 14:14:14 fjh: Makes sense to publish before the F2F. 14:14:14 s/one short/one shot/ 14:14:26 since we talked several times on the realtionship between domains and APIs for access controls, I thought it made sense to refer to WARP 14:14:36 Bryan: Calrify the duration of permission. What is the meaning of 'one-shot'? 14:14:41 we probably need to deal with one-shot versus permissions over time 14:14:54 generically 14:14:58 Bryan: Once I give access to a contact do I get access to further changes to that contact. 14:15:03 ...? 14:15:04 (you can actually keep access to the file for even longer than a session through localStorage I think) 14:15:14 bryan suggests we need to review in context of file API 14:15:17 q? 14:15:22 ack bryan 14:15:36 but as WARP apparetly is not to feature element but for the entire widget control, it does not fit here 14:15:51 fjh: Could be published next week. Gives us a couple of weeks before TPAC to get it in more shape. 14:15:53 s/to/tied 14:15:59 fjh: could then publish again after TPAC. 14:16:14 Robin: Wants to publish early and often. 14:16:14 nwidell has joined #dap 14:16:18 Dom: That makes sense 14:16:36 Dom: Depends on specific feedback on the draft. 14:17:00 PROPOSED RESOLUTION: Publish FPWD of Permissions Draft 14:17:15 + +46.1.07.15.aacc 14:17:18 (api-perms is the current shortname) 14:17:25 http://dev.w3.org/2009/dap/api-perms/ 14:17:40 Present+ Niklas_Widell 14:17:42 RESOLUTION: Publish FPWD of Permissions Draft (api-perms) 14:17:54 zakim, aacc is nwidell 14:17:54 +nwidell; got it 14:18:11 ACTION: Dom to get api-perms published as FPWD 14:18:11 Created ACTION-277 - Get api-perms published as FPWD [on Dominique Hazaël-Massieux - due 2010-10-06]. 14:18:31 plan to publish next week, probably Tue, maybe Thur 14:19:30 fjh: Let's take it to the list and progress the spec. 14:20:20 Suresh: Just to repeat, right now we have identifiers tied to individual operations and other one-to-n. Could we have identifiers for the entire API? 14:20:38 fjh: We can get there. Let's take it to the list. 14:20:44 TOPIC: Privacy 14:21:01 fjh: Offline comms with Alissa and John. Updates coming in the next week or two. 14:21:07 zakim, mute me 14:21:07 dom should now be muted 14:21:12 fjh: Alissa has the issues so we should get that in the doc. Can't do it today. 14:21:22 ..on the call 14:21:26 TOPIC: Contacts 14:21:59 http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/0134.html 14:22:13 Robin: No need to look in to the async thing. It's solved. 14:22:27 Robin: Other item is schema alignment. Discussion making some progress on list. 14:22:42 ...could make progress if we define the issues with the remaining fields (on list) 14:22:53 ...still need coordination and alignment with others 14:23:17 ...so let's continue the current discussion on the list 14:23:34 ...we could look at use cases/problems with implementations/other suggestions? 14:23:47 Suresh: we don't need to discuss things like name, address, telephone, etc. 14:24:01 ...one criteria is that the fields are common across formats. 14:24:22 ...in the current draft only a few fields fall in to this criteria 14:24:26 RRSAgent, draft minutes 14:24:26 I have made the request to generate http://www.w3.org/2010/09/29-dap-minutes.html dom 14:24:26 do we have a list of the problematic fields? 14:24:43 ...whatever fields we take are consistently defined across the formats 14:25:09 Robin: Looking for a way to make a resolution. Happy with free form discussion and we've already done that a lot 14:25:27 Suresh: Starting with what we have, most is OK except for a few fields mentioned on the mailing list 14:25:51 ...then we have agreement on the common fields. Then we look at the schema. Do we own them?/do we reference? 14:26:02 ...finally we need to map to formats of interest to participants. 14:26:46 Controversial list: updated, relationships, and anniversary 14:26:56 q+ 14:27:02 ack richt 14:28:17 + +82.10.31.28.aadd 14:29:21 zakim, aadd is soonho 14:29:21 +soonho; got it 14:29:37 Marcos_ has joined #dap 14:29:44 Marcos has joined #dap 14:30:02 Richard: Updated is in all versions of vCard. Relationships and anniversary not strong feelings though they are part of the latest vCard draft and can be retro-fitted to previous vCard versions with x- 14:30:39 zakim, who is here? 14:30:39 On the phone I see Bryan, darobin, Frederick, dom (muted), Suresh, enewland, AnssiK, ilkka, richt, nwidell, soonho 14:30:39 Suresh: Each format has different semantics and we need to address that. 14:30:41 On IRC I see Marcos, nwidell, soonho, richt, AnssiK, Dzung_Tran, enewland, Suresh, bryan, Zakim, RRSAgent, fjh, Mohammed, darobin, wmaslowski, lgombos, shepazu, ingmar, ilkka, dom, 14:30:43 ... trackbot 14:31:13 Robin: we can map to different semantics which is different to not being supported at all in other formats. 14:32:04 -nwidell 14:32:20 Suresh: In CAB we moved sync to a separate layer. How much of this needs to be specified in the W3C API? 14:32:52 Robin: Most sync can be based off of a timestamp in most cases. 14:33:30 +nwidell 14:34:02 Suresh: organizations in the spec seems overkill. Maybe that could be simplified. 14:34:55 q+ 14:35:16 -ilkka 14:35:26 ack richt 14:35:51 Robin: we are increasing the number of issues rather than decreasing them. If we put it on the mailing list then we can make progress. 14:36:02 ...Suresh, if you can put this on the mailing list then we can move forward 14:36:25 I'm happy to remove that. 14:36:46 RESOLUTION: Drop 'relationships'. Keep 'updated' in the W3C Contacts API. 14:37:15 Suresh: Another issue is the descriptions for these elements. 14:37:30 Robin: You're refering to referencing PoCo for descriptions? 14:37:46 ...The issue is the quality of the prose that we're referencing. Is it good enough? 14:37:47 +ilkka 14:38:17 Suresh: When we reference descriptions people assume we are basing our work on Portable contacts. Could be misleading. 14:38:20 q+ 14:38:39 Robin: we don't have any reference to a particular format. 14:38:40 ack richt 14:40:02 Richard: in the introduction we say its agnostic to underlying formats. Is that not clear enough? 14:40:11 Suresh: we need to be clearer with that. 14:40:32 ...not to do this at the normative level but create a mapping to formats in the annex. 14:41:25 Robin: The question is: Are the definitions we have today good enough? 14:41:42 Suresh: All fields are described in PoCo and OMA CAB. The meaning is fairly the same. 14:41:48 ...so what do we use in our spec. 14:41:51 ...? 14:42:22 q+ 14:43:12 ack richt 14:44:25 ACTION: Suresh to propose harmonisation descriptions for Contacts fields 14:44:25 Created ACTION-278 - Propose harmonisation descriptions for Contacts fields [on Suresh Chitturi - due 2010-10-06]. 14:44:44 Rich: if Suresh takes an action to do it, I'll be happy to incorporate 14:44:52 Suresh: before the f2f 14:45:12 Suresh: How does the group see taking fields and mapping them to different formats? 14:45:18 q+ 14:45:30 ack richt 14:46:04 +1 to incorporate stuff based on detailed submissions 14:46:50 Richard: Better to compare on the list or on another medium. If it turns out to be interesting then we can consider putting it in the spec. 14:46:56 Robin: agrees 14:48:04 I will take a stab at this (i.e. to map our fields with different formats vCard, PoCo, CAB) and we can decide if we should put it in Annex. 14:49:08 I said that it's ok to take this to the next conf call instead. 14:49:22 -richt 14:49:28 zakim, who is making noise> 14:49:28 I don't understand 'who is making noise>', fjh 14:49:30 -soonho 14:50:34 + +1.760.705.aaee - is perhaps richt 14:50:39 robin asks how to manage coordination 14:50:49 zakim, aaee is me 14:50:49 sorry, richt, I do not recognize a party named 'aaee' 14:50:59 zakim, who is here? 14:50:59 On the phone I see Bryan, darobin, Frederick, dom (muted), Suresh, enewland, AnssiK, nwidell, ilkka, richt 14:51:02 On IRC I see Marcos, nwidell, soonho, richt, AnssiK, enewland, Suresh, bryan, Zakim, RRSAgent, fjh, Mohammed, darobin, wmaslowski, lgombos, shepazu, ingmar, ilkka, dom, trackbot 14:53:09 http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/0140.html 14:53:18 Rich describes triggering the Contacts popup directly if on click, as for popups 14:54:35 -> http://dev.w3.org/html5/spec/browsers.html#dom-open Window.open() 14:55:41 -> http://www.w3.org/mid/Pine.LNX.4.64.1009231537090.3271@ps20323.dreamhostps.com Hixie on for Contacts 14:55:51 I hope we get to discuss future of element in DAP as well 14:55:54 Robin: The onclick stuff looks interesting. Certianly something to explore further. 14:57:25 +soonho 14:57:26 Robin: It's interesting and if we can model it on what HTML5 does for window.open that would be great. 14:57:35 s/Certianly/Certainly 14:57:40 rrsagent, generate minutes 14:57:40 I have made the request to generate http://www.w3.org/2010/09/29-dap-minutes.html fjh 14:58:03 ACTION-275? 14:58:03 ACTION-275 -- Richard Tibbett to review the delta between Contacts API and Mozilla's implementation http://www.w3.org/mid/1E15AA20-0551-49AB-B07D-19A0784E0316@mozilla.com -- due 2010-09-29 -- OPEN 14:58:03 http://www.w3.org/2009/dap/track/actions/275 14:58:15 s/Opera joined/Opera joined WG 14:58:41 Robin: It simplifies the HTML Contact Sharing. That kind of optimization is what we want 14:58:50 Robin: Any feedback from Mozilla? 14:58:56 Richard: Will follow up. 14:58:58 TOPIC: Captire 14:59:02 q+ to ask about 14:59:05 s/tire/ture/ 14:59:14 fjh: It will take a couple of weeks to work on the privacy aspects 14:59:18 Robin: ok 14:59:35 s/TOPIC: Captire/TOPIC: Capture 14:59:55 ack me 14:59:56 dom, you wanted to ask about 14:59:57 Robin: Would be good if someone pings the Google guys to see if there's some kind of alignment on Media Capture 15:00:19 Dom: Asking about HTML or API alignment? 15:00:21 Robin: Both 15:00:33 Dom: Perhaps Illka could start discussions since he's the editor? 15:00:36 s/Alissa has the issues so we should get that in the doc/Alissa has recorded the issues related to Privacy Rulesets, and is planning to update that document 15:00:41 Illka: Yes. I can do that. 15:01:30 -soonho 15:01:31 -> http://www.w3.org/mid/AANLkTimr0XsH8vJN-euKWLRpJbG8-HCaZmjsjyhUnRgn@mail.gmail.com 15:02:04 Robin: idea is to pick this thread up again. Does what we've described match what they are implementing? Are they interested in the next step, which is the API part? 15:02:15 Illka: Will follow up on this. 15:02:21 [I wonder if the API part couldn't ask the same trick that richt just came up with for Contacts] 15:02:40 ACTION: ilkka to talk to the Chrome folks about capture 15:02:40 Created ACTION-279 - Talk to the Chrome folks about capture [on Ilkka Oksanen - due 2010-10-06]. 15:02:53 darobin, I don't see why it couldn't apply to a few APIs. 15:02:59 TOPIC: element 15:03:03 ack me 15:03:07 Robin: Dom you wanted to discuss? 15:03:44 Dom: Feedback from the HTML Working Group. Feedback suggested that DAP could be a good home for this. 15:04:00 ....see if we have a plan for it and whether we are prepared to take it on. 15:04:26 Robin: Will ask Ian if he will edit the stuff in the context of the DAP WG. 15:04:40 ...group will need to create a resolution that we actually want to do this. 15:04:58 q+ 15:05:03 Dom: Talk to Ian and we'll go from there to produce a FPWD of the device element. 15:05:09 ACTION: Robin to ping Hixie about editing as part of DAP, based on answer we start CfC for publication 15:05:09 Created ACTION-280 - Ping Hixie about editing as part of DAP, based on answer we start CfC for publication [on Robin Berjon - due 2010-10-06]. 15:05:14 ...if Ian agrees of course. 15:05:20 q- 15:05:44 Robin: Charter-wise it's within our charter. 15:06:10 I was wondering how it might impact our schedule, first step is to get feedback 15:06:54 -Frederick 15:07:10 Robin: HTML ML is starting to crunch on LC issues. It's high traffic. DAP ML may be better for cutting edge feature discussions. 15:07:50 TOPC: Sys Info 15:07:53 +Frederick_Hirsch 15:07:55 TOPIC: Sys Info 15:07:55 q+ what about event loop 15:07:58 q+ to ask what about event loop 15:08:03 ack me 15:08:03 dom, you wanted to ask what about event loop 15:08:09 Robin: Need to review. Dong-Young and Richard also need to review as per their actions. 15:08:27 Dom: Robin, you took an action to see how the HTML5 event loop fits in to the Sys Info spec. Any news? 15:08:44 Robin: Taking more time to review Sys Info than I thought but I'm doing that as I go. 15:09:17 ...just figuring out exactly where it fits in. How much goes directly in to Sys Info and how much should be in the Device spec. 15:09:40 ...same feedback that Richard had when integrating the event loop in to Contacts. 15:10:22 q? 15:10:48 q+ 15:11:04 ack fjh 15:11:08 FYI I made two proposals for closing action items (123,196). 15:11:17 http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/0062.html 15:11:20 TOPIC: API Requirements 15:11:35 fjh: we are collecting some things that might need to be put in to this document. 15:11:42 ...Dom suggested we need to update this doc. 15:11:46 ...agree with that. 15:12:18 q+ to suggest a yearly update doesn't seem too much 15:12:19 Robin: Do we maintain it everytime we change our minds on what goes in to the specification. Or wait til CR and produce a doc that matches what we have accomplished? 15:12:39 ack dom 15:12:39 dom, you wanted to suggest a yearly update doesn't seem too much 15:13:04 Robin: Does it need to be one big doc or split it? 15:13:37 Dom: Shouldn't spend too much time keeping it up to date right now but the last update was 1 year ago. Perhaps its a good time to communicate the changes in that time. 15:13:49 q+ 15:14:05 Dom: I'm willing to take a go at this. 15:14:05 http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/ 15:14:09 ACTION: Dom to take a stab at updating the API Requirements documents 15:14:10 Created ACTION-281 - Take a stab at updating the API Requirements documents [on Dominique Hazaël-Massieux - due 2010-10-06]. 15:14:19 ack richt 15:14:22 zakim, mute me 15:14:22 dom should now be muted 15:14:47 -1 on folding in individual specs 15:14:57 requirements don't belong to API descriptions in my mind 15:15:01 I think there is value in having one separate document 15:15:13 Richard: How about folding requirements back in to their corresponding specs? i.e. Contact requirements in the Contacts spec. 15:15:14 -1 on folding in individual specs, want to see commonality 15:15:37 q+ 15:15:44 ack fjh 15:17:19 [can we agree to update the requirements and figure out where to stuff them later?] 15:17:27 zakim, mute me 15:17:27 ilkka should now be muted 15:17:56 Robin: Anything else on requirements 15:18:03 TOPIC: Messaging (redux) 15:18:08 -AnssiK 15:18:11 suggestion is that common patterns and requirements will emerge, helpful to see what is common to various APIs 15:18:14 ACTION: Robin get the ball rolling again on Messaging issues on the list 15:18:14 Created ACTION-282 - Get the ball rolling again on Messaging issues on the list [on Robin Berjon - due 2010-10-06]. 15:18:19 Robin: I'll take an action item to get discussion happening on list again. 15:18:38 -Frederick_Hirsch 15:18:43 +??P15 15:18:50 zakim, ??P15 is me 15:18:50 +fjh; got it 15:18:51 Robin: You have proposals for closing some actions? 15:18:53 ACTION-123? 15:18:53 ACTION-123 -- Bryan Sullivan to make a concrete proposal how Contacts could support use of specific address books -- due 2010-03-24 -- PENDINGREVIEW 15:18:53 http://www.w3.org/2009/dap/track/actions/123 15:19:04 q+ 15:19:12 Bryan: Can close ACTION-123 due to public-contacts-coord. 15:19:13 ACTION-196 15:19:21 (ACTION-123 is not about formats, it's about tracking source of contacts data) 15:19:22 ack me 15:19:23 ACTION-196? 15:19:23 ACTION-196 -- Bryan Sullivan to incorporate edits from James proposal http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0174.html -- due 2010-06-23 -- PENDINGREVIEW 15:19:23 http://www.w3.org/2009/dap/track/actions/196 15:19:30 ...ACTION-196 has been checked by James so can be closed also. 15:19:58 Dom: On ACTION-196 not bound to schema or formats. Was how to specify writing back to a specific address book. 15:20:13 Suresh: This is related to service id? 15:20:20 Dom: Yes 15:20:52 Bryan: No proposal at the moment. Could leave it open but prefer to close it. Worked through the issues at the time but no proposal at the end. 15:20:55 zakim, mute me 15:20:55 dom should now be muted 15:21:01 +1 on closing action and issue 15:21:07 issue-43? 15:21:07 ISSUE-43 -- Should we make the contacts API data-storage-aware? -- closed 15:21:07 http://www.w3.org/2009/dap/track/issues/43 15:21:24 action-123 closed 15:21:24 ACTION-123 Make a concrete proposal how Contacts could support use of specific address books closed 15:21:24 I absolutely do not want to talk about this stuff. 15:21:27 (it's closed because it has been replaced by ISSUE-77à 15:21:30 ISSUE-77? 15:21:30 ISSUE-77 -- Contacts need management of address book, different role than contacts user -- raised 15:21:30 http://www.w3.org/2009/dap/track/issues/77 15:21:49 s/à/)/ 15:21:55