17:43:54 RRSAgent has joined #tagmem 17:43:54 logging to http://www.w3.org/2013/01/24-tagmem-irc 17:44:02 Meeting: TAG 17:44:07 Chair: Noah Mendelsohn 17:44:12 ScribeNick: ht 17:44:16 Scribe: Henry S. Thompson 17:44:22 timbl has joined #tagmem 17:44:23 Agenda: http://www.w3.org/2001/tag/2013/01/24-agenda.html 17:53:48 JeniT has joined #tagmem 17:57:45 hi, thanks JeniT 17:58:08 what's the call-in number? 17:58:12 the call is now right? 17:58:19 Zakim, passcode? 17:58:19 the conference code is 0824 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), Marcos 17:58:21 yes, now 17:58:45 TAG_Weekly()1:00PM has now started 17:58:52 +[IPcaller] 17:59:00 Zakim, +[IPcaller] is me 17:59:00 sorry, Marcos, I do not recognize a party named '+[IPcaller]' 17:59:05 +[IPcaller.a] 17:59:06 Zakim, [IPcaller] is me 17:59:07 +Marcos; got it 17:59:16 +[IPcaller] 17:59:41 am I connected? 17:59:44 +??P5 18:00:00 wycats: are you IPcaller? 18:00:06 JeniT: I have no idea 18:00:11 JeniT: I called via Skype 18:00:14 wycats: say something 18:00:19 yes 18:00:47 Wasn't Marcos [IPCaller]? 18:00:54 yes, originally 18:01:04 wycats: no worries. It's only useful for muting 18:01:09 I can mute myself locally 18:01:12 zakim, who's on the call? 18:01:12 On the phone I see Marcos, JeniT, wycats, ht 18:01:36 hopefully no one hears me chewing away on a pear 18:01:36 Welcome guys -- I guess Noah is running late 18:01:50 +plinss 18:02:06 after last week's debacle I brought in my Blue Snowball to work 18:02:12 hopefully people will be able to hear me better 18:02:16 Marcos: as can I 18:04:25 noah has joined #tagmem 18:04:52 ht: are you scribing today? 18:04:58 I am 18:05:02 All set 18:05:04 will be there shortly....kicking a camper out of a phone room 18:05:15 Ashok has joined #tagmem 18:05:42 dialing 18:05:48 timbl_ has joined #tagmem 18:05:56 +Ashok_Malhotra 18:06:16 noah: there's an email from Amy 18:06:25 noah: re Tim's availability 18:06:27 Ah...haven't looked last hour, 18:06:38 +Yves 18:06:45 +[IPcaller] 18:07:01 + +1.212.565.aaaa 18:07:03 zakim, [IPcaller] is me 18:07:03 +noah; got it 18:07:11 just joined 18:07:13 sorry for the delay 18:09:16 Topic: Admin 18:09:24 Zakim, who is on the call? 18:09:24 On the phone I see Marcos, JeniT, wycats, ht (muted), plinss, Ashok_Malhotra, Yves, noah, slightlyoff 18:10:39 +1, LGTM 18:10:43 RESOLVED: http://www.w3.org/2001/tag/2012/12/20-minutes agreed as a correct record 18:10:59 NM: Two goals for the near term: 18:11:15 ... 1) Focus for the TAG, as membership changes 18:11:45 ... Suggestions welcome, by email, I'll schedule discussion when it looks likely to be productive 18:12:26 ... I need help moving beyond good top-level visions, which need filling in 18:13:02 ... 2) Ongoing work, some nearing completion, others less concrete 18:13:13 ... Need to either complete, or drop 18:13:54 Topic: March F2F location 18:14:13 NM: 17-19 March no longer possible for TimBL 18:14:57 ... And earlier hope that we might try London the preceding weekend is fading 18:15:15 Two options: London Fri-Sun 15-17 & Cambridge 19-21 USA 18:15:22 MC: Any WFM 18:15:27 can make london, although the friday is iffy thanks to TC39 flight back 18:15:34 either ok 18:15:37 unlikely to make cambridge 18:15:38 either works 18:15:40 I am with slightlyoff vis a vis TC39 18:15:57 can make cambridge but will miss one day, can't for london (I can make 1 day) 18:17:11 London No, Cambridge Yes 18:17:14 I can only do 16-17 in London, but I have always been at risk for this meeting 18:17:18 can we push it forward? 18:17:27 How far forward 18:17:27 these weeks seem pretty contended 18:17:28 ? 18:17:44 No, Tim's calendar is incredibly booked. We typically have to get on it 3 months in advance 18:18:20 thanks for the clarification 18:19:21 It looks like slightlyoff and my preference is both London 18:20:12 I am reviewing my calendar 18:20:14 I won't be in Cambridge, no 18:20:29 but i'm not more important than tim...break the tie on his calendar 18:20:32 HST, I can't do Cambridge 18:20:50 I have an existing obligation during the Cambridge time period but I could cancel 18:22:06 no objection, but regrets 18:22:28 no, *my* regrets for not being able to make it...not anyone's fault 18:22:36 RESOLUTION: Next TAG f2f will be Cambridge, MA on 19--21 March 18:23:45 agree with Henry 18:25:35 Topic: Polyglot / DOM 4 issue 18:25:45 q+ to mention XML Core situation 18:25:49 ack next 18:25:50 ht, you wanted to mention XML Core situation 18:25:50 q- 18:25:53 ack ht 18:26:19 Topic: XML Declaration in the DOM 18:26:38 HT: XML Core group is discussing this 18:26:54 HT: There's a concern that XML Declaration is in the XML Infoset 18:27:22 HT: Noah's agenda includes a contested assertion...there's email reporting some current browsers continue to support it. 18:27:42 NM: Should TAG do anything right now? 18:28:12 HT: Tempted to recuse myself. I'm active in the XML Core group. Not clear on TAG-level issue. Dropping it does seem inappropriate, or confusing at best. 18:29:05 I will certainly come back to the TAG on this if I think there's a genuine architectural issue here 18:29:30 I agree with noah 18:29:59 NM: Not clear we're ready to address this -- we would need to have some reason to suppose that we could get community engagement on the TAG's involvement 18:30:45 Topic: Progress on FragID finding 18:30:59 http://www.w3.org/2001/tag/products/fragids.html 18:31:05 NM: We have a project ongoing at the moment: 18:31:34 http://www.w3.org/TR/2012/WD-fragid-best-practices-20121025/ 18:31:36 NM: That page describes goals, deliverables, success criteria 18:31:41 Best Practices for Fragment Identifiers and Media Type Definitions 18:31:52 NM: And we have a public WD 18:31:56 ACTION-772? 18:31:56 ACTION-772 -- Larry Masinter to with help from Jeni to propose CR exit criteria for fragids finding Due 2013-01-08 -- due 2013-01-18 -- OPEN 18:31:56 http://www.w3.org/2001/tag/group/track/actions/772 18:32:13 NM: And the current leading edge is recorded in this action: 18:32:38 NM: We are heading for CR, and we were going to discuss exit criteria at the (cancelled) F2F 18:33:00 JT: I don't know where we are on exit criteria, I don't think I've heard from LM, who has that action 18:33:03 http://www.w3.org/2001/tag/doc/mimeTypesAndFragids 18:33:25 JT: I have made a new editors' draft, which incorporates comments from Richard Cyganek 18:33:35 Cyganiak 18:33:42 http://www.w3.org/2001/tag/doc/mimeTypesAndFragids-2013-01-05.html 18:34:04 s/Cyganek/Cyganiak/ 18:34:28 JT: I think we can still go direct to CR at this point 18:35:02 JT: I'll take over the CR exit criteria action 18:35:14 NM: Thanks 18:35:56 ACTION-772? 18:35:57 ACTION-772 -- Jeni Tennison to with help from Larry to propose CR exit criteria for fragids finding -- due 2013-02-12 -- OPEN 18:35:57 http://www.w3.org/2001/tag/group/track/actions/772 18:36:33 +1 18:36:46 topic: Back to DOM XML Declarations 18:36:59 NM: Notes that Yehuda and Alex favor discussing the DOM at the F2F 18:37:06 q+ 18:37:50 ack next 18:37:55 NM: Happy to have any topic raised by member on our telcon agenda 18:38:10 ... Often good to prepare stuff on telcons before we take them up at a f2f 18:38:24 Topic: Next steps for Publishing and Linking 18:38:40 ACTION-773? 18:38:40 ACTION-773 -- Ashok Malhotra to line up reviewers for Publishing and Linking and invite to participate in F2F -- due 2012-12-20 -- CLOSED 18:38:40 http://www.w3.org/2001/tag/group/track/actions/773 18:39:11 AM: We need a fair amount of work on this still 18:39:26 ... The two editors, AM and LM, are both on their way off the TAG 18:39:45 ... It would be great if a new member would take this up 18:39:54 ... Or perhaps JT could pick it up 18:40:27 NM: Points taken 18:40:53 ... What do people think -- should we continue to pursue this one? If so, then we'll look at how 18:41:03 q+ ht 18:41:06 I'm not personally interested in pursuing it with my time 18:41:08 ack next 18:42:09 HT: I'm conficted. I think it's potentially very important. I get profoundly frustrated when, knowledgeable journalists seem not to distinguish linking and embedding when reporting on serious cases involving extradition or other serious matters. 18:43:05 HT: Yes, different jurisdictions are different. I wish we could do the service of helping. We gave it a good shot. The comments from people who understand better what's neede have not been supportive. So, I'd love to see it move forward, but I can't do it. We may have to drop it. 18:43:10 ack nex 18:43:12 ack next 18:43:59 YL: The legal side gave us feedback that suggests workiing, as we have, only on the technical side, we won't get there -- to take this forward we need to recruit help on the legal side 18:44:07 s/workiing/working/ 18:44:29 NM: This feels that something we should have been able to make work, if we had managed to stay focussed 18:44:51 it may be the caes that the legal community is improvising too in a vacuum of settled case law 18:44:59 ... but the feedback we got from the legal side was not all consistent, and in attempting to follow it we lost focus 18:45:09 q+ 18:45:27 ack next 18:45:35 NM: When we tried to focus on the technology, I think we made some progress, but we couldn't quite close it 18:45:50 NM: I do hate to close something after so much effort 18:46:08 JT: Yes, but that is a sunk cost, and it probably is time to move on 18:46:41 q+ to say Jeni leads me to think that maybe the legal focus is what's made this difficult 18:46:44 JT: So maybe a finding or a REC is not the right vehicle for achieving our limited goal 18:47:13 ... So maybe realising that blog posts or articles in the press are legitimate TAG outputs 18:47:21 ... is the right thing to do for this 18:47:27 q+ 18:47:31 NM: So keep it as a work item, or not? 18:47:38 q+ 18:47:49 ack next 18:47:50 noah, you wanted to say Jeni leads me to think that maybe the legal focus is what's made this difficult 18:47:51 JT: Keep it on the list of things to include in strategic priorties at the F2F 18:48:01 q+ to say Jeni leads me to think that maybe the legal focus is what's made this difficult 18:48:16 Ax: What was the driver in the first place, for taking this on? 18:50:02 NM: There has been a steady trickle of legal cases [in US and UK] which involved sites with links and/or embedding, where public discussion was just muddled. And we did get, I think, requests from [the W3C's legal guy] Rigo Wenning, to help with this. 18:50:32 NM: We thought that a TAG finding on this would have more value than an individual's blog post 18:51:23 AR: So there was a specific request from lawyers for an explicit technical guidance 18:51:28 Jonathan brought Thinh along 18:51:30 s/guidance/guidance?/ 18:51:37 s/Ax:/AR:/ 18:51:41 Thinh from Creative Commons 18:52:01 HST: I am not sure we had an explicit request to start us off -- certainly some positive feedback once we got started 18:52:28 Yes. we had a chat with Thinh 18:52:40 AR: I think it would be a possible way forward to publish something pithy that says "Here's the relevant bits, in the TAG's opinion" 18:52:47 thanks 18:52:49 +1 18:53:06 Hmm. Did I not hear Alex suggest pointing to existing explanations? 18:53:24 NM: I think the problem is that the RFCs and related material is not at the right level for public consumption 18:53:59 I'm not trying to 18:54:06 . ACTION: Noah to schedule F2F discussion of whether and how to pursue Publishing and Linking 18:54:14 HST: I think JT's suggestion is the best we've got 18:54:25 +1 18:54:26 and don't think we should try to in an absence of compelling demand from a userbase with authority 18:54:32 q? 18:54:42 ack slightlyoff 18:54:50 ack plinss 18:55:10 PL: Couldn't we simply put this on an official TAG blog 18:55:17 NM: We do indeed have such a blog 18:55:33 ... But we've used it for personal posting, rather than corporate 18:55:42 NM: The entire finding? 18:55:55 AM: It's long for a blog post, isn't it? 18:56:08 ... Maybe take one part of it -- extract highlights? 18:56:12 +1 for a series 18:56:23 PL: Break it up into a series of articles would be fine 18:56:40 http://www.w3.org/blog/tag/ 18:56:55 AM: One on copyright, one on linking vs. embedding 18:57:20 NM: I'm concerned about the archival status of blog posts, compared to, say, W3C notes 18:57:45 ... Putting smaller pieces where they could be useful, yes, but not sure about doing it via a blog 18:57:52 NM: So what about notes? 18:58:21 NM: So some dimensions: how formal; what mechanism; how much TAG consensus required 18:59:26 ... And beyond the TAG, e.g. LM had been interested in the fact that REC-track gives some community buy-in 18:59:27 ACTION: Yves to figure out where our old TAG blog stuff is. 18:59:27 Created ACTION-778 - Figure out where our old TAG blog stuff is. [on Yves Lafon - due 2013-01-31]. 18:59:39 PL: CSS has its own blog. . . 18:59:55 annevk has joined #tagmem 19:00:07 NM: Sure, just there is a history which we need to hook up with 19:00:11 Zakim, details? 19:00:11 I don't understand your question, annevk. 19:00:18 Zakim, passcode? 19:00:18 the conference code is 0824 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), annevk 19:00:35 PL: OK, let's try moving that forward again 19:00:53 ... tweet about it, and improve its visibility 19:00:55 . ACTION: Noah to schedule F2F discussion of whether and how to pursue Publishing and Linking 19:01:17 AM: Yes 19:01:28 ACTION: Noah to schedule F2F discussion of whether and how to pursue Publishing and Linking - Due 2013-03-01 19:01:28 Created ACTION-779 - schedule F2F discussion of whether and how to pursue Publishing and Linking [on Noah Mendelsohn - due 2013-03-01]. 19:01:31 +??P14 19:01:48 zakim, ? is annevk 19:01:48 +annevk; got it 19:03:14 Topic: Future of Privacy by design note and related privacy issues 19:03:29 ACTION-774? 19:03:29 ACTION-774 -- Peter Linss to frame F2F discussion of Privacy by design note, and possible followup up with privacy group. Due: 2013-01-08 -- due 2012-12-20 -- OPEN 19:03:29 http://www.w3.org/2001/tag/group/track/actions/774 19:04:03 NM: This started with work by Dan Appelquist wrt Javascript APIs for minimal disclosure 19:04:04 "object capabilities" 19:04:18 AM: Minimization 19:04:45 NM: Then Robin Berjon shifted the focus, as Dan A. left the TAG 19:04:51 ... And then Robin left 19:05:05 q+ 19:05:09 q- 19:05:12 ack nextg 19:05:15 ack next 19:05:19 NM: And PL was given the action to take the existing content, slightly cleaned up, and publish it as a Note 19:05:50 AM: And we also agreed to ask the Privacy [WG?] to take this over 19:06:13 ... Also, Nick [?] is writing a document about fingerprinting, which makes up about half the content of our draft 19:06:16 q? 19:06:18 NM: So? 19:06:23 AM: Abandon it 19:06:28 s/Nock Doty/ 19:06:42 s/Nick [?]/Nick Doty/ 19:06:48 s/Nick/Nick Doty/ 19:07:07 s/Nick Nick Doty/Nick Doty/ 19:07:29 AM: I have had no answer from Pxx 19:07:38 NM: Draft me an email and I'll send it 19:08:10 PL: The idea was that by publishing it as a Note we could hand it over to PING 19:08:11 s/Pxx/PING/ 19:08:24 ACTION: Ashok to draft note to PING asking them to pick up our incomplete work on privacy by design by APIs 19:08:25 Created ACTION-780 - Draft note to PING asking them to pick up our incomplete work on privacy by design by APIs [on Ashok Malhotra - due 2013-01-31]. 19:08:38 s/Privacy [WG?]/Privacy Interest Group (PING)/ 19:09:25 NM: I'll wait a few days for comments from TAG members and then send it -- use tag@w3.org for that, please 19:09:28 PING: public-privacy@w3.org 19:09:53 Topic: ISSUE-57 19:10:49 HT: Jonathan and I made some progress at MIT in November. I will take this forward. Jeni's awaiting comments. Teaching full time. Won't do much between now and end of March 19:11:32 Try this link http://www.w3.org/2001/tag/products/defininguris.html 19:11:40 HST: JAR and I have made some progress, JT has improved her draft, we will make some progress but not much in the next few weeks 19:11:48 It's really more than ISSUE-57, we sort of use that as a shorthand name. 19:11:53 NM: How about a briefing at the F2F? 19:12:03 HST: Maybe -- ask me in a month 19:12:27 ACTION: Jeni to prepare reading and discussion on Defining URIS (ISSUE-57) for March F2F - Due 2013-03-01 19:12:27 Created ACTION-781 - prepare reading and discussion on Defining URIS (ISSUE-57) for March F2F [on Jeni Tennison - due 2013-03-01]. 19:12:38 JT: Yes -- I think it's appropriate to aim for feedback on the Primer and discussion about next steps 19:12:56 -ht 19:12:57 ScribeNick: JeniT 19:13:10 noah: this is also known as httpRange14 19:13:35 noah: this issue is about how to get information about things that aren't documents using HTTP 19:14:21 noah: why don't we have a session on F2F topics on next week's telcon 19:14:35 noah: please send emails with suggestions to the public mailing list 19:14:53 noah: can you put a "layering" item on the F2F agenda. I could write up a sentence or paragraph if that would be helpful 19:15:22 Topic: XML/HTML Unification 19:15:43 noah: is there anything useful we can do about this today? 19:15:51 noah: I have an action to announce that it's done 19:16:05 Here is a link to the Privacy by Design document: http://darobin.github.com/api-design-privacy/api-design-privacy.html 19:16:36 noah: I took an action to schedule discussion of the DOM stuff at the F2F 19:16:40 thanks Ashok 19:16:48 … there's a raging discussion on polyglot on both the HTML and TAG mailing lists 19:17:13 … in part in reaction to the TAG's reply to Henri 19:17:34 I am happy to wait until the F2F to discuss so that the new members can get a high-bandwidth dump of existing perspectives 19:17:39 sorry 19:17:39 … I'll wait to see what else people ask for me to schedule around this topic 19:17:41 q+ 19:17:43 my fault 19:17:50 ack next 19:18:05 1+ 19:18:07 q+ 19:18:26 Alex: I'd like to understand what's driving our interest here? 19:18:50 … what's the architectural principle, or is it because there's a disagreement? 19:19:02 noah: can we defer that to when Tim and/or Henry are with us? 19:19:44 … while HTML&JSON are increasingly being used, XML is still an important technology 19:20:13 … some people feel that publishing polyglot could help meet the requirements of those that want to publish HTML with an XML flavour 19:20:25 … we asked for the publication of the polyglot document 19:20:42 Anne: I was on the TF, and maybe the TAG asked for polyglot, but the TF didn't 19:20:58 noah: the TF surveyed the field, yes 19:21:08 … the TAG went further than the TF 19:21:11 q? 19:21:21 ack next 19:21:47 Yehuda: I think this is related to some of the issues that the new TAG members are interested in 19:21:56 … and we should have a discussion about this in a F2F 19:22:17 noah: we sometimes get requests that we have to respond to more quickly 19:22:35 Yehuda: we should respond to those, but a F2F discussion would be useful 19:22:57 ACTION: Noah to schedule F2F discussion of polyglot, the TAG's request to HTML WG on polygot, and HTML/XML Unification - Due 2013-03-01 19:22:57 Created ACTION-782 - schedule F2F discussion of polyglot, the TAG's request to HTML WG on polygot, and HTML/XML Unification [on Noah Mendelsohn - due 2013-03-01]. 19:23:09 q? 19:23:52 noah: please could existing TAG members go through your actions and either close them or send me email about what you want to do with them 19:24:14 … if there are other things that you want to discuss next week, please email them to me 19:24:27 I won't be able to attend next week's call (on vacation). Regrets. 19:24:46 I will scribe next week 19:24:53 -Ashok_Malhotra 19:24:54 ADJOURNED 19:24:54 -Marcos 19:24:58 -Yves 19:24:59 -slightlyoff 19:24:59 -JeniT 19:25:00 -plinss 19:25:08 -annevk 19:25:36 -wycats 19:25:58 rrsagent, draft minutes 19:25:58 I have made the request to generate http://www.w3.org/2013/01/24-tagmem-minutes.html JeniT 19:35:00 disconnecting the lone participant, noah, in TAG_Weekly()1:00PM 19:35:02 TAG_Weekly()1:00PM has ended 19:35:02 Attendees were Marcos, JeniT, ht, wycats, plinss, Ashok_Malhotra, Yves, +1.212.565.aaaa, noah, slightlyoff, annevk 19:46:07 annevk has joined #tagmem 20:01:05 JeniT has joined #tagmem 20:17:26 JeniT has joined #tagmem 20:30:25 Marcos has joined #tagmem 20:35:06 annevk has joined #tagmem 20:40:58 timbl_ has joined #tagmem 21:23:38 timbl_ has joined #tagmem 21:27:33 annevk has joined #tagmem 21:35:39 Zakim has left #tagmem 21:44:29 timbl__ has joined #tagmem 21:45:06 JeniT has joined #tagmem 21:47:43 annevk has joined #tagmem 22:57:36 JeniT has joined #tagmem 23:00:58 timbl_ has joined #tagmem 23:30:11 timbl_ has joined #tagmem 23:50:38 timbl__ has joined #tagmem