- From: Philip Fearon <pgfearo@googlemail.com>
- Date: Mon, 28 Feb 2011 00:16:45 +0000
- To: Michael Kay <mike@saxonica.com>
- Cc: Saasha Metsärantala <saasha@acc.umu.se>, public-qt-comments@w3.org
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 <mike@saxonica.com> 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 Monday, 28 February 2011 00:17:17 UTC