1 This is MS.NET bug note. I confirmed them with version 1.1.
3 In this document I refer to OASIS test suite. It is located here:
4 http://www.oasis-open.org/committees/documents.php?wg_abbrev=xslt
8 position() handling in predicates is incomplete. For example,
9 see foo [position() mod 1 > 0] [position() > 3] [2] result
10 (match_match19.xsl, match_match22.xsl and match_match26.xsl)
13 Import precedence resolution on attribute sets are buggy if there are
14 two imported stylesheets and both of them have identically-named
15 attribute in the identically-named attribute sets. MS takes the one
16 from the first stylesheet, but it must be the one from another.
17 (attribset_attribset_45.xsl)
20 http://www.w3.org/1999/11/REC-xslt-19991116-errata/ E26 says that
21 attribute sets are combined before use-attribute-set is replaced with
22 the actual attributes. MS does not conform to this requirement.
23 (attribset_attribset42.xsl)
30 MS.NET has "Oxford style" which for example converts 99 as
31 XXXXXXXXXIX. It is not violating XSLT 1.0 spec. However, section
32 7.7.1 explicitly describes 4 and 9 as iv and ix, so strict Oxford
33 style violates the spec.