- From: Mark Birbeck <mark.birbeck@formsPlayer.com>
- Date: Wed, 9 Jan 2008 10:24:41 +0000
- To: "Ben Adida" <ben@adida.net>
- Cc: "Manu Sporny" <msporny@digitalbazaar.com>, RDFa <public-rdf-in-xhtml-tf@w3.org>
Hi Ben, On 08/01/2008, Ben Adida <ben@adida.net> wrote: > > Manu Sporny wrote: > > Hi Mark, > > > > Just to understand when certain triples are generated, it is my > > understanding that all of the examples below should not generate any > > triples, please verify: > > > > ----------------------------------------------------------------- > > <div resource="#me" rel="foaf:knows"> > > <span resource="#ben"> > > </div> > > ----------------------------------------------------------------- > > No, that first div would generate > > <> foaf:knows <#me> . > > I suspect Mark agrees with me that that's the only triple generated > here... Yes. > ...but that example further shows the possible confusion when > @resource can complete a previous triple, though. Sure...but you could say that not having it complete a triple is also confusing, since it's inconsistent. :) So, let's move on... > > ----------------------------------------------------------------- > > <div href="#me" rel="foaf:knows"> > > <span href="#ben"> > > </div> > > ----------------------------------------------------------------- > > Same, that first div would generate the same triple, but yes, the inner > span would not, in my interpretation. Again, I suspect Mark agrees that > that's the only triple generated here, I believe his proposal is *only* > about @href/@resource completing *incomplete* triples. Well, it has two parts as I outlined in the closing remarks in my 'vote now' email. The first is that any attribute can set a subject (as demonstrated in the following examples), and secondly that all subjects should complete 'incomplete triples'. Thanks to Manu's work, I think we have reduced the disagreement to just this latter case. > > ----------------------------------------------------------------- > > <div href="#me"> > > <span rel="foaf:knows" href="#ben"> > > </div> > > ----------------------------------------------------------------- > > Well, actually, why wouldn't that generate a triple? We've always said > that an object like @href would cause chaining, so in this case, I would > not be opposed to seeing this generate: > > <#me> foaf:knows <#ben>. > > Just like when we have: > > <a href="foo.html"> > <span property="dc:title">Foo</span> > </a> > > we're really describing the target of the @href. Great! I therefore withdraw my "vote now" email. :) Basically I said that there was no point in separating the two issues, but if everyone is happy with this construct, we can focus on the 'incomplete triple' part. > > ----------------------------------------------------------------- > > <div resource="#me" rel="foaf:knows"> > > <div resource="#ben"> > > <a rel="foaf:knows" href="#mark">Mark</a> > > </div> > > </div> > > ----------------------------------------------------------------- > > Again, the first div would yield: > > <> foaf:knows <#me> . > > And again, I would not be opposed to seeing a @resource on its own still > trigger chaining, just like an @about on its own still completes a > hanging @rel, so I could certainly see: > > <#ben> foaf:knows <#mark> . > > I *think* on this one, Mark would agree with me. 110%! Hurray! :) Regards, Mark -- Mark Birbeck, formsPlayer mark.birbeck@formsPlayer.com | +44 (0) 20 7689 9232 http://www.formsPlayer.com | http://internet-apps.blogspot.com standards. innovation.
Received on Wednesday, 9 January 2008 10:24:48 UTC