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

Re: Rethinking @src in the context of chaining rules

From: Ivan Herman <ivan@w3.org>
Date: Thu, 20 Dec 2007 09:34:24 +0100
Message-ID: <476A2910.609@w3.org>
To: Ben Adida <ben@adida.net>
CC: RDFa <public-rdf-in-xhtml-tf@w3.org>


Ben Adida wrote:
> 
> As per my action item from last week, here are some thoughts on @src
> given the new chaining rules.
> 
> PROPOSAL: @src defines a subject, not an object. @about overrides @src
> in the same way that @resource overrides @href.
> 
> Arguments:
> 
> 0) Given that an image is inline, it would be quite odd not to be able
> to declare an @instanceof on that image using simply:
> 
> <img src="foo.jpg" instanceof="foaf:Image" />
> 
> 1) Having three different ways to specify an object, @resource, @href,
> and @src is probably a sign of bad design.
> 
> 2) Declaring a foaf:img is trivial with the new chaining rules, even
> when @src is the subject:
> 
> <div about="#me" rel="foaf:img">
>  <img src="foo.jpg" instanceof="foaf:Image" />
> </div>
> 
> 3) Using @about to override @src allows for just the kinds of situations
> where the rendered does not quite match the semantic: e.g. you used a
> thumbnail picture but you want to declare a semantic relationship with
> the full-size image.
> 
> 4) Ivan is happy :)
> 

How could I say no to the proposal then?:-)

Seriously: I agree. It solves the issues we had. One problem less:-)

Ivan

> 
> Okay, I could come up with more, but I'll just say that, given the clean
> design of Mark's chaining rules, the @src-as-subject proposal just makes
> sense in my mind.
> 
> -Ben
> 

-- 

Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf


Received on Thursday, 20 December 2007 08:34:27 GMT

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