att.typed

Attributes which can be used to classify or sub-classify features.
Module MEI.shared
Members
abbr, add, addName, altId, anchoredText, annot, app, application, arpeg, arranger, author, avFile, beamSpan, bend, bibl, biblList, bloc, breath, castList, change, composer, corpName, corr, country, cpMark, curve, damage, date, del, desc, dir, district, dynam, editor, ending, event, eventList, expan, expansion, famName, fermata, fig, fing, fingGrp, foreName, genName, geogFeat, geogName, gliss, graphic, hairpin, handList, harm, harpPedal, head, identifier, incip, ineume, itemList, label, lb, lem, lg, librettist, line, lyricist, mapping, mdiv, measure, mordent, nameLink, num, octave, orig, ornam, part, parts, pb, pedal, periodName, persName, pgFoot, pgFoot2, pgHead, pgHead2, phrase, ptr, quote, rdg, ref, region, reh, relatedItem, repository, restore, roleName, score, section, settlement, slur, styleName, surface, symbol, tempo, term, termList, tie, titlePage, trill, tupletSpan, turn, uneume, zone (direct members of att.typed)
Attributes
@subtype(optional)Provide any sub-classification for the element, additional to that given by its type attribute. Value of datatype NMTOKEN. att.typed
@type(optional)Characterizes the element in some sense, using any convenient classification scheme or typology. Value of datatype NMTOKEN. att.typed
Declaration
<attDef ident="type" usage="opt">
<desc>Characterizes the element in some sense, using any convenient classification scheme or typology.</desc>
<datatype maxOccurs="1" minOccurs="1">
<rng:data type="NMTOKEN"/>
</datatype>
</attDef>
<attDef ident="subtype" usage="opt">
<desc>Provide any sub-classification for the element, additional to that given by its type attribute.</desc>
<datatype maxOccurs="1" minOccurs="1">
<rng:data type="NMTOKEN"/>
</datatype>
<constraintSpec ident="When_subtype" scheme="isoschematron">
<constraint>
<sch:rule context="mei:*[@subtype]">
<sch:assert test="@type">An element with a subtype attribute must have a type attribute.</sch:assert>
</sch:rule>
</constraint>
</constraintSpec>
</attDef>
Remarks

When appropriate, values from an established typology should be used. Alternatively, a typology may be defined in the associated MEI header using the classification element. If values are to be taken from a project-specific list, this should be defined using the TEI valList element in a project-specific schema description.

Constraint
An element with a subtype attribute must have a type attribute.
<sch:rule context="mei:*[@subtype]">
<sch:assert test="@type">An element with a subtype attribute must have a type attribute.</sch:assert>
</sch:rule>