W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > January 2008

Re: Do the following examples generate any triples?

From: Ben Adida <ben@adida.net>
Date: Tue, 08 Jan 2008 13:13:39 -0800
Message-ID: <4783E783.6080703@adida.net>
To: Manu Sporny <msporny@digitalbazaar.com>
CC: RDFa <public-rdf-in-xhtml-tf@w3.org>

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, but that example further shows the possible confusion when
@resource can complete a previous triple, though.

> -----------------------------------------------------------------
> <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.

> -----------------------------------------------------------------
> <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.

> -----------------------------------------------------------------
> <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.


-Ben
Received on Tuesday, 8 January 2008 21:13:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 21:13:46 GMT