In Section 3.1.5, it says:
"2. If the expected type is a numeric type, then the given value V is
effectively replaced by fn:number(V[1])."
This should apply only when it is expecting up to one numeric value. If it
is expecting a sequence of (possibly several) numeric values, you wouldn't
want it to use just the first one.
For example, the expected type of the codepoints-to-string argument is
xs:integer*. codepoints-to-string( (97, 98, 99) ) should return "abc", not
just "a", regardless of XPath 1.0 compatibility mode.
I realize that codepoints-to-string is not part of XPath 1.0, but it still
seems that you wouldn't want its behavior to change because of XPath 1.0
compatibility mode.
Thanks,
Priscilla Walmsley