I agree that this is the right way to do it i.e. dont put maxoccurs onto
vallist. What worries me is that multi-valued attribute values are intrinsically
evil, as we have said before. eg 
- xml doesnt constrain or preserve the order of the values so you shouldnt
depend on it
- we have no way of saying whether the values are alterantives or components of
some larger entity -- and use cases for both


In message <4A0C79F8.5090104@oucs.ox.ac.uk> Sebastian Rahtz
<sebastian.rahtz@oucs.ox.ac.uk> writes:
> I want to be able to say
> 
>   <ptr rend="rss rssnoimage"/>
> 
> and have the values checked by the schema.
> 
> I ended up writing this:
> 
> <attDef ident="rend" mode="change">
> 	      <datatype maxOccurs="3"/>
> 	      <valList type="closed" mode="add">
> 		<valItem ident="rss"/>
> 		<valItem ident="rssnoimage"/>
> 		<valItem ident="rssimage"/>
> 		<valItem ident="rssbrief"/>
> 	      </valList>
> 	    </attDef>
> 
> note the <datatype> in parallel with the <valList>.
> 
> Does this make sense? should <valList> in
> fact support maxOccurs and minOccurs as well?
> -- 
> 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@lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council