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

Re: XML Schema compliance

From: Jeni Tennison <jeni@jenitennison.com>
Date: Wed, 9 Jul 2003 15:35:56 +0100
Message-ID: <2188014380.20030709153556@jenitennison.com>
To: "Savas Parastatidis" <Savas.Parastatidis@newcastle.ac.uk>
CC: xmlschema-dev@w3.org

Hi Savas,

> The XML Schema validator checked test.xsd for XML Schema compliance.
> It found the attribute type="xs:element" but ignored the contents.
> Then, it started building the new infoset. In the new infoset,
> xs:element is valid because there is a type declaration.

Right.

> What would have happened if type="xs:string"? Does the XML Schema
> validator assume that all XML-Schema datatypes are known in the new
> infoset?

Yes. Certain datatypes are "built-in", which means that they are
automatically included in the infoset for a schema. The built-in
datatypes are xs:anyType, xs:anySimpleType, the primitive types and
the other simple types in the http://www.w3.org/2001/XMLSchema
namespace. See:

  http://www.w3.org/TR/xmlschema-1/#section-Built-in-Simple-Type-Definition

> My problem with this has always been the fact that there are some
> datatypes that are seen as built-in in the XML Schema namespace and
> then this xs:element appears.

The definitions for the built-in datatypes are built-in to every
schema infoset. The definition for the xs:element datatype is only
present if it's imported from a Schema-for-Schema.

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/
Received on Wednesday, 9 July 2003 10:36:09 GMT

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