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

Re: [RDFa] ISSUE-42: @src, following up, proposal to resolve

From: Ivan Herman <ivan@w3.org>
Date: Tue, 10 Jul 2007 12:25:53 +0200
Message-ID: <46935EB1.8080408@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 agree (module the choice of the class attribute, of course).

The way I would describe it (and as you wrote in one of your mail): @src
behaves exactly like @href on and <a> element.

Ivan

Ben Adida wrote:
> 
> Mark recently led a discussion of the @src attribute, specifically @src
> on IMG. Here's how Mark summarized it:
> 
> ==========
> So to recap where this issue is at, so that those who haven't voted
> yet can state their preference, the sentiment is that the attributes
> with triple-generating potential on <img> are:
> 
>   <img about="s" rel="p" src="o" class="t">
> 
> and that 'type' applies to the object, 'o', rather than to the subject 's'.
> 
> As pointed out by Ben, in the sense that we have an element that
> contains an object that is also a subject, then this construct echoes
> striping. There may be scope for linking the two concepts in our
> documentation, or at the very least--which may be what Ben is
> saying--scope for showing that this isn't such a unique construct.
> 
> As for other attributes, such as @alt and @longdesc, we may or may not
> revisit those in the future, when we've learned a bit more about real
> life use-cases.
> ===========
> 
> 
> I propose that we resolve ISSUE-42 exactly as above for XHTML1.1+RDFa.
> 
> We'll discuss on Thursday if there are issues with the above conclusion!
> 
> -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 Tuesday, 10 July 2007 10:25:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:15:08 GMT