16:45:52 RRSAgent has joined #tagmem 16:45:52 logging to http://www.w3.org/2008/09/11-tagmem-irc 16:46:03 zakim, this will be tag 16:46:03 ok, skw; I see TAG_Weekly()1:00PM scheduled to start in 14 minutes 16:48:04 topic: http://www.w3.org/2001/tag/2008/09/11-agenda 16:48:43 topic is an IRC protocol thingy. so it's: /topic blah blah... 16:48:58 jar has changed the topic to: http://www.w3.org/2001/tag/2008/09/11-agenda 16:49:02 skw has changed the topic to: http://www.w3.org/2001/tag/2008/09/11-agenda 16:49:44 Meeting: TAG Weekly Telcon 16:49:53 Chair: Stuart Williams 16:50:05 Scribe: Ashok Malhotra 16:50:26 Regrets: Noah, Norm 16:58:06 regrets +DaveO(partial) 16:58:45 TAG_Weekly()1:00PM has now started 16:58:51 +??P0 16:58:59 zakim, ?? is me 16:58:59 +skw; got it 16:59:17 +Jonathan_Rees 17:00:46 Ashok has joined #tagmem 17:01:12 +Raman 17:02:26 raman has joined #tagmem 17:02:49 zakim, please call ht-781 17:02:49 ok, ht; the call is being made 17:02:51 +Ht 17:03:48 +Ashok_Malhotra 17:04:45 scribenick: Ashok 17:06:34 Regrets: Noah, Norm, partial regrets DaveO 17:06:48 No comments on agenda 17:07:20 Minutes from Sep 4 approved 17:08:06 +DanC.a 17:08:11 Next week call a risk. Regets from Tim. Stuart may not be able to make it 17:08:27 HT: Use the time to read our documents 17:08:44 Cancel next week's meeting 17:08:54 +1 use the time to read 17:08:55 Next meeting f2f 17:10:05 DanC has changed the topic to: q+ 17:10:08 Raman: If we are serious abt this, all TAG members shd read the HTML spec 17:10:11 q+ 17:10:18 DanC has changed the topic to: http://www.w3.org/2001/tag/2008/09/11-agenda 17:10:28 ack danc 17:11:30 DanC: Please create reading list and Agenda for f2f 17:11:42 Agenda Item 3: Binary XML 17:11:44 s/create/let's finish/ 17:12:08 q+ to acknowledge my EXI actions 17:12:20 ack ht 17:12:21 ht, you wanted to acknowledge my EXI actions 17:12:52 HT: I will read these on the 'plane and make a recommendation on what we shd do 17:14:05 DanC: Last, we said tell us how you are better than gzip 17:14:20 HT: That's where we are 17:14:44 Item 4: URNs and Registries 17:14:47 (though Dec sounds wierd... I thought our request was since Dec) 17:16:01 HT: I'm working on anew document. Shd have it ready middle on next week 17:16:16 s/anew/a new/ 17:17:08 close action-167 17:17:08 ACTION-167 S to start a thread on non-DNS authority resolution on www-tag closed 17:17:35 DanC: What's happening with XRIs? 17:18:17 SKW: Summarizes situation 17:18:49 We have not had a formal proposal saying would you be happy with ... 17:19:40 q+ to check whether skw meant it when he said "prefix", since DNS names go least-significant-first 17:20:22 SKW: We had a discussion on how the discussion was going 17:22:45 ack danc 17:22:45 DanC, you wanted to check whether skw meant it when he said "prefix", since DNS names go least-significant-first 17:22:55 q+ to say there's one thing we will need to chase no matter what 17:23:56 does either booth or bradly advocate an actual prefix? 17:24:04 ack ht 17:24:04 ht, you wanted to say there's one thing we will need to chase no matter what 17:24:25 Abstract Identifier document: http://wiki.oasis-open.org/xri/AbstractIdentifierArchitecture 17:26:04 SKW: That's not the proposal 17:26:26 (Out of order) saying "http://xri.*/*" are XRIS is same as saying "http://*/ark:*" are ARKs ... 17:26:58 And I think there is _some_ room to argue that both of these are OK, if not ideal 17:27:16 Item 5: Self-Describing Web 17:27:48 Noah has incorporated feedback from Norm and SKW: 17:28:13 q+ to ask a question 17:28:15 q+ to think about whether RDFa is critical path: if we leave it aside, what's the audience/purpose? 17:28:18 SKW: Norm and I would be supportive of publication 17:28:23 ack ht 17:28:23 ht, you wanted to ask a question 17:28:58 ht: In a discussion with a student I realized ... 17:29:00 I believe the following: "FYN works iff every party to the story is a) publically accountable 17:29:00 and b) aware of the dependency of the FYN story on their part of it. 17:29:02 " 17:29:43 I think you can follow-your-nose into policies and such that aren't world-readable 17:29:49 q+ 17:30:16 DanC: I would not say 'publically accounatable" 17:30:20 q? 17:30:38 HT: The parties have to be publically accountable 17:31:07 SKW: The draft does not say this 17:31:26 HT: I would like to discuss this 17:31:34 SKW: Pl. send comment 17:31:51 DanC: I disagree for 3 reasons 17:32:26 (I ran out after 2) 17:32:53 (1) need not be world-readable 17:33:04 (2) the URI for text/plain isn't actually critical path 17:33:07 ... currently 17:33:21 (though it's nice that the text/plain full URI is in an RFC) 17:33:27 HT: I will send mail on this 17:33:29 ack danc 17:33:29 DanC, you wanted to think about whether RDFa is critical path: if we leave it aside, what's the audience/purpose? and to 17:33:30 ack danc 17:34:03 DanC: How can we finish without RDFa story? 17:34:58 DanC: I'm not sure story holds up 17:35:28 SKW: can we document missing link and encourage them to put it in place. 17:35:47 http://www.w3.org/2001/tag/2008/09/f2fkc-agenda 17:35:53 Item 6 on Agenda 17:36:52 SKW: Talks abt the f2f agenda. Thanks Raman for his help 17:37:14 DanC: I would like to negotiate the reading list now 17:37:14 Zakim, who's on the phone? 17:37:14 On the phone I see skw, Jonathan_Rees, Raman, Ht, Ashok_Malhotra, DanC.a 17:38:28 I hear from skw: urnsregs, binaryxml, html*, 17:38:32 digest of ? 17:38:39 SKW: Shd read binary XML specs, HTML spec, collected digest of refernces from Raman's thread 17:38:42 self-describing web draft 17:38:55 passwords in the clear 17:38:58 Self-describing Web, Password in Clear, Versioning 17:39:01 versioning revision from david 17:39:45 +Dave_Orchard 17:39:58 Need two readers for Binary XML, HT is one. 17:41:04 URNs AneRegistries ... HT writing paper. Due Tuesday. Shd be read by f2f 17:41:54 * tim's bit 17:41:56 HT: We shd alll have read Tim's paper 17:42:07 a/alll/al/ 17:42:22 also had an explicit request from David for Jar's formal treatment... 17:42:26 s/alll/all/ 17:43:20 "the document"... one document on versioning? 17:43:30 DO nominates JAR's formalism 17:43:41 -Ht 17:44:03 +Ht 17:44:06 DaveO: What is new is Jonathan's formalism. Recommend people read this by f2f 17:44:28 DO: key chapter is ch5 17:44:38 DaveO: Please review Chapter 5. That is new and is key 17:46:27 HT nominates SVG and HTML thread from public-html... a dozen messages 17:46:58 HT: Read SVG and HTML thread. Read 10 msgs and get a feeling of the context 17:47:02 TVR 2nds... long thread... read for motivations 17:47:43 q+ html5/w3c history? 17:47:54 q+ jar 17:48:00 (looks like TVR's agenda input subsumes HT's suggestion to read a thread) 17:48:15 noah has joined #tagmem 17:49:14 TVR: Read HTML spec with a view thru the structuring lens I proposed 17:49:38 +Noah_Mendelsohn 17:49:57 JR: Is there a document that tells why W3C got involved in html5 17:50:55 Are you discussing reading list? 17:51:04 http://wiki.oasis-open.org/xri/AbstractIdentifierArchitecture 17:51:12 ? 17:51:37 DanC: I can point to formal mataerial but that's not what you want 17:53:03 on mime types... a section of the html spec 17:54:13 pwinc fri 17:54:18 Friday's OK if short, I think. 17:54:28 (thanks; I was just gonna ask for irc convirmation) 17:55:17 Noah: Are we all supposed to read whole HTML spec? 17:56:46 nm nominates thread on meeting goals 17:57:11 Noah: Please read thread on Tag Soup 17:57:50 HT: Norm is not coming to Kansas City 17:58:24 I think that the thread Noah referred to is based at: http://lists.w3.org/Archives/Member/tag/2008Aug/0019.html 18:00:35 DanC: I will send mail before EOD after editing agenda page 18:01:08 Possible topic GenricResources-53 18:01:25 Content negotiation and Abstract Documents 18:01:42 Not on agenda currently. You can looby me. 18:02:16 s/looby/lobby/ 18:02:55 TVR: Steve said he was pulling in my TPAC proposal 18:03:13 Item 8 -- AbberviatedURI-56 18:04:00 SKW: Asks abt status of CURIE comments 18:04:18 (anybody have a summary of the comment? the subject line was a generic "comments on X") 18:04:32 Noah: That's for responder to say 18:05:08 SKW: Summarizez comments 18:05:43 Editorial: Qnames never inted as attribute values. Some discussion on this 18:06:07 (pls promote that "main substantive comment" to the subject line) 18:06:11 SKW: Definition of XML Schema datatype 18:06:16 Please remember that we have already fed back on this point, see http://lists.w3.org/Archives/Public/www-html-editor/2008JanMar/0014.html 18:06:23 q+ to point to our earlier comments 18:06:41 queue=jar,ht 18:06:51 ? 18:07:48 AM: Noah you had a comment on lack of clarity between CURIE and URI where there is ambiguity 18:09:27 Noah: I sent this as a personal comment. If no objection, I can add to my note 18:10:14 q? 18:10:31 the whole point of safecurie was so that they can be put in uri contexts 18:11:12 q? 18:11:13 yes, now that I understand the comment, it seems to miss the point of safecuries 18:11:31 Well, it hijacks the use of [ in everyone's languages. 18:11:38 Raman: I'm uncomfotable with this. We need to allow new syntax in old contexts 18:11:45 q+ daveo 18:11:58 ack jar 18:12:01 q+ to say implying safecuries can be used in existing languages where URIs are expected hijacks the use of [ in those languages. 18:12:34 ack ht 18:12:58 jar: If there was no intention of extensing URI content there would be no CURIEs 18:13:00 RDFa already would violate a prohibition on safecuries. It's too late to prohibit safecuries 18:13:27 s/no CURIEs/no SafeCURIEs/ 18:13:41 HT: We shd be careful abt distinguishing between CURIE's and SafeCURIES 18:13:41 Please remember that we have already fed back on this point, see http://lists.w3.org/Archives/Public/www-html-editor/2008JanMar/0014.html 18:13:59 q? 18:14:35 HT: We shd not go back on that advice 18:15:48 TVR: The way Noah phrased it it sets a very high bar for new syntax 18:15:56 Two questions here! (1) CURIEs in URI contexts? (No.) (2) SafeCURIEs in URI contexts? (RDFa requires.) 18:16:11 -Dave_Orchard 18:16:30 -Ht 18:16:39 ack noah 18:16:39 noah, you wanted to say implying safecuries can be used in existing languages where URIs are expected hijacks the use of [ in those languages. 18:16:46 +Dave_Orchard 18:18:13 Noah: Explains his POV ... I shd open my spec to other syntax 18:18:28 relative URIs can start with [, yes? 18:18:35 timbl has joined #tagmem 18:18:42 They shd make clear that these things are not URis 18:18:45 ack daveo 18:19:16 DaveO: Supports Noah. CURIEs cannot be wedged into existing specifiactions 18:19:18 I repeat: There are two questions here! (1) CURIEs in URI contexts? (No.) (2) SafeCURIEs in URI contexts? (RDFa requires.) 18:19:46 -Dave_Orchard 18:19:49 jar, does RDFa use ? I see deployment problems there. 18:20:00 http://www.w3.org/mid/48B810F4.60807@aptest.com 18:20:05 DaveO: Must specify how CURIEs and URI are disambiguated 18:20:40 no, but it allows safecuries in other uri contexts, I believe. will check. 18:21:19 ok. deployment considerations for a/@href are somewhat special 18:21:49 TVR: XSLT uses { } is attribute value templates. Use of a special character 18:21:54 ok, URIorSafeCURIE only occurs in attributes that are newly added by RDFa 18:21:56 I did propose text to Shane on 8/29: 18:21:56 18:21:56 CURIEs and safe-CURIEs map to IRIs, but neither a CURIE nor a safe-CURIE 18:21:56 is an IRI or URI. Accordingly, CURIEs and safe-CURIEs 18:21:56 MUST NOT be used as values for attributes that are specified to contain 18:21:57 only URIs, IRIs, URI-references, IRI-references, etc. Specifications for 18:22:03 particular attribute values or other content MAY be written to allow 18:22:03 either CURIEs or IRIs (or URIs, etc.). The specifications for such 18:22:03 languages MUST provide rules for disambiguition in situations where the 18:22:05 same string could be interpreted as either a CURIE or an IRI. One way to 18:22:07 do this is to require that all CURIEs be expressed as safe-CURIEs, 18:22:09 implying that all unbracketed strings are to be interpreted as IRIs. 18:22:11 18:24:14 TVR: I'm mostly OK with this. 18:25:02 x:y 18:25:06 JAR: I'm bothered by saying "CURIES are not IRIs". There are bstrings that are both. 18:26:07 noodling... "neither every CURIE nor every safe-CURIE is an IRI or URI" 18:27:10 Noah: I will put this in a note to the TAG list and people call comment 18:27:45 s/call/can/ 18:28:36 So, Stuart, what's the next step on the response. 18:28:44 SKW: Let's conclude on email. 18:29:49 SKW: Noah to redraft considering Stuart's proposal on intent of qnames and add 8/29 draft text on using CURIEs where URIs expected 18:30:44 SHW: Any progress on 171 18:30:50 Dan: No. 18:30:54 -Raman 18:30:57 -Noah_Mendelsohn 18:31:03 zakim, make logs public 18:31:03 I don't understand 'make logs public', Ashok 18:31:06 p.s. any hosting issues? 18:31:27 rrsagent, make logs public 18:31:41 zakim, whois here? 18:31:41 I don't understand your question, skw. 18:31:51 zakim, who is here? 18:31:51 On the phone I see skw, Jonathan_Rees, Ashok_Malhotra, DanC.a 18:31:52 On IRC I see timbl, noah, raman, Ashok, RRSAgent, Zakim, skw, ht, jar, trackbot, DanC 18:31:56 zakim, list participants 18:31:56 As of this point the attendees have been skw, Jonathan_Rees, Raman, Ht, Ashok_Malhotra, DanC.a, Dave_Orchard, Noah_Mendelsohn 18:32:18 rrsagent, pointer 18:32:18 See http://www.w3.org/2008/09/11-tagmem-irc#T18-32-18 18:43:40 raman has left #tagmem 18:49:02 -skw 18:49:03 -Ashok_Malhotra 18:49:05 -Jonathan_Rees 18:49:17 skw has left #tagmem 18:54:06 disconnecting the lone participant, DanC.a, in TAG_Weekly()1:00PM 18:54:08 TAG_Weekly()1:00PM has ended 18:54:09 Attendees were skw, Jonathan_Rees, Raman, Ht, Ashok_Malhotra, DanC.a, Dave_Orchard, Noah_Mendelsohn 19:54:35 hmm... decisions decisions... 19:54:43 collect all preparation materials in one place in the agenda... 19:54:54 or tuck them under the relevant items? 19:55:00 I lean toward tucking, so far 19:55:48 hmm... how to do a crawl-and-zip...? 20:46:33 Zakim has left #tagmem 22:46:21 timbl_ has joined #tagmem