15:04:00 RRSAgent has joined #rdfa 15:04:00 logging to http://www.w3.org/2009/07/16-rdfa-irc 15:04:06 zakim, this will be rdfa 15:04:06 ok, msporny, I see SW_SWD(RDFa)11:00AM already started 15:04:36 zakim, codes? 15:04:36 I don't understand your question, markbirbeck. 15:04:42 zakim, code? 15:04:42 the conference code is 7332 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), markbirbeck 15:04:54 +Ben_Adida 15:05:03 Present: Steven_Pemberton, Shane_McCarron, Ben_Adida, Mark_Birbeck 15:05:20 zakim, dial steven-617 15:05:20 ok, Steven; the call is being made 15:05:21 +Steven 15:05:27 +??P31 15:05:30 +??P12 15:05:37 zakim, i am ??P12 15:05:37 +markbirbeck; got it 15:05:38 zakim, I am ??P31 15:05:38 +msporny; got it 15:05:49 Present+ Ralph_Swick 15:06:08 Agenda: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Jul/0085.html 15:06:28 Previous: http://www.w3.org/2009/07/09-rdfa-minutes.html 15:07:12 Scribe: Manu_Sporny 15:07:17 scribenick: msporny 15:07:23 zakim, who is here? 15:07:23 On the phone I see McCarron, Ralph, Ben_Adida, Steven, msporny, markbirbeck 15:07:25 On IRC I see RRSAgent, Zakim, markbirbeck, benadida, ShaneM, Steven, msporny 15:07:28 Meeting: RDFa in XHTML Task Force 15:07:28 zakim, mccarron is ShaneM 15:07:28 +ShaneM; got it 15:07:38 Chair: Ben_Adida 15:07:46 rrsagent, make log public 15:07:55 rrsagent, draft minutes 15:07:55 I have made the request to generate http://www.w3.org/2009/07/16-rdfa-minutes.html msporny 15:08:16 ShaneM: What about publishing the RDFa errata from the last meeting? 15:08:20 benadida: Yes, we should talk about that. 15:08:34 benadida: We should have a discussion about xmlns 15:09:18 benadida: It should be a different discussion... keep the topics separated 15:09:29 Ralph has joined #rdfa 15:09:33
  • Section 4.1. Document Conformance - In the future it is 15:09:33 possible that RDFa will also be defined in the context of HTML. 15:09:33 Consequently document authors SHOULD use lower-case prefix names 15:09:33 in order to be compatible with current and potential future 15:09:33 processors. 15:09:34
  • 15:09:49 Manu: I think we learned something important about xmlns in HTML5 yesterday 15:09:53 benadida: Is that the errata? 15:09:56 ShaneM: Yes 15:10:13 Manu: +1, that looks good. 15:10:13 +1 15:10:15 +1 15:10:17 +1 15:10:19 +1 15:10:46 RESOLVED: to publish the above errata on lowercase prefix names 15:11:31 benadida: Good that HTML5+RDFa went out 15:11:45 benadida: I think Sam thought we were trying to do something that we weren't with RDFa IG. 15:11:46 Errata is updated at http://www.w3.org/MarkUp/2008/REC-rdfa-syntax-20081014-errata/ 15:11:57 benadida: But it's nice that HTML5+RDFa IG is supported. 15:12:10 s/HTML5+RDFa/RDFa/ 15:12:28 Ralph: There were misunderstandings on both sides. 15:13:16 benadida: Still concerned that HTML WG and WHAT WG are seen as two separate entities. 15:14:26 Topic: Action Items 15:14:50 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:14:53 -- CONTINUES 15:15:18 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:15:20 -- CONTINUES 15:15:34 ACTION: Mark create base wizard suitable for cloning [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action12] 15:15:36 -- CONTINUES 15:16:41 ACTION: Mark write foaf examples for wiki [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action13] 15:16:45 -- DROP 15:16:55 markbirbeck: We should create a wishlist on the rdfa.info/wiki site 15:17:01 benadida: Yes, sounds good. 15:18:32 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:18:57 Ralph: There can only be one tracker instance per WG 15:19:01 benadida: Technical constraint? 15:19:20 Ralph: If we move forward with RDFa IG, there will be a tracker instance there. 15:19:36 Ralph: We can share SWD tracker for now and move data over. 15:19:41 -- CONTINUES 15:19:50 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:19:53 -- DROP 15:20:05 -> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Jul/0104.html last week's minutes 15:20:08 NOTE: The action items desperately need to be cleaned up. 15:20:22 Topic: Token @proposal 15:20:53 benadida: I think we agree that the main goal of the @token proposal is to make RDFa markup simpler and more Microformats-like. 15:21:11 markbirbeck: That makes it sound like it makes it more for the beginner author... 15:21:22 ShaneM: Dynamically extending collection of reserved words is also important. 15:21:39 benadida: So you can use unprefixed values easily? 15:22:13 benadida: What you said Shane, would rule out things like rel=":name", with @token we'd be able to do rel="name" 15:22:14 property=":name" 15:22:33 benadida: That wouldn't quite fit your use case... right? 15:22:37 http://webbackplane.com/mark-birbeck/blog/2009/04/30/tokenising-the-semantic-web 15:22:50 markbirbeck: If you do rel="name:" we already have that facility. 15:23:16 benadida: Just trying to clarify the problem we're trying to solve. 15:23:34 markbirbeck: We can already dynamically assign the prefix tokens... 15:24:16 benadida: If we got the route of "as simple as Microformats", ":name" doesn't necessarily work. 15:24:37 benadida: at least it may not be as simple as we want it. 15:24:56 benadida: Currently, rel="name" isn't supported and could be via a minor tweak. 15:25:07 benadida: Any other points? 15:25:22 benadida: Here's my concern with the @token proposal. 15:25:33 benadida: It's basically saying that there are some tokens you can find at URL X. 15:25:46 benadida: By saying something like this: 15:25:47
    15:25:48
    15:26:08 benadida: Everything within that DIV have rules that expand tokens. 15:26:17 markbirbeck: @token is merely a new proposed name for xmlns: 15:26:24 markbirbeck: It's exactly the same as @prefix before. 15:26:37 benadida: The bit you're talking about is the @profile attribute. 15:26:47 markbirbeck: I'm not the only one proposing that @profile should be used. 15:27:14 markbirbeck: The concensus seems to be that @profile is the way to get external documents. 15:27:28 benadida: How can I say name is foaf:name? 15:27:38 xmlns:Agent="http://purl.org/dc/terms/Agent" 15:27:38 xmlns:Person="http://xmlns.com/foaf/0.1/Person" 15:27:39 xmlns:title="http://xmlns.com/foaf/0.1/title" 15:27:39 xmlns:fn="http://xmlns.com/foaf/0.1/name" 15:27:41 > 15:27:43
    about="http://www.ivan-herman.net/me" 15:27:47 typeof="Person Agent" 15:27:49 > 15:27:51

    15:27:53 Dr 15:27:55 Ivan Herman 15:27:57

    15:27:59
    15:28:01 15:28:16 markbirbeck: That's how you get the Microformats-like markup. 15:28:38 markbirbeck: You can achieve that with @token by making the same mappings. 15:28:58 markbirbeck: Instead of requiring typeof="Person:", you can do typeof="Person" 15:29:06 markbirbeck: That's proposal 1 15:29:26 markbirbeck: Defining them external to the document is the RDFa Profiles discussion. 15:29:37 benadida: The worry I have is with proposal #2 15:29:47 benadida: The idea of pulling these in from a different URL... 15:30:08 benadida: Google with Rich Snippets could be the first customer of this feature - they're concerned about the number of prefix declarations. 15:30:21 markbirbeck: Yes, that's a concern. 15:30:27 benadida: Then let's use them as an example. 15:31:17 benadida: If they were to use @profile - and we think of RDFa as you browsing across websites and collecting triples. 15:31:32 benadida: If the @profile is not available for any reason, you have to delay interpretation into triples until it's available. 15:31:46 benadida: You can't just use a plain RDF store... 15:31:56 benadida: You /could/ do it via vocabulary equivalencies. 15:32:08 benadida: You could say google:title is the same thing as dc:title... 15:32:26 benadida: Then maybe the only thing we need is the ability to redefine the base prefix. 15:32:27 prefix="http://rdf.datavocabulary.org/rdf#" 15:32:54 s/datavocabulary/data-vocabulary/ 15:32:59 I think... 15:33:02 benadida: The matching of terms could be done via an RDF vocabulary 15:33:45 benadida: only when it's an unreserved term does it use the default prefix. 15:34:01 benadida: Is my concern clear? 15:34:20 markbirbeck: Yes, but in terms of the definition of @profile, the concern isn't as great as you might think. 15:34:32 markbirbeck: As with schemas, you're allowed to not dereference the document. 15:34:50 markbirbeck: an RDFa parser would be entitled to know the prefix mappings by derefercing the URI 15:35:08 markbirbeck: It's not that you don't dereference, it's that things won't break as often as you think. 15:35:21 markbirbeck: We could argue that we should /never/ dereference. 15:35:33 ack Ralph 15:35:33 Ralph, you wanted to support Ben's concern and proposal 15:35:59 Ralph: This is a potential interaction that we haven't really discussed. 15:36:06 Ralph: We don't depend on @profile now. 15:36:36 Ralph: Up to this point, without derefercing namespace URIs we can't construct the named graph without dereferencing. 15:36:54 Ralph: The ability to parse the document and get the triples out of it is important. 15:37:15 Ralph: If we find a mechanism that allows us to minimize the prefix bindings to just one, we can always parse the document. 15:37:32 Ralph: We may not be able to dereference the URI, but we can at least put the triple into our graph. 15:37:51 benadida: Yes, that's a better way to say it. I think we can cache these things. 15:38:20 benadida: Don't know if /requiring/ another layer of indirection is a good thing. 15:38:33 markbirbeck: If you know what a URI means, you don't have to dereference it. 15:39:30 Ralph: Sure, but we're creating a mechanism that allows us to encounter completely unknown @profile URIs... 15:40:17 Ralph: If we create a mechanism where we don't know how to expand the "Person" token without dereferncing another URI. 15:40:27 Ralph: Today, we can always expand the URI and put it in the triple store. 15:40:45 markbirbeck: Sure, let's put that to one side... I don't think we get all of the features that we want from what Ben is suggesting. 15:40:59 markbirbeck: One of the big things is the number of namespaces. Ben's proposal gives us 1. 15:41:28 markbirbeck: We're resurrecting the [default prefix mapping] 15:41:52 markbirbeck: The thing that keeps coming up with SearchMonkey is that they have a ton of namespaces up top. 15:42:10 markbirbeck: We created "vocabularies" that are built from other vocabularies. 15:42:17 markbirbeck: We end up with quite a few namespaces. 15:42:28 markbirbeck: If we don't want to go @profile, then that's fine. 15:43:09 markbirbeck: Let's stop thinking about explicit vocabularies, and more about mixing vocabularies. 15:43:28 markbirbeck: You need a more subtle and flexible vocabulary term declaration mechanism. 15:44:03 Ralph: By taking a bunch of terms I want to use from different vocabularies, I can give them names in my "ralph" namespace. 15:44:18 Ralph: My "ralph" namespace has a URI - I can parse triples out of them. 15:45:23 let's call that a "hybrid vocabulary" 15:45:28 Ralph: The one dereference of the Ralph namespace gives me the meaning of all of the names (mapping to dublin core, foaf, etc.) 15:45:50 Ralph: Dublin Core had this sort of approach in the past. 15:46:02 Ralph: It's a question of how the indirection happens... 15:46:09 Ralph: Where does the indirection go? 15:46:32 Ralph: In your proposal, you must dereference @profile. 15:46:37 markbirbeck: No, it doesn't. 15:46:53 Ralph: minutes are wrong... 15:47:05 Ralph: My understanding of the @token proposal is that you have to dereference. 15:47:20 markbirbeck: That doesn't have anything to do with the @token proposal. 15:47:31 ShaneM: It has to do with the @profile proposal. 15:48:10 [I stand (sit) corrected. Sorry for misunderstanding] 15:48:15 benadida: Dereferencing for @profile proposal is happening at the parser level. 15:48:57 benadida: It's not an issue of how many dereferencings are happening, it's at what level does it happen? 15:49:04 benadida: It's not a syntax issue, it's a vocabulary issue. 15:49:14 benadida: Maybe it should sit at the vocabulary layer of the stack. 15:49:25 markbirbeck: I'm confused about this... 15:49:43 markbirbeck: Proposal 1 is simply saying, instead of doing "Agent:", we allow "Agent" 15:49:54 [indeed, my concern is about _requiring_ URIs in @profile to be dereferenced before a string such as "Agent" can be expanded to a full URI] 15:50:31 markbirbeck: We haven't said anything about @profile in the @token proposal. 15:51:02 markbirbeck: You have more indirection and it's a bit more complicated. 15:51:13 benadida: Let's take a step back and look at the goal.. 15:51:14
    15:51:33 My name is Ben 15:51:34 ... 15:51:35
    15:52:02 benadida: We want that markup to be simple and non-prefixed. 15:52:07 benadida: We want that to be do-able in RDFa. 15:52:13 benadida: What is the enabler of that technology. 15:52:33 benadida: If you try to do it incrementally, you end up with the @token proposal. 15:52:40 benadida: maybe that mapping belongs at the vocabulary level. 15:53:04 markbirbeck: You're saying you can use owl:sameas at the vocabulary level. 15:53:19 markbirbeck: I'm saying that we can solve it at the CURIE level. 15:53:26 a:b a x:y . 15:53:51 ack Ralph 15:54:08 Ralph: I stand corrected with my earlier response. 15:54:20 Ralph: I could view @token syntax as a step beyond CURIEs. 15:54:50 Ralph: People are going to be frustrated with the list of items they have to use in their document. 15:55:06 Ralph: They're going to be annoyed by having to cut/paste entire chunks of @token attributes. 15:55:11 Ralph: @profile is a way to do that. 15:55:31 q+ to discuss profiles vs vocabs 15:55:32 Ralph: Now we're at the point of having an external document that provides a list of external mappings. 15:55:57 Ralph: When I look at the token proposal, I see a slippery progression to the point that we need something like @profile. 15:56:10 Ralph: I want to try to avoid that temptation. 15:56:12 ack Shane 15:56:12 ShaneM, you wanted to discuss profiles vs vocabs 15:56:29 ShaneM: Ben, owl:sameas ... 15:56:50 ShaneM: Hybrid vocabularies are fine, go ahead and do it, we already enable that (more or less). 15:57:14 benadida: No, we need to modify CURIE processing for that to happen. 15:57:31 ShaneM: Creating those external collections that you can use is an external issue 15:58:14 benadida: What do you think we're not focusing on enough. 15:58:31 ShaneM: We keep talking about the @token proposal, and others keep talking about external vocabularies. 15:58:59 Ralph: We can't look at either in isolation, we need to look at it from both ends. 15:59:08 Ralph: I don't think we can answer them in isolation. 15:59:20 markbirbeck: My prime goal is a Microformats look-alike. 15:59:38 markbirbeck: If we don't have an external document solution, then I'm not concerned with "Agent:" 15:59:39 remember that xmlms:shane="http://www.aptest.com/IDs/shane" works today 16:00:51 We had a straw horse proposal for external definitions at http://www.rdfa.info/wiki/RDFa_Profiles 16:00:51 markbirbeck: I'm not concerned with @token in-so-much as I'm concerned with Microformats simplicity. 16:01:03 benadida: We should try and simulate that the right way. 16:02:01 Manu: I think we need to be able to support external vocabularies 16:02:21 ... I don't yet understand Mark's proposal to see how to combine audio & media vocabularies with microformat vocabularies 16:02:27 ... this is a use case we have right now 16:02:44 ... I'll explain in email 16:02:51 s/Mark's/Ben's/ 16:04:01 ... if Ben's proposal is to allow a CURIE without a ':', I don't see how to do this in a way that works like Mark's proposal 16:04:49 ... it falls back to the vocabulary layer so the RDFa processing rules and parser don't need to say much 16:05:12 ... but it creates a big burden on users to create these 'bundled' vocabularies 16:05:32 Ben: we have a technology to map vocabulary terms and it worries me to create more layers of mapping 16:06:41 Mark: my model is to have tokens that map to [full] URIs 16:07:17 ... vocabulary mapping with owl:sameAs has been observed to require a higher level of RDF processor 16:09:45 Manu: this inferencing mechanism may not belong in the RDFa specification 16:10:11 ... where would we advise document authors of how owl:sameAs works? Best practices? 16:10:29 Ben: I'm suggesting we leverage more of the existing RDF mechanism 16:10:36 ... yes, it's present at a different layer 16:11:08 Mark: I'm only talking about an additional mechanism for abbreviating URIs 16:11:33 ... owl:sameAs is a very different kind of mechanism 16:12:03 ... it requires a higher level of [semantic] processing 16:12:08 s/I don't yet understand Mark's proposal/I don't yet understand Ben's proposal/ 16:13:02 Ralph: We can't process triples if we can't dereference in Mark's @profile proposal 16:13:11 Ralph: It's not clear-cut how we externalize token mappings. 16:13:22 ShaneM: Yes, but those are two separate issues. 16:13:42 ShaneM: They're orthogonal issues. 16:14:04 Ralph: They come from an objective that Mark's proposing - making the syntax look as close to Microformats as we can. 16:14:22 ShaneM: I don't think it's a lookup step. 16:14:40 markbirbeck: I think that Mark's understanding of expanding the definition of CURIEs is correct. 16:14:48 benadida: I don't think that's the issue 16:14:58 benadida: It doesn't include the definition of @profile. 16:15:16 benadida: Don't have an issue with augmenting the way CURIEs are parsed. 16:15:38 rel="foobar" 16:15:45 prefix="http://example.org/#" 16:16:21 benadida: Clearly and edge case we'd need to hash out. 16:17:53 benadida: My proposal is only intended to highlight this particular architectural issue. 16:19:05 q+ 16:19:17 ack steven 16:19:47 Steven: On vacation for 3 weeks. 16:20:03 +1 :) 16:20:10 ;-) 16:22:10 -markbirbeck 16:22:12 -ShaneM 16:22:12 -Ben_Adida 16:22:14 -Steven 16:22:23 -Ralph 16:23:10 ShaneM has left #rdfa 16:27:24 disconnecting the lone participant, msporny, in SW_SWD(RDFa)11:00AM 16:27:38 rrsagent, draft minutes 16:27:38 I have made the request to generate http://www.w3.org/2009/07/16-rdfa-minutes.html msporny 16:27:59 Regrets+ Michael_Hausenblas 16:40:58 rrsagent, draft minutes 16:40:58 I have made the request to generate http://www.w3.org/2009/07/16-rdfa-minutes.html msporny 17:00:06 Present+ Manu_Sporny 17:00:09 rrsagent, draft minutes 17:00:09 I have made the request to generate http://www.w3.org/2009/07/16-rdfa-minutes.html msporny 17:03:12 RESOLVED: to publish the above errata on lowercase prefix names 17:03:15 rrsagent, draft minutes 17:03:15 I have made the request to generate http://www.w3.org/2009/07/16-rdfa-minutes.html msporny 17:46:12 SW_SWD(RDFa)11:00AM has ended 17:46:14 Attendees were Ralph, Ben_Adida, Steven, markbirbeck, msporny, ShaneM 17:51:44 zakim, bye 17:51:44 Zakim has left #rdfa 17:51:48 rrsagent, byte 17:51:48 I'm logging. I don't understand 'byte', msporny. Try /msg RRSAgent help 17:51:51 rrsagent, bye 17:51:51 I see 6 open action items saved in http://www.w3.org/2009/07/16-rdfa-actions.rdf : 17:51:51 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] 17:51:51 recorded in http://www.w3.org/2009/07/16-rdfa-irc#T15-14-50 17:51:51 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] 17:51:51 recorded in http://www.w3.org/2009/07/16-rdfa-irc#T15-15-18 17:51:51 ACTION: Mark create base wizard suitable for cloning [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action12] [3] 17:51:51 recorded in http://www.w3.org/2009/07/16-rdfa-irc#T15-15-34 17:51:51 ACTION: Mark write foaf examples for wiki [recorded in http://www.w3.org/2008/09/11-rdfa-minutes.html#action13] [4] 17:51:51 recorded in http://www.w3.org/2009/07/16-rdfa-irc#T15-16-41 17:51:51 ACTION: Ralph make a request for an RDFa issue tracker instance [recorded in http://www.w3.org/2009/05/28-rdfa-minutes.html#action11] [5] 17:51:51 recorded in http://www.w3.org/2009/07/16-rdfa-irc#T15-18-32 17:51:51 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] [6] 17:51:51 recorded in http://www.w3.org/2009/07/16-rdfa-irc#T15-19-50