Hi John,

Someone should probably add this question to the general faq some day...
While Xerces is validating an instance document, it will also check the
corresponding schema to make sure it's valid; Xerces doesn't use
datatypes.xsd et al to do this because it can do it more efficiently
in-house, as it were.

So if you want to validate your schema, the easiest thing to do is to write
up a trivial valid instance document and run it through the parser.

Now you are right, of course, that any valid schema is an instance of the
schemas you cited, and Xerces should be able to handle it.  But 1.3.1
didn't support all schema features, and this is likely the underlying cause
of the myriad errors you saw.

Hope that helps,
Neil

Neil Graham
XML Parser Development
IBM Toronto Lab
Phone:  416-448-3519, T/L 778-3519
E-mail:  [EMAIL PROTECTED]



John Keyes <[EMAIL PROTECTED]> on 04/27/2001 09:16:25 AM

Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:
Subject:  Validating the Schema for Schemas


Xerces Version: 1.3.1

I downloaded the 'schema.xsd','datatypes.xsd', 'XMLSchema.dtd'
and 'datatypes.dtd' from www.w3.org.

I instantiated a DocumentBuilder in the manner described by the
DOM Plugability Section in JAXP 1.1.  This DocumentBuilder was
a validating parser.

I then called parse passing a File that contained a simple
Schema.

I wanted to check if the schema is a valid one and thus I needed
to validate it against the schema files described above.  This parse
resulted in around 200 error messages.  I could include these
error messages but there are so many I'm not sure it would be
valuable.

I was wondering if anyone has managed to validate an XML Schema ?

Thanks,
-John K


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to