Menu

#693 allocation of elements to module transcr

AMBER
closed-rejected
None
5(default)
2014-11-19
2014-09-26
No

the module transcr brings in all the things one needs for <facsimile> and <sourceDoc>, which is good. but look at the list of elements:

addSpan am damage damageSpan delSpan ex facsimile fw handNotes handShift line listTranspose metamark mod redo restore retrace sourceDoc space subst substJoin supplied surface surfaceGrp surplus transpose undo zone

Note the presence of (at least) fw, addSpan, delSpan, am, ex, supplied, space; but not (for example) add, del and gap. This just isn't consistent, is it? at least fw, am an ex must surely move to core.

Discussion

  • Lou Burnard

    Lou Burnard - 2014-09-26

    The reason e.g. am and ex are not in the core is because they were considered fairly specialised usages, and we wished to reduce the size of the core. So while they meet the criterion "can appear in almost any document" they don't meet the criterion "likely to be used in almost any kind of encoding". If you really want to perturb this sleeping dog, I'd suggest moving add del and gap out of the core rather.

     
  • Sebastian Rahtz

    Sebastian Rahtz - 2014-09-26

    I can see why we did this, but wish we hadn't. creating a new module with all the editorial things in might be preferable. Disruptive to the poor dogs, I agree.

    I'll just avoid using modules :-}

     
  • James Cummings

    James Cummings - 2014-11-19
    • status: open --> closed-rejected
    • assigned_to: James Cummings
     
  • James Cummings

    James Cummings - 2014-11-19

    Council decided at Raleigh F2F that there is no useful way to change this without module fragmentation which we've postponed until P6.