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

Re: finding closure on the issues

From: Ben Adida <ben@adida.net>
Date: Mon, 21 Jan 2008 10:25:07 -0800
Message-ID: <4794E383.3050701@adida.net>
To: Dan Brickley <danbri@danbri.org>
CC: RDFa <public-rdf-in-xhtml-tf@w3.org>

Dan Brickley wrote:
> Do you have a pointer to a brief summary of each? (test cases would be
> sweet too :)

Manu did a good job here on @href/@resource completing @rel:


On the @src issue, here's a summary independently of the first issue:

OPTION (a): @src is equivalent to @href/@resource and is overridden by
them (what we had until 3-4 weeks ago):

<div about="#me">
  <img rel="foaf:img" src="ben.jpg" />
<#me> foaf:img <ben.jpg> .

OPTION (b): @src is equivalent to @about and can thus be used with

<div about="#me" rel="foaf:img">
  <img src="ben.jpg" instanceof="foaf:Image" />
<#me> foaf:img <ben.jpg> .
<ben.jpg> a foaf:Image .

The issue with (a) is that you can't declare a type on an image and that
@src/@href/@resource are all the object, which gets a bit odd. Also,
@src and @href are both HTML attributes that imply inline-inclusion and
linkability, and I'm not sure one should override the other.

The issue with (b) is that the nice markup of @rel and @src on an IMG
tag goes away. The other issue is that any image inside a hanging @rel
completes it.

Received on Monday, 21 January 2008 18:25:23 UTC

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