#389 att.typed spec references nonexistent element

Lou Burnard

The specification for att.typed includes the following :
<p>When appropriate, use values from an established typology. Otherwise, define a typology using
the <gi>classification</gi> element of the <gi>encodingDesc</gi> within
the associated TEI header, or as a list within one of the components
of the <gi>encodingDesc</gi> element, or informally as descriptive prose within
the <gi>encodingDesc</gi> element.</p>
As noted on TEI-L (24 mar 2012, McCaskey) there is no such element as <classification>. But this paragraph probably also needs revision to mention the feasibility of defining and enforcing a taxonomy via ODD features such as a project-defined <valList>


  • James Cummings

    James Cummings - 2012-03-25

    I agree that the recommended method is (and should be here) to define the classification typology in the valList for an ODD. The <gi>remarks</gi> section should perhaps point to somewhere like USE.html#MDMDAL as containing more information on how to do this.

  • Lou Burnard

    Lou Burnard - 2012-04-18
    • milestone: --> GREEN
    • assigned_to: nobody --> louburnard
  • Lou Burnard

    Lou Burnard - 2012-04-20

    Made an attempt at rewording the paragraph as follows:

    <p>When appropriate, values from an established typology should be
    used. Alternatively a typology may be defined in the associated
    TEI header. If values are to be taken from a project-specific
    list, this should be defined using the <gi>valList</gi> element in
    the project-specific schema description, as described in <ptr
    target="#MDMDAL"/> .</p>

    Checked this in at rev 10274

  • Lou Burnard

    Lou Burnard - 2012-04-20
    • status: open --> closed-accepted