- From: Savas Parastatidis <Savas.Parastatidis@newcastle.ac.uk>
- Date: Wed, 9 Jul 2003 17:07:20 +0100
- To: "Jeni Tennison" <jeni@jenitennison.com>
- Cc: <xmlschema-dev@w3.org>
Hi Jeni, Thank you very much for your messages. I feel educated :-) However, it still feels strange that you can write type="xs:element". Best regards, -- Savas Parastatidis http://savas.parastatidis.name > -----Original Message----- > From: Jeni Tennison [mailto:jeni@jenitennison.com] > Sent: Wednesday, July 09, 2003 3:36 PM > To: Savas Parastatidis > Cc: xmlschema-dev@w3.org > Subject: Re: XML Schema compliance > > 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 12:08:03 UTC