[tei-council] description of <constraint>

[Sebastian Rahtz]

things work more or less with the new <constraint> and <constraintList>
elements inside elementSpec and schemaSpec. I have not yet implemented
their use in <attDef>, will do that gradually.


However, the issue I'd like a decision on is about a description.

there are four choices:

  a) do nothing yet. group <constraint>s by implementation language 
inside <constraintList>s,
      that's it

  b) embed constraint description in the language itself, by whatever 
means come naturally.

  c) add <desc>/<gloss>/<equiv> set to <constraint> content model

  d) add <desc>/<gloss>/<equiv> set to <constraintList> content model

(or e) propose a more complex documentation structure)

There may be issues in how to implement it, but if it can be
done, I am inclined to say we should do c) for the June release.
The argument in favour of a) is Laurent's sensible "do
not rush into things" view; but the TEI philosophy of literate
programming is fairly compelling.

I18N of Schematron messages is an area that scares me, but I do not know
what to do about it.

-- 
Sebastian Rahtz      
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431