14:53:08 RRSAgent has joined #rdfa 14:53:08 logging to http://www.w3.org/2009/07/09-rdfa-irc 14:53:15 Zakim has joined #rdfa 14:53:24 zakim, this will be rdfa 14:53:27 ok, msporny; I see SW_SWD(RDFa)11:00AM scheduled to start in 7 minutes 14:53:41 Meeting: RDFa in XHTML Task Force 14:53:49 Chair: Manu_Sporny 14:54:00 rrsagent, make log public 14:54:08 Present: Manu_Sporny 14:54:21 Regrets: Ben_Adida, Michael_Hausenblas 14:54:45 Agenda: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Jul/0032.html 14:54:58 Previous: http://www.w3.org/2009/06/25-rdfa-minutes.html 14:55:50 rrsagent, draft minutes 14:55:50 I have made the request to generate http://www.w3.org/2009/07/09-rdfa-minutes.html msporny 15:03:25 Present+ Steven_Pemberton 15:04:01 SW_SWD(RDFa)11:00AM has now started 15:04:08 +ShaneM 15:04:16 zakim, dial steven-617 15:04:16 ok, Steven; the call is being made 15:04:17 +Steven 15:04:27 ShaneM has joined #rdfa 15:04:32 +??P7 15:04:33 markbirbeck has joined #rdfa 15:04:41 zakim, I am ??P7 15:04:50 +msporny; got it 15:07:00 Present+ Shane_McCarron 15:08:01 zakim, who is on the call? 15:08:01 On the phone I see ShaneM, Steven, msporny 15:08:53 ACTION: Ben to author wiki page with charter template for RDFa IG. Manu to provide support where needed. [recorded in http://www.w3.org/2009/05/28-rdfa-minutes.html#action10] 15:08:55 -- CONTINUES 15:09:02 ACTION: Ben to prepare "how to write RDFa" screencast with fragment parser [recorded in http://www.w3.org/2009/06/11-rdfa-minutes.html#action05] 15:09:04 -- CONTINUES 15:09:11 ACTION: Mark create base wizard suitable for cloning [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action12] 15:09:13 -- CONTINUES 15:09:23 ACTION: Mark to send Ben ubiquity related wizard stuff [recorded in http://www.w3.org/2008/11/20-rdfa-minutes.html#action11] 15:09:31 -- CONTINUES 15:09:45 ACTION: Mark write foaf examples for wiki [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action13] 15:09:47 -- CONTINUES 15:09:58 ACTION: Ralph find the statement on test suite copyright [recorded in http://www.w3.org/2009/06/04-rdfa-minutes.html#action13] 15:10:00 -- CONTINUES 15:10:13 ACTION: Ralph make a request for an RDFa issue tracker instance [recorded in http://www.w3.org/2009/05/28-rdfa-minutes.html#action11] 15:10:15 -- CONTINUES 15:10:31 zakim, code? 15:10:31 ACTION: Ralph or Steven fix the .htaccess for the XHTML namespace [recorded in http://www.w3.org/2009/01/08-rdfa-minutes.html#action01].org/2009/01/08-rdfa-minutes.html#action01] 15:10:32 the conference code is 7332 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), markbirbeck 15:10:33 -- CONTINUES 15:10:58 ACTION: Ralph think about RSS+RDFa [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action15]008/09/11-rdfa-minutes.html#action15] 15:11:02 -- CONTINUES 15:11:15 + +0208761aaaa 15:11:21 zakim, i am aaaa 15:11:21 +markbirbeck; got it 15:12:20 Manu: Any changes to agenda? 15:12:51 Agenda: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Jul/0032 15:12:53 markbirbeck: I'm concerned about safe CURIEs in @rel 15:13:22 markbirbeck: Could we move #4 up to the first item? 15:13:48 markbirbeck: It might help to address major objections - it's been hanging on for some time. 15:14:02 markbirbeck: Simple solution is to do safe CURIEs in @rel. 15:14:53 Manu: Moving agenda item 4 up to 1 15:15:06 Topic: Use of regular CURIEs in @rel 15:15:22 ShaneM: I don't think we can do safe CURIEs in @rel 15:15:30 markbirbeck: I think this is a broader problem 15:15:46 markbirbeck: I think the whole issue is @rel="URL" is happening in Atom and other standards. 15:16:01 markbirbeck: We should recognize that this is a broader thing that people take issue with. 15:16:14 markbirbeck: We should come up with a major clarification, or we should try to come up with a solution. 15:16:22 markbirbeck: Just trying to set the context for this discussion. 15:16:27 ShaneM: I agree that that is the context. 15:16:41 ShaneM: I think it's good that people are using 'relations' with URIs. 15:16:50 ShaneM: I don't think that Atom has anything to do with HTML. 15:16:59 ShaneM: different protocol, different markup language. 15:17:13 ShaneM: If we were to change the syntax of @rel now, it would break every page that is using RDFa already. 15:17:22 ShaneM: It is an incompatible, dramatic, drastic change. 15:17:39 Steven: I think you're right - it was a decision we made long ago. 15:17:44 Steven: I don't think it's a good idea. 15:18:01 Ralph has joined #rdfa 15:18:20 markbirbeck: The argument when we made the decision was what happens when we use legacy values. 15:18:22 +Ralph 15:18:34 markbirbeck: It didn't occur to us at the time that it didn't preclude using safe CURIEs. 15:18:36 [apologies for being late] 15:18:55 markbirbeck: So we could've done it, but we didn't do it. It's a shame, really. 15:19:00 s/being/arriving 15:19:07 markbirbeck: There is another use case - the only way to get a URL into @rel is to use a CURIE. 15:19:16 I have made the request to generate http://www.w3.org/2009/07/09-rdfa-minutes.html Ralph 15:19:21 markbirbeck: It's the xmlns:http hack... 15:19:30 markbirbeck: It's a bit of a pain for some scenarios. 15:19:47 Present+ Mark_Birbeck 15:19:47 markbirbeck: I can see why people don't like it - it requires prefix mappings to be there. 15:20:13 Steven: Since you have URLs in some places and CURIEs in some places 15:20:26 Steven: A typical syntax for that is to use <> when you use a URI. 15:20:40 Steven: This wouldn't work now, ofcourse. 15:20:57 markbirbeck: The ideal scenario would be that every attribute could carry a CURIE, URI or token. 15:21:14 markbirbeck: The use of XML namespaces in RDF makes the assumption that you have this concept of a prefix... it's baggage. 15:21:15 well, it would be difficult in XML/HTML, since < and > have special meaning 15:21:36 {http://www.w3.org} 15:21:40 markbirbeck: Maybe we should explore Shane's point about it breaking something. 15:21:57 ShaneM: Look at Google's implementation = v:foo 15:21:59 «http://www.w3.org» 15:22:25 markbirbeck: One way to do it would be to signal a switch - to specify which version of RDFa you are using. 15:22:39 |http://www.w3.org| 15:22:42 ShaneM: We didn't require any sort of announcement mechanism. 15:22:55 ShaneM: @profile and @version come to mind. 15:23:13 markbirbeck: There is nothing to stop defining RDFa in X as different in RDFa in Y. 15:23:24 Steven: It would be nice if we had a unified syntax. 15:23:38 Steven: Can't we find a good way of marking a URI when a CURIE is expected? 15:24:02 Ralph: If there are reasons for RDFa to be different because of host language matters, that's one thing. 15:24:35 Ralph: I don't have to want to know that there are different versions of RDFa. 15:24:44 markbirbeck: The google example will have a defined namespace. 15:24:57 markbirbeck: That namespace will be defined. 15:25:06 Steven: Every CURIE or token begins with a letter. 15:25:13 Steven: We just have to choose a non-letter. 15:25:17 ShaneM: I disagree. 15:25:36 ShaneM: It's as simple as saying that if a namespace is not defined, then it is a URI. 15:25:42 markbirbeck: Yes. 15:25:57 markbirbeck: We probably discussed this ages ago - but not that it is so pressing, we should revisit this. 15:26:15 markbirbeck: Do we get any false positives? 15:26:35 markbirbeck: Do you falsely get a URL when somebody forgot to add the namespace? Yes... but tough. 15:26:42 markbirbeck: We should also allow square brackets. 15:28:01 ShaneM: What happens when somebody re-defines "urn:"? 15:28:14 Manu: Tough - they made a concious decision to do so. 15:28:18 markbirbeck: I agree. 15:28:30 markbirbeck: @rel="URL" is a handy thing. 15:28:43 markbirbeck: It addresses the cut/paste problem. 15:28:56 markbirbeck: If you're generating a snippet, you might as well just use URLs. 15:29:26 markbirbeck: I think what happened with square brackets was that we didn't like rel="[next]" and people didn't like that. 15:29:47 markbirbeck: We never went down the road of only use rel="[prefix:suffix]" 15:30:17 markbirbeck: "if the prefix is undefined, it's a URI" would work everywhere. 15:30:32 ShaneM: The TAG has made it very clear that the issue with CURIEs is that they look like URIs. 15:31:03 ShaneM: Now we're going down a road that may upset the TAG - all of a sudden it's difficult to differentiate between CURIEs and URIs. 15:31:20 Steven: We had no choice - we didn't invent this. 15:31:32 Steven: we extended an existing notation. 15:31:42 Steven: It looks just like QNames. 15:31:52 ShaneM: They TAG has a dislike for QNames in attributes. 15:32:01 Ralph: That's correct, that practice was not encouraged. 15:32:14 (in attribute _values_ ) 15:32:32 markbirbeck: The presence of a namespace prefix mapping makes it clear what you mean. 15:32:54 markbirbeck: You can diferentiate them when the statement in context. 15:33:44 Manu: Do we want to pass this approach by the list? 15:33:50 ShaneM: It doesn't even change the RDFa in XHTML spec. 15:34:25 markbirbeck: It's backwards compatible. 15:34:37 ShaneM: The RDFa in XHTML spec would have to change a bit. 15:34:56 markbirbeck: We may want to write an RDFa in HTML spec, that states this new rule. 15:35:51 Topic: Processing of xmlns:* in non-XML languages 15:36:53 Manu: Mark can you start by talking about the @token proposal? 15:37:09 markbirbeck: Yes - the @token is about bridging to the simplicity of Microformats. 15:37:30 markbirbeck: We may want to also help people create tokens on the fly to represent full URIs in a Microformats-style way. 15:38:11 markbirbeck: This @token spec would allow authors to define tokens, regardless of the host language. 15:38:30 markbirbeck: Instead of doing @prefix - you'd use @token. 15:38:54 markbirbeck: You could use 'dc' on it's own, without having to use a reference or suffix. 15:39:07 markbirbeck: The criticism is "How do you follow your nose?" 15:39:28 markbirbeck: Do you really need to make a request to find out what the tokens are? Via @profile? 15:39:52 markbirbeck: One answer is that for many of the standard use cases, you wouldn't have to go off to make the retrieval. 15:40:08 markbirbeck: Ben's criticism wonders whether the mapping should be done at another level. 15:40:27 markbirbeck: He's not here to make that case, so we may not be able to get much further one this. 15:40:52 Manu: Shane, elaborate on criticism of @token proposal? 15:40:59 ShaneM: Not concerned about multiple requests. 15:41:09 ShaneM: We make MANY connections when loading a web page 15:41:19 ShaneM: We also cache stuff - so it's not an issue... it's how it should work. 15:41:35 ShaneM: Manu and I put together a proposal that is similar to this called RDFa Profiles. 15:41:59 ShaneM: We started this discussion thinkinking that it is just a mental model - now we know that it's not. 15:42:23 ShaneM: The problem we're trying to solve is to see if there is a way for authors to extend the list of reserved words. 15:42:46 ShaneM: The proposal that Manu and I had was that the proposal needed an external document. 15:42:59 ShaneM: The external document was turned for RDF automatically. 15:43:27 ShaneM: My criticism of the @token proposal is that it's not clear how we get from embedded declaration to the RDF declaration. How do you follow your nose with @token? 15:43:36 ShaneM: I think that's Ben's concern as well. 15:44:16 markbirbeck: Just to understand... do you mean "What would the external document look like?" 15:44:23 markbirbeck: Or how to you get from @token to RDF. 15:44:34 markbirbeck: All I'm proposing is a small change to the CURIE spec. 15:44:43 ShaneM: Yes, I get that. 15:45:05 markbirbeck: So the minor change is that we can expand prefixes for CURIEs and stop there. 15:45:20 markbirbeck: The external document should itself be HTML+RDFa... as long as it maps to a set of triples. 15:45:36 markbirbeck: Somehow we get a list of mappings from that external document. 15:45:50 markbirbeck: The first approach is we just have @token and that's how the mapping is created. 15:46:13 markbirbeck: Not saying anything about the syntax in the @token attribute. 15:46:33 q+ to discuss using xmlns: 15:46:37 markbirbeck: Just saying that if one of the prefixes match in a CURIE via a @token, it should be used. 15:47:04 ack Shane 15:47:04 ShaneM, you wanted to discuss using xmlns: 15:47:36 ShaneM: If what we're talking about is having dynamically extensible reserved words... we should divorce the conversation from new attributes. 15:47:44 ShaneM: If that is a fine thing to do, then so be it. 15:48:31 ShaneM: We should make sure that the endpoint should be HTML+RDFa. 15:48:45 ShaneM: The thing that is referenced should be an HTML+RDFa document. 15:49:00 Ralph: The whole semantic web stack should be dereference-able in some RDF form. 15:49:40 ShaneM: In the case of Microformats, we talked about how to extend the XMP format that they use with RDFa to give something that looks almost exactly like Microformats. 15:49:46 We already support this: 15:49:51 @xmlns:author="http://example.org/author" 15:50:03 @rel="author:" 15:51:14 (not Adobe XMP, evidently?) 15:52:10 markbirbeck: I think we should move away from using prefix:suffix to something that could expand without the colon. 15:52:39 markbirbeck: so why not this: xmlns:author="http://example.org/author" and then rel="author" 15:52:52 markbirbeck: It makes it very easy to do cut/paste snippets. 15:53:16 markbirbeck: This is the "let's make it easier" approach. 15:53:24 markbirbeck: So, how do we define these things? 15:53:38 markbirbeck: We all agree that we need to create @prefix, so why not @token. 15:53:48 markbirbeck: If we are going to add a new attribute, why not add this feature as well? 15:54:02 ShaneM: This is a fine approach. 15:54:38 s/XMP/XMDP/ 15:55:22 ShaneM: Ben's position is to say that it works. 15:55:44 Ralph: There will probably be a discussion on xmlns:* 15:56:57 "RDFa means extensibility (which is why some people will never support it)": http://webbackplane.com/mark-birbeck/blog/2009/01/rdfa-means-extensibility 15:57:22 Ralph: xmlns:* isn't necessarily dead, but we might want to introduce another mapping mechanism to aid the discussion. 15:57:43 Good luck Ralph. 15:58:12 ShaneM: So, we could write a new CURIE spec since there isn't a current CURIE spec. 15:58:13 s/There will probably be/There will be a discussion on distributed extensibility in HTML and that will probably include 15:58:38 ShaneM: if we change anything like this, we're going to have to rev the spec. 15:58:48 ShaneM: If we are going to rev the spec, it would be a good change. 15:59:09 markbirbeck: If we add @prefix, why not call it @token - that's where I was coming from. 15:59:29 there should be incremental improvement of RDFa by updating the spec. 15:59:35 s/XMP format/XMDP format 15:59:42 markbirbeck: People still have to decide whether to use RDFa or Microformats. 15:59:55 s/(not Adobe XMDP, evidently?)// 16:00:00 markbirbeck: We should consider that when revving the spec. 16:00:07 I have made the request to generate http://www.w3.org/2009/07/09-rdfa-minutes.html Ralph 16:00:34 +1 16:00:59 Topic: Case sensitivity in xmlns: 16:01:13 s/we might want to introduce another mapping mechanism/I'm ok with referring to it by a different name 16:01:14 errata is here http://www.w3.org/MarkUp/2008/REC-rdfa-syntax-20081014-errata/ 16:01:17 I have made the request to generate http://www.w3.org/2009/07/09-rdfa-minutes.html Ralph 16:02:15 ShaneM: DOcument authors should use lower-case xmlns:prefix-names to be compatible across all processors. 16:02:40 ShaneM: +1 16:02:44 Ralph: +1 16:03:12 I want to claim victory on my action w.r.t. test suite license -- see http://www.w3.org/2009/06/11-rdfa-minutes.html#item01 16:03:27 yes, sorry - I didn't fix that in the last minutes. 16:03:33 victory! 16:04:09 markbirbeck: Is it not possible to rev the spec and include HTML? 16:04:14 ShaneM: No, absolutely not. 16:04:27 ShaneM: not chartered to do so. 16:04:36 Ralph: That is correct. 16:05:22 rrsagent, draft minutes 16:05:22 I have made the request to generate http://www.w3.org/2009/07/09-rdfa-minutes.html msporny 16:05:43 Present+ Ralph_Swick 16:07:20 http://www.semanticuniverse.com/premium/audio/semtech-2009-audio-semantics-google-rfda-microformats-and-more.html 16:07:21 -ShaneM 16:07:23 -Ralph 16:07:24 -Steven 16:07:26 -markbirbeck 16:07:39 Ralph, want me to clean up and send you the minutes? 16:07:46 That's the SemTech talk from Google, for those who couldn't be there. 16:07:51 yes, please, Manu; thanks 16:07:55 -msporny 16:07:57 SW_SWD(RDFa)11:00AM has ended 16:07:58 Attendees were ShaneM, Steven, msporny, +0208761aaaa, markbirbeck, Ralph 16:08:15 rrsagent, draft minutes 16:08:15 I have made the request to generate http://www.w3.org/2009/07/09-rdfa-minutes.html msporny 16:08:51 here's what I was refering to: 16:08:52 As to "polyglot" - again, I have to disagree. There is nothing in the current HTML5 draft that permits the use of rich compound documents that bring in multiple namespaces. There is also nothing that makes it possible to define extensions to the language in either of its forms. If there were, we wouldn't be having this conversation. 16:08:52 XHTML M12N permits these things and more. That extensibility is at the core of XHTML and the XHTML Family of modules and markup languages. XHTML conforming processors will happily adapt to new XHTML family markup languages, so I can sit in my little walled garden and add elements to my private markup language and it will still. just. work. That's the whole point. And HTML5 misses it. Completely. 16:09:32 Eloquently put. 16:09:55 But if we were defining extensibility today, would we use XML schemas and DTDs? 16:10:06 There must be an easier way. :) 16:10:10 :) 16:12:11 rrsagent, bye 16:12:11 I see 9 open action items saved in http://www.w3.org/2009/07/09-rdfa-actions.rdf : 16:12:11 ACTION: Ben to author wiki page with charter template for RDFa IG. Manu to provide support where needed. [recorded in http://www.w3.org/2009/05/28-rdfa-minutes.html#action10] [1] 16:12:11 recorded in http://www.w3.org/2009/07/09-rdfa-irc#T15-08-53 16:12:11 ACTION: Ben to prepare "how to write RDFa" screencast with fragment parser [recorded in http://www.w3.org/2009/06/11-rdfa-minutes.html#action05] [2] 16:12:11 recorded in http://www.w3.org/2009/07/09-rdfa-irc#T15-09-02 16:12:11 ACTION: Mark create base wizard suitable for cloning [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action12] [3] 16:12:11 recorded in http://www.w3.org/2009/07/09-rdfa-irc#T15-09-11 16:12:11 ACTION: Mark to send Ben ubiquity related wizard stuff [recorded in http://www.w3.org/2008/11/20-rdfa-minutes.html#action11] [4] 16:12:11 recorded in http://www.w3.org/2009/07/09-rdfa-irc#T15-09-23 16:12:11 ACTION: Mark write foaf examples for wiki [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action13] [5] 16:12:11 recorded in http://www.w3.org/2009/07/09-rdfa-irc#T15-09-45 16:12:11 ACTION: Ralph find the statement on test suite copyright [recorded in http://www.w3.org/2009/06/04-rdfa-minutes.html#action13] [6] 16:12:11 recorded in http://www.w3.org/2009/07/09-rdfa-irc#T15-09-58 16:12:11 ACTION: Ralph make a request for an RDFa issue tracker instance [recorded in http://www.w3.org/2009/05/28-rdfa-minutes.html#action11] [7] 16:12:11 recorded in http://www.w3.org/2009/07/09-rdfa-irc#T15-10-13 16:12:11 ACTION: Ralph or Steven fix the .htaccess for the XHTML namespace [recorded in http://www.w3.org/2009/01/08-rdfa-minutes.html#action01].org/2009/01/08-rdfa-minutes.html#action01] [8] 16:12:11 recorded in http://www.w3.org/2009/07/09-rdfa-irc#T15-10-31-1 16:12:11 ACTION: Ralph think about RSS+RDFa [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action15]008/09/11-rdfa-minutes.html#action15] [9] 16:12:11 recorded in http://www.w3.org/2009/07/09-rdfa-irc#T15-10-58 16:12:22 yeah... I am sure there is. but the m12n architecture permits the use of those easier ways 16:12:26 that's just implementation detials