Re: RDFa and Microformats

On 15 Sep 2008, at 13:59, Mark Birbeck wrote:

>>        <span content="v1"
>>        property="p1 p2">v2</span>
>>
>> How does the RDFa parser know that @content was added for p1 and  
>> not p2?
>> Answer: it doesn't; it can't;
>
> In the sense that it cannot know the 'intent', then of course you  
> are right.
>
> But the outcome of the mark-up is clearly defined in the RDFa
> processing rules, and you will get this:
>
>   <> p1 "v1" .
>   <> p2 "v1" .

And with:

	<span class="p1" content="v1"
	property="p2">v2</span>

the outcome of the mark-up is also clearly defined by RDFa processing  
rules:

	<> p2 "v1" .

So where's the problem?

> Also, as you said yourself earlier, the resource that the properties
> are being attached to is different in RDFa than it is in Microformats:
>
>   <div class="hcard">
>     <span property="foaf:name" class="fn"
>      content="Toby Inkster">Toby</span>
>   </div>

Here the problem is caused by the property attribute, not the content  
attribute. The RDFa triples created by the above markup are:

	<> foaf:name "Toby Inkster" .

Which is clearly not what was intended. However, removing @property,  
or adding @about/@typeof to the <div> fix things.

I'm not suggesting muddying the RDFa processing rules - merely  
stating that it should be safe for microformats parsers to make use  
of @content on elements which do not have @property; and to make use  
of @content on elements which *do* have @property, as long as it is  
used consistently with the RDFa processing model.

-- 
Toby A Inkster
<mailto:mail@tobyinkster.co.uk>
<http://tobyinkster.co.uk>

Received on Monday, 15 September 2008 13:47:45 UTC