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

[Lou Burnard]

We had the same discussion with reference to the co-existence of datatype and valList within a single attDef, I think. The conclusion was that the valList was to be interpreted as providing additional constraints to those i,plied by the datatype, and that contradiction (for example a numeric datatype together with valLists that specify non numeric values) wd be a semantic error. in fact eventually i think we decided that the presence of q valList deter,ined the datatype as data.enumerated.  Hence my original question.

  
________________________________________
From: tei-council-bounces at lists.village.Virginia.EDU [tei-council-bounces at lists.village.Virginia.EDU] On Behalf Of Sebastian Rahtz [sebastian.rahtz at oucs.ox.ac.uk]
Sent: 08 September 2009 15:31
To: David Sewell
Cc: TEI Council
Subject: Re: [tei-council] <valList> in <content> or alongside it?

On 8 Sep 2009, at 15:09, David Sewell wrote:

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

what it _means_ is indeed an interesting question. I tend to think
that you use the most specific;
so <content> may say <rng:text/>, but <valList> overrides that and
says exacty what text you can use.
You could also do <valList> as a Schematron constraint, of course

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