http://www.w3.org/Bugs/Public/show_bug.cgi?id=3224 ------- Comment #8 from mike@saxonica.com 2007-04-20 16:57 ------- >no errors result from comparisons--only true or false results. This might be true in a rather strict sense, but it seems a misleading statement. If you have a restriction of xs:integer, and define the maxInclusive value as "2007-04-20", you get an error. You can argue that this isn't an error that "results from a comparison" - rather, that the system refused to do a comparison; but in the ordinary sense of the word the error has occurred because 23 and 2007-04-20 cannot be compared (that is, they are incomparable). In fact, you seem to be using "incomparable" to describe a quite different relationship: a relationship where two values *can* be compared, and the outcome of the comparison is a value akin to "unknown". Furthermore, people are unlikely to read the phrase "as far as this specification is concerned" as excluding comparisons done within an assertion, where the XPath comparison semantics apply - and these can certainly result in errors.Received on Friday, 20 April 2007 16:57:48 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 October 2007 06:13:41 GMT