Subject:Schema Validation Author:Vinayak Sapre Date:14 Feb 2003 04:28 AM
I have observed that there are issues with different schema validators. For example the attached schema has a character data (period) in complextype which is validated by Stulus Studio but XML Spy, IBM's schema checker do not validate this.
What are the limitations of built in schema validator?
Is it a good to use external validator?
If yes which one is the best?
Subject:Re: Schema Validation Author:Alberto Massari Date:14 Feb 2003 05:43 AM
At 04.46 14/02/2003 -0500, you wrote:
>From: "Vinayak Sapre"
>I have observed that there are issues with different schema validators.
>For example the attached schema has a character data (period) in
>complextype which is validated by Stulus Studio but XML Spy, IBM's schema
>checker do not validate this.
>What are the limitations of built in schema validator?
The built in validator is Xerces 2.1, and it supports the XMLSchema 1.0
specs. The next version (Xerces 2.2, that will be part of Stylus Studio
5.0) will include changes required by the clarifications listed in the
In any case, the only recognized limitations of Xerces are listed at http://xml.apache.org/xerces-c/schema.html; all the others are bugs, so
please report them ;-)
>Is it a good to use external validator?
Yes; XMLSchema is a complex specification, and being pretty new,
implementations can behave differently. For an example of how you can set
up an external validator inside Stylus, look at the message http://edn.exceloncorp.com/read?6252,46
>If yes which one is the best?
The W3C set up a test collection, but the only published comparisons only
involve pretty old versions of MSV, XSV and Xerces (you can find the report
My advice is to ensure that your schemas can be processed by the validator
that you are going to use in your project; if you are going to publish the
schema for public consumption, you should probably test it against all of
them (XSV, Xerces-C, Xerces-J, MSXML, Oracle, ...)