[tei-council] Schematron rules

Laurent Romary laurent.romary at loria.fr
Tue Sep 9 10:32:43 EDT 2008


Exactly. And it seems that <content> and <constraint> are just two  
variations of one another (ideally member of a same class)

Le 9 sept. 08 à 12:51, Sebastian Rahtz a écrit :

> John wrote:
>>  It seems it
>> might make sense, conceptually, for <constraint> to be a child of
>> <content>.
>>
> that's a possibility. but since it also has
> to occur in classSpec and attDef and schemaSpec,
> I assumed it was easier to keep it simple.
>
> the other problem is that it would not solve
> one of my problems, viz the inability to
> update/replace/delete _components_
> of <content>
>
> -- 
> Sebastian Rahtz
> Information Manager, Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council



More information about the tei-council mailing list