[tei-council] <valList> in <content> or alongside it?

[Laurent Romary]

hmm, does this not lack... genericity somehow. Before going any  
further, we should have a clear view of what we mean with all these  
constraints...

Le 8 sept. 09 à 16:30, Sebastian Rahtz a écrit :

>
> On 8 Sep 2009, at 15:17, Laurent Romary wrote:
>
>> Just for the pleasure to contradict, I thought <valList> was one
>> possible way of expressing a content model, in its specific (ODD)
>> language. As a result, it should be situated within <content> just as
>> any relaxNg or schematron expression.
>
>
> hmm, you will recall that we just took schematron constraints _out_ of
> <content> into its own sibling element.....
> so what I suggest is that we have <constraintSpec>, <content> and
> <valLlst> all alongside each other
> --
> 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
>