Different treatment of @resource between RDFa 1.0 and 1.1

• From: Alan Jeffrey <ajeffrey@bell-labs.com>
• Date: Fri, 20 Apr 2012 12:00:23 -0500
• To: <public-rdfa@w3.org>
• Message-ID: <4F919627.7040602@bell-labs.com>

Hi everyone,

In our RDFa-annotated XML we have been using just the @resource, @rel 
and @href attributes for expressing hyperlinks, for example in RDFa 1.0:

   <foo xmlns:ex="http://example.com/ns#"
    resource="http://example.com/foo">
      <link rel="ex:bar" href="http://example.com/baz"/>
   </foo>

which generates the expected RDF from the 1.0 distiller:

   <rdf:RDF><rdf:Description rdf:about="http://example.com/foo">
     <ex:bar rdf:resource="http://example.com/baz"/>
   </rdf:Description></rdf:RDF>

but the 1.1 distiller generates different output (the @about value has 
changed):

   <rdf:RDF><rdf:Description rdf:about="">
     <ex:bar rdf:resource="http://example.com/baz"/>
   </rdf:Description></rdf:RDF>

Digging through the 1.1 spec (Sec 7.5, processing rule 5) it looks like 
the distiller is doing the right thing: the @resource attribute only 
sets the current object resource when there's an @rel, @rev or @property 
attribute.

Is this a deliberate non-backward-compatible change? Why doesn't 
@resource always set the current object resource?

Cheers,

Alan Jeffrey.

Received on Friday, 20 April 2012 17:01:10 UTC