Re: Does RDFa processing recurse into content:encoded?

Stephane Corlosquet wrote:
> Hi Richard,
>
> This is correct and was brought in a previous thread. In fact we've 
> added this content:encoded mapping knowingly. However, despite the 
> fact this is not part of the RDFa specs, some parsers could ignore 
> this restriction and try to parse the content of this rdf:XMLLiteral. 
> I don't think there is any problem with that? expect convincing RDFa 
> parsers developers :D
>
> Alternatively, in order to be in line with the specs, some extra 
> (hidden) RDFa markup could be generated outside the body element which 
> would reflect the content of the body. So Richard's example would become:
>
> <div class="body" property="content:encoded">
>  <p about="#me">
>    Hi, I'm <span property="foaf:name">Richard</span>!
>  </p>
> </div>
> <div class="hidden-rdfa">
> <span about="#me" property="foaf:name" content="Richard" />
> </div>
>
> This would involve RDFa parsing the content which ARC2 can do.
Don't understand the ARC2 specificity. Isn't RDFa parsing a feature of 
RDFa supporting user agents?

Please clarify what you mean. My assumption is that any RDFa aware user 
agent should be able to produce triples consistently from Drupal 
generated RDFa host/container resources.


Kingsley
>
> Steph.
>
> On Mon, Feb 8, 2010 at 2:29 PM, Richard Cyganiak 
> <richard.cyganiak@deri.org <mailto:richard.cyganiak@deri.org>> wrote:
>
>     Hi,
>
>     A question. What triples are generated from the following
>     HTML+RDFa snippet?
>
>     <div class="body" property="content:encoded">
>      <p about="#me">
>        Hi, I'm <span property="foaf:name">Richard</span>!
>      </p>
>     </div>
>
>     My reading of the spec is that it should create one triple, with
>     subject <>, property [content:encoded], and an rdf:XMLLiteral as
>     object.
>
>     My reading is that no foaf:name triple is generated, because RDFa
>     processing doesn't recurse into rdf:XMLLiterals.
>
>     Is this correct?
>
>     I'm asking because Drupal 7 puts a property="content:encoded" on
>     the body of any page, which is a reasonable thing to do, but
>     according to my understanding means that you cannot put RDFa
>     markup into the body of a Drupal 7 page (because RDFa processing
>     doesn't recurse into the body). If that's indeed the case, then
>     I'll probably have to raise this as an issue with the Drupal folks.
>
>     Thanks a lot,
>     Richard
>
>
>     -- 
>     Linked Data Technologist • Linked Data Research Centre
>     Digital Enterprise Research Institute (DERI), NUI Galway, Ireland
>     http://linkeddata.deri.ie/
>     skype:richard.cyganiak
>     tel:+353-91-49-5711
>
>
>


-- 

Regards,

Kingsley Idehen	      
President & CEO 
OpenLink Software     
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen

Received on Monday, 8 February 2010 20:28:32 UTC