- From: Ivan Herman <ivan@w3.org>
- Date: Tue, 09 Feb 2010 16:54:29 +0100
- To: Stephane Corlosquet <scorlosquet@gmail.com>
- CC: Richard Cyganiak <richard.cyganiak@deri.org>, Public RDFa <public-rdfa@w3.org>, Michael Hausenblas <michael.hausenblas@deri.org>, Lin Clark <lin.clark@deri.org>, Tobias Wunner <tobias.wunner@deri.org>
- Message-ID: <4B718535.3010402@w3.org>
Just as an info: one of the issues that will/should be taken up for RDFa1.1 is the exact handling of XMLLiterals; per charter this is the only feature that _might_ be changed in spite of creating a backward incompatible change... Ivan On 2010-2-8 22:01 , Stephane Corlosquet wrote: > I think this use case would make a good candidate for the next version > of RDFa. > > Steph. > > On Mon, Feb 8, 2010 at 3:52 PM, Richard Cyganiak > <richard.cyganiak@deri.org <mailto:richard.cyganiak@deri.org>> wrote: > > So the options are to willfully violate the RDFa spec, or to put the > same thing in the page twice. I don't like either of those. > > Thinking more about the issue, it occurs to me that one could argue > that the foaf:name triple is “there” anyways, even if the RDFa spec > says it's not: it's encoded *inside* the rdf:XMLLiteral. An RDFa > processor that finds an XMLLiteral inside a web page could certainly > decide to parse that literal for RDFa markup as well. > > Richard > > > > > On 8 Feb 2010, at 20:16, 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. > > 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 > > > > > -- > 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 > > -- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF : http://www.ivan-herman.net/foaf.rdf vCard : http://www.ivan-herman.net/HermanIvan.vcf
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Tuesday, 9 February 2010 15:52:27 UTC