This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the section, "15.5 Defining the Merge Keys" of XSLT 3.0 spec, there is one bullet point mentioned as following, "For each integer J in 1..N, consider the set of xsl:merge-key elements that are in position J among the xsl:merge-key children of their parent xsl:merge-source element. All the xsl:merge-key elements in this set must have the same effective value for their lang, order, collation, case-order, and data-type attributes, where having the same effective value in this case means that either both attributes must be absent, or both must be present and evaluate to the same value; and in addition in the case of collation the absolute URI must be the same after resolving against the base URI." The words "both" in above paragraph seems wrong. There are five attributes mentioned, and not two. I suggest the rephrasing to following, "For each integer J in 1..N, consider the set of xsl:merge-key elements that are in position J among the xsl:merge-key children of their parent xsl:merge-source element. All the xsl:merge-key elements in this set must have the same effective value for their lang, order, collation, case-order, and data-type attributes, where having the same effective value in this case means that either *all five of these* attributes must be absent, or *all five of these attributes* must be present and evaluate to the same value; and in addition in the case of collation the absolute URI must be the same after resolving against the base URI." My suggestions are within "*" characters.
This proposed rephrasing is incorrect. A better rephrasing would be: "For each integer J in 1..N, consider the set S of xsl:merge-key elements that are in position J among the xsl:merge-key children of their parent xsl:merge-source element. For each attribute A in the set lang, order, collation, case-order, and data-type, it must be the case that for any two elements s1 and s2 in S, the effective value of attribute A on s1 is the same as the effective value of attribute A on s2, where two attributes are said to have the same effective value if either (a) both attributes are absent, or (b) both attributes are present and evaluate to the same value; furthermore, in the case of the collation attribute, the absolute URI must be the same after resolving against the base URI." (The text could be more liberal and allow an attribute to be defaulted on one element and given an explicit value equivalent to the default on another. But it doesn't attempt to allow that and the intent here is to clarify the spec, not to write a better spec.)
Note that a proposed erratum was drafted, E29, but it appears that something went wrong with the rendering, which shows: Change Expression ulist[2]/item[2]/p selects nothing --- For reference, the HTML version of the erratum: https://htmlpreview.github.io/?https://github.com/w3c/qtspecs/blob/master/errata/xslt-30/html/xslt-30-errata.html#E29
The formatting of the erratum has been fixed.