[Bug 2456] Changes to min() and max()

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2456





------- Additional Comments From mike@saxonica.com  2005-12-13 12:04 -------
In raising this comment I asked why the change had been made: it appears it was
made in response to a comment from Joanne Tong (bug 1512) which was wrongly
classified as editorial. I didn't actually express a view about whether the
change was desirable.

I would now argue that the previous specification is better: the value returned
by max() and min() should be one of the values in the input sequence after
atomization and conversion of untypedAtomic values, but before type promotion.
The main reason for this is that "promotion" from decimal to double can lose
precision. For example, if @default is the untypedAtomic value "0.0", the result
of max((1.123456789123456789123456789, @default)) should be the value supplied
in the argument, not the result of rounding this value to the nearest double.

Received on Tuesday, 13 December 2005 12:05:21 UTC