Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - Re: UPA example >Thread Next - [ANN] EditiX XML Editor 2008 - Service Pack 4 Why do we have 'Schema Component Constraint: Element Declarations Consistent'To: <xmlschema-dev@--.---> Date: 6/26/2008 3:19:00 PM 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/ From mike@s... Thu Jun 26 14:19:11 2008 Received: from [1 | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
