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

Re: Atom 1.0 + RDFa 1.1

From: Toby Inkster <tai@g5n.co.uk>
Date: Mon, 15 Nov 2010 15:43:19 +0000
To: Ivan Herman <ivan@w3.org>
Cc: RDFa Working Group <public-rdfa-wg@w3.org>
Message-ID: <1289835800.9995.76.camel@ophelia2.g5n.co.uk>
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=""
    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>

If this is processed using
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
Received on Monday, 15 November 2010 15:44:11 UTC

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