W3C home > Mailing lists > Public > www-rdf-comments@w3.org > January to March 2002

Re: Error in the RDF/XML Syntax Specification

From: Sjoerd Visscher <sjoerd@w3future.com>
Date: Tue, 22 Jan 2002 20:56:53 +0100
Message-ID: <3C4DC405.30807@w3future.com>
To: www-rdf-comments@w3.org
> Other specifications such as the
>
>   XQuery 1.0 and XPath 2.0 Data Model (Working Draft 20 December 2001)
>   http://www.w3.org/TR/2001/WD-query-datamodel-20011220/
>
> define their Infoset filtering operation simply:
>
>   "Other information items and properties made available by the
>   Infoset processor are ignored."
>   -- Appendix A: XML Information Set Conformance
>      http://www.w3.org/TR/2001/WD-query-datamodel-20011220/#d2e4846


This is not true. They very precisely define the transformation.

For example: 
http://www.w3.org/TR/2001/WD-query-datamodel-20011220/#infoitem-to-node
clearly defines what is a node and what is not:

    else
        /* infoitem-kind(i) = "doctype" | "notation" | "unparsed-entity" */
        empty-sequence()

And in 
http://www.w3.org/TR/2001/WD-query-datamodel-20011220/#infoitem-to-element-node

    kids := collapse-text-nodes(sequence-map(infoitem-to-node, 
infoset-element-children(e))),

I think it's really important that the spec provides exact 
transformations from the XML semantics to the RDF semantics.
Ofcourse you could use the RDF/XML syntax to represent both the xml 
infoset and the rdf triples, and provide an XSLT tranformation, but that 
wouldn't be very helpful I guess.

Sjoerd Visscher
http://w3future.com
Received on Tuesday, 22 January 2002 14:56:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 21 September 2012 14:16:30 GMT