- From: <bugzilla@jessica.w3.org>
- Date: Fri, 05 Jun 2015 10:40:38 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28762 --- Comment #1 from Michael Kay <mike@saxonica.com> --- I propose to define the evaluation of merge keys as follows: <p diff="add" at="S-bug28762">The value of <var>N</var>th merge key value of an item <var>J</var> in a <termref def="dt-merge-input-sequence">merge input sequence</termref> <var>S</var> is the result of the expression in the <code>select</code> attribute of the <var>N</var>th <elcode>xsl:merge-key</elcode> child of the corresponding <elcode>xsl:merge-source</elcode> element, or in the absence of the <code>select</code> attribute, the result of the contained <termref def="dt-sequence-constructor"/>, evaluated with a <termref def="dt-focus"/> in which the <termref def="dt-context-item"/> is <var>J</var>, the <termref def="dt-context-position"/> is the position of <var>J</var> within <var>S</var>, and the <termref def="dt-context-size"/> is the number of items in <var>S</var>.</p> However, for this to work we need to change the definition of "merge input sequence" to be (in the case where sort-before-merge="yes") the sequence prior to sorting, rather than, as currently, the sequence after sorting. This appears to work. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 5 June 2015 10:40:41 UTC