12.1.57. <head>
| <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] | |
| Module | core — Specification |
| Attributes |
|
| Member of | |
| Contained by | |
| May contain | core: abbr bibl biblStruct cit date desc email expan graphic list listBibl name note quote ref ruby term title dictionaries: lang figures: figure gaiji: g header: idno linking: seg namesdates: affiliation forename orgName persName persPronouns placeName state surname trait tagdocs: ident transcr: metamark character data |
| 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: |
| Example | 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. |
| Example | The <head> element is also used to mark headings of other units, such as lists: |
| 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 | |


