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 (Microsoft) Datatypes tests, certain tests appear to assume that an instance document can be invalid because a QName or NOTATION does not satisfy the length, minLength, or maxLength facet defined in the schema. However, the specification is clear that although these facets are allowed (and deprecated), they have no effect on validity. See Validation Rule: Length Valid clause 1.3 Validation Rule: minLength Valid clause 1.3 Validation Rule: maxLength Valid clause 1.3 Affected tests include: <test group="QName_length001_1357" name="QName_length001_1357.i"/> <test group="QName_length003_1359" name="QName_length003_1359.i"/> <test group="QName_minLength003_1362" name="QName_minLength003_1362.i"/> <test group="QName_maxLength001_1364" name="QName_maxLength001_1364.i"/> <test group="NOTATION_length001_1372" name="NOTATION_length001_1372.i"/> <test group="NOTATION_length003_1374" name="NOTATION_length003_1374.i"/> <test group="NOTATION_minLength003_1377" name="NOTATION_minLength003_1377.i"/> <test group="NOTATION_maxLength001_1379" name="NOTATION_maxLength001_1379.i"/>
Additional tests that have this bug: msData/additional/test73986_2.xml msData/additional/test73986.xsd
Agreed that these tests are not applicable per spec. We are following up with the WG to determine the process of updating the test suite.
Agreed that these tests do no violate the length/minlength/maxlength facets. In theory before marking them valid we should check that they are not invalid for some other reason, however it appears they pass validation by Xerces and Saxon so they are probably OK.
*** Bug 4122 has been marked as a duplicate of this bug. ***