HI all,
This doesn't pertain to Saxon per se, but I am trying to better understand why the current XSLT3 working draft's treatment of map construction through xsl:map differs from the construction of maps in Xpath3 directly through map:new(), insofar as duplicate keys cause an error in the former case and not the latter.

Can someone enlighten me why map:new("A" := 1; "A" := 2) should lead to a different result from

<xsl:map>
<xsl:map-entry key ="'A'" select="1"/>
<xsl:map-entry key ="'A'" select="2"/>
</xsl:map>


This seems to limit use of xsl:map even more than the limitations described in the working draft.

-David

--

"A false conclusion, once arrived at and widely accepted is not dislodged easily, and the less it is understood, the more tenaciously it is held." - Cantor's Law of Preservation of Ignorance.