TEI Tite

A recommendation for off-site text encoding

Appendix C Acknowledgments

Previous Appendix B Formal specification

Home

The TEI Tite is simply a synthesis of work done at the

University of Michigan Digital Library Production Service,

University of Virginia Digital Library Production Service,

and the California Digital Library

and represented in their documents

Minimum standards for text capture,

Text Encoding Guidelines for Keyboarding Vendors,

and CDL TEI Base Encoding Guidelines,

respectively. Many thanks to the institutions and individuals responsible for sharing their experience and expertise for the benefit of the TEI community at large.

Also, thank you to members of the TEI Special Interest Group on Libraries who provided very valuable corrections and suggestions.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

TEI Tite

A recommendation for off-site text encoding

5. Block-level Features

Table of contents

5.1. Block Quotations

5.2. Figures

5.3. Tables and Lists

5.4. Notes

5.5. divWrapper Elements

5.6. Uncertain Blocks

Previous 4. Types of Text

Next 6. Phrase-level Features

Home

TEI: Block Quotations⚓︎5.1. Block Quotations

Use the q element to encode block quotations. A block quotation is indicated by its being set off from surrounding text either with extra line-spacing or margins or with a different typeface. If the quotation is of an entire text, use the floatingText element and its children inside the q element:

<div1 type="intro">
 <p>
<!-- ... -->
 </p>
 <q>
  <floatingText>
   <body>
    <lg type="poem">
<!-- poem -->
    </lg>
   </body>
  </floatingText>
 </q>
 <p>
<!-- ... -->
 </p>
</div1>

⚓︎

If present, transcribe all quotation marks or other delimiters inside the q element.

Previous 5.1. Block Quotations

Next 5.3. Tables and Lists

Home

TEI: Figures⚓︎5.2. Figures

Use the figure element to encode figures. If a figure has a heading or caption, encode it with the head element. If there is associated text, simply use a p to encode it.

Previous 5.2. Figures

Next 5.4. Notes

Home

TEI: Tables and Lists⚓︎5.3. Tables and Lists

Tables and lists are encoded as in the TEI Guidelines, but note the following.

If a cell in a table is a heading or a label, set the role attribute to label; if the cell contains data, there is no need to use role: data is the default. If a cell or row spans more than one column or row, use the rows or cols attributes set to the number of columns or rows that it spans.

If unsure about whether a structure is best encoded as a list or table, record it as a table only if it would not be properly understood without tabular layout.

Lists should be encoded as either sequences of <items> or label-item pairs. When items in the list contain a label, as in a gloss list, be sure to use the latter form.

Previous 5.3. Tables and Lists

Next 5.5. divWrapper Elements

Home

TEI: Notes⚓︎5.4. Notes

Both the reference to the note in the running text and the note itself must be encoded. Use ptr or ref to encode the reference. If there is no reference in the text (often the case for marginal notes), supply a ptr element in a reasonable place in the text running beside the note. If there is a reference (number, symbol, etc.), use the ref element and include the reference text as the content. In both cases, a target attribute must be supplied which contains the xml:id value of the associated note.

When encoding the note itself with the note element, the xml:id and place attributes must be supplied. See the TEI documentation for acceptable values for place; the most common will be foot, end, margin-left (-right, -top, -bot).

Transcribe the note directly after it is referenced in the document. In the case of notes without explicit reference (pointed to with ptr), set the anchored attribute to false.

Previous 5.4. Notes

Next 5.6. Uncertain Blocks

Home

TEI: divWrapper Elements⚓︎5.5. ‘divWrapper’ Elements

Elements that can appear at the beginning and end of structural divisions, such as argument, epigraph, and opener, are called ‘divWrapper’ elements in the TEI class system. An argument is a summary of what is to come; be sure to distinguish this from a heading, which is a title for the division. If an epigraph comes with bibliographic or simple citation material, encode this as well. For example:

<epigraph>
 <cit>
  <q>"I have sworn upon the altar of God eternal hostility against every form of tyranny over
     the mind of man."</q>
  <bibl>
   <author>Thomas Jefferson.</author>
  </bibl>
 </cit>
</epigraph>

⚓︎

Previous 5.5. divWrapper Elements

Home

TEI: Uncertain Blocks⚓︎5.6. Uncertain Blocks

In rare cases where the logical identity of a block-level element is hard to discern, use the TEI element ab (anonymous block) instead of applying a p or <div> element. In these cases, be sure to document this decision in accompanying notes. Applying this element should be viewed as a last resort.

The gap element should be used when for some reason the document being transcribed contains illegible text (smudged, torn, missing, etc.) or something outside the scope of transcription for a given project: characters in an unsupported character set, for instance. gap indicates that something is omitted. When using gap, set the reason attribute to an appropriate value. (See <unclear> below.)

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ab> (anonymous block)

These search results reproduce every example of the use of <ab> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <ab> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <abbr> (abbreviation)

These search results reproduce every example of the use of <abbr> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <abbr> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <add> (addition)

These search results reproduce every example of the use of <add> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <add> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <addrLine> (address line)

These search results reproduce every example of the use of <addrLine> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <addrLine> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <address> (address)

These search results reproduce every example of the use of <address> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <address> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <argument> (argument)

These search results reproduce every example of the use of <argument> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <argument> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <author> (author)

These search results reproduce every example of the use of <author> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <author> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

5. Block-level Features

5. Block-level Features

5.5. ‘divWrapper’ Elements

<epigraph>
 <cit>
  <q>"I have sworn upon the altar of God eternal hostility against every form of tyranny over
     the mind of man."</q>
  <bibl>
   <author>Thomas Jefferson.</author>
  </bibl>
 </cit>
</epigraph>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <b>

These search results reproduce every example of the use of <b> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <b> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <back> (back matter)

These search results reproduce every example of the use of <back> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <back> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Global Text Structure

3. Global Text Structure

3.1. TEI Tite text structure

<text xml:id="unique-identifier">
 <front>
<!-- front matter -->
 </front>
 <body>
<!-- body of text -->
 </body>
 <back>
<!-- back matter -->
 </back>
</text>

3.2. Groups of Texts

<text>
 <front>
<!-- front matter for the group -->
 </front>
 <group>
  <text>
   <front>
<!-- front matter of first text -->
   </front>
   <body>
<!-- body of first text -->
   </body>
   <back>
<!-- back matter of first text -->
   </back>
  </text>
  <text>
   <front>
<!-- front matter of second text -->
   </front>
   <body>
<!-- body of second text -->
   </body>
   <back>
<!-- back matter of second text -->
   </back>
  </text>
<!-- more texts or groups of texts here -->
 </group>
 <back>
<!-- back matter for the group -->
 </back>
</text>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <bibl> (bibliographic citation)

These search results reproduce every example of the use of <bibl> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <bibl> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

5. Block-level Features

5. Block-level Features

5.5. ‘divWrapper’ Elements

<epigraph>
 <cit>
  <q>"I have sworn upon the altar of God eternal hostility against every form of tyranny over
     the mind of man."</q>
  <bibl>
   <author>Thomas Jefferson.</author>
  </bibl>
 </cit>
</epigraph>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <body> (text body)

These search results reproduce every example of the use of <body> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <body> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Global Text Structure

5. Block-level Features

3. Global Text Structure

3.1. TEI Tite text structure

<text xml:id="unique-identifier">
 <front>
<!-- front matter -->
 </front>
 <body>
<!-- body of text -->
 </body>
 <back>
<!-- back matter -->
 </back>
</text>

3.2. Groups of Texts

<text>
 <front>
<!-- front matter for the group -->
 </front>
 <group>
  <text>
   <front>
<!-- front matter of first text -->
   </front>
   <body>
<!-- body of first text -->
   </body>
   <back>
<!-- back matter of first text -->
   </back>
  </text>
  <text>
   <front>
<!-- front matter of second text -->
   </front>
   <body>
<!-- body of second text -->
   </body>
   <back>
<!-- back matter of second text -->
   </back>
  </text>
<!-- more texts or groups of texts here -->
 </group>
 <back>
<!-- back matter for the group -->
 </back>
</text>

5. Block-level Features

5.1. Block Quotations

<div1 type="intro">
 <p>
<!-- ... -->
 </p>
 <q>
  <floatingText>
   <body>
    <lg type="poem">
<!-- poem -->
    </lg>
   </body>
  </floatingText>
 </q>
 <p>
<!-- ... -->
 </p>
</div1>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <byline> (byline)

These search results reproduce every example of the use of <byline> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <byline> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <cb> (column beginning)

These search results reproduce every example of the use of <cb> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <cb> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <cell> (cell)

These search results reproduce every example of the use of <cell> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <cell> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <cit> (cited quotation)

These search results reproduce every example of the use of <cit> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <cit> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

5. Block-level Features

5. Block-level Features

5.5. ‘divWrapper’ Elements

<epigraph>
 <cit>
  <q>"I have sworn upon the altar of God eternal hostility against every form of tyranny over
     the mind of man."</q>
  <bibl>
   <author>Thomas Jefferson.</author>
  </bibl>
 </cit>
</epigraph>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <closer> (closer)

These search results reproduce every example of the use of <closer> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <closer> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <colShift> (column shift)

These search results reproduce every example of the use of <colShift> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <colShift> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <date> (date)

These search results reproduce every example of the use of <date> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <date> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <dateline> (dateline)

These search results reproduce every example of the use of <dateline> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <dateline> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <del> (deletion)

These search results reproduce every example of the use of <del> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <del> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <desc> (description)

These search results reproduce every example of the use of <desc> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <desc> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <div1> (level-1 text division)

These search results reproduce every example of the use of <div1> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <div1> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Global Text Structure

5. Block-level Features

3. Global Text Structure

3.3. Structural Divisions

<div1 n="III" type="part">
 <head>III: It Awakes</head>
<!-- ... -->
</div1>

5. Block-level Features

5.1. Block Quotations

<div1 type="intro">
 <p>
<!-- ... -->
 </p>
 <q>
  <floatingText>
   <body>
    <lg type="poem">
<!-- poem -->
    </lg>
   </body>
  </floatingText>
 </q>
 <p>
<!-- ... -->
 </p>
</div1>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <div2> (level-2 text division)

These search results reproduce every example of the use of <div2> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <div2> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <div3> (level-3 text division)

These search results reproduce every example of the use of <div3> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <div3> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <div4> (level-4 text division)

These search results reproduce every example of the use of <div4> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <div4> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <div5> (level-5 text division)

These search results reproduce every example of the use of <div5> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <div5> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <div6> (level-6 text division)

These search results reproduce every example of the use of <div6> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <div6> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <div7> (level-7 text division)

These search results reproduce every example of the use of <div7> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <div7> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <docAuthor> (document author)

These search results reproduce every example of the use of <docAuthor> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <docAuthor> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <docDate> (document date)

These search results reproduce every example of the use of <docDate> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <docDate> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <docEdition> (document edition)

These search results reproduce every example of the use of <docEdition> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <docEdition> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <docImprint> (document imprint)

These search results reproduce every example of the use of <docImprint> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <docImprint> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <docTitle> (document title)

These search results reproduce every example of the use of <docTitle> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <docTitle> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <editor>

These search results reproduce every example of the use of <editor> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <editor> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <email> (electronic mail address)

These search results reproduce every example of the use of <email> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <email> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <epigraph> (epigraph)

These search results reproduce every example of the use of <epigraph> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <epigraph> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

5. Block-level Features

5. Block-level Features

5.5. ‘divWrapper’ Elements

<epigraph>
 <cit>
  <q>"I have sworn upon the altar of God eternal hostility against every form of tyranny over
     the mind of man."</q>
  <bibl>
   <author>Thomas Jefferson.</author>
  </bibl>
 </cit>
</epigraph>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <figure> (figure)

These search results reproduce every example of the use of <figure> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <figure> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <floatingText> (floating text)

These search results reproduce every example of the use of <floatingText> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <floatingText> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

5. Block-level Features

5. Block-level Features

5.1. Block Quotations

<div1 type="intro">
 <p>
<!-- ... -->
 </p>
 <q>
  <floatingText>
   <body>
    <lg type="poem">
<!-- poem -->
    </lg>
   </body>
  </floatingText>
 </q>
 <p>
<!-- ... -->
 </p>
</div1>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <foreign> (foreign)

These search results reproduce every example of the use of <foreign> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <foreign> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <formula> (formula)

These search results reproduce every example of the use of <formula> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <formula> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <front> (front matter)

These search results reproduce every example of the use of <front> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <front> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Global Text Structure

3. Global Text Structure

3.1. TEI Tite text structure

<text xml:id="unique-identifier">
 <front>
<!-- front matter -->
 </front>
 <body>
<!-- body of text -->
 </body>
 <back>
<!-- back matter -->
 </back>
</text>

3.2. Groups of Texts

<text>
 <front>
<!-- front matter for the group -->
 </front>
 <group>
  <text>
   <front>
<!-- front matter of first text -->
   </front>
   <body>
<!-- body of first text -->
   </body>
   <back>
<!-- back matter of first text -->
   </back>
  </text>
  <text>
   <front>
<!-- front matter of second text -->
   </front>
   <body>
<!-- body of second text -->
   </body>
   <back>
<!-- back matter of second text -->
   </back>
  </text>
<!-- more texts or groups of texts here -->
 </group>
 <back>
<!-- back matter for the group -->
 </back>
</text>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <g> (character or glyph)

These search results reproduce every example of the use of <g> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <g> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <gap> (gap)

These search results reproduce every example of the use of <gap> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <gap> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <graphic> (graphic)

These search results reproduce every example of the use of <graphic> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <graphic> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <group> (group)

These search results reproduce every example of the use of <group> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <group> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Global Text Structure

3. Global Text Structure

3.2. Groups of Texts

<text>
 <front>
<!-- front matter for the group -->
 </front>
 <group>
  <text>
   <front>
<!-- front matter of first text -->
   </front>
   <body>
<!-- body of first text -->
   </body>
   <back>
<!-- back matter of first text -->
   </back>
  </text>
  <text>
   <front>
<!-- front matter of second text -->
   </front>
   <body>
<!-- body of second text -->
   </body>
   <back>
<!-- back matter of second text -->
   </back>
  </text>
<!-- more texts or groups of texts here -->
 </group>
 <back>
<!-- back matter for the group -->
 </back>
</text>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <handShift> (handwriting shift)

These search results reproduce every example of the use of <handShift> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <handShift> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <head> (heading)

These search results reproduce every example of the use of <head> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <head> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Global Text Structure

3. Global Text Structure

3.3. Structural Divisions

<div1 n="III" type="part">
 <head>III: It Awakes</head>
<!-- ... -->
</div1>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <hi> (highlighted)

These search results reproduce every example of the use of <hi> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <hi> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <i>

These search results reproduce every example of the use of <i> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <i> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <item> (item)

These search results reproduce every example of the use of <item> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <item> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <l> (verse line)

These search results reproduce every example of the use of <l> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <l> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Types of Text

4. Types of Text

4.2. Verse

<lg type="stanza">
 <l>AS virtuous men pass mildly away,</l>
 <l rend="indent(1)">And whisper to their souls to<lb/> go,</l>
 <l>Whilst some of their sad friends<lb/> do say,</l>
 <l rend="indent(1)">"Now his breath goes," and<lb/> some say, "No."</l>
</lg>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <label> (label)

These search results reproduce every example of the use of <label> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <label> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <lb> (line beginning)

These search results reproduce every example of the use of <lb> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <lb> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Types of Text

4. Types of Text

4.2. Verse

<lg type="stanza">
 <l>AS virtuous men pass mildly away,</l>
 <l rend="indent(1)">And whisper to their souls to<lb/> go,</l>
 <l>Whilst some of their sad friends<lb/> do say,</l>
 <l rend="indent(1)">"Now his breath goes," and<lb/> some say, "No."</l>
</lg>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <lg> (line group)

These search results reproduce every example of the use of <lg> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <lg> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

4. Types of Text

5. Block-level Features

4. Types of Text

4.2. Verse

<lg type="stanza">
 <l>AS virtuous men pass mildly away,</l>
 <l rend="indent(1)">And whisper to their souls to<lb/> go,</l>
 <l>Whilst some of their sad friends<lb/> do say,</l>
 <l rend="indent(1)">"Now his breath goes," and<lb/> some say, "No."</l>
</lg>

5. Block-level Features

5.1. Block Quotations

<div1 type="intro">
 <p>
<!-- ... -->
 </p>
 <q>
  <floatingText>
   <body>
    <lg type="poem">
<!-- poem -->
    </lg>
   </body>
  </floatingText>
 </q>
 <p>
<!-- ... -->
 </p>
</div1>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <list> (list)

These search results reproduce every example of the use of <list> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <list> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <listBibl> (citation list)

These search results reproduce every example of the use of <listBibl> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <listBibl> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <milestone> (milestone)

These search results reproduce every example of the use of <milestone> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <milestone> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <name> (name, proper noun)

These search results reproduce every example of the use of <name> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <name> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <note> (note)

These search results reproduce every example of the use of <note> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <note> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <num> (number)

These search results reproduce every example of the use of <num> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <num> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <opener> (opener)

These search results reproduce every example of the use of <opener> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <opener> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ornament>

These search results reproduce every example of the use of <ornament> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <ornament> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <p> (paragraph)

These search results reproduce every example of the use of <p> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <p> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

5. Block-level Features

5. Block-level Features

5.1. Block Quotations

<div1 type="intro">
 <p>
<!-- ... -->
 </p>
 <q>
  <floatingText>
   <body>
    <lg type="poem">
<!-- poem -->
    </lg>
   </body>
  </floatingText>
 </q>
 <p>
<!-- ... -->
 </p>
</div1>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <pb> (page beginning)

These search results reproduce every example of the use of <pb> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <pb> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <postscript>

These search results reproduce every example of the use of <postscript> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <postscript> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ptr> (pointer)

These search results reproduce every example of the use of <ptr> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <ptr> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <pubPlace> (publication place)

These search results reproduce every example of the use of <pubPlace> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <pubPlace> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <publisher> (publisher)

These search results reproduce every example of the use of <publisher> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <publisher> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <q> (quoted)

These search results reproduce every example of the use of <q> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <q> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

5. Block-level Features

5. Block-level Features

5.1. Block Quotations

<div1 type="intro">
 <p>
<!-- ... -->
 </p>
 <q>
  <floatingText>
   <body>
    <lg type="poem">
<!-- poem -->
    </lg>
   </body>
  </floatingText>
 </q>
 <p>
<!-- ... -->
 </p>
</div1>

5.5. ‘divWrapper’ Elements

<epigraph>
 <cit>
  <q>"I have sworn upon the altar of God eternal hostility against every form of tyranny over
     the mind of man."</q>
  <bibl>
   <author>Thomas Jefferson.</author>
  </bibl>
 </cit>
</epigraph>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ref> (reference)

These search results reproduce every example of the use of <ref> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <ref> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <resp> (responsibility)

These search results reproduce every example of the use of <resp> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <resp> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <respStmt> (statement of responsibility)

These search results reproduce every example of the use of <respStmt> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <respStmt> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <row> (row)

These search results reproduce every example of the use of <row> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <row> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <salute> (salutation)

These search results reproduce every example of the use of <salute> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <salute> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <seg> (arbitrary segment)

These search results reproduce every example of the use of <seg> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <seg> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <signed> (signature)

These search results reproduce every example of the use of <signed> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <signed> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <smcap>

These search results reproduce every example of the use of <smcap> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <smcap> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <sp> (speech)

These search results reproduce every example of the use of <sp> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <sp> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <speaker>

These search results reproduce every example of the use of <speaker> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <speaker> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <stage> (stage direction)

These search results reproduce every example of the use of <stage> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <stage> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <sub>

These search results reproduce every example of the use of <sub> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <sub> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <sup>

These search results reproduce every example of the use of <sup> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <sup> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <table> (table)

These search results reproduce every example of the use of <table> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <table> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <text> (text)

These search results reproduce every example of the use of <text> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <text> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

3. Global Text Structure

3. Global Text Structure

3.1. TEI Tite text structure

<text xml:id="unique-identifier">
 <front>
<!-- front matter -->
 </front>
 <body>
<!-- body of text -->
 </body>
 <back>
<!-- back matter -->
 </back>
</text>

3.2. Groups of Texts

<text>
 <front>
<!-- front matter for the group -->
 </front>
 <group>
  <text>
   <front>
<!-- front matter of first text -->
   </front>
   <body>
<!-- body of first text -->
   </body>
   <back>
<!-- back matter of first text -->
   </back>
  </text>
  <text>
   <front>
<!-- front matter of second text -->
   </front>
   <body>
<!-- body of second text -->
   </body>
   <back>
<!-- back matter of second text -->
   </back>
  </text>
<!-- more texts or groups of texts here -->
 </group>
 <back>
<!-- back matter for the group -->
 </back>
</text>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <time> (time)

These search results reproduce every example of the use of <time> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <time> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <title> (title)

These search results reproduce every example of the use of <title> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <title> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <titlePage> (title page)

These search results reproduce every example of the use of <titlePage> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <titlePage> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <titlePart> (title part)

These search results reproduce every example of the use of <titlePart> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <titlePart> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <trailer>

These search results reproduce every example of the use of <trailer> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <trailer> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ul>

These search results reproduce every example of the use of <ul> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <ul> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <unclear> (unclear)

These search results reproduce every example of the use of <unclear> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <unclear> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

TEI Tite

A recommendation for off-site text encoding

4. Types of Text

Table of contents

4.1. Letters

4.2. Verse

4.3. Drama

4.4. Newspapers

Previous 3. Global Text Structure

Next 5. Block-level Features

Home

Tite is equipped to support basic encoding of several types of text: in terms of genre, it supports prose, verse, and drama, and in terms of format, it supports books, newspapers, pamphlets, and other similar printed material. Tite has special elements for letters, verse, drama, and newspapers.

Next 4.2. Verse

Home

TEI: Letters⚓︎4.1. Letters

opener and closer are elements designed to encode the beginning and ending sections of letters, prefaces, diary entries, or other personal types of writing. Both elements contain:

dateline: for recording time and place of composition; use date with when value (in W3C format as in the TEI Guidelines) to record date information

signed: for recording a signature

salute: for recording salutation at the beginning ("Dear Roger,") or end ("Yours truly,")

opener contains the additional elements epigraph, argument, and byline. epigraph will often be useful in the context of a letter. When encoding an epigraph, make sure to encode the content as you would any other feature, marking line groups, bibliographical elements, etc.

argument and byline, however, are not intended specifically for use with letters:

argument: for a summary that precedes a division

byline: for a statement of responsibility for the document

Previous 4.1. Letters

Next 4.3. Drama

Home

TEI: Verse⚓︎4.2. Verse

All verse should be encoded within at least one lg element, even when there are no distinct stanzas or when the verse is interspersed with prose. If it is known, use the type attribute to express the type of line group. Sometimes within a poem there is a question about what should be tagged as a lg or as a separate <div>. As a rough rule of thumb, if there is a title accompanying the division, use the <div> element; otherwise, use lg.

Each line of verse should be encoded with the l element, and care should be taken to distinguish these logical lines of verse from lines motivated by page layout. The latter should be encoded as lbs. Thus

AS virtuous men pass mildly away, And whisper to their souls to go, Whilst some of their sad friends do say, "Now his breath goes," and some say, "No." ⚓

should be encoded as

<lg type="stanza">
 <l>AS virtuous men pass mildly away,</l>
 <l rend="indent(1)">And whisper to their souls to<lb/> go,</l>
 <l>Whilst some of their sad friends<lb/> do say,</l>
 <l rend="indent(1)">"Now his breath goes," and<lb/> some say, "No."</l>
</lg>

⚓︎

Also, as in the example above, use the rend attribute to mark when a line is indented more than its siblings. Use ‘numbered’ indent values (e.g. ‘indent(1)’, ‘indent(2)’, etc.) to make clear levels of indentation.

Previous 4.2. Verse

Next 4.4. Newspapers

Home

TEI: Drama⚓︎4.3. Drama

The standard TEI elements for drama should be used: sp, stage, speaker. If the who attribute is used on sp, also transcribe who is given as the speaker, in whatever form it is written, in the speaker element. Short pieces of stage direction that accompany the speaker designation may be included in the speaker element.

Scenes and acts should be encoded as appropriately nested <div> elements with type attributes of scene or act, respectively. Cast lists can likewise be encoded using <div> and type="castlist".

Prologues and epilogues can be treated as sps of their own, unless their structure would be better represented by nested <div> elements.

Previous 4.3. Drama

Home

TEI: Newspapers⚓︎4.4. Newspapers

Tite includes the elements colShift and cb which are well suited for the multi-column layout of newspapers. Additional relevant elements are: ref, to encode a pointer to the continuation of a story in a different column or on a different page; and figure, to describe illustrations, advertisements, and cartoons.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

TEI Tite

A recommendation for off-site text encoding

2. General Requirements

Table of contents

2.1. What to Capture

2.2. End-of-line Hyphens

2.3. Character Encoding

2.4. Accuracy and Verification

2.5. Documenting the Encoding Process

Previous 1. Introduction

Next 3. Global Text Structure

Home

TEI: What to Capture⚓︎2.1. What to Capture

All printed material should be captured: all text (that is, printed characters) should be transcribed and the presence of graphical items or other non-transcribable elements should be indicated with markup.

Previous 2.1. What to Capture

Next 2.3. Character Encoding

Home

TEI: End-of-line Hyphens⚓︎2.2. End-of-line Hyphens

A distinction should be maintained in the electronic transcription between end-of-line or ‘soft’ hyphens (an artifact of page layout) and ‘hard’ hyphens (a linguistic feature). The former should be transcribed as the SOFT HYPHEN (U+00AD) character; the latter, as the HYPHEN-MINUS (U+002D) character generally available on Western keyboards. In the rare case of coincidence of the two types — where a word that is normally hyphenated is split across a line break at its hyphen — the hyphen should be considered hard, and transcribed as the HYPHEN-MINUS.

Previous 2.2. End-of-line Hyphens

Next 2.4. Accuracy and Verification

Home

TEI: Character Encoding⚓︎2.3. Character Encoding

Characters should be encoded in UTF-8. For characters not easily input from the keyboard, use hexadecimal numeric entities (e.g. é, the small latin e with acute accent, is represented as &#x00E9;).

Previous 2.3. Character Encoding

Next 2.5. Documenting the Encoding Process

Home

TEI: Accuracy and Verification⚓︎2.4. Accuracy and Verification

The standard for accuracy of transcription should be at least 99.99% (1 error in 10,000 characters). The sample size for verification will be 5% of the total text.

Previous 2.4. Accuracy and Verification

Home

TEI: Documenting the Encoding Process⚓︎2.5. Documenting the Encoding Process

Almost surely, difficult encoding situations will arise whose resolution may not be covered by this documentation or the TEI Guidelines. In such cases, it is important to document the markup choices that are made. To this end each encoded file should be accompanied by a document with such notes. These notes should reference features of a document that seem remarkable to encoders and how these were handled by encoders.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

TEI Tite

A recommendation for off-site text encoding

3. Global Text Structure

Table of contents

3.1. TEI Tite text structure

3.2. Groups of Texts

3.3. Structural Divisions

3.4. Front and Back Matter

Previous 2. General Requirements

Next 4. Types of Text

Home

TEI: TEI Tite text structure⚓︎3.1. TEI Tite text structure

In TEI Tite, text is the root element, containing front matter, the body of the text, and back matter.

<text xml:id="unique-identifier">
 <front>
<!-- front matter -->
 </front>
 <body>
<!-- body of text -->
 </body>
 <back>
<!-- back matter -->
 </back>
</text>

⚓︎

The text's xml:id attribute should contain a unique identifier for the document being encoded.

Tite omits the <teiHeader> element as a convenience to transcribers. This departs from normal TEI practice, which requires <TEI> as the root element, containing <teiHeader> and text elements. In order to bring a document encoded in TEI Tite into adherence with the TEI Abstract Model, projects should add a teiHeader before engaging in post-transcription processing.

Previous 3.1. TEI Tite text structure

Next 3.3. Structural Divisions

Home

TEI: Groups of Texts⚓︎3.2. Groups of Texts

A document should be encoded as a group of texts only when each member of the group contains its own front or back matter (most often, a separate title page). In this case the group element should be a child of the text element, and should contain child text elements each containing a front, body, and back (each text need not have both front and back matter, but should have at least one). Note that this group of texts will still have its own front and back matter. When dealing with a group of texts, the basic TEI text structure is modified to look like:

<text>
 <front>
<!-- front matter for the group -->
 </front>
 <group>
  <text>
   <front>
<!-- front matter of first text -->
   </front>
   <body>
<!-- body of first text -->
   </body>
   <back>
<!-- back matter of first text -->
   </back>
  </text>
  <text>
   <front>
<!-- front matter of second text -->
   </front>
   <body>
<!-- body of second text -->
   </body>
   <back>
<!-- back matter of second text -->
   </back>
  </text>
<!-- more texts or groups of texts here -->
 </group>
 <back>
<!-- back matter for the group -->
 </back>
</text>

⚓︎

In cases where a document appears to contain a group of texts but the above condition is not met, encode each unit as a (numbered) <div> with an appropriate type attribute.

Previous 3.2. Groups of Texts

Next 3.4. Front and Back Matter

Home

TEI: Structural Divisions⚓︎3.3. Structural Divisions

Tite uses numbered divisions: div1 through div7, which stand for levels of nesting within a text. div1s nest inside or are contained by the front, body, and back elements, div2s nest inside or are contained by div1s, etc. The document's table of contents is often a good place to find cues about where structural divisions start and end; other cues can be blank pages, recurring typographical or ornamental features, or a numbering system ("Chapter 5" etc.). Also, the presence of a heading will often indicate the beginning of a division.

The type attribute should be used to express the type of division being marked. Where present, use a name for division type given in the document itself. Though any constrained enumerated list of type values will have to be determined on a job-by-job basis, some examples of appropriate division types are:

act

article

book

chapter

essay

letter

part

scene

section

subsection

When a heading is present, encode it with the head element. If there is more than one heading at the beginning of a given division, encode each heading with its own head element, using the type attribute to distinguish them. Appropriate values are:

main

sub (subtitle)

alt (alternate)

desc (descriptive)

The n attribute should be used to record sequential labels associated with a structural division (numbers, numerals, letters). When present, these labels should also be transcribed within the content of head element. For instance:

<div1 n="III" type="part">
 <head>III: It Awakes</head>
<!-- ... -->
</div1>

⚓︎

TEI: False Indicators⚓︎3.3.1. False Indicators

A divisional title is a page that resembles a half-title page: it displays the title or heading of a major structural unit on an otherwise blank page. Divisional titles should be encoded not with a separate <div> element, but as a head within the appropriate <div>. For half-title pages and similar fly-title pages see the section on Front Matter.

Another potential false indication of a new structural division is an ornament used as an informal division: a printer's ornament of some sort, a string of asterisks or periods, or a horizontal line. Mark these with the special ornament element. If the ornament is a horizontal line or printer's device or otherwise not transcribable, make the element empty and include an appropriate type attribute (line or ornament); if the ornament is made up of characters, transcribe the characters into the ornament's content.

Previous 3.3. Structural Divisions

Home

TEI: Front and Back Matter⚓︎3.4. Front and Back Matter

Front and back matter should be encoded with the front and back elements, respectively. div1 elements should contain the major sections and should be characterized by type attribute values. The exception, however, is the title page, which should be encoded with the titlePage element and its children. The titlePart element should have a type attribute with one of the following values:

main

sub (subtitle)

desc (descriptive title)

alt (alternate title)

volume (volume information)

<titlePart type="volume"> should be used to encode volume information wherever it is found on the title page, even if it is separated from the other title information. The elements that make up the titlePage content model are: graphic, byline, epigraph, docTitle, titlePart, docAuthor, docEdition, docImprint, docDate, figure, ornament.

Information on the verso of the title page should be included as well (after a pb).

Common items to encode in front and back matter -- and therefore common type attribute values for front and back divisions are:

front

acknowledgements

advertisement

castlist

contents

dedication

fly-title

foreword

introduction

preface

back

appendix

bibliography

colophon

glossary

index

Half-title and fly-title pages may be encountered in the front matter. A half-title page precedes the title page proper and sometimes includes volume or series information; a fly-title page comes at the very end of the front matter, just before the body. In the case of half-titles, encode these as <div1 type="half-title"> (with titlePart elements inside docTitle elements as appropriate); in the case of fly-titles, encode them likewise with <div1 type="fly-title">, making sure to make the fly-title division the last part of the front matter (and not the first part of the body, as may seem reasonable as well).

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

TEI Tite

A recommendation for off-site text encoding

Appendix B Formal specification

Previous Appendix A TEI Tite and the Best Practices for TEI in Libraries

Next Appendix C Acknowledgments

Home

Schema tei_tite: changed components

Schema tei_tite: unchanged components

add: (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]

address: (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]

addrLine: (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]

argument: (argument) contains a formal list or prose description of the topics addressed by a subdivision of a text. [4.2. Elements Common to All Divisions 4.6. Title Pages]

att.anchoring: (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.

att.ascribed.directed: provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]

att.calendarSystem: provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 14.4. Dates]

att.cmc: (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment.

att.cReferencing: provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer.

att.declarable: provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [16.3. Associating Contextual Information with a Text]

att.docStatus: provides attributes for use on metadata elements describing the status of a document.

att.fragmentable: provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.

att.global.change: provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.

att.global.facs: provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [12.1. Digital Facsimiles]

att.global.linking: provides a set of attributes for hypertextual linking. [17. Linking, Segmentation, and Alignment]

att.global.responsibility: provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 12.3.2.2. Hand, Responsibility, and Certainty Attributes 18.3. Spans and Interpretations 14.1.1. Linking Names and Their Referents]

att.global.source: provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]

att.media: provides attributes for specifying display and related properties of external media.

att.milestoneUnit: provides attributes to indicate the type of section which is changing at a specific milestone. [3.11.3. Milestone Elements 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]

att.notated: provides attributes to indicate any specialised notation used for element content.

att.personal: (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [14.2.1. Personal Names]

att.resourced: provides attributes by which a resource (such as an externally held media file) may be located.

att.sortable: provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [10.1. Dictionary Body and Overall Structure]

att.tableDecoration: provides attributes used to decorate rows or cells of a table. [15. Tables, Formulæ, Graphics, and Notated Music]

att.timed: provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information]

att.transcriptional: provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [12.3.1.4. Additions and Deletions]

att.written: provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]

author: (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]

back: (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]

bibl: (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]

body: (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]

byline: (byline) contains the primary statement of responsibility given for a work on its title page or at the head or end of the work. [4.2.2. Openers and Closers 4.5. Front Matter]

cb: (column beginning) marks the beginning of a new column of a text on a multi-column page. [3.11.3. Milestone Elements]

cell: (cell) contains one cell of a table. [15.1.1. TEI Tables]

closer: (closer) groups together salutations, datelines, bylines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions]

dateline: (dateline) contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. [4.2.2. Openers and Closers]

del: (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]

desc: (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [23.4.1. Description of Components]

div1: (level-1 text division) contains a first-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]

div2: (level-2 text division) contains a second-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]

div3: (level-3 text division) contains a third-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]

div4: (level-4 text division) contains a fourth-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]

div5: (level-5 text division) contains a fifth-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]

div6: (level-6 text division) contains a sixth-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]

div7: (level-7 text division) contains the smallest possible subdivision of the front, body or back of a text, larger than a paragraph. [4.1.2. Numbered Divisions]

docAuthor: (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline). [4.6. Title Pages]

docDate: (document date) contains the date of a document, as given on a title page or in a dateline. [4.6. Title Pages]

docEdition: (document edition) contains an edition statement as presented on a title page of a document. [4.6. Title Pages]

docImprint: (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. [4.6. Title Pages]

docTitle: (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. Title Pages]

editor: contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]

email: (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]

epigraph: (epigraph) contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page. [4.2.3. Arguments, Epigraphs, and Postscripts 4.2. Elements Common to All Divisions 4.6. Title Pages]

figure: (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [15.4. Specific Elements for Graphic Images]

floatingText: (floating text) contains a single text of any kind, whether unitary or composite, which interrupts the text containing it at any point and after which the surrounding text resumes. [4.3.2. Floating Texts]

foreign: (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]

front: (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]

group: (group) contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc. [4. Default Text Structure 4.3.1. Grouped Texts 16.1. Varieties of Composite Text]

handShift: (handwriting shift) marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [12.3.2.1. Document Hands]

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]

hi: (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]

item: (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]

label: (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]

lb: (line beginning) marks the beginning of a topographic line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.6. Speech Contents]

lg: (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.6. Speech Contents]

list: (list) contains any sequence of items organized as a list. [3.8. Lists]

listBibl: (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]

macro.abContent: (anonymous block content) defines the content of anonymous block elements. [1.3. The TEI Class System]

macro.limitedContent: (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]

macro.paraContent: (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]

macro.phraseSeq: (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]

macro.phraseSeq.limited: (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]

macro.specialPara: ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]

milestone: (milestone) marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element. [3.11.3. Milestone Elements]

model.addressLike: groups elements used to represent a postal or email address. [1. The TEI Infrastructure]

model.addrPart: groups elements such as names or postal codes which may appear as part of a postal address. [3.6.2. Addresses]

model.attributable: groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]

model.biblLike: groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]

model.biblPart: groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References]

model.certLike: groups elements which are used to indicate uncertainty or precision of other elements.

model.cmc: includes the CMC-specific element <post> and makes it available on the divPart level. This allows for using (and combining) occurrences of <post>, <u>, <incident>, and <kinesic> in one and the same <div> in order to be able to represent the combined use of written and spoken posts, utterances, and nonverbal acts on the GUI of multimodal CMC environments.

model.common: groups common chunk- and inter-level elements. [1.3. The TEI Class System]

model.dateLike: groups elements containing temporal expressions. [3.6.4. Dates and Times 14.4. Dates]

model.descLike: groups elements which contain a description of their function.

model.div1Like: groups top-level structural divisions.

model.div2Like: groups second-level structural divisions.

model.div3Like: groups third-level structural divisions.

model.div4Like: groups fourth-level structural divisions.

model.div5Like: groups fifth-level structural divisions.

model.div6Like: groups sixth-level structural divisions.

model.div7Like: groups seventh-level structural divisions.

model.divBottom: groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]

model.divBottomPart: groups elements which can occur only at the end of a text division. [4.6. Title Pages]

model.divGenLike: groups elements used to represent a structural division which is generated rather than explicitly present in the source.

model.divLike: groups elements used to represent un-numbered generic structural divisions.

model.divPart: groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]

model.divTop: groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]

model.divTopPart: groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]

model.divWrapper: groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions]

model.egLike: groups elements containing examples or illustrations. [23.1.1. Phrase Level Terms]

model.emphLike: groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]

model.entryPart: groups non-morphological elements appearing within a dictionary entry. [10.1. Dictionary Body and Overall Structure]

model.frontPart: groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ]

model.frontPart.drama: groups elements which appear at the level of divisions within front or back matter of performance texts only. [7.1. Front and Back Matter ]

model.gLike: groups elements used to represent individual non-Unicode characters or glyphs.

model.global: groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]

model.global.edit: groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]

model.global.meta: groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]

model.graphicLike: groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]

model.headLike: groups elements used to provide a title or heading at the start of a text division.

model.highlighted: groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]

model.hiLike: groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]

model.imprintPart: groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]

model.inter: groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]

model.labelLike: groups elements used to gloss or explain other parts of a document.

model.limitedPhrase: groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]

model.listLike: groups list-like elements. [3.8. Lists]

model.lLike: groups elements representing metrical components such as verse lines.

model.lPart: groups phrase-level elements which may appear within verse only. [6.2. Components of the Verse Line]

model.measureLike: groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.6.3. Numbers and Measures]

model.milestoneLike: groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.11.3. Milestone Elements]

model.nameLike: groups elements which name or refer to a person, place, or organization.

model.nameLike.agent: groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]

model.noteLike: groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]

model.oddDecl: groups elements which generate declarations in some markup language in ODD documents.

model.offsetLike: groups elements which can appear only as part of a place name. [14.2.3. Place Names]

model.paraPart: groups elements that may appear in paragraphs and similar elements. [3.1. Paragraphs]

model.phrase: groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]

model.phrase.xml: groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values. [23. Documentation Elements]

model.placeNamePart: groups elements which form part of a place name. [14.2.3. Place Names]

model.placeStateLike: groups elements which describe changing states of a place.

model.pLike: groups paragraph-like elements.

model.pLike.front: groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]

model.pPart.data: groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]

model.pPart.edit: groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]

model.pPart.editorial: groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes]

model.pPart.msdesc: groups phrase-level elements used in manuscript description. [11. Manuscript Description]

model.pPart.transcriptional: groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]

model.ptrLike: groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]

model.quoteLike: groups elements used to directly contain quotations.

model.respLike: groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.

model.segLike: groups elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories]

model.specDescLike: groups elements for referring to specification elements. [23. Documentation Elements]

model.stageLike: groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. Other Types of Performance Text]

model.titlepagePart: groups elements which can occur as direct constituents of a title page, such as docTitle, docAuthor, docImprint, or epigraph. [4.6. Title Pages]

name: (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]

opener: (opener) groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. [4.2. Elements Common to All Divisions]

p: (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.6. Speech Contents]

postscript: contains a postscript, e.g. to a letter. [4.2. Elements Common to All Divisions]

publisher: (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]

pubPlace: (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]

q: (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]

resp: (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]

respStmt: (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]

row: (row) contains one row of a table. [15.1.1. TEI Tables]

salute: (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc. [4.2.2. Openers and Closers]

seg: (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [17.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.6. Speech Contents]

signed: (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. [4.2.2. Openers and Closers]

sp: (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.2. Speeches and Speakers]

speaker: contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.13.2. Core Tags for Drama]

table: (table) contains text displayed in tabular form, in rows and columns. [15.1.1. TEI Tables]

teidata.certainty: defines the range of attribute values expressing a degree of certainty.

teidata.count: defines the range of attribute values used for a non-negative integer value used as a count.

teidata.duration.iso: defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats.

teidata.duration.w3c: defines the range of attribute values available for representation of a duration in time using W3C datatypes.

teidata.enumerated: defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.

teidata.language: defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]

teidata.numeric: defines the range of attribute values used for numeric values.

teidata.outputMeasurement: defines a range of values for use in specifying the size of an object that is intended for display.

teidata.point: defines the data type used to express a point in cartesian space.

teidata.pointer: defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.

teidata.probability: defines the range of attribute values expressing a probability.

teidata.probCert: defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.

teidata.temporal.w3c: defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.

teidata.text: defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.

teidata.truthValue: defines the range of attribute values used to express a truth value.

teidata.versionNumber: defines the range of attribute values used for version numbers.

teidata.word: defines the range of attribute values expressed as a single word or token.

teidata.xmlName: defines attribute values which contain an XML name.

teidata.xpath: defines attribute values which contain an XPath expression.

text: (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 16.1. Varieties of Composite Text]

title: (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]

titlePage: (title page) contains the title page of a text, appearing within the front or back matter. [4.6. Title Pages]

titlePart: (title part) contains a subsection or division of the title of a work, as indicated on a title page. [4.6. Title Pages]

trailer: contains a closing title or footer appearing at the end of a division of a text. [4.2.4. Content of Textual Divisions 4.2. Elements Common to All Divisions]

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

Table of contents

1. Introduction

2. General Requirements

2.1. What to Capture

2.2. End-of-line Hyphens

2.3. Character Encoding

2.4. Accuracy and Verification

2.5. Documenting the Encoding Process

3. Global Text Structure

3.1. TEI Tite text structure

3.2. Groups of Texts

3.3. Structural Divisions

3.3.1. False Indicators

3.4. Front and Back Matter

4. Types of Text

4.1. Letters

4.2. Verse

4.3. Drama

4.4. Newspapers

5. Block-level Features

5.1. Block Quotations

5.2. Figures

5.3. Tables and Lists

5.4. Notes

5.5. divWrapper Elements

5.6. Uncertain Blocks

6. Phrase-level Features

6.1. Typographical Changes

6.2. Phrase-level Quotation

6.3. Alignment and Indentation

6.4. Uncertain Segments

6.5. Unknown Glyphs

7. Reference Systems

Appendix A TEI Tite and the Best Practices for TEI in Libraries

Appendix B Formal specification

Appendix C Acknowledgments

Appendices

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

TEI Tite

A recommendation for off-site text encoding

1. Introduction

Next 2. General Requirements

Home

TEI Tite is a constrained customization of TEI designed for use when outsourcing production of TEI documents to vendors, who use some combination of OCR and keyboarding to produce encoded text. While the canonical version of Tite is maintained by the TEI Council, a derived version is used in the AccessTEI program.

TEI Tite is meant to express a transitional format for documents, not an archival one. A project outsourcing encoding of documents using Tite should convert Tite documents created by vendors into a more suitable format for long-term preservation, such as one of the encoding levels of Best Practices for TEI in Libraries or a project-specific TEI customization.

While Tite includes only a limited set of all of the elements in TEI, it should not be confused with TEI Lite, which also contains a subset of elements. What distinguishes Tite from other TEI customizations is that Tite is meant to prescribe exactly one way of encoding a particular feature of a document in as many cases as possible, ensuring that any two encoders would produce the same XML document for a source document.

This document specifies how a source document should be encoded using TEI Tite. Its organizing model is roughly the structure of a TEI document itself, and it proceeds from high-level features to low, starting with general requirements, text structure, directions on when to group texts, considerations about type of text (genre and format), continuing down to instructions on marking phrase-level features, reference systems, and so forth. In its original ODD (one document does-it-all) format, this document can generate everything necessary for working in TEI Tite: both documentation (this Tite-specific prose as well as the full technical documentation for each of its elements) and schemas in either W3C Schema, RELAX NG, or XML DTD. Software utilities, including the Roma web tool, can generate these.

Tite uses a subset of the TEI's elements, except for a few shortcut elements for the convenience of use by vendors (b, i, ul, sup, sub, smcap, colShift and ornament) which can be transformed to normal TEI elements. Tite is also not a TEI-conformant customization since it breaks the TEI Abstract Model by omitting <teiHeader> for encoder convenience. That is, Tite was created primarily by removing elements and attributes from the TEI, and not from extensive modification. As a TEI customization, Tite inherits TEI semantics, and ambiguity in this specification should be resolved with reference to the TEI Guidelines. What makes Tite distinct is that where the TEI in general is famously tolerant of multiple methods of encoding a given feature, Tite seeks uniformity of encoding through constraint, via its stripped-down tag set and via this specification.

Tite can be used to encode printed prose, poetry, drama, newspapers, and anything else which can be described with the basic TEI building-blocks of divisions, paragraphs, line groups, and speeches.

In this documentation, document refers generally to the item (book, pamphlet, newspaper, etc.) to be encoded and text to either linguistic (as opposed to graphic) material or a logically distinct literary unit.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

TEI Tite

A recommendation for off-site text encoding

6. Phrase-level Features

Table of contents

6.1. Typographical Changes

6.2. Phrase-level Quotation

6.3. Alignment and Indentation

6.4. Uncertain Segments

6.5. Unknown Glyphs

Previous 5. Block-level Features

Next 7. Reference Systems

Home

TEI: Typographical Changes⚓︎6.1. Typographical Changes

There are six elements in Tite that capture specific typographical features:

b

for bold-face glyphs

i

for italicized glyphs

ul

for underlined glyphs

smcap

for glyphs in small-caps

sub

for glyphs in subscript

sup

for glyphs in superscript

These mark the physical change, and are agnostic about a logical motivation for it. There are two exceptions to this approach, however: marking foreign words and titles. In the case of foreign words, use the foreign element; in the case of titles, use the title element only if certain that the word or phrase in question is a title. If a phrase is, say, italicized, but you are uncertain about its being a title, use the i element instead. Foreign words should be marked only if they are typographically distinguished from surrounding text.

In addition, the <handshift> element may be used within the body of a transcription to indicate where a change of hand is detected for whatever reason.

If there is a typographical feature not covered by the above elements, the TEI hi element is still available in Tite. Use it without a rend attribute.

Previous 6.1. Typographical Changes

Next 6.3. Alignment and Indentation

Home

TEI: Phrase-level Quotation⚓︎6.2. Phrase-level Quotation

For passages set off by quotation marks or another delimeter, use the q element, including the delimeter inside the tag.

Previous 6.2. Phrase-level Quotation

Next 6.4. Uncertain Segments

Home

TEI: Alignment and Indentation⚓︎6.3. Alignment and Indentation

If the alignment of an element seems remarkable, set the element's rend attribute to an appropriate value (normally center, right, left, etc.). However, when semantic already accounts for its cause, description of alignment is not necessary. Headings, for instance, do not need to be marked as being centered.

To indicate level of indentation (often in verse), use numerical ‘arguments’ to ‘indent’, as in indent(1), indent(-1), and so on.

Previous 6.3. Alignment and Indentation

Next 6.5. Unknown Glyphs

Home

TEI: Uncertain Segments⚓︎6.4. Uncertain Segments

The seg element is the phrase-level analogue to the ab element. If a phrase-level feature seems to be present but its identity is hard to fathom, use this element. This, again, is a last resort.

Alternately, when a passage of text is for some reason too hard to read, use the unclear element, setting the reason attribute to an appropriate value. When using unclear, surround the entire word with the tag if any part of it is unclear (not just the illegible letter, say).

Previous 6.4. Uncertain Segments

Home

TEI: Unknown Glyphs⚓︎6.5. Unknown Glyphs

For cases in which it is unknown which character a given glyph corresponds to, mark the glyph with the g element to indicate the uncertainty. By convention in Tite, g represents any unknown glyph; no ref attribute is necessary. Note that unknown glyphs are different from illegible text.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<ab>

<ab> (anonymous block) contains any component-level unit of text, acting as a container for phrase or inter level elements analogous to, but without the same constraints as, a paragraph. [17.3. Blocks, Segments, and Anchors]

Module | linking

Attributes

part part⚓︎

Status
Optional

Member of | macro.abContent model.pLike

Contained by

core: item note q sp stage

figures: cell figure

linking: ab

textstructure: argument back body div1 div2 div3 div4 div5 div6 div7 epigraph front postscript

May contain

core: abbr add address bibl cb cit date del desc email foreign gap graphic hi l label lb lg list listBibl milestone name note num pb ptr q ref stage time title unclear

derived-module-tei_tite: b colShift i ornament smcap sub sup ul

figures: figure formula table

gaiji: g

linking: ab seg

textstructure: floatingText

transcr: handShift

character data

Note | 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.

Example

<div type="book" n="Genesis">
 <div type="chapter" n="1">
  <ab>In the beginning God created the heaven and the earth.</ab>
  <ab>And the earth was without form, and void; and
     darkness was upon the face of the deep. And the
     spirit of God moved upon the face of the waters.</ab>
  <ab>And God said, Let there be light: and there was light.</ab>
<!-- ...-->
 </div>
</div>

Show all ⚓︎

Schematron

<sch:rule context="tei:l//tei:ab">
<sch:assert test="ancestor::tei:floatingText | parent::tei:figure | parent::tei:note"> Abstract model violation: Metrical lines (<l> elements) may not contain higher-level divisions such as <p> or <ab>, unless <ab> is a child of <figure> or <note>, or is a descendant of <floatingText>.
</sch:assert>
</sch:rule>

Content model

<content>
 <macroRef key="macro.abContent"/>
</content>

Schema Declaration

element ab { attribute part { text }?, macro.abContent }

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

type type⚓︎

Status
Optional

Member of | model.pPart.editorial

Contained by

core: abbr add addrLine author bibl date del desc editor email foreign head hi item l label name note num p pubPlace publisher q ref resp speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell

linking: ab seg

textstructure: byline closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain

core: abbr add address cb cit date del email foreign gap graphic hi lb milestone name note num pb ptr q ref time title unclear

derived-module-tei_tite: b colShift i smcap sub sup ul

figures: figure formula

gaiji: g

linking: seg

textstructure: floatingText

transcr: handShift

character data

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

Example

<choice>
 <expan>North Atlantic Treaty Organization</expan>
 <abbr cert="low">NorATO</abbr>
 <abbr cert="high">NATO</abbr>
 <abbr cert="high" xml:lang="fr">OTAN</abbr>
</choice>

Show all ⚓︎

Example

<choice>
 <abbr>SPQR</abbr>
 <expan>senatus populusque romanorum</expan>
</choice>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element abbr { attribute type { text }?, macro.phraseSeq }

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 14.4. Dates]
Module | tei
Members | author date docDate editor name resp time title

Attributes

att.datable.w3c

@when

@from

@to

Note

This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 14.4. Dates]
Module | tei
Members | att.datable [author date docDate editor name resp time title]

Attributes

when when⚓︎
supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.

Status
Optional

Datatype
teidata.temporal.w3c

Examples of W3C date, time, and date & time formats.

<p>
 <date when="1945-10-24">24 Oct 45</date>
 <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>
 <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>
 <time when="14:12:38">fourteen twelve and 38 seconds</time>
 <date when="1962-10">October of 1962</date>
 <date when="--06-12">June 12th</date>
 <date when="---01">the first of the month</date>
 <date when="--08">August</date>
 <date when="2006">MMVI</date>
 <date when="0056">AD 56</date>
 <date when="-0056">56 BC</date>
</p>

⚓︎

This list begins in
 the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after
 Pentecost, in that year the
<date calendar="#julian" when="1632-06-06">27th of May (old style)</date>.

⚓︎

<opener>
 <dateline>
  <placeName>Dorchester, Village,</placeName>
  <date when="1828-03-02">March 2d. 1828.</date>
 </dateline>
 <salute>To
   Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time>
</opener>

⚓︎

from from⚓︎
indicates the starting point of the period in standard form, e.g. yyyy-mm-dd.

Status
Optional

Datatype
teidata.temporal.w3c

to to⚓︎
indicates the ending point of the period in standard form, e.g. yyyy-mm-dd.

Status
Optional

Datatype
teidata.temporal.w3c

Schematron

<sch:rule context="tei:*[@when]">
<sch:report test="@notBefore|@notAfter|@from|@to"
 role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report>
</sch:rule>

Schematron

<sch:rule context="tei:*[@from]">
<sch:report test="@notBefore"
 role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report>
</sch:rule>

Schematron

<sch:rule context="tei:*[@to]">
<sch:report test="@notAfter"
 role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report>
</sch:rule>

Example

<date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date>

⚓︎

Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]

Module | tei

Members
abbr add addrLine address argument author b back bibl body byline cb cell closer colShift date dateline del desc div1 div2 div3 div4 div5 div6 div7 docAuthor docDate docEdition docImprint docTitle editor email epigraph figure floatingText foreign formula front g gap graphic group handShift head hi i item l label lb lg list listBibl milestone name note num opener ornament p pb postscript ptr pubPlace publisher q ref resp respStmt row salute seg signed smcap sp speaker stage sub sup table text time title titlePage titlePart trailer ul unclear

Attributes

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

xml:id xml:id⚓︎
(identifier) provides a unique identifier for the element bearing the attribute.

Status
Optional

Datatype
ID

Note

The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

n n⚓︎
(number) gives a number (or other label) for an element, which is not necessarily unique within the document.

Status
Optional

Datatype
teidata.text

Note

The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

xml:lang xml:lang⚓︎
(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.

Status
Optional

Datatype
teidata.language

<p> … The consequences of
 this rapid depopulation were the loss of the last
<foreign xml:lang="rap">ariki</foreign> or chief
 (Routledge 1920:205,210) and their connections to
 ancestral territorial organization.</p>

⚓︎

Note

The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the <teiHeader> from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

The authoritative list of registered language subtags is maintained by IANA and is available at https://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see https://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

xml:space xml:space⚓︎
signals an intention about how white space should be managed by applications.

Status
Optional

Datatype
teidata.enumerated

Legal values are:

default

signals that the application's default white-space processing modes are acceptable

preserve

indicates the intent that applications preserve all white space

Note

The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]

Module | tei

Members
att.global [abbr add addrLine address argument author b back bibl body byline cb cell closer colShift date dateline del desc div1 div2 div3 div4 div5 div6 div7 docAuthor docDate docEdition docImprint docTitle editor email epigraph figure floatingText foreign formula front g gap graphic group handShift head hi i item l label lb lg list listBibl milestone name note num opener ornament p pb postscript ptr pubPlace publisher q ref resp respStmt row salute seg signed smcap sp speaker stage sub sup table text time title titlePage titlePart trailer ul unclear]

Attributes

rend rend⚓︎
(rendition) indicates how the element in question was rendered or presented in the source text.

Status
Optional

Datatype
1–∞ occurrences of teidata.word separated by whitespace

<head rend="align(center) case(allcaps)">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
<lb/>On Her <lb/>
 <hi rend="case(mixed)">New Blazing-World</hi>.
</head>

⚓︎

Note

These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

style style⚓︎
contains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text.

Status
Optional

Datatype
teidata.text

<head style="text-align: center; font-variant: small-caps;">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
<lb/>
 <hi style="font-variant: normal">New Blazing-World</hi>.
</head>

⚓︎

Note

Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

Note | These guidelines provide no semantic basis or suggested precedence when both rend and rendition are provided. For this reason simultaneous use of both is not recommended for interchange unless documentation explaining the use is provided, probably in an ODD customization.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
Module | tei
Members | note ptr ref

Attributes

targetLang targetLang⚓︎
specifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.

Status
Optional

Datatype
teidata.language

Schematron

<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
<sch:assert test="@target">@targetLang should only be used on <<sch:name/>> if @target is specified.</sch:assert>
</sch:rule>

<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">
 <ptr xml:id="pol-swh_aln_2.1.1-ptr"
  target="pol/UDHR/text.xml#pol_txt_1-head" type="tuv" targetLang="pl"/>
 <ptr xml:id="pol-swh_aln_2.1.2-ptr"
  target="swh/UDHR/text.xml#swh_txt_1-head" type="tuv" targetLang="sw"/>
</linkGrp>

⚓︎

In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.

Note

The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

target target⚓︎
specifies the destination of the reference by supplying one or more URI References.

Status
Optional

Datatype
1–∞ occurrences of teidata.pointer separated by whitespace

Note

One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

Schematron

<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
<sch:assert test="@target">@targetLang should only be used on <<sch:name/>> if @target is specified.</sch:assert>
</sch:rule>

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 18.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.6. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 14.3.2.3. Personal Relationships 12.3.1.1. Core Elements for Transcriptional Work 17.1.1. Pointers and Links 17.3. Blocks, Segments, and Anchors 13.2. Linking the Apparatus to the Text 23.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 24.3.1.3. Modification of Attribute and Attribute Value Lists]

Module | tei
Members | abbr add address bibl cb date del desc div1 div2 div3 div4 div5 div6 div7 figure floatingText g graphic group head label lb lg list listBibl milestone name note num pb ptr q ref seg table text time title titlePage titlePart trailer

Attributes

type type⚓︎
characterizes the element in some sense, using any convenient classification scheme or typology.

Status
Optional

Datatype
teidata.enumerated

<div type="verse">
 <head>Night in Tarras</head>
 <lg type="stanza">
  <l>At evening tramping on the hot white road</l>
  <l>…</l>
 </lg>
 <lg type="stanza">
  <l>A wind sprang up from nowhere as the sky</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.

Schematron

<sch:rule context="tei:*[@subtype]">
<sch:assert test="@type"> The <<sch:name/>> element should not be categorized in detail with @subtype unless also categorized in general with @type.
</sch:assert>
</sch:rule>

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 24.3.1.3. Modification of Attribute and Attribute Value Lists .

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<cit>

<cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 10.3.5.1. Examples]

Module | core
Member of | model.quoteLike

Contained by

core: abbr add addrLine author cit del desc editor email foreign head hi item l label name note num p pubPlace publisher q ref sp speaker stage title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell figure

linking: ab seg

textstructure: argument body div1 div2 div3 div4 div5 div6 div7 docAuthor docDate docEdition epigraph postscript salute signed titlePart trailer

May contain

core: bibl cb cit gap graphic lb listBibl milestone note pb ptr q ref

derived-module-tei_tite: colShift

figures: figure formula

textstructure: floatingText

Example

<cit>
 <quote>and the breath of the whale is frequently attended with such an insupportable smell,
   as to bring on disorder of the brain.</quote>
 <bibl>Ulloa's South America</bibl>
</cit>

Show all ⚓︎

Example

<entry>
 <form>
  <orth>horrifier</orth>
 </form>
 <cit type="translation" xml:lang="en">
  <quote>to horrify</quote>
 </cit>
 <cit type="example">
  <quote>elle était horrifiée par la dépense</quote>
  <cit type="translation" xml:lang="en">
   <quote>she was horrified at the expense.</quote>
  </cit>
 </cit>
</entry>

Show all ⚓︎

Example

<cit type="example">
 <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>
 <media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"
  mimeType="audio/wav"/>
 <cit type="translation">
  <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>
 </cit>
 <cit type="translation">
  <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>
 </cit>
</cit>

Show all ⚓︎

Content model

<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.biblLike"/>
  <classRef key="model.egLike"/>
  <classRef key="model.entryPart"/>
  <classRef key="model.global"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.attributable"/>
  <elementRef key="pc"/>
  <elementRef key="q"/>
 </alternate>
</content>

Schema Declaration

element cit
{
   (
      model.biblLike
    | model.egLike
    | model.entryPart
    | model.global
    | model.graphicLike
    | model.ptrLike
    | model.attributable
    | pc
    | q
   )+
}

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<date>

<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.datable

att.datable.w3c

@when

@from

@to

att.typed

@type

att.calendarSystem

@calendar

att.cmc

@generatedBy

Member of | model.dateLike

Contained by

core: abbr add addrLine author bibl date del desc editor email foreign head hi item l label name note num p pubPlace publisher q ref resp speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell

linking: ab seg

textstructure: byline closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain

core: abbr add address cb date del email foreign gap graphic hi lb milestone name note num pb ptr q ref time title unclear

derived-module-tei_tite: b colShift i smcap sub sup ul

figures: figure formula

gaiji: g

linking: seg

transcr: handShift

character data

Example

<date when="1980-02">early February 1980</date>

Show all ⚓︎

Example

Given on the <date when="1977-06-12">Twelfth Day
 of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic
 the Two Hundredth and first and of the University the Eighty-Sixth.</date>

Show all ⚓︎

Example

<date when="1990-09">September 1990</date>

Show all ⚓︎

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>

Schema Declaration

element date { ( text | model.gLike | model.phrase | model.global )* }

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<formula>

<formula> (formula) contains a mathematical or other formula. [15.2. Formulæ and Mathematical Expressions]

Module | figures

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.notated

@notation

notation notation⚓︎

Status
Optional

Member of | model.graphicLike

Contained by

core: abbr add addrLine author cit date del editor email foreign head hi item l label name note num p pubPlace publisher q ref speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell figure formula table

linking: ab seg

textstructure: byline closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain

core: graphic hi q

derived-module-tei_tite: b i smcap sub sup ul

figures: formula

character data

Example

<formula notation="tex">$E=mc^2$</formula>

Show all ⚓︎

Example

<formula notation="none">E=mc<hi rend="sup">2</hi>
</formula>

Show all ⚓︎

Example

<formula notation="mathml">
 <m:math>
  <m:mi>E</m:mi>
  <m:mo>=</m:mo>
  <m:mi>m</m:mi>
  <m:msup>
   <m:mrow>
    <m:mi>c</m:mi>
   </m:mrow>
   <m:mrow>
    <m:mn>2</m:mn>
   </m:mrow>
  </m:msup>
 </m:math>
</formula>

Show all ⚓︎

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.hiLike"/>
 </alternate>
</content>

Schema Declaration

element formula
{
   attribute notation { text }?,
   ( text | model.graphicLike | model.hiLike )*
}

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<g>

<g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes]

Module | gaiji

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.typed

@type

ref ref⚓︎

Status
Optional

Member of | model.gLike

Contained by

core: abbr add addrLine author bibl date del editor email foreign head hi item l label name note num p pubPlace publisher q ref speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell

linking: ab seg

textstructure: byline closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain | Character data only
Note | The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph.

Example

<g ref="#ctlig">ct</g>

Show all ⚓︎

This example points to a <glyph> element with the identifier ctlig like the following:

<glyph xml:id="ctlig">
<!-- here we describe the particular ct-ligature intended -->
</glyph>

Show all ⚓︎

Example

<g ref="#per-glyph">per</g>

Show all ⚓︎

The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per-glyph as follows:

<glyph xml:id="per-glyph">
<!-- ... -->
</glyph>

Show all ⚓︎

Content model

<content>
 <textNode/>
</content>

Schema Declaration

element g { attribute ref { text }?, text }

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<gap>

<gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.timed

@start

@end

hand hand⚓︎

Status
Optional

reason reason⚓︎
(reason) gives the reason for omission.

Status
Optional

Datatype
1–∞ occurrences of teidata.enumerated separated by whitespace

Suggested values include:

cancelled

(cancelled)

deleted

(deleted)

editorial

(editorial) for features omitted from transcription due to editorial policy

illegible

(illegible)

inaudible

(inaudible)

irrelevant

(irrelevant)

sampling

(sampling)

agent agent⚓︎

Status
Optional

Member of | model.global.edit

Contained by

core: abbr add addrLine address author bibl cit date del editor email foreign head hi item l label lg list name note num p pubPlace publisher q ref resp sp speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell figure table

linking: ab seg

textstructure: argument back body byline closer dateline div1 div2 div3 div4 div5 div6 div7 docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group opener postscript salute signed text titlePage titlePart trailer

May contain | core: desc

Note

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.

Example

<gap quantity="4" unit="chars"
 reason="illegible"/>

Show all ⚓︎

Example

<gap quantity="1" unit="essay"
 reason="sampling"/>

Show all ⚓︎

Example

<del>
 <gap atLeast="4" atMost="8" unit="chars"
  reason="illegible"/>
</del>

Show all ⚓︎

Example

<gap extent="several lines" reason="lost"/>

Show all ⚓︎

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>

Schema Declaration

element gap
{
   attribute hand { text }?,
   attribute reason
   {
      list
      {
         (
            "cancelled"
          | "deleted"
          | "editorial"
          | "illegible"
          | "inaudible"
          | "irrelevant"
          | "sampling"
          | teidata.enumerated
         )+
      }
   }?,
   attribute agent { text }?,
   ( model.descLike | model.certLike )*
}

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 12.1. Digital Facsimiles]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.media

@width

@height

@scale

att.resourced

@url

att.typed

@type

width width⚓︎

Status
Optional

height height⚓︎

Status
Optional

scale scale⚓︎

Status
Optional

Member of | model.graphicLike model.titlepagePart

Contained by

core: abbr add addrLine author cit date del editor email foreign head hi item l label name note num p pubPlace publisher q ref speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell figure formula table

linking: ab seg

textstructure: byline closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePage titlePart trailer

May contain | core: desc

Note

The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute.

Within the body of a text, a graphic element indicates the presence of a graphic component in the source itself. Within the context of a <facsimile> or <sourceDoc> element, however, a graphic element provides an additional digital representation of some part of the source being encoded.

Example

<figure>
 <graphic url="fig1.png"/>
 <head>Figure One: The View from the Bridge</head>
 <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
   series of buoys strung out between them.</figDesc>
</figure>

Show all ⚓︎

Example

<facsimile>
 <surfaceGrp n="leaf1">
  <surface>
   <graphic url="page1.png"/>
  </surface>
  <surface>
   <graphic url="page2-highRes.png"/>
   <graphic url="page2-lowRes.png"/>
  </surface>
 </surfaceGrp>
</facsimile>

Show all ⚓︎

Example

<facsimile>
 <surfaceGrp n="leaf1" xml:id="spi001">
  <surface xml:id="spi001r">
   <graphic type="normal"
    subtype="thumbnail" url="spi/thumb/001r.jpg"/>
   <graphic type="normal" subtype="low-res"
    url="spi/normal/lowRes/001r.jpg"/>
   <graphic type="normal"
    subtype="high-res" url="spi/normal/highRes/001r.jpg"/>
   <graphic type="high-contrast"
    subtype="low-res" url="spi/contrast/lowRes/001r.jpg"/>
   <graphic type="high-contrast"
    subtype="high-res" url="spi/contrast/highRes/001r.jpg"/>
  </surface>
  <surface xml:id="spi001v">
   <graphic type="normal"
    subtype="thumbnail" url="spi/thumb/001v.jpg"/>
   <graphic type="normal" subtype="low-res"
    url="spi/normal/lowRes/001v.jpg"/>
   <graphic type="normal"
    subtype="high-res" url="spi/normal/highRes/001v.jpg"/>
   <graphic type="high-contrast"
    subtype="low-res" url="spi/contrast/lowRes/001v.jpg"/>
   <graphic type="high-contrast"
    subtype="high-res" url="spi/contrast/highRes/001v.jpg"/>
   <zone xml:id="spi001v_detail01">
    <graphic type="normal"
     subtype="thumbnail" url="spi/thumb/001v-detail01.jpg"/>
    <graphic type="normal"
     subtype="low-res"
     url="spi/normal/lowRes/001v-detail01.jpg"/>
    <graphic type="normal"
     subtype="high-res"
     url="spi/normal/highRes/001v-detail01.jpg"/>
    <graphic type="high-contrast"
     subtype="low-res"
     url="spi/contrast/lowRes/001v-detail01.jpg"/>
    <graphic type="high-contrast"
     subtype="high-res"
     url="spi/contrast/highRes/001v-detail01.jpg"/>
   </zone>
  </surface>
 </surfaceGrp>
</facsimile>

Show all ⚓︎

Content model

<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>

Schema Declaration

element graphic
{
   attribute width { text }?,
   attribute height { text }?,
   attribute scale { text }?,
   model.descLike*
}

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<l>

<l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.6. Speech Contents]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.fragmentable

@part

part part⚓︎

Status
Optional

Member of | model.lLike

Contained by

core: add del head hi item lg note p q ref sp stage title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell figure

linking: ab seg

textstructure: argument body div1 div2 div3 div4 div5 div6 div7 docEdition epigraph postscript salute signed titlePart trailer

May contain

core: abbr add address bibl cb cit date del desc email foreign gap graphic hi label lb list listBibl milestone name note num pb ptr q ref stage time title unclear

derived-module-tei_tite: b colShift i ornament smcap sub sup ul

figures: figure formula table

gaiji: g

linking: seg

textstructure: floatingText

transcr: handShift

character data

Example

<l met="x/x/x/x/x/" real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l>

Show all ⚓︎

Schematron

<sch:rule context="tei:l">
<sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]">Abstract model violation: Metrical lines (<l> elements) may not contain <l> or <lg> elements.</sch:report>
</sch:rule>

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
 </alternate>
</content>

Schema Declaration

element l
{
   attribute part { text }?,
   ( text | model.gLike | model.phrase | model.inter | model.global )*
}

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.anchoring

@anchored

@targetEnd

att.cmc

@generatedBy

att.pointing

@targetLang

@target

att.typed

@type

att.written

@hand

anchored anchored⚓︎

Status
Optional

targetEnd targetEnd⚓︎

Status
Optional

Member of | model.noteLike

Contained by

core: abbr add addrLine address author bibl cit date del editor email foreign head hi item l label lg list name note num p pubPlace publisher q ref resp respStmt sp speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell figure table

linking: ab seg

textstructure: argument back body byline closer dateline div1 div2 div3 div4 div5 div6 div7 docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group opener postscript salute signed text titlePage titlePart trailer

May contain

core: abbr add address bibl cb cit date del desc email foreign gap graphic hi l label lb lg list listBibl milestone name note num p pb ptr q ref sp stage time title unclear

derived-module-tei_tite: b colShift i ornament smcap sub sup ul

figures: figure formula table

gaiji: g

linking: ab seg

textstructure: floatingText

transcr: handShift

character data

Example

In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":

And yet it is not only
 in the great line of Italian renaissance art, but even in the
 painterly <note place="bottom" type="gloss"
 resp="#MDMH">
 <term xml:lang="de">Malerisch</term>. This word has, in the German, two
 distinct meanings, one objective, a quality residing in the object,
 the other subjective, a mode of apprehension and creation. To avoid
 confusion, they have been distinguished in English as
<mentioned>picturesque</mentioned> and
<mentioned>painterly</mentioned> respectively.
</note> style of the
 Dutch genre painters of the seventeenth century that drapery has this
 psychological significance.

<!-- elsewhere in the document -->
<respStmt xml:id="MDMH">
 <resp>translation from German to English</resp>
 <name>Hottinger, Marie Donald Mackie</name>
</respStmt>

Show all ⚓︎

For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.

Example

The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:

Mevorakh b. Saadya's mother, the matriarch of the
 family during the second half of the eleventh century, <note n="126" anchored="true"> The
 alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
 Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
 published by Jacob Mann.

Show all ⚓︎

However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.

Content model

<content>
 <macroRef key="macro.specialPara"/>
</content>

Schema Declaration

element note
{
   attribute anchored { text }?,
   attribute targetEnd { text }?,
   macro.specialPara
}

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<num>

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

type type⚓︎
indicates the type of numeric value.

Status
Optional

Datatype
teidata.enumerated

Suggested values include:

cardinal

absolute number, e.g. 21, 21.5

ordinal

ordinal number, e.g. 21st

fraction

fraction, e.g. one half or three-quarters

percentage

a percentage

Note

If a different typology is desired, other values can be used for this attribute.

value value⚓︎

Status
Optional

Member of | model.measureLike

Contained by

core: abbr add addrLine author bibl date del desc editor email foreign head hi item l label name note num p pubPlace publisher q ref resp speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell

linking: ab seg

textstructure: byline closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain

core: abbr add address cb cit date del email foreign gap graphic hi lb milestone name note num pb ptr q ref time title unclear

derived-module-tei_tite: b colShift i smcap sub sup ul

figures: figure formula

gaiji: g

linking: seg

textstructure: floatingText

transcr: handShift

character data

Note | Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 19. Feature Structures. The num element is intended for use in simple applications.

Example

<p>I reached <num type="cardinal" value="21">twenty-one</num> on
 my <num type="ordinal" value="21">twenty-first</num> birthday</p>
<p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>
 </num> cm per second.</p>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.phraseSeq"/>
</content>

Schema Declaration

element num
{
   attribute type
   {
      "cardinal" | "ordinal" | "fraction" | "percentage" | teidata.enumerated
   }?,
   attribute value { text }?,
   macro.phraseSeq
}

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

att.typed

@type

Member of | model.milestoneLike

Contained by

core: abbr add addrLine address author bibl cit date del editor email foreign head hi item l label lg list listBibl name note num p pubPlace publisher q ref resp sp speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell figure table

linking: ab seg

textstructure: argument back body byline closer dateline div1 div2 div3 div4 div5 div6 div7 docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group opener postscript salute signed text titlePage titlePart trailer

May contain | Empty element

Note

A pb element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the pb element itself.

The type attribute may be used to characterize the page beginning in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page beginning is word-breaking, or to note the source from which it derives.

Example

Page numbers may vary in different editions of a text.

<p> ... <pb n="145" ed="ed2"/>
<!-- Page 145 in edition "ed2" starts here --> ... <pb n="283" ed="ed1"/>
<!-- Page 283 in edition "ed1" starts here--> ... </p>

Show all ⚓︎

Example

A page beginning may be associated with a facsimile image of the page it introduces by means of the facs attribute

<body>
 <pb n="1" facs="page1.png"/>
<!-- page1.png contains an image of the page;
                        the text it contains is encoded here -->
 <p>
<!-- ... -->
 </p>
 <pb n="2" facs="page2.png"/>
<!-- similarly, for page 2 -->
 <p>
<!-- ... -->
 </p>
</body>

Show all ⚓︎

Content model

<content>
 <empty/>
</content>

Schema Declaration

element pb { empty }

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cReferencing

@cRef

att.cmc

@generatedBy

att.pointing

@targetLang

@target

att.typed

@type

cRef cRef⚓︎

Status
Optional

Member of | model.ptrLike

Contained by

core: abbr add addrLine author bibl cit date del desc editor email foreign head hi item l label name note num p pubPlace publisher q ref resp speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell

linking: ab seg

textstructure: byline closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain | Empty element
Note | The target and cRef attributes are mutually exclusive.

Example

<ptr target="#p143 #p144"/>
<ptr target="http://www.tei-c.org"/>
<ptr cRef="1.3.4"/>

Show all ⚓︎

Schematron

<sch:rule context="tei:ptr">
<sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <<sch:name/>>.</sch:report>
</sch:rule>

Content model

<content>
 <empty/>
</content>

Schema Declaration

element ptr { attribute cRef { text }?, empty }

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cReferencing

@cRef

att.cmc

@generatedBy

att.pointing

@targetLang

@target

att.typed

@type

cRef cRef⚓︎

Status
Optional

Member of | model.ptrLike

Contained by

core: abbr add addrLine author bibl cit date del desc editor email foreign head hi item l label name note num p pubPlace publisher q ref resp speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell

linking: ab seg

textstructure: byline closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain

core: abbr add address bibl cb cit date del desc email foreign gap graphic hi l label lb lg list listBibl milestone name note num pb ptr q ref stage time title unclear

derived-module-tei_tite: b colShift i ornament smcap sub sup ul

figures: figure formula table

gaiji: g

linking: seg

textstructure: floatingText

transcr: handShift

character data

Note | The target and cRef attributes are mutually exclusive.

Example

See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second
 sentence</ref>

Show all ⚓︎

Example

See also <ref target="#locution">s.v. <term>locution</term>
</ref>.

Show all ⚓︎

Schematron

<sch:rule context="tei:ref">
<sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <<sch:name/>>.</sch:report>
</sch:rule>

Content model

<content>
 <macroRef key="macro.paraContent"/>
</content>

Schema Declaration

element ref { attribute cRef { text }?, macro.paraContent }

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<stage>

<stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.5. Stage Directions]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.ascribed.directed

@toWhom

att.cmc

@generatedBy

att.written

@hand

type type⚓︎

Status
Optional

Member of | model.stageLike

Contained by

core: add del desc head hi item l lg note p q ref sp stage title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell figure

linking: ab seg

textstructure: argument body div1 div2 div3 div4 div5 div6 div7 docEdition epigraph postscript salute signed titlePart trailer

May contain

core: abbr add address bibl cb cit date del desc email foreign gap graphic hi l label lb lg list listBibl milestone name note num p pb ptr q ref sp stage time title unclear

derived-module-tei_tite: b colShift i ornament smcap sub sup ul

figures: figure formula table

gaiji: g

linking: ab seg

textstructure: floatingText

transcr: handShift

character data

Note | The who attribute may be used to indicate more precisely the person or persons participating in the action described by the stage direction.

Example

<stage type="setting">A curtain being drawn.</stage>
<stage type="setting">Music</stage>
<stage type="entrance">Enter Husband as being thrown off his horse and falls.</stage>
<!-- Middleton : Yorkshire Tragedy -->
<stage type="exit">Exit pursued by a bear.</stage>
<stage type="business">He quickly takes the stone out.</stage>
<stage type="delivery">To Lussurioso.</stage>
<stage type="novelistic">Having had enough, and embarrassed for the family.</stage>
<!-- Lorraine Hansbury : a raisin in in the sun -->
<stage type="modifier">Disguised as Ansaldo.</stage>
<stage type="entrance modifier">Enter Latrocinio disguised as an empiric</stage>
<!-- Middleton: The Widow -->
<stage type="location">At a window.</stage>
<stage rend="inline" type="delivery">Aside.</stage>

Show all ⚓︎

Example

<l>Behold. <stage n="*" place="margin">Here the vp<lb/>per part of the <hi>Scene</hi> open'd; when
   straight appear'd a Heauen, and all the <hi>Pure Artes</hi> sitting on
   two semi<lb/>circular ben<lb/>ches, one a<lb/>boue another: who sate thus till the rest of the
 <hi>Prologue</hi> was spoken, which being ended, they descended in
   order within the <hi>Scene,</hi> whiles the Musicke plaid</stage> Our
 Poet knowing our free hearts</l>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.specialPara"/>
</content>

Schema Declaration

element stage { attribute type { text }?, macro.specialPara }

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<time>

<time> (time) contains a phrase defining a time of day in any format. [3.6.4. Dates and Times]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.calendarSystem

@calendar

att.cmc

@generatedBy

att.datable

att.datable.w3c

@when

@from

@to

att.typed

@type

from from⚓︎

Status
Optional

to to⚓︎

Status
Optional

extent extent⚓︎

Status
Optional

Member of | model.dateLike

Contained by

core: abbr add addrLine author bibl date del desc editor email foreign head hi item l label name note num p pubPlace publisher q ref resp speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell

linking: ab seg

textstructure: byline closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain

core: abbr add address cb date del email foreign gap graphic hi lb milestone name note num pb ptr q ref time title unclear

derived-module-tei_tite: b colShift i smcap sub sup ul

figures: figure formula

gaiji: g

linking: seg

transcr: handShift

character data

Example

As he sat smiling, the
 quarter struck — <time when="11:45:00">the quarter to twelve</time>.

Show all ⚓︎

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>

Schema Declaration

element time
{
   attribute from { text }?,
   attribute to { text }?,
   attribute extent { text }?,
   ( text | model.gLike | model.phrase | model.global )*
}

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

§

Home

<unclear>

<unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [12.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions]

Module | core

Attributes

att.global

@xml:id

@n

@xml:lang

@xml:space

att.global.change

@change

att.global.facs

@facs

att.global.linking

@corresp

@synch

@sameAs

@copyOf

@next

@prev

@exclude

@select

att.global.rendition

@rend

@style

att.global.responsibility

@cert

@resp

att.global.source

@source

att.cmc

@generatedBy

hand hand⚓︎

Status
Optional

reason reason⚓︎
indicates why the material is hard to transcribe.

Status
Optional

Datatype
1–∞ occurrences of teidata.enumerated separated by whitespace

Suggested values include:

illegible

(illegible)

inaudible

(inaudible)

faded

(faded)

background_noise

(background noise)

eccentric_ductus

(eccentric ductus) indicates illegibility due to an unusual, awkward, or incompetent execution of a glyph or glyphs

<div>
 <head>Rx</head>
 <p>500 mg <unclear reason="illegible">placebo</unclear>
 </p>
</div>

Show all ⚓︎

Note

One or more words may be used to describe the reason; usually each word will refer to a single cause.

agent agent⚓︎

Status
Optional

Member of | model.pPart.transcriptional

Contained by

core: abbr add addrLine author bibl date del editor email foreign head hi item l label lg name note num p pubPlace publisher q ref speaker stage time title unclear

derived-module-tei_tite: b i smcap sub sup ul

figures: cell

linking: ab seg

textstructure: byline closer dateline docAuthor docDate docEdition docImprint opener salute signed titlePart trailer

May contain

core: abbr add address bibl cb cit date del desc email foreign gap graphic hi l label lb lg list listBibl milestone name note num pb ptr q ref stage time title unclear

derived-module-tei_tite: b colShift i ornament smcap sub sup ul

figures: figure formula table

gaiji: g

linking: seg

textstructure: floatingText

transcr: handShift

character data

Note

The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 22. Certainty, Precision, and Responsibility.

The <damage>, gap, del, unclear and <supplied> elements may be closely allied in use. 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 hand attribute points to a definition of the hand concerned, as further discussed in section 12.3.2.1. Document Hands.

Example

<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>

Show all ⚓︎

Content model

<content>
 <macroRef key="macro.paraContent"/>
</content>

Schema Declaration

element unclear
{
   attribute hand { text }?,
   attribute reason
   {
      list
      {
         (
            "illegible"
          | "inaudible"
          | "faded"
          | "background_noise"
          | "eccentric_ductus"
          | teidata.enumerated
         )+
      }
   }?,
   attribute agent { text }?,
   macro.paraContent
}

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

TEI Tite

A recommendation for off-site text encoding

7. Reference Systems

Previous 6. Phrase-level Features

Next Appendix A TEI Tite and the Best Practices for TEI in Libraries

Home

Encode page breaks (pb) at the start of each page, and encode breaks even for blank pages. If the page is numbered, include the page number as the value of the n attribute and, again, no matter where the page number is printed on the page, place the pb element at the ‘top.’

If marking column breaks, follow the same rules as for page breaks. Column breaks are imagined to appear at the top of the column, at the beginning of the column's text. The colShift element exists to record a change in columnar layout. If such a change occurs, mark the beginning of the new layout with colShift and supply the new number of columns as the value for the n attribute.

For many applications, it will not be important to capture line breaks in ordinary prose text, but in cases where they are purposeful (such as the layout of acrostics, or where a word is broken across a line), they should be captured using the lb element, placing it at the start of each line.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

TEI Tite

A recommendation for off-site text encoding

Appendix A TEI Tite and the Best Practices for TEI in Libraries

Next Appendix B Formal specification

Home

The Best Practices for TEI in Libraries ("BP") creates common definitions of ‘levels of encoding’ based on depth of markup applied. Because the levels of encoding provide a tremendously useful common set of terms, it's helpful to situate TEI Tite according to them.

Mapped to BP levels, TEI Tite would sit between Level 3 and Level 4: it requires use of all the elements from Level 3 plus additional ones, but requires fewer elements than Level 4. Relative to Level 3, ‘Simple Analysis,’ Tite

encourages the use of the rend attribute on typographically distinct text (marked with hi), implicitly, through the provision of convenience elements (i, b, etc.), and it provides the title and foreign elements for semantic markup of typographically distinct phrases; in level 3, the rend attribute is optional, and title and foreign are not provided

provides some genre-specific elements in addition to those for verse that level three also provides (lg, l): sp, speaker, and stage for drama, the colShift element especially for newspapers.

The most useful comparison for Tite is to Level 4 (‘Basic Content Analysis’), provides the most useful comparison. The folowing items represent instances where Tite is less ambitious than Level 4:

except in the case of the foreign and title elements, it is preferred in Tite to describe typographical changes physically, rather than semantically; Tite uses i, b, etc. where level four uses <emph>, <gloss>, <term>

Tite provides only q for quoted material, where level four is more discriminating, using <quote>, <said>, <mentioned>, <soCalled>

Tite doesn't provide elements for editorial intervention, as level four does: <choice>, <sic>, <corr>

Tite doesn't provide entity-specific naming elements, like <persName>, <placeName>, <orgName> and their list- (<listPerson>, etc.) forms

Bringing Tite-encoded documents up to BP Level 4 would simply require application of additional markup, not significant reworking of markup, and in that way Tite is compatible with the BP.

Do also keep in mind that Tite lacks both the <teiHeader> and root <TEI> element used in TEI-conformant documents.

TEI Guidelines . This page generated on 2026-07-28T11:29:48Z.

TEI Tite

A recommendation for off-site text encoding

Perry Trolard, for the TEI Consortium

TEI Tite

A recommendation for off-site text encoding

Perry Trolard, for the TEI Consortium

Version 1.1 — September 2011

Information about this book

Title statement

TEI TiteA recommendation for off-site text encoding

Perry Trolard

Publication

Publisher

TEI Consortium

Availability

Distributed under a Creative Commons Attribution-ShareAlike 3.0 Unported License

Copyright 2013 TEI Consortium.

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright holder or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.

TEI material can be licensed differently depending on the use you intend to make of it. Hence it is made available under both the CC+BY and BSD-2 licences. The CC+BY licence is generally appropriate for usages which treat TEI content as data or documentation. The BSD-2 licence is generally appropriate for usage of TEI content in a software environment. For further information or clarification, please contact the TEI Consortium.

Source

Written as the principal product of an independent study under John Unsworth at the Graduate School of Library and Information Science, University of Illinois at Urbana-Champaign, May 2009.

This electronic document is the original, but it primarily synthesizes work done at the

University of Michigan Digital Library Production Service,

University of Virginia Digital Library Production Service,

and the California Digital Library

and represented in their documents

Minimum standards for text capture,

Text Encoding Guidelines for Keyboarding Vendors,

and CDL TEI Base Encoding Guidelines.

, respectively.