26832 2014-09-17 10:08:50 +0000 [XP31] 3.7.2 General Comparisons 2015-07-07 15:55:32 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XPath 3.1 Working drafts SGI Windows NT RESOLVED FIXED https://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xpath-31.html#id-general-comparisons P2 normal --- 1 tim jonathan.robie josh.spiegel mike public-qt-comments oldest_to_newest 111681 0 tim 2014-09-17 10:08:50 +0000 The problem here isn't specific to XPath 3.1, but it might be a good time to clear this issue up now... In 3.7.2 General Comparisons, Step 4 says: "The result of the comparison is true if and only if there is a pair of atomic values, one in the first operand sequence and the other in the second operand sequence, that have the required magnitude relationship. Otherwise the result of the comparison is false... " This suggests that possible outcomes are only true or false. However, the paragraph then goes on to mention one error condition. So possible outcomes are: true: e.g. true() = true() false: e.g. true() = false() FORG0006: e.g. true() = xs:yearMonthDuration('P1999Y') FORG0001: e.g. xs:yearMonthDuration('P1999Y') = xs:untypedAtomic('untyped') XPTY0004: e.g. xs:yearMonthDuration('P1999Y') = xs:dateTime('2013-01-01T00:00:00Z') (the last of which being determined statically). The discrepancy between the two statements suggests that it might be permissible to ignore all errors and return only true or false. A similar problem occurs in the test describing comparison when XPath 1.0 compatibility mode is false. 112033 1 jonathan.robie 2014-09-23 17:25:56 +0000 I will change this to: Otherwise the result of the comparison is false or an error. 121770 2 mike 2015-07-06 08:31:06 +0000 The change promised in comment #1 does not appear in the current draft specification. 121854 3 josh.spiegel 2015-07-07 15:55:00 +0000 Previously, it was only changed in XPath in the case where XPath compatibility mode is true.