<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1 Headings and Trailers]
Modulecore — Elements Available in All TEI Documents
Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.written (@hand)
Member of
model.headLike model.pLike.front
Contained by
core: divGen lg list listBibl
drama: castGroup castList epilogue performance prologue set spGrp
figures: figure table
msdescription: msDesc msFrag msPart
namesdates: climate event listEvent listNym listOrg listPerson listPlace listRelation org place population state terrain trait
textcrit: listApp listWit
textstructure: argument back body div div1 div2 div3 div4 div5 div6 div7 front group postscript
May contain
analysis: c cl interp interpGrp m pc phr s span spanGrp w
certainty: certainty precision respons
core: abbr add address bibl biblStruct binaryObject cb choice cit corr date del desc distinct email emph expan foreign gap gb gloss graphic hi index l label lb lg list listBibl measure measureGrp media mentioned milestone name note num orig pb ptr q quote ref reg rs said sic soCalled stage term time title unclear
dictionaries: lang oRef oVar pRef pVar
drama: camera caption castList move sound tech view
figures: figure formula notatedMusic table
gaiji: g
header: biblFull idno
iso-fs: fLib fs fvLib
linking: alt altGrp anchor join joinGrp link linkGrp seg timeline
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName affiliation bloc climate country district forename genName geo geogFeat geogName listEvent listNym listOrg listPerson listPlace location nameLink offset orgName persName placeName population region roleName settlement state surname terrain trait
spoken: incident kinesic pause shift vocal writing
tagdocs: att classSpec code constraintSpec dataSpec eg egXML elementSpec gi ident listRef macroSpec moduleSpec outputRendition specDesc specGrp specGrpRef specList tag val
textcrit: app listApp listWit witDetail
textstructure: floatingText
transcr: addSpan am damage damageSpan delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space subst substJoin supplied surplus undo
verse: caesura rhyme
Note

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.

Example

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>
Example

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>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration
<rng:element name="head">
 <rng:ref name="att.global.attributes"/>
 <rng:ref name="att.global.rendition.attributes"/>
 <rng:ref name="att.global.linking.attributes"/>
 <rng:ref name="att.global.analytic.attributes"/>
 <rng:ref name="att.global.facs.attributes"/>
 <rng:ref name="att.global.change.attributes"/>
 <rng:ref name="att.global.responsibility.attributes"/>
 <rng:ref name="att.typed.attributes"/>
 <rng:ref name="att.written.attributes"/>
 <rng:zeroOrMore>
  <rng:choice>
   <rng:text/>
   <rng:ref name="lg"/>
   <rng:ref name="model.gLike"/>
   <rng:ref name="model.phrase"/>
   <rng:ref name="model.inter"/>
   <rng:ref name="model.lLike"/>
   <rng:ref name="model.global"/>
  </rng:choice>
 </rng:zeroOrMore>
</rng:element>
element head
{
   att.global.attributes,
   att.global.rendition.attributes,
   att.global.linking.attributes,
   att.global.analytic.attributes,
   att.global.facs.attributes,
   att.global.change.attributes,
   att.global.responsibility.attributes,
   att.typed.attributes,
   att.written.attributes,
   (
      text
    | lg
    | model.gLike
    | model.phrase
    | model.inter
    | model.lLike
    | model.global
   )*
}