W3C home > Mailing lists > Public > xmlschema-dev@w3.org > July 2003

Re: XML Schema compliance

From: Jeni Tennison <jeni@jenitennison.com>
Date: Tue, 8 Jul 2003 15:30:02 +0100
Message-ID: <114101260344.20030708153002@jenitennison.com>
To: "Savas Parastatidis" <Savas.Parastatidis@newcastle.ac.uk>
CC: xmlschema-dev@w3.org

Hi Savas,

> This is the modified version. I just changed the "schemaLocation" to
> point to a file locally. Can you use the file attached? It is the
> Schema-for-Schemas with a slightly modified xs:element complexType
> (the "type" attribute has been commented out).
[snip]
> Now, if your schema validator says that this is valid, I would argue
> that it has ignored the xs:element element definition found in the
> SfS.xsd but has not ignored the xs:element type declaration. Why?

The schema validator that I used (Xerces-J) reported that the schema
was valid, as expected. SfS.xsd is used in constructing the infoset
for my test.xsd schema that's used to validate my instance document;
it is not used to validate test.xsd to check that it's a valid schema.
The contents of SfS.xsd have absolutely no bearing on whether the
validator thinks that test.xsd is valid or not.

> If the validator says that this is invalid, then that means that is
> has replaced everything that it knows about the XML Schema
> structures because of the import statement. Doesn't that potentially
> break all the XML Schema validation rules?

If I found a validator that used the <xsd:import> from the schema that
it was validating to create the schema-for-schema that it used to
validate that schema then yes, I would say that validator was terribly
buggy. If you've experienced such a validator I suggest that you write
to the developers with a bug report.

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/
Received on Tuesday, 8 July 2003 10:30:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:39 GMT