Re: [XSLT] schema-for-xslt20.xsd not determinist

For info, after reporting it wouldn't compile, I've discovered (on
.NET 2.0) how to successfully compile the schema-for-xslt20.xsd which
imports XMLSchema.xsd, both of these import xml.xsd.

It seems with XmlSchemaSet, the order you add the schemas is critical.
You must first add XMLSchema.xsd explicitly, and then add
schema-for-xslt20.xsd. So, in this case, you can't rely on the usual
XmlSchemaSet behaviour where it detects imported schemas and adds them
for you, because then XMLSchema.xsd will be added after

The error I was getting when relying on XmlSchemaSet's auto-import was:

'The WhiteSpace constraining facet is prohibited for 'anySimpleType'.
- Line: 1767 Pos: 8

Also, XMLSchema.xsd compiles fine on its own also, unmodified. - I
thought it needed some changes first, but I was wrong - possibly
thrown by the XSLT thing.

Phil Fearon
Qutoric Limited

On Mon, Feb 28, 2011 at 12:16 AM, Philip Fearon <> wrote:
> Thanks. I had inferred the 'special' nature of this schema
> (XmlSchema.xsd) from comments within the file, so I wasn't too
> disappointed to find .NET couldn't handle it without some tweaking.
> Anyway, from what I've seen, tool suppliers tend to use their own
> customised schema versions, perhaps so that things like
> auto-completion, and validation error reports for XSD files are more
> consistent. Certainly, my own interest in compiling both XmlSchema.xsd
> and schema-for-xslt20.xsd  was only to access post-compile info used
> for XSLT/XPath auto-completion and displaying XSD type information
> within a tool.
> Phil Fearon
> Qutoric Limited
> On Sun, Feb 27, 2011 at 9:47 PM, Michael Kay <> wrote:
>> XmlSchema.xsd was designed to compile - but the schema processor needs to
>> handle it a bit specially, because it defines things in the xsd namespace
>> which ordinary user schemas aren't supposed to do. So yes, some schema
>> processors won't cope with it.
>> Michael Kay
>> Saxonica

Received on Tuesday, 1 March 2011 15:56:14 UTC