att.typed

att.typed provides attributes which can be used to classify or subclassify elements in any way. [1.3.1 Attribute Classes]
Moduletei — 1 The TEI Infrastructure
Membersatt.pointing.group [linkGrp joinGrp altGrp] application change quote cit gloss term corr reg add del name rs measureGrp date time ptr ref head note milestone gb pb lb cb bibl biblStruct listBibl relatedItem lg text floatingText div div1 div2 div3 div4 div5 div6 div7 trailer g charProp mapping rhyme spGrp camera pause vocal kinesic incident writing gramGrp colloc re msDesc dim origDate origPlace stamp collection altIdentifier msName explicit filiation finalRubric incipit rubric decoNote seal accMat provenance custEvent surface surfaceGrp zone addSpan damage damageSpan delSpan restore line mod listApp orgName persName surname forename genName nameLink addName roleName placeName bloc country region district settlement offset geogName geogFeat climate event listOrg listEvent listPerson listPlace location org listRelation relationGrp place population state terrain trait nym listNym notatedMusic figure link ab anchor seg join alt s cl phr w m c pc eTree eLeaf ident moduleSpec exemplum altIdent constraintSpec
AttributesAttributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Datatype

<rng:ref name="data.enumerated"/>
data.enumerated
<div type="poetry">
 <head>Night in Tarras</head>
 <lg type="verse">
  <l>At evening tramping on the hot white road</l>
  <l></l>
 </lg>
</div>
Note
The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.
subtypeprovides a sub-categorization of the element, if needed
Status Optional
Datatype

<rng:ref name="data.enumerated"/>
data.enumerated
Note
The subtype attribute may be used to provide any sub-classification for the element, additional to that provided by its type attribute.
Note
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 valList element in the project-specific schema description, as described in 23.3.1.4 Modification of Attribute and Attribute Value Lists .