20060 2012-11-23 13:24:45 +0000 [XT3TS] as-2904 2013-12-09 12:25:17 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Test Suite Working drafts PC Windows 3.1 CLOSED FIXED P2 normal --- 1 tim abel.online mike public-qt-comments oldest_to_newest 78694 0 tim 2012-11-23 13:24:45 +0000 This test performs validation without importing any schemas. I suspect that otherwise the in-scope schema definitions is implementation defined. In our old test suite, we had a hack to import any schemas referenced in the catalog into the static context before compiling. It would be nice not to have this hack in the new test suite. Without the import, static type analysis can prove that the validation will fail. 78698 1 tim 2012-11-23 13:52:53 +0000 as-2906 has a similar problem. 79976 2 mike 2012-12-11 22:52:28 +0000 I think you probably have an argument here. The spec says: The components in the schema constructed from the synthetic schema document (see 3.16 Importing Schema Components) will always be available for validating constructed nodes; if additional schema components are needed, they may be located in other ways, for example implicitly from knowledge of the namespace in which the elements and attributes appear, or using the xsi:schemaLocation attribute of elements within the tree being validated. In other words, if we want to ensure interoperable behaviour, we need to have an xsl:import-schema declaration for the schema components needed for validation. It seems to me rather restrictive for a product to allow validation only against a schema that is known statically, but it seems clear from the spec that a conformant product is allowed to impose this restriction. So I have changed the tests accordingly. 97313 3 tim 2013-12-09 12:25:17 +0000 Thanks.