RE: [relax-ng-comment] Are sequences and interleaves overloaded?

[Jeff Lowery <jlowery@scenicsoft.com>]

Thanks again, for the solution.

Despite the fact that RELAX NG handles my little data model problem just
fine, so you still think there's any merit in "normalizing" content models
so that continguity and order are treated separately? I'm not suggesting
that this be done for RELAX NG, I'm merely just wondering if this was given
consideration by your group and if it was rejected, why?

BTW, small error in the fantasy schema in the prior message:

> <?xml version="1.0" encoding="UTF-8"?>
> <schema
>     xmlns="http://www.w3.org/2001/XMLSchema"
>     xmlns:g="http://www.example.com/g"
>     targetNamespace="http://www.example.com/g"
>     elementFormDefault="qualified"
>
>     <group name="ABC">
>         <unordered contiguous="false">
>             <element name="A" minOccurs="0"
>                maxOccurs="unbounded"/>
>             <element name="B"  minOccurs="0"
>                maxOccurs="unbounded"/>
>             <element name="C" minOccurs="0"
>                maxOccurs="unbounded"/>
>             <any namespace="##other" processContents="lax"/>
>         </unordered>
>     </group>
>
>     <complexType name="foo">
>         <unordered contiguous="true">
>             <ordered contiguous="false">
>                 <element name="x"/>
>                 <element name="y"/>
>                 <element name="z"/>
>             </ordered>
>>>           <!-- maxOccurs="unbounded" unnecessary here: -->
>>>           <group ref="g:ABC"/>   
>         </unordered>
>     </complexType>
>
>     <element name="foos">
>         <complexType>
>             <ordered> <!-- contiguous="true" by default -->
>                 <element name="foo" type="g:foo"
>                     maxOccurs="unbounded"/>
>             </ordered>
>         </complexType>
>     </element>
> </schema>