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

ISSUE: @href anywhere

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Wed, 23 May 2007 20:32:06 +0100
Message-ID: <640dd5060705231232k2538a90dle43fe1cdc57bcd8c@mail.gmail.com>
To: RDFa <public-rdf-in-xhtml-tf@w3.org>

Hello all,

Since we need to resolve this, and because no-one has threatened to
kill anyone on this list for quite a while :), I thought it worth
kicking off the discussion about '@href anywhere'.

Before we start, can I ask that we keep separate two aspects of this
discussion--the requirement and (if people agree on the requirement)
its implementation. In my view '@href everywhere' is only a means to
an end, and the question is not primarily about whether we confuse
authors if we leave it in, but what functionality do we lose if we
take it out. So, I would suggest that if we can agree on what that the
purpose of '@href everywhere' is, we can then look at whether we can
provide that same functionality in some other way...and if we can, the
problem just disappears! :)

I've made separate entries on this, so that the discussion can be
managed, and hopefully we retain focus. In my view, the functionality
that we want from '@href everywhere' is the ability to express express
objects that are resources, but not necessarily navigable links. I've
introduced that idea here:


One way we might solve this would be to re-introduce the old @resource
attribute. I've started a thread for discussing that approach here:




  Mark Birbeck, formsPlayer

  mark.birbeck@x-port.net | +44 (0) 20 7689 9232
  http://www.formsPlayer.com | http://internet-apps.blogspot.com

  standards. innovation.
Received on Wednesday, 23 May 2007 19:32:16 UTC

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