Copyright © 2017 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This document addresses errors in the XPath and XQuery Functions and Operators 3.1 Recommendation published on 21 March 2017. It records all errors that, at the time of this document's publication, have solutions that have been approved by the XSL Working Group and 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 XSL Working Group and 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 [FO31errata] 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/.
This is an editor's 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
FO31.E2 The "properties" section is missing for the fn:boolean function and for many of the functions in the "op" namespace.
FO31.E1 There is an example for fn:exists that is incomplete (it is not a valid expression).
Indexes
See Bug 30151
The "properties" section is missing for the fn:boolean function and for
many of the functions in the "op" namespace.
13 Oct 2017: Proposed
In 7.3.1 fn:boolean (Signature section):
Insert after the text:
fn:boolean($arg as item()*) as xs:booleanThe following:
This function is deterministic, context-independent, and focus-independent.
In 1.7.4 Properties of functions (tenth paragraph):
Insert before the text:
The fn:function-lookup function is a special case because it is
potentially dependent on everything in the static and dynamic context. This is because the static and dynamic
context of the call to fn:function-lookup are used as the static and dynamic context of the
function that fn:function-lookup returns.
The following:
Where the properties of a function are not explicitly listed, the function is deterministic, context-independent, and focus-independent.
See Bug 30133
There is an example for fn:exists that is incomplete (it is not a valid expression).
11 Jul 2017: Proposed
11 Jul 2017: Accepted
In 14.1.2 fn:exists (Examples section, first code section):
Replace the text:
let $break :=
return fn:exists($break)
With:
let $break := <br/> return fn:exists($break)
1.7.4 Properties of functions
FO31.E2
7.3.1 fn:boolean
FO31.E2
14.1.2 fn:exists
FO31.E1
Bug #30133: FO31.E1
Bug #30151: FO31.E2
fn:boolean: FO31.E2
fn:exists: FO31.E1