- From: <xquery@attbi.com>
- Date: Sun, 22 Jun 2003 21:47:56 +0000
- To: public-qt-comments@w3.org
I should add that the example will result in an error, since the doc() function returns a document node and document nodes are disallowed in element content (section 3.2.7.1, second rule numbered 1). Also, the two computed element constructor examples in section 3.2.7.1 that compute the name are both type errors: element {node-name($e)} {$e/@*, 2 * data($e)} (which has been reported previously) because node-name() returns an xs:QName? instead of an xs:QName, and also element {$dict/entry[word=name($e)]/variant[lang="Italian"]} {$e/node()} (which returns an element instead of xs:QName). Either the examples need to be corrected to match the rules, or else the rules need to be corrected to match the examples (possibly by applying atomization to the name expression). > The example in section 3.7.2.3 of the XQuery May 2 draft appears to contain an > error (missing curly braces): It should be > > document > { > <author-list> > { doc("bib.xml")//book/author } > </author-list> > } > > It is not a syntax error without these, but then the path will be included > verbatim instead of executing it as an embedded expression. > > > Cheers, > > Michael Brundage > Writing as > Author, "XQuery: The XML Query Language" (Addison-Wesley, to appear 2003) > Co-author, "Professional XML Databases" (Wrox Press, 2000) > > not as > Technical Lead > Common Query Runtime/XML Query Processing > WebData XML Team > Microsoft
Received on Sunday, 22 June 2003 17:48:02 UTC