Re: ISSUE: @href anywhere

1- I fully agree with the validity of the requirement in[1]

2- Using @resource as proposed in[2] seems to solve the problem of[1]
cleanly and without any further clashes.

I think the argument put forward in[2] for accepting @href on any
element, too, is solely due to a forward expectation on what XHTML2 will
do. However, as far as I know, there is no firm decision on that in
XHTML2, let alone the fact it still in a Working Draft stage, meaning
that we really do not know how this will evolve. Who knows? Maybe the
XHTML group will drop this feature in a future release!

Consequently, I would rather opt for using @resource only for the time
being. If and when XHTML2 becomes a Rec (or Last Call, or Candidate Rec,
I am not sure), we can think of a revised version of RDFa *adapted to
XHTML2*. After all, XHTML2 can and will introduce other features that
make sense in RDFa sense (<link> and <meta> everywhere!), so such
extensions may become necessary in other areas of RDFa, too. Our goal at
the moment is XHTML1.1/HTML5 after all.

A related, technical question: can I use *both* @resource and @href on,
say, and <a>? Similarly, can I use *both* @resource and @src on and
'img'? My proposal is 'yes' and @resource has a higher 'priority', so to
say, in terms of RDFa.

Ivan


[1]
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007May/0018.html
[2]
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007May/0020.html

Mark Birbeck wrote:
> 
> 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:
> 
>  <http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007May/0018.html>
> 
> 
> 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:
> 
>  <http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007May/0020.html>
> 
> 
> Regards,
> 
> Mark
> 

-- 

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