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

Re: Rethinking @src in the context of chaining rules

From: Niklas Lindström <lindstream@gmail.com>
Date: Tue, 8 Jan 2008 19:45:38 +0100
Message-ID: <cf8107640801081045m66e0fa58mfa1be51b1984de7c@mail.gmail.com>
To: "Ben Adida" <ben@adida.net>
Cc: "Manu Sporny" <msporny@digitalbazaar.com>, RDFa <public-rdf-in-xhtml-tf@w3.org>

Hi all!

I've been catching up on a lot, and this is indeed making my head
spin..  But that's good, these are important and complex issues.

For now, my mind is mostly (somewhat) clear on the issue of @src, issue #1.

I think the question is whether the page (or a "subsumed"/nested
subject) and @src have a reference relation or a composition relation.
Think of a web page (as we think of them today). It's not "complete"
without resources connected with @src  -- e.g. images, scripts and
other objects. But @href:s like links are "outward" relations. And
stylesheet links are also substitutable (@rel="alternate"), so they're
not parts of the composition, IMHO. (Granted, iframes are weird parts
in this view, but haven't they always been? ;) .. )

Also, I agree with the XHTML2 argument that this:

    <img src="me.jpg" rel="foaf:depicts" href="#me"/>

should yield:

    <me.jpg> foaf:depicts <#me> .

(Although it goes beyond XHTML 1.1, I think it is worth reflecting upon.)

Thus, I believe @src should behave as @about (same relation as @href
to @resource).

BTW: can someone point me to the motivating use cases and what current
consensus is regarding hanging rels? I've yet to spot this in the
tangle of threads in my mailbox.. :/

Best regards,
Received on Tuesday, 8 January 2008 18:45:45 UTC

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