[tei-council] valList in <content> of <elementSpec>

[Lou Burnard]

Sebastian Rahtz wrote:
> 
> The content model for <content> is this:
> 
>    <rng:zeroOrMore>
>        <rng:choice>
>          <rng:ref name="macro.schemaPattern"/>
>          <rng:ref name="valList"/>
>        </rng:choice>
>      </rng:zeroOrMore>
> 
> 
> where macro.schemaPattern expands to "anything". What upsets the  
> schema processor is that if it meets <valList>, is that matching the  
> "valList" rule or the "anything" rule? RELAX NG does not care, but W3C  
> Schema has to come to a conclusion about it (as DTDs do as well), and  
> it has no way to work out the truth.
> 
> What's to be done? we have three choices:
> 
>   1. stop allowing <valList> as a child of <content> and make it a  
> sibling instead
>   2. remove <content> from tei_all to avoid the situation
i.e. sweep it under the carpet and look the other way? not really a solution

>   3. accept that we don't support XSD schemas properly
> 
or DTDs

Are these really the only options of course. I can think of at least two 
others

4. redefine macro.schemaPattern so that it accepts only relevant 
elements from the rng namespace (is that possible?)

5. just remove the reference to valList, since it will be matched by the 
current macro.schemaPattern anyway


> I think the only acceptable answer here is 1., and I propose that we  
> allow <valList> as a sibling of <content>, in the same way that it is  
> a sibling of <datatype> in <attDef>.
> 

don't like this very much