Re: Ignore Order while validating XSD

On 26 Jan 2009, at 09:08 , Eduardo Oliveira wrote:

> ...
> Even, I have a problem because I can not limit the repeating size  
> because the elements are inside an unbounded size choice element,  
> isn´t it?

Correct.  XSD 1.1 may be helpful to you here (so make sure your vendors
know you would like to see it supported), because it will allow you to
express

>
> Another problem I had is using xs:all inside the xs:group cause an  
> error. Is it not possible?

No, all-groups complicate matters a great deal when they are allowed
inside of other group types.  It's not the occurrence of xsd:all inside
the model group definition that is forbidden, but the use of that
defined all-group inside a sequence.  So what you want may be more like
this:


  <xsd:group name="bcx">
   <xsd:choice>
    <xsd:element ref="my:b" />
    <xsd:element ref="my:c" />
    <xsd:element ref="my:x" />
   </xsd:choice>
  </xsd:group>

  <xsd:complexType name="oliveira">
   <xsd:sequence>
    <xsd:choice minOccurs="0" maxOccurs="unbounded">
     <xsd:group ref="my:bcx"/>
    </xsd:choice>
    <xsd:element ref="my:a" />
    <xsd:choice minOccurs="0" maxOccurs="unbounded">
     <xsd:element ref="my:a" />
     <xsd:group ref="my:bcx"/>
    </xsd:choice>
   </xsd:sequence>
  </xsd:complexType>

I hope this helps.


-- 
C. M. Sperberg-McQueen, W3C XML Activity
http://www.w3.org/People/cmsmcq
http://cmsmcq.com/mib/
http://www.balisage.net/