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

[Sebastian Rahtz]

On 31 Aug 2009, at 13:27, Lou Burnard wrote:
>
>
>>  3. accept that we don't support XSD schemas properly
>>
> or DTDs

we accepted that some time ago. The lack of any concept of "any  
element" in DTD and the lack of namespace support means that it'll  
never work.

>
> 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?)

but <content> is supposed to work with any XML schema notation, so I  
hesitate to hard-wire it to RELAX NG
it also means providing the relaxng schema with the XSD, yet another  
file and namespace for the poor people to contend with.

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

nice try, but when you define macro.schemaPattern to be rng:* (as we  
do in P5), you lose again

>
>
>> 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

why not? it would put <elementSpec> and <attDef>  more in sync, which  
can only be good (expecting as I do that we'll want to blur the  
distinction in ODD3).

Sebastian Rahtz
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

Sólo le pido a Dios
que el futuro no me sea indiferente