W3C home > Mailing lists > Public > xmlschema-dev@w3.org > June 2008

Why do we have 'Schema Component Constraint: Element Declarations Consistent'

From: Pete Cordell <petexmldev@codalogic.com>
Date: Thu, 26 Jun 2008 14:19:13 +0100
Message-ID: <002601c8d78f$3c2e94c0$ea00a8c0@Codalogic>
To: <xmlschema-dev@w3.org>

I was just wondering why schema has the rules about "Schema Component 
Constraint: Element Declarations Consistent".  i.e. if two elements in the 
same complex type have the same name, then they have to have the same type. 
Surely if the association of element information items to particles is 
unambiguous and someone wants to declare:

<xs:sequence>
<xs:element name='a' type='xs:int'/>
<xs:element name='a' type='xs:string'/>
</xs:sequence>

then how does it break XML or schema to allow them to do it?  I can see that 
this might be a problem for XSLT processing, and as such such a schema 
design could be deemed practice, but is that schemas problem?

Thanks,

Pete Cordell
Codalogic
For XML C++ data binding visit http://www.codalogic.com/lmx/
Received on Thursday, 26 June 2008 13:20:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:56:14 UTC