Some spice: two items:
I want to return to the question of the children of <choice>.
What is not evident from the alphabetical listing of its members:
abbr corr expan orig reg seg sic unclear
is the sets of pairings:
Can someone please explain how <seg> came to be included in content model
of <choice>? Also <unclear>?
I note in passing that <c> can be a child of the <choice> children and
come to my second question. It relates to a statement by Michael...
would be using the type attribute's value, not so much to assign a
taxonomic category as to express a content restraint. And I would tend to
regard that as a precursor of attribute abuse, if not actually already
abusive in itself,
In my opinion such a practice is not yet abusive especially if the
practice is documented in the TEI header. One could of course extend the
tag set to create attributes which indicate the restraints on the content
of the element to which they attributes. Interestingly <seg> has the
possibility of taking a "subtype" attribute. It is conceivable that a
project implement taxonic description on the "type" attribute and mark
indications of content restraint on the "subtype".