3733 2006-09-15 19:39:14 +0000 [XPath] reorder rules in Node Comparisons 2006-09-19 17:40:11 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XPath 2.0 Candidate Recommendation PC Windows XP CLOSED FIXED P2 normal --- 3699 1 andrew.eisenberg chamberl tim public-qt-comments oldest_to_newest 11806 0 andrew.eisenberg 2006-09-15 19:39:14 +0000 In http://www.w3.org/Bugs/Public/show_bug.cgi?id=3699, it was suggested that bullets 2 and 3 be swapped in section 3.5.3, Node Comparisons. This section now reads as follows: "The result of a node comparison is defined by the following rules: 1. The operands of a node comparison are evaluated in implementation-dependent order. 2. Each operand must be either a single node or an empty sequence; otherwise a type error is raised [err:XPTY0004]. 3. If either operand is an empty sequence, the result of the comparison is an empty sequence, and the implementation need not evaluate the other operand or apply the operator. However, an implementation may choose to evaluate the other operand in order to determine whether it raises an error. 4. ..." As written, the commentor thought that we might intend that "() is 100" be required to raise XPTY0004. 11871 1 chamberl 2006-09-19 17:39:57 +0000 Andrew, On Sept. 16, 2006, the Query and XSLT working groups discussed this issue and agreed with your suggestion to reverse the order of Rules 2 and 3 in Section 3.5.3, Node Comparisons. This change will enable an early exit from node comparisons if either operand is an empty sequence (preserving consistency with value comparisons.) Since you were present during the discussion, I am marking this bug report as Fixed and Closed. Regards, Don Chamberlin (for the Query and XSLT working groups)