[tei-council] *Spec content inconsistency

[Syd Bauman]

This corresponds to SF bug report #571, which I gave priority 5
because I still don't konw which is high and which is low. (IIRC,
someone told me at the F2F meeting, but the minutes say "Action on
JC: to investigate the Allura system if possible to make the meanings
of the numbers explicit.".) This should be a "2" or an "8", whichever
is lower.

---------

classSpec, elementSpec, macroSpec, and schemaSpec all start with
  ( model.glossLike | model.descLike )*,

but constraintSpec starts with
  model.descLike*,
  model.glossLike*,

and moduleSpec starts with
  model.glossLike*, model.descLike+, 

Is there a strong reason to constrain the order in
<constraintSpec> but not the others? And I understand why we want
to require at least one <desc> in a <moduleSpec>, but is there a
reason to constrain the order?

One reaction might be to change them all to the
  ( model.glossLike | model.descLike )*,

and then require <desc> in <moduleSpec> but not the others. But
first I think it's worth asking the model.glossLike is in
<constraintSpec> at all? What's it for? They don't need
<altIdent>s or <gloss>s, do they? (Not likely to need an <equiv>,
either, but I suppose it's possible.)