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

Re: Help with test case 105 and 106

From: Ben Adida <ben@adida.net>
Date: Tue, 02 Sep 2008 17:51:59 -0700
Message-ID: <48BDDFAF.7050108@adida.net>
To: Micah Dubinko <Micah.Dubinko@marklogic.com>
CC: RDFa <public-rdf-in-xhtml-tf@w3.org>

Micah Dubinko wrote:
>> This should begin to point out why, once you have
>>
>>    <> dc:creator _:blanknode
>>
>> there's really nothing you can do with that inner @href anymore.
> 
> There's no test for this, but would the same apply to @property? As in:
>   <div about="" rel="dc:creator">
>      <a property="foobar" href="ben.html">Ben</a> created this page.
>   </div>
> 
> What should come out of that? Still a blank dc:creator node?

Good question, and it took me a bit of time to remember the reasoning
here (Mark helped, as he often does with these more advanced cases.)

The idea is that the structure of the blank nodes is only decided by
@rel and @rev. So in fact, @property does *not* do the same thing. @href
completes the hanging @rel, and @property applies to @href.

You might want to rewrite it this way to make it clearer:

   <div about="" rel="dc:creator">
      <a href="ben.html" property="foobar">Ben</a> created this page.
   </div>

And you get:

  <> dc:creator <ben.html> .
  <ben.html> foobar "Ben" .

And you can see from this example why this is more useful than having
@property prevent the @rel completion.

-Ben
Received on Wednesday, 3 September 2008 00:52:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 September 2008 00:52:37 GMT