The <ab> element may be used at the encoder's discretion to mark any component-level elements in a text for which no other more specific appropriate markup is defined. Unlike paragraphs, <ab> may nest and may use the @type and @subtype attributes.

element ab
{
   tei_att.cmc.attributes,
   attribute rend
   {
      list
      {
         (
            "right"
          | "left"
          | "centre"
          | "indent0"
          | "indent1"
          | "indent2"
          | "indent3"
          | "blockIndent"
          | "hangingIndent1"
          | "hangingIndent2"
          | "hangingIndent3"
          | "blockquote"
         )+
      }
   }?,
   attribute type { "head" | "p" | "url" }?,
   tei_macro.abContent
}

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

element abbr { tei_att.cmc.attributes, tei_macro.phraseSeq }

This element is intended only for cases where no abstract is available in the original source. Any abstract already present in the source document should be encoded as a <div> within the <front>, as it should for a born-digital document.

element abstract { ( tei_model.pLike | tei_model.listLike | listBibl )+ }

In a diplomatic edition attempting to represent an original source, the <add> element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended.

In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of <add> may be appropriate, dependent on the editorial philosophy of the project.

element add
{
   tei_att.cmc.attributes,
   tei_att.placement.attribute.place,
   attribute hand { teidata.pointer }?,
   tei_macro.paraContent
}

An identifying number of some kind must be supplied if known; if it is not known, this should be stated.

element altIdentifier
{
   tei_placeName?,
   tei_country?,
   tei_settlement?,
   tei_institution?,
   tei_repository?,
   tei_collection?,
   tei_idno,
   tei_note?
}

May contain titles and statements of responsibility (author, editor, or other), in any order.

The <analytic> element may only occur within a <biblStruct>, where its use is mandatory for the description of an analytic level bibliographic item.

element analytic
{
   (
      tei_author
    | editor
    | tei_respStmt
    | tei_title
    | tei_model.ptrLike
    | tei_date
    | textLang
    | tei_idno
    | tei_availability
   )*
}

element app
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { teidata.enumerated }?,
   attribute from { teidata.pointer }?,
   attribute to { teidata.pointer }?,
   attribute loc { list { teidata.word+ } }?,
   (
      tei_lem?,
      (
         tei_model.rdgLike
       | tei_model.noteLike
       | tei_witDetail
       | tei_wit
       | tei_rdgGrp
      )*
   )
}

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes @key or @ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.

In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.

Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

element author
{
   attribute xml:id { xsd:ID }?,
   attribute role { list { teidata.enumerated+ } }?,
   attribute key { teidata.text }?,
   attribute ref { list { teidata.pointer+ } }?,
   tei_macro.phraseSeq
}

NB: The value in <authority> will be used as your ‘Contributor‘ name in the browsing facets on Epsilon.

element authority { tei_macro.phraseSeq.limited }

A consistent format should be adopted

element availability
{
   attribute xml:id
   {
      "displayImageRights" | "downloadImageRights" | "metadataRights"
   }?,
   attribute status { "restricted" | "unrestricted" }?,
   ( tei_model.availabilityPart | tei_model.pLike )+
}

Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the <back> and <front> elements are identical.

element back
{
   (
      model.frontPart
    | tei_model.pLike.front
    | tei_model.pLike
    | tei_model.listLike
    | tei_model.global
   )*,
   (
      (
         model.div1Like,
         ( model.frontPart | model.div1Like | tei_model.global )*
      )
    | (
         tei_model.divLike,
         ( model.frontPart | tei_model.divLike | tei_model.global )*
      )
   )?,
   (
      (
         tei_model.divBottomPart,
         ( tei_model.divBottomPart | tei_model.global )*
      )?
   )
}

Contains phrase-level elements, together with any combination of elements from the model.biblPart class

                               <bibl type="provenance">Archives of the Gray Herbarium, Harvard University (121)</bibl>
                           

Although editors will be expected to maintain the information in this element for the time being, this useage is deprated and is expected to be abandoned before the end of 2015 (see the guidelines and tag set documentation on <sourceDesc>.

element bibl
{
   tei_att.canonical.attribute.ref,
   tei_att.cmc.attributes,
   attribute n { teidata.text }?,
   attribute sameAs { teidata.pointer }?,
   attribute cert { teidata.probCert }?,
   attribute resp { list { teidata.pointer+ } }?,
   attribute key { data.pointer }?,
   attribute type { "provenance" | "printedSource" }?,
   attribute key { data.pointer }?,
   (
      text
    | model.gLike
    | tei_model.highlighted
    | tei_model.pPart.data
    | tei_model.pPart.edit
    | tei_model.segLike
    | tei_model.ptrLike
    | tei_model.biblPart
    | tei_model.global
   )*
}

When a single page is being cited, use the @from and @to attributes with an identical value. When no clear endpoint is provided, the @from attribute may be used without @to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff</biblScope>.

It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint.

element biblScope
{
   attribute n
   {
      "01"
    | "02"
    | "03"
    | "04"
    | "05"
    | "06"
    | "07"
    | "08"
    | "09"
    | "10"
    | "11"
    | "12"
    | "13"
    | "14"
    | "15"
    | "16"
    | "17"
    | "18"
    | "19"
    | "20"
    | "21"
    | "22"
    | "23"
    | "24"
    | "25"
    | "26"
    | "27"
    | "28"
    | "29"
    | "30"
   },
   attribute unit { "vol" },
   tei_macro.phraseSeq
}

element biblStruct
{
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   attribute xml:id { xsd:ID }?,
   (
      tei_analytic*,
      ( ( tei_monogr, series* )+ ),
      ( tei_model.noteLike | tei_model.ptrLike | tei_relatedItem | citedRange )*
   )
}

element body
{
   tei_model.global*,
   ( ( tei_model.divTop, ( tei_model.global | tei_model.divTop )* )? ),
   ( ( model.divGenLike, ( tei_model.global | model.divGenLike )* )? ),
   (
      ( ( tei_model.divLike, ( tei_model.global | model.divGenLike )* )+ )
    | ( ( model.div1Like, ( tei_model.global | model.divGenLike )* )+ )
    | (
         ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+ ),
         (
            (
               ( tei_model.divLike, ( tei_model.global | model.divGenLike )* )+
            )
          | ( ( model.div1Like, ( tei_model.global | model.divGenLike )* )+ )
         )?
      )
   ),
   ( ( tei_model.divBottom, tei_model.global* )* )
}

On this element, the global @n attribute indicates the number or other value associated with the column which follows the point of insertion of this <cb> element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column beginnings relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The <cb> element is placed at the head of the column to which it refers.

Markup of an early English dictionary printed in two columns:

      <pb/>
      <cb n="1"/>
      <entryFree><form>Well</form>, <sense>a Pit to hold Spring-Water</sense>:
                <sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner
                    sinks into the Ground, to find out and disappoint the Enemies Mines,
                    or to prepare one</sense>.</entryFree>
      <entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or
                <sense>lie groveling</sense>.</entryFree>
      <!-- remainder of column -->
      <cb n="2"/>
      <entryFree><form>Wey</form>, <sense>the greatest Measure for dry Things,
                    containing five Chaldron</sense>.</entryFree>
      <entryFree><form>Whale</form>, <sense>the greatest of
                    Sea-Fishes</sense>.</entryFree>
    

element cb { tei_att.cmc.attributes, empty }

element cell
{
   attribute rend
   {
      list
      {
         (
            "right"
          | "left"
          | "centre"
          | "borderAll"
          | "borderBottom"
          | "borderLeft"
          | "borderRight"
          | "borderSides"
          | "borderTop"
          | "vAlignTop"
          | "vAlignMiddle"
          | "vAlignBottom"
          | "width05"
          | "width10"
          | "width15"
          | "width20"
          | "width25"
          | "width30"
          | "width33"
          | "width35"
          | "width40"
          | "width45"
          | "width50"
          | "width55"
          | "width60"
          | "width65"
          | "width66"
          | "width70"
          | "width75"
          | "width80"
          | "width85"
          | "width90"
          | "width95"
          | "width100"
         )+
      }
   }?,
   attribute rows { teidata.count }?,
   attribute cols { teidata.count }?,
   tei_macro.specialPara
}

The @who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent first. The @status attribute may be used to indicate the status of a document following the change documented.

You should create a new <change> element with required @when attribute giving the date, and content giving a natural-language account of each significant revision. The person who made it goes in a <name> element with an @xml:id value that will be assigned by the senior editors when someone starts work, but is normally based on that person's first initial plus her or his surname, e.g. ‘mhawkins’, ‘lsmith’ or ‘sevans’.

Proofreading a file counts as a <change> even if the proofreader has not in fact made any changes to it since it records that the files has undergone a particular part of our editorial process.

If the @xml:id value of any of the people working on the document has previously been declared, subsequent occurrences of her or his <name> take a @sameAs value of # followed by the relevant string.

                               <change when="2015-10-02" status="draft">Transcribed by <name xml:id="mjhawkins">Michael Hawkins</name></change>
                               <change when="2015-10-12" status="proofed">Proofed by <name xml:id="lsmith">Liz Smith</name></change>
                               <change when="2015-10-15" status="released">Proofed by <name sameAs="#lsmith">Liz Smith</name></change>
                           

element change
{
   attribute rend { list { teidata.word+ } }?,
   attribute when { teidata.temporal.w3c }?,
   attribute status
   {
      "approved"
    | "candidate"
    | "cleared"
    | "deprecated"
    | "draft"
    | "embargoed"
    | "expired"
    | "frozen"
    | "galley"
    | "proposed"
    | "published"
    | "recommendation"
    | "submitted"
    | "unfinished"
    | "withdrawn"
    | teidata.enumerated
   }?,
   attribute type { "footnotes" | "letter" | "translation" }?,
   tei_macro.specialPara
}

Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

Note also that <choice> elements may self-nest.

Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 13.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.

      <p>Lastly, That, upon his solemn oath to observe all the above
                articles, the said man-mountain shall have a daily allowance of
                meat and drink sufficient for the support of <choice><sic>1724</sic><corr>1728</corr></choice> of our subjects,
                with free access to our royal person, and other marks of our
                <choice><orig>favour</orig><reg>favor</reg></choice>.</p>
    

element choice
{
   tei_att.cmc.attributes,
   ( tei_model.choicePart | tei_choice ),
   ( tei_model.choicePart | tei_choice ),
   ( tei_model.choicePart | tei_choice )*
}

element closer
{
   tei_att.cmc.attributes,
   (
      text
    | model.gLike
    | byline
    | tei_signed
    | dateline
    | tei_salute
    | tei_model.phrase
    | tei_model.global
   )*
}

element collection { tei_macro.phraseSeq.limited }

If all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone:

I don't know,
      Juan. It's so far in the past now — how <corr>can we</corr> prove
      or disprove anyone's theories?

It is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading:

I don't know, Juan. It's so far in the past now —
      how <choice><sic>we can</sic><corr>can we</corr></choice> prove or
      disprove anyone's theories?

element corr { tei_att.cmc.attributes, tei_macro.paraContent }

Every record must have one /@type='sent'.

element correspAction
{
   attribute type { "sent" | "received" },
   attribute subtype { teidata.enumerated }?,
   ( tei_model.correspActionPart+ | tei_model.pLike+ )
}

element correspDesc { tei_model.correspDescPart+ | tei_model.pLike+ }

The recommended source for codes to represent coded country names is ISO 3166.

element country { tei_att.cmc.attributes, tei_macro.phraseSeq }

Pay careful attention when entering values into @notBefore and/or @notAfter since they will sometimes differ from the natural language date by +/- one day when the natural language form of the date employs exclusive reckoning whereas the TEI attributes @notBefore and @notAfter employ inclusive reckoning. Exclusive reckonings of dates, for example, are 'after 6 July 1870' (i.e. the earliest date it could have been written is 5 July 1870) or 'before 6 July 1870' (the latest date it could have been written is 5 July 1870). In both cases, 6 July 1870 is not a valid date that the document could have been written. Inclusive reckonings include the date mentioned. Therefore, if you say something was written @notBefore ‘06-07-1870’, you are saying that the document was written on 6 July 1870 or later. Similarly, notAfter ‘06-07-1870’ means that the document was written on or before 6 July 1870. The key when coding date ranges is to carefully consider what the earliest and latest possible date the letter could have been written on and to use those values in @notBefore and @notAfter.

For more information on coding dates, see Appendix I: Correspondence Dates.

<date> also appears within <publicationStmt>. There, all that is required is to put the publication year of the Darwin volume into @when.

All Julian dates should be converted to their Gregorian values before placing them into @when, @notBefore, or @notAfter.

This example means ‘either 1 or 2 February 1861’.

                               <date when="1861-02-01" xml:id="date1" exclude="#date2"/>
                               <date when="1861-02-02" xml:id="date2" exclude="#date1"/>
                           

element date
{
   tei_att.cmc.attributes,
   attribute xml:id { xsd:ID }?,
   attribute exclude { list { teidata.pointer+ } }?,
   attribute when { teidata.temporal.w3c }?,
   attribute notBefore { teidata.temporal.w3c }?,
   attribute notAfter { teidata.temporal.w3c }?,
   ( text | model.gLike | tei_model.phrase | tei_model.global )*
}

This element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.

The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the <gap> tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the <gap> element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way.

Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 22. Certainty, Precision, and Responsibility).

There is a clear distinction in the TEI between <del> and <surplus> on the one hand and <gap> or <unclear> on the other. <del> indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. <gap> or <unclear>, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 12.3.1.7. Text Omitted from or Supplied in the Transcription and 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription.

element del
{
   tei_att.cmc.attributes,
   attribute type { teidata.enumerated }?,
   tei_macro.paraContent
}

element div
{
   tei_att.placement.attributes,
   attribute xml:id { xsd:ID }?,
   attribute n { teidata.text }?,
   attribute type
   {
      "annotations"
    | "cdnotes"
    | "enclosure"
    | "footnotes"
    | "letter"
    | "text"
    | "tnotes"
    | "transcription"
    | "translation"
   }?,
   attribute subtype { "letter" | "other" | "translation" }?,
   attribute hand { teidata.pointer }?,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.divLike | model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+ ),
                  (
                     (
                        ( tei_model.divLike | model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

element edition { tei_att.global.attributes, tei_macro.phraseSeq }

element editionStmt
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | ( tei_edition, tei_model.respLike* ) )
}

A declaration of editorial principles and practices that is visible to the reader.

NB: The contents of this tag appear underneath the letter transcription in Epsilon.

element editorialDecl { ( tei_model.pLike | model.editorialDeclPart )+ }

element encodingDesc { ( tei_model.encodingDescPart | tei_model.pLike )+ }

element ex { tei_macro.xtext }

The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

element expan { tei_att.cmc.attributes, tei_macro.phraseSeq }

The <measure> element may be used to supply normalized or machine tractable versions of the size or sizes concerned.

      <extent>
        <measure unit="MiB" quantity="4.2">About four megabytes</measure>
        <measure unit="pages" quantity="245">245 pages of source
material</measure>
      </extent>
    

element extent { tei_att.global.attributes, tei_macro.phraseSeq }

element facsimile
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   (
      front?,
      (
         ( tei_model.graphicLike | tei_surface | surfaceGrp )+
       | tei_facsimile+
      ),
      tei_back?
   )
}

element figure
{
   tei_att.cmc.attributes,
   attribute rend
   {
      list
      {
         (
            "floatRight"
          | "floatLeft"
          | "blockCentred"
          | "inline"
          | "width05"
          | "width10"
          | "width15"
          | "width20"
          | "width25"
          | "width30"
          | "width33"
          | "width35"
          | "width40"
          | "width45"
          | "width50"
          | "width55"
          | "width60"
          | "width65"
          | "width66"
          | "width70"
          | "width75"
          | "width80"
          | "width85"
          | "width90"
          | "width95"
          | "width100"
         )+
      }
   }?,
   (
      tei_model.headLike
    | tei_model.common
    | figDesc
    | tei_model.graphicLike
    | tei_model.global
    | tei_model.divBottom
   )*
}

The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

element fileDesc
{
   (
      tei_titleStmt,
      tei_editionStmt?,
      tei_extent?,
      tei_publicationStmt,
      tei_seriesStmt*,
      tei_notesStmt?
   ),
   tei_sourceDesc+
}

The global @xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.

This element is intended for use only where no other element is available to mark the phrase or words concerned. The global @xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element.

The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.

element foreign
{
   tei_att.cmc.attributes,
   attribute xml:lang { teidata.language }?,
   tei_macro.phraseSeq
}

element forename
{
   tei_att.cmc.attributes,
   attribute full { "yes" | "abb" | "init" }?,
   tei_macro.phraseSeq
}

element formula { tei_att.cmc.attributes, mathml.math }

Funders provide financial support for a project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support and authority.

element funder { tei_macro.phraseSeq.limited }

The <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion.

element gap
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.dimensions.attributes,
   tei_att.editLike.attributes,
   tei_att.timed.attributes,
   attribute reason
   {
      list
      {
         (
            "cancelled"
          | "deleted"
          | "editorial"
          | "illegible"
          | "inaudible"
          | "irrelevant"
          | "sampling"
          | teidata.enumerated
         )+
      }
   }?,
   attribute agent { teidata.enumerated }?,
   ( model.descLike | model.certLike )*
}

The block alignment and size of the image within the transcribed text are indicated with its parent <figure>.

element graphic
{
   tei_att.cmc.attributes,
   attribute width { teidata.outputMeasurement }?,
   attribute height { teidata.outputMeasurement }?,
   attribute url { teidata.pointer },
   model.descLike*
}

element handNotes { handNote+ }

The <handShift> element may be used either to denote a shift in the document hand (as from one scribe to another, on one writing style to another). Or, it may indicate a shift within a document hand, as a change of writing style, character or ink. Like other milestone elements, it should appear at the point of transition from some other state to the state which it describes.

element handShift
{
   attribute scribe { teidata.name }?,
   attribute new { teidata.pointer }?,
   empty
}

The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section.

The most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:

      <div1 n="I" type="book">
        <head>In the name of Christ here begins the first book of the ecclesiastical history of
          Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
        <div2 type="section">
          <head>In the name of Christ here begins Book I of the history.</head>
          <p>Proposing as I do ...</p>
          <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve
            years passed.</p>
          <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six
            years from the beginning of the world down to the death of Saint Martin.</trailer>
        </div2>
      </div1>
    

When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the @place attribute.

      <div type="subsection">
        <head place="margin">Secunda conclusio</head>
        <p>
          <lb n="1251"/><hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied></hi>
          <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium
          [...]
        </p>
      </div>
    

The <head> element is also used to mark headings of other units, such as lists:

With a few exceptions, connectives are equally
      useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted"><head>Connectives</head><item>above</item><item>accordingly</item><item>across from</item><item>adjacent to</item><item>again</item><item><!-- ... --></item></list>
      

element head
{
   tei_att.cmc.attributes,
   attribute rend { list { ( "right" | "left" | "centre" )+ } }?,
   (
      text
    | tei_lg
    | model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.lLike
    | tei_model.global
   )*
}