16:50:03 RRSAgent has joined #tagmem 16:50:03 logging to http://www.w3.org/2008/06/19-tagmem-irc 16:50:11 Zakim has joined #tagmem 16:50:18 zakim, this will be tag 16:50:18 ok, Stuart; I see TAG_Weekly()1:00PM scheduled to start in 10 minutes 16:50:38 meeting: TAG Weekly 16:50:48 chair: Stuart Williams 16:51:18 scribe: Dan Connolly 16:51:28 Regrets: Noah Mendelsohn 16:51:36 agenda? 16:51:45 agenda+ Convene 16:52:01 agenda+ News and New Items 16:52:25 agenda+ scalabilityOfURIAccess-58 16:52:38 agenda+ XMLVersioning-41 16:52:56 agenda+ tagSoupIntegration-54 16:53:21 agenda+ Issues and Action Item review. 16:53:39 agenda+ Any other business. 16:58:00 TAG_Weekly()1:00PM has now started 16:58:06 +Raman 16:58:58 amalhotr has joined #tagmem 16:59:02 +??P5 16:59:34 zakim, who is on the call? 16:59:34 On the phone I see Raman, ??P5 16:59:34 Ashok has joined #tagmem 17:00:04 zakim, ??P5 is jar 17:00:04 +jar; got it 17:00:49 let me try the other phone 17:00:56 -jar 17:00:59 +??P1 17:01:05 zakim, ??p1 is me 17:01:05 +Stuart; got it 17:01:28 +jar 17:01:44 zakim, please call ht-781 17:01:44 ok, ht; the call is being made 17:01:46 +Ht 17:01:57 +Ashok_Malhotra 17:02:32 zakim, who is on the phone? 17:02:32 On the phone I see Raman, Stuart, jar, Ht, Ashok_Malhotra 17:02:38 +Norm 17:02:44 +DanC.a 17:03:54 Zakim, take up item 1 17:03:54 agendum 1. "Convene" taken up [from Stuart] 17:04:05 regrets: Noah 17:04:50 agenda review... TVR asks that we make sure to give tagSoup considerable time 17:05:58 -> http://www.w3.org/2008/06/12-tagmem-minutes 12 Jun minutes 17:06:06 RESOLVED: to approve 12 Jun minutes 17:06:14 Zakim, who's on the phone? 17:06:14 On the phone I see Raman, Stuart, jar, Ht, Ashok_Malhotra, Norm, DanC.a 17:06:51 SKW: propose to meet 26 Jun as usual... nominate DO to scribe, but can't confirm, so NDW? 17:07:06 +TimBL 17:07:06 RESOLVED: to meet again 26 Jun, NDW to scribe 17:07:19 AM: meeting [some date]? 17:07:34 SKW: haven't looked forward that far; might meet with XRI TC then 17:07:40 s/[some date]/3 July/ 17:07:48 Zakim, next item 17:07:48 agendum 2. "News and New Items" taken up [from Stuart] 17:07:57 q+ to note public suffix list 17:08:18 timbl has joined #tagmem 17:08:27 SKW: I note www-tag discussion of widget: URI scheme 17:09:27 NDW: I'm interested in a suggestion from LMM about addressing into zips/packages 17:09:28 From: http://lists.w3.org/Archives/Public/www-tag/2008Jun/0090 17:09:31 timbl has joined #tagmem 17:09:37 Regardless, we need the TAG's support resolving this 17:09:37 issue sooner than later. 17:11:38 [missed some...] 17:11:58 some discussion of itunes: 17:12:13 and ado: 17:12:15 daap: ? 17:12:54 TVR: one end-to-end architecture is: (1) start with HTTP, (2) get a media type, (3) get a namespace. But due to software bugs, sometimes a URI scheme is easier to deploy 17:13:25 I am interested in us getting involved 17:13:41 :) 17:13:44 (is that WG chartered to do a new URI scheme?) 17:13:54 several show interest in getting involved 17:14:18 SKW: ok, I'll let them know we're interested to get involved 17:14:39 ACTION: stuart respond to Marcus re widget: URI scheme 17:14:39 Created ACTION-162 - Respond to Marcus re widget: URI scheme [on Stuart Williams - due 2008-06-26]. 17:14:59 http://lists.w3.org/Archives/Public/www-archive/2008Jun/0126.html 17:15:03 Zakim, next item 17:15:03 I see a speaker queue remaining and respectfully decline to close this agendum, DanC 17:15:13 q? 17:15:20 q- 17:15:34 agenda + public suffix list 17:15:39 Zakim, next item 17:15:39 agendum 3. "scalabilityOfURIAccess-58" taken up [from Stuart] 17:16:15 TimBL: question is, if the W3C systems team says "for the good running of the web, please install these catalogs"... is that good? 17:16:29 q+ to say that supporting XML Catalogs ought to be sufficient 17:16:30 ... I'm concerned that some catalog systems use public identifiers rather than URIs 17:16:47 q? 17:16:48 q+ 17:16:52 ack Norm 17:16:52 Norm, you wanted to say that supporting XML Catalogs ought to be sufficient 17:17:19 NDW: XML catalogs seems sufficient; SGML catalogs would be overkill... 17:17:40 ... and while XML catalogs allow public identifiers, it seems reasonable to stick to URIs 17:17:42 q+ to ask what the point I'm missing is 17:17:59 as google's AC rep, I'd like the W3C to do something here because we and many large companies get periodically locked out of the W3C site because some piece of test code inadvertantly hammers the W3C site in the process of implementing a spec 17:18:08 ack danc 17:18:11 ack DanC 17:18:14 q+ to suggest that Ted should build a sample catalog as he might distribute and to volunteer to review it. 17:18:21 q+ to express concern about the use of ur: all over the spec 17:18:44 ack ht 17:18:44 ht, you wanted to ask what the point I'm missing is 17:18:44 The namespace name defined by this Standard is "urn:oasis:names:tc:entity:xmlns:xml:catalog". 17:19:41 DanC: in the past, the cache key for catalogs wasn't a URI; but catalogs now have URI support; any cache mechanism that uses URIs as the cache key is OK by me 17:19:58 ht: what am I missing? what good is a catalog without... 17:20:13 ack norm 17:20:13 Norm, you wanted to suggest that Ted should build a sample catalog as he might distribute and to volunteer to review it. 17:20:31 I think he should build THE calalog 17:20:32 DanC: the catalog comes along with the cache hit data 17:20:51 ACTION: norm to review a catalog, should norm provide it 17:20:51 Sorry, couldn't find user - norm 17:20:55 q? 17:20:58 ack timbl 17:20:58 timbl, you wanted to express concern about the use of ur: all over the spec 17:21:00 ack timbl 17:21:25 NDW: yes, the catalog spec pre-dates my change in opinion from urns to http URIs for xml namespaces 17:22:06 ACTION: Norman to coordinate with Ted to build a sample catalog 17:22:06 Created ACTION-163 - Coordinate with Ted to build a sample catalog [on Norman Walsh - due 2008-06-26]. 17:22:41 HT: bummer, that it starts urn: but the software we're interested to exploit knows that namespace name 17:22:48 Norm changed his mind, http://norman.walsh.name/2004/03/03/266NorthPleasant 17:23:11 Maybe we should serve http://legacy.w3.org/urn/oasis:names:tc:entity:xmlns:xml:catalog 17:23:12 Zakim, take up item 5 17:23:12 agendum 5. "tagSoupIntegration-54" taken up [from Stuart] 17:23:47 SKW invites TVR to summarize last week's discussion http://www.w3.org/2008/06/12-tagmem-minutes#item06 17:25:00 agenda+ developing dialog with the XRI TC (if time permits - otherwise take to email) 17:25:35 TVR: a provocative question, following ht's attempt to get namespaces into HTML design: does it make sense to work toward convergence of XML and HTML? [tvr quickly gives lots of context at a rate the scribe fails to match] 17:27:35 TVR: [explains 2 extreme positions and some middle ground; scribe would like help recovering them] 17:28:24 TimBL: thanks for the summary... reminds me of discussion about RDFa; the spec sticks to XHTML, but a lot of the practical deployment looks like it's in HTML. [?] 17:28:45 ... likewise, I'd expect that if good tags are added to HTML, they'd get adopted in XHTML 17:29:22 ... there's an issue in that in HTML, there just aren't any namespaces. But you can get around that by saying the root HTML namespace is implicit, based on the media type 17:29:22 action-145? 17:29:22 ACTION-145 -- Tim Berners-Lee to add public prose around his slides at the AC meeting to make the case for extensiblity and flexible XML -- due 2008-06-26 -- OPEN 17:29:22 http://www.w3.org/2001/tag/group/track/actions/145 17:29:44 q? 17:30:05 TimBL: some people are going to need some things from HTML and some things from XML, and keeping those separate isn't going to help 17:30:21 TimBL: pls continue that action; I do hope to get to it 17:31:51 TVR: I agree RDFa is an example of something with bottom-up motivation that works pretty well, techinically; but attempts to integrated it into HTML 5 don't seem to be received well 17:32:23 regrets+ DO 17:32:55 q? 17:33:07 q+ 17:33:10 TVR: [more interesting stuff that consumes too much of the scribe's brain for him to summarize in real time] 17:33:13 ack tim 17:33:50 q+ to waffle in the same general space as TVR 17:34:52 Raman pose two questions to encourage convergence: what changes to namespaces could be accomodated; likewise for XML. In each case also consider who benefits from what changes (IIRC) 17:35:10 q? 17:35:30 q+ 17:35:43 ack Norm 17:35:43 Norm, you wanted to waffle in the same general space as TVR 17:36:07 [scribe missed some from TVR and TimBL] 17:37:01 NDW: I've been thinking/writing about the situation with HTML and XML; I can see technical rationale for convergence, but I don't see that the respective communities have sufficient motivation 17:38:06 TVR: I think this fork in the web is a really bad thing... one possibility is that the two languages come together such that when you're writing, you don't think of two languages but just one 17:38:20 ... but there's also... let's call it the cohabitation question 17:38:35 q+ to mutter about open/closed language syntax and extensibility v interoperability 17:39:02 ... since we haven't asked the co-habitation question, things from one language tend to pollute the other, usually to the detriment of the XML side 17:39:44 The cohabitation question is precisely the question we started this issue with: "Is the indefinite persistence of 'tag soup' HTML consistent with a sound architecture for the Web?" 17:39:45 q? 17:39:48 ack DanC 17:39:57 ... so I think it will help to think about how these two things can sit side by side on the web 17:40:00 q+ to talk about the white space xml mparser flag having 3 values 17:41:21 TVR: much/most Atom/RSS feeds aren't valid 17:41:23 q? 17:43:28 I just tried two random atom feeds, the first was well-formed, the second had an un-escaped & . . . :-( 17:43:36 :-( 17:44:17 q+ to point out xhtml + css is a hands-down winner with authors 17:44:33 q+ to add html tag soup is pushed by the browsers who have the implementations 17:44:42 +10 to DC about innovators: I just spent the morning with a startup who just got 2nd round funding who have a very cool, with customers, xhtml+css+xml schema web site management tool 17:45:52 ack Stuart 17:45:52 Stuart, you wanted to mutter about open/closed language syntax and extensibility v interoperability 17:46:24 We'll trade you namespaces lite for document.write :-) 17:46:56 q? 17:47:04 q+ raman: to add that document.write is the actual dividing issue -- not surface syntax 17:47:39 I understand that the XML whitespace parsing rules are an external parameter given to the parser., an not available anywhere in a follow your nose way. This seems to be a big XML bug. It seems o me to be that the HTML pasring rules are in a similar place. 17:47:58 ack timbl 17:47:58 timbl, you wanted to talk about the white space xml mparser flag having 3 values 17:51:00 discussion of design constraints on RDFa which may be due to problems in other specs or bugs in software... 17:52:52 ... in particular, whether whitespace is preserved in XSLT, and getting at namespace info in XSLT 17:55:23 ack raman 17:55:23 raman, you wanted to point out xhtml + css is a hands-down winner with authors and to add html tag soup is pushed by the browsers who have the implementations 17:56:21 ack raman: 17:56:21 raman:, you wanted to add that document.write is the actual dividing issue -- not surface syntax 17:56:56 TVR: also, much of the tag soup started as clean XML in the author's hand, but then downstream tools emit tag soup 17:57:51 TVR: various syntax fix-ups are manageable, but document.write is fundamentally different. 17:58:17 q? 17:58:25 ... document.write tangles things up... that's why HTML 5 is so contorted 17:59:38 It seems to me that AJAX replaces the need for it, but... 18:00:19 NDW: document.write is too far deployed to say "don't do that"? 18:00:26 HT: it's in google ads and such 18:00:48 DanC: TV gave me some hope that's not permanent, that it's manageable over years 18:00:50 q? 18:01:47 TVR: yes... much of the stuff that was necessary for interop in the 2001-2003 timeframe isn't necessary in current browsers, but there's a feedback loop that is hard to break 18:03:43 ACTION-7? 18:03:43 ACTION-7 -- Dan Connolly to work with Olivier and Tim to draft a position regarding extensibility of HTML and the role of the validator for consideration by the TAG -- due 2008-05-15 -- PENDINGREVIEW 18:03:43 http://www.w3.org/2001/tag/group/track/actions/7 18:09:17 Does anyone have an architecture for an extensible validator? 18:10:16 yes, they announced a "unicorn" design 18:14:40 agenda ? 18:17:35 action-7? 18:17:35 ACTION-7 -- Tim Berners-Lee to draft a position regarding extensibility of HTML and the role of the validator for consideration by the TAG -- due 2008-06-26 -- PENDINGREVIEW 18:17:35 http://www.w3.org/2001/tag/group/track/actions/7 18:17:53 action-7? 18:17:53 ACTION-7 -- Tim Berners-Lee to draft a position regarding extensibility of HTML and the role of the validator for consideration by the TAG -- due 2008-07-31 -- OPEN 18:17:53 http://www.w3.org/2001/tag/group/track/actions/7 18:18:43 Zakim, take up item 4 18:18:43 agendum 4. "XMLVersioning-41" taken up [from Stuart] 18:19:14 Alternative language versioning formalism Jonathan Rees (Tuesday, 27 May) 18:19:19 http://lists.w3.org/Archives/Public/www-tag/2008May/0155.html 18:21:10 Def. L is extensible if there is an L' that extends it. 18:23:23 -Ht 18:23:34 action-149? 18:23:34 ACTION-149 -- Henry S. Thompson to henry to help Jonathan with ACTION-148 and ACTION-158 -- due 2008-05-26 -- OPEN 18:23:34 http://www.w3.org/2001/tag/group/track/actions/149 18:23:39 action-158? 18:23:39 ACTION-158 -- Jonathan Rees to write up thoughts on versioning and share with the group -- due 2008-05-28 -- PENDINGREVIEW 18:23:39 http://www.w3.org/2001/tag/group/track/actions/158 18:24:03 close action-158 18:24:03 ACTION-158 Write up thoughts on versioning and share with the group closed 18:24:30 close action-149 18:24:30 ACTION-149 Henry to help Jonathan with ACTION-148 and ACTION-158 closed 18:24:35 action-148? 18:24:35 ACTION-148 -- Jonathan Rees to see if he can develop a formal basis for the definition of extensibility, possibly includiing definitions of forwards/backwards compatibility -- due 2008-05-26 -- CLOSED 18:24:35 http://www.w3.org/2001/tag/group/track/actions/148 18:24:56 action-158? 18:24:56 ACTION-158 -- Jonathan Rees to write up thoughts on versioning and share with the group -- due 2008-05-28 -- CLOSED 18:24:56 http://www.w3.org/2001/tag/group/track/actions/158 18:26:18 action-158? 18:26:18 ACTION-158 -- Jonathan Rees to write up thoughts on versioning and share with the group -- due 2008-05-28 -- PENDINGREVIEW 18:26:18 http://www.w3.org/2001/tag/group/track/actions/158 18:26:27 SKW: I hope to pick this up again when DO is around 18:26:40 Zakim, close item 6 18:26:40 agendum 6, Issues and Action Item review., closed 18:26:40 agenda ? 18:26:41 I see 6 items remaining on the agenda; the next one is 18:26:43 agenda? 18:26:43 3. scalabilityOfURIAccess-58 [from Stuart] 18:27:12 Zakim, take up item 8 18:27:12 agendum 8. "public suffix list" taken up [from DanC] 18:27:25 http://lists.w3.org/Archives/Public/www-tag/2008Jun/0095.html 18:27:29 public suffix list: when opacity meets security [metaDataInURI-31 siteData-36] 18:30:53 how would you do a follow your nose from a URI scheme name? 18:31:45 it seems to be there is at least human redirection through the IANA scheme registry to specifications.... 18:31:53 the list: http://mxr.mozilla.org/mozilla-central/source/netwerk/dns/src/effective_tld_names.dat?raw=1 18:31:58 and those specifications refer to other specification... 18:32:28 -Ashok_Malhotra 18:32:30 -Norm 18:32:35 -jar 18:32:40 Norm has joined #tagmem 18:34:40 -TimBL 18:34:44 -Stuart 18:34:56 -Raman 18:35:14 Stuart has left #tagmem 18:39:57 disconnecting the lone participant, DanC.a, in TAG_Weekly()1:00PM 18:40:00 TAG_Weekly()1:00PM has ended 18:40:01 Attendees were Raman, jar, Stuart, Ht, Ashok_Malhotra, Norm, DanC.a, TimBL 18:43:27 Norm has joined #tagmem