W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > November 2010

Re: Atom 1.0 + RDFa 1.1

From: Ivan Herman <ivan@w3.org>
Date: Mon, 15 Nov 2010 17:01:00 +0100
Cc: RDFa Working Group <public-rdfa-wg@w3.org>
Message-Id: <6B495D67-1508-4016-91EE-5EBE5AA55827@w3.org>
To: Toby Inkster <tai@g5n.co.uk>
Ah o.k. You have just found a bug in my list management stuff:-)

For an RDFa-savy preprocessing is of course easy because it can find an XML Literal declaration. I see that an XSLT based one would go wrong... I am not sure what we can do about it, though.


On Nov 15, 2010, at 16:43 , Toby Inkster wrote:

> On Mon, 2010-11-15 at 16:22 +0100, Ivan Herman wrote:
>>> Here's the example again:
>>> <feed xmlns="http://www.w3.org/2005/Atom"
>>>   property="http://example.com/xml"
>>>   datatype="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral"
>>>> <entry /></feed>
>> is this a realistic example? I mean: how would such a situation in
>> Atom occur? What does it mean? Is it a real-life issue? 
> No, it's not realistic - it's a minimal example. If you'd prefer...
>  <div about=""
>     property="dc:description"
>     datatype="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral">
>    This page is all about the book
>    <div about="http://www.worldcatlibraries.org/isbn/9780262912423"
>          typeof="bibo:Book" class="book-template">
>       <em property="dc:title">A Semantic Web Primer</em>
>       <ul rel="dc:creator" resource="::List">
>         <li property="::member">Grigoris Antoniou</li>
>         <li property="::member">Frank van Harmelen</li>
>       </ul>
>    </div>
>  </div>
> If this is processed using
> http://www.w3.org/2010/02/rdfa/wiki/ContainersAndCollections#Collection.2FContainer_transformation_of_the_DOM
> then the XMLLiteral will contain dummy elements that were inserted by
> the pre-processor. And in fact, these dummy elements will break the HTML
> content model, as they need to be parents of <li> but children of <ul>,
> and I don't think any such elements exist (perhaps <noscript>??)
> Pre-processing in general is incompatible with XMLLiterals, unless the
> preprocessor is exceptionally careful at not changing any elements that
> will be part of an XMLLiteral; or there is some sort of communication
> between the code that does the pre-processing and the code that
> generates XMLLiterals, to make sure that any changes made by the
> pre-processor are undone when generating an XMLLiteral. 
> -- 
> Toby A Inkster
> <mailto:mail@tobyinkster.co.uk>
> <http://tobyinkster.co.uk>

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

Received on Monday, 15 November 2010 15:59:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:22 UTC