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

Re: XML Schema compliance

From: Jeni Tennison <jeni@jenitennison.com>
Date: Fri, 4 Jul 2003 15:55:07 +0100
Message-ID: <159152848123.20030704155507@jenitennison.com>
To: "Jim Webber" <jim.webber@arjuna.com>
CC: "'Savas Parastatidis'" <Savas.Parastatidis@newcastle.ac.uk>, "'Henry S. Thompson'" <ht@cogsci.ed.ac.uk>, <xmlschema-dev@w3.org>, "'Paul Watson'" <Paul.Watson@newcastle.ac.uk>

Hi Jim,

> This is probably a rather dumb question, but it would help me
> immensely if you could offer some insight on why all of the tool
> manufacturers have, purportedly mistakenly, created software which
> flags extension of xs:element (and other types in the XML Schema
> schema) as errors.

Well, it's certainly not true of *all* the tool manufacturers. For
example, I just tried:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
           elementFormDefault="qualified">

<xs:import namespace="http://www.w3.org/2001/XMLSchema" 
           schemaLocation="http://www.w3.org/2001/XMLSchema.xsd" />

<xs:complexType name="foo">
  <xs:complexContent>
    <xs:extension base="xs:element">
      <xs:attribute name="bar" type="xs:integer" />
    </xs:extension>
  </xs:complexContent>
</xs:complexType>

<xs:element name="foo" type="foo" />

</xs:schema>

with Xerces-J 2.4.0 and it worked just fine...

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/
Received on Friday, 4 July 2003 10:55:14 GMT

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