16:53:37 RRSAgent has joined #tagmem 16:53:37 logging to http://www.w3.org/2012/05/24-tagmem-irc 16:53:50 zakim, who's here 16:55:44 Zakim has joined #tagmem 16:56:59 zakim, this will be tag_weekly 16:56:59 ok, masinter, I see TAG_Weekly()1:00PM already started 16:57:07 zakim, who's here 16:57:07 masinter, you need to end that query with '?' 16:57:10 zakim, who's here? 16:57:10 On the phone I see Masinter 16:57:11 On IRC I see RRSAgent, masinter, JeniT, noah_lunch, trackbot, plinss, Yves 16:57:54 +plinss 16:59:28 +Noah_Mendelsohn 16:59:37 zakim, Noah_Mendelsohn is me 16:59:37 +noah; got it 17:00:16 zakim, who is here? 17:00:16 On the phone I see Masinter, plinss, noah 17:00:17 On IRC I see RRSAgent, masinter, JeniT, noah, trackbot, plinss, Yves 17:01:02 Ashok has joined #tagmem 17:01:07 +??P11 17:01:31 jar has joined #tagmem 17:01:56 +Ashok_Malhotra 17:01:57 +TimBL 17:02:05 +jar 17:02:26 timbl has joined #tagmem 17:02:33 scribe: Jonathan Rees 17:02:44 trackbot, start meeting 17:02:46 RRSAgent, make logs public 17:02:48 Zakim, this will be TAG 17:02:48 ok, trackbot, I see TAG_Weekly()1:00PM already started 17:02:49 Meeting: Technical Architecture Group Teleconference 17:02:49 Date: 24 May 2012 17:02:59 scribenick: jar 17:03:14 agenda: http://www.w3.org/2001/tag/2012/05/24-agenda 17:03:23 topic: Convene 17:03:58 regrets from Robin for today 17:04:17 Regrets: Yves Lafon, Henry Thompson 17:04:25 Chair: Noah Mendelsohn 17:04:39 No regrets for next week 17:04:50 topic: Approve minutes of prior meeting 17:04:55 http://www.w3.org/2001/tag/2012/05/17-minutes 17:05:09 timbl has joined #tagmem 17:05:14 RESOLVED: approve http://www.w3.org/2001/tag/2012/05/17-minutes as record of that meeting 17:05:31 topic: Administrative items 17:06:15 noah: F2F - think about taking on vendor prefixes 17:06:38 ACTION-697? 17:06:38 ACTION-697 -- Larry Masinter to prepare for discussion of CA infrastructure weakness (e.g. DANE) -- due 2012-05-29 -- OPEN 17:06:38 http://www.w3.org/2001/tag/group/track/actions/697 17:07:18 lm: I'm not going to do a lot more on DANE, not much we can do 17:07:36 s/more/more right now/ 17:07:41 close ACTION-697 17:07:41 ACTION-697 Prepare for discussion of CA infrastructure weakness (e.g. DANE) closed 17:08:19 . ACTION: Larry to keep an eye on issues relating to CA infrastructure weakness, including DANE - Due 2012-09-01 17:08:26 ACTION: Larry to keep an eye on issues relating to CA infrastructure weakness, including DANE - Due 2012-09-01 17:08:26 Created ACTION-710 - keep an eye on issues relating to CA infrastructure weakness, including DANE [on Larry Masinter - due 2012-09-01]. 17:08:31 s/not much we/doesn't seem much the TAG/ 17:08:51 ACTION-690? 17:08:51 ACTION-690 -- Jeni Tennison to sort next steps on Fragment Identifiers and Mime Types -- due 2012-05-05 -- PENDINGREVIEW 17:08:51 http://www.w3.org/2001/tag/group/track/actions/690 17:09:03 ACTION-672? 17:09:03 ACTION-672 -- Jeni Tennison to work with PLH to create W3C-sponsored registry of HTML extensions, and get that referenced from HTML media type registration, per http://lists.w3.org/Archives/Public/www-tag/2012Jan/0048.html -- due 2012-05-29 -- OPEN 17:09:03 http://www.w3.org/2001/tag/group/track/actions/672 17:09:55 I thought the ball was in my court to mark the product page approved 17:10:03 jt: Re fragids and mime types, I did a product page, needs to be revised per comments 17:10:28 nm: I thought we had approved the product page & the NM was supposed to do clerical work. Happy with product page 17:10:39 s/the N/that NM/ 17:10:52 Jeni will mark product page as "not draft". 17:11:25 close ACTION-690 17:11:25 ACTION-690 sort next steps on Fragment Identifiers and Mime Types closed 17:11:25 jt: I've done an initial draft that's currently with Larry. I can take an action to provide it for F2F 17:11:52 lm: I'll try to get back to you [JT] by this weekend, otherwise just go ahead and publish 17:12:38 nm: On the master work plan page we sometimes pull out 1-2 next steps, pls check that 17:13:08 jt: Re action 672, let's talk about that when it's done 17:13:52 -jar 17:13:54 nm: I will do a local arrangements page for the F2F 17:14:19 +jar 17:15:24 Regrets LM for 3rd day of F2F 17:16:36 +1 17:16:37 topic: Vendor prefixes 17:17:15 lm: Because it was a narrow enough use case, and the community was making progress, this seemed interesting 17:17:47 lm: There are differences of opinion as to whether old stuff *should* go away ever [to force updates] 17:18:13 lm: The question is whether the CSS experience could apply in other situations 17:18:50 q+ to say that I think vendors are thinking in different terms 17:18:50 lm: Interesting proposal to put dates in vendor prefixes. 17:19:15 ack next 17:19:16 noah, you wanted to say that I think vendors are thinking in different terms 17:19:24 plinss: I don't think Apple has publicly said they're never going to drop things, seems flexible 17:19:38 plinss: Mozilla, Opera have been aggressive about dropping prefixes 17:20:49 nm: Difference between architecture and market pressure [?] - difficult to deal with market pressure issues in the TAG 17:21:17 lm: I think it's part of designing standards and extensibility regimes. It's important what vendors say, not just what they do. 17:21:36 lm: Authors aren't in the room, so we need to look for a trip point, and in this case it's the browsers 17:22:22 nm: But vendors can't predict how things will go, so won't want to make any promises. Users want to deploy quickly and then never rev 17:23:04 lm: I disagree. Don't think there's lock-in. There's no point in having a deployment plan unless people agree to abide by it 17:24:05 I do understand what you're saying. I'm just skeptical that vendors will do what you want them to do. 17:24:21 …I'm getting mixed messages. What you really want is that when a standard version comes a long, the prefixed version will go away. That means vendor needs to announce intent to remove nonstandard version, when standard arrives 17:24:59 … What I was hoping for was that at least some browsers would have some visual indication of obsolete or soon to be obsolete features 17:25:08 pl: SOme of them do this in their developer views 17:25:16 The message I'm hearing is: many "customers" write their pages once, and then kill the funding or the teams that would be capable of rewriting them to change the spelling of things like CSS prefixes. The economic incentive for them to do that 2nd step isn't there. 17:26:31 nm: Look at how people fund these projects. Right now they use vendor prefixes. Then they move on. What I heard is that the team has disbanded by this time. So this would mean decisions not to use the features in the first place 17:26:59 lm: The use case was when there was a design team that wants continued work 17:27:42 lm: There has to be lead time, so people are prepared 17:27:53 lm: How can we strengthen the will to move on 17:28:01 nm: SOmething the TAG can do? 17:28:20 lm: Right now the deployment plans are locked inside places that are hard to find 17:28:52 nm: Peter, how is CSS working on this issue? 17:29:24 pl: We see most of the problem as education. Initiative to teach comes from the community, we try to correct them 17:29:52 i thought we could document the issues around deployment plans, and point out best practices about how to design extensibility methods 17:30:14 that's more general than CSS; we might look at why it is easier because of the "cascading" of style sheets 17:30:16 nm: So what can we do. Isn't CSS already doing a lot 17:31:02 pl: One way the TAG could help CSS is re proposal from Florian. I think his proposal would be harmful, and it would be useful if the TAG had an opinion on it 17:31:02 TAG could evaluate Florian's proposal and other alternatives? 17:31:39 if we worked on this, it should be rec-track 17:32:35 lm: Is this is the kind of thing we work on, we should get wide community approval, head for Rec track. But from a perspective that doesn't tie it to CSS 17:32:50 lm: Cascading makes this unique 17:33:34 is this a lesson for XML-ER? 17:33:52 nm: We've tried to crack distributed extensibility nut many times. Agree that focus here is good. Feels like next step should come from CSS WG 17:34:09 for example, if this extensibility method doesn't apply to XML, is there a refocus of XML dealing with un-recognized elements to make it more extensibile? 17:34:18 s/sibile/sible/ 17:34:32 nm: Worried about umpteenth frontal assault on issue 17:34:35 q+ 17:34:54 ack next 17:34:58 lm: Looking at specific cases is a good way to deal with general cases (Polya How to Solve It) 17:35:20 tbl: Not a good time for TAG to generalize, good to look at cases 17:35:25 i'm a big fan of Polya -- here is a specific instance where a solution is tractable. The universal problem was too hard, but we might make progress on this one 17:35:50 nm: Should we do anything else re Florian's proposal? 17:36:10 i think one of the big questions is whether "old stuff goes away" -- is it, or is it not, reasonable to assume that once a usage becomes significant it will never get dropped? 17:36:37 jt: Didin't PL just say it would be helpful for the TAG to evaluate Florian's proposal? 17:37:25 i'd like to see the extensibility mechanism in CSS documented 17:37:46 in a way that actually corresponds to what CSS WG thinks the policy is 17:38:24 lm: I'd like to see the CSS deployment policy to be written up, in one place. I don't think there is a document that describes the policy 17:38:54 lm: Reluctant to compare a proposal to the current policy, in the absence of a document describing the policy 17:40:28 pl: It would be sensible for the WG to do this 17:41:07 lm: Peter, what do you want to do? 17:42:26 pl: I'm not necessarily endorsing the current policy, just wanting to comment on Florian's proposal 17:42:44 . ACTION: Peter to report on CSS WG plans for documenting policies relating to deployment and withdrawal of vendor-prefixed identifiers - Due 2012-06-11 17:42:59 ACTION: Peter to report on CSS WG plans for documenting policies relating to deployment and withdrawal of vendor-prefixed identifiers - Due 2012-06-11 17:42:59 Created ACTION-711 - report on CSS WG plans for documenting policies relating to deployment and withdrawal of vendor-prefixed identifiers [on Peter Linss - due 2012-06-11]. 17:43:24 topic: Pending review action items 17:43:35 http://www.w3.org/2001/tag/group/track/actions/pendingreview 17:43:55 ACTION-541? 17:43:55 ACTION-541 -- Jeni Tennison to helped by DKA to produce draft on technical issues relating to copyright/linking -- due 2012-05-15 -- OPEN 17:43:55 http://www.w3.org/2001/tag/group/track/actions/541 17:44:03 JT: We agreed to bump 17:44:30 ACTION-541 Due 2012-08-01 17:44:30 ACTION-541 Helped by DKA to produce draft on technical issues relating to copyright/linking due date now 2012-08-01 17:44:38 ACTION-6190? 17:44:38 ACTION-6190 does not exist 17:44:41 ACTION-610? 17:44:42 ACTION-610 -- Jeni Tennison to draft initial cut at http://www.w3.org/standards/webarch/metaformats -- due 2012-04-17 -- OPEN 17:44:42 http://www.w3.org/2001/tag/group/track/actions/610 17:44:54 ACTION-610 Due 2012-05-29 17:44:54 ACTION-610 Draft initial cut at http://www.w3.org/standards/webarch/metaformats due date now 2012-05-29 17:45:11 ACTION-677? 17:45:11 ACTION-677 -- Noah Mendelsohn to contact HTML WG co-chairs to ask about timing for output of Encrypted Media TF -- due 2012-04-24 -- PENDINGREVIEW 17:45:11 http://www.w3.org/2001/tag/group/track/actions/677 17:45:34 Reply from Maceij Stachowiak: 17:45:34 The current status is: 17:45:34 - The Task Force has been proposed, but not yet created 17:45:34 - We posted a Call for Consensus on a proposal to create the Task Force 17:45:34 - There have been numerous objections, statements of support, and considerable discussion 17:45:34 - On request, and based on the amount of discussion, the Call for Consensus has been extended until at least April 18th, and may be extended further. 17:45:59 close, don't see any follow-ups 17:46:03 nm: I did this one. Anyone want followup? 17:46:20 close ACTION-677 17:46:20 ACTION-677 Contact HTML WG co-chairs to ask about timing for output of Encrypted Media TF closed 17:46:35 ACTION-682? 17:46:35 ACTION-682 -- Jonathan Rees to suggest to TAG sections of HTTPbis specification that TAG should review -- due 2012-04-17 -- PENDINGREVIEW 17:46:35 http://www.w3.org/2001/tag/group/track/actions/682 17:47:08 JAR: Mark Nottingham said sections in question will likely be changed. May not be time to comment. 17:47:12 there was also an objection that it wasn't really in scope for the document or IETF 17:47:41 s/document/HTTP document/ 17:48:12 ACTION-682? 17:48:12 ACTION-682 -- Jonathan Rees to suggest to TAG sections of HTTPbis specification that TAG should review -- due 2012-07-10 -- OPEN 17:48:12 http://www.w3.org/2001/tag/group/track/actions/682 17:48:25 ACTION-687? 17:48:25 ACTION-687 -- Noah Mendelsohn to look for opportunities to discuss putting forward something to the AB about the Process and the failed reference from REC drafts to expired RFCs as a side-effect of scope creep etc. -- due 2012-05-22 -- PENDINGREVIEW 17:48:25 http://www.w3.org/2001/tag/group/track/actions/687 17:48:39 http://www.w3.org/mid/4FA063B3.4080507%2540arcanedomain.com 17:49:07 Proposal from Noah (25 April): http://lists.w3.org/Archives/Public/www-tag/2012Apr/0185.html 17:49:34 Larry's note: http://lists.w3.org/Archives/Public/www-tag/2012Apr/0207.html 17:49:46 " 17:49:46 I suggest the tag ask the AB more generally about the process for insuring our resolution affects the rec process. At what point are sppecs required to have stable references, and what are the explicit exception guidelines?" 17:52:22 lm: Henry said he wanted to review the old advice he drafted. We agreed to let QA document stand for now, but that we should pick it up at some point [?] 17:52:45 ACTION-669? 17:52:45 ACTION-669 -- Henry Thompson to review http://www.w3.org/TR/qaframe-spec/#ref-define-practice and see whether TAG needs to do more on references to evolving specs Due: 2012-08-01 -- due 2012-06-01 -- OPEN 17:52:45 http://www.w3.org/2001/tag/group/track/actions/669 17:52:57 lm: That's the one 17:53:54 lm: Suggest adding to that action something about tracking down the process question too 17:54:52 lm: Link to the emails too in that note? 17:54:55 close ACTION-687 17:54:55 ACTION-687 Look for opportunities to discuss putting forward something to the AB about the Process and the failed reference from REC drafts to expired RFCs as a side-effect of scope creep etc. closed 17:55:00 JR: they're linked from 687 17:55:24 topic: Overdue action items 17:55:40 nm: Especially looking for actions that lead into the F2F 17:55:40 http://www.w3.org/2001/tag/group/track/actions/overdue?sort=owner 17:55:48 -JeniT 17:56:56 nm: A high proportion of these are owned by people not on call 17:57:28 action-606 17:57:35 Larry: ACTION-685 17:57:51 action-543 17:57:56 jr: My actions related to f2f: 704, 201. Action in progress not related to F2F: 695 17:57:58 ACTION-693 was raised in the context of storage, I think. 17:58:17 ACTION-606? 17:58:17 ACTION-606 -- Peter Linss to invite I18N and other concerned groups to provide written technical input as prep to discussion with the TAG regarding unicode normalization -- due 2012-05-23 -- OPEN 17:58:17 http://www.w3.org/2001/tag/group/track/actions/606 17:58:22 ACTION-585? 17:58:22 ACTION-585 -- Larry Masinter to meet with Yves prior to the IETF document to review this draft-freed-media-type-regs-00. -- due 2011-07-28 -- CLOSED 17:58:22 http://www.w3.org/2001/tag/group/track/actions/585 17:58:25 jr: Planning to work on 201 soon but probably not ready for F2F 17:58:25 ACTION-543? 17:58:25 ACTION-543 -- Peter Linss to propose addition to MIME/Web draft to discuss sem-web use of fragids not grounded in media type -- due 2012-05-23 -- OPEN 17:58:27 http://www.w3.org/2001/tag/group/track/actions/543 17:58:32 ACTION-704? 17:58:32 ACTION-704 -- Jonathan Rees to with help from Jeni and Henry to try to identify next steps for moving forward on httpRange-14 -- due 2012-05-15 -- OPEN 17:58:34 http://www.w3.org/2001/tag/group/track/actions/704 17:58:39 ACTION-201? 17:58:39 ACTION-201 -- Jonathan Rees to report on status of AWWSW discussions -- due 2012-05-15 -- OPEN 17:58:39 http://www.w3.org/2001/tag/group/track/actions/201 17:58:52 ACTION-693?] 17:58:54 ACTION-693? 17:58:54 ACTION-693 -- Robin Berjon to draft scope and goals for the Patterns/Pitfalls work in local/remote storage synch -- due 2012-04-19 -- OPEN 17:58:54 http://www.w3.org/2001/tag/group/track/actions/693 17:59:06 ACTION-606? 17:59:06 ACTION-606 -- Peter Linss to invite I18N and other concerned groups to provide written technical input as prep to discussion with the TAG regarding unicode normalization -- due 2012-05-23 -- OPEN 17:59:06 http://www.w3.org/2001/tag/group/track/actions/606 18:00:10 ACTION-606? 18:00:10 ACTION-606 -- Peter Linss to invite I18N and other concerned groups to provide written technical input as prep to discussion with the TAG regarding unicode normalization -- due 2012-05-23 -- OPEN 18:00:10 http://www.w3.org/2001/tag/group/track/actions/606 18:00:42 what input on I18N and normalization does the TAG want? 18:01:17 this is on comparison & normalization? 18:01:57 lm: I'm interested & willing to talk about unicode normalization. Hard to tell whether this is about CSS selectors 18:02:21 pl: Selectors is just one of many places. Question is early, late, very late normalization 18:02:21 i run into this with IRI docs 18:02:40 if we're going to talk about unicode normalization, i'd want to cover IRIs too then 18:03:03 +1 to Larry 18:03:26 lm: If we're going to talk about unicode normalization, the IRI issues need to be in scope 18:03:40 … want to put the IRI comparison document in scope 18:03:54 nm: The action doesn't mention CSS, it's the I8n WG 18:04:10 lm: A month ago they committed to reviwing the IRI documents 18:04:43 nm: I just want to know if this is to be a F2F session 18:04:43 s/they/I18N WG/ 18:05:04 pl: Reluctant to ask them for a document without TAG commitment to work on this [?] 18:05:09 q+ 18:05:30 nm: I don't think their effort will be wasted 18:05:35 ack next 18:05:54 am: Didn't we get something from Addison outlining what the issues were? 18:06:09 http://tools.ietf.org/html/draft-ietf-iri-comparison 18:06:51 and http://tools.ietf.org/html/draft-ietf-iri-comparison-01#section-5.2.2 in particular 18:07:49 nm: Can I delegate to Peter the decision about how to talk to I18N and whether to schedule a F2F session? 18:08:10 . ACTION: Peter to help us decide whether to have F2F session on i18n and comparison Due 2012-05-29 18:08:19 lm: If we decide to talk about it, I'll help prepare, but have no particular opinion on whether to talk about it 18:08:33 . ACTION: Peter to help us decide whether to have F2F session on i18n and comparison Due 2012-05-29 18:08:49 ACTION: Peter to help us decide whether to have F2F session on i18n and comparison Due 2012-05-29 18:08:49 Created ACTION-712 - Help us decide whether to have F2F session on i18n and comparison Due 2012-05-29 [on Peter Linss - due 2012-05-31]. 18:08:57 ACTION-606? 18:08:57 ACTION-606 -- Peter Linss to invite I18N and other concerned groups to provide written technical input as prep to discussion with the TAG regarding unicode normalization -- due 2012-05-23 -- OPEN 18:08:57 http://www.w3.org/2001/tag/group/track/actions/606 18:09:19 ACTION-606 Due 2012-06-12 18:09:19 ACTION-606 Invite I18N and other concerned groups to provide written technical input as prep to discussion with the TAG regarding unicode normalization due date now 2012-06-12 18:10:43 http://www.w3.org/2001/tag/group/track/actions/open?sort=owner 18:10:50 nm: We'll be talking about the high priority items for sure, just trying to find other things we ought to talk about at the F2F, that we might have forgotten about 18:11:19 ACTION-694? 18:11:19 ACTION-694 -- Noah Mendelsohn to work up simple intro to http+aes uri scheme and schedule discussion, possibly with PLH -- due 2012-05-29 -- OPEN 18:11:19 http://www.w3.org/2001/tag/group/track/actions/694 18:12:24 This is about the proposed acct: URI scheme http://lists.w3.org/Archives/Public/www-tag/2012May/0097.html 18:14:12 nm: Tim, last week we had a F2F planning session, and the agenda looked thin. So I scheduled today's discussion of pending and overdue actions 18:14:38 ACTION-543? 18:14:38 ACTION-543 -- Peter Linss to propose addition to MIME/Web draft to discuss sem-web use of fragids not grounded in media type -- due 2012-05-23 -- OPEN 18:14:38 http://www.w3.org/2001/tag/group/track/actions/543 18:15:57 ACTION-543 relates to what Jeni's doing right? 18:16:00 LM: Right. 18:16:03 lm: When I saw 543 I thought it was about Jeni's draft 18:16:22 lm: Just change the title 18:17:02 ACTION-543? 18:17:02 ACTION-543 -- Peter Linss to propose addition to Fragid draft to discuss sem-web use of fragids not grounded in media type -- due 2012-07-17 -- OPEN 18:17:02 http://www.w3.org/2001/tag/group/track/actions/543 18:17:18 ACTION-606? 18:17:18 ACTION-606 -- Peter Linss to invite I18N and other concerned groups to provide written technical input as prep to discussion with the TAG regarding unicode normalization -- due 2012-06-12 -- OPEN 18:17:18 http://www.w3.org/2001/tag/group/track/actions/606 18:17:35 ACTION-478? 18:17:35 ACTION-478 -- Jonathan Rees to prepare a second draft of a finding on persistence of references, to be based on decision tree from Oct. 2010 F2F -- due 2012-04-24 -- OPEN 18:17:35 http://www.w3.org/2001/tag/group/track/actions/478 18:17:54 JAR: Working on it, but not for F2F 18:18:03 JAR: Maybe should talk to Larry 18:18:27 ACTION-478 is a MAYBE for the F2F 18:19:08 ACTION-478 Due 2012-07-10 18:19:08 ACTION-478 Prepare a second draft of a finding on persistence of references, to be based on decision tree from Oct. 2010 F2F due date now 2012-07-10 18:19:18 meaning now = which you wish to have persist' 18:19:19 ACTION-704? 18:19:19 ACTION-704 -- Jonathan Rees to with help from Jeni and Henry to try to identify next steps for moving forward on httpRange-14 -- due 2012-05-15 -- OPEN 18:19:19 http://www.w3.org/2001/tag/group/track/actions/704 18:19:34 ACTION-704 Due 2012-05-29 18:19:34 ACTION-704 with help from Jeni and Henry to try to identify next steps for moving forward on httpRange-14 due date now 2012-05-29 18:19:37 s/which/'the associations which/ 18:19:47 ACTION-695? 18:19:47 ACTION-695 -- Jonathan Rees to check with Thomas Roessler on whether security review of CORS is coming up in W3C/IETF liaison -- due 2012-04-19 -- OPEN 18:19:47 http://www.w3.org/2001/tag/group/track/actions/695 18:20:10 JAR: I have pinged him. 18:20:18 ACTION-695 Due 2012-05-29 18:20:18 ACTION-695 Check with Thomas Roessler on whether security review of CORS is coming up in W3C/IETF liaison due date now 2012-05-29 18:20:23 NM: 695 is happening? 18:20:25 JAR: Yes. 18:20:31 ACTION-201? 18:20:31 ACTION-201 -- Jonathan Rees to report on status of AWWSW discussions -- due 2012-05-15 -- OPEN 18:20:31 http://www.w3.org/2001/tag/group/track/actions/201 18:20:47 ACTION-201 Due 2012-06-02 18:20:47 ACTION-201 Report on status of AWWSW discussions due date now 2012-06-02 18:21:00 ACTIOM-650? 18:21:26 i had a interesting convo (cc'd www-archive) on issue-57 and think the distinction between communication & semantics perspectives is key 18:21:37 ACTIOM-650? 18:21:44 ACTION-650? 18:21:44 ACTION-650 -- Jonathan Rees to review what provenance WG is doing with an eye to application to privacy issues -- due 2012-04-17 -- OPEN 18:21:44 http://www.w3.org/2001/tag/group/track/actions/650 18:21:55 ACTION-650 Due 2012-08-01 18:21:55 ACTION-650 Review what provenance WG is doing with an eye to application to privacy issues due date now 2012-08-01 18:22:09 culminating on http://lists.w3.org/Archives/Public/www-archive/2012May/0035.html 18:22:39 -TimBL 18:22:41 ADJOURNED 18:22:41 -Masinter 18:22:42 -plinss 18:22:44 -noah 18:22:54 -Ashok_Malhotra 18:22:56 rrsagent, pointer 18:22:56 See http://www.w3.org/2012/05/24-tagmem-irc#T18-22-56 18:22:56 -jar 18:22:56 TAG_Weekly()1:00PM has ended 18:22:56 Attendees were Masinter, plinss, noah, JeniT, Ashok_Malhotra, TimBL, jar 18:52:17 JeniT has joined #tagmem 20:16:04 JeniT has joined #tagmem 20:29:48 Zakim has left #tagmem