13:45:47 RRSAgent has joined #dap 13:45:47 logging to http://www.w3.org/2010/08/04-dap-irc 13:45:49 RRSAgent, make logs world 13:45:49 Zakim has joined #dap 13:45:51 Zakim, this will be DAP 13:45:51 ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 15 minutes 13:45:52 Meeting: Device APIs and Policy Working Group Teleconference 13:45:52 Date: 04 August 2010 13:46:02 Chair: Frederick_Hirsch 13:46:10 Present+: Frederick_Hirsch 13:46:24 Present+ Frederick_Hirsch 13:46:27 s/Present+: Frederick_Hirsch// 13:46:57 Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2010Aug/0009.html 13:47:43 Regrets: Robin_Berjon 13:49:59 Dzung_Tran has joined #dap 13:50:10 Present+ Dzung_Tran 13:51:14 Suresh has joined #dap 13:51:25 Present+ Suresh_Chitturi 13:52:39 nstratford has joined #dap 13:58:04 jmorris has joined #dap 13:58:25 soonho has joined #dap 13:58:35 Present+ John_Morris 13:58:44 Present+ Soonho_Lee 13:59:23 Present+ Neil_Stratford 14:01:05 zakim, call thomas-781 14:01:05 ok, tlr; the call is being made 14:01:06 UW_DAP()10:00AM has now started 14:01:08 +Thomas 14:01:18 Present+ Thomas_781 14:01:20 gah 14:01:23 Present+ Thomas_Roessler 14:01:29 +Dom 14:01:31 + +1.202.744.aaaa 14:01:46 +[IPcaller] 14:01:47 + +1.425.214.aabb 14:01:48 - +1.425.214.aabb 14:01:53 zakim, .aaaa is jmorris 14:01:53 sorry, jmorris, I do not recognize a party named '.aaaa' 14:02:02 + +1.425.214.aacc 14:02:05 +[IPcaller.a] 14:02:06 Regrets+ Ingmar_Kliche 14:02:06 -[IPcaller] 14:02:13 zakim, aaaa is jmorris 14:02:13 +jmorris; got it 14:02:15 zakim, [IPcaller.a] is me 14:02:15 +fjh; got it 14:02:22 + +1.972.373.aadd 14:02:23 + +1.202.637.aaee 14:02:23 zakim, who's on the call? 14:02:24 On the phone I see Thomas, Dom, jmorris, +1.425.214.aacc, fjh, +1.972.373.aadd, +1.202.637.aaee 14:02:28 zakim, aadd is Suresh 14:02:28 +Suresh; got it 14:02:33 zakim, who is here? 14:02:33 On the phone I see Thomas, Dom, jmorris, +1.425.214.aacc, fjh, Suresh, +1.202.637.aaee 14:02:35 On IRC I see soonho, jmorris, nstratford, Suresh, Dzung_Tran, Zakim, RRSAgent, fjhtoo, fjh, tlr, shepazu, wmaslowski, ingmar, ilkka, lgombos, dom, trackbot 14:02:40 enewland has joined #dap 14:02:47 Present+ erica_newland 14:02:48 Present+ Dominique_Hazael-Massieux 14:03:05 +[IPcaller] 14:03:46 zakim, [IPcaller] is me 14:03:46 +nstratford; got it 14:03:58 maoteo has joined #dap 14:04:02 zakim, aaee is probably enewland 14:04:02 +enewland?; got it 14:04:10 bryan_sullivan has joined #dap 14:04:22 zakim, who is here? 14:04:22 On the phone I see Thomas, Dom, jmorris, +1.425.214.aacc, fjh, Suresh, enewland?, nstratford 14:04:23 present+ bryan_sullivan 14:04:25 On IRC I see bryan_sullivan, maoteo, enewland, jmorris, nstratford, Suresh, Dzung_Tran, Zakim, RRSAgent, fjhtoo, fjh, tlr, shepazu, wmaslowski, ingmar, ilkka, lgombos, dom, 14:04:26 Present+ Maria_Oteo 14:04:26 zakim, enewland? is enewland 14:04:27 ... trackbot 14:04:28 +enewland; got it 14:04:30 somebody_ has joined #dap 14:04:42 Present+ Daniel_Coloma 14:04:42 zakim, aacc is bryan_sullivan 14:04:42 +bryan_sullivan; got it 14:05:37 zakim, who is here? 14:05:37 On the phone I see Thomas, Dom, jmorris, bryan_sullivan, fjh, Suresh, enewland, nstratford 14:05:39 On IRC I see somebody_, bryan_sullivan, maoteo, enewland, jmorris, nstratford, Suresh, Dzung_Tran, Zakim, RRSAgent, fjhtoo, fjh, tlr, shepazu, wmaslowski, ingmar, ilkka, lgombos, 14:05:41 ... dom, trackbot 14:05:53 soonho has joined #dap 14:06:04 SribeNick:Suresh 14:06:12 Present+ Soonho_Lee 14:06:15 Erica is able to scribe next week, thanks 14:06:17 ScribeNick: Suresh 14:06:45 TPAC registration and information available (F2F after London F2F, 4-5 November ) 14:06:49 Topic: Announcements 14:06:57 http://lists.w3.org/Archives/Member/member-device-apis/2010Jun/0001.html 14:07:11 November 4-5 for a F2F 14:07:16 + +4aaff 14:07:21 Regrets+ Alissa_Cooper 14:07:34 zakim, mute me 14:07:34 Dom should now be muted 14:07:47 http://www.w3.org/2002/09/wbs/43696/tpac2010dap/ 14:07:49 http://www.w3.org/2002/09/wbs/43696/tpac2010dap/ 14:08:22 + +34.97.421.aagg 14:08:32 Frederick: please register and fill in the questionnarie 14:08:44 Zakim, aagg is maoteo 14:08:44 +maoteo; got it 14:09:12 -> http://www.w3.org/2002/09/wbs/35125/TPAC2010reg/ Actual TPAC Registration form 14:09:38 The questionnaire is for WG planning, and can be done anytime, and should be done even if you don't plan to attend. 14:09:59 The TPAC registration is essential if you plan to attend 14:10:24 -> http://www.w3.org/2002/09/wbs/43696/seoul-f2f-dates/ March 2011 F2F in Seoul 14:10:37 ack me 14:10:41 March F2F, plan for Seoul Korea, http://www.w3.org/2002/09/wbs/43696/seoul-f2f-dates/ 14:11:17 zakim, mute me 14:11:17 Dom should now be muted 14:11:18 dom notes hosting is confirmed 14:11:33 zakim, who is here? 14:11:33 On the phone I see Thomas, Dom (muted), jmorris, bryan_sullivan, fjh, Suresh, enewland, nstratford, +4aaff, maoteo 14:11:35 On IRC I see soonho, somebody_, bryan_sullivan, maoteo, enewland, jmorris, nstratford, Suresh, Dzung_Tran, Zakim, RRSAgent, fjhtoo, fjh, tlr, shepazu, wmaslowski, ingmar, ilkka, 14:11:37 ... lgombos, dom, trackbot 14:11:56 Media Capture Working Draft published, 20 July - http://www.w3.org/TR/html-media-capture/ 14:12:05 Richard Tibbett now at Opera, http://lists.w3.org/Archives/Public/public-device-apis/2010Aug/0006.html 14:12:21 Topic: Minutes review 14:12:34 http://www.w3.org/2009/dap/minutes#draft-minutes 14:12:43 please review and indicate corrections 14:13:06 fjh: the approval is deferred until Robin s back from vacation 14:13:13 Topic:Privacy and Policy 14:13:18 zakim, aaff is yourHandle 14:13:18 +yourHandle; got it 14:13:49 zakim, yourHandle is really soonho 14:13:49 +soonho; got it 14:14:04 Bryan: Are there minutes available from the privacy workshop? 14:14:36 http://www.w3.org/2010/07/12-privacy-minutes.html 14:14:38 http://www.w3.org/2010/07/13-privacy-minutes.html 14:14:42 draft minutes 14:14:44 tlr: Summary report will be available soon 14:16:03 ACTION-210? 14:16:03 ACTION-210 -- Alissa Cooper to summarize and add issues to ruleset doc -- due 2010-07-21 -- OPEN 14:16:03 http://www.w3.org/2009/dap/track/actions/210 14:16:07 fjh: the group needs to make a decision on how to move the ruleset forward 14:16:10 richt has joined #dap 14:16:13 ack me 14:16:19 Present+ Richard_Tibbett 14:16:46 q+ 14:16:48 + +44.757.091.aahh 14:17:00 ack bryan_sullivan 14:17:09 zakim, mute me 14:17:09 Dom should now be muted 14:17:26 Bryan: we should continue to discuss this - will take some time to flesh it out...UI aspects 14:17:26 zakim, who is here? 14:17:26 On the phone I see Thomas, Dom (muted), jmorris, bryan_sullivan, fjh, Suresh, enewland, nstratford, soonho, maoteo, +44.757.091.aahh 14:17:28 On IRC I see richt, soonho, somebody_, bryan_sullivan, maoteo, enewland, jmorris, nstratford, Suresh, Dzung_Tran, Zakim, RRSAgent, fjhtoo, fjh, tlr, shepazu, wmaslowski, ingmar, 14:17:29 -> http://lists.w3.org/Archives/Public/public-privacy/2010JulSep/ public-privacy@w3.org mailing list 14:17:31 ... ilkka, lgombos, dom, trackbot 14:17:40 q- 14:18:16 fjh: next step is to wait for ACTION 210.. 14:18:49 John: agreed, it needs more discussion 14:18:53 privacy plan - outline issues (ACTION-210), propose means to address if possible, then WG decision on next steps 14:19:34 q+ 14:19:46 ack Suresh 14:20:09 Suresh: Notification API? 14:20:20 q- 14:20:30 http://dev.w3.org/2009/dap/features/ 14:20:40 -> http://lists.w3.org/Archives/Public/public-web-notification/ list for discussions around the chartering of a Web Notification WG 14:20:43 fjh: it's probably an error...should be deleted 14:20:57 q+ 14:21:11 ack tlr 14:21:42 -> http://lists.w3.org/Archives/Public/public-geolocation/2010Aug/thread.html#msg1 Thread around the need for a URI for geolocation API in widgets 14:21:57 q+ 14:22:48 (I'm not sure if Notifications are very privacy-invasive in general) 14:23:00 (+1 on that, just pointing out the general point) 14:23:02 Suggest we avoid discussion of where URIs should be defined, currently keep in Features document so we can have text around the topic, and clarity 14:23:10 -> http://www.w3.org/2002/09/wbs/33280/notif2010/ Call for Review: Rich Web Client Activity Proposal - Web Notification Working Group (Member-only) 14:23:13 Also suggest we limit to APIs in DAP + Geoloc, as a starting point 14:23:21 tlr: FYI, notification work is being planned in a separate working group 14:23:27 http://lists.w3.org/Archives/Member/w3c-ac-members/2010JulSep/0013.html (member-confidential link) 14:23:41 -> http://lists.w3.org/Archives/Public/public-new-work/2010Jul/0001.html Proposed W3C Charter: Web Notification Working Group (until 2010-08-23) [public announcement] 14:23:59 fjh: re feature, what is our next steps? 14:24:25 ack me 14:25:20 ack bryan_sullivan 14:25:36 dom: we need to be aware that there are exisiting feature classification, and make sure we take them as input for our work 14:25:50 q+ 14:26:35 dom notes features can be used in various contexts, policy, widget, also potentially checkPermissions proposal, installable applications manifest 14:26:57 action: fjh to send notice on features draft to list and ask for help progressing 14:26:58 Created ACTION-244 - Send notice on features draft to list and ask for help progressing [on Frederick Hirsch - due 2010-08-11]. 14:27:29 zakim, mute me 14:27:29 Dom should now be muted 14:27:31 action: fjh to provide notice on tpac questionnaire 14:27:31 Created ACTION-245 - Provide notice on tpac questionnaire [on Frederick Hirsch - due 2010-08-11]. 14:27:41 q- 14:27:48 q+ to ask about WAC 14:28:16 q- 14:28:59 ack fjh 14:28:59 fjh, you wanted to ask about WAC 14:29:45 fjh: does anyone know anything on WAC? 14:30:49 fjh: back to Policy, if there is any input please provide it to help progress policy work 14:30:58 s/on WAC/on how WAC plans to align with DAP's specs/ 14:31:09 I suggest members of this WG that are involved with WAC to make sure WAC is aware of WG API work and strive toward alignment 14:31:19 my comment re Web Notification WG proposal, this seems related to work that I lead in OMA and discussions we have had with HTML WG re Server-Sent Events and OMA Push (including SIP Push). I think this would be better handled as a new spec inside Webapps rather than a new group. AT&T would support this work, but joining another group is problematic. 14:31:35 ACTION-218? 14:31:35 ACTION-218 -- Paddy Byers to provide proposal for feature architecture text regarding web and widgets cases for feature document -- due 2010-07-21 -- OPEN 14:31:35 http://www.w3.org/2009/dap/track/actions/218 14:31:45 ACTION-241? 14:31:45 ACTION-241 -- Frederick Hirsch to review and update policy requirements -- due 2010-07-23 -- OPEN 14:31:45 http://www.w3.org/2009/dap/track/actions/241 14:31:49 action-242? 14:31:49 ACTION-242 -- Paddy Byers to review and update policy requirements -- due 2010-07-23 -- OPEN 14:31:49 http://www.w3.org/2009/dap/track/actions/242 14:32:02 Topic: Message API Status 14:32:08 http://lists.w3.org/Archives/Public/public-device-apis/2010Aug/0005.html 14:32:27 ACTION-222? 14:32:27 ACTION-222 -- Thomas Roessler to review the Messaging security section -- due 2010-08-15 -- OPEN 14:32:27 http://www.w3.org/2009/dap/track/actions/222 14:32:35 action-221? 14:32:35 ACTION-221 -- Maria Angeles Oteo to draft a security section for Messaging -- due 2010-07-22 -- PENDINGREVIEW 14:32:35 http://www.w3.org/2009/dap/track/actions/221 14:32:47 ACTION-221? 14:32:47 ACTION-221 -- Maria Angeles Oteo to draft a security section for Messaging -- due 2010-07-22 -- PENDINGREVIEW 14:32:47 http://www.w3.org/2009/dap/track/actions/221 14:33:44 fjh: we should publish FPWD 14:33:48 tlr: +1 14:33:56 +1 14:34:42 Date: 10 Aug 2010 14:35:09 RESOLUTION: To publish FPWD of Messaging API - 10 Aug 2010 14:35:20 ACTION: Dom to request approval for FPWD for messaging and prepare publication 14:35:21 Created ACTION-246 - Request approval for FPWD for messaging and prepare publication [on Dominique Hazaël-Massieux - due 2010-08-11]. 14:35:31 action: fjh to send transition request for Message API FPWD publication 14:35:31 Created ACTION-247 - Send transition request for Message API FPWD publication [on Frederick Hirsch - due 2010-08-11]. 14:35:37 ack me 14:35:45 zakim, mute me 14:35:45 Dom should now be muted 14:36:06 Topic: SysInfo status 14:36:18 http://lists.w3.org/Archives/Public/public-device-apis/2010Aug/0002.html 14:37:39 Bryan will work on editorial items, anticipate completion mid-August 14:37:46 ISSUE-92? 14:37:46 ISSUE-92 -- Sysinfo, permissions for get vs monitor; -- open 14:37:46 http://www.w3.org/2009/dap/track/issues/92 14:38:04 ack me 14:38:26 "Should the privacy prompts/indications for operators that are permanent (watch) vs one-shot (get) differ? " 14:38:45 zakim, mute me 14:38:45 Dom should now be muted 14:40:12 q+ 14:40:20 action: jmorris to provide a proposal relevant to ISSUE-92, sysinfo privacy prompts for operators get vs watch 14:40:20 Created ACTION-248 - Provide a proposal relevant to ISSUE-92, sysinfo privacy prompts for operators get vs watch [on John Morris - due 2010-08-11]. 14:40:25 ack Suresh 14:41:13 (wouldn't monitor be equivalent to get then?) 14:41:38 I see that there are no exceptions for monitor(), shoudl we consider adding exceptions? 14:41:57 (I suggest sending this as a question to the editors before raising an issue) 14:42:49 ISSUE: some properties of sysinfo are static so monitor might not make sense 14:42:50 Created ISSUE-96 - Some properties of sysinfo are static so monitor might not make sense ; please complete additional details at http://www.w3.org/2009/dap/track/issues/96/edit . 14:43:26 action-203? 14:43:26 ACTION-203 -- Bryan Sullivan to add proposal from John Morris re buckets to sysinfo, http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0322.html -- due 2010-07-07 -- PENDINGREVIEW 14:43:26 http://www.w3.org/2009/dap/track/actions/203 14:43:26 Suresh to send a note to the list re ISSUE-96 14:43:37 action-211? 14:43:37 ACTION-211 -- Alissa Cooper to make proposal on list for sysinfo privacy section -- due 2010-07-21 -- OPEN 14:43:37 http://www.w3.org/2009/dap/track/actions/211 14:43:42 q- 14:43:49 action-212? 14:43:49 ACTION-212 -- Bryan Sullivan to incorporate proposal from ACTION-211 into SysInfo draft -- due 2010-07-21 -- CLOSED 14:43:49 http://www.w3.org/2009/dap/track/actions/212 14:44:00 action-211 closed 14:44:00 ACTION-211 Make proposal on list for sysinfo privacy section closed 14:44:23 -enewland 14:44:32 action-212 closed 14:44:32 ACTION-212 Incorporate proposal from ACTION-211 into SysInfo draft closed 14:44:34 (I think that's done; but Alissa will review it as part of ACTION-210) 14:44:59 correct. will review sysinfo after the edits 14:45:27 Expect that ACTION-213 and ACTION-243 will be done after edits complete, Bryan please notify the WG when complete 14:45:43 assume also for ACTION-214 14:46:12 Topic: Contacts API 14:46:21 http://lists.w3.org/Archives/Public/public-device-apis/2010Aug/0007.html (richard) 14:46:47 Richard plans to update over the next two weeks 14:46:51 ACTION-215? 14:46:51 ACTION-215 -- Dominique Hazaël-Massieux to write up issues with write/delete access for Contacts APIs -- due 2010-07-21 -- PENDINGREVIEW 14:46:51 http://www.w3.org/2009/dap/track/actions/215 14:46:53 q+ 14:46:57 ack tlr 14:47:39 tlr: coordination between OMA CAB and IETF vCard 14:47:51 tlr link on vcard4, http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0142.html 14:47:54 -> http://www.w3.org/mid/1279639071.29671.160.camel%2540localhost Write-access difficulties (for contacts and other APIs) — for ACTION-215 14:48:54 tlr: OMA initial response was to have W3C align with OMA work 14:49:02 q+ 14:49:11 tlr: we need to get IETF people involved as well 14:51:20 Agree with fjh. We will need another working draft for Contacts API and Contacts Writer API in the very near future, which was mentioned before and during the f2f. 14:51:28 ack bryan_sullivan 14:52:06 q+ 14:52:14 suggest we publish another WD in mid-August of Contacts without delay, then allow review of other materials etc. Need to think about when Last Call might happen 14:52:21 ack Suresh 14:52:28 q+ 14:53:09 Bryan: I can facilitate the information from OMA CAB 14:53:40 I'd like to set a schedule for Last Call for Contacts. 14:53:46 me too 14:54:30 sounds to me that we risk a large delay in reaching DAP Contacts last call, given various other partiers 14:54:30 ...and last call sooner rather than later, with inputs from vcard, oma and any other external groups before that time. (1 or 2 months from now?) 14:54:35 s/partiers/parties 14:54:54 ack Suresh 14:55:34 suresh notes that OMA might provide an official liaison to DAP 14:55:57 suresh notes that OMA schema is much more detailed, closer to vcard than DAP contacts 14:56:10 I'd like input from OMA, vcard on the public mailing list and propose to set the schedule for last call in one month. 14:57:05 +1 on intermediate draft showing removal of write access 14:57:45 tlr: based on the discussion, I would support publishling a ordinary public draft 14:57:50 plan to publish WD when current round of edits is done, then review convergence and plan schedule for Last Call 14:57:52 q+ to ask whether we are just publishing Contacts API working draft (not writer api)? 14:57:54 Link to the OMA CAB address book schema spec: http://member.openmobilealliance.org/ftp/Public_documents/COM/COM-CAB/Permanent_documents/OMA-SUP-XSD_cab_address_book-V1_0-20100309-D.zip 14:58:38 ack richt 14:58:38 richt, you wanted to ask whether we are just publishing Contacts API working draft (not writer api)? 14:59:45 bryan, is the spec relating to this XSD available? 15:00:14 in fact... 15:00:19 richard asks whether we want to publish writer at same time as contacts, so material is lost 15:00:32 that xsd defines an element and doesn't say anything about the data model 15:00:49 that's right, the schema is still TBD 15:00:54 (I'm not sure about publishing contacts writer, but I wouldn't object to it) 15:01:25 i will try to send the link to the actual spec or maybe better to have it through the OMA liaison 15:01:59 +??P11 15:02:14 suresh, thanks 15:02:47 Dong-Young has joined #dap 15:03:20 Present+ Dong-Young_Lee 15:04:15 ack me 15:04:21 ACTION-215? 15:04:21 ACTION-215 -- Dominique Hazaël-Massieux to write up issues with write/delete access for Contacts APIs -- due 2010-07-21 -- PENDINGREVIEW 15:04:21 http://www.w3.org/2009/dap/track/actions/215 15:04:24 http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0112.html 15:04:25 ACTION: Suresh to review OMA CAB, vCard work and provide a summary on how we may progress 15:04:25 Created ACTION-249 - Review OMA CAB, vCard work and provide a summary on how we may progress [on Suresh Chitturi - due 2010-08-11]. 15:04:26 Further link to the spec which describes the CAB address book schema as an object accessible via an OMA XML Document Management Service (XDMS): http://member.openmobilealliance.org/ftp/Public_documents/COM/COM-CAB/Permanent_documents/OMA-TS-CAB_XDMS-V1_0-20100722-D.zip 15:05:36 action: richard add issue to contact writer corresponding to Dom's email for ACTION-215, http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0112.html 15:05:36 Created ACTION-250 - Add issue to contact writer corresponding to Dom's email for ACTION-215, http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0112.html [on Richard Tibbett - due 2010-08-11]. 15:06:11 ACTION-230? 15:06:11 ACTION-230 -- Wojciech Maslowski to specify "add to calendar" based on ICS-objects opening -- due 2010-08-05 -- OPEN 15:06:11 http://www.w3.org/2009/dap/track/actions/230 15:06:12 ISSUE: Write-access difficulties (in contacts and other APIs), see http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0112.html 15:06:12 Created ISSUE-97 - Write-access difficulties (in contacts and other APIs), see http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0112.html ; please complete additional details at http://www.w3.org/2009/dap/track/issues/97/edit . 15:06:48 (regarding contacts, there was also discussion around ) 15:06:50 ACTION-224? 15:06:50 ACTION-224 -- Wojciech Maslowski to look into options for contacts API -- due 2010-08-05 -- OPEN 15:06:50 http://www.w3.org/2009/dap/track/actions/224 15:07:05 fjh: the plan is to publish a read-only draft in mid-August after edits, and FPWD of contact writer later 15:07:15 correct, dom, but nothing much to say on that on this call :-( 15:08:10 Topic: Calendar 15:08:16 q+ 15:08:22 ack tlr 15:08:31 http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0142.html 15:08:38 calConnect, http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0143.html 15:08:52 OASIS WS-Calendaring 15:08:53 tlr: no active work in IETF re calendar 15:09:33 http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-calendar 15:09:45 the open question is how can we be compatible with other calender services over the wire 15:10:55 tlr notes will need use cases for lunisolar calendars and help on working on that if needed 15:11:21 ACTION-227? 15:11:21 ACTION-227 -- Dominique Hazaël-Massieux to compare iCalendar recurrence model with current Calendar API -- due 2010-07-22 -- PENDINGREVIEW 15:11:21 http://www.w3.org/2009/dap/track/actions/227 15:11:32 http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0115.html 15:11:34 q+ 15:12:02 ack richt 15:12:48 +1 to work on the gregorian for the moment 15:13:26 we have a way forward now on Calendar with the resolution to continue with what we have now (smaller scope than lunisolar support)... 15:13:35 ...and having a TimezonedDate proposal that is nearly complete 15:13:42 dom: we need to take a look at my comments... 15:13:54 Topic: Capture 15:13:56 http://lists.w3.org/Archives/Public/public-device-apis/2010Aug/0004.html 15:14:08 dom, we do need to address your comments on Calendar Recurrence rules. Will do that on the mailing list. 15:14:21 "how do we properly reference 15:14:21 external IDLs (after we moved e.g. FormatData into external spec 15:14:21 HTMLMEDIACAPTURE)?" 15:14:35 (I'll respond to him on the list) 15:14:44 ACTION-235? 15:14:44 ACTION-235 -- Ingmar Kliche to polish Media Capture -- due 2010-07-23 -- OPEN 15:14:44 http://www.w3.org/2009/dap/track/actions/235 15:15:16 RE: referencing external widls. perhaps we should be defining modules as in the WebIDL spec. AFAICS, modules can be referenced across specs like ::module1::submodule1 (etc) 15:16:11 Topic: Action and issue review 15:16:22 ACTION-210 stays open 15:16:31 ACTION-211? 15:16:31 ACTION-211 -- Alissa Cooper to make proposal on list for sysinfo privacy section -- due 2010-07-21 -- CLOSED 15:16:31 http://www.w3.org/2009/dap/track/actions/211 15:17:01 ACTION-213, ACTION-243, ACTION-214 open, await update of Sysinfo before review 15:17:09 wmaslowski_ has joined #dap 15:17:10 Opera__ has joined #dap 15:17:11 ACTION-216? 15:17:11 ACTION-216 -- WonSuk Lee to reformulate gallery API to look like contacts API -- due 2010-07-21 -- OPEN 15:17:11 http://www.w3.org/2009/dap/track/actions/216 15:17:34 ACTION-218? 15:17:34 ACTION-218 -- Paddy Byers to provide proposal for feature architecture text regarding web and widgets cases for feature document -- due 2010-07-21 -- OPEN 15:17:34 http://www.w3.org/2009/dap/track/actions/218 15:17:47 ACTION-222? 15:17:47 ACTION-222 -- Thomas Roessler to review the Messaging security section -- due 2010-08-15 -- OPEN 15:17:47 http://www.w3.org/2009/dap/track/actions/222 15:17:49 today 15:18:00 ACTION-238? 15:18:00 ACTION-238 -- Bryan Sullivan to inform OMA groups of our status -- due 2010-07-23 -- OPEN 15:18:00 http://www.w3.org/2009/dap/track/actions/238 15:18:19 Bryan will provide an update 15:18:28 ISSUE-92? 15:18:28 ISSUE-92 -- Sysinfo, permissions for get vs monitor; -- open 15:18:28 http://www.w3.org/2009/dap/track/issues/92 15:18:36 ISSUE-78? 15:18:36 ISSUE-78 -- Capture has a minimisation problem with EXIF data (e.g. it could be Geotagged) -- open 15:18:36 http://www.w3.org/2009/dap/track/issues/78 15:19:02 http://www.w3.org/TR/2010/WD-html-media-capture-20100720/#security has text around it 15:19:02 q+ 15:19:08 ack me 15:19:10 ack dom 15:19:38 ISSUE-78: http://www.w3.org/TR/2010/WD-html-media-capture-20100720/#security has text around it 15:19:38 ISSUE-78 Capture has a minimisation problem with EXIF data (e.g. it could be Geotagged) notes added 15:19:42 "For instance, embedding the user’s location in a captured media metadata (e.g. EXIF) might transmit more private data than the user might be expecting" 15:20:30 "Implementations must not embed information in the EXIF header which could be used for non-intended purposes (such as geolocation or device id). " http://dev.w3.org/2009/dap/camera/Overview-API.html#security 15:20:35