- From: Mark Birbeck <mark.birbeck@formsPlayer.com>
- Date: Wed, 12 Sep 2007 12:16:51 +0100
- To: "Ivan Herman" <ivan@w3.org>
- Cc: public-rdf-in-xhtml-tf.w3.org <public-rdf-in-xhtml-tf@w3.org>, "Ben Adida" <ben@adida.net>
Hi Ivan,
Excellent...many thanks.
Two small things:
> It seems that Case 3 covers these edge cases, and works. My vote goes
> for that one. The only caveat is, somewhat philosophically, that the
> choice of the subject on the rdf:type triples is not necessarily the
> 'inherited' subject via the @about chain like for other things. Oh well,
> we can't get it all...
True. But in one of my emails I was trying to remind the group that
the origin of the use of class/role/instanceof was as a shorthand for:
<div>
<link rel="rdf:type" resource="[a:b]" />
</div>
We no longer support link and meta anywhere, but that is due to
browser limitations, and other versions of 'RDFa in x' could well
support it. The effect of link here is to create a bnode on the div,
and I think we should ensure that this does the same to keep things
consistent:
<div instanceof="a:b">
...
</div>
> <div about="#q">
> <span rel="rdf:type" resource="FULL URI FOR a:b"/>
> <span property="c:d">bla...
Note that you can do this:
<div about="#q">
<span rel="rdf:type" resource="[a:b]" />
<span property="c:d">bla...
@about and @resource support 'safe curie', whilst @href does not.
> It would be good if we could make a choice among those three, and then
> live with the consequences, so to say:-).
Sure. I'm going to try to word number 3 is simply as possible. I've
already done exactly the same as you did for your number 2 in my
parser, and it works fine, except of course for the situation where
there is no @about on the element. So it should be possible to add
this last condition quite simply.
Regards,
Mark
--
Mark Birbeck, formsPlayer
mark.birbeck@formsPlayer.com | +44 (0) 20 7689 9232
http://www.formsPlayer.com | http://internet-apps.blogspot.com
standards. innovation.
Received on Wednesday, 12 September 2007 11:17:11 UTC