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

[David Sewell]

What would be the effect of creating an <elementSpec> containing both
<content> and <valList>? Would that mean a content model for the element
of "either (structure defined by <content>) or (value from value list)"?
I can see theoretical use cases for that.

In any case I would vote for extracting <valList> from <content> to
become a child of <elementSpec>.

On Sun, 6 Sep 2009, Sebastian Rahtz wrote:

> Anyone else have fews on this fascinating topic?
> --
> 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
>
>
>
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 801079, Charlottesville, VA 22904-4318 USA
Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903
Email: dsewell at virginia.edu   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/