This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The specification for adaptive serialization says: An atomic value of any other type is serialized using the syntax of a constructor function: xs:TYPE("VAL") where TYPE is the name of the primitive type, and VAL is the result of applying the fn:string() function. This makes the following tests incorrect: Serialization-adaptive-37, -41, -42 In each of these cases the expected result uses a non-primitive type (xs:dateTimeStamp, xs:yearMonthDuration, xs:dayTimeDuration). May be worth raising as a spec issue, but for the moment, the test seems clearly to expect something different from what the spec says.
Do you have a strong preference either way?
I'm undecided. On the one hand, if the type information is there, it seems silly to lose it. On the other hand, I think xs:int is probably best displayed in the same way as xs:integer, so we lose the extra info in that case. I think the current spec is workable and that's what we've implemented, so I'm content with the status quo.
This should be fixed as requested. Please confirm.
Confirmed OK.