14:53:58 RRSAgent has joined #rdfa 14:53:58 logging to http://www.w3.org/2009/08/06-rdfa-irc 14:54:07 Zakim has joined #rdfa 14:54:13 zakim, this will be RDFa 14:54:13 ok, msporny; I see SW_SWD(RDFa)11:00AM scheduled to start in 6 minutes 14:54:22 Scribe: Manu_Sporny 14:54:26 Chair: Ben_Adida 14:54:34 Regrets: Michael_Hausenblas 14:54:42 Present: Manu_Sporny, Mark_Birbeck 14:54:57 Meeting: RDF in XHTML Task Force 14:55:37 Agenda: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Aug/0039.html 14:55:48 rrsagent, make log public 14:55:58 rrsagent, draft minutes 14:55:58 I have made the request to generate http://www.w3.org/2009/08/06-rdfa-minutes.html msporny 14:56:31 previous: http://www.w3.org/2009/07/30-rdfa-minutes.html 14:56:35 rrsagent, draft minutes 14:56:35 I have made the request to generate http://www.w3.org/2009/08/06-rdfa-minutes.html msporny 15:00:23 zakim, code? 15:00:23 the conference code is 7332 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), msporny 15:00:54 SW_SWD(RDFa)11:00AM has now started 15:01:01 +??P7 15:01:07 zakim, I am P7 15:01:07 sorry, msporny, I do not see a party named 'P7' 15:01:10 zakim, I am ??P7 15:01:10 +msporny; got it 15:03:04 ShaneM has joined #rdfa 15:03:29 +ShaneM 15:03:57 present+ Shane_McCarron 15:04:03 +Ben_Adida 15:04:12 present+ Ben_Adida 15:04:47 benadida has joined #rdfa 15:05:22 markbirbeck has joined #rdfa 15:05:45 Sorry I'm late. Just coming. 15:05:56 -ShaneM 15:06:00 +ShaneM 15:06:03 zakim, code? 15:06:03 the conference code is 7332 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), markbirbeck 15:06:43 + +1.208.761.aaaa 15:06:48 zakim, i am aaaa 15:06:48 +markbirbeck; got it 15:08:04 Topic: Action Items 15:08:49 ACTION: Ben to summarize architectural issues (security) re: @profile proposal for tokenizing the web. [recorded in http://www.w3.org/2009/07/30-rdfa-minutes.html#action04] 15:08:58 -- done 15:09:44 ACTION: Shane to produce proposed diff re: XMLLiteral change [recorded in http://www.w3.org/2009/07/30-rdfa-minutes.html#action03] 15:09:53 -- continues 15:10:05 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:10:16 benadida: have made some progress on that, got up early to work on it. 15:10:20 worth reviewing --> http://rdfa.info/wiki/Rdfa-ig-charter 15:10:27 benadida: might want to have people start reviewing that now. 15:10:37 benadida: Focuses around two activities. 15:10:42 benadida: Provide input to HTML WG on RDFa. 15:10:50 benadida: RDFa in XHTML v1.1 15:11:18 benadida: The proposals we're making for simpler syntax (@profile, @token) will push us towards 1.1 for XHTML+RDFa 15:11:28 benadida: Those are the two foci of the RDFa IG. 15:11:37 -- continues 15:12:03 Topic: Continued @profile discussion 15:14:03 http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Aug/0037.html 15:14:15 benadida: That's the summary of the issue... 15:14:26 s/issue.../issues.../ 15:14:39 markbirbeck: @profile is how do we find a bunch of tokens. 15:15:31 benadida: We didn't go too deep without you here, Mark. 15:15:46 benadida: The security issue seems to have struck a chord with Manu and Shane. 15:16:10 benadida: The parser now needs to dereference 3rd party resources and that is an issue with Javascript and XMLHttpRequest. 15:16:31 markbirbeck: Right. 15:16:42 markbirbeck: The substance of my proposal was about the tokenisation aspect. 15:16:59 markbirbeck: We should consider using the tokenization term. 15:17:12 markbirbeck: We should attempt to address the xmlns: issues that people have been concerned about. 15:17:36 markbirbeck: The issues that you are raising are with the mechanism of finding other tokens. 15:18:21 benadida: The question is where in the stack does the tokenization happen? 15:19:09 markbirbeck: I think tokenization does exist. 15:19:16 markbirbeck: This is purely about languages that reflect RDF. 15:19:32 markbirbeck: You're saying that tokenization is part of the CURIE stack. 15:19:51 markbirbeck: Language (N3, RDF/XML) has its own way of expressing RDF. 15:20:22 markbirbeck: CURIEs do a pretty good job of summarizing URIs. 15:20:40 markbirbeck: Why not allow the syntax to not need colons for expressing CURIEs. 15:21:33 benadida: Right, so to be precise: In any implementation, where would it live? 15:21:47 benadida: This would have to live in the layer above the RDF store... 15:21:57 benadida: You have to resolve the CURIE into a URI before you put it into the RDF store. 15:22:43 Shane: Mark's proposal is in essence, in an existing RDFa document today, with a minor change to the processing model, you could declare a token mapping /in-line/ and then use that token mapping as a defined term. 15:23:29 Shane: you could do something like Shane McCarron 15:23:41 benadida: I think the common goal we want is the simpler syntax. 15:24:03 ShaneM has joined #rdfa 15:24:38 Shane McCarron 15:25:25 Manu: These are separate issues, tokenization and @profile. 15:25:40 benadida: Well, what's the goal? 15:25:51 markbirbeck: So, there are a number of goals. 15:25:58 markbirbeck: One of them is that xmlns: is problematic. 15:26:40 markbirbeck: We're trying to make it easier to author. 15:26:54 markbirbeck: The big problem with Microformats was never really the syntax. 15:27:07 markbirbeck: The vocabularies don't scale. 15:27:14 markbirbeck: There isn't a unified parsing mechanism. 15:27:56 markbirbeck: The goal of tokenization is to provide Microformats-like markup. 15:28:51 markbirbeck: I'm proposing a solution for what we agree is a particular problem. 15:29:02 markbirbeck: Tokenization isn't an end in itself. 15:29:06 markbirbeck: it isn't. 15:29:09 q+ to talk about why remote vocabs are a problem 15:29:35 ack shanem 15:29:35 ShaneM, you wanted to talk about why remote vocabs are a problem 15:30:11 ShaneM: I don't think anybody disagrees that we need to provide an easier markup mechanism. 15:30:42 ShaneM: The issue isn't @token - it's that having collections of those terms expressed remotely in a way that is discoverable, is problematic 15:31:01 ShaneM: it's problematic because we have issues with Javascript + XMLHttpRequest. 15:31:14 markbirbeck: Yes, I understand that. 15:31:55 markbirbeck: There are ways of loading remote URLs in Javascript. 15:32:13 markbirbeck: We still haven't addressed the conceptual question... 15:32:52 markbirbeck: There are conceptual issues about mapping at the RDF level. 15:33:15 markbirbeck: We need to get the conceptual level right. 15:33:24 benadida: I think we agree on the approach. 15:33:49 benadida: I think it's a symptom of the conceptual issue. 15:34:29 benadida: I think we're putting too much responsibility on the parser. 15:34:38 benadida: The parser has to dereference 3rd party resources. 15:34:49 benadida: It's a symptom of the larger issue. 15:34:55 markbirbeck: I fundamentally disagree with you. 15:35:26 markbirbeck: There is an issue - how do you get the document? 15:35:37 markbirbeck: But that doesn't tell you anything about the fundamental distinction. 15:36:11 markbirbeck: We have a way of mapping text to URIs. 15:36:25 markbirbeck: currently in RDFa. 15:36:34 markbirbeck: So, using owl:sameAs is problematic. 15:36:56 markbirbeck: All @token does is add a way of mapping text to URIs. 15:37:32 q+ xmlns: and IE 15:37:39 q- 15:37:47 q+ msporny xmlns and IE 15:37:52 q+ 15:38:31 Slightly modify Shane's example, by adding a colon: 15:38:33 Shane McCarron 15:41:47 markbirbeck: So, we can already to the markup above. 15:42:33 markbirbeck: When you're working out CURIEs, the above works. 15:44:29 markbirbeck: The proposal doesn't hinge on @profile or @token - it's just a way to use colon-less reserved words in @property/@rel/etc. 15:45:00 benadida: I don't think we can look at that goal separately from making the syntax simpler. 15:47:42 benadida: If we're looking at the end-goal - looking at the proposal piece-meal doesn't help. 15:48:53 markbirbeck: What I want to stress is that the rdf:subproperty approach requires some mechanism to load an external document. 15:50:35 google's markup: 15:50:36
15:50:36

Blast 'Em Up 15:50:36 Review

15:50:36

by Bob Smith

15:50:37

March 20, 2009

15:50:38

This is a great game. I 15:50:40 enjoyed it from the opening battle to the final showdown 15:50:42 with the evil aliens.

15:50:44

4.5 out of 5 stars

15:50:46
15:51:21
15:51:22

Blast 'Em Up 15:51:22 Review

15:51:22 ... 15:52:05 benadida: You have to dereference at some point. 15:52:14 benadida: But the key is, /when/ you do it. 15:52:36 benadida: Mark, in your proposal, until you dereference the 3rd party resource, you've got nothing that you can do any processing on. 15:52:59 markbirbeck: If you went the @profile route, then yes, you are correct. 15:53:06 markbirbeck: There are different ways of doing it. 15:53:23 markbirbeck: One way is where @profile is hardwired or well-known. 15:54:01 markbirbeck: Your proposal achieves something different than where I see the whole Microformats-style going. 15:54:15 Note that these two approaches (token and default prefix) are complementary. 15:54:27 markbirbeck: provided that they don't use any of the standard terms (such as next/prev/etc). 15:54:52 prefix : reference 15:55:35 q+ to disagree about what curies know about references 15:55:41 ack xmlns: 15:55:43 ack IE 15:55:46 ack msporny 15:56:02 noooooooo! 15:56:05 :) 15:57:10 markbirbeck: With your proposal, its very difficult to mix vocabularies. 15:57:27 markbirbeck: doing this is difficult if not impossible: profile="a=b c=d" 15:57:33 markbirbeck: with your proposal. 15:57:47 benadida: There is some way that we need to resolve these reserved words. 15:57:57 benadida: To fully resolve it, I'd rather we delegate it to the RDF stack. 15:58:09 benadida: Rather than pushing that functionality into the RDFa processor. 15:58:32 benadida: Adding another layer of resolution in the parser is going to cause us more problems than solve issues. 15:59:43 markbirbeck: That is a separate discussion - how do we load other stuff. 15:59:55 markbirbeck: Even if you forget the owl:sameAs stuff. 16:00:02 markbirbeck: One issue is how we map things. 16:00:19 markbirbeck: how do we map yahoo's products to google's products. 16:00:23 markbirbeck: I'm not talking about that. 16:00:31 markbirbeck: I'm talking about simply the abbreviation mechanism. 16:00:46 markbirbeck: my criticism of your proposal, is that there are 2 major criticisms. 16:00:56 markbirbeck: one - you're using suffixes instead of tokens 16:01:17 markbirbeck: we came up with an algorithm in XHTML+RDFa so that you can distinguish those from values. 16:01:37 markbirbeck: problem two - you only solve the problem for one vocabulary in any given context. 16:01:47 benadida: problem one is a small weakness - I agree. 16:01:55 benadida: problem two, I disagree with. 16:02:34 benadida: Google can, in their schema, say v:title maps to dc:title 16:03:28 markbirbeck: What happens when I want to add properties from the Good Relations vocabulary? 16:03:59 markbirbeck: how can I mix vocabularies? 16:04:06 benadida: That's not a problem, it's a feature 16:04:21 benadida: We're addressing authors that want to just use one vocabulary. 16:04:45 q+ to mention that authors can create hybrid vocabs too 16:04:50 markbirbeck: We're getting to the crux of the problem we're trying to solve. 16:05:08 markbirbeck: Most may not understand how to mix vocabularies. 16:06:09 markbirbeck: Most of the work I'm doing requires that you use many, many vocabularies. 16:06:20 markbirbeck: We should work out what we're trying to achieve. 16:06:36 ack shanem 16:06:36 ShaneM, you wanted to disagree about what curies know about references and to mention that authors can create hybrid vocabs too 16:06:57 ShaneM: I disagree that CURIEs don't know about references. 16:07:16 ShaneM: we built into a CURIEs a way to specify a default prefix. 16:07:28 ShaneM: reserved words are also processed first. 16:07:40 ShaneM: I think being able to set the default prefix can be enabled. 16:08:14 benadida: What are the next steps? 16:08:29 markbirbeck: There may be a way of harmonizing the two. 16:08:40 ShaneM: The two proposals are complimentary. 16:08:53 I wonder if it is possible to define a hybrid "vocabulary" that encompasses all of the existing microformat terms? 16:09:20 markbirbeck: Ben, your proposal is that we enable default prefix. 16:09:59 markbirbeck: If we're happy that @token is resolved, then we may be able to enable default prefix. 16:10:28 benadida: Worried about teaching these features. 16:10:38 markbirbeck: I think we focus on the language elements that address the use cases. 16:11:13 reserved terms are checked first in the RDFa processing model... If we permitted "tokens" then those would get evaluated before looking for a default prefix. Ben seems to agree with this. 16:12:15 benadida: I'm worried about the consequences to the stack with your solution... what role are we giving the parser. 16:14:03 -markbirbeck 16:14:05 -ShaneM 16:16:54 ShaneM has left #rdfa 16:23:55 -msporny 16:23:56 SW_SWD(RDFa)11:00AM has ended 16:23:57 Attendees were msporny, ShaneM, Ben_Adida, +1.208.761.aaaa, markbirbeck 16:41:17 rrsagent, draft minutes 16:41:17 I have made the request to generate http://www.w3.org/2009/08/06-rdfa-minutes.html msporny 16:41:39 regrets+ Steven_Pemberton 16:41:49 regrets+ Ralph_Swick 16:41:51 rrsagent, draft minutes 16:41:51 I have made the request to generate http://www.w3.org/2009/08/06-rdfa-minutes.html msporny 16:42:42 s/minutes.html#action10]/minutes.html#action10] -- continues/ 16:42:43 rrsagent, draft minutes 16:42:43 I have made the request to generate http://www.w3.org/2009/08/06-rdfa-minutes.html msporny 16:58:22 rrsagent, bye 16:58:22 I see 3 open action items saved in http://www.w3.org/2009/08/06-rdfa-actions.rdf : 16:58:22 ACTION: Ben to summarize architectural issues (security) re: @profile proposal for tokenizing the web. [recorded in http://www.w3.org/2009/07/30-rdfa-minutes.html#action04] [1] 16:58:22 recorded in http://www.w3.org/2009/08/06-rdfa-irc#T15-08-49 16:58:22 ACTION: Shane to produce proposed diff re: XMLLiteral change [recorded in http://www.w3.org/2009/07/30-rdfa-minutes.html#action03] [2] 16:58:22 recorded in http://www.w3.org/2009/08/06-rdfa-irc#T15-09-44 16:58:22 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] [3] 16:58:22 recorded in http://www.w3.org/2009/08/06-rdfa-irc#T15-10-05