Encoding for Interchange: an introduction to the TEI
language: en
availability: Distributed under a Creative Commons Attribution-ShareAlike 3.0 Unported License Copyright 2013 TEI Consortium. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditio (http://creativecommons.org/licenses/by-sa/3.0/)

TEI Lite: Encoding for Interchange: an introduction to the TEI
Final revised edition for TEI P5

Lou Burnard
C. M. Sperberg-McQueen
August 2012

Prefatory note

TEI Lite was the name adopted for what the TEI editors originally conceived of as a simple demonstration of how the TEI (Text Encoding Initiative) encoding scheme might be adopted to meet 90% of the needs of 90% of the TEI user community. In retrospect, it was predictable that many people should imagine TEI Lite to be all there is to TEI, or find TEI Lite to be far too heavy for their needs.

The original TEI Lite (1996) was based largely on observations of existing and previous practice in the encoding of texts, particularly as manifest in the collections of the Oxford Text Archive and other collections of the period. It is therefore unsurprising that it seems to have become, if not a de facto standard, at least a common point of departure for electronic text centres and encoding projects world wide. Maybe the fact that we actually produced this shortish, readable, manual for it also helped.

Early adopters of TEI Lite included a number of Electronic Text Centers and digital library initiatives. It was also adopted as the basis for some early TEI-conformant authoring systems, and as the basis for introductory tutorials, many of them in languages other than English (see further the list of legacy versions at ).

In 2002, following the publication of TEI P4, the XML version of the TEI Guidelines, which uses the generation of TEI Lite as an example of the TEI modification mechanism, the opportunity was taken to produce a lightly revised XML-conformant version. In 2006, a more substantially revised version based on TEI P5 was produced; this reflected the many changes between TEI P4 and TEI P5, but was not otherwise significantly different. In 2012, the TEI Technical Council, decided that a final revision should be undertaken to ensure that the documentation remained consistent with the latest (2.1) release of TEI P5. This version uses a recently added mechanism in the TEI customization architecture, which permits a customization to define only the TEI elements to be included in a schema, rather than the elements to be excluded from it. As such it is probably more resilient to change than earlier versions.

Lou Burnard, August 2012

This document provides an introduction to the recommendations of the Text Encoding Initiative (TEI), by describing a specific subset of the full TEI encoding scheme. The scheme documented here can be used to encode a wide variety of commonly encountered textual features, in such a way as to maximize the usability of electronic transcriptions and to facilitate their interchange among scholars using different computer systems. It is fully compatible with the full TEI scheme, as defined by TEI document P5, Guidelines for Electronic Text Encoding and Interchange, as of February 2006, and available from the TEI Consortium website at .

Introduction

The Text Encoding Initiative (TEI) Guidelines are addressed to anyone who wants to interchange information stored in an electronic form. They emphasize the interchange of textual information, but other forms of information such as images and sound are also addressed. The Guidelines are equally applicable in the creation of new resources and in the interchange of existing ones.

The Guidelines provide a means of making explicit certain features of a text in such a way as to aid the processing of that text by computer software running on different machines. This process of making explicit we call markup or encoding. Any textual representation on a computer uses some form of markup; the TEI came into being partly because of the enormous variety of mutually incomprehensible encoding schemes currently besetting scholarship, and partly because of the expanding range of scholarly uses now being identified for texts in electronic form.

The TEI Guidelines describe an encoding scheme which can be expressed using a number of different formal languages. The first editions of the Guidelines used the Standard Generalized Markup Language (SGML); since 2002, this has been replaced by the use of the Extensible Markup Language (XML). These markup languages have in common the definition of text in terms of elements and attributes, and rules governing their appearance within a text. The TEI's use of XML is ambitious in its complexity and generality, but it is fundamentally no different from that of any other XML markup scheme, and so any general-purpose XML-aware software is able to process TEI-conformant texts.

Since 2001, the TEI has been a community initiative supported by an international membership consortium. It was originally an international research project sponsored by the Association for Computers and the Humanities, the Association for Computational Linguistics, and the Association for Literary and Linguistic Computing, with substantial funding over its first five years from the U.S. National Endowment for the Humanities, Directorate General XIII of the Commission of the European Communities, the Andrew W. Mellon Foundation, the Social Science and Humanities Research Council of Canada and others. The Guidelines were first published in May 1994, after six years of development involving many hundreds of scholars from different academic disciplines worldwide. During the years that followed, the Guidelines became increasingly influential in the development of the digital library, in the language industries, and even in the development of the World Wide Web itself. The TEI Consortium was set up in January 2001, and a year later produced an edition of the Guidelines entirely revised for XML compatibility. In 2004, it set about a major revision of the Guidelines to take full advantage of new schema languages, the first release of which appeared in 2005. This revision of the TEI Lite document conforms to version 2.1 of this most recent edition of the Guidelines, TEI P5, released in June 2012.

At the outset of its work, the overall goals of the TEI were defined by the closing statement of a planning conference held at Vassar College, N.Y., in November, 1987; these Poughkeepsie Principles were further elaborated in a series of design documents. The Guidelines, say these design documents, should:

- suffice to represent the textual features needed for research;
- be simple, clear, and concrete;
- be easy for researchers to use without special-purpose software;
- allow the rigorous definition and efficient processing of texts;
- provide for user-defined extensions;
- conform to existing and emergent standards.

The world of scholarship is large and diverse. For the Guidelines to have wide acceptability, it was important to ensure that:

- the common core of textual features be easily shared;
- additional specialist features be easy to add to (or remove from) a text;
- multiple parallel encodings of the same feature should be possible;
- the richness of markup should be user-defined, with a very small minimal requirement;
- adequate documentation of the text and its encoding should be provided.

The present document describes a manageable selection from the extensive set of elements and recommendations resulting from those design goals, which is called TEI Lite.

In selecting from the several hundred elements defined by the full TEI scheme, we have tried to identify a useful starter set, comprising the elements which almost every user should know about. Experience working with TEI Lite will be invaluable in understanding the full TEI scheme and in knowing how to integrate specialized parts of it into the general TEI framework.

Our goals in defining this subset may be summarized as follows:

- it should be able to handle adequately a reasonably wide variety of texts, at the level of detail found in existing practice (as demonstrated in, for example, the holdings of the Oxford Text Archive);
- it should be useful for the production of new documents (such as this one) as well as the encoding of existing texts;
- it should be usable with a wide range of existing XML software;
- it should be a pure subset of the full TEI scheme and defined using the customizaticon methods described in the TEI Guidelines;
- it should be as small and simple as is consistent with the other goals.

The reader may judge our success in meeting these goals for him or herself.

Although we have tried to make this document self-contained, as suits a tutorial text, the reader should be aware that it does not cover every detail of the TEI encoding scheme. All of the elements described here are fully documented in the TEI Guidelines themselves, which should be consulted for authoritative reference information on these, and on the many others which are not described here. Some basic knowledge of XML is assumed.

A Short Example

We begin with a short example, intended to show what happens when a passage of prose is typed into a computer by someone with little sense of the purpose of mark-up, or the potential of electronic texts. In an ideal world, such output might be generated by a very accurate optical scanner. It attempts to be faithful to the appearance of the printed text, by retaining the original line breaks, by introducing blanks to represent the layout of the original headings and page breaks, and so forth. Where characters not available on the keyboard are needed (such as the accented letter a in faàl or the long dash), it attempts to mimic their appearance.

CHAPTER 38

READER, I married him. A quiet wedding we had: he and I, the par-
son and clerk, were alone present. When we got back from church, I
went into the kitchen of the manor-house, where Mary was cooking
the dinner, and John cleaning the knives, and I said --
'Mary, I have been married to Mr Rochester this morning.' The
housekeeper and her husband were of that decent, phlegmatic
order of people, to whom one may at any time safely communicate a
remarkable piece of news without incurring the danger of having
one's ears pierced by some shrill ejaculation and subsequently stunned
by a torrent of wordy wonderment. Mary did look up, and she did
stare at me; the ladle with which she was basting a pair of chickens
roasting at the fire, did for some three minutes hang suspended in air,
and for the same space of time John's knives also had rest from the
polishing process; but Mary, bending again over the roast, said only --
'Have you, miss? Well, for sure!'
A short time after she pursued, 'I seed you go out with the master,
but I didn't know you were gone to church to be wed'; and she
basted away. John, when I turned to him, was grinning from ear to
ear.
'I telled Mary how it would be,' he said: 'I knew what Mr Ed-
ward' (John was an old servant, and had known his master when he
was the cadet of the house, therefore he often gave him his Christian
name) -- 'I knew what Mr Edward would do; and I was certain he
would not wait long either: and he's done right, for aught I know. I
wish you joy, miss!' and he politely pulled his forelock.
'Thank you, John. Mr Rochester told me to give you and Mary
this.'
I put into his hand a five-pound note.  Without waiting to hear
more, I left the kitchen. In passing the door of that sanctum some time
after, I caught the words --
'She'll happen do better for him nor ony o' t' grand ladies.' And
again, 'If she ben't one o' th' handsomest, she's noan faa\l, and varry
good-natured; and i' his een she's fair beautiful, onybody may see
that.'
I wrote to Moor House and to Cambridge immediately, to say what
I had done: fully explaining also why I had thus acted. Diana and

474

JANE EYRE                      475

Mary approved the step unreservedly. Diana announced that she
would just give me time to get over the honeymoon, and then she
would come and see me.
'She had better not wait till then, Jane,' said Mr Rochester, when I
read her letter to him; 'if she does, she will be too late, for our honey-
moon will shine our life long: its beams will only fade over your
grave or mine.'
How St John received the news I don't know: he never answered
the letter in which I communicated it: yet six months after he wrote
to me, without, however, mentioning Mr Rochester's name or allud-
ing to my marriage. His letter was then calm, and though very serious,
kind. He has maintained a regular, though not very frequent correspond-
ence ever since: he hopes I am happy, and trusts I am not of those who
live without God in the world, and only mind earthly things.

This transcription suffers from a number of shortcomings:

- the page numbers and running titles are intermingled with the text in a way which makes it difficult for software to disentangle them;
- no distinction is made between single quotation marks and apostrophe, so it is difficult to know exactly which passages are in direct speech;
- the preservation of the copy text's hyphenation means that simple-minded search programs will not find the broken words;
- the accented letter in faàl and the long dash have been rendered by ad hoc keying conventions which follow no standard pattern and will be processed correctly only if the transcriber remembers to mention them in the documentation;
- paragraph divisions are marked only by the use of white space, and hard carriage returns have been introduced at the end of each line. Consequently, if the size of type used to print the text changes, reformatting will be problematic.

We now present the same passage, as it might be encoded using the TEI Guidelines. As we shall see, there are many ways in which this encoding could be extended, but as a minimum, the TEI approach allows us to represent the following distinctions:

- Paragraph and chapter divisions are now marked explicitly.
- Apostrophes are distinguished from quotation marks; direct speech is explicitly marked.
- The accented letter and the long dash are correctly represented.
- Page divisions have been marked with an empty <pb> element alone.
- The lineation of the original has not been retained and words broken by typographic accident at the end of a line have been re-assembled without comment.
- For convenience of proof reading, a new line has been introduced at the start of each paragraph, but the indentation is removed.

<pb n="474"/>
<div type="chapter" n="38">
  <p>Reader, I married him. A quiet wedding we had: he and I, the parson and clerk, were alone
  present. When we got back from church, I went into the kitchen of the manor-house, where
  Mary was cooking the dinner, and John cleaning the knives, and I said —</p>
  <p>
    <q>Mary, I have been married to Mr Rochester this morning.</q> The housekeeper and her
    husband were of that decent, phlegmatic order of people, to whom one may at any time safely
    communicate a remarkable piece of news without incurring the danger of having one's ears
    pierced by some shrill ejaculation and subsequently stunned by a torrent of wordy
    wonderment. Mary did look up, and she did stare at me; the ladle with which she was basting
    a pair of chickens roasting at the fire, did for some three minutes hang suspended in air,
    and for the same space of time John's knives also had rest from the polishing process; but
  Mary, bending again over the roast, said only —</p>
  <p>
    <q>Have you, miss? Well, for sure!</q>
  </p>
  <p>A short time after she pursued, <q>I seed you go out with the master, but I didn't know
  you were gone to church to be wed</q>; and she basted away. John, when I turned to him, was
  grinning from ear to ear. <q>I telled Mary how it would be,</q> he said: <q>I knew what Mr
  Edward</q> (John was an old servant, and had known his master when he was the cadet of the
  house, therefore he often gave him his Christian name) — <q>I knew what Mr Edward would do;
  and I was certain he would not wait long either: and he's done right, for aught I know. I
  wish you joy, miss!</q> and he politely pulled his forelock.</p>
  <p>
    <q>Thank you, John. Mr Rochester told me to give you and Mary this.</q>
  </p>
  <p>I put into his hand a five-pound note. Without waiting to hear more, I left the kitchen.
  In passing the door of that sanctum some time after, I caught the words —</p>
  <p>
    <q>She'll happen do better for him nor ony o' t' grand ladies.</q> And again, <q>If she
    ben't one o' th' handsomest, she's noan faàl, and varry good-natured; and i' his een she's
    fair beautiful, onybody may see that.</q>
  </p>
  <p>I wrote to Moor House and to Cambridge immediately, to say what I had done: fully
  explaining also why I had thus acted. Diana and <pb n="475"/> Mary approved the step
  unreservedly. Diana announced that she would just give me time to get over the honeymoon,
  and then she would come and see me.</p>
  <p>
    <q>She had better not wait till then, Jane,</q> said Mr Rochester, when I read her letter
    to him; <q>if she does, she will be too late, for our honeymoon will shine our life long:
    its beams will only fade over your grave or mine.</q>
  </p>
  <p>How St John received the news I don't know: he never answered the letter in which I
  communicated it: yet six months after he wrote to me, without, however, mentioning Mr
  Rochester's name or alluding to my marriage. His letter was then calm, and though very
  serious, kind. He has maintained a regular, though not very frequent correspondence ever
  since: he hopes I am happy, and trusts I am not of those who live without God in the world,
  and only mind earthly things.</p>
</div>

This particular encoding represents a set of choices or priorities. As a trivial example, note that in the second example, end-of-line hyphenation has been silently removed. Conceivably Brontë (or her printer) intended the word honeymoon to appear as honey-moon on its second appearance, though this seems unlikely: our decision to focus on Brontë's text, rather than on the printing of it in this particular edition, makes it impossible to be certain. This is an instance of the fundamental selectivity of any encoding. An encoding makes explicit only those textual features of importance to the encoder. It is not difficult to think of ways in which the encoding of even this short passage might readily be extended. For example:

- a regularized form of the passages in dialect could be provided;
- footnotes glossing or commenting on any passage could be added;
- pointers linking parts of this text to others could be added;
- proper names of various kinds could be distinguished from the surrounding text;
- detailed bibliographic information about the text's provenance and context could be prefixed to it;
- a linguistic analysis of the passage into sentences, clauses, words, etc., could be provided, each unit being associated with appropriate category codes;
- the text could be segmented into narrative or discourse units;
- systematic analysis or interpretation of the text could be included in the encoding, with potentially complex alignment or linkage between the text and the analysis, or between the text and one or more translations of it;
- passages in the text could be linked to images or sound held on other media.

TEI-recommended ways of carrying out most of these are described in the remainder of this document. The TEI scheme as a whole also provides for an enormous range of other possibilities, of which we cite only a few:

- detailed analysis of the components of names;
- detailed meta-information providing thesaurus-style information about the text's origins or topics;
- information about the printing history or manuscript variations exhibited by a particular series of versions of the text.

For recommendations on these and many other possibilities, the full Guidelines should be consulted.

The Structure of a TEI Text

All TEI-conformant texts contain (a) a TEI header (marked up as a <teiHeader> element) and (b) the transcription of the text proper (marked up as a <text> element). These two elements are combined together to form a single <TEI> element, which must be declared within the TEI namespace[^1].

[^1: A namespace is an XML concept. Its function is to identify the vocabulary from which a group of element names are drawn, using a standard identifier resembling a web address. The namespace for all TEI elements is http://www.tei-c.org/ns/1.0]

The TEI header provides information analogous to that provided by the title page of a printed text. It has up to four parts: a bibliographic description of the machine-readable text, a description of the way it has been encoded, a non-bibliographic description of the text (a text profile), and a revision history. The header is described in more detail in section The Electronic Title Page.

A TEI text may be unitary (a single work) or composite (a collection of single works, such as an anthology). In either case, the text may have an optional front or back. In between is the body of the text, which, in the case of a composite text, may consist of groups, each containing more groups or texts.

A unitary text will be encoded using an overall structure like this:

<TEI>
  <teiHeader/>
  <text>
    <front/>
    <body/>
    <back/>
  </text>
</TEI>

A composite text also has an optional front and back. In between occur one or more groups of texts, each with its own optional front and back matter. A composite text will thus be encoded using an overall structure like this:

<TEI>
  <teiHeader/>
  <text>
    <front/>
    <group>
      <text>
        <front/>
        <body/>
        <back/>
      </text>
      <text>
        <front/>
        <body/>
        <back/>
      </text>

    </group>
    <back/>
  </text>
</TEI>

It is also possible to define a composite of complete TEI texts, each with its own header. Such a collection is known as a TEI corpus, and may itself have a header:

<teiCorpus>
  <teiHeader/>
  <TEI>
    <teiHeader/>
    <text/>
  </TEI>
  <TEI>
    <teiHeader/>
    <text/>
  </TEI>
</teiCorpus>

It is also possible to create a composite of corpora -- that is, one <teiCorpus> element may contain many nested <teiCorpus> elements rather than many nested <TEI> elements, to any depth considered necessary.

In the remainder of this document, we discuss chiefly simple text structures. The discussion in each case consists of a short list of relevant TEI elements with a brief definition of each, followed by definitions for any attributes specific to that element, and a reference to any classes of which the element is a member. These references are linked to full specifications for each object, as given in the TEI Guidelines. In most cases, short examples are also given.

For example, here are the elements discussed so far:

Encoding the Body

As indicated above, a simple TEI document at the textual level consists of the following elements: Elements specific to front and back matter are described below in section Front and Back Matter. In this section we discuss the elements making up the body of a text.

Text Division Elements

The body of a prose text may be just a series of paragraphs, or these paragraphs may be grouped together into chapters, sections, subsections, etc. Each paragraph is tagged using the <p> tag. The <div> element is used to represent any such grouping of paragraphs.

The @type attribute on the <div> element may be used to supply a conventional name for this category of text division, or otherwise distinguish them. Typical values might be book, chapter, section, part, poem, song, etc. For a given project, it will usually be advisable to define and adhere to a specific list of such values.

A <div> element may itself contain further, nested, <div>s, thus mimicking the traditional structure of a book, which can be decomposed hierarchically into units such as parts, containing chapters, containing sections, and so on. TEI texts in general conform to this simple hierarchic model.

The @xml:id attribute may be used to supply a unique identifier for the division, which may be used for cross references or other links to it, such as a commentary, as further discussed in section Cross References and Links. It is often useful to provide an @xml:id attribute for every major structural unit in a text, and to derive its values in some systematic way, for example by appending a section number to a short code for the title of the work in question, as in the examples below. It is particularly useful to supply such identifiers if the resource concerned is to be made available over the web, since they make it much easier for other web-based applications to link directly to the corresponding parts of your text.

The @n attribute may be used to supply (additionally or alternatively) a short mnemonic name or number for a division, or any other element. If a conventional form of reference or abbreviation for the parts of a work already exists (such as the book/chapter/verse pattern of Biblical citations), the @n attribute is the place to record it; unlike the identifier supplied by @xml:id, it does not need to be unique.

The @xml:lang attribute may be used to specify the language of the division. Languages are identified by an internationally defined code, as further discussed in section Foreign Words or Expressions below.

The @rend attribute may be used to supply information about the rendition (appearance) of a division, or any other element, as further discussed in section Marking Highlighted Phrases below. As with the @type attribute, a project will often find it useful to predefine the possible values for this attribute, but TEI Lite does not constrain it in anyway.

These four attributes, @xml:id, @n, @xml:lang, and @rend are so widely useful that they are allowed on any element in any TEI schema: they are global attributes. Other global attributes defined in the TEI Lite scheme are discussed in section Special kinds of Linking.

The value of every @xml:id attribute should be unique within a document. One simple way of ensuring that this is so is to make it reflect the hierarchic structure of the document. For example, Smith's Wealth of Nations as first published consists of five books, each of which is divided into chapters, while some chapters are further subdivided into parts. We might define @xml:id values for this structure as follows:

<body>
  <div xml:id="WN1" n="I" type="book">
    <div xml:id="WN101" n="I.1" type="chapter"/>
    <div xml:id="WN102" n="I.2" type="chapter"/>

    <div xml:id="WN110" n="I.10" type="chapter">
      <div xml:id="WN1101" n="I.10.1" type="part"/>
      <div xml:id="WN1102" n="I.10.2" type="part"/>
    </div>

  </div>
  <div xml:id="WN2" n="II" type="book"/>
</body>

A different numbering scheme may be used for @xml:id and @n attributes: this is often useful where a canonical reference scheme is used which does not tally with the structure of the work. For example, in a novel divided into books each containing chapters, where the chapters are numbered sequentially through the whole work, rather than within each book, one might use a scheme such as the following:

<body>
  <div xml:id="TS01" n="1" type="volume">
    <div xml:id="TS011" n="1" type="chapter"/>
    <div xml:id="TS012" n="2" type="chapter"/>
  </div>
  <div xml:id="TS02" n="2" type="volume">
    <div xml:id="TS021" n="3" type="chapter"/>
    <div xml:id="TS022" n="4" type="chapter"/>
  </div>
</body>

Here the work has two volumes, each containing two chapters. The chapters are numbered conventionally 1 to 4, but the @xml:id values specified allow them to be regarded additionally as if they were numbered 1.1, 1.2, 2.1, 2.2.

Headings and Closings

Every <div> may have a title or heading at its start, and (less commonly) a trailer such as End of Chapter 1 at its end. The following elements may be used to transcribe them: Some other elements which may be necessary at the beginning or ending of text divisions are discussed below in section Prefatory Matter.

Whether or not headings and trailers are included in a transcription is a matter for the individual transcriber to decide. Where a heading is completely regular (for example Chapter 1) or may be automatically constructed from attribute values (e.g. <div type="chapter" n="1">), it may be omitted; where it contains otherwise unrecoverable text it should always be included. For example, the start of Hardy's Under the Greenwood Tree might be encoded as follows:

<div xml:id="UGT1" n="Winter" type="Part">
  <div xml:id="UGT11" n="1" type="Chapter">
    <head>Mellstock-Lane</head>
    <p>To dwellers in a wood almost every species of tree ... </p>
  </div>
</div>

Prose, Verse and Drama

As in the Bronte example above, the paragraphs making up a textual division are tagged with the <p> tag. In poetic or dramatic texts different tags are needed, to represent verse lines and stanzas in the first case, or individual speeches and stage directions in the second. :

Here, for example, is the start of a poetic text in which verse lines and stanzas are tagged:

<lg n="I">
  <l>I Sing the progresse of a
  deathlesse soule,</l>
  <l>Whom Fate, with God made, but doth not controule,</l>
  <l>Plac'd in
  most shapes; all times before the law</l>
  <l>Yoak'd us, and when, and since, in this I
  sing.</l>
  <l>And the great world to his aged evening;</l>
  <l>From infant morne, through manly
  noone I draw.</l>
  <l>What the gold Chaldee, of silver Persian saw,</l>
  <l>Greeke brass, or
  Roman iron, is in this one;</l>
  <l>A worke t'out weare Seths pillars, bricke and
  stone,</l>
  <l>And (holy writs excepted) made to yeeld to none,</l>
</lg>

Note that the <l> element marks verse lines, not typographic lines: the original lineation of the first few lines above has not therefore been made explicit by this encoding, and may be lost. The <lb> element described in section Page and Line Numbers might additionally be used to mark typographic lines if so desired.

Here is the end of a famous dramatic text, in which speeches and stage directions are marked:

<sp>
  <speaker>Vladimir</speaker>
  <p>Pull on your trousers.</p>
</sp>
<sp>
  <speaker>Estragon</speaker>
  <p>You want me to pull off my trousers?</p>
</sp>
<sp>
  <speaker>Vladimir</speaker>
  <p>Pull <emph>on</emph> your trousers.</p>
</sp>
<sp>
  <speaker>Vladimir</speaker>
  <p>
    <stage>(realizing his trousers are down)</stage>.
  True</p>
</sp>
<stage>He pulls up his trousers</stage>
<sp>
  <speaker>Vladimir</speaker>
  <p>Well? Shall we go?</p>
</sp>
<sp>
  <speaker>Estragon</speaker>
  <p>Yes, let's go.</p>
</sp>
<stage>They do not move.</stage>

Note that the <stage> (stage direction) element can appear either within a speech or between speeches. The <sp> ("speech") element contains, following an optional <speaker> element indicating who is speaking, either paragraphs (if the speech is in prose) or verse lines or stanzas as in the next example. In this case, it is quite common to find that verse lines are split between speakers. The easiest way of encoding this is to use the @part attribute to indicate that the lines so fragmented are incomplete :

<div type="Act" n="I">
  <head>ACT I</head>
  <div type="Scene" n="1">
    <head>SCENE I</head>
    <stage rend="italic"> Enter Barnardo and Francisco, two Sentinels, at several doors</stage>
    <sp>
      <speaker>Barn</speaker>
      <l part="Y">Who's there?</l>
    </sp>
    <sp>
      <speaker>Fran</speaker>
      <l>Nay, answer me. Stand and unfold yourself.</l>
    </sp>
    <sp>
      <speaker>Barn</speaker>
      <l part="I">Long live the King!</l>
    </sp>
    <sp>
      <speaker>Fran</speaker>
      <l part="M">Barnardo?</l>
    </sp>
    <sp>
      <speaker>Barn</speaker>
      <l part="F">He.</l>
    </sp>
    <sp>
      <speaker>Fran</speaker>
      <l>You come most carefully upon your hour.</l>
    </sp>

  </div>
</div>

The same mechanism may be applied to stanzas which are divided between two speakers:

<div>
  <sp>
    <speaker>First voice</speaker>
    <lg type="stanza" part="I">
      <l>But why drives on that ship so fast</l>
      <l>Withouten wave or wind?</l>
    </lg>
  </sp>
  <sp>
    <speaker>Second Voice</speaker>
    <lg part="F">
      <l>The air is cut away before.</l>
      <l>And closes from behind.</l>
    </lg>
  </sp>

</div>

The <sp> element can also be used for dialogue presented in a prose work as if it were drama, as in the next example, which also demonstrates the use of the @who attribute to bear a code identifying the speaker of the piece of dialogue concerned:

<div>
  <sp who="#OPI">
    <speaker>The reverend Doctor Opimian</speaker>
    <p>I do not think I have named a single unpresentable fish.</p>
  </sp>
  <sp who="#GRM">
    <speaker>Mr Gryll</speaker>
    <p>Bream, Doctor: there is not much to be said for bream.</p>
  </sp>
  <sp who="#OPI">
    <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>
</div>

Here the @who attribute values (#OPI etc.) are links, pointing to a list of the characters in the novel, each of which has an identifier:

<list>
  <head>Characters in the novel</head>
  <item xml:id="OPI">
  <name>Dr Opimian</name> : named for the famous Roman fine wine</item>
  <item xml:id="GRM">
    <name>Mr Gryll</name> : named for the mythical Gryllus, one of Ulysses'
    sailors transformed by Circe into a pig, who argues that he was happier in that state than
  as a man</item>
</list>

Page and Line Numbers

Page and line breaks etc. may be marked with the following elements. These elements mark a single point in the text, not a span of text. The global @n attribute should be used to supply the number of the page or line beginning at the tag.

When working from a paginated original, it is often useful to record its pagination, if only to simplify later proof-reading. It is also useful for synchronizing an encoded text with a set of page images. Recording the line breaks may be useful for similar reasons.

If features such as pagination or lineation are marked for more than one edition, specify the edition in question using the @ed attribute, and supply as many tags are necessary. For example, in the following passage we indicate where the page breaks occur in two different editions ("ED1" and "ED2")

<p>I wrote to Moor House and to Cambridge immediately, to say what I had done: fully
explaining also why I had thus acted. Diana and <pb ed="ED1" n="475"/> Mary approved the step
unreservedly. Diana announced that she would <pb ed="ED2" n="485"/>just give me time to get
over the honeymoon, and then she would come and see me.</p>

A special attribute @break may be used to indicate whether or not this empty element is considered as a word-breaking, irrespective of any adjacent whitespace. For example, in the following encoded sample:

The <pb> and <lb> elements are special cases of the general class of milestone elements which mark reference points within a text. The generic <milestone> element can mark any kind of reference point: for example, a column break, the start of a new kind of section not otherwise tagged, or in general any significant change in the text not marked by an XML element. The names used for types of unit and for editions referred to by the @ed and @unit attributes may be chosen freely, but should be documented in the header <refsDecl> element (see Reference and Classification Declarations). The <milestone> element may be used to replace the others, or the others may be used as a set; they should not be mixed arbitrarily.

Marking Highlighted Phrases

Changes of Typeface, etc.

Highlighted words or phrases are those made visibly different from the rest of the text, typically by a change of type font, handwriting style, ink colour etc., which is intended to draw the reader's attention to some associated change.

The global @rend attribute can be attached to any element, and used wherever necessary to specify details of the highlighting used for it in the source. For example, a heading rendered in bold might be tagged <head rend="bold">, and one in italic <head rend="italic">.

The values to be used for the @rend attribute are not specified by the TEI Guidelines, since they will depend entirely on the needs of the particular project. Some typical values might include italic, bold etc. for font variations; center, right etc. for alignment; large, small etc. for size; smallcaps, allcaps etc. for type variants and so on. Several such words may be used in combination as necessary, but no formal syntax is proposed. The full TEI Guidelines provide more rigorous mechanisms, using other W3C standards such as CSS, as an alternative to the use of @rend.

It is not always possible or desirable to interpret the reasons for such changes of rendering in a text. In such cases, the element <hi> may be used to mark a sequence of highlighted text without making any claim as to its status.

In the following example, the use of a distinct typeface for the subheading and for the included name are recorded but not interpreted:

<p>
  <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 ...</p>

Alternatively, where the cause for the highlighting can be identified with confidence, a number of other, more specific, elements are available.

Some features (notably quotations and glosses) may be found in a text either marked by highlighting, or with quotation marks. In either case, the elements <q> and <gloss> (as discussed in the following section) should be used. If the highlighting is to be recorded, use the global @rend attribute.

As an example of the elements defined here, consider the following sentence: On the one hand the Nibelungenlied is associated with the new rise of romance of twelfth-century France, the romans d'antiquité, the romances of Chrétien de Troyes, and the German adaptations of these works by Heinrich van Veldeke, Hartmann von Aue, and Wolfram von Eschenbach. Interpreting the role of the highlighting, the sentence might look like this:

<p>On the one hand the <title>Nibelungenlied</title>
is associated with the new rise of romance of twelfth-century France, the <foreign>romans
d'antiquité</foreign>, the romances of Chrétien de Troyes, ...</p>

Describing only the appearance of the original, it might look like this:

<p>On the one hand the <hi rend="italic">Nibelungenlied</hi> is associated with the new rise of romance of twelfth-century France,
the <hi rend="italic">romans d'antiquité</hi>, the romances of Chrétien de Troyes,
...</p>

Quotations and Related Features

Like changes of typeface, quotation marks are conventionally used to denote several different features within a text, of which the most frequent is quotation. When possible, we recommend that the underlying feature be tagged, rather than the simple fact that quotation marks appear in the text, using the following elements:

Here is a simple example of a quotation:

<p>Few dictionary makers are likely to forget Dr. Johnson's description of the
lexicographer as <q>a harmless drudge.</q>
</p>

To record how a quotation was printed (for example, in-line or set off as a display or block quotation), the @rend attribute should be used. This may also be used to indicate the kind of quotation marks used.

Direct speech interrupted by a narrator can be represented simply by ending the quotation and beginning it again after the interruption, as in the following example:

<p>
  <q>Who-e debel you?</q> — he at last said —
  <q>you no speak-e, damme, I kill-e.</q> And so saying, the lighted tomahawk began
flourishing about me in the dark.</p>

If it is important to convey the idea that the two <q> elements together make up a single speech, the linking attributes @next and @prev may be used, as described in section Special kinds of Linking.

Quotations may be accompanied by a reference to the source or speaker, using the @who attribute, whether or not this is explicit in the text, as in the following example:

<q who="#Wilson">Spaulding, he came
down into the office just this day eight weeks with this very paper in his hand, and he
says:—<q who="#Spaulding">I wish to the Lord, Mr. Wilson, that I was a red-headed
man.</q>
</q>

This example also demonstrates how quotations may be embedded within other quotations: one speaker (Wilson) quotes another speaker (Spaulding).

The creator of the electronic text must decide whether quotation marks are replaced by the tags or whether the tags are added and the quotation marks kept. If the quotation marks are removed from the text, the @rend attribute may be used to record the way in which they were rendered in the copy text.

The full TEI Guidelines provide additional elements to distinguish direct speech, quotation, and other typical uses of quotation mark although it is not always possible and may not be considered desirable to interpret the function of quotation marks in a text. For simplicity, only <q> (which may be used for any such case) has been included in TEI Lite.

Foreign Words or Expressions

Words or phrases which are not in the main language of the texts may be tagged as such in one of two ways. If the word or phrase is already tagged for some reason, the element indicated should bear a value for the global @xml:lang attribute indicating the language used. Where there is no applicable element, the element <foreign> may be used, again using the @xml:lang attribute. For example:

<p>John has real <foreign xml:lang="fr">savoir-faire</foreign>.</p>
<p>Have you read <title xml:lang="de">Die
Dreigroschenoper</title>?</p>
<p>
  <mentioned xml:lang="fr">Savoir-faire</mentioned> is French
for know-how.</p>
<p>The court issued a writ of <term xml:lang="la">mandamus</term>.</p>

As these examples show, the <foreign> element should not be used to tag foreign words if some other more specific element such as <title>, <mentioned>, or <term> applies. The global @xml:lang attribute may be attached to any element to show that it uses some other language than that of the surrounding text.

The codes used to identify languages, supplied on the @xml:lang attribute, must be constructed in a particular way, and must conform to common Internet standards[^2], as further explained in the relevant section of the TEI Guidelines. Some simple example codes for a few languages are given here:

zh	Chinese	grc	Ancient Greek
en	English	el	Greek
enm	Middle English	ja	Japanese
fr	French	la	Latin
de	German	sa	Sanskrit

[^2: The relevant standard is Best Current Practice 47 (). The authoritative list of registered subtags is maintained by IANA and is available at . For a general overview of the construction of language tags, see , and for a practical step-by-step guide, see .]

Notes

All notes, whether printed as footnotes, endnotes, marginalia, or elsewhere, should be marked using the same element: Where possible, the body of a note should be inserted in the text at the point at which its identifier or mark first appears. This may not be possible for example with marginalia, which may not be anchored to an exact location. For simplicity, it may be adequate to position marginal notes before the relevant paragraph or other element. Notes may also be placed in a separate division of the text (as end-notes are, in printed books) and linked to the relevant portion of the text using their @target attribute.

The @n attribute may be used to supply the number or identifier of a note if this is required. The @resp attribute should be used consistently to distinguish between authorial and editorial notes, if the work has both kinds.

Examples:

<p>Collections are ensembles of
distinct entities or objects of any sort. <note place="foot" n="1"> We explain below why we
use the uncommon term <mentioned>collection</mentioned> instead of the expected
<mentioned>set</mentioned>. Our usage corresponds to the <mentioned>aggregate</mentioned>
of many mathematical writings and to the sense of <mentioned>class</mentioned> found in
older logical writings. </note> The elements ...</p>

<lg xml:id="RAM609">
  <note place="margin">The
  curse is finally expiated</note>
  <l>And now this spell was snapt: once more</l>
  <l>I viewed
  the ocean green,</l>
  <l>And looked far forth, yet little saw</l>
  <l>Of what had else been seen
  —</l>
</lg>

Cross References and Links

Explicit cross references or links from one point in a text to another in the same or another document may be encoded using the elements described in this section. Implicit links (such as the association between two parallel texts, or that between a text and its interpretation) may be encoded using the linking attributes discussed in section Special kinds of Linking.

Simple Cross References

A cross reference from one point within a single document to another can be encoded using either of the following elements:

The difference between these two elements is that <ptr> is an empty element, simply marking a point from which a link is to be made, whereas <ref> may contain some text as well, typically identifying the target of the cross reference. The <ptr> element would be used for a cross reference which is to be indicated by some non-verbal means such as a symbol or icon, or in an electronic text by a button. It is also useful in document production systems, where the formatter can generate the correct verbal form of the cross reference.

The following two forms, for example, are logically equivalent :

See especially <ref target="#SEC12">section 12 on
page 34</ref>.

See especially <ptr target="#SEC12"/>. The value of the @target attribute on either element may be the identifier of some other element within the current document. The passage or phrase being pointed at must bear an identifier, and must therefore be tagged as an element of some kind. In the following example, the cross reference is to a <div> element:

... see especially <ptr target="#SEC12"/>. ... <div xml:id="SEC12">
     <head>Concerning Identifiers</head>

   </div>

Because the @xml:id attribute is global, any element in a TEI document may be pointed to in this way. In the following example, a paragraph has been given an identifier so that it may be pointed at:

... this is
     discussed in <ref target="#pspec">the paragraph on links</ref> ... <p xml:id="pspec">Links
     may be made to any kind of element ...</p>

Sometimes the target of a cross reference does not correspond with any particular feature of a text, and so may not be tagged as an element of some kind. If the desired target is simply a point in the current document, the easiest way to mark it is by introducing an <anchor> element at the appropriate spot. If the target is some sequence of words not otherwise tagged, the <seg> element may be introduced to mark them. These two elements are described as follows:

In the following (imaginary) example, <ref> elements have been used to represent points in this text which are to be linked in some way to other parts of it; in the first case to a point, and in the second, to a sequence of words:

Returning to <ref target="#ABCD">the point where I
     dozed off</ref>, I noticed that <ref target="#EFGH">three words</ref> had been circled in
     red by a previous reader

This encoding requires that elements with the specified identifiers (ABCD and EFGH in this example) are to be found somewhere else in the current document. Assuming that no element already exists to carry these identifiers, the <anchor> and <seg> elements may be used:

....
     <anchor type="bookmark" xml:id="ABCD"/> .... ....<seg type="target" xml:id="EFGH"> ...
     </seg> ...

The @type attribute should be used (as above) to distinguish amongst different purposes for which these general purpose elements might be used in a text. Some other uses are discussed in section Special kinds of Linking below.

Pointing to other documents

So far, we have shown how the elements <ptr> and <ref> may be used for cross-references or links whose targets occur within the same document as their source. However, the same elements may also be used to refer to elements in any other XML document or resource, such as a document on the web, or a database component. This is possible because the value of the @target attribute may be any valid universal resource indicator (URI)[^3].

[^3: A full definition of this term, defined by the W3C (the consortium which manages the development and maintenance of the World Wide Web), is beyond the scope of this tutorial: however, the most frequently encountered version of a URI is the familiar URL used to indicate a web page, such as http://www.tei-c.org/index.xml]

A URI may reference a web page or just a part of one, for example http://www.tei-c.org/index.xml#SEC2. The sharp sign indicates that what follows it is the identifier of an element to be located within the XML document identified by what precedes it: this example will therefore locate an element which has an @xml:id attribute value of "SEC2" within the document retrieved from http://www.tei-c.org/index.xml. In the examples we have discussed so far, the part to the left of the sharp sign has been omitted: this is understood to mean that the referenced element is to be located within the current document.

Parts of an XML document can be specified by means of other more sophisticated mechanisms using a special language called Xpath, also defined by the W3C. This is particularly useful where the elements to be linked to do not bear identifiers and must therefore be located by some other means.

Special kinds of Linking

The following special purpose linking attributes are defined for every element in the TEI Lite scheme:

@ana
- links an element with its interpretation.
@corresp
- links an element with one or more other corresponding elements.
@next
- links an element to the next element in an aggregate.
@prev
- links an element to the previous element in an aggregate.

The @ana (analysis) attribute is intended for use where a set of abstract analyses or interpretations have been defined somewhere within a document, as further discussed in section Interpretation and Analysis. For example, a linguistic analysis of the sentence John loves Nancy might be encoded as follows:

<seg type="sentence" ana="SVO">
  <seg type="lex" ana="#NP1">John</seg>
  <seg type="lex" ana="#VVI">loves</seg>
  <seg type="lex" ana="#NP1">Nancy</seg>
</seg>

This encoding implies the existence elsewhere in the document of elements with identifiers "SVO", "NP1", and "VV1" where the significance of these particular codes is explained. Note the use of the <seg> element to mark particular components of the analysis, distinguished by the @type attribute.

The @corresp (corresponding) attribute provides a simple way of representing some form of correspondence between two elements in a text. For example, in a multilingual text, it may be used to link translation equivalents, as in the following example

<seg xml:lang="fr" xml:id="FR1" corresp="#EN1">Jean
aime Nancy</seg>
<seg xml:lang="en" xml:id="EN1" corresp="#FR1">John loves
Nancy</seg>

The same mechanism may be used for a variety of purposes. In the following example, it has been used to represent the correspondences between the show and Shirley, and between NBC and the network:

<p>
  <title xml:id="shirley">Shirley</title>, which
  made its Friday night debut only a month ago, was not listed on <name xml:id="nbc">NBC</name>'s new schedule, although <seg xml:id="network" corresp="#nbc">the network</seg>
  says <seg xml:id="show" corresp="#shirley">the show</seg> still is being
considered.</p>

The @next and @prev attributes provide a simple way of linking together the components of a discontinuous element, as in the following example:

<q xml:id="Q1a" next="#Q1b">Who-e debel you?</q> —
he at last said — <q xml:id="Q1b" prev="#Q1a">you no speak-e, damme, I kill-e.</q> And so
saying, the lighted tomahawk began flourishing about me in the dark.

Editorial Interventions

The process of encoding an electronic text has much in common with the process of editing a manuscript or other text for printed publication. In either case a conscientious editor may wish to record both the original state of the source and any editorial correction or other change made in it. The elements discussed in this and the next section provide some facilities for meeting these needs.

Correction and Normalization

The following elements may be used to mark correction, that is editorial changes introduced where the editor believes the original to be erroneous:

The following elements may be used to mark normalization, that is editorial changes introduced for the sake of consistency or modernization of a text:

As an example, consider this extract from the quarto printing of Shakespeare's Henry V. ... for his nose was as sharp as a pen and a table of green feelds

A modern editor might wish to make a number of interventions here, specifically to modernize (or normalise) the Elizabethan spellings of a' and feelds for he and fields respectively. He or she might also want to emend table to babbl'd, following an editorial tradition that goes back to the 18th century Shakespearian scholar Lewis Theobald. The following encoding would then be appropriate:

... for his nose was as sharp as
a pen and <reg>he</reg>
<corr resp="#Theobald">babbl'd</corr> of green <reg>fields</reg>

A more conservative or source-oriented editor, however, might want to retain the original, but at the same time signal that some of the readings it contains are in some sense anomalous:

... for his nose was as sharp as a pen and
<orig>a</orig>
<sic>table</sic> of green <orig>feelds</orig>

Finally, a modern digital editor may decide to combine both possibilities in a single composite text, using the <choice> element. This allows an editor to mark where alternative readings are possible:

... for his nose was as sharp as a pen and
<choice>
  <orig>a</orig>
  <reg>he</reg>
</choice>
<choice>
  <corr resp="#Theobald">babbl'd</corr>
  <sic>table</sic>
  </choice> of green
  <choice>
    <orig>feelds</orig>
    <reg>fields</reg>
  </choice>

Omissions, Deletions, and Additions

In addition to correcting or normalizing words and phrases, editors and transcribers may also supply missing material, omit material, or transcribe material deleted or crossed out in the source. In addition, some material may be particularly hard to transcribe because it is hard to make out on the page. The following elements may be used to record such phenomena:

These elements may be used to record changes made by an editor, by the transcriber, or (in manuscript material) by the author or scribe. For example, if the source for an electronic text read The following elements are provided for for simple editorial interventions. then it might be felt desirable to correct the obvious error, but at the same time to record the deletion of the superfluous second for, thus: The following elements are provided for <del resp="#LB">for</del> simple editorial interventions. The attribute value #LB on the @resp attribute is used to point to a fuller definition (typically in a <respStmt> element) for the agency responsible for correcting the duplication of for.

If the source read The following elements provided for simple editorial interventions. (i.e. if the verb had been inadvertently dropped) then the corrected text might read: The following elements <add resp="#LB">are</add> provided for simple editorial interventions.

These elements are also used to record authorial changes in manuscripts. A manuscript in which the author has first written How it galls me, what a galling shadow, then crossed out the word galls and inserted dogs might be encoded thus:

How it <del hand="#DHL" type="overstrike">galls</del>
<add hand="#DHL" place="supralinear">dogs</add> me, what a galling shadow

Again, the code #DHL points to another location where more information about the hand concerned is to be found [The full TEI provides a range of elements for encoding metadata about manuscript production and description, which are not however included in TEI Lite].

Similarly, the <unclear> and <gap> elements may be used together to indicate the omission of illegible material; the following example also shows the use of <add> for a conjectural emendation:

One hundred
  &amp; twenty good regulars joined to me <unclear>
  <gap reason="indecipherable"/>
</unclear>
&amp; instantly, would aid me signally <add hand="#ed">in?</add> an enterprise against
Wilmington.

The <del> element marks material which has been transcribed as part of the electronic text despite being marked as deleted, while <gap> marks the location of material which is omitted from the electronic text, whether it is legible or not. A language corpus, for example, might omit long quotations in foreign languages:

<p> ... An example of a list appearing in a fief
ledger of <name type="place">Koldinghus</name>
<date>1611/12</date> is given below. It shows cash income from a sale of
honey.</p>
<gap>
  <desc>quotation from ledger (in Danish)</desc>
</gap>
<p>A description of the
overall structure of the account is once again ... </p>

Other corpora (particular those constructed before the widespread use of scanners) systematically omit figures and mathematics:

  <p>At the bottom of your screen below the mode line is the <term>minibuffer</term>. This is
  the area where Emacs echoes the commands you enter and where you specify filenames for Emacs
  to find, values for search and replace, and so on. <gap reason="graphic">
  <desc>diagram of
  Emacs screen</desc>
</gap>
  </p>

The full TEI scheme provides more precise ways of capturing different aspects of a transcription, distinguishing for example between text added or supplied by the encoder and text indicated as supplied or deleted in the source. TEI Lite does not provide different tags for these purposes.

Abbreviations and their Expansion

Like names, dates, and numbers, abbreviations may be transcribed as they stand or expanded; they may be left unmarked, or encoded using the following elements:

The <abbr> element is useful as a means of distinguishing semi-lexical items such as acronyms or jargon:

We can sum up the above
discussion as follows: the identity of a <abbr>CC</abbr> is defined by that calibration of
values which motivates the elements of its <abbr>GSP</abbr>;

Every manufacturer of <abbr>3GL</abbr> or
<abbr>4GL</abbr> languages is currently nailing on <abbr>OOP</abbr> extensions

The @type attribute may be used to distinguish types of abbreviation by their function.

The <expan> element is used to mark an expansion supplied by an encoder. This element is particularly useful in the transcription of manuscript materials. For example, the character p with a bar through its descender as a conventional representation for the word "per" is commonly encountered in Medieval European manuscripts. An encoder may choose to expand this as follows: <expan>per</expan>

The expansion corresponding with an abbreviated form may not always contain the same letters as the abbreviation. Where it does, however, common editorial practice is to italicize or otherwise signal which letters have been supplied. The <expan> element should not be used for this purpose since its function is to indicate an expanded form, not a part of one. For example, consider the common abbreviation "wt" (for "with") found in medieval texts. In a modern edition, an editor might wish to represent this as with , italicising the letters not found in the source. One simple means of achieving that would be an encoding such as the follow

<expan>w<hi rend="it">i</hi>t<hi rend="it">h</hi>
</expan>

The full TEI also provides elements <ex> and <am> for use in this situation, but these are not included in the TEI Lite schema.

To record both an abbreviation and its expansion, the <choice> element mentioned above may be used to group the abbreviated form with its proposed expansion:

<choice>
  <abbr>wt</abbr>
  <expan>with</expan>
</choice>

Names, Dates, and Numbers

The TEI scheme defines elements for a large number of data-like features which may appear almost anywhere within almost any kind of text. These features may be of particular interest in a range of disciplines; they all relate to objects external to the text itself, such as the names of persons and places, numbers and dates. They also pose particular problems for many natural language processing (NLP) applications because of the variety of ways in which they may be presented within a text. The elements described here, by making such features explicit, reduce the complexity of processing texts containing them.

Names and Referring Strings

A referring string is a phrase which refers to some person, place, object, etc. Two elements are provided to mark such strings:

The @type attribute is used to distinguish amongst (for example) names of persons, places and organizations, where this is possible:

<q>My dear <rs type="person">Mr. Bennet</rs>, </q>
said his lady to him one day, <q>have you heard that <rs type="place">Netherfield Park</rs>
is let at last?</q>

It being one of the principles of the <rs type="organization">Circumlocution Office</rs> never, on any account whatsoever, to give a
straightforward answer, <rs type="person">Mr Barnacle</rs> said, <q>Possibly.</q>

As the following example shows, the <rs> element may be used for any reference to a person, place, etc, not necessarily one in the form of a proper noun or noun phrase.

<q>My dear <rs type="person">Mr. Bennet</rs>,</q>
said <rs type="person">his lady</rs> to him one day...

The <name> element by contrast is provided for the special case of referencing strings which consist only of proper nouns; it may be used synonymously with the <rs> element, or nested within it if a referring string contains a mixture of common and proper nouns.

Simply tagging something as a name is rarely enough to enable automatic processing of personal names into the canonical forms usually required for reference purposes. The name as it appears in the text may be inconsistently spelled, partial, or vague. Moreover, name prefixes such as van or de la, may or may not be included as part of the reference form of a name, depending on the language and country of origin of the bearer.

The @key attribute provides an alternative normalized identifier for the object being named, like a database record key. It may thus be useful as a means of gathering together all references to the same individual or location scattered throughout a document:

<q>My dear <rs type="person" key="BENM1">Mr.
Bennet</rs>, </q> said <rs type="person" key="BENM2">his lady</rs> to him one day, <q>have
you heard that <rs type="place" key="NETP1">Netherfield Park</rs> is let at
last?</q>

This use should be distinguished from the case of the <reg> (regularization) element, which provides a means of marking the standard form of a referencing string as demonstrated below:

<name type="person" key="WADLM1">
  <choice>
    <sic>Walter de la Mare</sic>
    <reg>de la Mare, Walter</reg>
  </choice>
  </name> was
  born at <name key="Ch1" type="place">Charlton</name>, in <name key="KT1" type="county">Kent</name>, in 1873.

The <index> element discussed in Index Generation may be more appropriate if the function of the regularization is to provide a consistent index:

<p>
  <name type="place">Montaillou</name> is not a
  large parish. At the time of the events which led to <name type="person">Fournier</name>'s
  <index>
    <term>Benedict XII, Pope of Avignon (Jacques Fournier)</term>
  </index>
  investigations, the local population consisted of between 200 and 250
inhabitants.</p>

Although adequate for many simple applications, these methods have two inconveniences: if the name occurs many times, then its regularised form must be repeated many times; and the burden of additional XML markup in the body of the text may be inconvenient to maintain and complex to process. For applications such as onomastics, relating to persons or places named rather than the name itself, or wherever a detailed analysis of the component parts of a name is needed, the full TEI Guidelines provide a range of other solutions.

Dates and Times

Tags for the more detailed encoding of times and dates include the following:

These elements have a number of attributes which can be used to provide normalised versions of their values. The @when attribute specifies a normalized form for the date or time, using one of the standard formats defined by ISO 8601. Partial dates or times (e.g. 1990, September 1990, twelvish) can be expressed by omitting a part of the value supplied, as in the following examples:

<date when="1980-02-21">21
Feb 1980</date>
<date when="1990">1990</date>
<date when="1990-09">September 1990</date>
<date when="--09">September</date>
<date when="2001-09-11T12:48:00">Sept 11th, 12 minutes before 9
am</date>

Note in the last example the use of a normalized representation for the date string which includes a time: this example could thus equally well be tagged using the <time> element.

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>

<l>specially when it's nine below zero</l>
<l>and <time when="15:00:00">three o'clock in the afternoon</time>
</l>

Numbers

Numbers can be written with either letters or digits (twenty-one, xxi, and 21) and their presentation is language-dependent (e.g. English 5th becomes Greek 5.; English 123,456.78 equals French 123.456,78). In natural-language processing or machine-translation applications, it is often helpful to distinguish them from other, more lexical parts of the text. In other applications, the ability to record a number's value in standard notation is important. The <num> element provides this possibility:

For example:

<num value="33">xxxiii</num>
<num type="cardinal" value="21">twenty-one</num>
<num type="percentage" value="10">ten percent</num>
<num type="percentage" value="10">10%</num>
<num type="ordinal" value="5">5th</num>

Lists

The element <list> is used to mark any kind of list. A list is a sequence of text items, which may be numbered, bulleted, or arranged as a glossary list. Each item may be preceded by an item label (in a glossary list, this label is the term being defined):

Individual list items are tagged with <item>. The first <item> may optionally be preceded by a <head>, which gives a heading for the list. The numbering of a list may be omitted, indicated using the @n attribute on each item, or (rarely) tagged as content using the <label> element. The following are all thus equivalent:

<list>
  <head>A short list</head>
  <item>First item in list.</item>
  <item>Second item in list.</item>
  <item>Third item in list.</item>
</list>
<list>
  <head>A short list</head>
  <item n="1">First item in list.</item>
  <item n="2">Second item in list.</item>
  <item n="3">Third item in list.</item>
</list>
<list>
  <head>A short list</head>
  <label>1</label>
  <item>First item in list.</item>
  <label>2</label>
  <item>Second item in list.</item>
  <label>3</label>
  <item>Third item in list.</item>
</list>

The styles should not be mixed in the same list.

A simple two-column table may be treated as a glossary list, tagged <list type="gloss">. Here, each item comprises a term and a gloss, marked with <label> and <item> respectively. These correspond to the elements <term> and <gloss>, which can occur anywhere in prose text.

<list type="gloss">
  <head>Vocabulary</head>
  <label xml:lang="enm">nu</label>
  <item>now</item>
  <label xml:lang="enm">lhude</label>
  <item>loudly</item>
  <label xml:lang="enm">bloweth</label>
  <item>blooms</item>
  <label xml:lang="enm">med</label>
  <item>meadow</item>
  <label xml:lang="enm">wude</label>
  <item>wood</item>
  <label xml:lang="enm">awe</label>
  <item>ewe</item>
  <label xml:lang="enm">lhouth</label>
  <item>lows</item>
  <label xml:lang="enm">sterteth</label>
  <item>bounds, frisks</item>
  <label xml:lang="enm">verteth</label>
  <item xml:lang="la">pedit</item>
  <label xml:lang="enm">murie</label>
  <item>merrily</item>
  <label xml:lang="enm">swik</label>
  <item>cease</item>
  <label xml:lang="enm">naver</label>
  <item>never</item>
</list>

Where the internal structure of a list item is more complex, it may be preferable to regard the list as a table, for which special-purpose tagging is defined below (Tables).

Lists of whatever kind can, of course, nest within list items to any depth required. Here, for example, a glossary list contains two items, each of which is itself a simple list:

<list type="gloss">
  <label>EVIL</label>
  <item>
    <list type="simple">
      <item>I am cast upon a horrible desolate island, void of all hope of recovery.</item>
      <item>I am singled out and separated as it were from all the world to be miserable.</item>
      <item>I am divided from mankind — a solitaire; one banished from human society.</item>
    </list>
  </item>
  <label>GOOD</label>
  <item>
    <list type="simple">
      <item>But I am alive; and not drowned, as all my ship's company were.</item>
      <item>But I am singled out, too, from all the ship's crew, to be spared from
      death...</item>
      <item>But I am not starved, and perishing on a barren place, affording no
      sustenances....</item>
    </list>
  </item>
</list>

A list need not necessarily be displayed in list format. For example,

  <p>On those remote pages it is written that animals
  are divided into <list rend="run-on">
  <item n="a">those that belong to the Emperor,</item>
  <item n="b"> embalmed ones, </item>
  <item n="c"> those that are trained, </item>
  <item n="d"> suckling pigs, </item>
  <item n="e"> mermaids, </item>
  <item n="f"> fabulous ones, </item>
  <item n="g"> stray dogs, </item>
  <item n="h"> those that are included in this classification, </item>
  <item n="i"> those that tremble as if they were mad, </item>
  <item n="j"> innumerable ones, </item>
  <item n="k"> those drawn with a very fine camel's-hair brush, </item>
  <item n="l"> others, </item>
  <item n="m"> those that have just broken a flower vase, </item>
  <item n="n"> those that resemble flies from a distance.</item>
</list>
  </p>

Lists of bibliographic items should be tagged using the <listBibl> element, described in the next section.

Bibliographic Citations

It is often useful to distinguish bibliographic citations where they occur within texts being transcribed for research, if only so that they will be properly formatted when the text is printed out. The element <bibl> is provided for this purpose. Where the components of a bibliographic reference are to be distinguished, the following elements may be used as appropriate. It is generally useful to mark at least those parts (such as the titles of articles, books, and journals) which will need special formatting. The other elements are provided for cases where particular interest attaches to such details.

For example, the following editorial note might be transcribed as shown: He was a member of Parliament for Warwickshire in 1445, and died March 14, 1470 (according to Kittredge, Harvard Studies 5. 88ff).

He was a member of Parliament for Warwickshire
in 1445, and died March 14, 1470 (according to <bibl>
<author>Kittredge</author>,
<title>Harvard Studies</title>
<biblScope>5. 88ff</biblScope>
</bibl>).

For lists of bibliographic citations, the <listBibl> element should be used; it may contain a series of <bibl> elements.

Tables

Tables represent a challenge for any text processing system, but simple tables, at least, appear in so many texts that even in the simplified TEI tag set presented here, markup for tables is necessary. The following elements are provided for this purpose:

For example, Defoe uses mortality tables like the following in the Journal of the Plague Year to show the rise and ebb of the epidemic:

  <p>It was indeed coming on amain, for the burials
  that same week were in the next adjoining parishes thus:— <table rows="5" cols="4">
  <row role="data">
    <cell role="label">St. Leonard's, Shoreditch</cell>
    <cell>64</cell>
    <cell>84</cell>
    <cell>119</cell>
  </row>
  <row role="data">
    <cell role="label">St. Botolph's, Bishopsgate</cell>
    <cell>65</cell>
    <cell>105</cell>
    <cell>116</cell>
  </row>
  <row role="data">
    <cell role="label">St. Giles's, Cripplegate</cell>
    <cell>213</cell>
    <cell>421</cell>
    <cell>554</cell>
  </row>
</table>
  </p>
  <p>This shutting up of houses was at first counted a very cruel and unchristian
  method, and the poor people so confined made bitter lamentations. ... </p>

Figures and Graphics

Not all the components of a document are necessarily textual. The most straightforward text will often contain diagrams or illustrations, to say nothing of documents in which image and text are inextricably intertwined, or electronic resources in which the two are complementary.

The encoder may simply record the presence of a graphic within the text, possibly with a brief description of its content, and may also provide a link to a digitized version of the graphic, using the following elements:

Any textual information accompanying the graphic, such as a heading and/or caption, may be included within the <figure> element itself, in a <head> and one or more <p> elements, as also may any text appearing within the graphic itself. It is strongly recommended that a prose description of the image be supplied, as the content of a <figDesc> element, for the use of applications which are not able to render the graphic, and to render the document accessible to vision-impaired readers. (Such text is not normally considered part of the document proper.)

The simplest use for these elements is to mark the position of a graphic and provide a link to it, as in this example;

<pb n="412"/>
<figure>
  <graphic url="p412fig.png"/>
</figure>
<pb n="413"/>

This indicates that the graphic contained by the file p412fig.png appears between pages 412 and 413.

The <graphic> element can appear anywhere that textual content is permitted, within but not between paragraphs or headings. In the following example, the encoder has decided to treat a specific printer's ornament as a heading:

<head>
  <graphic url="http://www.iath.virginia.edu/gants/Ornaments/Heads/hp-ral02.gif"/>
</head>

More usually, a graphic will have at the least an identifying title, which may be encoded using the <head> element, or a number of figures may be grouped together in a particular structure. It is also often convenient to include a brief description of the image. The <figure> element provides a means of wrapping one or more such elements together as a kind of graphic block:

<figure>
  <graphic url="fessipic.png"/>
  <head>Mr Fezziwig's Ball</head>
  <figDesc>A Cruikshank
  engraving showing Mr Fezziwig leading a group of revellers.</figDesc>
</figure>

These cases should be carefully distinguished from the case where an encoded text is complemented by a collection of digital images, maintained as a distinct resource. The @facs attribute may be used to associate any element in an encoded text with a digital facsimile of it. In the simple case where only page images are available, the @facs attribute on the <pb> element may be used to associate each image with an appropriate point in the text:

<text>
  <pb facs="page1.png" n="1"/>

  <pb facs="page2.png" n="2"/>

</text>

This method is only appropriate in the simple case where each digital image file page1.png etc. corresponds with a single transcribed and encoded page. If more detailed alignment of image and transcription is required, for example because the image files actually represent double page spreads, more sophisticated mechanisms are provided in the full TEI Guidelines.

Interpretation and Analysis

It is often said that all markup is a form of interpretation or analysis. While it is certainly difficult, and may be impossible, to distinguish firmly between objective and subjective information in any universal way, it remains true that judgments concerning the latter are typically regarded as more likely to provide controversy than those concerning the former. Many scholars therefore prefer to record such interpretations only if it is possible to alert the reader that they are considered more open to dispute, than the rest of the markup. This section describes some of the elements provided by the TEI scheme to meet this need.

Orthographic Sentences

Interpretation typically ranges across the whole of a text, with no particular respect to other structural units. A useful preliminary to intensive interpretation is therefore to segment the text into discrete and identifiable units, each of which can then bear a label for use as a sort of canonical reference. To facilitate such uses, these units may not cross each other, nor nest within each other. They may conveniently be represented using the following element:

As the name suggests, the <s> element is most commonly used (in linguistic applications at least) for marking orthographic sentences, that is, units defined by orthographic features such as punctuation. For example, the passage from Jane Eyre discussed earlier might be divided into s-units as follows:

<pb n="474"/>
<div type="chapter" n="38">
  <p>
    <s n="001">Reader, I married him.</s>
    <s n="002">A quiet wedding we had:</s>
    <s n="003">he
    and I, the parson and clerk, were alone present.</s>
    <s n="004">When we got back from
    church, I went into the kitchen of the manor-house, where Mary was cooking the dinner, and
    John cleaning the knives, and I said —</s>
  </p>
  <p>
    <q>
      <s n="005">Mary, I have been married to Mr Rochester this morning.</s>
  </q> ... </p>
</div>

Note that <s> elements cannot nest: the beginning of one <s> element implies that the previous one has finished. When s-units are tagged as shown above, it is advisable to tag the entire text end-to-end, so that every word in the text being analysed will be contained by exactly one <s> element, whose identifier can then be used to specify a unique reference for it. If the identifiers used are unique within the document, then the @xml:id attribute might be used in preference to the @n used in the above example.

Words and punctuation

Tokenization, that is, the identification of lexical or non-lexical tokens within a text, is a very common requirement for all kinds of textual analysis, and not an entirely trivial one. The decision as to whether, for example, can't in English or du in French should be treated as one word or two is not simple. Consequently it is often useful to make explicit the preferred tokenization in a marked up text. The following elements are available for this purpose:

For example, the output from a part of speech tagger might be recorded in TEI Lite as follows:

<s n="1">
  <w ana="#NP0">Marley</w>
  <w ana="#VBD">was</w>
  <w ana="#AJ0">dead</w>
  <pc>:</pc>
  <w ana="#TO0">to</w>
  <w ana="#VBB">begin</w>
  <w ana="#PRP">with</w>
  <pc>. </pc>
</s>

In this example, each word has been decorated with an automatically generated part of speech code, using the @ana attribute discussed in section Special kinds of Linking above. The <w> also provides for each word to be associated with a root form or lemma, either explicitly using the @lemma attribute, or by reference, using the @lemmaRef attribute, as in this example: ...<w ana="#VBD" lemma="be" lemmaRef="http://www.myLexicon.com/be">was</w> ...

General-Purpose Interpretation Elements

The <w> element is a specialisation of the <seg> element which has already been introduced for use in identifying otherwise unmarked targets of cross references and hypertext links (see section Cross References and Links); it identifies some phrase-level portion of text to which the encoder may assign a user-specified @type, as well as a unique identifier; it may thus be used to tag textual features for which there is no other provision in the published TEI Guidelines.

For example, the Guidelines provide no apostrophe element to mark parts of a literary text in which the narrator addresses the reader (or hearer) directly. One approach might be to regard these as instances of the <q> element, distinguished from others by an appropriate value for the @who attribute. A possibly simpler, and certainly more general, solution would however be to use the <seg> element as follows:

<div type="chapter" n="38">
  <p>
  <seg type="apostrophe">Reader, I married him.</seg> A quiet wedding we had: ...</p>
</div>

The @type attribute on the <seg> element can take any value, and so can be used to record phrase-level phenomena of any kind; it is good practice to record the values used and their significance in the header.

A <seg> element of one type (unlike the <s> element which it superficially resembles) can be nested within a <seg> element of the same or another type. This enables quite complex structures to be represented; some examples were given in section Special kinds of Linking above. However, because it must respect the requirement that elements be properly nested and may not cut across each other, it cannot cope with the common requirement to associate an interpretation with arbitrary segments of a text which may completely ignore the document hierarchy. It also requires that the interpretation itself be represented by a single coded value in the @type attribute.

Neither restriction applies to the <interp> element, which provides powerful features for the encoding of quite complex interpretive information in a relatively straightforward manner. These elements allow the encoder to specify both the class of an interpretation, and the particular instance of that class which the interpretation involves. Thus, whereas with <seg> one can say simply that something is an apostrophe, with <interp> one can say that it is an instance (apostrophe) of a larger class (rhetorical figures).

Moreover, <interp> is a stand off element: it does not surround the segments of text which it describes, but instead is linked to the passage in question either by means of the @ana attribute discussed in section Special kinds of Linking above, or by means of its own @inst attribute. This means that any kind of analysis can be represented, independently of the document hierarchy, as well as facilitating the grouping of analyses of a particular type together. A special purpose <interpGrp> element is provided for the latter purpose.

For example, suppose that you wish to mark such diverse aspects of a text as themes or subject matter, rhetorical figures, and the locations of individual scenes of the narrative. Different portions of our sample passage from Jane Eyre for example, might be associated with the rhetorical figures of apostrophe, hyperbole, and metaphor; with subject-matter references to churches, servants, cooking, postal service, and honeymoons; and with scenes located in the church, in the kitchen, and in an unspecified location (drawing room?).

These interpretations could be placed anywhere within the <text> element; it is however good practice to put them all in the same place (e.g. a separate section of the front or back matter), as in the following example:

<back>
  <div type="Interpretations">
    <p>
      <interp xml:id="fig-apos-1" resp="#LB-MSM" type="figureOfSpeech">apostrophe</interp>
      <interp xml:id="fig-hyp-1" resp="#LB-MSM" type="figureOfSpeech">hyperbole</interp>
      <interp xml:id="set-church-1" resp="#LB-MSM" type="setting">church</interp>
      <interp xml:id="ref-church-1" resp="#LB-MSM" type="reference">church</interp>
      <interp xml:id="ref-serv-1" resp="#LB-MSM" type="reference">servants</interp>
    </p>
  </div>
</back>

The evident redundancy of this encoding can be considerably reduced by using the <interpGrp> element to group together all those <interp> elements which share common attribute values, as follows:

<back>
  <div type="Interpretations">
    <p>
      <interpGrp type="figureOfSpeech" resp="#LB-MSM">
        <interp xml:id="fig-apos">apostrophe</interp>
        <interp xml:id="fig-hyp">hyperbole</interp>
        <interp xml:id="fig-meta">metaphor</interp>
      </interpGrp>
      <interpGrp type="scene-setting" resp="#LB-MSM">
        <interp xml:id="set-church">church</interp>
        <interp xml:id="set-kitch">kitchen</interp>
        <interp xml:id="set-unspec">unspecified</interp>
      </interpGrp>
      <interpGrp type="reference" resp="#LB-MSM">
        <interp xml:id="ref-church">church</interp>
        <interp xml:id="ref-serv">servants</interp>
        <interp xml:id="ref-cook">cooking</interp>
      </interpGrp>
    </p>
  </div>
</back>

Once these interpretation elements have been defined, they can be linked with the parts of the text to which they apply in either or both of two ways. The @ana attribute can be used on whichever element is appropriate:

<div type="chapter" n="38">
  <p xml:id="P38.1" ana="#set-church #set-kitch">
    <s xml:id="P38.1.1" ana="#fig-apos">Reader, I
    married him.</s>
  </p>
</div>

Note in this example that since the paragraph has two settings (in the church and in the kitchen), the identifiers of both have been supplied.

Alternatively, the <interp> elements can point to all the parts of the text to which they apply, using their @inst attribute:

<interp xml:id="fig-apos-2" type="figureOfSpeech" resp="#LB-MSM" inst="#P38.1.1">apostrophe</interp>
<interp xml:id="set-church-2" type="scene-setting" inst="#P38.1" resp="#LB-MSM">church</interp>
<interp xml:id="set-kitchen-2" type="scene-setting" inst="#P38.1" resp="#LB-MSM">kitchen</interp>

The <interp> element is not limited to any particular type of analysis. The literary analysis shown above is but one possibility; one could equally well use <interp> to capture a linguistic part-of-speech analysis. For example, the example sentence given in section Special kinds of Linking assumes a linguistic analysis which might be represented as follows:

<interp xml:id="NP1" type="pos">noun
phrase, singular</interp>
<interp xml:id="VV1" type="pos">inflected verb, present-tense
singular</interp> ...

Technical Documentation

Although the focus of this document is on the use of the TEI scheme for the encoding of existing pre-electronic documents, the same scheme may also be used for the encoding of new documents. In the preparation of new documents (such as this one), XML has much to recommend it: the document's structure can be clearly represented, and the same electronic text can be re-used for many purposes — to provide both online hypertext or browsable versions and well-formatted typeset versions from a common source for example.

To facilitate this, the TEI Lite schema includes some elements for marking features of technical documents in general, and of XML-related documents in particular.

Additional Elements for Technical Documents

The following elements may be used to mark particular features of technical documents:

The following example shows how these elements might be used to encode a passage from a tutorial introducing the Fortran programming language:

  <p>It is traditional to introduce a language with a
  program like the following: <eg xml:space="preserve"> CHAR*12 GRTG
  GRTG = 'HELLO WORLD'
  PRINT *, GRTG
  END
</eg>
  </p>
  <p>This simple example first declares a variable <ident>GRTG</ident>, in the line
  <code>CHAR*12 GRTG</code>, which identifies <ident>GRTG</ident> as consisting of 12 bytes
  of type <ident>CHAR</ident>. To this variable, the value <val>HELLO WORLD</val> is then
  assigned.</p>

A formatting application, given a text like that above, can be instructed to format examples appropriately (e.g. to preserve line breaks, or to use a distinctive font). Similarly, the use of tags such as <ident> greatly facilitates the construction of a useful index.

The <formula> element should be used to enclose a mathematical or chemical formula presented within the text as a distinct item. Since formulae generally include a large variety of special typographic features not otherwise present in ordinary text, it will usually be necessary to present the body of the formula in a specialized notation. The notation used should be specified by the @notation attribute, as in the following example:

<formula notation="tex"> \begin{math}E =
mc^{2}\end{math} </formula>

A particular problem arises when XML encoding is the subject of discussion within a technical document, itself encoded in XML. In such a document, it is clearly essential to distinguish clearly the markup occurring within examples from that marking up the document itself, and end-tags are highly likely to occur. One simple solution is to use the predefined entity reference &lt; to represent each < character which marks the start of an XML tag within the examples. A more general solution is to mark off the whole body of each example as containing data which is not to be scanned for XML mark-up by the parser. This is achieved by enclosing it within a special XML construct called a CDATA marked section, as in the following example:

<p>A list should be encoded as
follows: <eg><![ CDATA [ <list> <item>First item in the
list</item> <item>Second item</item> </list> ]]> </eg> The
<gi>list</gi> element consists of a series of <gi>item</gi>
elements.

The <list> element used within the example above will not be regarded as forming part of the document proper, because it is embedded within a marked section (beginning with the special markup declaration "<![CDATA[", and ending with "]]>").

Note also the use of the <gi> element to tag references to element names (or generic identifiers) within the body of the text.

Generated Divisions

Most modern document production systems have the ability to generate automatically whole sections such as a table of contents or an index. The TEI Lite scheme provides an element to mark the location at which such a generated section should be placed.

The <divGen> element can be placed anywhere that a division element would be legal, as in the following example:

<front>
  <titlePage/>
  <divGen type="toc"/>
  <div>
    <head>Preface</head>

  </div>
</front>
<body/>
<back>
  <div>
    <head>Appendix</head>

  </div>
  <divGen type="index" n="Index"/>
</back>

This example also demonstrates the use of the @type attribute to distinguish the different kinds of division to be generated: in the first case a table of contents (a toc) and in the second an index.

When an existing index or table of contents is to be encoded (rather than one being generated) for some reason, the <list> element discussed in section Lists should be used.

Index Generation

While production of a table of contents from a properly tagged document is generally unproblematic for an automatic processor, the production of a good quality index will often require more careful tagging. It may not be enough simply to produce a list of all parts tagged in some particular way, although extracting (for example) all occurrences of elements such as <term> or <name> will often be a good departure point for an index.

The TEI schema provides a special purpose <index> tag which may be used to mark both the parts of the document which should be indexed, and how the indexing should be done.

For example, the second paragraph of this section might include the following:

... TEI lite also provides a special purpose
  <gi>index</gi> tag <index>
  <term>indexing</term>
</index>
<index>
  <term>index (tag)</term>
  <index>
    <term>use in index generation</term>
  </index>
</index>
which may be used ...

The <index> element can also be used to provide a form of interpretive or analytic information. For example, in a study of Ovid, it might be desired to record all the poet's references to different figures, for comparative stylistic study. In the following lines of the Metamorphoses, such a study would record the poet's references to Jupiter (as deus, se, and as the subject of confiteor [in inflectional form number 227]), to Jupiter-in-the-guise-of-a-bull (as imago tauri fallacis and the subject of teneo), and so on.[^4]

<l n="3.001">iamque deus posita fallacis
imagine tauri</l>
<l n="3.002">se confessus erat Dictaeaque rura tenebat</l>

This need might be met using the <note> element discussed in section in Notes, or with the <interp> element discussed in section Interpretation and Analysis. Here we demonstrate how it might also be satisfied by using the <index> element.

[^4: The analysis is taken, with permission, from Willard McCarty and Burton Wright, An Analytical Onomasticon to the Metamorphoses of Ovid (Princeton: Princeton University Press, forthcoming). Some simplifications have been undertaken.]

We assume that the object is to generate more than one index: one for names of deities (called @dn), another for onomastic references (called @on), a third for pronominal references (called @pr) and so forth. One way of achieving this might be as follows:

  <l n="3.001">iamque deus posita
  fallacis imagine tauri <index indexName="dn">
  <term>Iuppiter</term>
  <index>
    <term>deus</term>
  </index>
</index>
<index indexName="on">
  <term>Iuppiter (taurus)</term>
  <index>
    <term>imago tauri
    fallacis</term>
  </index>
</index>
  </l>
  <l n="3.002">se confessus erat Dictaeaque rura tenebat
  <index indexName="pr">
    <term>Iuppiter</term>
    <index>
      <term>se</term>
    </index>
  </index>
  <index indexName="v">
    <term>Iuppiter</term>
    <index>
      <term>confiteor
      (v227)</term>
    </index>
  </index>
  </l>

For each <index> element above, an entry will be generated in the appropriate index, using as headword the content of the <term> element it contains; the <term> elements nested within the secondary <index> element in each case provide a secondary keyword. The actual reference will be taken from the context in which the <index> element appears, i.e. in this case the identifier of the <l> element containing it.

Addresses

The <address> element is used to mark a postal address of any kind. It contains one or more <addrLine> elements, one for each line of the address.

Here is a simple example:

<address>
  <addrLine>Computer Center (M/C 135)</addrLine>
  <addrLine>1940 W. Taylor, Room 124</addrLine>
  <addrLine>Chicago, IL 60612-7352</addrLine>
  <addrLine>U.S.A.</addrLine>
</address>

The individual parts of an address may be further distinguished by using the <name> element discussed above (section Names and Referring Strings).

<address>
  <addrLine>Computer Center (M/C 135)</addrLine>
  <addrLine>1940 W. Taylor, Room 124</addrLine>
  <addrLine>
  <name type="city">Chicago</name>, IL 60612-7352</addrLine>
  <addrLine>
    <name type="country">USA</name>
  </addrLine>
</address>

Character Sets, Diacritics, etc.

With the advent of XML and its adoption of Unicode as the required character set for all documents, most problems previously associated with the representation of the divers languages and writing systems of the world are greatly reduced. For those working with standard forms of the European languages in particular, almost no special action is needed: any XML editor should enable you to input accented letters or other non-ASCII characters directly, and they should be stored in the resulting file in a way which is transferable directly between different systems.

There are two important exceptions: the characters & and < may not be entered directly in an XML document, since they have a special significance as initiating markup. They must always be represented as entity references, like this: &amp; or &lt;. Other characters may also be represented by means of entity reference where necessary, for example to retain compatibility with a pre-Unicode processing system.

Front and Back Matter

Front Matter

For many purposes, particularly in older texts, the preliminary material such as title pages, prefatory epistles, etc., may provide very useful additional linguistic or social information. P5 provides a set of recommendations for distinguishing the textual elements most commonly encountered in front matter, which are summarized here.

Title Page

The start of a title page should be marked with the element <titlePage>. All text contained on the page should be transcribed and tagged with the appropriate element from the following list:

Typeface distinctions should be marked with the @rend attribute when necessary, as described above. Very detailed description of the letter spacing and sizing used in ornamental titles is not as yet provided for by the Guidelines. Changes of language should be marked by appropriate use of the @xml:lang attribute or the <foreign> element, as necessary. Names of people, places, or organizations, may be tagged using the <name> element wherever they appear if no other more specific element is available.

Two example title pages follow:

<titlePage rend="Roman">
  <docTitle>
    <titlePart type="main"> PARADISE REGAIN'D. A POEM In IV <hi>BOOKS</hi>. </titlePart>
    <titlePart> To which is added <title>SAMSON AGONISTES</title>. </titlePart>
  </docTitle>
  <byline>The Author <docAuthor>JOHN MILTON</docAuthor>
  </byline>
  <docImprint>
    <name>LONDON</name>, Printed by <name>J.M.</name> for <name>John Starkey</name>
    at the <name>Mitre</name> in <name>Fleetstreet</name>, near
    <name>Temple-Bar.</name>
  </docImprint>
  <docDate>MDCLXXI</docDate>
</titlePage>

<titlePage>
  <docTitle>
    <titlePart type="main"> Lives of the Queens of England, from the Norman
    Conquest;</titlePart>
    <titlePart type="sub">with anecdotes of their courts. </titlePart>
  </docTitle>
  <titlePart>Now first published from Official Records and other authentic documents private
  as well as public.</titlePart>
  <docEdition>New edition, with corrections and additions</docEdition>
  <byline>By <docAuthor>Agnes Strickland</docAuthor>
  </byline>
  <epigraph>
    <q>The treasures of antiquity laid up in old historic rolls, I opened.</q>
    <bibl>BEAUMONT</bibl>
  </epigraph>
  <docImprint>Philadelphia: Blanchard and Lea</docImprint>
  <docDate>1860.</docDate>
</titlePage>

As elsewhere, the @ref attribute may be used to link a name with a canonical definition of the entity being named. For example:

  <byline>By <docAuthor>
  <name ref="http://en.wikipedia.org/wiki/Agnes_Strickland">Agnes
  Strickland</name>
</docAuthor>
  </byline>

Prefatory Matter

Major blocks of text within the front matter should be marked using <div> elements; the following suggested values for the @type attribute may be used to distinguish various common types of prefatory matter:

preface
- A foreword or preface addressed to the reader in which the author or publisher explains the content, purpose, or origin of the text
dedication
- A formal offering or dedication of a text to one or more persons or institutions by the author.
abstract
- A summary of the content of a text as continuous prose
ack
- A formal declaration of acknowledgment by the author in which persons and institutions are thanked for their part in the creation of a text
contents
- A table of contents, specifying the structure of a work and listing its constituents. The <list> element should be used to mark its structure.
frontispiece
- A pictorial frontispiece, possibly including some text.

Where other kinds of prefatory matter are encountered, the encoder is at liberty to invent other values for the @type attribute.

Like any text division, those in front matter may contain low level structural or non-structural elements as described elsewhere. They will generally begin with a heading or title of some kind which should be tagged using the <head> element. Epistles will contain the following additional elements:

Epistles which appear elsewhere in a text will, of course, contain these same elements.

As an example, the dedication at the start of Milton's Comus should be marked up as follows:

<div type="dedication">
  <head>To the Right Honourable <name>JOHN Lord Viscount BRACLY</name>, Son and Heir apparent
  to the Earl of Bridgewater, &amp;c.</head>
  <salute>MY LORD,</salute>
  <p>THis <hi>Poem</hi>, which receiv'd its first occasion of Birth from your Self, and
  others of your Noble Family .... and as in this representation your attendant
  <name>Thyrsis</name>, so now in all reall expression</p>
  <closer>
    <salute>Your faithfull, and most humble servant</salute>
    <signed>
      <name>H. LAWES.</name>
    </signed>
  </closer>
</div>

Back Matter

Structural Divisions of Back Matter

Because of variations in publishing practice, back matter can contain virtually any of the elements listed above for front matter, and the same elements should be used where this is so. Additionally, back matter may contain the following types of matter within the <back> element. Like the structural divisions of the body, these should be marked as <div> elements, and distinguished by the following suggested values of the @type attribute:

appendix
- An ancillary self-contained section of a work, often providing additional but in some sense extra-canonical text.
glossary
- A list of terms associated with definition texts (‘glosses’): this should be encoded as a <list type="gloss"> element
notes
- A section in which textual or other kinds of notes are gathered together.
bibliogr
- A list of bibliographic citations: this should be encoded as a <listBibl>
index
- Any form of pre-existing index to the work (An index may also be generated for a document by using the <index> element described above).
colophon
- A statement appearing at the end of a book describing the conditions of its physical production.

The Electronic Title Page

Every TEI text has a header which provides information analogous to that provided by the title page of printed text. The header is introduced by the element <teiHeader> and has four major parts:

A corpus or collection of texts with many shared characteristics may have one header for the corpus and individual headers for each component of the corpus. In this case the @type attribute indicates the type of header.
<teiHeader
        type="corpus">
introduces the header for corpus-level information.

Some of the header elements contain running prose which consists of one or more <p>s. Others are grouped:

- Elements whose names end in Stmt (for statement) usually enclose a group of elements recording some structured information.
- Elements whose names end in Decl (for declaration) enclose information about specific encoding practices.
- Elements whose names end in Desc (for description) contain a prose description.

The File Description

The <fileDesc> element is mandatory. It contains a full bibliographic description of the file with the following elements:

A minimal header has the following structure:

<teiHeader>
  <fileDesc>
    <titleStmt/>
    <publicationStmt/>
    <sourceDesc/>
  </fileDesc>
</teiHeader>

The Title Statement

The following elements can be used in the <titleStmt>:

The title of a digital resource derived from a non-digital one will obviously be similar. However, it is important to distinguish the title of the computer file from that of the source text, for example:

[title of source]: a machine readable transcription [title of
source]: electronic edition A machine readable version of: [title of source]

The <respStmt> element contains the following subcomponents: Example:

<titleStmt>
  <title>Two stories by Edgar Allen Poe: a machine readable transcription</title>
  <author>Poe, Edgar Allen (1809-1849)</author>
  <respStmt>
    <resp>compiled by</resp>
    <name>James D. Benson</name>
  </respStmt>
</titleStmt>

The Edition Statement

The <editionStmt> groups information relating to one edition of the digital resource (where edition is used as elsewhere in bibliography), and may include the following elements:

Example:

<editionStmt>
  <edition n="U2">Third
  draft, substantially revised <date>1987</date>
  </edition>
</editionStmt>

Determining exactly what constitutes a new edition of an electronic text is left to the encoder.

The Extent Statement

The <extent> statement describes the approximate size of the digital resource.

Example:

<extent>4532
bytes</extent>

The Publication Statement

The <publicationStmt> is mandatory. It may contain a simple prose description or groups of the elements described below:

At least one of these three elements must be present, unless the entire publication statement is in prose. The following elements may occur within them:

Example:

<publicationStmt>
  <publisher>University of Victoria Humanities Computing and Media Centre</publisher>
  <pubPlace>Victoria, BC</pubPlace>
  <date>2011</date>
  <availability status="restricted">
    <licence target="http://creativecommons.org/licenses/by-sa/3.0/"> Distributed under a
    Creative Commons Attribution-ShareAlike 3.0 Unported License </licence>
  </availability>
</publicationStmt>

Series and Notes Statements

The <seriesStmt> element groups information about the series, if any, to which a publication belongs. It may contain <title>, <idno>, or <respStmt> elements.

The <notesStmt>, if used, contains one or more <note> elements which contain a note or annotation. Some information found in the notes area in conventional bibliography has been assigned specific elements in the TEI scheme.

The Source Description

The <sourceDesc> is a mandatory element which records details of the source or sources from which the computer file is derived. It may contain simple prose or a bibliographic citation, using one or more of the following elements:

Examples:

<sourceDesc>
  <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
  1968)</bibl>
</sourceDesc>

<sourceDesc>
  <bibl>
    <author>CNN Network News</author>
    <title>News headlines</title>
    <date>12 Jun
    1989</date>
  </bibl>
</sourceDesc>

The Encoding Description

The <encodingDesc> element specifies the methods and editorial principles which governed the transcription of the text. Its use is highly recommended. It may be prose description or may contain elements from the following list:

Project and Sampling Descriptions

Examples of <projectDesc> and <samplingDesc>:

<encodingDesc>
  <projectDesc>
    <p>Texts collected for
    use in the Claremont Shakespeare Clinic, June 1990.
    </p>
  </projectDesc>
</encodingDesc>

<encodingDesc>
  <samplingDecl>
    <p>Samples of
    2000 words taken from the beginning of the text</p>
  </samplingDecl>
</encodingDesc>

Editorial Declarations

The <editorialDecl> contains a prose description of the practices used when encoding the text. Typically this description should cover such topics as the following, each of which may conveniently be given as a separate paragraph.

correction
- how and under what circumstances corrections have been made in the text.
normalization
- the extent to which the original source has been regularized or normalized.
quotation
- what has been done with quotation marks in the original -- have they been retained or replaced by entity references, are opening and closing quotes distinguished, etc.
hyphenation
- what has been done with hyphens (especially end-of-line hyphens) in the original -- have they been retained, replaced by entity references, etc.
segmentation
- how has the text has been segmented, for example into sentences, tone-units, graphemic strata, etc.
interpretation
- what analytic or interpretive information has been added to the text.

Example:

<editorialDecl>
  <p>The part of
  speech analysis applied throughout section 4 was added by hand and has not been
  checked.</p>
  <p>Errors in transcription controlled by using the WordPerfect spelling
  checker.</p>
  <p>All words converted to Modern American spelling using Webster's 9th
  Collegiate dictionary.</p>
</editorialDecl>

Reference and Classification Declarations

The <refsDecl> element is used to document the way in which any standard referencing scheme built into the encoding works. In its simplest form, it consists of prose description.

Example:

<refsDecl>
  <p>The <att>n</att>
  attribute on each <gi>div</gi> contains the canonical reference for each division in the
  form XX.yyy where XX is the book number in roman numeral and yyy is the section number in
  arabic.</p>
  <p>Milestone tags refer to the edition of 1830 as E30 and that of 1850 as E50.
  </p>
</refsDecl>

The <classDecl> element groups together definitions or sources for any descriptive classification schemes used by other parts of the header. At least one such scheme must be provided, encoded using the following elements:

In the simplest case, the taxonomy may be defined by a bibliographic reference, as in the following example:

<classDecl>
  <taxonomy xml:id="LC-SH">
    <bibl>Library of Congress Subject Headings
    </bibl>
  </taxonomy>
</classDecl>

Alternatively, or in addition, the encoder may define a special purpose classification scheme, as in the following example:

<taxonomy xml:id="B">
  <bibl>Brown Corpus</bibl>
  <category xml:id="B.A">
    <catDesc>Press
    Reportage</catDesc>
    <category xml:id="B.A1">
      <catDesc>Daily</catDesc>
    </category>
    <category xml:id="B.A2">
      <catDesc>Sunday</catDesc>
    </category>
    <category xml:id="B.A3">
      <catDesc>National</catDesc>
    </category>
    <category xml:id="B.A4">
      <catDesc>Provincial</catDesc>
    </category>
    <category xml:id="B.A5">
      <catDesc>Political</catDesc>
    </category>
    <category xml:id="B.A6">
      <catDesc>Sports</catDesc>
    </category>
  </category>
  <category xml:id="B.D">
    <catDesc>Religion</catDesc>
    <category xml:id="B.D1">
      <catDesc>Books</catDesc>
    </category>
    <category xml:id="B.D2">
      <catDesc>Periodicals and
      tracts</catDesc>
    </category>
  </category>
</taxonomy>

Linkage between a particular text and a category within such a taxonomy is made by means of the <catRef> element within the <textClass> element, as described in the next section below.

The Profile Description

The <profileDesc> element enables information characterizing various descriptive aspects of a text to be recorded within a single framework. It has three optional components:

The <creation> element is useful for documenting where a work was created, even though it may not have been published or recorded there.

Example:

<creation>
  <date when="1992-08">August 1992</date>
  <name type="place">Taos, New Mexico</name>
</creation>

The <langUsage> element is useful where a text contains many different languages. It may contain <language> elements to document each particular language used: For example, a text containing predominantly text in French as spoken in Quebec, but also smaller amounts of British and Canadian English might be documented as follows:

<langUsage>
  <language ident="fr-CA" usage="60">Québecois</language>
  <language ident="en-CA" usage="20">Canadian business English</language>
  <language ident="en-GB" usage="20">British English</language>
</langUsage>

The <textClass> element classifies a text. This may be done with reference to a classification system locally defined by means of the <classDecl> element, or by reference to some externally defined established scheme such as the Universal Decimal Classification. Texts may also be classified using lists of keywords, which may themselves be drawn from locally or externally defined control lists. The following elements are used to supply such classifications:

The simplest way of classifying a text is by means of the <classCode> element. For example, a text with classification 410 in the Universal Decimal Classification might be documented as follows: <classCode scheme="http://www.udc.org">410</classCode>

When a classification scheme has been locally defined using the <taxonomy> element discussed in the preceding subsection, the <catRef> element should be used to reference it. To continue the earlier example, a work classified in the Brown Corpus as
Press
          reportage - Sunday
and also as Religion might be documented as follows: <catRef target="#B.A3 #B.D"/>

The element <keywords> contains a list of keywords or phrases identifying the topic or nature of a text. As usual, the attribute @scheme identifies the source from which these terms are taken. For example, if the LC Subject Headings are used, following declaration of that classification system in a <taxonomy> element as above :

<textClass>
  <keywords scheme="#LCSH">
    <list>
      <item>English literature -- History and criticism -- Data processing.</item>
      <item>English literature -- History and criticism -- Theory etc.</item>
      <item>English language -- Style -- Data processing.</item>
    </list>
  </keywords>
</textClass>

Multiple classifications may be supplied using any of the mechanisms described in this section.

The Revision Description

The <revisionDesc> element provides a change log in which each change made to a text may be recorded. The log may be recorded as a sequence of <change> elements each of which contains a brief description of the change. The attributes @when and @who may be used to identify when the change was carried out and the agency responsible for it.

Example:

<revisionDesc>
  <change when="1991-03-06" who="#EMB">File format updated</change>
  <change when="1990-05-25" who="#EMB">Stuart's corrections entered</change>
</revisionDesc>

In a production environment it will usually be found preferable to use some kind of automated system to track and record changes. Many such version control systems, as they are known, can also be configured to update the TEI Header of a file automatically.

List of Elements Described

The TEI Lite schema is a pure subset of TEI P5. In the following list of elements and classes used, some information, notably the examples, derives from the canonical definition for the element in TEI P5 and may therefore refer to elements or attributes not provided by TEI Lite. Note however that only the elements listed here are available within the TEI Lite schema. These specifications also refer to many attributes which although available in TEI Lite are not discussed in this tutorial for lack of space.

<TEI>
@version

att.global
@xml:base

att.global.rendition
@style
@rendition

att.global.linking
@synch
@sameAs
@copyOf
@exclude
@select

att.datable.w3c
@notBefore
@notAfter
@from
@to

att.datable
@calendar

att.internetMedia

model.msItemPart

model.msQuoteLike

model.personPart

<editorialDecl>

<editorialDecl>
  <p>All words converted to Modern American spelling using
  Websters 9th Collegiate dictionary</p>
  <p>All opening quotation marks converted to “ all closing
  quotation marks converted to &amp;cdq;.</p>
</editorialDecl>

<editorialDecl>
  <p>Certains mots coupés par accident typographique en fin de ligne ont été réassemblés
  sans commentaire.</p>
  <p>Les "guillements français" ont été remplacée par des "guillemets droits" (sans
  symétrie)</p>
</editorialDecl>

<editorialDecl>
  <p> 所有字皆轉換為源自Websters 9th Collegiate字典的現代美語拼法</p>
  <p>所有的前括號都改成" 後括號都改成 "</p>
</editorialDecl>

<cit>

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

<cit>
  <q>Regarde de tous tes yeux, regarde</q>
  <bibl>Jules Verne, Michel Strogof</bibl>
</cit>