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

ISSUE-120: Ambiguous Situation with nested @rel where inner @rel is neither CURIE nor link type

From: SWD Issue Tracker <dean+cgi@w3.org>
Date: Fri, 9 May 2008 00:38:40 +0000 (UTC)
To: public-swd-wg@w3.org,public-rdf-in-xhtml-tf@w3.org
Message-Id: <20080509003840.70408153720@plopper.w3.org>


ISSUE-120: Ambiguous Situation with nested @rel where inner @rel is neither CURIE nor link type

http://www.w3.org/2006/07/SWD/track/issues/120

Raised by: Ben Adida
On product: RDFa

As per Ben's email [1]

"""
Here's the markup that we believe is ambiguous:

<div about="" rel="dc:creator">
    <img rel="myfoobarrel" href="ben.jpg" />
</div>

The question here is: does <ben.jpg> complete dc:creator, because 
myfoobarrel is neither a CURIE nor a link type? In other words, do we 
get the following triple:

   <> dc:creator <ben.jpg> .

?

My interpretation of the spec is that rel="myfoobarrel" is completely 
ignored, meaning that the triple completion behaves as if there was no 
@rel on the img, which means that <ben.jpg> indeed completes dc:creator. 
And I think that's a bad outcome.

Instead, I think the *presence* of @rel, no matter what it contains, 
should cause completion of the incomplete triples. Then, once the 
triples are completed, the *contents* of the @rel are considered for new 
triple creation.

Consider what would happen if you had a different @rel:

<div about="" rel="dc:creator">
    <img rel="foaf:img" href="ben.jpg" />
</div>

which would then yield:

   <> dc:creator _:bnode1 .
   _:bnode1 foaf:img <ben.jpg> .

Changing the @rel value on img should certainly kill the second triple, 
but I don't see why it should change the first triple at all.

"""


[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008May/0045.html
Received on Friday, 9 May 2008 00:39:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 9 May 2008 00:39:19 GMT