[tei-council] reconsidering model.glossLike (bugs 3565137)
James Cummings
James.Cummings at it.ox.ac.uk
Sun Sep 23 18:11:02 EDT 2012
Lou,
If I'm understanding correctly, does that mean that the list of
elements with (1) (2) will not have <certainty> as a child, and
those with (1)(3) will lose <gloss>,<equiv>, and <altIdent>?
I don't think many people will have used <gloss> on those
elements, and as long as they retain <desc>, I don't see bad
side-effects from doing this.
Anyone else?
-James
On 23/09/12 22:37, Lou Burnard wrote:
> I started looking at 3565137, and then got cold feet.
>
> Current members of model.glossLike are: model.certLike [certainty
> respons] desc gloss precision equiv altIdent
>
> Seems to me that of these only equiv and altIdent are really "gloss
> like". Equally, model.certLike and precision seem rather inappropriate
> inside *Spec elements.
>
> I fear a fairly major reorganization is needed. Here's my first shot
> at it.
>
> The elements currently containing model.glossLike are : attDef
> category certainty char classSpec constraintSpec elementSpec gap glyph
> graphic incident interp interpGrp join joinGrp kinesic macroSpec
> moduleSpec precision respons schemaSpec space substJoin taxonomy
> valItem and vocal.
>
> The only thing that all these elements actually have in common is that
> they all need a<desc>. Apart from that:
>
> The following need gloss, equiv, altIdent:
> attDef, category, classSpec, constraintSpec, elementSpec,
> macroSpec moduleSpec schemaSpec taxonomy, valItem
>
> The following need precision and model.certLike
> certainty gap precision respons space substJoin
>
> So, cautiously, I am thinking of doing the following:
>
> (1) define (new) model.descLike, with<desc> as its sole member
> (2) redefine model.glossLike with<gloss>,<equiv>, and<altIdent> as
> its members
> (3) Add<precision> to model.certLike
>
> Revise class memberships as follows:
>
> attDef (1) (2)
> category (1) (2)
> certainty (1) (3)
> char (1)
> classSpec (1) (2)
> constraintSpec (1) (2)
> elementSpec (1) (2)
> gap (1) (3)
> glyph (1)
> graphic (1)
> incident (1) (3)
> interp (1) (3)
> interpGrp (1) (3)
> join (1) (3)
> joinGrp (1) (3)
> kinesic (1)
> macroSpec (1) (2)
> moduleSpec (1) (2)
> precision (1) (3)
> respons (1) (3)
> schemaSpec (1) (2)
> space (1) (3)
> substJoin (1) (3)
> taxonomy (1) (2)
> valItem (1) (2)
> vocal (1)
>
> But I think I'll sleep on it first.
>
>
--
Dr James Cummings, researchsupport at it.ox.ac.uk
Research Support, IT Services, University of Oxford
More information about the tei-council
mailing list