13:28:55 RRSAgent has joined #dap 13:28:55 logging to http://www.w3.org/2010/06/23-dap-irc 13:28:57 RRSAgent, make logs world 13:28:57 Zakim has joined #dap 13:28:59 Zakim, this will be DAP 13:29:00 ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 32 minutes 13:29:00 Meeting: Device APIs and Policy Working Group Teleconference 13:29:00 Date: 23 June 2010 13:37:39 Regrets+ Claes_Nilsson 13:48:55 Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0239.html 13:49:54 fjh has changed the topic to: DAP 3279 agenda http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0239.html ; pls register Present+ first_last ; update zakim, aaaa is handle (fjh) 13:50:07 Chair: Robin_Berjon, Frederick_Hirsch 13:50:16 Present+ Robin_Berjon, Frederick_Hirsch 13:51:15 Regrets+ Maria_Oteo 13:55:53 paddy has joined #dap 13:58:02 alissa has joined #dap 13:58:32 UW_DAP()10:00AM has now started 13:58:39 +[IPcaller] 13:58:45 zakim, [IPcaller] is me 13:58:45 +fjh; got it 13:59:33 wonsuk has joined #dap 13:59:35 I keep getting kicked off the bridge; has the code changed? 13:59:40 + +1.202.436.aaaa 13:59:54 darobin has joined #dap 14:00:09 zakim, +1.202.436.aaaa is alissa 14:00:09 +alissa; got it 14:00:20 Present+ Alissa_Cooper 14:00:29 zakim, code? 14:00:29 the conference code is 3279 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), fjh 14:00:52 +??P5 14:01:00 +[IPcaller] 14:01:01 present+ Paddy_Byers 14:01:10 Zakim, [IPCaller] is me 14:01:10 +darobin; got it 14:01:15 +Dom 14:01:17 Present+ Dominique_Hazael-Massieux 14:01:18 + +358.504.86aabb 14:01:27 zakim, aabb is ilkka 14:01:27 +ilkka; got it 14:01:31 Regrets+ Dzung_Tran 14:01:31 + +1.202.637.aacc 14:01:40 Present+ Ilkka_Oksanen 14:01:45 zakim, ??P5 is me 14:01:45 +paddy; got it 14:01:47 enewland has joined #dap 14:01:50 +wonsuk 14:01:52 present+ enewland 14:02:10 -wonsuk 14:02:12 zakim, who's on the call? 14:02:12 On the phone I see fjh, alissa, paddy, darobin (muted), Dom, ilkka, +1.202.637.aacc 14:02:15 Suresh has joined #dap 14:02:22 Present+ Wonsuk_Lee 14:02:23 zakim, aacc is probably enewland 14:02:23 +enewland?; got it 14:02:23 zakim, aacc is enewland 14:02:24 sorry, enewland, I do not recognize a party named 'aacc' 14:02:27 Present+ Suresh_Chitturi 14:02:35 marengo has joined #dap 14:02:58 + +1.972.373.aadd 14:03:04 zakim, aadd is Suresh 14:03:05 +Suresh; got it 14:03:09 richt has joined #dap 14:03:14 LauraA has joined #dap 14:03:17 s/Present+ enewland/Present+ Erica_Newland/ 14:03:23 Present+ LauraA 14:03:31 Topic: Agenda Review and Administrative 14:03:38 Agenda additions 14:03:46 +[IPcaller] 14:03:55 a. XACML IPR at beginning of policy section 14:04:00 Zakim, +[IPcaller] is me 14:04:01 sorry, richt, I do not recognize a party named '+[IPcaller]' 14:04:04 b. F2F planning during administrative 14:04:09 darobin has joined #dap 14:04:22 Present+ Richard_Tibbett 14:04:25 c. additional API from Richard http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0254.html 14:04:40 d additional API from James http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0253.html 14:04:52 zakim, who is here? 14:04:52 On the phone I see fjh, alissa, paddy, darobin (muted), Dom, ilkka, enewland?, Suresh, [IPcaller] 14:04:54 On IRC I see darobin, LauraA, richt, marengo, Suresh, enewland, wonsuk, alissa, paddy, Zakim, RRSAgent, fjh, trackbot, lgombos, ilkka, ingmar, dom 14:05:03 -alissa 14:05:19 + +44.777.541.aaee 14:05:22 Zakim, IPCaller is me 14:05:22 +richt; got it 14:05:31 +alissa 14:05:37 zakim, aaee is LauraA 14:05:37 +LauraA; got it 14:05:44 zakim, who is here? 14:05:44 On the phone I see fjh, paddy, darobin (muted), Dom, ilkka, enewland?, Suresh, richt, LauraA, alissa 14:05:46 On IRC I see darobin, LauraA, richt, marengo, Suresh, enewland, wonsuk, paddy, Zakim, RRSAgent, fjh, trackbot, lgombos, ilkka, ingmar, dom 14:05:59 alissa has joined #dap 14:06:10 ScribeNick richt 14:06:18 ScribeNick: richt 14:08:28 [regrets from me for the call next week] 14:08:36 fjh: Need to have stuff in place before the f2f. 14:08:59 fjh: Need some publications. Need actions to be looked at and completed for the f2f 14:09:12 tlr has joined #dap 14:09:22 fjh: Any suggestions for the agenda, please send them ahead of time 14:09:23 + +1.202.637.aaff - is perhaps enewland? 14:09:34 s/agenda/F2F agenda 14:10:16 fjh: F2F agenda items before the next conference call (29th July) would be good. 14:10:19 Is there going to be a dial-in facility at F2F? 14:10:30 The F2F is coming soon, after the next two calls. 14:10:34 +wonsuk 14:10:39 zakim, aaff is jmorris 14:10:39 sorry, enewland, I do not recognize a party named 'aaff' 14:10:47 Suresh, we haven't planned for it, but I can investigate if that's an option 14:10:59 To make the F2F productive we should have material for review in advance, so please complete actions and make proposals before the 7 July call, preferably for next week 14:11:00 thanks Dom, it will be appreciated! 14:11:14 Input on the agenda in advance would be useful, especially topics or proposals 14:11:19 ACTION: Dom to look into calling-in possibilities for London F2F 14:11:20 Created ACTION-199 - Look into calling-in possibilities for London F2F [on Dominique Hazaël-Massieux - due 2010-06-30]. 14:11:28 Please remember to register 14:12:00 DAP registration form http://www.w3.org/2002/09/wbs/43696/london2010/ 14:12:17 TPAC in November, 2nd F2F 14:12:18 http://lists.w3.org/Archives/Member/member-device-apis/2010Jun/0001.html 14:12:33 TOPIC: Minutes Approval 14:12:39 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/att-0177/minutes-2010-06-16.html 14:12:49 RESOLUTION: 16th June Minutes approved 14:13:00 TOPIC: Policy Framework Updates 14:13:08 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0204.html 14:13:19 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0216.html 14:13:21 fjh: Laura did a few updates based on Dom's comments. FJH made a few updates also. 14:13:41 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0235.html 14:13:43 fjh: Additional comments on the framework received on the list. 14:13:51 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0238.html 14:14:00 fjh: Where are we at with this? 14:14:18 paddy: Based on how the document has been put together (from input spec sources) 14:14:32 paddy: Need to go back and make sure references/terminology is clear. 14:15:04 fjh: For the doc, if we make the changes can we publish 14:15:07 paddy: yes 14:15:11 -1 on rushing the publication for next week 14:15:12 q+ 14:15:26 +1 to Dom 14:15:26 fjh: Would like to publish next week 14:15:53 dom: Still a lot of clarification required before we go to FPWD 14:16:22 fjh: we have never published. Would like to get something out there. Although we have a lot of feedback to get through 14:16:39 dom: For FPWD we must agree on the scope of the work 14:16:50 dom: It's not clear we're all clear on the scope at this stage 14:17:18 FWIW, the API docs took a long time to get to FPWD 14:17:56 dom: spec is difficult to understand. perhaps not clear enough on the scope at this stage 14:18:30 fjh: let's make the changes and hope we can publish soon. 14:18:49 action: paddy to provide clarifications to framework document as well as to address concerns raised by Suresh http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0235.html 14:18:49 Sorry, amibiguous username (more than one match) - paddy 14:18:49 Try using a different identifier, such as family name or username (eg. pbyers, pbyers2) 14:19:03 ACTION: pbyers2 to provide clarifications to framework document as well as to address concerns raised by Suresh http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0235.html 14:19:04 Created ACTION-200 - Provide clarifications to framework document as well as to address concerns raised by Suresh http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0235.html [on Paddy Byers - due 2010-06-30]. 14:19:23 fjh: will defer this decision for another time (ACTION-200) 14:19:42 q? 14:19:45 ack suresh 14:20:01 suresh: agrees with Dom. having a good draft is better than going through feedback 14:20:08 q- 14:20:24 fjh: understands that rationale. will wait on ACTION-200 14:20:25 TOPIC: Policy Profile 14:20:30 tlr has joined #dap 14:20:31 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0216.html 14:20:41 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0237.html 14:20:53 fjh: fixed validation problems and attributes have been merged to a single set of definitions. 14:21:14 fjh: doc is in better shape. Dom has done some edits also. 14:21:43 fjh: XACML works under the Royalty Free mode on Limited Terms 14:21:48 ACTION-185? 14:21:48 ACTION-185 -- Frederick Hirsch to investigate IP status for XACML -- due 2010-06-16 -- PENDINGREVIEW 14:21:48 http://www.w3.org/2009/dap/track/actions/185 14:22:04 fjh: XACML 1.0 and 2.0 done under original policy. Latest spec is under RAND policy 14:22:22 re the impact of the IPR policy of XACML 2.0 on our work: http://www.w3.org/2003/12/22-pp-faq.html#outside-normative-ref says "W3C Recommendations may include normative references to standards or technologies developed outside of W3C. However, the Working Group should keep in mind the importance of royalty-free implementations of Web standards. In the event it becomes clear that the licensing status of those externally-developed technologies could become a barrier t 14:22:22 o implementation of the technology according to the W3C Royalty-Free (RF) Licensing Requirements, W3C may choose not to publish the document or may launch a PAG." 14:22:30 fjh: Questions whether XACML 3.0 will be appropriate depending on the timelines of the WG 14:22:50 q? 14:22:56 q+ 14:23:00 ack Suresh 14:23:45 suresh: Had a look at XACML IPR. Initially looked RF. Originally RAND. Unclear if RAND commitments will carry on in to RF domain 14:24:20 suresh: unclear if they have a Patent Exclusion Policy like W3C 14:24:55 fjh: there was a transition period. Originally RAND. Now there are new modes and there is a transition period. 14:25:30 fjh: TCs that existed before the transition operated under the old mode. Obligations during transition are still under original obligations i.e. RAND (not necessarily RF) 14:25:40 fjh: new stuff will be under RF terms 14:26:18 fjh: Looking at XACML 3.0. Will feedback how that may relate to all this. 14:27:06 suresh: If we make references to XACML we need to be careful. At this point, perhaps we should make it an informative reference. 14:27:10 fjh: that's what we have now 14:27:24 q+ 14:27:48 fjh: rather than discussing this complex IPR, let's focus on the technology for now. 14:28:11 fjh: If you do something similar it may still be subject to patents. It's not necessarily just a XACML issue. 14:28:43 fjh: we may end up doing something different but perhaps premature to get so deep in to this IPR discussion 14:29:09 we need to be consicous on the implications upfront 14:29:17 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0228.html 14:29:39 (the schema was actually mostly duplicated effort) 14:29:46 fjh: {goes through Dom's email} 14:29:49 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0232.htm 14:29:59 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0236.html 14:30:00 jsalsman has joined #dap 14:30:33 zakim, who's noisy? 14:30:44 dom, listening for 10 seconds I heard sound from the following: Dom (26%), richt (21%), fjh (10%), Suresh (72%) 14:30:49 dom: I went through the documents last week in some detail. I now have an understanding of how it is supposed to work. 14:30:54 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0257.html 14:30:57 + +1.650.335.aagg 14:31:16 Present+ James_Salsman 14:31:24 dom: we have a lot of things to work through before it is useful for both web apps and widgets 14:31:36 dom: led me to renew the focus on a smaller scope to begin with. 14:31:47 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0257.html 14:31:54 ...and perhaps look at interchange afterwards. 14:32:29 fjh: I'm not clear on why a profile wasn't done rather than a copy/paste/modify. 14:33:08 fjh: Do we need the power of XACML for our purposes? A lot dealing with the trust domain (e.g. from a certificate) in XACML 14:33:21 fjh: perhaps that is not necessary for our purposes 14:33:38 fjh: Nokia input did something much simpler than this 14:33:44 (I think the point of that XACML modification is precisely because the full power of XACML wasn't needed) 14:34:20 fjh: what do we lose with some more simplicity? Do we need all the complexity e.g. combining algorithms, policy sets, etc. Will help when we get to testing 14:35:15 dom: If we are going to allow for external policy providers change the way user agents react to API calls, we need to understand the current situation for .e.g browser for API calls. 14:36:07 dom: e.g. a current browser may prompt user for a specific API call. For other interfaces there is no JS interface. e.g. cannot access a file object via JS..only available through input file element 14:36:23 dom: perhaps not clear that we can reduce this to a set of all/deny permits in a XACML profile. 14:36:30 zakim, who is here? 14:36:30 On the phone I see fjh, paddy, darobin, Dom, ilkka, enewland?, Suresh, richt, LauraA, alissa, enewland?, wonsuk, +1.650.335.aagg 14:36:33 On IRC I see jsalsman, tlr, alissa, darobin, LauraA, richt, marengo, Suresh, enewland, wonsuk, paddy, Zakim, RRSAgent, fjh, trackbot, lgombos, ilkka, ingmar, dom 14:36:44 dom: we need to first understand the current detail in user agents interacting with existing APIs 14:36:54 that's me at 650 14:37:25 q+ 14:37:55 dom: It's not a case of browsers/widgets. Used browser as the starting point. A lot of experience in defining policies. Points on list should also apply to widgets cases. 14:37:59 [using browsers as a benchmark makes a lot of sense to me] 14:38:08 (sorry I'm late, local minor emergency) 14:38:27 zakim, aaff is jmorris 14:38:27 sorry, enewland, I do not recognize a party named 'aaff' 14:38:48 dom: Interested in figuring out the scope of this work. Not planning on editing at this stage. 14:39:01 ack paddy 14:39:07 fjh: If you can help answer some of the questions you raised on the mailing list, that would be helpful. 14:39:41 paddy: Agree with Dom's comment. Sounds like we need to further define the model. We were going to break model in two parts: 14:39:51 ... trust domain and permissions given to those trust domains. 14:39:59 ...not done yet. That may take us away from XACML. 14:40:39 ....when we did the BONDI docs we put text to further explain what 'prompt' actually meant. 14:41:29 ...roughly it meant that there is explicit user interaction although there are other requirements. e.g. User revocation was not definable in (XACML) policy 14:41:42 q+ re next steps 14:42:08 ...the best user experience is unclear. Worst thing would be to take away the best user experience in the absence of a best current practice on user experience. 14:42:23 ...a lot of that context was lost in transition to the W3C document 14:43:04 fjh: Paddy, can you write down a list of the key points considered in BONDI? 14:43:14 fjh: Makes sense to seperate trust domain from access control decision 14:43:39 ...how do we proceed? Brainstorm on the mailing list? 14:43:48 Present+ John_Morris 14:44:27 q+ 14:44:34 ack fjh 14:44:34 fjh, you wanted to discuss next steps 14:44:49 -wonsuk 14:45:30 suresh: important to have some level of access control. do we want to go down to granular details. Will be difficult to enforce as it is currently just a model 14:45:48 s/model/logical model 14:45:53 q+ to say we should start with WARP+ 14:45:58 ack Suresh 14:46:29 fjh: model doesn't change so much if we change the underlying technology. Need to determine trust domain and be explicit about trust domains 14:47:38 ack dom 14:47:38 dom, you wanted to say we should start with WARP+ 14:48:08 action: fjh to review WARP from perspective of use for DAP 14:48:08 Created ACTION-201 - Review WARP from perspective of use for DAP [on Frederick Hirsch - due 2010-06-30]. 14:48:17 dom: instead of focusing on interchangable policies, instead look at what WARP currently allows for Widgets. Look what is missing for more detailed policies to be built around them. 14:48:28 ....once that is clarified, look at thow we can make these policies insterchangable 14:48:28 flowcharts could be good. This might be an opportunity to simplify behaviors and add representation later 14:48:34 what is WARP? 14:48:52 -> http://www.w3.org/TR/widgets-access/ WARP 14:48:53 suresh: agree with Dom. 14:49:21 suresh: Looking at WARP, more than declaring intent. It talks about UA policy allow/deny. 14:49:35 proposed RESOLUTION: WG agrees to focus on policy model before details 14:49:56 RESOLUTION: WG agrees to focus on policy model before details 14:50:42 TOPIC: Features and Capabilities 14:50:52 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0205.html 14:50:59 fjh: Discussion on the list. 14:51:44 q+ to leave the tooling for later, note that WebIDL option only works for our own APIs 14:51:46 fjh: Can we automate WebIDL wrt/ features and capabilities 14:51:54 ack dom 14:51:54 dom, you wanted to leave the tooling for later, note that WebIDL option only works for our own APIs 14:52:18 dom: ther emay be ways for automation but we are a long way from talking about tooling at this point. 14:52:30 dom: for features and capabilities, we need to really focus on how it applis 14:52:36 a/applis/applies 14:53:04 ...policy framework is not only intended to apply to our APIs, but to other APIs (e.g. Geolocation?) 14:53:10 [I don't want to get into tooling right now, but I'd like to point out that it's easy to create "Web IDL Component Designators" in order to add extended attributes to parts of a Web IDL] 14:53:22 ...and to other groups/APIs to which we have no link at all. 14:53:55 ...when we reach last call I think we should approach this. Right now it may be too early. 14:54:20 fjh: so I understand, we shouldn't build a decision on the current APIs until the policy model is better scoped/defined. 14:54:59 fjh: any simplifications we can do will help the WG. If we can simplify we should do so. 14:55:00 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0212.html 14:55:26 zakim, mute me 14:55:26 Dom should now be muted 14:56:09 [e.g. { action: "addExtAttr", path: "/interface:Unicorn/operation:neigh(float)", content: "[RestID=name]" }] 14:56:12 jmorris has joined #dap 14:57:09 Present+ John_Morris 14:57:56 TOPIC: FPWD Policy Framework 14:58:12 zakim, unmute me 14:58:12 Dom should no longer be muted 14:58:17 fjh: If we don't publish in the next couple of weeks we will publish at the F2F 14:58:33 dom: we will be publishing 2 or 3 specs next week. 14:59:00 dom: no pressure to publish in the next couple of weeks 15:00:35 Topic: APIs 15:00:39 soonho has joined #dap 15:01:25 Was ACTION-191 approved? 15:01:25 darobin: perhaps we can't get througg the agenda as published in the remaining time for the call today 15:01:35 yes 15:01:35 darobin: James, you wanted to bring up your action items? 15:01:47 zakim, mute me 15:01:47 Dom should now be muted 15:01:59 ACTION-191? 15:01:59 ACTION-191 -- James Salsman to send pre-LC editorial comments on system-info and camera/Media Capture -- due 2010-06-16 -- CLOSED 15:01:59 http://www.w3.org/2009/dap/track/actions/191 15:02:23 jsalsman: Action has been approved. Just wanted to check if it has been included in the spec. 15:02:53 darobin: any opinions on this? 15:03:01 Zakim, enewland? is jmorris 15:03:01 sorry, jmorris, I do not recognize a party named 'enewland?' 15:03:08 jsalsman: hope this is correct as per the action item 15:03:33 suresh: obviously free-form is not great but when specifying the properties are we specifying the formats? 15:03:35 zakim, enewland is jmorris 15:03:35 sorry, fjh, I do not recognize a party named 'enewland' 15:03:35 Zakim, enewland is jmorris 15:03:36 sorry, jmorris, I do not recognize a party named 'enewland' 15:03:53 suresh: MIME type needs to be a certain format 15:04:03 jslasman: included a format for speex (sp?) 15:04:14 jsalsman: unencumbered format 15:04:20 audio/x-speex 15:05:18 ACTION: Roll in changes from the outcome of ACTION-191 15:05:18 Sorry, couldn't find user - Roll 15:05:33 ACTION: Dzung to include changes from ACTION-191 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0253.html 15:05:34 Created ACTION-202 - Include changes from ACTION-191 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0253.html [on Dzung Tran - due 2010-06-30]. 15:06:16 q+ 15:06:25 darobin: do we need to seperate each media type per entry? 15:06:41 suresh: yes, otherwise we need to parse the whole string 15:07:04 attribute DOMString[] compFormats; 15:07:15 "audio/x-speex;quality=7;bitrate=16000, audio/ogg" 15:07:25 ["audio/x-speex;quality=7;bitrate=16000", "audio/ogg"] 15:07:47 darobin: issue in the provided code snippet should be amended. 15:09:51 darobin: Sticking to strings is common enough at this point 15:10:07 darobin: Let's stick to strings. If it's a problem we can revisit this 15:10:19 zakim, mute me 15:10:19 ack ill 15:10:20 jsalsman should now be muted 15:10:26 ack ilk 15:10:49 illka: jsalman's last comment about Media Capture API. Proposal for impl to choose the audio format to use? 15:11:10 suresh: aid to check which formats are supported by the system. 15:11:47 darobin: example gives 'audio/x-wav' as an example...proposal is to change to another format? 15:12:15 darobin: idea is not to refer too much to proprietary formats. even if impl choose to support them. 15:12:24 yes, use good examples, especially when union types can be replaced with open standards 15:12:55 Topic: Implied Auth Model for Sys Info 15:14:14 sysinfo.authfor("Power", "Light", "Network") 15:14:23 is this an optimization , box car of requests 15:15:27 sysinfo.get({ Network: function (res, err) {...}, Power: function (res, err) {....}); 15:17:23 the second is possibly more interesting: variadic sysinfo.get attributes. 15:17:35 q+ 15:18:15 q+ 15:18:26 ack jmorris 15:18:36 q- 15:18:43 that's my understanding, darobin. one prompt is too little, prompt per sysinfo property is too much. 15:18:45 ack alissa 15:19:08 s/ that's/ that's/ 15:20:40 q+ 15:22:33 ack jmorris 15:24:03 let's take it back to the list 15:24:14 jmorris suggests could have groupings for environmental vs device capabilities etc 15:25:07 sysinfo not to be published right now, still being discussed 15:25:53 +1 to publish snapshot of contacts 15:27:44 suresh asks how to tell where data comes from 15:28:05 richard talks about mozilla implementation, provides dashboard to identify sources 15:28:20 richard notes, not exposed to api 15:30:27 ack me 15:31:54 PROPOSED RESOLUTION: Publish WD of Contacts with note indicating that some parts, including schema, are still in flux 15:32:37 disagree with the resolution. An intermediate draft is in flux by default 15:33:30 RESOLUTION: Publish WD of Contacts with note indicating that some parts, including schema, are still in flux 15:33:37 -alissa 15:33:40 -jsalsman 15:33:42 -enewland? 15:33:44 -Suresh 15:33:46 -ilkka 15:33:46 [I'll note that there won't be staff contacts to help through the publication process, hopes that's ok] 15:33:47 -fjh 15:33:47 -paddy 15:33:48 -LauraA 15:33:48 -richt 15:33:50 -Dom 15:33:53 rrsagent, generate minutes 15:33:53 I have made the request to generate http://www.w3.org/2010/06/23-dap-minutes.html fjh 15:34:20 -enewland? 15:34:55 s/I keep getting kicked off the bridge; has the code changed?// 15:35:16 Present+ Erica_Newland 15:35:27 Present- enewland 15:35:37 s;s/Present+ enewland/Present+ Erica_Newland/;; 15:36:31 s/barrier t/barrier to/ 15:36:51 s/o implementation/implementation/ 15:37:14 s/(sorry I'm late, local minor emergency)// 15:37:24 s/that's me at 650// 15:37:52 s/applis/applies/ 15:38:05 s;a/applis/applies;; 15:38:26 rrsagent, generate minutes 15:38:26 I have made the request to generate http://www.w3.org/2010/06/23-dap-minutes.html fjh 15:39:01 s/ScribeNick richt// 15:39:20 disconnecting the lone participant, darobin, in UW_DAP()10:00AM 15:39:21 UW_DAP()10:00AM has ended 15:39:25 Attendees were fjh, alissa, darobin, Dom, +358.504.86aabb, ilkka, +1.202.637.aacc, paddy, wonsuk, enewland?, +1.972.373.aadd, Suresh, +44.777.541.aaee, richt, LauraA, 15:39:28 ... +1.202.637.aaff, +1.650.335.aagg, jsalsman 15:39:35 rrsagent, generate minutes 15:39:35 I have made the request to generate http://www.w3.org/2010/06/23-dap-minutes.html fjh 15:39:43 ah, yeah, remembering to hang up is a feature 15:39:52 fjh: pointer? 15:41:36 odd, only on my local copy. when checked in no problem. 15:41:53 must need to reload the scripts. let me check 15:42:21 nope, restarted browser and still see it 15:42:25 locally only 15:42:49 empty cache and still see it locally 15:43:13 I think it's probably a local-only bug 15:43:22 probably Safari being confused by file: 15:43:27 got it. it was pulling in the local scrpt for some reason. 15:43:28 as always 15:43:37 refreshed local build directory from CVS now works fine. 15:43:42 ah cool 15:43:47 thanks, apologies for the interruption 15:43:50 I would love to publish a REC in 1899 though 15:43:55 :) 15:44:01 a first 15:44:28 thanks for the script update 15:44:35 a pleasure 15:44:56 I need to find two-three days in a row to complete the transition to ReSpec 2, it's nicer and stabler 15:45:10 cool, didn't know there was one 16:25:44 wonsuk has left #dap 17:50:24 Zakim has left #dap