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

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

From: Ben Adida <ben@adida.net>
Date: Sat, 10 May 2008 12:23:32 -0700
Message-ID: <4825F634.9050903@adida.net>
To: Manu Sporny <msporny@digitalbazaar.com>
CC: public-rdf-in-xhtml-tf@w3.org

Manu Sporny wrote:
> However, I also see specifying:
> 
> rel=""
> 
> as very different from specifying
> 
> rel="foobarrel"

I would find it very confusing if those two cases would cause a triple 
"from above" to complete differently.

> In the first case, the author meant to stop chaining by specifying
> rel="". In the second case, the author did not mean to stop chaining by
> specifying rel="foobarrel".

Looking at the whole markup:

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

I don't think we can justify connecting dc:creator to <ben.jpg>, 
especially when a different *value* of @rel would break that connection.

There's not other situation where that happens in RDFa: triple structure 
is affected by the *presence* of attributes, never by their specific 
value. Sure, a triple might disappear if @rel goes from valid to invalid 
CURIE, but the *other* triples whose predicate are specified elsewhere 
are not affected.

-Ben
Received on Saturday, 10 May 2008 19:24:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 May 2008 19:24:07 GMT