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

an issue we need to address - bad @rel in the middle of a chain.

From: Ben Adida <ben@adida.net>
Date: Thu, 08 May 2008 17:36:21 -0700
Message-ID: <48239C85.2030107@adida.net>
To: RDFa <public-rdf-in-xhtml-tf@w3.org>

Hi all,

In a discussion today, Shane and I uncovered an edge case for which we 
have no test case. I think the spec says something about this edge case, 
and that the outcome is wrong. Shane thinks the spec is ambiguous. So, 
in either case, we need to clarify the situation.

Here's the markup that we believe is ambiguous:

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

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" />

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.



PS: adding this as an issue as soon as the email shows up in the archive.
Received on Friday, 9 May 2008 00:37:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:27 UTC