Re: [RDFa] A summary of @rel everywhere

Hi Ben,

I have some comments on this, but I need to resolve one thing first;
where is this coming from:

> - all contained statements default to having as subject the object of
> the @rel triple, whether it is a bnode, a URI indicated by @id, or the
> URI of the @href if there is one.

and:

> 3) (assuming @href can go anywhere)
>
> <div about="#foo" rel="foaf:topic" href="#event_0" class="cal:Vevent">
>   <span property="cal:dtstart">2007-07-07</span>
> </div>
>
> yields
>
> <#foo> foaf:topic <#event_0> .
>
> <#event_0> rdf:type cal:Vevent ;
>   cal:dtstart "2007-07-07" .

I don't recall us ever making @href the *subject* of any contained
triples. That's how things used to be in the earliest, earliest drafts
(something I called "chaining") but it just didn't work. :)

This means--at least in my view of where we are currently--the
following triples would be generated from your example:

  <#foo>
    rdf:type cal:Vevent;
    foaf:topic <#event_0>;
    cal:dtstart "2007-07-07" .

Since we've agreed that if @rel is on its own (with no @href) then the
subject of any contained statements is the object of that
statement--i.e., a bnode. So the following mark-up _would_ give the
triples desired above:

  <div about="#foo" rel="foaf:topic">
    <div class="cal:Vevent">
      <span property="cal:dtstart">2007-07-07</span>
    </div>
  </div>

This is obviously pretty important, so if you have any references to
where the behaviour of @href was changed to become the subject of
contained statements I'd appreciate the links. Thanks.

Regards,

Mark

-- 
  Mark Birbeck, formsPlayer

  mark.birbeck@x-port.net | +44 (0) 20 7689 9232
  http://www.formsPlayer.com | http://internet-apps.blogspot.com

  standards. innovation.

Received on Tuesday, 10 July 2007 11:43:17 UTC