[tei-council] Wot is wrong with my ODD?

[Martin Holmes]

On 14-06-08 12:17 AM, Sebastian Rahtz wrote:
>
>
> Carved in stone on my iPad
>
>> On 8 Jun 2014, at 00:10, "Lou Burnard"
>> <lou.burnard at retired.ox.ac.uk> wrote:
>>
>> My mistake. You want
>>
>> <elementSpec ident="seg" mode="change"> <content allowText="true">
>> <elementRef key="orgName"/> <elementRef key="persName" />
>> <elementRef key="choice" /> <elementRef key="seg" /> <elementRef
>> key="trait"/> </content> </elementSpec>
>>
>>
>> @allowText has a lot of side effects...
>
> Are you saying that the presence of allowText generates an implicit
> alternate? As it stands, I would suggest what you have above is
> contradictory and impossible to satisfy

I'm quite confused now. What I like about PureODD is that (I thought) it 
was relatively transparent and comprehensible. If this:

<elementSpec ident="seg" mode="change">
        <content allowText="true">
              <elementRef key="orgName" maxOccurs="unbounded" 
minOccurs="0"/>
              <elementRef key="persName" maxOccurs="unbounded" 
minOccurs="0"/>
              <elementRef key="choice" maxOccurs="unbounded" minOccurs="0"/>
              <elementRef key="seg" maxOccurs="unbounded" minOccurs="0"/>
              <elementRef key="trait" maxOccurs="unbounded" minOccurs="0"/>
        </content>
</elementSpec>

is different from this:

<elementSpec ident="seg" mode="change">
     <content allowText="true">
              <elementRef key="orgName"/>
              <elementRef key="persName" />
              <elementRef key="choice" />
              <elementRef key="seg" />
              <elementRef key="trait"/>
        </content>
</elementSpec>

and (especially) if the latter is somehow impossible, then we need to 
revisit it and ultimately document it in much more detail.

Cheers,
Martin

>
> Sebastian
>