Re: XSD - Extensibility and Non-Determinism

Case 1 open extensibility on the extension element in the middle of the
content model.

<xs:sequence>
<xs:element name="A" type="xs:string" />
<xs:element name="B" type="xs:string" />
<xs:element name="extension" type="xs:any" />
 <xs:element name="D" type="xs:string" />
 <xs:element name="E" type="xs:string" />
</xs:sequence>

Open extensibility on the extension element in the middle of the content
model.

Case 2
<xs:complexType name="A1Type">
  <xs:complexContent>
     <xs:extension>
        <xs:sequence>
        <xs:element name="D" type="xs:string" />
        <xs:element name="extension" type="xs:any" />
       </xs:sequence>
     </xs:extension>
  </xs:complexContent>
</xs:complexType>

<xs:complexType name="A2Type">
  <xs:complexContent>
     <xs:extension base="A1Type>
        <xs:sequence>
        <xs:element name="F" type="xs:string" />
        <xs:element name="extension" type="xs:any" />
       </xs:sequence>
     </xs:extension>
  </xs:complexContent>
</xs:complexType>

A2Type extends A1Type but both have open extensibility on the extension
element.

On Sun, Aug 7, 2022 at 7:02 PM C. M. Sperberg-McQueen <
[email protected]> wrote:

>
> Ihe Onwuka <[email protected]> writes:
>
> > If a type that has some form of open extensibility is extended by
> > another type that also has some form of open extensibility would such
> > an extension be non-deterministic.
>
> > If a type has an openly extensible element but it is not placed at the
> > end of the content model declaration does it follow that that type
> > declaration has built-in non-determinism?
>
> I think that in both cases it depends on what you mean by open
> extensibility.  Can you provide a small concrete example?
>
> Michael
>
> --
> C. M. Sperberg-McQueen
> Black Mesa Technologies LLC
> http://blackmesatech.com
>