- From: Ivan Herman <ivan@w3.org>
- Date: Sun, 13 May 2012 14:20:11 +0200
- To: Niklas Lindström <lindstream@gmail.com>
- Cc: Gregg Kellogg <gregg@greggkellogg.net>, W3C RDFWA WG <public-rdfa-wg@w3.org>
Niklas, I am on a meeting, so I cannot check but, afaik, even in RDFa 1.0 @content gets the upper hand. The automatic type setting for XML Literal occurs only if the element content is used for a literal, ie, when there is no @content. Ivan On May 13, 2012, at 12:47 , Niklas Lindström wrote: > Oh, yes, you're right. Thanks! > > Specifically this means that in 1.0, even if the value is given in a > @content, the nested content isn't parsed for RDFa, right? So that the > result would be only: > > <http://example.net/> rdf:value "value one" . > > Or does it also mean that the first value is typed as an XMLLiteral > (even though it's taken from @content)? > > Best regards, > Niklas > > > On Sat, May 12, 2012 at 11:45 PM, Gregg Kellogg <gregg@greggkellogg.net> wrote: >> Niklas, I saw that 0292 is enabled for both RDFa 1.0 and RDFa 1.1. However, my RDFa 1.0 processor treats the property value of <a> as an XMLLiteral. In RDFa 1.0 if a @property value contains elements, it's treated as an XMLLiteral. >> >> I'm going to change this to be an RDFa 1.1-only test. >> >> Gregg >> > ---- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Sunday, 13 May 2012 12:17:09 UTC