17:02:45 RRSAgent has joined #tagmem 17:02:45 logging to http://www.w3.org/2009/03/12-tagmem-irc 17:02:57 zakim, list 17:02:57 I see TAG_Weekly()1:00PM, WAI_UAWG()1:00PM, HTML_WG()12:00PM, T&S_EGOV(F2F2)9:00AM, WS_WSRA(F2F)9:00AM active 17:02:59 also scheduled at this time is WS_Policy(Editors)1:00PM 17:03:02 zakim, tihs is TAG 17:03:02 sorry, noah, I do not recognize a party named 'tihs' 17:03:09 zakim, this is TAG 17:03:09 ok, noah; that matches TAG_Weekly()1:00PM 17:03:13 zakim, who is here? 17:03:13 On the phone I see Masinter, Raman, Noah_Mendelsohn, alanr 17:03:15 On IRC I see RRSAgent, Zakim, jar, johnk, noah, raman, masinter, DanC, ht, trackbot 17:03:20 Zakim, this is tag 17:03:20 DanC, this was already TAG_Weekly()1:00PM 17:03:21 zakim, please call ht-781 17:03:21 ok, DanC; that matches TAG_Weekly()1:00PM 17:03:25 ok, ht; the call is being made 17:03:27 +Ht 17:03:31 +DanC 17:03:33 +John_Kemp 17:03:38 plh has joined #tagmem 17:03:50 zakim, alanr is jar 17:03:57 +jar; got it 17:04:01 +Plh 17:04:05 zakim, who is here? 17:04:06 On the phone I see Masinter, Raman, Noah_Mendelsohn, jar, Ht, John_Kemp, DanC, Plh 17:04:11 On IRC I see plh, RRSAgent, Zakim, jar, johnk, noah, raman, masinter, DanC, ht, trackbot 17:04:41 Meeting: TAG Weekly 17:04:50 CHAIR: Noah 17:05:06 chair: Noah 17:06:09 NM: canceling the call for the 19th 17:06:36 (26 Mar TAG call conflicts with HTTP bis IETF meeting, which I hope to attend) 17:06:42 johnk_ has joined #tagmem 17:07:04 link to agenda 17:07:08 http://www.w3.org/2001/tag/2009/03/12-agenda 17:07:42 TOPIC: pending action items 17:07:55 +1 17:07:59 NM: propose that we resolve procedures for closing open issues via email 17:08:09 (agreement) 17:08:29 NM: HT, can you scribe? 17:08:31 s/issues/actions/ 17:08:33 noah: "Our clocks are fine" 17:08:35 HT: OK... 17:09:08 Note I sent email asking to not close actions that (a) have no associated ISSSUES and (b) have no other followon 17:09:46 action-243? 17:09:46 ACTION-243 -- Dan Connolly to assemble minutes from SFO for day 1 based on http://www.w3.org/2009/03/03-tagmem-irc -- due 2009-03-17 -- OPEN 17:09:46 http://www.w3.org/2001/tag/group/track/actions/243 17:10:12 johnk has joined #tagmem 17:10:14 (the guilty wave hands) 17:10:45 q+ 17:11:22 NM: will schedule ongoing activity to review priorities + "big themes" 17:11:34 pop 17:11:36 NM: any need to discus this more now? 17:11:36 q- 17:11:40 ack next 17:11:42 group: no 17:12:40 NM: been sent a survey inquiring about TAG interest in 2-6 Sept. TPAC meeting, we should decide by the 18th 17:13:07 TOPIC: XHTML 17:13:26 http://www.w3.org/2009/02/status.html#hot 17:14:05 LMM: would like to understand this issue better 17:14:33 we'd like to understand the proposal and possibly refine it 17:15:00 PLH: two groups using the same ns/media type 17:15:19 PLH: HTML, XHTML 17:16:42 q+ to note Device Independent Authoring Language http://www.w3.org/TR/2007/WD-dial-primer-20071101/ 17:16:43 q? 17:16:47 PLH: can we resolve conflict by getting XHTML to stop using the ns/media type? 17:17:01 LMM: is there a written proposal? 17:17:14 PLH: no fully-fledged proposal - 17:17:26 PLH: what is impact on XForms, for example? 17:17:39 ack danc 17:17:39 DanC, you wanted to note Device Independent Authoring Language http://www.w3.org/TR/2007/WD-dial-primer-20071101/ 17:18:06 DanC: DIAL is a way that XHTML is used 17:18:12 TVR: it's a profile 17:18:52 what is the relationship of DIAL to the issue being raised? 17:19:03 DanC: It's not critical for DIAL to use the 1999 ns/media type 17:19:04 q+ arch issue media type, namespace, versioning 17:19:41 TVR: this is a TAG Issue because: 17:20:03 the relevance of DIAL is that I'd like to know if those who recently showed interest in XHTML 2 would be happy if it were renamed "DIAL" 17:20:23 TVR: how to support in webarch how to discover what language you are getting at each point? 17:20:50 the application/xhtml+xml media type has 'failed' 17:21:00 TVR: xhtml+xml has failed as a media type 17:21:17 TVR: media type is thus useful 17:21:35 TVR: ns is also being abused 17:21:47 TVR: 3rd thing is versioning 17:22:08 TVR: Larry started discussion in HTML5 about ns as versioning mechanism 17:22:24 TVR: XHTML2 went back to using the old ns 17:22:34 TVR: two groups in the same space is certainly sub-optimal 17:22:57 TVR: your proposal is interesting, but from webarch perspective, we will not be in any better place 17:23:10 PLH: agree, this doesn't resolve all the issues 17:23:20 PLH: but that is not my goal 17:23:44 q+ to make sure I understand what's intended 17:24:11 q+ to discuss XForms 17:24:19 politics intertwined with architecture 17:24:46 TVR: web is bigger than browser 17:25:05 PLH: proposal is to address one specific issue 17:25:19 ack next 17:25:20 noah, you wanted to make sure I understand what's intended 17:25:30 s/thus useful/thus not useful/ 17:25:37 q+ to suggest we work with PLH to make the choices clearer 17:25:48 NM: agrees with TVRs points 17:26:36 NM: who "owns" the namespace and media type? 17:27:07 NM: we've decided to put new NS, and media type on XHTML2 17:27:48 NM: is my understanding correct? 17:27:51 PLH: yes 17:28:08 need to come up with agreement on what the issues are and what the choices really are, put into a form where the membership can really review and comment on it. as currently framed, the "idea" is incoherent and disruptive 17:28:39 PLH: new namespace solves the bootstrap problem 17:28:58 different architectural choices in this space will impact companies and their businesses in different ways, and consensus will be hard because of the economic impacts 17:29:11 TVR: what I hear is we create YA media type 17:29:20 ("that won't work" ... umm... really? as far as I understand the DIAL use cases, they don't need MS IE to grok a new media type) 17:29:43 zakim, unmute ht 17:29:43 Ht should no longer be muted 17:30:13 larry, when you verbally ack somebody, it helps to simultaneously "ack next"; Zakim is smart enough to unmute people who get the floor 17:30:17 johnk_ has joined #tagmem 17:30:21 q? 17:30:28 ack ht 17:30:28 ht, you wanted to discuss XForms 17:31:07 q+ 17:31:13 CORRECTION: by using the OLD namespace in XHTML2, you solve the bootstrapping problem by using JS to handle the XHTML 17:31:52 HT: from TAG perspective, NS competition is place where we should start 17:32:01 ack next 17:32:02 masinter, you wanted to suggest we work with PLH to make the choices clearer 17:32:34 LMM: clear that is important for w3c, decision is not speculative or forward-looking 17:32:48 LMM: choices for members are not clear 17:33:13 LMM: cannot see it being possible to make an informed choice on a proposal that is not fully-fledged 17:33:41 q+ to add that defining Web purely as a browser for N years after having defined it *without* the browser fo r8 years is a mistake. We need a balance 17:33:47 q- later 17:33:52 LMM: would be a good service to the community to write out the issues and choices 17:34:21 LMM: TAG should take on such a work item 17:34:46 ack raman 17:34:46 raman, you wanted to add that defining Web purely as a browser for N years after having defined it *without* the browser fo r8 years is a mistake. We need a balance 17:35:27 TVR: risk is that you equate the browser with the Web 17:36:08 q+ to discuss content creators 17:36:14 (good point; the risk that "future of browser" will be understood as "future of W3C" is pretty high. not a bet I'd take) 17:36:47 TVR: problem is that we have made the mistake of ignoring the browser, and don't wish to swing back too far the other way 17:37:39 PLH: yes, it is a difficult balance 17:38:00 PLH: we will have a panel at the AC meeting 17:38:15 (scribe missed most of the names) 17:38:54 PLH: Steven Pemberton will be at the AC meeting and on the panel. 17:38:54 people come to the AC meetings to represent their companies, and need to review their company's point of view. That point of view needs to be based on choices that have been explained clearly. The current proposal isn't. 17:38:56 TVR: DAISY has been based on XHTML2 17:39:06 q? 17:39:27 q+ to ask TAG members if they're willing to take on this issue and immediate actions 17:39:30 http://www.daisy.org/ ? 17:39:49 http://www.daisy.org/, yes 17:39:51 Larry, I'd be curious to know what the specific goal would be of TAG work (not unsympathetic, by the way) 17:40:26 I will now be at the AC, with my Edinburgh hat on 17:40:33 create a background document which lays out the issues and considerations we've already discussed, and the relevant sections of AWWW and the impact it would have 17:41:17 q? 17:42:00 ack next 17:42:39 ack next 17:42:40 noah, you wanted to discuss content creators 17:42:42 TVR: back to language design issues 17:42:45 q+ noah 17:42:47 oops; sorry 17:42:50 i'm using the queue but giving raman slack 17:43:14 TVR: web has always been extensible (netscape plugins eg) 17:43:24 q+ noah to discuss content creators 17:43:35 TVR: then JS+DHTML 17:43:37 yay greasemonkey! 17:43:43 TVR: then greasemonkey 17:44:14 (hmm... stack: plug-in API, browser extension, greasemonkey) 17:44:17 different kinds of extensibility: protocol, MIME type, namespace, .... 17:44:20 TVR: can extend on the protocol handler, or on the MIME type, or on namespaces 17:44:28 q+ to note that MS implements a namespace hook 17:44:37 q+ to disagree with TV about NS and media type dispatching 17:44:59 Seeing the list plugin, extension, greasemonkey all together for some reason reminds me that at the F2F we noodled on the TAG focusing more on Web security. 17:45:21 johnk has joined #tagmem 17:46:05 TVR: believe this is a big mistake 17:46:20 DanC: what should we do instead? 17:48:24 TVR: not concerned about the specific item per se 17:48:54 LMM: panel should try and frame a TAG overview of the arch issues, pointing to relevant findings and issues 17:49:11 Larry, should we give someone an action to prepare a TAG position for either you or some other TAG member to present? 17:49:17 LMM: I can't be on the panel as both TAG rep and company rep 17:50:11 (then LMM said he *can* do both of those. hmm.) 17:50:48 LMM: concerned that this topic has this proposal already as if there is some reasonable resolution already 17:51:02 LMM: would like to frame the issues coherently first 17:51:54 TVR: yes, feels like a fait accompli 17:52:04 q? 17:52:07 ack masinter 17:52:07 masinter, you wanted to ask TAG members if they're willing to take on this issue and immediate actions 17:52:16 ack noah 17:52:16 noah, you wanted to discuss content creators 17:52:56 NM: if there's some chance that we need to present a TAG position, we need to work on this soon 17:53:10 NM: should we assign an action to guide TAG through such a process? 17:53:46 q+ 17:53:58 NM: a possible issue about who represents TAG on this panel 17:54:04 q+ to correct Noah's mischaracterization of what I said 17:54:11 q+ to add that Larry is well-respected as Larry --- I wouldn't split hairs about Tag concensus position and Larry being the message bearer 17:54:35 NM: wanted to mention the content creators 17:54:55 I didn't volunteer to be on the panel to represent either Adobe or the TAG but to add what I hoped was an informed perspective 17:55:03 NM: if we can have fair representation from content creators in this discussion, that would be good 17:55:57 ack DanC 17:55:57 DanC, you wanted to note that MS implements a namespace hook 17:55:58 DanC: MS has implemented ns support (URI-based extensibility) since IE6 17:56:01 ack ht 17:56:01 ht, you wanted to disagree with TV about NS and media type dispatching 17:56:08 and representation can't really happen until we've discussed the issues and come to a conclusion, and I don't think we'll have a fully-fledged "considered position". I'm not proposing that the TAG have a "considered position" but that we document the analysis of the issues we've done so far in order to make the discussion at AC more productive 17:56:45 HT: agree with Noah that we continue to struggle to find content-creators willing to talk about this issue 17:57:21 HT: when NS + media-type extensibility is made available to developers, it *is* used 17:57:40 HT: using HTML+SVG because MathML works now 17:57:53 HT: this wasn't possible a year ago 17:58:08 HT: that entry point into extensibility is worth fighting for 17:58:36 Henry reminds me that more specialized communities, like scientists, may have an important perspective on extensibility. 17:58:56 HT: takes us back to the core question: are we prepared to declare text/html media-type and 1999 ns an "open" framework? 17:59:30 HT: starting the discussion at the procedural level is a mistake 17:59:35 q+ to point out that it is possible to have two different languages with the same namespace, as long as there is a versioning mechanism to distinguish between them 17:59:44 s/1999/1999.xhtml/ 18:00:19 i say 'versioning' in a named or branched sense, not just a linear way 18:01:28 (agreement that browsers have NOT written off NS-based extensibility) 18:01:48 it sounds like the proposal is based on false assumptions? 18:02:03 HTML+SVG is being discussed 18:02:11 q+ to ask about HTML 5 and extensibility 18:02:34 johnk_ has joined #tagmem 18:02:36 (I'm persuaded the current proposal is misleading) 18:02:37 ack plh 18:02:39 want to push again on the framework of the panel and the AC meeting. The "panel" should be an explanation of the issues and the point of view, and not an uninformed debate 18:04:01 BTW: if you look at materials XML schema developed in exploring versioning they strongly support what Larry is saying about the distinction between namespaces and language versions 18:04:17 LMM: if you don't use NS for versioning, then you can use some other indicator (eg. DOCTYPE or explicit version number attribute) 18:05:01 LMM: should push on this notion of versioning being a linear progression 18:05:24 As I wrote in the TAG blog article, I think you only need to distinguish versions in the representation IF the same content would have different meaning in two or more versions. If all that happens is that content becomes legal or becomes illegal, you can tell that without labeling the versions at all 18:05:50 See blog entry at: http://www.w3.org/QA/2007/12/version_identifiers_reconsider.html 18:06:20 LMM: different WGs are talking past each other - don't want to see a panel as a debate 18:06:39 q+ 18:06:41 LMM: panel should be a discussion without a presumption that there will be some immediate vote or action 18:06:58 HST endorses LMM's analysis: see http://www.pdfpower.com/XML2005Proceedings/ship/82/XML_2005_82.HTML 18:07:09 q? 18:07:17 LMM: TAG has worked on versioning extensively, and should use this chance to solicit opinion from members to create a coherent proposal 18:07:19 q, ack 18:07:33 q? 18:07:43 ack masinter 18:07:43 masinter, you wanted to correct Noah's mischaracterization of what I said and to point out that it is possible to have two different languages with the same namespace, as long as 18:07:46 ... there is a versioning mechanism to distinguish between them 18:07:48 q- 18:07:52 ack raman 18:07:52 raman, you wanted to add that Larry is well-respected as Larry --- I wouldn't split hairs about Tag concensus position and Larry being the message bearer 18:07:56 ack noah 18:08:34 i'm really sorry, need to get off phone for a bit 18:08:39 johnk has joined #tagmem 18:09:11 NM: is it really only in HTML5 discussions that are saying "look, if I do SVG/MathML, I want to do it without ns?" 18:09:19 HT: yes, my understaning 18:09:24 TVR: (agrees) 18:09:31 -Masinter 18:09:40 can stay on IRC 18:09:41 sorry 18:09:51 q? 18:10:02 ack plh 18:10:18 PLH: panel is not there for a debate or to make a decision 18:10:31 PLH: but to get feedback 18:10:42 (I don't know how to answer noah's question; many of the loudest voices in the HTML 5 discussion represent browsers) 18:10:44 q+plh, reason the panel has become critical is because of SB's phrasing of the AC agenda 18:10:55 q+ raman 18:10:59 q+ to worry about version-dependent semantics 18:11:03 NH: is there anything that the TAG can help with in support of this panel? 18:11:43 PLH: if TAG was willing to write something about this issue, that would be helpful 18:12:13 NM: this is a complex topic which includes opinions which do not yet converge 18:12:38 q? 18:12:56 NM: (a little surprised at this issue taking the turn it has towards TAG action on the general issue) 18:13:30 s/action on the general issue/focusing on versioning vs. other HTML problems/ 18:14:42 NM: (repeats question to PLH about what specifically the TAG could do) 18:15:25 NM: if we should do anything more than we're already doing, we need to decide that now 18:15:52 1+ to HT presenting on behalf of the TAG 18:16:07 Yes, I like that. PLH, is there room? Is that a good thing? 18:16:31 HT: point that Larry raised - the media-type to namespace to formal version identifier should be made on the panel 18:16:34 there is room, and I welcome Henry 18:16:49 Great. Let me set up the necessary actions when Henry is done talking. 18:17:03 at this point, even getting a one-level indirection/extension mechanism would be a win. With 3 possibilities, all 3 are abused, and people need to invent itunes: 18:17:54 NM: HT, can you circulate a proposal? 18:17:58 HT: accepts 18:18:16 (I don't need to be in the critical path; I'm happy for HT and LMM to say what they like, whether on behalf of me, the TAG, or otherwise.) 18:18:37 ACTION: ht to circulate a proposal framing this issue 18:18:38 Created ACTION-246 - Circulate a proposal framing this issue [on Henry S. Thompson - due 2009-03-19]. 18:19:02 will help, think this is quite valuable 18:19:59 -Plh 18:20:18 TOPIC: Metadata 18:20:41 NM: JAR took ACTION-227 18:20:50 action-227? 18:20:50 ACTION-227 -- Jonathan Rees to summarize TAG work on metadata, with Larry -- due 2009-02-24 -- PENDINGREVIEW 18:20:50 http://www.w3.org/2001/tag/group/track/actions/227 18:21:01 NM: proposes to close 227 18:21:07 (agreed) 18:21:34 close ACTION-227 18:21:34 ACTION-227 Summarize TAG work on metadata, with Larry closed 18:21:41 q+ 18:22:00 q- ht 18:22:17 johnk_ has joined #tagmem 18:22:49 http://www.w3.org/2001/tag/2009/02/metadata-survey.html 18:22:53 action-227: http://www.w3.org/2001/tag/2009/02/metadata-survey.html 18:22:53 ACTION-227 Summarize TAG work on metadata, with Larry notes added 18:23:13 ack raman 18:23:15 sorry can't get back on phone 18:23:30 No problem, Larry. 18:23:35 Thanks for getting back to us. 18:24:03 DanC: would like to wait for Larry on this item... 18:24:09 proposal to adjourn 18:24:15 Discussion tabled pending Larry's participation. 18:24:24 ADJOURNED 18:24:39 -Ht 18:24:43 -Raman 18:25:11 -John_Kemp 18:25:28 -Noah_Mendelsohn 18:25:40 plh has left #tagmem 18:25:43 sorry 18:25:45 Zakim, who's on the phone? 18:25:45 On the phone I see jar, DanC 18:26:01 i'll check in with HT 18:26:33 617 253-8581 18:26:43 -DanC 18:26:44 TAG_Weekly()1:00PM has ended 18:26:46 Attendees were Masinter, Raman, Noah_Mendelsohn, Ht, DanC, John_Kemp, jar, Plh 18:30:22 johnk has joined #tagmem 20:06:15 johnk has joined #tagmem 20:29:55 Zakim has left #tagmem 21:26:43 rrsagent, generate minutes 21:26:43 I have made the request to generate http://www.w3.org/2009/03/12-tagmem-minutes.html johnk 21:36:21 rrsagent, make logs public 21:59:15 DanC has joined #tagmem 22:34:46 johnk has joined #tagmem 23:43:24 johnk has joined #tagmem