- From: Philip Fearon <pgfearo@googlemail.com>
- Date: Sun, 27 Feb 2011 21:20:49 +0000
- To: Michael Kay <mike@saxonica.com>
- Cc: Saašha Metsärantala <saasha@acc.umu.se>, public-qt-comments@w3.org
For the record, schema-for-xslt20.xsd compiles (and validates) ok after adding it to a .NET XmlSchemaSet instance, with custom XmlResolver. There was initially a problem with the XmlSchema.xsd, imported by schema-for-xslt20.xsd, as it appears this imported schema was never designed to compile. Removing a number of xs:restriction elements in XmlSchema.xsd did the trick. When fixing the xsd I found it useful to rig up a UI so that, when compile errors occur, they're immediately highlighted in an editor showing the xsd source. The xml.xsd was also initially giving me some problems, but this was down to my code, failing to prevent it being auto-imported twice into the XmlSchemaSet. As soon as I corrected this, there were no further issues. Phil Fearon http://qutoric.com On Sat, Feb 26, 2011 at 11:03 PM, Michael Kay <mike@saxonica.com> wrote: > > On 26/02/2011 15:00, Saašha Metsärantala wrote: >> >> Hello! >> >> The XML Schema provided by W3C for XSLT 2.0 doesn't seem to be determinist and thus fails to compile. Trying to validate the example file at >> http://www.w3.org/TR/xslt20/#d5e14761 (locally saved as example_function.xsl after insertion of an XML declaration), the error message is the following: >> >> xmllint --noout --schema http://www.w3.org/2007/schema-for-xslt20.xsd example_function.xsl >> > > Thank you for the comment. We are aware that there are a couple of schema processors fail to compile the schema for XSLT 2.0. We have looked into the issue and we believe that the schema is correct, and these processors are in error. Unfortunately there are several XSD processors that fail to implement the finer details of the specification correctly. Please report the error to the vendor of your schema processor. > > Michael Kay > Saxonica > > >
Received on Sunday, 27 February 2011 21:21:24 UTC