4922 2007-08-08 14:12:37 +0000 modelGroups: redefined schemaLocation not present 2007-08-09 13:13:55 +0000 1 1 1 Unclassified XML Schema Test Suite Microsoft tests 2006-11-06 PC Windows XP RESOLVED INVALID P2 normal --- 1 mhpchan ht public-xml-schema-testsuite oldest_to_newest 16085 0 mhpchan 2007-08-08 14:12:37 +0000 testcases affected: msData/modelGroups/mgO020.xsd msData/modelGroups/mgP041.xsd msData/modelGroups/mgP050.xsd Testcases are trying to redefine a group that is originated from foo.xsd. foo.xsd does not exist and xml4c has thrown a warning instead of an error. The schema spec is open in this issue because it says that these are only 'hints'. The processor/parser have a lot of freedom in how this type of issue is handled. Currently, it seems that xml4c will handle this type of issue with a warning instead of an error. Therefore, a scenario that tests for warnings should be used to test the above testcases. 16086 1 ht 2007-08-08 15:31:56 +0000 I think this comment is mistaken -- schemaLocation is a hint in instance documents, and on xs:import, but not on xs:include or xs:redefine. The spec ("Schema Representation Constraint: Redefinition Constraints and Semantics", http://www.w3.org/TR/xmlschema-1/#src-redefine) says "1 If there are any element information items among the [children] other than <annotation> then the ·actual value· of the schemaLocation [attribute] must successfully resolve." As the most recent PWD of XML Schema 1.1 clarifies, that "must" is an RFC2119 MUST.