16161 2012-02-29 16:58:25 +0000 disallowedSubst00503m3,4,5 should be invalid for XSD 1.1 2012-12-04 00:52:14 +0000 1 1 1 Unclassified XML Schema Test Suite Sun Tests 2006-11-06 All Windows 3.1 NEW decided P2 normal --- 1 am_spamfaenger cmsmcq David_E3 mike public-xml-schema-testsuite oldest_to_newest 64730 0 am_spamfaenger 2012-02-29 16:58:25 +0000 In my opinion the expected result of the test cases disallowedSubst00503m3, disallowedSubst00503m4 and disallowedSubst00503m5 of set ElemDecl should be invalid for XSD 1.1 because they violate clause 4 of Schema Component Constraint: Element Declaration Properties Correct. As described in http://www.w3.org/TR/xmlschema11-1/#key-val-sub-type a complex type definition S is validly substitutable for another complex type definition T if: "S is validly derived from T subject to the blocking keywords in the union of K and T. {prohibited substitutions}, as defined in Type Derivation OK (Complex) (§3.4.6.5)" So in difference to XSD 1.0 this also considers the prohibited substitutions of T (i.e. the value of the block attribute of the complex type definition "Type" in the concrete examples). 66700 1 David_E3 2012-04-13 15:52:42 +0000 Needs further research. Once the test suite is in its new location this research will be easier. 66704 2 mike 2012-04-13 17:04:32 +0000 I agree with Andreas. The spec has been deliberately changed. In XSD 1.0 you were allowed to say that Member1 is in the substitution group of Head, but saying this had no effect, so the instance is invalid. In XSD 1.1 we've changed it so instead of being ineffective, it's an error. (Saxon issues a warning at schema processing time; the code that issues this warning carries a comment which could be interpreted as slanderous.) 66913 3 mike 2012-04-20 22:41:28 +0000 As far as I can see the same reasoning also makes the following invalid: disallowedSubst00105m disallowedSubst00106m2 disallowedSubst00501m2 disallowedSubst00502m3 disallowedSubst00502m4 66916 4 mike 2012-04-20 22:53:50 +0000 To try and sum up my reading of the current rules in ordinary English: (a) if you declare an element M as being in the substitution group of H, and H blocks substitution, that's not in itself an error, it just means M can't be substituted for H. (b) however, if the type of M is not substitutable for the type of H, perhaps because either H or the type of H blocks substitution (or restriction|extension, if the type of M is a restriction|extension), that is an error - it makes the schema invalid. This is the case that has changed since 1.0. I suppose it's pointless to ask why the distinction? 67059 5 mike 2012-04-25 20:17:05 +0000 Other affected tests in the Microsoft ElementDecl test set: elemT062 elemT063 elemT064 elemT065 elemT066 elemT077 67108 6 mike 2012-04-26 14:33:19 +0000 Test msData/additional/addB114.xsd has the same problem. 67323 7 David_E3 2012-05-04 16:22:58 +0000 Resolved: change the outcome of the listed tests to invalid for 1.1.