4135 2007-01-02 18:17:26 +0000 Microsoft "schema" test set, schU1 (circular redefines) 2010-06-04 16:04:54 +0000 1 1 1 Unclassified XML Schema Test Suite Microsoft tests 2006-11-06 PC Windows XP NEW disputedSpec P2 normal --- 1 mike ht cmsmcq public-xml-schema-testsuite oldest_to_newest 13325 0 mike 2007-01-02 18:17:26 +0000 In the Microsoft "schema" test set, test <test group="schU1" name="schU1"/> there are two schema documents, each of which redefines the other. The metadata indicates that this is considered valid. I can't find an explicit ban on circular redefines. However, I believe there is an implicit ban. XML Schema Part 1 Schema Representation Constraint: Redefinition Constraints and Semantics states: If the ·actual value· of the schemaLocation [attribute] successfully resolves [then] it resolves to [something which] corresponds to a <schema> element information item in a well-formed information set, which in turn corresponds to a valid schema. In the presence of circular redefines, I don't believe that this rule is decideable. You can't determine whether the information set corresponds to a valid schema without processing the xs:redefines, and this leads to infinite regress. (Perhaps this is wriggling. The same argument could be used to disallow circular xs:include. However, it's relatively easy to find an algorithm for determining that either all the xs:include directives in a cycle are valid, or none of them are. Because of the special semantics of xs:redefine, it's far less clear that such an algorithm exists in this case.) 13431 1 mike 2007-01-11 00:14:29 +0000 *** Bug 4134 has been marked as a duplicate of this bug. *** 13895 2 zafara 2007-02-02 19:37:34 +0000 Agreed that this test should not be published as a compliance test. We are following up with the WG to determine the process of updating the test suite. 31341 3 ht 2010-01-29 15:42:25 +0000 Looks to me like the WG needs to rule on this: does the spec. allow circular redefines, or not? 35972 4 cmsmcq 2010-06-04 16:04:54 +0000 One problem here is the parallel to circular includes. The spec neither explicitly licenses nor explicitly forbids either circular inclusion nor circular redefinition, and implementations differ in whether they allow them or not. The interpretation of circular include as legal seems to depend on the idea that there is a fixed-point semantics for inclusion under which circular inclusions are perfectly well defined. The same sort of fixed-point semantics can be applied to circular redefine in at least some cases. Many people seem to shy away from this as too horrible to contemplate. But if the spec is assumed to have silently assumed a fixed-point semantics for the one, then why not for the other?