Errata for XML Syntax for XQuery 1.0 (XQueryX)

31 March 2009

Latest version:: http://www.w3.org/XML/2007/qt-errata/XQueryX-errata.html
Editor:: Jim Melton, Oracle mailto:jim.melton@acm.org

Abstract

This document addresses errors in the XML Syntax for XQuery 1.0 (XQueryX) Recommendation published on 23 January 2007. It records all errors that, at the time of this document's publication, have solutions that have been approved by the XML Query Working Group. For updates see the latest version of that document.

The errata are numbered, and are listed in reverse chronological order of their date of origin. Each erratum is classified as Substantive, Editorial, or Markup. These categories are defined as follows:

Substantive: a change to the specification that may require implementations to change and that may change the outcome of a stylesheet or query.
Editorial: a clarification, correction of a textual error, or removal of an inconsistency, where the Working Group does not believe that the intent of the specification has changed. The erratum may affect implementations or user-written queries and stylesheets if the previous lack of clarity in the specification resulted in a misreading.
Markup: correction of formatting; the effect is cosmetic only.

Each entry contains the following information:

A description of the error.
A reference to the Bugzilla entry recording the original problem report, subsequent discussion, and resolution by the Working Group.
Key dates in the process of resolving the error.
Where appropriate, one or more textual changes to be applied to the published Recommendation.

Colored boxes and shading are used to help distinguish new text from old, however these visual clues are not essential to an understanding of the change. The styling of old and new text is an approximation to its appearance in the published Recommendation, but is not normative. Hyperlinks are shown underlined in the erratum text, but the links are not live.

A number of indexes appear at the end of the document.

Substantive corrections are proposed by the XML Query Working Group (part of the XML Activity), where there is consensus that they are appropriate; they are not to be considered normative until approved by a Call for Review of Proposed Corrections or a Call for Review of an Edited Recommendation.

Please report errors in this document using W3C's public Bugzilla system (instructions can be found at http://www.w3.org/XML/2005/04/qt-bugzilla). If access to that system is not feasible, you may send your comments to the W3C XSLT/XPath/XQuery public comments mailing list, public-qt-comments@w3.org. It will be very helpful if you include the string [XQXerrata] in the subject line of your report, whether made in Bugzilla or in email. Each Bugzilla entry and email message should contain only one error report. Archives of the comments and responses are available at http://lists.w3.org/Archives/Public/public-qt-comments/.

Status of this Document

This is a public draft. None of the errata reported in this document have been approved by a Call for Review of Proposed Corrections or a Call for Review of an Edited Recommendation. As a consequence, they must not be considered to be normative.

The Working Group does not intend to progress these errata to normative status; instead, it intends to publish a second edition of the Recommendation incorporating these errata, and to progress the second edition to normative status.

Errata

XQX.E6 The Introduction failed to specify that Notes are not normative.

XQX.E5 The XSLT stylsheet in Appendix B contains a template for the transformation of <xqx:namespaceDeclaration> elements that fails to correctly "escape" curly braces in the same manner as does the template for the transformation of <xqx:attributeConstructor> elements.

XQX.E4 The XQueryX Recommendation currently links to an obsolete version of the XQuery 1.0 grammar applet.

XQX.E3 The XSLT stylesheet in Appendix B contains a template for the transformation of <xqx:parenthesizedExpr> elements that is unnecessary and the presence of which may be confusing.

XQX.E2 The XQueryX solution to Example 4 incorrectly contains an <xqx:parenthesizedExpr> element.

XQX.E1 The published XQueryX schema defines many elements using anonymous complex types.

Indexes

Index by affected section

Index by Bugzilla entry

Index by Introduction

XQX.E6 - editorial

See Bug 6377

Description

The Introduction failed to specify that Notes are not normative. A paragraph containing that statement has been inserted.

History

6 Jan 2009: Proposed

28 Jan 2009: Corrected

Change

In 1 Introduction (second paragraph):

Insert after the text:

XQueryX is an XML representation of an XQuery. It was created by mapping the productions of the XQuery grammar into XML productions. The result is not particularly convenient for humans to read and write, but it is easy for programs to parse, and because XQueryX is represented in XML, standard XML tools can be used to create, interpret, or modify queries.

The following:

In this document, examples and material labeled as "Note" are provided for explanatory purposes and are not normative.

XQX.E5 - substantive

See Bug 5343

Description

The XSLT stylsheet in Appendix B contains a template for the transformation of <xqx:namespaceDeclaration> elements that fails to correctly "escape" curly braces in the same manner as does the template for the transformation of <xqx:attributeConstructor> elements.

History

4 Jan 2008: Proposed

23 Jan 2008: Accepted

Change

In B Transforming XQueryX to XQuery:

Replace the following XSLT template:

  <xsl:template match="xqx:namespaceDeclaration">
    <xsl:text> xmlns</xsl:text>
    <xsl:if test="xqx:prefix">
      <xsl:text>:</xsl:text>
      <xsl:value-of select="xqx:prefix"/>
    </xsl:if>
    <xsl:value-of select="$EQUAL"/>
    <xsl:call-template name="quote">
      <xsl:with-param name="item" select="xqx:uri"/>
    </xsl:call-template>
  </xsl:template>

with:

  <xsl:template match="xqx:namespaceDeclaration">
    <xsl:text> xmlns</xsl:text>
    <xsl:if test="xqx:prefix">
      <xsl:text>:</xsl:text>
      <xsl:value-of select="xqx:prefix"/>
    </xsl:if>
    <xsl:value-of select="$EQUAL"/>
    <xsl:call-template name="quote">
       <xsl:with-param name="item">
         <xsl:call-template name="globalReplace">
           <xsl:with-param name="stringToBeFixed">
             <xsl:call-template name="globalReplace">
               <xsl:with-param name="stringToBeFixed">
                 <xsl:value-of select="xqx:uri"/>
               </xsl:with-param>
               <xsl:with-param name="toBeReplaced">
                 <xsl:text>{</xsl:text>
               </xsl:with-param>
               <xsl:with-param name="replacement">
                 <xsl:text>{{</xsl:text>
               </xsl:with-param>
             </xsl:call-template>
           </xsl:with-param>
           <xsl:with-param name="toBeReplaced">
             <xsl:text>}</xsl:text>
           </xsl:with-param>
           <xsl:with-param name="replacement">
             <xsl:text>}}</xsl:text>
           </xsl:with-param>
         </xsl:call-template>
       </xsl:with-param>
    </xsl:call-template>
  </xsl:template>

XQX.E4 - editorial

See Bug 5323

Description

The XQueryX Recommendation currently links to an obsolete version of the XQuery 1.0 grammar applet.

History

18 Dec 2007: Proposed

23 Jan 2008: Accepted

Change

In 3.1.4 Corresponding Grammar Abstract Parse Tree (first paragraph):

Replace the text:

For comparison, here is the abstract parse tree corresponding to the XQuery for Example 1, as produced by the XQuery grammar applets found at http://www.w3.org/2005/qt-applets/xqueryApplet.html.

With:

For comparison, here is the abstract parse tree corresponding to the XQuery for Example 1, as produced by the XQuery grammar applets found at http://www.w3.org/2007/01/applets/.

XQX.E3 - editorial

See Bug 4963

Description

The XSLT stylesheet in Appendix B contains a template for the transformation of <xqx:parenthesizedExpr> elements that is unnecessary and the presence of which may be confusing.

History

20 Aug 2007: Proposed

11 Sep 2007: Accepted

Change

In B Transforming XQueryX to XQuery:

Delete the following XSLT template:

  <xsl:template match="xqx:parenthesizedExpr">
    <xsl:value-of select="$LPAREN"/><xsl:apply-templates/><xsl:value-of select="$RPAREN"/>
  </xsl:template>

XQX.E2 - editorial

See Bug 4963

Description

The XQueryX solution to Example 4 incorrectly contains an <xqx:parenthesizedExpr> element. That element should instead be an <xqx:sequenceExpr> element.

History

20 Aug 2007: Proposed

11 Sep 2007: Accepted

Change

In 3.4.2 A Solution in XQueryX:

Replace the following XQueryX fragment:

                        <xqx:parenthesizedExpr>
                          <xqx:unionOp>
                            <xqx:firstOperand>
                              <xqx:pathExpr>
                                <xqx:stepExpr>
                                  <xqx:xpathAxis>child</xqx:xpathAxis>
                                  <xqx:nameTest xqx:prefix="ma">Seller</xqx:nameTest>
                                </xqx:stepExpr>
                              </xqx:pathExpr>
                            </xqx:firstOperand>
                            <xqx:secondOperand>
                              <xqx:pathExpr>
                                <xqx:stepExpr>
                                  <xqx:xpathAxis>child</xqx:xpathAxis>
                                  <xqx:nameTest xqx:prefix="ma">High_Bidder</xqx:nameTest>
                                </xqx:stepExpr>
                              </xqx:pathExpr>
                            </xqx:secondOperand>
                          </xqx:unionOp>
                        </xqx:parenthesizedExpr>

with:

                        <xqx:sequenceExpr>
                          <xqx:unionOp>
                            <xqx:firstOperand>
                              <xqx:pathExpr>
                                <xqx:stepExpr>
                                  <xqx:xpathAxis>child</xqx:xpathAxis>
                                  <xqx:nameTest xqx:prefix="ma">Seller</xqx:nameTest>
                                </xqx:stepExpr>
                              </xqx:pathExpr>
                            </xqx:firstOperand>
                            <xqx:secondOperand>
                              <xqx:pathExpr>
                                <xqx:stepExpr>
                                  <xqx:xpathAxis>child</xqx:xpathAxis>
                                  <xqx:nameTest xqx:prefix="ma">High_Bidder</xqx:nameTest>
                                </xqx:stepExpr>
                              </xqx:pathExpr>
                            </xqx:secondOperand>
                          </xqx:unionOp>
                        </xqx:sequenceExpr>

XQX.E1 - editorial

See Bug 4924

Description

The published XQueryX schema defines many elements using anonymous complex types. That makes it infeasible to extend the content model of those elements in other specifications that define XQueryX extensions corresponding perhaps to XQuery extensions. While conceptually simple, a number of changes are required to ensure that all elements are defined using named complex types.

History

14 Aug 2007: Proposed

15 Aug 2007: Accepted