[tei-council] rowing back on <mixedContent>

[Lou Burnard]

On 04/07/14 18:28, Sebastian Rahtz wrote:
> On 4 Jul 2014, at 17:46, Lou Burnard <lou.burnard at retired.ox.ac.uk> wrote:
>
>> On 04/07/14 17:00, Sebastian Rahtz wrote:
>>> which sort of fudges the issue. I am not sure whether XSD can model
>>> it or not.
>>>
>> My browsing indicates yes and no.
> it’s a confusing business. But so far as I can see this is valid:
>
>   <xs:element name="a">
>      <xs:complexType mixed="true">
>        <xs:choice>
>          <xs:choice minOccurs="1" maxOccurs="unbounded">
>            <xs:element ref="x"/>
>            <xs:element ref="y"/>
>          </xs:choice>
>          <xs:choice minOccurs="2" maxOccurs="unbounded">
>            <xs:element ref="b"/>
>            <xs:element ref="c"/>
>          </xs:choice>
>        </xs:choice>
>      </xs:complexType>

[of course, if you didnt have those pesky @minOccurs values, this would 
just be plain  old mixed content (text|x|y|b|c)*]

In Pure, would we express this as

<content>
<alternate allowText="true">
<alternate minOccurs="1" maxOccurs="unbounded">
<elementRef key="x"/>
<elementRef key="y"/>
</alternate>
<alternate minOccurs="2" maxOccurs="unbounded">
<elementRef key="b"/>
<elementRef key="c"/>
</alternate>
</alternate>

or

<content>
<alternate >
<textNode/>
<alternate minOccurs="1" maxOccurs="unbounded">
<textNode/>
<elementRef key="x"/>
<elementRef key="y"/>
</alternate>
<alternate minOccurs="2" maxOccurs="unbounded">
<textNode/>
<elementRef key="b"/>
<elementRef key="c"/>
</alternate>
</alternate>


?