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

Re: Comments on RDFa in XHTML Syntax draft

From: Ben Adida <ben@adida.net>
Date: Mon, 24 Mar 2008 16:23:22 -0700
Message-ID: <47E837EA.4090306@adida.net>
To: Laurens Holst <lholst@students.cs.uu.nl>
CC: Mark Birbeck <mark.birbeck@x-port.net>, public-rdf-in-xhtml-tf@w3.org


Laurens,

Thanks for your feedback on these issues, it's much appreciated.

> I understand. Is there any particular reason then that @href isn’t 
> treated in the same way? It seems to me it has the same benefits there.

Typically, an element with @href can have child elements, so that allows 
authors to attach additional triples:

   <a rel="dc:creator" href="http://ben.adida.net/#me">
     <span property="foaf:name">Ben</span>
   </a>

leads to

   <> dc:creator <http://ben.adida.net/#me> .

   <http://ben.adida.net/#me> foaf:name "Ben" .

Also, if you use @href without @about, then it can complete triples 
"from above":

   <div rel="foaf:knows">
     <a href="http://example.com/markbirbeck">Mark</a>,
     <a href="http://example.com/ivanherman">Ivan</a>
   </div>

leads to:

   <> foaf:knows <http://example.com/markbirbeck>
   <> foaf:knows <http://example.com/ivanherman>

So I think the important use cases are fulfilled here. If we allowed 
@rel to "slip in between" @href and @resource, that would get quite 
complicated (and it would prevent @resource from overriding @href in 
many cases.)

-Ben
Received on Monday, 24 March 2008 23:23:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:01:56 UTC