Re: finding closure on the issues

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:

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jan/0095


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" />
</div>
=======
<#me> foaf:img <ben.jpg> .


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

<div about="#me" rel="foaf:img">
  <img src="ben.jpg" instanceof="foaf:Image" />
</div>
========
<#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.

-Ben

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