TEI Tite — A recommendation for off-site text encoding
Perry Trolard, for the TEI Consortium
Version 1.1 — September 2011

Table of contents

1 Introduction

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, cols 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.

2 General Requirements

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.

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.

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;).

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.

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.

3 Global 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.

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.

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>

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.

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

4 Types of Text

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.

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 (formatted yyyy-mm-dd) 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

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.

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.

4.4 Newspapers

Tite includes the elements cols 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.

5 Block-level Features

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.

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.

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.

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.

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>

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

6 Phrase-level Features

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.

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.

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.

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

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.

7 Reference Systems

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 cols element exists to record a change in columnar layout. If such a change occurs, mark the beginning of the new layout with cols and supply the new number of columns as the value for the n attribute.

If line breaks are to be captured, use the lb element.

Appendices

TEI Tite and the Best Practices for TEI in Libraries

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

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:

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.

Formal specification

Schema tei_tite: Elements

<ab>

<ab> (anonymous block) contains any arbitrary component-level unit of text, acting as an anonymous container for phrase or inter level elements analogous to, but without the semantic baggage of, a paragraph. [16.3. ]
Modulelinking — Formal specification
Member of
Contained by
May contain
Declaration
element ab { macro.paraContent }
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>
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.

<abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.5.5. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element abbr { att.global.attributes, att.typed.attributes, macro.phraseSeq }
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>
Example
<choice>
 <abbr>SPQR</abbr>
 <expan>senatus populusque romanorum</expan>
</choice>
Note

The abbr tag is not required; if appropriate, the encoder may transcribe abbreviations in the source text silently, without tagging them. If abbreviations are not transcribed directly but expanded silently, then the TEI header should so indicate.

<add>

<add> (addition) contains letters, words, or phrases inserted in the text by an author, scribe, annotator, or corrector. [3.4.3. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.transcriptional (@hand, @status, @cause, @seq) att.typed (@type)
Member of
Contained by
May contain
Declaration
element add
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.typed.attributes,
   macro.paraContent
}
Example
The story I am going to relate is true as to
its main facts, and as to the consequences <add place="above">of
these facts</add> from which this tale takes its title.
Note

The add element should not be used for additions made by editors or encoders. In these cases, either the <corr> or <supplied> element should be used.

<address>

<address> contains a postal address, for example of a publisher, an organization, or an individual. [3.5.2. 2.2.4. 3.11.2.3. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
derived-module-tei_tite: cols
figures: figure
Declaration
element address
{
   att.global.attributes,
   ( model.global*, ( ( model.addrPart ), model.global* )+ )
}
Example
<address>
 <street>via Marsala 24</street>
 <postCode>40126</postCode>
 <name>Bologna</name>
 <name n="I">Italy</name>
</address>
Example
<address>
 <addrLine>Computing Center, MC 135</addrLine>
 <addrLine>P.O. Box 6998</addrLine>
 <addrLine>Chicago, IL 60680</addrLine>
 <addrLine>USA</addrLine>
</address>
Note

This element should be used for postal addresses only. Within it, the generic element addrLine may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc.

<addrLine>

<addrLine> (address line) contains one line of a postal address. [3.5.2. 2.2.4. 3.11.2.3. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
core: address
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element addrLine { att.global.attributes, macro.phraseSeq }
Example
<address>
 <addrLine>Computing Center, MC 135</addrLine>
 <addrLine>P.O. Box 6998</addrLine>
 <addrLine>Chicago, IL</addrLine>
 <addrLine>60680 USA</addrLine>
</address>
Note

Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an address element directly but may be wrapped within an addrLine if they form part of the printed address in some source text.

<argument>

<argument> contains a formal list or prose description of the topics addressed by a subdivision of a text. [4.2. 4.6. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
derived-module-tei_tite: cols ornament
figures: figure table
linking: ab
textstructure: floatingText
Declaration
element argument
{
   att.global.attributes,
   ( ( model.global | model.headLike )*, ( ( model.common ), model.global* )+ )
}
Example
<argument>
 <p>Monte Video — Maldonado — Excursion
   to R Polanco — Lazo and Bolas — Partridges —
   Absence of Trees — Deer — Capybara, or River Hog —
   Tucutuco — Molothrus, cuckoo-like habits — Tyrant
   Flycatcher — Mocking-bird — Carrion Hawks —
   Tubes formed by Lightning — House struck</p>
</argument>
Note

Often contains either a list or a paragraph

<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.11.2.2. 2.2.1. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
core: bibl
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element author { att.global.attributes, macro.phraseSeq }
Example
<author>British Broadcasting Corporation</author>
<author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
<author>Anonymous</author>
<author>Bill and Melinda Gates Foundation</author>
<author>
 <persName>Beaumont, Francis</persName> and
<persName>John Fletcher</persName>
</author>
<author>
 <orgName key="BBC">British Broadcasting
   Corporation</orgName>: Radio 3 Network
</author>
Note

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

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

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

<b> [http://www.tei-c.org/ns/tite/1.0]

<b> (bold) for capturing typographical feature: bold glyphs.
Modulederived-module-tei_tite
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element b { att.global.attributes, macro.paraContent }

<back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. 4. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
textstructure: floatingText text
May contain
Declaration
element back
{
   att.global.attributes,
   (
      ( model.frontPart | model.pLike.front | model.global )*,
      (
         (
            (
               ( model.div1Like ),
               ( model.frontPart | model.div1Like | model.global )*
            )
          | (
               ( model.divLike ),
               ( model.frontPart | model.divLike | model.global )*
            )
         )?
      ),
      ( ( ( model.divBottomPart ), ( model.divBottomPart | model.global )* )? )
   )
}
Example
<back>
 <div1 type="appendix">
  <head>The Golden Dream or, the Ingenuous Confession</head>
  <p>To shew the Depravity of human Nature </p>
 </div1>
 <div1 type="epistle">
  <head>A letter from the Printer, which he desires may be inserted</head>
  <salute>Sir.</salute>
  <p>I have done with your Copy, so you may return it to the Vatican, if you please </p>
 </div1>
 <div1 type="advert">
  <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr
     Newbery's at the Bible and Sun in St Paul's Church-yard.</head>
  <list>
   <item n="1">The Christmas Box, Price 1d.</item>
   <item n="2">The History of Giles Gingerbread, 1d.</item>
   <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,
       10 Vol, Pr. bound 1l.</item>
  </list>
 </div1>
 <div1 type="advert">
  <head>
   <hi rend="center">By the KING's Royal Patent,</hi> Are sold by J. NEWBERY, at the
     Bible and Sun in St. Paul's Church-Yard.</head>
  <list>
   <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c.
       2s. 6d</item>
   <item n="2">Dr. Hooper's Female Pills, 1s.</item>
  </list>
 </div1>
</back>
Note

The content model of back matter is identical to that of front matter, reflecting the facts of cultural history.

<bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. 2.2.7. 15.3.2. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.declarable (@default) att.typed (@type) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Declaration
element bibl
{
   att.global.attributes,
   att.declarable.attributes,
   att.typed.attributes,
   att.sortable.attributes,
   att.docStatus.attributes,
   (
      text
    | model.gLikemodel.highlightedmodel.pPart.datamodel.pPart.editmodel.segLikemodel.ptrLikemodel.biblPartmodel.global
   )*
}
Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
1990)</bibl>
Example
<bibl>
 <title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
 <date>1968</date>.
</bibl>
Example
<bibl type="article" subtype="book_chapter" xml:id="carlin_2003">
 <author>
  <name>
   <surname>Carlin</surname>
     (<forename>Claire</forename>)</name>
 </author>,
<title level="a">The Staging of Impotence : France’s last
   congrès</title> dans
<bibl type="monogr">
  <title level="m">Theatrum mundi : studies in honor of Ronald W.
     Tobin</title>, éd.
 <editor>
   <name>
    <forename>Claire</forename>
    <surname>Carlin</surname>
   </name>
  </editor> et
 <editor>
   <name>
    <forename>Kathleen</forename>
    <surname>Wine</surname>
   </name>
  </editor>,
 <pubPlace>Charlottesville, Va.</pubPlace>,
 <publisher>Rookwood Press</publisher>,
 <date when="2003">2003</date>.
 </bibl>
</bibl>
Note

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

<body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
textstructure: floatingText text
May contain
Declaration
element body
{
   att.global.attributes,
   (
      model.global*,
      ( ( model.divTop ), ( model.global | model.divTop )* )?,
      ( ( model.divGenLike ), ( model.global | model.divGenLike )* )?,
      (
         ( ( model.divLike ), ( model.global | model.divGenLike )* )+
       | ( ( model.div1Like ), ( model.global | model.divGenLike )* )+
       | (
            ( ( model.common ), model.global* )+,
            (
               ( ( model.divLike ), ( model.global | model.divGenLike )* )+
             | ( ( model.div1Like ), ( model.global | model.divGenLike )* )+
            )?
         )
      ),
      ( ( model.divBottom ), model.global* )*
   )
}
Example
<body>
 <l>Nu scylun hergan hefaenricaes uard</l>
 <l>metudæs maecti end his modgidanc</l>
 <l>uerc uuldurfadur sue he uundra gihuaes</l>
 <l>eci dryctin or astelidæ</l>
 <l>he aerist scop aelda barnum</l>
 <l>heben til hrofe haleg scepen.</l>
 <l>tha middungeard moncynnæs uard</l>
 <l>eci dryctin æfter tiadæ</l>
 <l>firum foldu frea allmectig</l>
 <trailer>primo cantauit Cædmon istud carmen.</trailer>
</body>

<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. 4.5. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
textstructure: docAuthor
transcr: handShift
Declaration
element byline
{
   att.global.attributes,
   ( text | model.gLike | model.phrase | docAuthor | model.global )*
}
Example
<byline>Written by a CITIZEN who continued all the
while in London. Never made publick before.</byline>
Example
<byline>Written from her own MEMORANDUMS</byline>
Example
<byline>By George Jones, Political Editor, in Washington</byline>
Example
<byline>BY
<docAuthor>THOMAS PHILIPOTT,</docAuthor>
Master of Arts,
(Somtimes)
Of Clare-Hall in Cambridge.</byline>
Note

The byline on a title page may include either the name or a description for the document's author. Where the name is included, it may optionally be tagged using the docAuthor element.

<cb>

<cb> (column break) marks the boundary between one column of a text and the next in a standard reference system. [3.10.3. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type) att.edition (@ed, @edRef)
Member of
Contained by
May containEmpty element
Declaration
element cb
{
   att.global.attributes,
   att.typed.attributes,
   att.edition.attributes,
   empty
}
Example

Markup of an early English dictionary printed in two columns:

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

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

<cell>

<cell> contains one cell of a table. [14.1.1. ]
Modulefigures — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.tableDecoration (@role, @rows, @cols)
Member of
Contained by
figures: row
May contain
Declaration
element cell
{
   att.global.attributes,
   att.tableDecoration.attributes,
   macro.paraContent
}
Example
<row>
 <cell role="label">General conduct</cell>
 <cell role="data">Not satisfactory, on account of his great unpunctuality
   and inattention to duties</cell>
</row>

<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. 4.3.1. 9.3.5.1. ]
Modulecore — Formal specification
Member of
Contained by
May contain
derived-module-tei_tite: cols
figures: figure
textstructure: floatingText
Declaration
element cit
{
   (
      model.qLikemodel.egLikemodel.biblLikemodel.ptrLikemodel.globalmodel.entryPart
   )+
}
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>
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>

<closer>

<closer> groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. 4.2. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
textstructure: dateline salute signed
transcr: handShift
Declaration
element closer
{
   att.global.attributes,
   (
      text
    | model.gLikesigneddatelinesalutemodel.phrasemodel.global
   )*
}
Example
<div type="letter">
 <p> perhaps you will favour me with a sight of it when convenient.</p>
 <closer>
  <salute>I remain, &amp;c. &amp;c.</salute>
  <signed>H. Colburn</signed>
 </closer>
</div>
Example
<div type="chapter">
 <p> and his heart was going like mad and yes I said yes I will Yes.</p>
 <closer>
  <dateline>
   <name type="place">Trieste-Zürich-Paris,</name>
   <date>1914–1921</date>
  </dateline>
 </closer>
</div>

<cols> [http://www.tei-c.org/ns/tite/1.0]

<cols> (columns) with the ‘n’ attribute (denoting new number of columns) is used to mark where a document changes columnar layout.
Modulederived-module-tei_tite
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
edindicates the edition or version in which the change in columnar layout is located at this point
Status Optional
Datatype data.code
Member of
Contained by
May containEmpty element
Declaration
element cols
{
   att.global.attributes,
   attribute [http://www.tei-c.org/ns/tite/1.0]ed { data.code }?,
   empty
}

<date>

<date> contains a date in any format. [3.5.4. 2.2.4. 2.5. 3.11.2.3. 15.2.3. 13.3.6. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type) att.datable.w3c (@when, @from, @to)
Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element date
{
   att.global.attributes,
   att.datable.w3c.attribute.when,
   att.datable.w3c.attribute.from,
   att.datable.w3c.attribute.to,
   att.typed.attributes,
   ( text | model.gLike | model.phrase | model.global )*
}
Example
<date when="1980-02">early February 1980</date>
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>
Example
<date when="1990-09">September 1990</date>

<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. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
core: lg list
figures: table
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element dateline { att.global.attributes, macro.phraseSeq }
Example
<dateline>Walden, this 29. of August 1592</dateline>
Example
<div type="chapter">
 <p> and his heart was going like mad and yes I said yes I will Yes.</p>
 <closer>
  <dateline>
   <name type="place">Trieste-Zürich-Paris,</name>
   <date>1914–1921</date>
  </dateline>
 </closer>
</div>

<del>

<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, annotator, or corrector. [3.4.3. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.transcriptional (@hand, @status, @cause, @seq) att.typed (@type)
Member of
Contained by
May contain
Declaration
element del
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.typed.attributes,
   macro.paraContent
}
Example
<l>
 <del rend="overtyped">Mein</del> Frisch <del rend="overstrike" type="primary">schwebt</del>
weht der Wind
</l>
Example
<del rend="overstrike">
 <gap reason="illegible" quantity="5" unit="character"/>
</del>
Note

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

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

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

There is a clear distinction in the TEI between del, which is a statement of the the or a later scribe's intent to cancel or remove text, and elements such as gap or unclear which signal the editor's decision to omit or inability to read the text remaining. See further sections 11.3.1.7. and, for the close association of the del tag with the gap, <damage>, unclear and <supplied> elements (the latter three tags available when using the additional tagset for transcription of primary sources), 11.3.3.2. .

The del tag should not be used for deletions made by editors or encoders. In these cases, either <corr>, <surplus> or gap should be used.

<desc>

<desc> (description) contains a brief description of the object documented by its parent element, including its intended usage, purpose, or application where this is appropriate. [22.4.4. 22.4.5. 22.4.6. 22.4.7. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element desc { att.global.attributes, macro.limitedContent }
Example
<desc>contains a brief description of the purpose and application for an element, attribute,
attribute value, class, or entity.</desc>
Note

TEI convention requires that this be expressed as a finite clause, begining with an active verb.

<div1>

<div1> (level-1 text division) contains a first-level subdivision of the front, body, or back of a text. [4.1.2. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
textstructure: back body front
May contain
Declaration
element div1
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( model.divTop | model.global )*,
      (
         (
            ( ( model.div2Like | model.divGenLike ), model.global* )+
          | (
               ( ( model.common ), model.global* )+,
               ( ( model.div2Like | model.divGenLike ), model.global* )*
            )
         ),
         ( ( model.divBottom ), model.global* )*
      )?
   )
}
Example
<div1 xml:id="levi" n="I" type="part">
 <head>Part I: Of Man </head>
 <div2 xml:id="levi1" n="1" type="chapter">
  <head>Chap. I. Of Sense </head>
  <p>Concerning the Thoughts of man... </p>
 </div2>
</div1>
<div1 xml:id="levii" n="II" type="part">
 <head>Part II: Of Common-Wealth</head>
</div1>
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

<div2>

<div2> (level-2 text division) contains a second-level subdivision of the front, body, or back of a text. [4.1.2. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
textstructure: div1
May contain
Declaration
element div2
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( model.divTop | model.global )*,
      (
         (
            ( ( model.div3Like | model.divGenLike ), model.global* )+
          | (
               ( ( model.common ), model.global* )+,
               ( ( model.div3Like | model.divGenLike ), model.global* )*
            )
         ),
         ( ( model.divBottom ), model.global* )*
      )?
   )
}
Example
<div1 n="2" type="part">
 <head>The Second Partition:
   The Cure of Melancholy</head>
 <div2 n="2.1" type="section">
  <div3 n="2.1.1" type="member">
   <div4 n="2.1.1.1" type="subsection">
    <head>Unlawful Cures rejected.</head>
    <p>Inveterate melancholy, howsoever it may seem to
         be a continuate, inexorable disease, hard to be
         cured, accompanying them to their graves most part
         (as <ref target="#a">Montanus</ref> observes), yet many
         times it may be helped...
    </p>
   </div4>
  </div3>
 </div2>
 <div2 n="2.2" type="section">
  <div3 n="2.2.1" type="member">
   <head>Sect. II. Memb. I</head>
   <p/>
  </div3>
 </div2>
 <div2 n="2.3" type="section">
  <div3 n="2.3.1" type="member">
   <head>Sect. III. Memb. I</head>
   <p/>
  </div3>
 </div2>
</div1>
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

<div3>

<div3> (level-3 text division) contains a third-level subdivision of the front, body, or back of a text. [4.1.2. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
textstructure: div2
May contain
Declaration
element div3
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( model.divTop | model.global )*,
      (
         (
            ( ( model.div4Like | model.divGenLike ), model.global* )+
          | (
               ( ( model.common ), model.global* )+,
               ( ( model.div4Like | model.divGenLike ), model.global* )*
            )
         ),
         ( ( model.divBottom ), model.global* )*
      )?
   )
}
Example
<div2 n="2.2" type="section">
 <div3 n="2.2.1" type="member">
  <head>Sect. II. Memb. I</head>
  <p/>
 </div3>
 <div3 n="2.2.2" type="member">
  <head>Memb. II Retention and Evacuation rectified.</head>
  <p/>
 </div3>
 <div3 n="2.2.3" type="member">
  <head>Memb. III Ayr rectified. With a digression of the Ayr.</head>
  <p/>
 </div3>
</div2>
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

<div4>

<div4> (level-4 text division) contains a fourth-level subdivision of the front, body, or back of a text. [4.1.2. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
textstructure: div3
May contain
Declaration
element div4
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( model.divTop | model.global )*,
      (
         (
            ( ( model.div5Like | model.divGenLike ), model.global* )+
          | (
               ( ( model.common ), model.global* )+,
               ( ( model.div5Like | model.divGenLike ), model.global* )*
            )
         ),
         ( ( model.divBottom ), model.global* )*
      )?
   )
}
Example
<div3 n="2.2.1" type="member">
 <head>Sect. II. Memb. I</head>
 <div4 n="2.2.1.1" type="subsection">
  <head>Subsect I. — Dyet rectified in substance.</head>
  <p>Diet, <term xml:lang="grc">diaitotiku</term>, <term xml:lang="la">victus</term> or
     living </p>
 </div4>
 <div4 n="2.2.2.1" type="subsection">
  <head>Subsect II. — Dyet rectified in quantity.</head>
  <p>Man alone, saith Cardan, eates and drinks without appetite, and useth all his pleasures
     without necessity </p>
 </div4>
</div3>
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

<div5>

<div5> (level-5 text division) contains a fifth-level subdivision of the front, body, or back of a text. [4.1.2. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
textstructure: div4
May contain
Declaration
element div5
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( model.divTop | model.global )*,
      (
         (
            ( ( model.div6Like | model.divGenLike ), model.global* )+
          | (
               ( ( model.common ), model.global* )+,
               ( ( model.div6Like | model.divGenLike ), model.global* )*
            )
         ),
         ( ( model.divBottom ), model.global* )*
      )?
   )
}
Example
<div2 type="chapter">
 <head>Recipes</head>
 <head>Chapter VI.</head>
 <div3>
  <head>Fruit and vegetable soups</head>
  <p>...</p>
  <div4>
   <head>Stocks for all kinds of soups</head>
   <div5 type="recipe">
    <head>Rich strong stock</head>
   </div5>
   <div5 type="recipe">
    <head>Medium Stock</head>
   </div5>
  </div4>
  <div4 type="recipe">
   <head>Apple soup</head>
   <div5>
    <head>Ingredients</head>
    <list>
     <item>2 lbs. of good boiling apples,</item>
     <item>3/4 teaspoonful of white pepper,</item>
     <item>6 cloves,</item>
     <item>cayenne or ginger to taste,</item>
     <item>3 quarts of medium stock</item>
    </list>
   </div5>
   <div5>
    <head>Mode</head>
    <p>Peel and quarter the apples taking out their cores; put them into
         the stock, stew them gently till tender, Rub the whole through a
         strainer, add the seasoning. give it one boil up, and serve.</p>
   </div5>
   <div5>
    <head>Time</head>
    <p>1 hour.</p>
   </div5>
   <div5>
    <head>Average cost</head>
    <p>per quart, 1s.</p>
   </div5>
   <div5>
    <head>Seasonable</head>
    <p>from September to December.</p>
   </div5>
   <div5>
    <head>Sufficient</head>
    <p> for 10 persons</p>
   </div5>
   <div5>
    <head>The apple</head>
    <p>This useful fruit is mentioned in Holy Writ; and Homer describes it
         as valuable in his time... As a food, the apple cannot be considered
         to rank high, as more than the half of it consists of water, and
         the rest of its properties are not the most nourishing. It is
         however a useful adjunct to other kinds of food, and, when cooked, is
         esteemed as slightly laxative.</p>
   </div5>
  </div4>
  <div4 type="recipe">
   <head>Artichoke (Jerusalem) soup</head>
   <p>...</p>
  </div4>
 </div3>
</div2>
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

<div6>

<div6> (level-6 text division) contains a sixth-level subdivision of the front, body, or back of a text. [4.1.2. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
textstructure: div5
May contain
Declaration
element div6
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( model.divTop | model.global )*,
      (
         (
            ( ( model.div7Like | model.divGenLike ), model.global* )+
          | (
               ( ( model.common ), model.global* )+,
               ( ( model.div7Like | model.divGenLike ), model.global* )*
            )
         ),
         ( ( model.divBottom ), model.global* )*
      )?
   )
}
Example
<div2 type="chapter">
 <head>Recipes</head>
 <head>Chapter VI.</head>
 <div3>
  <head>Fruit and vegetable soups</head>
  <p>...</p>
  <div4>
   <head>Stocks for all kinds of soups</head>
   <div5 type="recipe">
    <head>Rich strong stock</head>
    <div6>
     <head>Ingredients</head>
     <list>
      <item>4 lbs of shin of beef,</item>
      <item>4 lbs of knuckle of veal,</item>
      <item>4 quarts of water</item>
     </list>
    </div6>
    <div6>
     <head>Mode</head>
     <p>Line a delicately clean stewpan... Strain through a very
           fine hair sieve, or tammy, and it will be fit for use</p>
    </div6>
    <div6>
     <head>Time</head>
     <p>5 hours.</p>
    </div6>
    <div6>
     <head>Average cost</head>
     <p>1s 3d. per quart</p>
    </div6>
   </div5>
   <div5 type="recipe">
    <head>Medium Stock</head>
   </div5>
  </div4>
 </div3>
</div2>
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

<div7>

<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. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
textstructure: div6
May contain
Declaration
element div7
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( model.divTop | model.global )*,
      (
         ( ( model.common ), model.global* )+,
         ( ( model.divBottom ), model.global* )*
      )?
   )
}
Example
<div2 type="chapter">
 <head>Recipes</head>
 <head>Chapter VI.</head>
 <div3>
  <head>Fruit and vegetable soups</head>
  <p>...</p>
  <div4>
   <head>Stocks for all kinds of soups</head>
   <div5 type="recipe">
    <head>Asparagus soup</head>
    <div6 type="altRecipe">
     <head>I.</head>
     <div7>
      <head>Ingredients</head>
      <list>
       <item> ...</item>
      </list>
     </div7>
     <div7>
      <head>Mode</head>
      <p>Put the beef, cut into pieces and rolled in flour, into a
             stewpan...</p>
     </div7>
    </div6>
    <div6 type="altRecipe">
     <head>II.</head>
     <div7>
      <head>Ingredients</head>
      <list>
       <item> ...</item>
      </list>
     </div7>
     <div7>
      <head>Mode</head>
      <p>Boil the peas, and rub them through a sieve; add the gravy...</p>
     </div7>
    </div6>
   </div5>
  </div4>
 </div3>
</div2>
Note

any sequence of low-level structural elements, e.g., paragraphs (p), lists (list), or examples (<eg> or <egXML>).

<docAuthor>

<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. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element docAuthor { att.global.attributes, macro.phraseSeq }
Example
<titlePage>
 <docTitle>
  <titlePart>Travels into Several Remote Nations of the World, in Four
     Parts.</titlePart>
 </docTitle>
 <byline> By <docAuthor>Lemuel Gulliver</docAuthor>, First a Surgeon,
   and then a Captain of several Ships</byline>
</titlePage>
Note

The document author's name often occurs within a byline, but the docAuthor element may be used whether the byline element is used or not.

<docDate>

<docDate> (document date) contains the date of a document, as given (usually) on a title page. [4.6. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
whengives the value of the date in standard form, i.e. YYYY-MM-DD.
Status Optional
Datatype data.temporal.w3c
Values a date in one of the formats specified in XML Schema Part 2: Datatypes Second Edition
Note

For simple dates, the when attribute should give the Gregorian or proleptic Gregorian date in the form (YYYY-MM-DD) specified by XML Schema Part 2.

Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element docDate
{
   att.global.attributes,
   attribute when { data.temporal.w3c }?,
   macro.phraseSeq
}
Example
<docImprint>Oxford, Clarendon Press, <docDate>1987</docDate>
</docImprint>
Note

Cf. the general date element in the core tag set. This specialized element is provided for convenience in marking and processing the date of the documents, since it is likely to require specialized handling for many applications.

<docEdition>

<docEdition> (document edition) contains an edition statement as presented on a title page of a document. [4.6. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
textstructure: back front titlePage
May contain
Declaration
element docEdition { att.global.attributes, macro.paraContent }
Example
<docEdition>The Third edition Corrected</docEdition>
Note

Cf. the <edition> element of bibliographic citation. As usual, the shorter name has been given to the more frequent element.

<docImprint>

<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. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
textstructure: back front titlePage
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
textstructure: docDate
transcr: handShift
Declaration
element docImprint
{
   att.global.attributes,
   (
      text
    | model.gLikemodel.phrasepubPlacedocDatepublishermodel.global
   )*
}
Example
<docImprint>Oxford, Clarendon Press, 1987</docImprint>
Imprints may be somewhat more complex:
<docImprint>
 <pubPlace>London</pubPlace>
Printed for <name>E. Nutt</name>,
at
<pubPlace>Royal Exchange</pubPlace>;
<name>J. Roberts</name> in
<pubPlace>wick-Lane</pubPlace>;
<name>A. Dodd</name> without
<pubPlace>Temple-Bar</pubPlace>;
and <name>J. Graves</name> in
<pubPlace>St. James's-street.</pubPlace>
 <date>1722.</date>
</docImprint>
Note

Cf. the <imprint> element of bibliographic citations. As with title, author, and editions, the shorter name is reserved for the element likely to be used more often.

<docTitle>

<docTitle> (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
textstructure: back front titlePage
May contain
derived-module-tei_tite: cols
figures: figure
textstructure: titlePart
Declaration
element docTitle
{
   att.global.attributes,
   ( model.global*, ( titlePart, model.global* )+ )
}
Example
<docTitle>
 <titlePart type="main">The DUNCIAD, VARIOURVM.</titlePart>
 <titlePart type="sub">WITH THE PROLEGOMENA of SCRIBLERUS.</titlePart>
</docTitle>

<editor>

<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.11.2.2. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
core: bibl
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element editor { att.global.attributes, macro.phraseSeq }
Example
<editor>Eric Johnson</editor>
<editor role="illustrator">John Tenniel</editor>
Note

A consistent format should be adopted.

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.

<email>

<email> (electronic mail address) contains an e-mail address identifying a location to which e-mail messages can be delivered. [3.5.2. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element email { att.global.attributes, macro.phraseSeq }
Example
<email>membership@tei-c.org</email>
Note

The format of a modern Internet email address is defined in RFC 2822

<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. 4.2. 4.6. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
derived-module-tei_tite: cols ornament
figures: figure table
linking: ab
textstructure: floatingText
Declaration
element epigraph { att.global.attributes, ( model.common | model.global )* }
Example
<epigraph xml:lang="la">
 <cit>
  <bibl>Lucret.</bibl>
  <quote>
   <l part="F">petere inde coronam,</l>
   <l>Vnde prius nulli velarint tempora Musae.</l>
  </quote>
 </cit>
</epigraph>

<figure>

<figure> groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. ]
Modulefigures — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
May contain
Declaration
element figure
{
   att.global.attributes,
   att.typed.attributes,
   (
      model.headLikemodel.common
    | figDesc
    | model.graphicLikemodel.globalmodel.divBottomPart
   )*
}
Example
<figure>
 <head>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>
 <graphic url="http://www.example.org/fig1.png" scale="0.5"/>
</figure>

<floatingText>

<floatingText> 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. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
May contain
derived-module-tei_tite: cols
figures: figure
textstructure: back body front group
Declaration
element floatingText
{
   att.global.attributes,
   att.typed.attributes,
   (
      model.global*,
      ( front, model.global* )?,
      ( body | group ),
      model.global*,
      ( back, model.global* )?
   )
}
Example
<body>
 <div type="scene">
  <sp>
   <p>Hush, the players begin...</p>
  </sp>
  <floatingText type="pwp">
   <body>
    <div type="act">
     <sp>
      <l>In Athens our tale takes place ....</l>
     </sp>
    </div>
   </body>
  </floatingText>
  <sp>
   <p>Now that the play is finished ...</p>
  </sp>
 </div>
</body>
Note

A floating text has the same content as any other and may thus be interrupted by another floating text, or contain a group of tesselated texts.

<foreign>

<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element foreign { att.global.attributes, macro.phraseSeq }
Example
This is
heathen Greek to you still? Your <foreign xml:lang="la">lapis
philosophicus</foreign>?
Note

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

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

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

<formula>

<formula> contains a mathematical or other formula. [14.2. ]
Modulefigures — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
core: graphic hi
derived-module-tei_tite: b i smcap sub sup ul
figures: formula
Declaration
element formula
{
   att.global.attributes,
   ( text | model.graphicLike | model.hiLike )*
}
Example
<formula notation="tex">$E=mc^2$</formula>
Example
<formula notation="none">E=mc<hi rend="sup">2</hi>
</formula>
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>

<front>

<front> (front matter) contains any prefatory matter (headers, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. 4. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
textstructure: floatingText text
May contain
Declaration
element front
{
   att.global.attributes,
   (
      ( model.frontPart | model.pLike.front | model.global )*,
      (
         (
            (
               ( model.div1Like ),
               ( model.frontPart | model.div1Like | model.global )*
            )
          | (
               ( model.divLike ),
               ( model.frontPart | model.divLike | model.global )*
            )
         )?
      ),
      ( ( ( model.divBottomPart ), ( model.divBottomPart | model.global )* )? )
   )
}
Example
<front>
 <epigraph>
  <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis
     vidi in ampulla pendere, et cum illi pueri dicerent:
  <q xml:lang="grc">Sibylla ti weleis</q>; respondebat
     illa: <q xml:lang="grc">apowanein welo.</q>
  </quote>
 </epigraph>
 <div type="dedication">
  <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>
  </p>
 </div>
</front>
Example
<front>
 <div type="dedication">
  <p>To our three selves</p>
 </div>
 <div type="preface">
  <head>Author's Note</head>
  <p>All the characters in this book are purely imaginary, and if the
     author has used names that may suggest a reference to living persons
     she has done so inadvertently.
     ...</p>
 </div>
</front>

<g>

<g> (character or glyph) represents a glyph, or a non-standard character. [5. ]
Modulegaiji — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
May containCharacter data only
Declaration
element g { att.global.attributes, att.typed.attributes, text }
Example
<g ref="#ctlig">ct</g>
This example points to a <glyph> element with the identifier ctlig like the following:
<glyph xml:id="ctlig"/>
Example
<g ref="#per-glyph">per</g>
The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per like the following:
<glyph xml:id="per-glyph"/>
Note

The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph.

<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.4.3. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
reasongives the reason for omission. Sample values include sampling, inaudible, irrelevant, cancelled.
Status Optional
Datatype 1–∞ occurrences of  data.wordseparated by whitespace
Values any short indication of the reason for the omission.
Member of
Contained by
May contain
core: desc
Declaration
element gap
{
   att.global.attributes,
   attribute reason { list { data.word+ } }?,
   ( model.descLike | model.certLike )*
}
Example
<gap quantity="4" unit="chars" reason="illegible"/>
Example
<gap quantity="1" unit="essay" reason="sampling"/>
Example
<del>
 <gap
   atLeast="4"
   atMost="8"
   unit="chars"
   reason="illegible"/>

</del>
Example
<gap extent="unknown" unit="lines" reason="lost"/>
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 11.3.3.2. 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.

<graphic>

<graphic> indicates the location of an inline graphic, illustration, or figure. [3.9. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.resourced (@url)
Member of
Contained by
May contain
core: desc
Declaration
element graphic
{
   att.global.attributes,
   att.resourced.attributes,
   model.descLike*
}
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>
Note

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

<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. 4.3.1. 15.1. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
textstructure: floatingText group text
May contain
Declaration
element group
{
   att.global.attributes,
   (
      ( model.divTop | model.global )*,
      ( ( text | group ), ( text | group | model.global )* ),
      model.divBottom*
   )
}
Example
<text>
 <front/>
 <group>
  <text/>
  <text/>
 </group>
</text>

<handShift>

<handShift> marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [11.3.2.1. ]
Moduletranscr — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
newidentifies the new hand.
Status Recommended
Datatype data.pointer
Values must refer to a <handNote> element, typically but not necessarily declared in the current document header (see section 11.3.2.1. ).
Note

This attribute serves the same function as the hand attribute provided for those elements which are members of the att.transcriptional class. It may be renamed at a subsequent major release.

Member of
Contained by
May containEmpty element
Declaration
element handShift
{
   att.global.attributes,
   attribute new { data.pointer }?,
   empty
}
Example
<l>When wolde the cat dwelle in his ynne</l>
<handShift medium="greenish-ink"/>
<l>And if the cattes skynne be slyk <handShift medium="black-ink"/> and gaye</l>
Note

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

<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. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
May contain
Declaration
element head
{
   att.global.attributes,
   att.typed.attributes,
   (
      text
    | lgmodel.gLikemodel.phrasemodel.intermodel.lLikemodel.global
   )*
}
Example

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

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

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

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

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

<hi>

<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. 3.3.2. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element hi { att.global.attributes, macro.paraContent }
Example
<hi rend="gothic">And this Indenture further witnesseth</hi>
that the said <hi rend="italic">Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...

<i> [http://www.tei-c.org/ns/tite/1.0]

<i> (italics) for capturing typographical feature: italicized glyphs.
Modulederived-module-tei_tite
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element i { att.global.attributes, macro.paraContent }

<item>

<item> contains one component of a list. [3.7. 2.5. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.sortable (@sortKey)
Member of
Contained by
core: list
May contain
Declaration
element item
{
   att.global.attributes,
   att.sortable.attributes,
   macro.specialPara
}
Example
<list type="ordered">
 <head>Here begin the chapter headings of Book IV</head>
 <item n="4.1">The death of Queen Clotild.</item>
 <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
 <item n="4.3">The wives and children of Lothar.</item>
 <item n="4.4">The Counts of the Bretons.</item>
 <item n="4.5">Saint Gall the Bishop.</item>
 <item n="4.6">The priest Cato.</item>
 <item> ...</item>
</list>
Note

May contain simple prose or a sequence of chunks.

Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the item element is by definition synonymous with the use of the label element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the label element, not n.

<l>

<l> (verse line) contains a single, possibly incomplete, line of verse. [3.12.1. 3.12. 7.2.5. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element l { att.global.attributes, macro.paraContent }
Example
<l met="-/-/-/-/-/" part="Y"/>

<label>

<label> contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.7. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element label { att.global.attributes, att.typed.attributes, macro.phraseSeq }
Example

Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:

<list type="gloss" xml:lang="enm">
 <head xml:lang="en">Vocabulary</head>
 <headLabel xml:lang="en">Middle English</headLabel>
 <headItem xml:lang="en">New English</headItem>
 <label>nu</label>
 <item xml:lang="en">now</item>
 <label>lhude</label>
 <item xml:lang="en">loudly</item>
 <label>bloweth</label>
 <item xml:lang="en">blooms</item>
 <label>med</label>
 <item xml:lang="en">meadow</item>
 <label>wude</label>
 <item xml:lang="en">wood</item>
 <label>awe</label>
 <item xml:lang="en">ewe</item>
 <label>lhouth</label>
 <item xml:lang="en">lows</item>
 <label>sterteth</label>
 <item xml:lang="en">bounds, frisks (cf. <cit>
   <ref>Chaucer, K.T.644</ref>
   <quote>a courser, <term>sterting</term>as the fyr</quote>
  </cit>
 </item>
 <label>verteth</label>
 <item xml:lang="la">pedit</item>
 <label>murie</label>
 <item xml:lang="en">merrily</item>
 <label>swik</label>
 <item xml:lang="en">cease</item>
 <label>naver</label>
 <item xml:lang="en">never</item>
</list>
Example

Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the label element is synonymous with the n attribute on the item element:

I will add two facts, which have seldom occurred
in the composition of six, or at least of five quartos. <list rend="runon" type="ordered">
 <label>(1)</label>
 <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>
 <label>(2) </label>
 <item>Not a sheet has been seen by any human eyes, excepting those of the author and the
   printer: the faults and the merits are exclusively my own.</item>
</list>
Example

Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:

<list type="gloss">
 <label>March 1757.</label>
 <item>I wrote some critical observations upon Plautus.</item>
 <label>March 8th.</label>
 <item>I wrote a long dissertation upon some lines of Virgil.</item>
 <label>June.</label>
 <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus
     amori.</quote>
 </item>
 <label>August.</label>
 <item>I went to Crassy, and staid two days.</item>
</list>

Note that the label might also appear within the item rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.

Example

Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the label element appears within the p or lg element, rather than as a preceding sibling of it.

<p>[...]
<lb/>&amp; n’entrer en mauuais &amp; mal-heu-
<lb/>ré meſnage. Or des que le conſente-
<lb/>ment des parties y eſt le mariage eſt
<lb/> arreſté, quoy que de faict il ne ſoit
<label place="margin">Puiſſance maritale
   entre les Romains.</label>
 <lb/> conſommé. Depuis la conſomma-
<lb/>tion du mariage la femme eſt ſoubs
<lb/> la puiſſance du mary, s’il n’eſt eſcla-
<lb/>ue ou enfant de famille : car en ce
<lb/> cas, la femme, qui a eſpouſé vn en-
<lb/>fant de famille, eſt ſous la puiſſance
[...]</p>
<p>In this example the text of the label appears in the right hand
margin of the original source, next to the paragraph it describes, but
approximately in the middle of it.
</p>
<p>If so desired the <gi>type</gi> attribute may be used to
distinguish different categories of label.</p>

<lb>

<lb> (line break) marks the start of a new (typographic) line in some edition or version of a text. [3.10.3. 7.2.5. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type) att.edition (@ed, @edRef)
Member of
Contained by
May containEmpty element
Declaration
element lb
{
   att.global.attributes,
   att.typed.attributes,
   att.edition.attributes,
   empty
}
Example

This example shows typographical line breaks within metrical lines, where they occur at different places in different editions:

<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example

This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word.

<titlePart rend="italic">
 <lb/>L'auteur susdict supplie les Lecteurs
<lb/>benevoles, soy reserver à rire au
soi-<lb break="no"/>xante &amp; dixhuytiesme livre.

</titlePart>
Note

By convention, lb elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next lb element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the l element is available) except in circumstances where structural units cannot otherwise be marked.

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

<lg>

<lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.12.1. 3.12. 7.2.5. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
May contain
Declaration
element lg
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( model.divTop | model.global )*,
      ( model.lLike | model.stageLike | model.labelLike | lg ),
      ( model.lLike | model.stageLike | model.labelLike | model.global | lg )*,
      ( ( model.divBottom ), model.global* )*
   )
}
Schematron

<sch:assert
 test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">
An lg element
must contain at least one child l, lg or gap element.</sch:assert>
Example
<lg type="free">
 <l>Let me be my own fool</l>
 <l>of my own making, the sum of it</l>
</lg>
<lg type="free">
 <l>is equivocal.</l>
 <l>One says of the drunken farmer:</l>
</lg>
<lg type="free">
 <l>leave him lay off it. And this is</l>
 <l>the explanation.</l>
</lg>
Note

contains verse lines or nested line groups only, possibly prefixed by a heading.

<list>

<list> (list) contains any sequence of items organized as a list. [3.7. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.sortable (@sortKey)
typedescribes the form of the list.
Status Optional
Datatype data.enumerated
Suggested values include:
ordered
list items are numbered or lettered.
bulleted
list items are marked with a bullet or other typographic device.
simple
list items are not numbered or bulleted. [Default]
gloss
each list item glosses some term or concept, which is given by a label element preceding the list item.
Note

The formal syntax of the element declarations allows label tags to be omitted from lists tagged <list type="gloss">; this is however a semantic error.

Member of
Contained by
May contain
Declaration
element list
{
   att.global.attributes,
   att.sortable.attributes,
   attribute type { "ordered" | "bulleted" | "simple" | "gloss" | xsd:Name }?,
   (
      ( ( model.divTop ) | ( model.global ) )*,
      (
         ( item, model.global* )+
       | (
            headLabel?,
            headItem?,
            ( label, model.global*, item, model.global* )+
         )
      ),
      ( ( model.divBottom ), model.global* )*
   )
}
Example
<list type="ordered">
 <item>a butcher</item>
 <item>a baker</item>
 <item>a candlestick maker, with <list type="bullets">
   <item>rings on his fingers</item>
   <item>bells on his toes</item>
  </list>
 </item>
</list>
Example

The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):

<div1 type="section">
 <head>Athelstan's Ordinance</head>
 <list type="ordered">
  <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with
     the stolen goods, [if he is] over twelve years and [if the value of the goods is] over
     eightpence. <list type="ordered">
    <item n="1.1">And if anyone does spare one, he is to pay for the thief with his
         wergild — and the thief is to be no nearer a settlement on that account — or to
         clear himself by an oath of that amount.</item>
    <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is
         not to be spared [whether younger or older than twelve].</item>
    <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may
         then be redeemed with 120 shillings; and the kindred are to stand surety for him
         that he will desist for ever.</item>
    <item n="1.4">And if he steals after that, they are to pay for him with his wergild,
         or to bring him back there.</item>
    <item n="1.5">And if he steals after that, they are to pay for him with his wergild,
         whether to the king or to him to whom it rightly belongs; and everyone of those who
         supported him is to pay 120 shillings to the king as a fine.</item>
   </list>
  </item>
  <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom
     no justice can be obtained, that one should order their kindred to fetch back such a
     person to justice and to find him a lord in public meeting. <list type="ordered">
    <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,
         he is then to be a fugitive afterwards, and he who encounters him is to strike him
         down as a thief.</item>
    <item n="2.2">And he who harbours him after that, is to pay for him with his wergild
         or to clear himself by an oath of that amount.</item>
   </list>
  </item>
  <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds
     his guilty man, so that the king is appealed to, is to repay the value of the goods and
     120 shillings to the king; and he who appeals to the king before he demands justice as
     often as he ought, is to pay the same fine as the other would have done, if he had
     refused him justice. <list type="ordered">
    <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes
         known about him, is to forfeit the slave and be liable to his wergild on the first
         occasionp if he does it more often, he is to be liable to pay all that he owns.</item>
    <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been
         an accessory of thieves who have committed theft, is to liable to the same.</item>
   </list>
  </item>
  <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to
     a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is
     afterwards convicted at the three-fold ordeal.</item>
 </list>
</div1>

Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.

Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they
confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards
inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy
Cross. <list type="simple">
  <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have
     subscribed to the pious and catholic validity of this document with the sign of the Holy
     Cross.</item>
  <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with
     the sign of the Holy Cross.</item>
  <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the
     sign of the Holy Cross.</item>
  <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the
     sign of the Holy Cross.</item>
  <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of
     the Holy Cross.</item>
  <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>
  <item>I, Æthelwine, bishop, have subscribed through delegates.</item>
  <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy
     Cross.</item>
 </list>
</p>
Note

May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

<listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.11.1. 2.2.7. 15.3.2. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.sortable (@sortKey) att.declarable (@default) att.typed (@type)
Member of
Contained by
May contain
derived-module-tei_tite: cols
Declaration
element listBibl
{
   att.global.attributes,
   att.sortable.attributes,
   att.declarable.attributes,
   att.typed.attributes,
   ( model.headLike*, ( model.biblLike | model.milestoneLike | listBibl )+ )
}
Example
<listBibl>
 <head>Works consulted</head>
 <bibl>Blain, Clements and Grundy: Feminist Companion to
   Literature in English (Yale, 1990)
 </bibl>
 <biblStruct>
  <analytic>
   <title>The Interesting story of the Children in the Wood</title>
  </analytic>
  <monogr>
   <title>The Penny Histories</title>
   <author>Victor E Neuberg</author>
   <imprint>
    <publisher>OUP</publisher>
    <date>1968</date>
   </imprint>
  </monogr>
 </biblStruct>
</listBibl>

<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.10.3. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.milestoneUnit (@unit) att.typed (@type) att.edition (@ed, @edRef)
Member of
Contained by
May containEmpty element
Declaration
element milestone
{
   att.global.attributes,
   att.milestoneUnit.attributes,
   att.typed.attributes,
   att.edition.attributes,
   empty
}
Example
<milestone n="23" ed="La" unit="Dreissiger"/>
... <milestone n="24" ed="AV" unit="verse"/> ...
Note

For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc.

The order in which milestone elements are given at a given point is not normally significant.

<name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.5.1. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.personal (@full, @sort) att.datable (@calendar) (att.datable.w3c (@when, @from, @to)) att.typed (@type)
Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element name
{
   att.global.attributes,
   att.personal.attributes,
   att.datable.attributes,
   att.typed.attributes,
   macro.phraseSeq
}
Example
<name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name type="person" ref="#HOC001">Occleve</name>
Note

Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included.

<note>

<note> contains a note or annotation. [3.8.1. 2.2.6. 3.11.2.7. 9.3.5.4. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.pointing (@targetLang, @target) att.typed (@type)
Member of
Contained by
May contain
Declaration
element note
{
   att.global.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   macro.specialPara
}
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.

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:

<respStmt xml:id="MDMH">
 <resp>translation from German to English</resp>
 <name>Hottinger, Marie Donald Mackie</name>
</respStmt>
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.

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.

<num>

<num> (number) contains a number, written in any form. [3.5.3. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
typeindicates the type of numeric value.
Status Optional
Datatype data.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.

Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element num
{
   att.global.attributes,
   attribute type
   {
      "cardinal" | "ordinal" | "fraction" | "percentage" | xsd:Name
   }?,
   macro.phraseSeq
}
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>
Note

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

<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. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element opener
{
   att.global.attributes,
   (
      text
    | model.gLikemodel.phraseargumentbylinedatelineepigraphsalutesignedmodel.global
   )*
}
Example
<opener>
 <dateline>Walden, this 29. of August 1592</dateline>
</opener>
Example
<opener>
 <dateline>
  <name type="place">Great Marlborough Street</name>
  <date>November 11, 1848</date>
 </dateline>
 <salute>My dear Sir,</salute>
</opener>
<p>I am sorry to say that absence from town and other circumstances have prevented me from
earlier enquiring...</p>

<ornament> [http://www.tei-c.org/ns/tite/1.0]

<ornament> for capturing typographical feature: printer's ornament, horizontal line, strings of asterisks or periods, etc, indicating an informal division that does not call for a new <div> element. If a horizontal rule or printer's ornament, use appropriate rend attribute and leave the element empy; if the ornament can be represented with characters, include these in the element.
Modulederived-module-tei_tite
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May containCharacter data only
Declaration
element ornament { att.global.attributes, text }

<p>

<p> (paragraph) marks paragraphs in prose. [3.1. 7.2.5. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.fragmentable (@part)
Member of
Contained by
May contain
Declaration
element p
{
   att.global.attributes,
   att.fragmentable.attributes,
   macro.paraContent
}
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
   done?</q>
</p>
<p>
 <q>I have now arranged that you can be married a second time,</q> replied Thjostolf.
</p>
<p>
 <q>Then you must mean that Thorvald is dead,</q> she said.
</p>
<p>
 <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q>
</p>

<pb>

<pb> (page break) marks the boundary between one page of a text and the next in a standard reference system. [3.10.3. ]
Modulecore — Formal specification
AttributesAttributes att.global.facs (@facs) att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type) att.edition (@ed, @edRef)
Member of
Contained by
May containEmpty element
Declaration
element pb
{
   att.global.facs.attributes,
   att.global.attributes,
   att.typed.attributes,
   att.edition.attributes,
   empty
}
Example

Page numbers may vary in different editions of a text.

<p> ... <pb n="145" ed="ed2"/>
... <pb n="283" ed="ed1"/>
... </p>
Example

A page break 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"/>
 <p/>
 <pb n="2" facs="page2.png"/>
 <p/>
</body>
Note

By convention, pb elements should appear at the start of the page to which they refer. The global n attribute indicates the number or other value associated with the page which follows. 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 break in any respect, for example as word-breaking or not.

<postscript>

<postscript> contains a postscript, e.g. to a letter. [4.2. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
derived-module-tei_tite: cols ornament
figures: figure table
linking: ab
Declaration
element postscript
{
   att.global.attributes,
   (
      ( model.global | model.divTopPart )*,
      ( model.common ),
      ( model.global | model.common )*,
      ( ( model.divBottomPart ), model.global* )*
   )
}
Example
<div type="letter">
 <opener>
  <dateline>
   <placeName>Rimaone</placeName>
   <date when="2006-11-21">21 Nov 06</date>
  </dateline>
  <salute>Dear Susan,</salute>
 </opener>
 <p>Thank you very much for the assistance splitting those
   logs. I'm sorry about the misunderstanding as to the size of
   the task. I really was not asking for help, only to borrow the
   axe. Hope you had fun in any case.</p>
 <closer>
  <salute>Sincerely yours,</salute>
  <signed>Seymour</signed>
 </closer>
 <postscript>
  <label>P.S.</label>
  <p>The collision occured on <date when="2001-07-06">06 Jul 01</date>.</p>
 </postscript>
</div>

<ptr>

<ptr> (pointer) defines a pointer to another location. [3.6. 16.1. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.pointing (@targetLang, @target) att.typed (@type)
Member of
Contained by
May containEmpty element
Declaration
element ptr
{
   att.global.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   empty
}
Schematron

<sch:report test="@target and @cRef">Only one of the
attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
Example
<ptr target="#p143 #p144"/>
<ptr target="http://www.tei-c.org"/>
<ptr cRef="1.3.4"/>

<publisher>

<publisher> provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.11.2.3. 2.2.4. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
core: bibl
textstructure: docImprint
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element publisher { att.global.attributes, macro.phraseSeq }
Example
<imprint>
 <pubPlace>Oxford</pubPlace>
 <publisher>Clarendon Press</publisher>
 <date>1987</date>
</imprint>
Note

Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

<pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.11.2.3. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
core: bibl
textstructure: docImprint
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element pubPlace { att.global.attributes, macro.phraseSeq }
Example
<publicationStmt>
 <publisher>Oxford University Press</publisher>
 <pubPlace>Oxford</pubPlace>
 <date>1989</date>
</publicationStmt>

<q>

<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. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.source (@source)
typemay be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
Status Optional
Datatype data.enumerated
Suggested values include:
spoken
representation of speech
thought
representation of thought, e.g. internal monologue
written
quotation from a written source
soCalled
authorial distance
foreign
(foreign words)
distinct
(linguistically distinct)
term
(technical term)
emph
(rhetorically emphasized)
mentioned
refering to itself, not its normal referant
Member of
Contained by
May contain
Declaration
element q
{
   att.global.attributes,
   att.source.attributes,
   attribute type
   {
      "spoken"
    | "thought"
    | "written"
    | "soCalled"
    | "foreign"
    | "distinct"
    | "term"
    | "emph"
    | "mentioned"
    | xsd:Name
   }?,
   macro.specialPara
}
Example
It is spelled <q>Tübingen</q> — to enter the
letter <q>u</q> with an umlaut hold down the <q>option</q> key and press
<q>0 0 f c</q>
Note

May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, q may be thought of as syntactic sugar for hi with a value of rend that indicates the use of such mechanisms as quotation marks.

<ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. 16.1. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.pointing (@targetLang, @target) att.typed (@type)
Member of
Contained by
May contain
Declaration
element ref
{
   att.global.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   macro.paraContent
}
Schematron

<sch:report test="@target and @cRef">Only one of the
attributes @target' and @cRef' may be supplied on <sch:name/>
</sch:report>
Example
<ref
  target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">
See especially the second
sentence</ref> See also <ref>s.v. <term>locution</term>
</ref>.
Example
<ref
  target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">
See especially the second
sentence</ref>
Example
See also <ref>s.v. <term>locution</term>
</ref>.
Note

The target and cRef attributes are mutually exclusive.

<resp>

<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.11.2.2. 2.2.1. 2.2.2. 2.2.5. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
core: respStmt
May contain
Declaration
element resp { att.global.attributes, macro.phraseSeq.limited }
Example
<respStmt>
 <resp key="com">compiler</resp>
 <name>Edward Child</name>
</respStmt>
Note

The attributes key or ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form, by referring directly (using ref) or indirectly (using key) to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

<respStmt>

<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.11.2.2. 2.2.1. 2.2.2. 2.2.5. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
core: bibl
May contain
core: name resp
Declaration
element respStmt
{
   att.global.attributes,
   ( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) )
}
Example
<respStmt>
 <resp>transcribed from original ms</resp>
 <persName>Claus Huitfeldt</persName>
</respStmt>
Example
<respStmt>
 <resp>converted to XML encoding</resp>
 <name>Alan Morrison</name>
</respStmt>

<row>

<row> contains one row of a table. [14.1.1. ]
Modulefigures — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.tableDecoration (@role, @rows, @cols)
Member of
Contained by
figures: table
May contain
figures: cell
Declaration
element row { att.global.attributes, att.tableDecoration.attributes, cell+ }
Example
<row role="data">
 <cell role="label">Classics</cell>
 <cell>Idle listless and unimproving</cell>
</row>

<salute>

<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. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
core: lg list
figures: table
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element salute { att.global.attributes, macro.phraseSeq }
Example
<salute>To all courteous mindes, that will voutchsafe the readinge.</salute>

<seg>

<seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. 6.2. 7.2.5. ]
Modulelinking — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
May contain
Declaration
element seg { att.global.attributes, att.typed.attributes, macro.paraContent }
Example
<seg>When are you leaving?</seg>
<seg>Tomorrow.</seg>
Example
<s>
 <seg rend="caps" type="initial-cap">So father's only</seg> glory was the ballfield.
</s>
Example
<seg type="preamble">
 <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>
 <seg>Sinfiotli was the eldest of his sons ...</seg>
 <seg>Borghild, Sigmund's wife, had a brother ... </seg>
</seg>
Note

The seg element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a ptr or other similar element.

<signed>

<signed> (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. [4.2.2. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element signed { att.global.attributes, macro.paraContent }
Example
<signed>Thine to command <name>Humph. Moseley</name>
</signed>
Example
<closer>
 <signed>Sign'd and Seal'd,
 <list>
   <item>John Bull,</item>
   <item>Nic. Frog.</item>
  </list>
 </signed>
</closer>

<smcap> [http://www.tei-c.org/ns/tite/1.0]

<smcap> (smallcaps) for capturing typographical feature: glyphs in small capitals.
Modulederived-module-tei_tite
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element smcap { att.global.attributes, macro.paraContent }

<sp>

<sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.12.2. 3.12. 7.2.2. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
derived-module-tei_tite: cols
figures: figure table
linking: ab
textstructure: floatingText
Declaration
element sp
{
   att.global.attributes,
   (
      model.global*,
      ( speaker, model.global* )?,
      (
         (
            lgmodel.lLikemodel.pLikemodel.listLikemodel.stageLikemodel.qLike
         ),
         model.global*
      )+
   )
}
Example
<sp>
 <speaker>The reverend Doctor Opimian</speaker>
 <p>I do not think I have named a single unpresentable fish.</p>
</sp>
<sp>
 <speaker>Mr Gryll</speaker>
 <p>Bream, Doctor: there is not much to be said for bream.</p>
</sp>
<sp>
 <speaker>The Reverend Doctor Opimian</speaker>
 <p>On the contrary, sir, I think there is much to be said for him. In the first place....</p>
 <p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I
   will forbear...</p>
</sp>
Note

The who attribute on this element may be used either in addition to the speaker element or as an alternative.

Note

Lines or paragraphs, stage directions, and phrase-level elements.

The who attribute on this element may be used either in addition to the speaker element or as an alternative.

<speaker>

<speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.12.2. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
core: sp
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element speaker { att.global.attributes, macro.phraseSeq }
Example
<sp who="#ni #rsa">
 <speaker>Nancy and Robert</speaker>
 <stage type="delivery">(speaking simultaneously)</stage>
 <p>The future? ...</p>
</sp>
<list type="speakers">
 <item xml:id="ni"/>
 <item xml:id="rsa"/>
</list>

<stage>

<stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.12.2. 3.12. 7.2.4. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element stage { att.global.attributes, macro.specialPara }
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.</stage>
<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>
<stage type="modifier">Disguised as Ansaldo.</stage>
<stage type="location">At a window.</stage>
<stage rend="inline" type="delivery">Aside.</stage>

<sub> [http://www.tei-c.org/ns/tite/1.0]

<sub> (subscript) for capturing typographical feature: subscript glyphs.
Modulederived-module-tei_tite
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element sub { att.global.attributes, macro.paraContent }

<sup> [http://www.tei-c.org/ns/tite/1.0]

<sup> (superscript) for capturing typographical feature: superscript glyphs.
Modulederived-module-tei_tite
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element sup { att.global.attributes, macro.paraContent }

<table>

<table> contains text displayed in tabular form, in rows and columns. [14.1.1. ]
Modulefigures — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
rowsindicates the number of rows in the table.
Status Optional
Datatype data.count
Values If no number is supplied, an application must calculate the number of rows.
Note

Rows should be presented from top to bottom.

cols(columns) indicates the number of columns in each row of the table.
Status Optional
Datatype data.count
Values If no number is supplied, an application must calculate the number of columns.
Note

Within each row, columns should be presented left to right.

Member of
Contained by
May contain
Declaration
element table
{
   att.global.attributes,
   attribute rows { data.count }?,
   attribute cols { data.count }?,
   (
      ( model.headLike | model.global )*,
      ( ( row, model.global* )+ | ( ( model.graphicLike ), model.global* )+ ),
      ( ( model.divBottom ), model.global* )*
   )
}
Example
<table rows="4" cols="4">
 <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
 <row role="label">
  <cell role="data"/>
  <cell role="data">Dossing Cribs or Lodging Houses</cell>
  <cell role="data">Beds</cell>
  <cell role="data">Needys or Nightly Lodgers</cell>
 </row>
 <row role="data">
  <cell role="label">Bury St Edmund's</cell>
  <cell role="data">5</cell>
  <cell role="data">8</cell>
  <cell role="data">128</cell>
 </row>
 <row role="data">
  <cell role="label">Thetford</cell>
  <cell role="data">3</cell>
  <cell role="data">6</cell>
  <cell role="data">36</cell>
 </row>
 <row role="data">
  <cell role="label">Attleboro'</cell>
  <cell role="data">3</cell>
  <cell role="data">5</cell>
  <cell role="data">20</cell>
 </row>
 <row role="data">
  <cell role="label">Wymondham</cell>
  <cell role="data">1</cell>
  <cell role="data">11</cell>
  <cell role="data">22</cell>
 </row>
</table>
Note

Contains an optional heading and a series of rows.

Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.

<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. 15.1. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type)
Member of
Contained by
textstructure: group
May contain
derived-module-tei_tite: cols
figures: figure
textstructure: back body front group
Declaration
element text
{
   att.global.attributes,
   att.typed.attributes,
   (
      model.global*,
      ( front, model.global* )?,
      ( body | group ),
      model.global*,
      ( back, model.global* )?
   )
}
Example
<text>
 <front>
  <docTitle>
   <titlePart>Autumn Haze</titlePart>
  </docTitle>
 </front>
 <body>
  <l>Is it a dragonfly or a maple leaf</l>
  <l>That settles softly down upon the water?</l>
 </body>
</text>
Example

The body of a text may be replaced by a group of nested texts, as in the following schematic:

<text>
 <front/>
 <group>
  <text/>
  <text/>
 </group>
</text>
Note

This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the floatingText is provided for this purpose.

<time>

<time> contains a phrase defining a time of day in any format. [3.5.4. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style) att.typed (@type) att.datable (@calendar) att.datable.w3c (from, to, @when)
Member of
Contained by
May contain
derived-module-tei_tite: b cols i smcap sub sup ul
figures: figure formula
gaiji: g
linking: seg
transcr: handShift
Declaration
element time
{
   att.global.attributes,
   att.datable.attribute.calendar,
   att.datable.w3c.attribute.when,
   att.typed.attributes,
   ( text | model.gLike | model.phrase | model.global )*
}
Example
As he sat smiling, the
quarter struck — <time when="11:45:00">the quarter to twelve</time>.

<title>

<title> contains a title for any kind of work. [3.11.2.2. 2.2.1. 2.2.5. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
Status Optional
Datatype data.enumerated
Sample values include:
main
main title
sub
(subordinate) subtitle, title of part
alt
(alternate) alternate title, often in another language, by which the work is also known
short
abbreviated form of title
desc
(descriptive) descriptive paraphrase of the work functioning as a title
Note

This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single title element.

levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
Status Optional
Datatype data.enumerated
Legal values are:
a
(analytic) analytic title (article, poem, or other item published as part of a larger item)
m
(monographic) monographic title (book, collection, or other item published as a distinct item, including single volumes of multi-volume works)
j
(journal) journal title
s
(series) series title
u
(unpublished) title of unpublished material (including theses and dissertations unless published by a commercial press)
Note

The level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level ‘a’, and one appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

Member of
Contained by
May contain
Declaration
element title
{
   att.global.attributes,
   attribute type { data.enumerated }?,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   macro.paraContent
}
Example
<title>Information Technology and the Research Process: Proceedings of
a conference held at Cranfield Institute of Technology, UK,
18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable
edition</title>
Example
<title type="full">
 <title type="main">Synthèse</title>
 <title type="sub">an international journal for
   epistemology, methodology and history of
   science</title>
</title>
Note

The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

<titlePage>

<titlePage> (title page) contains the title page of a text, appearing within the front or back matter. [4.6. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
typeclassifies the title page according to any convenient typology.
Status Optional
Datatype data.enumerated
Note

This attribute allows the same element to be used for volume title pages, series title pages, etc., as well as for the‘main’ title page of a work.

Member of
Contained by
textstructure: back front
May contain
Declaration
element titlePage
{
   att.global.attributes,
   attribute type { data.enumerated }?,
   (
      model.global*,
      ( model.titlepagePart ),
      ( model.titlepagePart | model.global )*
   )
}
Example
<titlePage>
 <docTitle>
  <titlePart type="main">THOMAS OF Reading.</titlePart>
  <titlePart type="alt">OR, The sixe worthy yeomen of the West.</titlePart>
 </docTitle>
 <docEdition>Now the fourth time corrected and enlarged</docEdition>
 <byline>By T.D.</byline>
 <figure>
  <head>TP</head>
  <p>Thou shalt labor till thou returne to duste</p>
  <figDesc>Printers Ornament used by TP</figDesc>
 </figure>
 <docImprint>Printed at <name type="place">London</name> for <name>T.P.</name>
  <date>1612.</date>
 </docImprint>
</titlePage>

<titlePart>

<titlePart> contains a subsection or division of the title of a work, as indicated on a title page. [4.6. ]
Moduletextstructure — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
typespecifies the role of this subdivision of the title.
Status Optional
Datatype data.enumerated
Suggested values include:
main
main title of the work [Default]
sub
(subordinate) subtitle of the work
alt
(alternate) alternative title of the work
short
abbreviated form of title
desc
(descriptive) descriptive paraphrase of the work
Member of
Contained by
textstructure: back docTitle front titlePage
May contain
Declaration
element titlePart
{
   att.global.attributes,
   attribute type { "main" | "sub" | "alt" | "short" | "desc" | xsd:Name }?,
   macro.paraContent
}
Example
<docTitle>
 <titlePart type="main">THE FORTUNES
   AND MISFORTUNES Of the FAMOUS
   Moll Flanders, &amp;c.
 </titlePart>
 <titlePart type="desc">Who was BORN in NEWGATE,
   And during a Life of continu'd Variety for
   Threescore Years, besides her Childhood, was
   Twelve Year a <hi>Whore</hi>, five times a <hi>Wife</hi> (wherof
   once to her own Brother) Twelve Year a <hi>Thief,</hi>
   Eight Year a Transported <hi>Felon</hi> in <hi>Virginia</hi>,
   at last grew <hi>Rich</hi>, liv'd <hi>Honest</hi>, and died a
 <hi>Penitent</hi>.</titlePart>
</docTitle>

<ul> [http://www.tei-c.org/ns/tite/1.0]

<ul> (underline) for capturing typographical feature: underlined glyphs.
Modulederived-module-tei_tite
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
Member of
Contained by
May contain
Declaration
element ul { att.global.attributes, macro.paraContent }

<unclear>

<unclear> contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. 3.4.3. ]
Modulecore — Formal specification
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style)
reasonindicates why the material is hard to transcribe.
Status Optional
Datatype 1–∞ occurrences of  data.wordseparated by whitespace
Values one or more words describing the difficulty, e.g. faded, background-noise, passing-truck, illegible, eccentric-ductus.
<div>
 <head>Rx</head>
 <p>500 mg <unclear reason="illegible">placebo</unclear>
 </p>
</div>
Member of
Contained by
May contain
Declaration
element unclear
{
   att.global.attributes,
   attribute reason { list { data.word+ } }?,
   macro.paraContent
}
Example
and from time to time invited in like manner
his att<unclear>ention</unclear>

Here the last few letters of the word are hard to read.

Example
<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
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 21. .

The <damage>, gap, del, unclear and <supplied> elements may be closely allied in use. See section 11.3.3.2. for discussion of which element is appropriate for which circumstance.

Schema tei_tite: Model classes

model.addressLike

model.addressLike groups elements used to represent a postal or e-mail address. [1. ]
Moduletei — Formal specification
Used by
Membersemail address

model.addrPart

model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.5.2. ]
Moduletei — Formal specification
Used by
Membersmodel.nameLike [model.nameLike.agent [name] ] addrLine

model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.11. ]
Moduletei — Formal specification
Used by
Membersbibl

model.biblPart

model.biblPart groups elements which represent components of a bibliographic description. [3.11. ]
Moduletei — Formal specification
Used by
Membersmodel.respLike [author editor respStmt] model.imprintPart [publisher pubPlace] bibl

model.choicePart

model.choicePart groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.4. ]
Moduletei — Formal specification
Used by
Membersunclear abbr seg

model.common

model.common groups common chunk- and inter-level elements. [1.3. ]
Moduletei — Formal specification
Used by
Membersmodel.divPart [model.lLike [l] model.pLike [p ab] lg sp] model.inter [model.egLike model.biblLike [bibl] model.labelLike [desc label] model.listLike [list listBibl table] model.stageLike [stage] model.qLike [model.quoteLike [cit] q floatingText] ornament]
Note

This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

model.dateLike

model.dateLike groups elements containing temporal expressions. [3.5.4. 13.3.6. ]
Moduletei — Formal specification
Used by
Membersdate time

model.descLike

model.descLike groups elements which contain a description of their function.
Moduletei — Formal specification
Used by
Membersdesc

model.div1Like

model.div1Like groups top-level structural divisions.
Moduletei — Formal specification
Used by
Membersdiv1

model.div2Like

model.div2Like groups second-level structural divisions.
Moduletei — Formal specification
Used by
Membersdiv2

model.div3Like

model.div3Like groups third-level structural divisions.
Moduletei — Formal specification
Used by
Membersdiv3

model.div4Like

model.div4Like groups fourth-level structural divisions.
Moduletei — Formal specification
Used by
Membersdiv4

model.div5Like

model.div5Like groups fifth-level structural divisions.
Moduletei — Formal specification
Used by
Membersdiv5

model.div6Like

model.div6Like groups sixth-level structural divisions.
Moduletei — Formal specification
Used by
Membersdiv6

model.div7Like

model.div7Like groups seventh-level structural divisions.
Moduletei — Formal specification
Used by
Membersdiv7

model.divBottom

model.divBottom groups elements appearing at the end of a text division. [4.2. ]
Moduletei — Formal specification
Used by
Membersmodel.divWrapper [byline dateline argument epigraph salute docAuthor docDate] model.divBottomPart [closer signed postscript]

model.divBottomPart

model.divBottomPart groups elements which can occur only at the end of a text division. [4.6. ]
Moduletei — Formal specification
Used by
Memberscloser signed postscript

model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. ]
Moduletei — Formal specification
Used by
Membersmodel.lLike [l] model.pLike [p ab] lg sp
Note

Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

model.divTop

model.divTop groups elements appearing at the beginning of a text division. [4.2. ]
Moduletei — Formal specification
Used by
Membersmodel.divWrapper [byline dateline argument epigraph salute docAuthor docDate] model.divTopPart [model.headLike [head] opener]

model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. ]
Moduletei — Formal specification
Used by
Membersmodel.headLike [head] opener

model.divWrapper

model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. ]
Moduletei — Formal specification
Used by
Membersbyline dateline argument epigraph salute docAuthor docDate

model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. ]
Moduletei — Formal specification
Used by
Membersforeign title

model.frontPart

model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. ]
Moduletei — Formal specification
Used by
MemberstitlePage

model.gLike

model.gLike groups elements used to represent individual non-Unicode characters or glyphs.
Moduletei — Formal specification
Used by
Membersg

model.global

model.global groups elements which may appear at any point within a TEI text. [1.3. ]
Moduletei — Formal specification
Used by
Membersmodel.milestoneLike [milestone pb lb cb cols] model.noteLike [note] model.global.edit [gap] figure

model.global.edit

model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. ]
Moduletei — Formal specification
Used by
Membersgap

model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.9. ]
Moduletei — Formal specification
Used by
Membersgraphic formula

model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Moduletei — Formal specification
Used by
Membershead

model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct. [3.3. ]
Moduletei — Formal specification
Used by
Membersmodel.hiLike [hi b i ul sub sup smcap] model.emphLike [foreign title]

model.hiLike

model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. ]
Moduletei — Formal specification
Used by
Membershi b i ul sub sup smcap

model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints. [3.11. ]
Moduletei — Formal specification
Used by
Memberspublisher pubPlace

model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. ]
Moduletei — Formal specification
Used by
Membersmodel.egLike model.biblLike [bibl] model.labelLike [desc label] model.listLike [list listBibl table] model.stageLike [stage] model.qLike [model.quoteLike [cit] q floatingText] ornament

model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Moduletei — Formal specification
Used by
Membersdesc label

model.limitedPhrase

model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. ]
Moduletei — Formal specification
Used by
Membersmodel.hiLike [hi b i ul sub sup smcap] model.emphLike [foreign title] model.pPart.editorial [abbr] model.ptrLike [ptr ref] model.pPart.data [model.dateLike [date time] model.measureLike [num] model.addressLike [email address] model.nameLike [model.nameLike.agent [name] ] ]

model.linePart

model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element.
Moduletei — Formal specification
Used by
Membersmodel.segLike [seg] model.hiLike [hi b i ul sub sup smcap] model.pPart.transcriptional [add del unclear handShift]

model.listLike

model.listLike groups list-like elements. [3.7. ]
Moduletei — Formal specification
Used by
Memberslist listBibl table

model.lLike

model.lLike groups elements representing metrical components such as verse lines.
Moduletei — Formal specification
Used by
Membersl

model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.5.3. ]
Moduletei — Formal specification
Used by
Membersnum

model.milestoneLike

model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. 3.10.3. ]
Moduletei — Formal specification
Used by
Membersmilestone pb lb cb cols

model.msItemPart

model.msItemPart groups elements which can appear within a manuscript item description.
Moduletei — Formal specification
Used by
Membersmodel.quoteLike [cit] model.respLike [author editor respStmt] model.msQuoteLike [title] bibl listBibl

model.msQuoteLike

model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
Moduletei — Formal specification
Used by
Memberstitle

model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei — Formal specification
Used by
Membersmodel.nameLike.agent [name]
Note

A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.5. ]
Moduletei — Formal specification
Used by
Membersname
Note

This class is used in the content model of elements which reference names of people or organizations.

model.noteLike

model.noteLike groups globally-available note-like elements. [3.8. ]
Moduletei — Formal specification
Used by
Membersnote

model.personPart

model.personPart groups elements which form part of the description of a person. [15.2.2. ]
Moduletei — Formal specification
Used by
Membersbibl

model.phrase

model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. ]
Moduletei — Formal specification
Used by
Membersmodel.segLike [seg] model.highlighted [model.hiLike [hi b i ul sub sup smcap] model.emphLike [foreign title] ] model.graphicLike [graphic formula] model.pPart.edit [model.pPart.editorial [abbr] model.pPart.transcriptional [add del unclear handShift] ] model.ptrLike [ptr ref] model.pPart.data [model.dateLike [date time] model.measureLike [num] model.addressLike [email address] model.nameLike [model.nameLike.agent [name] ] ]
Note

This class of elements can occur only within larger elements of the class inter or chunk. In prose, this means these elements can occur within paragraphs, list items, lines of verse, etc.

model.pLike

model.pLike groups paragraph-like elements.
Moduletei — Formal specification
Used by
Membersp ab

model.pLike.front

model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. ]
Moduletei — Formal specification
Used by
Membershead byline argument epigraph docTitle titlePart docAuthor docEdition docImprint docDate

model.pPart.data

model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.5. ]
Moduletei — Formal specification
Used by
Membersmodel.dateLike [date time] model.measureLike [num] model.addressLike [email address] model.nameLike [model.nameLike.agent [name] ]

model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.4. ]
Moduletei — Formal specification
Used by
Membersmodel.pPart.editorial [abbr] model.pPart.transcriptional [add del unclear handShift]

model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.4. ]
Moduletei — Formal specification
Used by
Membersabbr

model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.4. ]
Moduletei — Formal specification
Used by
Membersadd del unclear handShift

model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.6. ]
Moduletei — Formal specification
Used by
Membersptr ref

model.publicationStmtPart

model.publicationStmtPart groups elements which may appear within the <publicationStmt> element of the TEI Header. [2.2.4. ]
Moduletei — Formal specification
Used by
Membersaddress date publisher pubPlace

model.qLike

model.qLike groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. ]
Moduletei — Formal specification
Used by
Membersmodel.quoteLike [cit] q floatingText

model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Moduletei — Formal specification
Used by
Memberscit

model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Moduletei — Formal specification
Used by
Membersauthor editor respStmt

model.segLike

model.segLike groups elements used for arbitrary segmentation. [16.3. 17.1. ]
Moduletei — Formal specification
Used by
Membersseg
Note

The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header.

model.stageLike

model.stageLike groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. ]
Moduletei — Formal specification
Used by
Membersstage
Note

Stage directions are members of class inter: that is, they can appear between or within component-level elements.

model.titlepagePart

model.titlepagePart groups elements which can occur as direct constituents of a title page, such as docTitle, docAuthor, docImprint, or epigraph. [4.6. ]
Moduletei — Formal specification
Used by
Membersgraphic byline argument epigraph docTitle titlePart docAuthor docEdition docImprint docDate ornament

Schema tei_tite: Attribute classes

att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events.
Moduletei — Formal specification
Membersname
AttributesAttributes att.datable.w3c (@when, @from, @to)
calendarindicates the system or calendar to which the date represented by the content of this element belongs.
Status Optional
Datatype data.pointer
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length(.) gt 0">@calendar indicates the system or calendar to which the date represented by the content of this element
belongs, but this <sch:name/> element has no textual content.</sch:assert></sch:rule>
He was born on <date calendar="#Gregorian">Feb. 22, 1732</date>
(<date calendar="#Julian" when="1732-02-22"> Feb. 11, 1731/32, O.S.</date>).

att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events using the W3C datatypes.
Moduletei — Formal specification
Membersatt.datable [name]
AttributesAttributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.temporal.w3c
Values A normalized form of temporal expression conforming to the W3C XML Schema Part 2: Datatypes Second Edition.

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

The value of the when attribute should be the 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 part of the when 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.

fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.temporal.w3c
Values A normalized form of temporal expression conforming to the W3C XML Schema Part 2: Datatypes Second Edition.
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.temporal.w3c
Values A normalized form of temporal expression conforming to the W3C XML Schema Part 2: Datatypes Second Edition.

att.declarable

att.declarable provides attributes for those elements in the TEI Header which may be independently selected by means of the special purpose decls attribute. [15.3. ]
Moduletei — Formal specification
Membersbibl listBibl
AttributesAttributes
defaultindicates whether or not this element is selected by default when its parent is selected.
Status Optional
Datatype data.truthValue
Legal values are:
true
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected. [Default]
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. . Only one element of a particular type may have a default attribute with a value of true.

att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Moduletei — Formal specification
Membersbibl
AttributesAttributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
Status Optional
Datatype data.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">
 <change when="2010-10-21" status="published"/>
 <change when="2010-10-02" status="cleared"/>
 <change when="2010-08-02" status="embargoed"/>
 <change when="2010-05-01" status="frozen" who="#MSM"/>
 <change when="2010-03-01" status="draft" who="#LB"/>
</revisionDesc>

att.edition

att.edition provides attributes identifying the source edition from which some encoded feature derives.
Moduletei — Formal specification
Membersmilestone pb lb cb
AttributesAttributes
ed(edition) supplies an arbitrary identifier for the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
Status Optional
Datatype 1–∞ occurrences of  data.codeseparated by whitespace
Values A string of characters or sigil used conventionally to identify the edition.
edRef (edition reference) provides a pointer to the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace
Example
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example
<listBibl>
 <bibl xml:id="stapledon1937">
  <author>Olaf Stapledon</author>,
 <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>
 </bibl>
 <bibl xml:id="stapledon1968">
  <author>Olaf Stapledon</author>,
 <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>
 </bibl>
</listBibl>
<p>Looking into the future aeons from the supreme moment of
the cosmos, I saw the populations still with all their
strength maintaining the<pb n="411" edRef="#stapledon1968"/>essentials of their ancient culture,
still living their personal lives in zest and endless
novelty of action, … I saw myself still
preserving, though with increasing difficulty, my lucid
con-<pb n="291" edRef="#stapledon1937"/>sciousness;</p>

att.fragmentable

att.fragmentable groups structural elements which may be fragmented, usually as a consequence of some overlapping hierarchy.
Moduletei — Formal specification
Membersp
AttributesAttributes
partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure : for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
Status Optional
Datatype data.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) either the element is not fragmented, or no claim is made as to its completeness. [Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

The values I, M, or F should be used only where it is clear how the element may be be reconstituted.

att.global

att.global provides attributes common to all elements in the TEI encoding scheme.
Moduletei — Formal specification
Membersp foreign hi q desc gap add del unclear name email address addrLine num date time abbr ptr ref list item label head note graphic milestone pb lb cb author editor respStmt resp title publisher pubPlace bibl listBibl l lg sp speaker stage text body group floatingText div1 div2 div3 div4 div5 div6 div7 byline dateline argument epigraph opener closer salute signed postscript titlePage docTitle titlePart docAuthor docEdition docImprint docDate front back table row cell formula figure seg g handShift b i ul sub sup smcap cols ornament
AttributesAttributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
Datatype xsd:ID
Note

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

n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Status Optional
Datatype data.text
Values the value consists of a single token which may however contain punctuation characters, whitespace or word separating characters. It need not be restricted to numbers.
Note

The n attribute may be 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(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Status Optional
Datatype data.language
Values 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 Internet Engineering Task Force (IETF) definitions.
<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.

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

rend(rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
Datatype 1–∞ occurrences of  data.wordseparated by whitespace
Values may contain any number of tokens, each of which may contain letters, punctuation marks, or symbols, but not whitespace or word-separating characters.
<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.

stylecontains 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 data.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, 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.

att.global.facs

att.global.facs groups elements corresponding with all or part of an image, because they contain an alternative representation of it, typically but not necessarily a transcription of it. [11.1. ]
Moduletranscr — Formal specification
Memberspb
AttributesAttributes
facs(facsimile) points to all or part of an image which corresponds with the content of the element.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace

att.milestoneUnit

att.milestoneUnit provides an attribute to indicate the type of section which is changing at a specific milestone. [3.10.3. 2.3.6.3. 2.3.6. ]
Modulecore — Formal specification
Membersmilestone
AttributesAttributes
unitprovides a conventional name for the kind of section changing at this milestone.
Status Required
Datatype data.enumerated
Suggested values include:
page
physical page breaks (synonymous with the pb element).
column
column breaks.
line
line breaks (synonymous with the lb element).
book
any units termed book, liber, etc.
poem
individual poems in a collection.
canto
cantos or other major sections of a poem.
speaker
changes of speaker or narrator.
stanza
stanzas within a poem, book, or canto.
act
acts within a play.
scene
scenes within a play or act.
section
sections of any kind.
absent
passages not present in the reference edition.
unnumbered
passages present in the text, but not to be included as part of the reference.
<milestone n="23" ed="La" unit="Dreissiger"/>
... <milestone n="24" ed="AV" unit="verse"/> ...
Note

If the milestone marks the beginning of a piece of text not present in the reference edition, the special value absent may be used as the value of unit. The normal interpretation is that the reference edition does not contain the text which follows, until the next milestone tag for the edition in question is encountered.

In addition to the values suggested, other terms may be appropriate (e.g. Stephanus for the Stephanus numbers in Plato).

att.personal

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. [13.2.1. ]
Moduletei — Formal specification
Membersname
AttributesAttributes
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
Status Optional
Datatype data.enumerated
Legal values are:
yes
the name component is spelled out in full. [Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.
sortspecifies the sort order of the name component in relation to others within the name.
Status Optional
Datatype data.count
Values A positive number indicating the sort order.

att.pointing

att.pointing defines a set of attributes used by all elements which point to other elements by means of one or more URI references.
Moduletei — Formal specification
Membersptr ref note
AttributesAttributes
targetLangspecifies 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 data.language
Schematron

<sch:rule
 context="tei:*[not(self::tei:schemaSpec)][@targetLang]">

<sch:assert test="count(@target)">@targetLang can only be used if @target is specified.</sch:assert></sch:rule>
Values 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 Internet Engineering Task Force (IETF) definitions.
<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.

targetspecifies the destination of the reference by supplying one or more URI References
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace
Values 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.

att.resourced

att.resourced provides attributes by which a resource (such as an externally held media file) may be located.
Moduletei — Formal specification
Membersgraphic
AttributesAttributes
url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
Status Required
Datatype data.pointer

att.sortable

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. [1. ]
Moduletei — Formal specification
Memberslist item bibl listBibl
AttributesAttributes
sortKeysupplies the sort key for this element in an index, list or group which contains it.
Status Optional
Datatype data.word
Values a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent.
David's other principal backer, Josiah
ha-Kohen <index indexName="NAMES">
 <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term>
</index> b. Azarya, son of one of the last gaons of Sura was David's own first
cousin.
Note

The sort key is used to determine the sequence and grouping of entries in an index.

Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

att.source

att.source provides attributes for pointing to the source of a bibliographic reference. [3.3.3. 8.3.4. ]
Moduletei — Formal specification
Membersq
AttributesAttributes
source (pointer to a bibliographical source reference) provides a pointer to the bibliographical source from which a quotation or citation is drawn.
Status Optional
Datatype 1–∞ occurrences of  data.pointerseparated by whitespace
Values Must point to one or more bibliographic elements in the TEI header or elsewhere
Example
<p>
As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>)
tells us, <quote source="#mcc_2012">‘Collaboration’ is a a
   problematic and should be a contested term.</quote>
</p>
Example
<p>
 <quote source="#chicago_15_ed">Grammatical theories
   are in flux, and the more we learn, the less we
   seem to know.</quote>
</p>
<bibl xml:id="chicago_15_ed">
 <title level="m">The Chicago Manual of Style</title>,
<edition>15th edition</edition>.
<pubPlace>Chicago</pubPlace>:
<publisher>University of Chicago Press</publisher>
(<date>2003</date>),
<biblScope type="pp">p.147</biblScope>.

</bibl>

att.tableDecoration

att.tableDecoration provides attributes used to decorate rows or cells of a table. [14. ]
Moduletei — Formal specification
Membersrow cell
AttributesAttributes
roleindicates the kind of information held in this cell or in each cell of this row.
Status Optional
Datatype data.enumerated
Suggested values include:
label
labelling or descriptive information only.
data
data values. [Default]
Note

When this attribute is specified on a row, its value is the default for all cells in this row. When specified on a cell, its value overrides any default specified by the role attribute of the parent row element.

rowsindicates the number of rows occupied by this cell or row.
Status Optional
Datatype data.count
Default 1
Values A number; a value greater than one indicates that this cell (or row) spans several rows.
Note

Where several cells span several rows, it may be more convenient to use nested tables.

cols(columns) indicates the number of columns occupied by this cell or row.
Status Optional
Datatype data.count
Default 1
Values A number; a value greater than one indicates that this cell or row spans several columns.
Note

Where an initial cell spans an entire row, it may be better treated as a heading.

att.transcriptional

att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [1. ]
Moduletei — Formal specification
Membersadd del
AttributesAttributes
handsignifies the hand of the agent which made the intervention.
Status Optional
Datatype data.pointer
Values must refer to a <handNote> element, typically declared in the document header (see section 11.3.2.1. ).
statusindicates the effect of the intervention, for example in the case of a deletion, strikeouts which include too much or too little text, or in the case of an addition, an insertion which duplicates some of the text already present.
Status Optional
Datatype data.enumerated
Sample values include:
duplicate
all of the text indicated as an addition duplicates some text that is in the original, whether the duplication is word-for-word or less exact.
duplicate-partial
part of the text indicated as an addition duplicates some text that is in the original
excessStart
some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
excessEnd
some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
shortStart
some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
shortEnd
some text at the end of the deletion is not marked as deleted even though it clearly should be.
partial
some text in the deletion is not marked as deleted even though it clearly should be.
unremarkable
the deletion is not faulty. [Default]
Note

Status information on each deletion is needed rather rarely except in critical editions from authorial manuscripts; status information on additions is even less common.

Marking a deletion or addition as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.

causedocuments the presumed cause for the intervention.
Status Optional
Datatype data.enumerated
Legal values are:
fix
repeated for the purpose of fixation
unclear
repeated to clarify a previously illegible or badly written text or mark
seq(sequence) assigns a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred.
Status Mandatory when applicable
Datatype data.count

att.typed

att.typed provides attributes which can be used to classify or subclassify elements in any way.
Moduletei — Formal specification
Membersadd del name date time abbr ptr ref label head note milestone pb lb cb bibl listBibl lg text floatingText div1 div2 div3 div4 div5 div6 div7 figure seg g
AttributesAttributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Datatype data.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.

Schema tei_tite: Macros

data.code

data.code defines the range of attribute values expressing a coded value by means of a pointer to some other element which contains a definition for it.
Moduletei — Formal specification
Used by
Element:
Declaration
data.code = data.word
Note

It will usually be the case that the item pointed to is to be found somewhere else in the current TEI document, typically in the header, but this is not mandatory.

data.count

data.count defines the range of attribute values used for a non-negative integer value used as a count.
Moduletei — Formal specification
Used by
Element:
Declaration
data.count = xsd:nonNegativeInteger
Note

Only positive integer values (including zero) are permitted

data.duration.iso

data.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
Moduletei — Formal specification
Used by
Declaration
data.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Example
<time dur-iso="PT0,75H">three-quarters of an hour</time>
Example
<date dur-iso="P1,5D">a day and a half</date>
Example
<date dur-iso="P14D">a fortnight</date>
Example
<time dur-iso="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.

data.duration.w3c

data.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Moduletei — Formal specification
Used by
Declaration
data.duration.w3c = xsd:duration
Example
<time dur="PT45M">forty-five minutes</time>
Example
<date dur="P1DT12H">a day and a half</date>
Example
<date dur="P7D">a week</date>
Example
<time dur="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see the W3C specification.

data.enumerated

data.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Moduletei — Formal specification
Used by
Element:
Declaration
data.enumerated = data.name
Note

Attributes using this datatype must contain a word which follows the rules defining a legal XML name (see http://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.

data.language

data.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. ]
Moduletei — Formal specification
Used by
Declaration
data.language = xsd:language
Note

The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 4646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.

A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.

language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at http://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at http://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case. The list of codes can be found at http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/index.html. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
private use
An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI conformant, a corresponding <language> element must be present in the TEI header.

There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.

Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.

Examples include

sn
Shona
zh-TW
Taiwanese
zh-Hant-HK
Chinese written in traditional script as used in Hong Kong
en-SL
English as spoken in Sierra Leone
pl
Polish
es-MX
Spanish as spoken in Mexico
es-419
Spanish as spoken in Latin America

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

data.name

data.name defines the range of attribute values expressed as an XML Name.
Moduletei — Formal specification
Used by
Declaration
data.name = xsd:Name
Note

Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see http://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

data.numeric

data.numeric defines the range of attribute values used for numeric values.
Moduletei — Formal specification
Used by
Declaration
data.numeric =
   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
Note

Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.

A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

data.outputMeasurement

data.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display on the web.
Moduletei — Formal specification
Used by
Declaration
data.outputMeasurement =
   token
   {
      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)"
   }
Example
<figure>
 <head>The TEI Logo</head>
 <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
   between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
   background.</figDesc>
 <graphic
   height="600px"
   width="600px"
   url="http://www.tei-c.org/logos/TEI-600.jpg"/>

</figure>
Note

These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

data.pointer

data.pointer defines the range of attribute values used to provide a single URI pointer to any other resource, either within the current document or elsewhere.
Moduletei — Formal specification
Used by
Element:
Declaration
data.pointer = xsd:anyURI
Note

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

data.temporal.w3c

data.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 specification.
Moduletei — Formal specification
Used by
Element:
Declaration
data.temporal.w3c =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

data.text

data.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.
Moduletei — Formal specification
Used by
Declaration
data.text = string
Note

Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

data.truthValue

data.truthValue defines the range of attribute values used to express a truth value.
Moduletei — Formal specification
Used by
Declaration
data.truthValue = xsd:boolean
Note

The possible values of this datatype are 1 or true, or 0 or false.

Note

This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: data.xTruthValue.

data.word

data.word defines the range of attribute values expressed as a single word or token.
Moduletei — Formal specification
Used by
data.codeElement:
Declaration
data.word = token { pattern = "(\p{L}|\p{N}|\p{P}|\p{S})+" }
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. ]
Moduletei — Formal specification
Used by
Declaration
macro.limitedContent = ( text | model.limitedPhrase | model.inter )*

macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. ]
Moduletei — Formal specification
Used by
Declaration
macro.paraContent =
   ( text | model.gLike | model.phrase | model.inter | model.global | lg )*

macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. ]
Moduletei — Formal specification
Used by
Declaration
macro.phraseSeq = ( text | model.gLike | model.phrase | model.global )*

macro.phraseSeq.limited

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. ]
Moduletei — Formal specification
Used by
Declaration
macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*

macro.specialPara

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. ]
Moduletei — Formal specification
Used by
Declaration
macro.specialPara =
   (
      text
    | model.gLikemodel.phrasemodel.intermodel.divPartmodel.global
   )*

Acknowledgments

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

and represented in their documents

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.

Perry Trolard, for the TEI Consortium. Date: Version 1.1 — September 2011