Content Model of TEI element

[dasch124]

The problem reported in issue #66 has popped up for us again: With the quite lax definition/polymorphy of the <TEI> element's content model, we run into generating non-deterministic XSD schemas again:

 <xs:element name="TEI">
      <xs:complexType>
         <xs:sequence>
            <xs:element ref="tei:teiHeader"/>
            <xs:choice>
               <xs:sequence>
                  <xs:element maxOccurs="unbounded" ref="tei:model.resource"/>
                  <xs:element minOccurs="0" maxOccurs="unbounded" ref="tei:TEI"/>
               </xs:sequence>
               <xs:element maxOccurs="unbounded" ref="tei:TEI"/>
            </xs:choice>
    ... 
</xs:element>

While I understand the need for great flexibility for TEI All, I wonder whether Lex0 shouldn't strive to enforce a more coherent macro structure across its instances? If not (and if it's important to keep the definition in line with TEI All), then we can easily restrict this on our side.

[laurentromary]

The group thinks there is no need to have a recursive TEI. Still we may want to leave it like that. Vienna has found a work around.