W3C home > Mailing lists > Public > public-swd-wg@w3.org > July 2007

Re: [RDFa] ISSUE-34: partial resolution to @href everywhere

From: Ivan Herman <ivan@w3.org>
Date: Sat, 14 Jul 2007 10:03:03 +0200
Message-ID: <46988337.7030403@w3.org>
To: Ben Adida <ben@adida.net>
CC: RDFa <public-rdf-in-xhtml-tf@w3.org>, SWD WG <public-swd-wg@w3.org>
I am on record not being really favourable of the href everywhere, but
as the WG has decided to do it, I am in favour of Ben's proposal
(@resource overriding @href).


Ben Adida wrote:
> Hi all,
> Today, we agreed that we would support @href *and* @resource everywhere,
> with the following note:
> - @href may become navigable/clickable in a future version of XHTML
> - we encourage X/HTML WGs to *not* make @resource clickable/navigable.
> - from an RDFa standpoint, they both determine the object of a triple
> (or the subject under a @rev).
> The question, then, is what to do when *both* @resource and @href
> appear.
> I have a proposal, which I think makes sense and provides solid
> justification for having both attributes: @resource overrides @href just
> like @content overrides the content of an element.
> Effectively, this joins up with Mark's reasoning that @resource is used
> when the navigable link is not really the semantic link. If there is a
> clickable and semantic link, use @href. If there is only a semantic
> link, use @resource. If there's both but they're not the same, use both
> attributes accordingly.
> Thoughts?
> -Ben


Ivan Herman, W3C Semantic Web Activity Lead
URL: http://www.w3.org/People/Ivan/
PGP Key: http://www.cwi.nl/%7Eivan/AboutMe/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf

Received on Saturday, 14 July 2007 08:03:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:31:44 UTC