Correct behaviour of map:merge for same keys
Replies (1)
Please register to reply
Added by Thomas Fischer about 8 years ago
Hi, I'm struggling with the same key behavior for map:merge The Saxon documentation at http://www.saxonica.com/documentation/#!functions/map/merge says: [...] W3C Specification introduce a significant change [...] to take the value from the first map containing that key.
The W3C Spec at https://www.w3.org/TR/xpath-functions-31/#func-map-merge says: The associated value for each such key is taken from the last map in the input sequence [...]
Also, the Saxon documentation mentions an @$options argument@ which doesn't appear in the W3C specs.
Am I just looking into the wrong spec?
salute Thomas
I think that you can now view the latest snapshot of the spec at
http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/Overview.html
Please register to reply