- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 08 Feb 2010 18:00:39 -0500
- To: Stephane Corlosquet <scorlosquet@gmail.com>
- CC: Public RDFa <public-rdfa@w3.org>
Stephane Corlosquet wrote: > > > On Mon, Feb 8, 2010 at 3:28 PM, Kingsley Idehen > <kidehen@openlinksw.com <mailto:kidehen@openlinksw.com>> wrote: > > 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. > > > What I meant here is that when the page is rendered on the server > side, the content of the body is parsed by ARC2 and the triples > contained in the XMLLiteral are appended to the HTML+RDFa document. > This would allow RDFa parsers which do not recursively process the > XMLLiteral content to still get the RDFa expressed in it. This is just > an alternative to work around the fact that RDFa parsers don't support > this feature. Note that I just used ARC2 as an RDFa parser example but > this would work with any RDFa parser. To convert back to RDFa, there > are tools like [1]. > > Steph. > > [1] http://www.ebusiness-unibw.org/tools/rdf2rdfa/ We have our own tools for handling different RDF model data representations as per the example above, I just wanted to grok the reasoning behind the ARC2 specificity in your comments :-) Kingsley > > > > Kingsley > > > Steph. > > > On Mon, Feb 8, 2010 at 2:29 PM, Richard Cyganiak > <richard.cyganiak@deri.org <mailto:richard.cyganiak@deri.org> > <mailto: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 > <http://www.openlinksw.com/blog/%7Ekidehen> > Twitter/Identi.ca: kidehen > > > > > -- 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 23:01:07 UTC