#501 att.typed overlapps confusingly with many other definitions


att.typed contains @type and @subtype. Many elemtns (and a small number of attribute classes) define @type seperately. In a previous interation, the datatype of @type was standardised to data.enumerated.

I suggest the next step is to add the individual elements to att.typed and move examples and use cases from the local definition of @type to the notes field of the tag definition. The only practical effect of this (other than clearer documentation) would be to add @subtype to many elements that already have @type.

I suggest not touching att.entryLike att.interpLike or att.textCritical for the moment.

I'm happy to work through these.


  • James Cummings

    James Cummings - 2013-04-09
    • Group: --> AMBER
  • James Cummings

    James Cummings - 2013-11-09

    I believe this is better handled by local modifications of the att.typed @type now that we have this mechanism. Closing this ticket for now, partly because this is mentioned in another ticket elsewhere.

  • James Cummings

    James Cummings - 2013-11-09
    • status: open --> closed-accepted
    • Priority: 5 --> 1(low)