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

Re: Rethinking @src in the context of chaining rules

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Thu, 20 Dec 2007 10:20:26 -0500
Message-ID: <476A883A.8040006@digitalbazaar.com>
To: RDFa <public-rdf-in-xhtml-tf@w3.org>

Ben Adida wrote:
> PROPOSAL: @src defines a subject, not an object. @about overrides @src
> in the same way that @resource overrides @href.

An alternative would be to remove @src from generating anything.

Mark's most recent e-mail confused me a bit.

My understanding was that, at the moment, @instanceof only applies to
@about. Ben's proposal would make it such that @instanceof applied to
@about and to @src.

Mark's last e-mail made is seem like @instanceof applies to whatever the
current subject is... which goes against test #53, which we are
reviewing today, and the discussion we had last week.

If we remove @src, we are left with one way of specifying the subject on
the current element - @about. This means that we would repeat ourselves
when doing anything with images:

<img about="me.jpg" src="me.jpg" instanceof="foaf:Image" />

Do we care that we have to repeat ourselves for IMG? It seems as if
we're going to great lengths to support @src, which is complicating the
parser rules a bit (not really that much, but, it seems to be of concern).

I can't imagine that removing @src from generating anything will be a
popular decision. It does, however, a) simplify the parsing rules and b)
doesn't prevent us from generating the triples that we were generating
before.

-- manu

-- 
Manu Sporny
President/CEO - Digital Bazaar, Inc.
blog: Over One Million Songs Available on Bitmunk
http://blog.digitalbazaar.com/2007/10/29/one-million-songs-on-bitmunk/
Received on Thursday, 20 December 2007 15:20:44 GMT

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