20102 2012-11-27 17:19:48 +0000 [XT3TS] backwards-039 2012-11-28 06:59:28 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Test Suite Working drafts PC Windows NT CLOSED FIXED P2 normal --- 1 tim abel.online mike public-qt-comments oldest_to_newest 78926 0 tim 2012-11-27 17:19:48 +0000 Are the expected results for this test correct? The keys are: <xsl:key name="k" match="item" use="."/> (from XSLT 1.0 stylesheet) <xsl:key name="k" match="item" use="number(.)"/> (from XSLT 2.0 stylesheet) The input number is: <content> <data> <item>1.00</item> <item>2.00</item> <item>1</item> <item>2</item> </data> </content> Both will use backwards-compatbility behaviour, due to one key being from an XSLT 1.0 stylesheet. key('k', 1.0) will return: <item>1.00</item> because number(<item>1.00</item>) cast as string = number(1.0) cast as string and <item>1</item> because number(<item>1</item>) cast as string = number(1.0) cast as string Have I missed something? 78960 1 mike 2012-11-28 00:08:07 +0000 Saxon is failing this test too, so I suspect you are right that something is wrong with the test. 78961 2 mike 2012-11-28 00:45:25 +0000 I agree with your analysis and will change the expected result accordingly. I'm puzzled by the history. The test appeared in the old test suite as backwards026a and the new test seems identical to the old; Saxon was reporting success against the old test, yet when I run it freestanding it doesn't report the expected results. The old test suite used the same results file for both tests backwards026 and backwards026a and this could have somehow confused my test driver. Anyway, investigating history is rarely productive in such matters, so I shall just fix it. 78978 3 tim 2012-11-28 06:59:28 +0000 We were also passing the test in the old test suite. Confirmed fixed - thanks.