W3C home > Mailing lists > Public > xmlschema-dev@w3.org > May 2007

Re: XML Schema Element ordering

From: Pete Cordell <petexmldev@tech-know-ware.com>
Date: Fri, 18 May 2007 10:50:29 +0100
Message-ID: <016b01c79932$84494f80$4200a8c0@Codalogic>
To: "Rich Adili" <Rich.Adili@xata.com>, <xmlschema-dev@w3.org>

In XSD schema, a base and the extra components of a derived type are always 
combined as if they are two components of an xs:sequence (i.e. base 
components first, then derived components).

So I don't think you can change your schema to get what you want.  I'm 
afraid you are going to have to change your boss instead!

HTH,

Pete.
--
=============================================
Pete Cordell
Tech-Know-Ware Ltd
for XML Schema to C++ data binding visit
 http://www.tech-know-ware.com/lmx/
 http://www.codalogic.com/lmx/
=============================================

----- Original Message ----- 
From: "Rich Adili" <Rich.Adili@xata.com>
To: <xmlschema-dev@w3.org>
Sent: Friday, May 18, 2007 5:10 AM
Subject: XML Schema Element ordering


I suppose this is a noob question but I've not found a good answer yet,
so...

This xml will not validate against the enclosed schema unless I reorder
the four text elements to match. How can I adjust the schema to allow
mix-and-match ordering of the elements without breaking the "Upper" and
"Lower" set relationships? I've heard the lecture that node order
shouldn't matter in XML but my boss is funny about giving orders and
having them followed...

<?xml version="1.0" encoding="UTF-8"?>
<Upper xsi:noNamespaceSchemaLocation="junk.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ValidationError>text</ValidationError>
<WildAndCrazy>text</WildAndCrazy>
<ValidationWarning>text</ValidationWarning>
<Guy>text</Guy>
</Upper>

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:complexType name="Lower" abstract="true">
<xsd:sequence minOccurs="0" maxOccurs="unbounded">
<xsd:element ref="ValidationError"
minOccurs="0"/>
<xsd:element ref="ValidationWarning"
minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="ValidationError"/>
<xsd:element name="ValidationWarning"/>
<xsd:element name="Upper">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="Lower">
<xsd:sequence minOccurs="0"
maxOccurs="unbounded">
<xsd:element
ref="WildAndCrazy" minOccurs="0"/>
<xsd:element ref="Guy"
minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="WildAndCrazy"/>
<xsd:element name="Guy"/>
</xsd:schema>
Received on Friday, 18 May 2007 09:54:34 GMT

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