4948 2007-08-14 14:10:40 +0000 Particles: Ob003 2010-07-06 13:59:26 +0000 1 1 1 Unclassified XML Schema Test Suite Microsoft tests 2006-11-06 PC Windows XP RESOLVED FIXED Metadata updated 2010-07-06 P2 normal --- 1 mhpchan ht David_E3 mike public-xml-schema-testsuite oldest_to_newest 16143 0 mhpchan 2007-08-14 14:10:40 +0000 Currently, the schema for msData/particles/particlesOb003.xsd is valid. Within the schema, the namespace constraint is specified but the process Contents constraint is absent; therefore, defaulting in 'strict'. The xml instance that follows this schema follows the namespace constraint specified but the element that it declares is not declared in the schema. Because the processContents is defaulted to 'strict', the instance should report an error and the scenario used to should an invalid scenario. A simple change in the scenario to test this instance should result in a successful testcase. The following instances follow the same pattern as above: Ob006 Ob007 Ob012 Ob015 Ob022 Ob042 Ob047 Ob048 Ob052 Ob054 Ob057 Ob059 Ob060 35231 1 mike 2010-04-23 15:57:05 +0000 The issue here seems to be that the result depends on what schema you use for validation. Is it the schema built from the schema documents listed in the metadata? Or do you add the schemas listed in the xsi:schemaLocation attribute in the instance? The test suite documentation is unclear. Perhaps we need to add metadata to the test catalog to say whether xsi:schemaLocation should be honoured. 35232 2 David_E3 2010-04-23 16:07:37 +0000 WG decided that the sense of the test is correct, but the intention would be clearer by adding the schema document referenced in the instance to the metadata. Same for the other tests listed below.