TEI Lite: Encoding for Interchange: an introduction to the TEI Revised for TEI P5 release
Lou Burnard
C. M. Sperberg-McQueen
February 2006

Prefatory note

TEI Lite was the name adopted for what the TEI editors originally conceived of as a simple demonstration of how the TEI 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 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 in our own experience. 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’, many of whom produced their own documentation and tutorial materials (some examples are listed in the TEI Tutorials pages). It was also widely adopted as the basis for TEI-conformant authoring systems. Documentation introducing TEI Lite has been widely used for tutorial purposes and has been widely translated (see further the list of versions at http://www.tei-c.org/Lite/).

With the publication of TEI P4, the XML version of the TEI Guidelines, which uses the generation of TEI Lite as an example of the modification mechanism built into the TEI Guidelines, the opportunity was taken to produce a lightly revised XML-conformant version, but the present revision is the first substantively changed version since its first appearance in 1997. This revision takes advantage of the many new features introduced into the TEI Guidelines at release P5. A brief list of those changes likely to affect users of previous versions of this document is given below (Appendix A Substantive changes from the P4 version).

Lou Burnard, February 2006

Contents

Guidelines for Electronic Text Encoding and Interchange, as of February 2006, and available from the TEI Consortium website at http://www.tei-c.org. 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 .

1 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 programs 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.

The TEI was sponsored by the Association for Computers and the Humanities, the Association for Computational Linguistics, and the Association for Literary and Linguistic Computing, and is now maintained and developed by an independent membership consortium, hosted by four major Universities. Funding has been provided in part from the U.S. National Endowment for the Humanities, Directorate General XIII of the Commission of the European Communities, the Andrew W. Mellon Foundation, and the Social Science and Humanities Research Council of Canada. 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 were 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 manual conforms to version 0.3 of this most recent edition of the Guidelines, TEI P5.

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:
The world of scholarship is large and diverse. For the Guidelines to have wide acceptability, it was important to ensure that:
  1. the common core of textual features be easily shared;
  2. additional specialist features be easy to add to (or remove from) a text;
  3. multiple parallel encodings of the same feature should be possible;
  4. the richness of markup should be user-defined, with a very small minimal requirement;
  5. 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:

The reader may judge our success in meeting these goals for him or herself. At the time of first writing (1995), our confidence that we have at least partially done so is borne out by its use in practice for the encoding of real texts. The Oxford Text Archive uses TEI Lite when it translates texts from its holdings from their original markup schemes into SGML; the Electronic Text Centers at the University of Virginia and the University of Michigan have used TEI Lite to encode their holdings. And the Text Encoding Initiative itself uses TEI Lite, in its current technical documentation — including this document.

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.

2 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:
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:
<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>
This particular encoding represents a set of choices or priorities. The decision to focus on Brontë's text, rather than on the printing of it in this particular edition, 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 TEI-recommended way of carrying out most of these is 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: For recommendations on these and many other possibilities, the full Guidelines should be consulted.

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

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 19 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> [ TEI Header information ] </teiHeader>
  <text>
   <front> [ front matter ... ] </front>
   <body> [ body of text ... ] </body>
   <back> [ back matter ... ] </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> [ header information for the composite ] </teiHeader>
  <text>
   <front> [ front matter for the composite ] </front>
   <group>
    <text>
     <front> [ front matter of first text ] </front>
     <body> [ body of first text ] </body>
     <back> [ back matter of first text ] </back>
    </text>
    <text>
     <front> [ front matter of second text] </front>
     <body> [ body of second text ] </body>
     <back> [ back matter of second text ] </back>
    </text>
    [ more texts or groups of texts here ]
    </group>
   <back> [ back matter for the composite ] </back>
  </text>
 </TEI>
It is also possible to define a composite of TEI texts, each with its own header. Such a collection is known as a TEI corpus, and may itself have a header:
 <teiCorpus>
  <teiHeader> [header information for the corpus]</teiHeader>
  <TEI>
   <teiHeader>[header information for first text]</teiHeader>
   <text> [first text in corpus] </text>
  </TEI>
  <TEI>
   <teiHeader>[header information for second text]</teiHeader>
   <text> [second text in corpus] </text>
  </TEI>
 </teiCorpus>
It is not however possible to create a composite of corpora -- that is, a number of <teiCorpus> elements combined together and treated as a single object. This is a restriction of the current version of the TEI Guidelines.

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:

4 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 18 Front and Back Matter. In this section we discuss the elements making up the body of a text.

4.1 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.
  • p (paragraph) marks paragraphs in prose.
  • div (text division) contains a subdivision of the front, body, or back of a text.

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

The n attribute may be used to supply (additionally or alternatively) a short mnemonic name or number for the division. 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.

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 6.3 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 6 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 8.3 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="WN1n="Itype="book">
   <div xml:id="WN101n="I.1type="chapter"> ... </div>
   <div xml:id="WN102n="I.2type="chapter"> ... </div>
   ...
   <div xml:id="WN110n="I.10type="chapter">
    <div xml:id="WN1101n="I.10.1type="part"> ... </div>
    <div xml:id="WN1102n="I.10.2type="part"> ... </div>
   </div>
   ...
   </div>
  <div xml:id="WN2n="IItype="book"> .... </div>
 </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="TS01n="1type="Volume">
   <div xml:id="TS011n="1type="Chapter"> ... </div>
   <div xml:id="TS012n="2"> ...</div>
  </div>
  <div xml:id="TS02n="2type="Volume">
   <div xml:id="TS021n="3type="Chapter"> ...</div>
   <div xml:id="TS022n="4"> ...</div>
  </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.

4.2 Headings and Closings

Every <div> may have a title or heading at its start, and (less commonly) a closing such as ‘End of Chapter 1’. The following elements may be used to transcribe them:
  • head (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc.
  • trailer (trailer) contains a closing title or footer appearing at the end of a division of a text.
Some other elements which may be necessary at the beginning or ending of text divisions are discussed below in section 18.1.2 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="UGT1n="Wintertype="Part">
  <div xml:id="UGT11n="1type="Chapter">
   <head>Mellstock-Lane</head>
   <p>To dwellers in a wood almost every species of tree ... </p>
  </div>
 </div>

4.3 Prose, Verse and Drama

As noted above, the paragraphs making up a textual division should be tagged with the <p> tag. For example:
 <p>I fully appreciate Gen. Pope's splendid achievements with their invaluable results; but you must know that Major Generalships in the Regular Army, are not as plenty as blackberries. </p>
A number of different tags are provided for the encoding of the structural components of verse and performance texts (drama, film, etc.):
  • l (verse line) contains a single, possibly incomplete, line of verse.
  • lg (line group) contains a group of verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc.
  • sp (speech) An individual speech in a performance text, or a passage presented as such in a prose or verse text.
  • speaker A specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment.
  • stage (stage direction) contains any kind of stage direction within a dramatic text or fragment.
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 5 Page and Line Numbers may be used to mark typographic lines if so desired.

Sometimes, particularly in dramatic texts, 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, as in this example:
 <div type="Actn="I">
  <head>ACT I</head>
  <div type="Scenen="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="stanzapart="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>
This example shows how dialogue presented in a prose work as if it were drama should be encoded. It 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 Opimiam</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 Opimiam</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>

5 Page and Line Numbers

Page and line breaks may be marked with the following empty 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. Recording the line breaks may be useful for the same reason; treatment of end-of-line hyphenation in printed source texts will require some consideration.

If pagination, etc., 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="ED1n="475"/> Mary approved the
 step unreservedly. Diana announced that she would
 <pb ed="ED2n="485"/>just give me time to get over the
 honeymoon, and then she would come and see me.</p>

The <pb> and <lb> elements are special cases of the general class of milestone elements which mark reference points within a text. TEI Lite also includes a generic <milestone> element, which is not restricted to special cases but 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. 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.

6 Marking Highlighted Phrases

6.1 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. For example, a heading rendered in bold might be tagged <head rend="bold">, and one in italic <head rend="italic">.

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.
  • hi (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made.
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.
  • emph (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect.
  • foreign (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text.
  • gloss identifies a phrase or word used to provide a gloss or definition for some other word or phrase.
  • label contains the label associated with an item in a list; in glossaries, marks the term being defined.
  • mentioned marks words or phrases mentioned, not used.
  • term contains a single-word, multi-word, or symbolic designation which is regarded as a technical term.
  • title contains the full title of a work of any kind.

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

6.2 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:
  • q (quoted speech, thought, or writing) contains material which is marked as (ostensibly) quoted from elsewhere; in narrative, this element is used to mark direct or indirect speech; in dictionaries, it may be used to mark real or contrived examples of usage; in manuscript descriptions or other metadata, to mark extracts quoted from the source being documented.
  • mentioned marks words or phrases mentioned, not used.
  • soCalled (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics.
  • gloss identifies a phrase or word used to provide a gloss or definition for some other word or phrase.
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 8.3 Special kinds of Linking.
Quotations may be accompanied by a reference to the source or speaker, using the who attribute, whether or not the source is given 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.

As with highlighting, it is not always possible and may not be considered desirable to interpret the function of quotation marks in a text in this way. In such cases, the tag <hi rend="quoted"> might be used to mark quoted text without making any claim as to its status.

6.3 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="fra">savoir-faire</foreign>.</p>
 <p>Have you read <title xml:lang="deu">Die Dreigroschenoper</title>?</p>
 <p>
  <mentioned xml:lang="fra">Savoir-faire</mentioned> is French for
 know-how.</p>
 <p>The court issued a writ of <term xml:lang="lat">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 standards1, as further explained in the relevant section of the TEI Guidelines. Some simple example codes for a few languages are given here:
zh or zho Chinese grc Ancient Greek
en English ell or el Greek
enm Middle English ja or jpn Japanese
fr or fra French la or lat Latin
de or deu German sa or san Sanskrit

7 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; otherwise, the TEI header should state which kind they are.

Examples:
 <p>Collections are ensembles of distinct entities or objects of any sort. <note place="footn="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>

8 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 8.3 Special kinds of Linking.

8.1 Simple Cross References

A cross reference from one point within a single document to another can be encoded using either of the following elements:
  • ref defines a reference to another location, possibly modified by additional text or comment.
  • ptr/ defines a pointer to another location.

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 the text of the cross-reference itself. 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 (assuming we have documented somewhere the exact verbal form of cross references represented by <ptr> elements):
See especially  <ref target="#SEC12">section 12 on page 34</ref>.
See especially  <ptr target="#SEC12"/>.
The value of the target attribute must have been used as the identifier of some other element within the current document. This implies that 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 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>
The targType attribute can be used to specify that the element pointed to must be of a particular type, as in the following example:
... this is discussed in  <ref target="#dspectargType="div body"> the section on links</ref>

This reference should fail if the element with identifier dspec is neither a <div> nor a <body>.

The type attribute can be used to categorize the link represented by the pointer in any convenient way. The resp and crDate attributes may also be used to represent the person or agency responsible for making the link, and its date of creation, as in the following example:
... this is discussed in  <ref type="xrefcrdate="950521target="#dspec"> the section on links</ref>
These attributes are most likely to be of use in hypertext systems containing very many pointers used for a variety of purposes and created by a variety of means.
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:
  • anchor/ (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element.
  • seg (arbitrary segment) contains any arbitrary phrase-level unit of text (including other seg elements).
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="bookmarkxml:id="ABCD"/> ....
....
 <seg type="targetxml: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 8.3 Special kinds of Linking below.

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

Within a URL, 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. A full specification of the language is well beyond the scope of this document; here we provide only a flavour of its power.

In the XPath language, locations are defined as a series of steps, each one identifying some part of the document, often in terms of the locations identified by the previous step. For example, you would point to the third sentence of the second paragraph of chapter two by selecting chapter two in the first step, the second paragraph in the second step, and the third sentence in the last step. A step can be defined in terms of the document tree itself, using such concepts as parent, descendent, preceding, etc. or, more loosely, in terms of text patterns, word or character positions.

8.3 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 15 Interpretation and Analysis. For example, a linguistic analysis of the sentence ‘John loves Nancy’ might be encoded as follows:
 <seg type="sentenceana="SVO">
  <seg type="lexana="#NP1">John</seg>
  <seg type="lexana="#VVI">loves</seg>
  <seg type="lexana="#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 lang="FRAxml:id="FR1corresp="#EN1">Jean aime Nancy</seg>
 <seg lang="ENGxml:id="EN1corresp="#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 anaphoric 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="networkcorresp="#nbc">the network</seg>
 says <seg xml:id="showcorresp="#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="Q1anext="#Q1b">Who-e debel you?</q>
— he at last said —
 <q xml:id="Q1bprev="#Q1a">you no speak-e, damme, I kill-e.</q> And so saying,
the lighted tomahawk began flourishing
about me in the dark.

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

9.1 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:
  • corr (correction) contains the correct form of a passage apparently erroneous in the copy text.
  • sic contains text reproduced although apparently incorrect or inaccurate.
The following elements may be used to mark normalization, that is editorial changes introduced for the sake of consistency or modernization of a text:
  • orig (original form) contains a reading which is marked as following the original, rather than being normalized or corrected.
  • reg (regularization) contains a reading which has been regularized or normalized in some sense.
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 Shakesperean scholar 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.
  • choice groups a number of alternative encodings for the same point in a text.
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>

9.2 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:
  • add (addition) contains letters, words, or phrases inserted in the text by an author, scribe, annotator, or corrector.
  • gap (omitted material) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible or inaudible.
  • del (deletion) contains a letter, word or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, annotator, or corrector.
  • unclear contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source.
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 indicates that ‘LB’ corrected 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 not limited to changes made by an editor; they can also be 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="DHLtype="overstrike">galls</del>
 <add hand="DHLplace="supralinear">dogs</add> me,
what a galling shadow
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 & twenty good regulars joined to me  <unclear>
  <gap reason="indecipherable"/>
 </unclear>
& instantly, would aid me signally
 <add hand="ed">in?</add>
an enterprise against Wilmington.
The <del> element marks material which is 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>

9.3 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:
  • abbr (abbreviation) contains an abbreviation of any sort.
  • expan (expansion) contains the expansion of an abbreviation.
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. An appropriate encoding for this purpose would be
 <expan>w<hi>i</hi>t<hi>h</hi>
 </expan>
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>

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

10.1 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:
  • rs (referencing string) contains a general purpose name or referring string.
  • name (name, proper noun) contains a proper noun or noun phrase.
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="personkey="BENM1">Mr. Bennet</rs>,
  </q> said
 <rs type="personkey="BENM2">his lady</rs>
to him one day,
 <q>have you heard that <rs type="placekey="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="personkey="WADLM1">
  <choice>
   <sic>Walter de la Mare</sic>
   <reg>de la Mare, Walter</reg>
  </choice>
 </name> was born at

 <name key="Ch1type="place">Charlton</name>, in

 <name key="KT1type="county">Kent</name>, in 1873.
The <index> element discussed in indexing 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.

10.2 Dates and Times

Tags for the more detailed encoding of times and dates include the following:
  • date contains a date in any format.
  • time contains a phrase defining a time of day in any format.
The value 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 value="1980-02-21">21 Feb 1980</date>
 <date value="1990">1990</date>
 <date value="1990-09">September 1990</date>
 <date value="--09">September</date>
 <date value="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 value="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 value="15:00">three o'clock in the afternoon</time>
 </l>

10.3 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:
  • num (number) contains a number, written in any form.
For example:
 <num value="33">xxxiii</num>
 <num type="cardinalvalue="21">twenty-one</num>
 <num type="percentagevalue="10">ten percent</num>
 <num type="percentagevalue="10">10%</num>
 <num type="ordinalvalue="5">5th</num>

11 Lists

The element <list> is used to mark any kind of list. A list is a sequence of text items, which may be ordered, unordered, or 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 lang="enm">nu</label>
  <item>now</item>
  <label lang="enm">lhude</label>
  <item>loudly</item>
  <label lang="enm">bloweth</label>
  <item>blooms</item>
  <label lang="enm">med</label>
  <item>meadow</item>
  <label lang="enm">wude</label>
  <item>wood</item>
  <label lang="enm">awe</label>
  <item>ewe</item>
  <label lang="enm">lhouth</label>
  <item>lows</item>
  <label lang="enm">sterteth</label>
  <item>bounds, frisks</item>
  <label lang="enm">verteth</label>
  <item lang="lat">pedit</item>
  <label lang="enm">murie</label>
  <item>merrily</item>
  <label lang="enm">swik</label>
  <item>cease</item>
  <label 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 (13 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.

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

13 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="5cols="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>

14 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, by using the elements described in this section. The same elements may also be used to embed digitized versions of the graphic within an electronic document.

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 may also 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"/>
 <graphic url="p412fig.png"/>
 <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>

When a digitized version of the graphic concerned is available, it may be embedded at the appropriate point within the document in this way.

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

15.1 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:
  • s (s-unit) contains a sentence-like division of a text.
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="chaptern="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.

15.2 General-Purpose Interpretation Elements

A more general purpose segmentation element, the <seg> has already been introduced for use in identifying otherwise unmarked targets of cross references and hypertext links (see section 8 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 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="chaptern="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 8.3 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.
  • interp (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text.
  • interpGrp (interpretation group) collects together a set of related interpretations which share responsibility or type.
These elements allows 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 an empty element, which must be linked to the passage to which it applies either by means of the ana attribute discussed in section 8.3 Special kinds of Linking above, or by means of its own inst attribute. This means that any kind of analysis can be represented, with no need to respect the document hierarchy, and also facilitates 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="figure of speech"
      value="apostrophe"/>

    <interp
      xml:id="fig-hyp-1"
      resp="#LB-MSM"
      type="figure of speech"
      value="hyperbole"/>

    <interp
      xml:id="set-church-1"
      resp="#LB-MSM"
      type="setting"
      value="church"/>

    <interp
      xml:id="ref-church-1"
      resp="#LB-MSM"
      type="reference"
      value="church"/>

    <interp
      xml:id="ref-serv-1"
      resp="#LB-MSM"
      type="reference"
      value="servants"/>

   </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="figure of speechresp="#LB-MSM">
     <interp xml:id="fig-aposvalue="apostrophe"/>
     <interp xml:id="fig-hypvalue="hyperbole"/>
     <interp xml:id="fig-metavalue="metaphor"/>
    </interpGrp>
    <interpGrp type="scene-settingresp="#LB-MSM">
     <interp xml:id="set-churchvalue="church"/>
     <interp xml:id="set-kitchvalue="kitchen"/>
     <interp xml:id="set-unspecvalue="unspecified"/>
    </interpGrp>
    <interpGrp type="referenceresp="#LB-MSM">
     <interp xml:id="ref-churchvalue="church"/>
     <interp xml:id="ref-servvalue="servants"/>
     <interp xml:id="ref-cookvalue="cooking"/>
    </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="chaptern="38">
  <p xml:id="P38.1ana="#set-church #set-kitch"/>
  <s xml:id="P38.1.1ana="#fig-apos">Reader, I married him.</s>
 ...</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="figure of speech"
   resp="#LB-MSM"
   value="apostrophe"
   inst="#P38.1.1"/>

 <interp
   xml:id="set-church-2"
   type="scene-setting"
   value="church"
   inst="#P38.1"
   resp="#LB-MSM"/>

 <interp
   xml:id="set-kitchen-2"
   type="scene-setting"
   value="kitchen"
   inst="#P38.1"
   resp="#LB-MSM"/>
The <interp> 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 8.3 Special kinds of Linking assumes a linguistic analysis which might be represented as follows:
 <interp xml:id="NP1type="posvalue="noun phrase, singular"/>
 <interp
   xml:id="VV1"
   type="pos"
   value="inflected verb, present-tense singular"/>

...

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

16.1 Additional Elements for Technical Documents

The following elements may be used to mark particular features of technical documents:
  • eg contains any kind of illustrative example.
  • code contains literal code from some formal language such as a programming language
  • ident contains an identifier or name for an object of some kind in a formal language
  • gi (generic identifier) contains the name (generic identifier) of an element.
  • att (attribute) contains the name of an attribute appearing within running text.
  • formula contains a mathematical or other formula.
  • val (value) contains a single attribute value.
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> 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.

16.2 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.
  • divGen (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear.
The <divGen> element can be placed anywhere that a division element would be legal, as in the following example:
 <front>
  <titlePage> ... </titlePage>
  <divGen type="toc"/>
  <div type="Preface">
   <head>Preface</head> ... </div>
 </front>
 <body> ... </body>
 <back>
  <div>
   <head>Appendix</head> ... </div>
  <divGen type="indexn="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 11 Lists should be used.

16.3 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.
  • index (index entry) marks a location to be indexed for whatever purpose.
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.2
 <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 7 Notes, or with the <interp> element discussed in section 15 Interpretation and Analysis. Here we demonstrate how it might also be satisfied by using the <index> element.
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.

16.4 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.
  • address contains a postal address, for example of a publisher, an organization, or an individual.
  • addrLine contains one line of a postal 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 10.1 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>

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

18 Front and Back Matter

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

18.1.1 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:
  • titlePage (title page) contains the title page of a text, appearing within the front or back matter.
  • docTitle (document title) contains the title of a document, including all its constituents, as given on a title page.
  • titlePart (title part) contains a subsection or division of the title of a work, as indicated on a title page.
  • byline contains the primary statement of responsibility given for a work on its title page or at the head or end of the work.
  • docAuthor (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline).
  • docDate (document date) contains the date of a document, as given (usually) on a title page.
  • docEdition (document edition) contains an edition statement as presented on a title page of a document.
  • docImprint (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page.
  • epigraph (epigraph) contains a quotation, anonymous or attributed, appearing at the start of a section or chapter, or on a title page.

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 lang attribute or the <foreign> element, as necessary. Names, wherever they appear, should be tagged using the <name>, as elsewhere.

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>

18.1.2 Prefatory Matter

Major blocks of text within the front matter should be marked as <div> or <div> elements; the following suggested values for the type attribute may be used to distinguish various common types of prefatory matter:
foreword
a text addressed to the reader, by the author, editor or publisher, possibly in the form of a letter.
preface
a text addressed to the reader, by the author, editor or publisher, possibly in the form of a letter.
dedication
a text (often a letter) addressed to someone other than the reader in which the author typically commends the work in hand to the attention of the person concerned.
abstract
a prose argument summarizing the content of the work.
ack
Acknowledgements.
contents
a table of contents (typically this should be tagged as a <list>).
frontispiece
a pictorial frontispiece, possibly including some text.
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:
  • salute (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc.
  • signed (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text.
  • byline contains the primary statement of responsibility given for a work on its title page or at the head or end of the work.
  • dateline contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer.
  • argument A formal list or prose description of the topics addressed by a subdivision of a text.
  • cit A quotation from some other document, together with a bibliographic reference to its source.
  • opener groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter.
  • closer groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter.

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, &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
  <closer>
    <salute>Your faithfull, and most humble servant</salute>
    <signed>
     <name>H. LAWES.</name>
    </signed>
   </closer>
  </p>
 </div>

18.2 Back Matter

18.2.1 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 appendix.
glossary
a list of words and definitions, typically marked up as a <list type="gloss"> element .
notes
a series of <note> elements.
bibliography
a series of bibliographic references, typically in the form of a special bibliographic-list element <listBibl>, whose items are individual <bibl> elements.
index
a set of index entries, possibly represented as a structured list or glossary list, with optional leading <head> and perhaps some paragraphs of introductory or closing text (An index may also be generated for a document by using the <index> element, described above in section ).
colophon
a description at the back of the book describing where, when, and by whom it was printed; in modern books it also often gives production details and identifies the type faces used.

19 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, which share many 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:

19.1 The File Description

The <fileDesc> element is mandatory. It contains a full bibliographic description of the file with the following elements:
  • titleStmt (title statement) groups information about the title of a work and those responsible for its intellectual content.
  • editionStmt (edition statement) groups information relating to one edition of a text.
  • extent describes the approximate size of a text as stored on some carrier medium, whether digital or non-digital, specified in any convenient units.
  • publicationStmt (publication statement) groups information concerning the publication or distribution of an electronic or other text.
  • seriesStmt (series statement) groups information about the series, if any, to which a publication belongs.
  • notesStmt (Notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description.
  • sourceDesc supplies a description of the source text(s) from which an electronic text was derived or generated.
A minimal header has the following structure:
 <teiHeader>
  <fileDesc>
   <titleStmt> ... </titleStmt>
   <publicationStmt> ... </publicationStmt>
   <sourceDesc> ... </sourceDesc>
  </fileDesc>
 </teiHeader>

19.1.1 The Title Statement

The following elements can be used in the <titleStmt>:
  • title contains the full title of a work of any kind.
  • author in a bibliographic reference, contains the name of the author(s), personal or corporate, of a work; the primary statement of responsibility for any bibliographic item.
  • sponsor specifies the name of a sponsoring organization or institution.
  • funder (Funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text.
  • principal (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text.
  • respStmt (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply.
It is recommended that the title should distinguish the computer file from 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:
  • resp contains a phrase describing the nature of a person's intellectual responsibility.
  • name (name, proper noun) contains a proper noun or noun phrase.
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>

19.1.2 The Edition Statement

The <editionStmt> groups information relating to one edition of a text (where edition is used as elsewhere in bibliography), and may include the following elements:
  • edition (Edition) describes the particularities of one edition of a text.
  • respStmt (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply.
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.

19.1.3 The Extent Statement

The <extent> statement describe the approximate size of a file.

Example:
 <extent>4532 bytes</extent>

19.1.4 The Publication Statement

The <publicationStmt> is mandatory. It may contain a simple prose description or groups of the elements described below:
  • publisher provides the name of the organization responsible for the publication or distribution of a bibliographic item.
  • distributor supplies the name of a person or other agency responsible for the distribution of a text.
  • authority (release authority) supplies the name of a person or other agency responsible for making an electronic file available, other than a publisher or distributor.
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:
  • pubPlace contains the name of the place where a bibliographic item was published.
  • address contains a postal address, for example of a publisher, an organization, or an individual.
  • idno (identifying number) supplies any standard or non-standard number used to identify a bibliographic item.
  • availability supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, etc.
  • date contains a date in any format.
Example:
 <publicationStmt>
  <publisher>Oxford University Press</publisher>
  <pubPlace>Oxford</pubPlace>
  <date>1989</date>
  <idno type="ISBN"> 0-19-254705-5</idno>
  <availability>Copyright 1989, Oxford University Press</availability>
 </publicationStmt>

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

19.1.6 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:
  • bibl (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.
  • biblFull contains a fully-structured bibliographic citation, in which all components of the TEI file description are present.
  • listBibl (citation list) contains a list of bibliographic citations of any kind.
Examples:
 <sourceDesc>
  <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile, 1968)</bibl>
 </sourceDesc>
 <sourceDesc>
  <scriptStmt xml:id="CNN12">
   <bibl>
    <author>CNN Network News</author>
    <title>News headlines</title>
    <date>12 Jun 1989</date>
   </bibl>
  </scriptStmt>
 </sourceDesc>

19.2 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:
  • projectDesc (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected.
  • samplingDecl (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection.
  • editorialDecl (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text.
  • refsDecl (references declaration) specifies how canonical references are constructed for this text.
  • classDecl (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text.

19.2.1 Project and Sampling Descriptions

Examples of <projectDesc> and <samplingDesc>:
 <encodingDesc>
  <projectDesc>Texts collected for use in the Claremont Shakespeare Clinic, June 1990. </projectDesc>
 </encodingDesc>
 <encodingDesc>
  <samplingDecl>Samples of 2000 words taken from the beginning of the text </samplingDecl>
 </encodingDesc>

19.2.2 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>
  <p>All quotation marks converted to entity references odq and cdq.</p>
 </editorialDecl>

19.2.3 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 N attribute on each DIV and DIV contains the canonical reference for each such division in the form XX.yyy where XX is the book number in roman numeral and yyy is the section number in arabic.</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:
  • taxonomy (taxonomy) defines a typology used to classify texts either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy.
  • bibl (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.
  • category (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy.
  • catDesc (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal textDesc.
In the simplest case, the taxonomy may be defined by a bibliographic reference, as in the following example:
 <classDecl>
  <taxonomy xml:id="LCSH">
   <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 further described below.

19.3 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:
  • creation contains information about the creation of a text.
  • langUsage (language usage) describes the languages, sublanguages, registers, dialects etc. represented within a text.
  • textClass (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc.

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 value="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:
  • language characterizes a single language or sublanguage used within a text.
an example is needed.
The <textClass> element classifies a text by reference to the system or systems defined by the <classDecl> element, and contains one or more of the following elements:
  • keywords contains a list of keywords or phrases identifying the topic or nature of a text.
  • classCode contains the classification code used for this text in some standard classification system.
  • catRef/ (category reference) specifies one or more defined categories within some taxonomy or text typology.
The element <keywords> contains a list of keywords or phrases identifying the topic or nature of a text. The attribute scheme links these to the classification system defined in <taxonomy>.
 <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>

19.4 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 thje change. The attributes date and who may be used to identify when the change was carried out and the agency responsible for it.

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

20 List of Elements Described

The following list shows all the elements defined for the TEI Lite schema, with a brief description of each, and a link to its full specification in the Appendix.
Appendixes

Appendix A Substantive changes from the P4 version

This revision of the TEI Lite schema conforms to the TEI P5 Guidelines, which makes a number of changes from the TEI P4 Guidelines underlying earlier versions of TEI Lite. The following brief list indicates some of the major changes which will be needed in existing TEI P4-conformant documents before they can be used with the new schema. A fuller list is in preparation for publication as a part of TEI P5: the items listed here relate specifically to changes in TEI Lite only.

Appendix B Formal specification

The TEI Lite is a pure subset of the TEI. All of the elements defined in it are taken from the following standard TEI modules: tei, core, header, textstructure, figures, linking, analysis, and tagdocs.

The following elements from those modules are excluded from the schema: <ab>, <alt>, <altGrp>, <altIdent>, <analytic>, <attDef>, <attList>, <attRef>, <biblItem>, <biblStruct>, <binaryObject>, <broadcast>, <c>, <cb>, <cl>, <classSpec>, <classes>, <content>, <correction>, <datatype>, <defaultVal>, <desc>, <distinct>, <div0>, <div1>, <div2>, <div3>, <div4>, <div5>, <div6>, <div7>, <egXML>, <elementSpec>, <email>, <equipment>, <equiv>, <exemplum>, <floatingtext>, <fsdDecl>, <headItem>, <headLabel>, <hyphenation>, <imprimatur>, <interpretation>, <join>, <joinGrp>, <link>, <linkGrp>, <listRef>, <m>, <macroSpec>, <measure>, <meeting>, <memberOf>, <metDecl>, <metSym>, <moduleRef>, <moduleSpec>, <monogr>, <normalization>, <phr>, <postBox>, <postCode>, <quotation>, <recording>, <recordingStmt>, <remarks>, <schemaSpec>, <scriptStmt>, <segmentation>, <series>, <span>, <spanGrp>, <specDesc>, <specGrp>, <specGrpRef>, <specList>, <state>, <stdVals>, <street>, <stringVal>, <tag>, <timeline>, <valDesc>, <valItem>, <valList>, <variantEncoding>, <w>, <when>

Here is the TEI Lite schema itself :

Classes defined

att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual.

Module tei
Members change q sp
Attributes In addition to global attributes
who indicates the person, or group of people, to whom the element content is ascribed.
Status Optional
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values For transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified <person> element.

att.authorialIntervention

att.authorialIntervention provides attributes describing the nature of an authorial intervention.

Module tei
Members add del
Attributes In addition to global attributes
hand signifies the hand of the agent which made the addition or performed the deletion.
Status Optional
Datatype data.pointer
Values must refer to a <hand> element, typically declared in the document header (see section ).
status may be used to indicate faulty deletions, e.g. strikeouts which include too much or too little text, or erroneous additions, e.g., an insertion which duplicates some of the text already present.

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

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

Status Optional
Datatype data.enumerated
Sample values include:
duplicate all of the text indicated as an addition duplicates some text that is in the original, whether the duplication is word-for-word or less exact.
duplicate-partial part of the text indicated as an addition duplicates some text that is in the original
excessStart some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
excessEnd some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
shortStart some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
shortEnd some text at the end of the deletion is not marked as deleted even though it clearly should be.
unremarkable the deletion is not faulty. [Default]
type classifies the type of addition or deletion using any convenient typology.

No recommendation of any particular typology is made here; note however that the type attribute should not be used to record the manner in which a deletion is signalled in the source. This should be recorded using the global rend attribute, with values such as subpunction (dots below the line indicate matter to be deleted); overstrike (lines through the text indicated matter to be deleted); erasure (material to be deleted has been erased, but remains legible enough to transcribe); bracketed (brackets around the material indicate that it is spurious or superfluous), etc.

Status Optional
Datatype data.enumerated
Values a string identifying the class of addition or deletion.

att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events.

Module tei
Members date time
Attributes Global attributes and those inherited from [att.datable.w3c ]
Note

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

att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events using the W3C datatypes.

Module tei
Members att.datable [ date time]
Attributes In addition to global attributes
period supplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred.
Status Optional
Datatype data.pointer
when supplies the value of a date or time in a standard form.Example

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

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

A usage example of <date>.

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

A usage example of <time>.

 <opener>
  <dateline>
   <placeName>Dorchester, Village,</placeName>
   <date when="1828-03-02">March 2d. 1828.</date>
  </dateline>
  <salute>To Mrs. Cornell,</salute>
  Sunday <time when="12:00:00">noon.</time>
 </opener>
The value of the when attribute is a string representing a date, date & time, or time, in any one of the following forms:
  • a date in any of the standard formats described by XML Schema Part 2: Datatypes Second Edition, i.e. most commonly yyyy-mm-dd, but also yyyy, --mm, ---dd, yyyy-mm, or --mm-dd
  • a time in the standard format described by XML Schema Part 2: Datatypes Second Edition, i.e. hh:mm:ss
  • a combined date and time in any of the standard formats described by XML Schema Part 2: Datatypes Second Edition, i.e. yyyy-mm-ddThh:mm:ss

The value of when is constrained to be in one of the date, time, or combined date & time formats recognized by the W3C XML Schema Part 2: Datatypes specification. This is true whether the date component (if any) is a Gregorian or a proleptic Gregorian date.

At the time of this writing, the W3C does not permit the year 0000, which would normally be used to represent the year 1 BCE. Using the current W3C system, the year 1 BCE is indicated with -0001, the year 2 BCE with -0002, etc.
It is the intention of the XML Schema Working Group to allow 0000 as … the lexical representation of 1 BCE (which is a leap year), -0001 will become the lexical representation of 2 BCE, -0002 of 3 BCE, etc.
Thus in some cases it may be advantageous to use the when-iso attribute to indicate years BCE instead.
Status Optional
Datatype data.temporal.w3c
Values A normalized form of temporal expression conforming to the W3C XML Schema Part 2: Datatypes Second Edition.
notBefore specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.temporal.w3c
Values A normalized form of temporal expression conforming to the W3C XML Schema Part 2: Datatypes Second Edition.
notAfter specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype data.temporal.w3c
Values A normalized form of temporal expression conforming to the W3C XML Schema Part 2: Datatypes Second Edition.
from indicates the starting point of the period in standard form.
Status Optional
Datatype data.temporal.w3c
Values A normalized form of temporal expression conforming to the W3C XML Schema Part 2: Datatypes Second Edition.
to indicates the ending point of the period in standard form.
Status Optional
Datatype data.temporal.w3c
Values A normalized form of temporal expression conforming to the W3C XML Schema Part 2: Datatypes Second Edition.
Note

If both when and dur are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. In order to represent a time range by a duration and its ending time the when-iso attribute must be used.

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

att.declarable

att.declarable provides attributes for those elements in the TEI Header which may be independently selected by means of the specialpurpose decls attribute.

Module tei
Members bibl biblFull editorialDecl langUsage listBibl projectDesc refsDecl samplingDecl sourceDesc textClass
Attributes In addition to global attributes
default indicates whether or not this element is selected by default when its parent is selected.
Status Mandatory when applicable
Datatype xsd:boolean
Legal values are:
true (This element is selected if its parent is selected)
false (This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.) [Default]
Note

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

att.declaring

att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element.

Module tei
Members back body div front gloss group ptr ref term text
Attributes In addition to global attributes
decls identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
Status Mandatory when applicable
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values must identify a set of declarable elements of different types.
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter .

att.divLike

att.divLike provides a set of attributes common to all elements which behave in the same way as divisions.

Module tei
Members div lg
Attributes In addition to global attributes
type specifies a name conventionally used for this level of subdivision, e.g. act, volume, book, section, canto, etc.
Status Recommended
Datatype data.enumerated
Values any string of characters
org specifies how the content of the division is organized.
Status Optional
Legal values are:
composite (composite content: i.e. no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships.)
uniform (uniform content: i.e. the immediate contents of this element are regarded as forming a logical unit, to be processed in sequence.) [Default]
sample indicates whether this division is a sample of the original source and if so, from which part.
Status Optional
Legal values are:
initial (division lacks material present at end in source.)
medial (division lacks material at start and end.)
final (division lacks material at start.)
unknown (position of sampled material within original unknown.)
complete (division is not a sample.) [Default]
part specifies whether or not the division is fragmented by some other structural element, for example a speech which is divided between two or more verse stanzas.

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

Status Mandatory when applicable
Legal values are:
Y (the division is incomplete in some respect)
N (either the division is complete, or no claim is made as to its completeness.) [Default]
I (the initial part of an incomplete division)
M (a medial part of an incomplete division)
F (the final part of an incomplete division)

att.duration

att.duration provides attributes for normalization of elements that contain datable events.

Module tei
Members date time
Attributes Global attributes and those inherited from [att.duration.w3c ]
Note

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

att.duration.w3c

att.duration.w3c attributes for recording normalized temporal durations

Module tei
Members att.duration [ date time]
Attributes In addition to global attributes
dur (duration) indicates the length of this element in time.
Status Optional
Datatype data.duration.w3c
Note

If both when and dur are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. In order to represent a time range by a duration and its ending time the when-iso attribute must be used.

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

att.editLike

att.editLike provides attributes describing the nature of a encoded scholarly intervention or interpretation of any kind.

Module tei
Members add corr date del expan gap reg time unclear
Attributes In addition to global attributes
cert signifies the degree of certainty associated with the intervention or interpretation.
Status Optional
Datatype data.certainty
resp indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Status Optional
Datatype data.pointer
Values A pointer to an element in the document header that is associated with a person asserted as responsible for some aspect of the text's creation, transcription, editing, or encoding.
evidence indicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.

Status Optional
Datatype data.enumerated
Suggested values include:
internal there is internal evidence to support the intervention.
external there is external evidence to support the intervention.
conjecture the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
Note

The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

att.global

att.global provides a set of attributes common to all elements in the TEI encoding scheme.

Module tei
Members
Attributes In addition to global attributes and those inherited from [att.global.linking att.global.analytic ]
xml:space signals an intention that white space should be preserved by applications

The XML specification provides further guidance on the use of this attribute.

Status Optional
Legal values are:
default
preserve
xml:id provides a unique identifier for the element bearing the attribute.

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

Status Optional
Datatype xsd:ID
Values any valid XML identifier .
n gives a number (or other label) for an element, which is not necessarily unique within the document.

The n attribute may be used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

Status Optional
Datatype 1–∞ occurrences of data.wordseparated by whitespace
Values any string of characters; often, but not necessarily, numeric.
xml:lang indicates the language of the element content using the codes from RFC 3066

If no value is specified for xml:lang, the xml:lang value for the immediately enclosing element is inherited; for this reason, a value should always be specified on the outermost element (<TEI>).

Status Optional
Datatype data.language
Values The value must conform to RFC 3066 or its succesor. If the value is a private use code (i.e., starts with x-) it should, and if not it may, match the value of an ident attribute of a <language> element supplied in the TEI Header of the current document.
rend indicates how the element in question was rendered or presented in the source text.Example
 <head
   rend="align(center) slant(upright) case(allcaps)">

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

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

Status Optional
Datatype 1–∞ occurrences of data.wordseparated by whitespace
Values any string of characters; if the typographic rendition of a text is to be systematically recorded, a systematic set of values for the rend attribute should be defined.
xml:base provides a base URI reference with which applications can resolve relative URI references into absolute URI references.Example
 <div type="bibl">
  <head>Bibliography</head>
  <listBibl
    xml:base="http://www.lib.ucdavis.edu/BWRP/Works/">

   <bibl n="1">
    <author>
     <name>Landon, Letitia Elizabeth</name>
    </author>
    <ref target="LandLVowOf.sgm">
     <title>The Vow of the Peacock</title>
    </ref>
   </bibl>
   <bibl n="2">
    <author>
     <name>Compton, Margaret Clephane</name>
    </author>
    <ref target="NortMIrene.sgm">
     <title>Irene, a Poem in Six Cantos</title>
    </ref>
   </bibl>
   <bibl n="3">
    <author>
     <name>Taylor, Jane</name>
    </author>
    <ref target="TaylJEssay.sgm">
     <title>Essays in Rhyme on Morals and Manners</title>
    </ref>
   </bibl>
  </listBibl>
 </div>
Status Optional
Datatype data.pointer
Values any syntactically valid URI reference.
Note

The global attributes described here are made part of the attribute definition list declaration of each element by including a reference to the pattern att.global.attributes in each such declaration.

att.global.analytic

att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text.

Module analysis
Members att.global
Attributes In addition to global attributes
ana indicates one or more elements containing interpretations of the element on which the ana attribute appears.

When multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple mutually consistent interpretations of the same passage in different contexts.

Status Optional
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values one or more valid identifiers of one or more interpretive elements (usually <fs> or <interp>), separated by white space.

att.global.linking

att.global.linking defines a set of attributes for hypertext and other linking, which are enabled for all elements when the additional tag set for linking is selected.

Module linking
Members att.global
Attributes In addition to global attributes
corresp points to elements that correspond to the current element in some way.
Status Optional
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values one or more URIs, separated by white space.
synch points to elements that are synchronous with the current element.
Status Optional
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values one or more URIs, separated by white space.
sameAs points to an element that is the same as the current element.
Status Optional
Datatype data.pointer
Values a URI.
copyOf points to an element of which the current element is a copy.

Any content of the current element should be ignored. Its true content is that of the element being pointed at.

Status Optional
Datatype data.pointer
Values a URI.
next points to the next element of a virtual aggregate of which the current element is part.
Status Optional
Datatype data.pointer
Values a URI.
prev points to the previous element of a virtual aggregate of which the current element is part.
Status Optional
Datatype data.pointer
Values a URI.
exclude points to elements that are in exclusive alternation with the current element.
Status Optional
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values one or more URIs, separated by white space.
select selects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.

This attribute should be placed on an element which is superordinate to all of the alternants from which the selection is being made.

Status Optional
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values one or more URIs, separated by white space.

att.interpLike

att.interpLike provides attributes for elements which represent a formal analysis or interpretation.

Module tei
Members interp interpGrp
Attributes In addition to global attributes
resp indicates who is responsible for the interpretation.

Status Optional
Datatype data.pointer
Values A pointer to an element indicating the person responsible for the interpretation, typically to a <respStmt> in the <teiHeader>.
type indicates what kind of phenomenon is being noted in the passage.
Status Recommended
Datatype data.enumerated
Sample values include:
image (identifies an image in the passage.)
character (identifies a character associated with the passage.)
theme (identifies a theme in the passage.)
allusion (identifies an allusion to another text.)
inst points to instances of the analysis or interpretation represented by the current element.

The current element should be an analytic one. The element pointed at should be a textual one.

Status Optional
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values One or more valid identifiers, separated by white space.

att.measured

att.measured provides attributes for any kind of measurement, for example to provide a normalized form, or otherwise qualify the measurement given as content of the element concerned.

Module tei
Members gap measureGrp
Attributes In addition to global attributes
unit names the units used for the measurement.

The unit should normally be named using the standard abbreviation for an SI unit (see further http://www.bipm.org/en/si/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as "lines" or "characters".

Status Optional
Datatype data.enumerated
Suggested values include:
cm (centimetres)
mm (millimetres)
in (inches)
lines (lines of text)
chars (characters of text)
extent specifies the size of the measurement in the units specified
Status Optional
Datatype data.numeric
commodity indicates the substance that is being measured where this affects the meaning of the measurement
Status Optional
Datatype 1–∞ occurrences of data.wordseparated by whitespace
scope specifies the applicability of this measurement, where more than one object is being measured.

Status Optional
Datatype data.enumerated
Sample values include:
all (measurement applies to all instances.)
most (measurement applies to most of the instances inspected.)
range (measurement applies to only the specified range of instances.)

att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc.

Module tei
Members name pubPlace rs
Attributes In addition to global attributes
key provides an external means of locating a full definition for the entity being named, such as a database record key or other token.

The value may be a unique identifier from a database, or any other externally-defined name for the referent.

Status Optional
Datatype data.key
Values any string of Unicode characters
ref provides an explicit means of locating a full definition for the entity being named by means of a URI.

The value must point directly to an XML element containing the corresponding information, located within the current document or elsewhere and acccessible by a URI.

Status Optional
Datatype data.pointer
Values any valid URI
nymRef provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.

The value must point directly to an XML element containing the corresponding information, located within the current document or elsewhere and acccessible by a URI.

Status Optional
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values any valid URI

att.placement

att.placement provides attributes for describing where on the source page or object a textual element appears.

Module tei
Members add figure note
Attributes In addition to global attributes
place
Status Recommended
Datatype data.enumerated
Suggested values include:
infralinear (below the line)
margin-bot (in bottom margin)
margin-left (in left margin)
margin-right (in right margin)
margin-top (in top margin)
opposite (on opposite page)
overleaf (on the other side of the leaf)
supralinear (above the line)
verso (on verso of sheet)
app (note appears in the apparatus at the foot of the page.)
end (note appears at end of chapter or volume.)
foot (note appears at foot of page.)
inline (note appears as a marked paragraph in the body of the text.)
interlinear (note appears between lines of the text; a less precise form of either infralinear or supralinear.)
inline (addition is made in a space left in the witness by an earlier scribe.)
mixed (one or more of the other values)

att.pointing

att.pointing defines a set of attributes used by all elements which point to other elements by means of one or more URI references.

Module linking
Members ptr ref
Attributes In addition to global attributes
type categorizes the pointer in some respect, using any convenient set of categories.
Status Optional
Datatype data.word
Values Any string of XML name characters. The type should indicate the intended function of the pointer, or the rhetorical relationship between its source and target.
evaluate specifies the intended meaning when the target of a pointer is itself a pointer.

If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

Status Optional
Legal values are:
all (if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.)
one (if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.)
none (no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.)

att.segLike

att.segLike provides attributes for elements used for arbitrary segmentation.

Module tei
Members s seg
Attributes In addition to global attributes
type characterizes the type of segment.
Status Optional
Datatype data.enumerated
Values For a <cl> may take values such as finite, nonfinite, declarative, interrogative, relative etc. For a <phr> or <w>, values such as noun, verb, preposition, etc., may be used. For an <m> element, values such as clitic, prefix, stem will be more appropriate. For a <c> element, values such as letter, punctuation, digit may be used.
function characterizes the function of the segment.
Status Optional
Datatype data.enumerated
Values For a <cl>, may take values such as coordinate, subject, adverbial etc. For a <phr>, such values as subject, predicate etc. may be more appropriate.
part specifies whether or not the segment is fragmented by some other structural element, for example a clause which is divided between two or more sentences.

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

Status Mandatory when applicable
Legal values are:
Y (the segment is incomplete in some respect)
N (either the segment is complete, or no claim is made as to its completeness) [Default]
I (the initial part of an incomplete segment)
M (a medial part of an incomplete segment)
F (the final part of an incomplete segment)

att.spanning

att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it.

Module tei
Members index
Attributes In addition to global attributes
spanTo indicates the end of a span initiated by the element bearing this attribute.
Status Mandatory when applicable
Datatype data.pointer
Values points to an element following this one in the current document.
Note

The span is defined as running in document order from the start of the content of the pointing element (if any) to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element.

att.tableDecoration

att.tableDecoration provides attributes used to decorate rows or cells of a table.

Module tei
Members cell row
Attributes In addition to global attributes
role indicates the kind of information held in this cell or in each cell of this row.

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

Status Optional
Datatype data.enumerated
Suggested values include:
label (labelling or descriptive information only.)
data (data values.) [Default]
rows indicates the number of rows occupied by this cell or row.

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

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

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

Status Optional
Datatype data.count
Values A number; a value greater than one indicates that this cell or row spans several columns.

att.translatable

att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document.

Module tei
Members gloss
Attributes In addition to global attributes
version specifies the version name or number of the source from which the translated version was derived

The version may be a number, a letter, or a date

Status Optional
Datatype data.word

att.typed

att.typed provides generic attributes which can be used to classify or subclassify elements in any way.

Module tei
Members anchor date ident measureGrp relatedItem term text time
Attributes In addition to global attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Datatype data.word
subtype provides a sub-categorization of the element, if needed

The subtype attribute may be used to provide any sub-classification for the element, additional to that provided by its type attribute.

Status Optional
Datatype data.word
Note

The typology used may be formally defined using the the <classification> element of the <encodingDesc> within the associated TEI header, or informally as descriptive prose within the <encodingDesc> element.

model.addrPart

model.addrPart (address part) elements such as names or postal codes which may appear as a part of a postal address.

Module tei
Used by address
Members addrLine model.nameLike [ model.nameLike.agent [ name] rs]

model.addressLike

model.addressLike groups phrase-level elements used to represent postal or e-mail addresses.

Module tei
Used by model.pPart.data
Members address

model.biblLike

model.biblLike groups elements containing a bibliographic description.

Module tei
Used by cit listBibl sourceDesc taxonomy model.inter model.common
Members bibl biblFull

model.biblPart

model.biblPart (bibliographic citation part) groups elements which can appear within bibliographic citation elements.

Module tei
Used by bibl
Members distributor edition extent idno model.imprintPart [ biblScope pubPlace publisher] model.respLike [ author editor respStmt] relatedItem
Note

This class is used in defining the content model of the <bibl> and <biblItem> elements.

model.blockLike

model.blockLike groups segmenting elements.

Module tei
Used by sp
Members seg

model.choicePart

model.choicePart groups those elements (other than choice itself) which can be used in choice alternation

Module tei
Used by choice
Members abbr corr expan orig reg seg sic unclear

model.common

model.common groups common chunk- and inter-level elements.

Module tei
Used by argument body div macro.componentSeq
Members eg figure label model.biblLike [ bibl biblFull] model.divPart [ l lg p sp] model.listLike [ list listBibl] model.qLike [ cit q quote] table
Note

This class defines the set of chunk- and inter-level elements available in all bases; it is used in defining the standard models chunk.seq and macro.specialPara in the general and mixed bases.

model.dateLike

model.dateLike (dates and times) groups elements containing temporal expressions.

Module tei
Used by imprint model.pPart.data model.recordingPart
Members date time
Note

This class allows certain content models to permit a temporal expression encoded with either a <date> or a <time> element.

model.divGenLike

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

Module tei
Used by body
Members divGen

model.divLike

model.divLike groups elements used to represent structural divisions recursively.

Module tei
Used by back body front
Members div

model.divPart

model.divPart groups elements which can occur between, but not within, paragraphs and other chunks.

Module tei
Used by change macro.specialPara model.common
Members l lg p sp
Note

Note that this element class does not include members of the inter class, which can appear either within or between chunks. Unlike elements of that class, chunks cannot occur within chunks.

model.divWrapper

model.divWrapper (top-of-div elements) groups elements which can occur at the start or end of any division class element.

Module tei
Used by back body div divGen group lg list listBibl
Members argument byline dateline docAuthor docDate epigraph head opener salute

model.divWrapper.bottom

model.divWrapper.bottom (Bottom-of-division elements) groups elements which can occur only at the end of a text division; for example, a trailer.

Module tei
Used by back body div group lg list listBibl
Members closer signed trailer

model.egLike

model.egLike (examples) groups together elements for containing examples

Module tei
Used by model.phrase model.limitedPhrase
Members eg

model.emphLike

model.emphLike groups semantic phrase-level elements

Module tei
Used by model.highlighted model.limitedPhrase
Members code emph foreign gloss ident mentioned soCalled term title

model.encodingPart

model.encodingPart groups elements which may be used inside encodingDesc and appear multiple times

Module header
Used by encodingDesc
Members classDecl editorialDecl projectDesc refsDecl samplingDecl

model.frontPart

model.frontPart groups elements which appear at the level of divisions within front or back matter.

Module tei
Used by back front
Members divGen titlePage

model.global

model.global (global inclusions) groups empty elements which may appear at any point within a TEI text.

Module tei
Used by address argument back bibl body byline change cit closer date div docImprint docTitle figure front group imprint lg list listBibl opener row sp table text time titlePage macro.componentSeq macro.paraContent macro.phraseSeq macro.phraseSeq.limited macro.specialPara
Members anchor model.global.edit [ gap] model.global.meta [ index interp interpGrp] model.milestoneLike [ lb milestone pb] model.noteLike [ note]

model.global.edit

model.global.edit groups empty elements which perform a specifically editorial function, for example by indicating the start of a span of text added, deleted, or missing in a source.

Module tei
Used by model.global
Members gap
Note

Members of this class can appear anywhere within a document, between or within components or phrases.

model.global.meta

model.global.meta groups empty elements which describe the status of other elements, for example by holding groups of links or of abstract interpretations, or by providing indications of certainty etc., and which may appear at any point in a document.

Module tei
Used by model.global
Members index interp interpGrp
Note

Encoders may find it convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text.

model.glossLike

model.glossLike groups elements which provide an alternative name, explanation, or description for any markup construct.

Module tei
Used by category taxonomy
Members gloss

model.graphicLike

model.graphicLike (images, audio, formulae, etc.) groups elements containing images, formulae, and similar objects

Module tei
Used by figure model.phrase
Members formula graphic

model.headerPart

model.headerPart groups elements which may be used inside teiHeader and appear multiple times

Module header
Used by teiHeader
Members encodingDesc profileDesc

model.hiLike

model.hiLike groups phrase-level elements related to highlighting that have no specific semantics

Module tei
Used by model.highlighted
Members hi

model.highlighted

model.highlighted groups phrase-level elements related to highlighting.

Module tei
Used by bibl model.phrase
Members model.emphLike [ code emph foreign gloss ident mentioned soCalled term title] model.hiLike [ hi]

model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints.

Module tei
Used by imprint model.biblPart
Members biblScope pubPlace publisher

model.inter

model.inter groups elements of the intermediate (inter-level) class: these elements can occur both within and and between paragraphs or other chunk-level elements.

Module tei
Used by change macro.limitedContent macro.paraContent macro.specialPara
Members figure label model.biblLike [ bibl biblFull] model.listLike [ list listBibl] model.qLike [ cit q quote] model.stageLike [ stage] table
Note

This element class contains a subset of those elements which can appear in the unstructured ‘soup’ with which paragraph and other elements at the lowest level of crystal structures are filled: specifically all the elements which can also occur as structural elements in their own right. In prose, this means the elements in this class can appear both within and between paragraphs. This class is thus distinct from the purely phrase-level elements which can appear only within soup, and not on their own; the latter class, in keeping with this metaphor, is called ‘broth’; it is represented by the class phrase. Cf. also the class chunks.

model.lLike

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

Module tei
Used by lg sp
Members l

model.labelLike

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

Module tei
Used by
Members label

model.limitedPhrase

model.limitedPhrase groups those elements which can occur at the level of individual words or phrases, excluding elements intended for transcription.

Module tei
Used by catDesc change macro.limitedContent macro.phraseSeq.limited
Members model.egLike [ eg] model.emphLike [ code emph foreign gloss ident mentioned soCalled term title] model.pPart.data [ model.addressLike [ address] model.dateLike [ date time] model.measureLike [ measureGrp num] model.nameLike [ model.nameLike.agent [ name] rs] ] model.pPart.editorial [ abbr choice expan] model.ptrLike [ ptr ref] model.xmlPhrase [ att gi val]
Note

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

Elements which are primarily useful for the encoding of extant texts (e.g., <del>) are excluded from this class.

model.listLike

model.listLike groups all list-like elements.

Module tei
Used by model.inter model.common
Members list listBibl

model.measureLike

model.measureLike (numbers, amounts, measurements, etc.) groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning

Module tei
Used by measureGrp model.pPart.data
Members measureGrp num

model.milestoneLike

model.milestoneLike (reference system elements) groups milestone-style elements used to represent reference systems

Module tei
Used by model.global
Members lb milestone pb

model.msItemPart

model.msItemPart The class of elements which can appear within a manuscript item description.

Module tei
Used by
Members bibl listBibl model.quoteLike [ quote] model.respLike [ author editor respStmt] title

model.nameLike

model.nameLike (names of people, places, or organizations, or refering strings) groups those elements which name or refer to a person, place (man-made or geographic), or organization

Module tei
Used by model.addrPart model.pPart.data
Members model.nameLike.agent [ name] rs
Note

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

model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies.

Module tei
Used by respStmt model.nameLike
Members name
Note

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

model.noteLike

model.noteLike groups all note-like elements.

Module tei
Used by notesStmt model.global
Members note

model.pLike

model.pLike The class of elements which are paragraphs for the purpose of interchange.

Module tei
Used by availability cRefPattern editionStmt editorialDecl encodingDesc figure projectDesc publicationStmt refsDecl samplingDecl seriesStmt sourceDesc sp
Members p

model.pLike.front

model.pLike.front (Front matter chunk elements) groups elements which can occur as direct constituents of front matter, when a full title page is not given.

Module tei
Used by front
Members argument byline docAuthor docDate docEdition docImprint docTitle epigraph head titlePart

model.pPart.data

model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data.

Module tei
Used by bibl model.phrase model.limitedPhrase
Members model.addressLike [ address] model.dateLike [ date time] model.measureLike [ measureGrp num] model.nameLike [ model.nameLike.agent [ name] rs]

model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription.

Module tei
Used by bibl model.phrase
Members model.pPart.editorial [ abbr choice expan] model.pPart.transcriptional [ add corr del orig reg sic unclear]

model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring

Module tei
Used by model.pPart.edit model.limitedPhrase
Members abbr choice expan

model.pPart.transcriptional

model.pPart.transcriptional groups only those phrase-level elements for simple editorial correction and transcription that are not likely to be useful for authoring

Module tei
Used by model.pPart.edit
Members add corr del orig reg sic unclear

model.personPart

model.personPart groups elements which describe characteristics of the people referenced by a text, or participating in a language interaction.

Module tei
Used by
Members bibl model.assertLike
Note

This class is used to define the content model for the <person> and <personGrp> elements.

model.phrase

model.phrase groups those elements which can occur at the level of individual words or phrases.

Module tei
Used by byline closer date docImprint opener time macro.paraContent macro.phraseSeq macro.specialPara
Members model.egLike [ eg] model.graphicLike [ formula graphic] model.highlighted [ model.emphLike [ code emph foreign gloss ident mentioned soCalled term title] model.hiLike [ hi] ] model.pPart.data [ model.addressLike [ address] model.dateLike [ date time] model.measureLike [ measureGrp num] model.nameLike [ model.nameLike.agent [ name] rs] ] model.pPart.edit [ model.pPart.editorial [ abbr choice expan] model.pPart.transcriptional [ add corr del orig reg sic unclear] ] model.ptrLike [ ptr ref] model.segLike [ s seg] model.xmlPhrase [ att gi val]
Note

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

model.profileDescPart

model.profileDescPart groups elements which may be used inside profileDesc and appear multiple times

Module header
Used by profileDesc
Members langUsage textClass

model.ptrLike

model.ptrLike groups elements used for purposes of location and reference

Module tei
Used by bibl cit model.phrase model.limitedPhrase
Members ptr ref

model.publicationStmtPart

model.publicationStmtPart (publication statement elements) groups the children of publicationStmt

Module tei
Used by publicationStmt
Members address authority availability date distributor idno pubPlace publisher

model.qLike

model.qLike groups elements related to highlighting which can appear either within or between chunk-level elements.

Module tei
Used by model.inter model.common
Members cit q quote

model.quoteLike

model.quoteLike (quote and similar elements) groups elements used to directly contain quotations.

Module tei
Used by cit model.msItemPart
Members quote

model.recordingPart

model.recordingPart (dates and date ranges) groups elements used to describe details of an audio or video recording

Module tei
Used by
Members model.dateLike [ date time] respStmt

model.respLike

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

Module tei
Used by model.biblPart model.msItemPart
Members author editor respStmt

model.segLike

model.segLike groups elements used for arbitrary segmentation.

Module tei
Used by bibl model.phrase
Members s seg
Note

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

model.stageLike

model.stageLike (stage directions) groups elements containing specialized stage directions defined in the additional tag set for performance texts.

Module tei
Used by sp model.inter
Members stage
Note

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

model.titlepagePart

model.titlepagePart (Title page elements) groups those elements which can occur as direct constituents of a title page (docTitle, docAuth, docImprint, epigraph, etc.)

Module tei
Used by titlePage
Members byline docAuthor docDate docEdition docImprint docTitle epigraph figure graphic titlePart

model.xmlPhrase

model.xmlPhrase groups elements used to encode XML constructs at the phrase level, e.g. element names, attribute names, and attribute values

Module tei
Used by model.phrase model.limitedPhrase
Members att gi val

Elements defined

TEI

<TEI> (TEI document) contains a single TEI-conformant document, comprising a TEI header and a text, either in isolation or as part of a teiCorpus element. «#DS» «#CCDEF»

Module textstructure
Parents teiCorpus
Attributes In addition to global attributes
version The version of the TEI scheme
Status Optional
Datatype xsd:decimal
Values A number identifying the version of the TEI guidelines
Declaration
element TEI
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute version { xsd:decimal }?,
   ( teiHeader, text )
}
Example
 <TEI
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <teiHeader>
   <fileDesc>
    <titleStmt>
     <title>The shortest TEI Document Imaginable</title>
    </titleStmt>
    <publicationStmt>
     <p>First published as part of TEI P2.</p>
    </publicationStmt>
    <sourceDesc>
     <p>No source: this is an original work.</p>
    </sourceDesc>
   </fileDesc>
  </teiHeader>
  <text>
   <body>
    <p>This is about the shortest TEI document imaginable.</p>
   </body>
  </text>
 </TEI>
Note

This element is required.

abbr

<abbr> (abbreviation) contains an abbreviation of any sort. «#CONAAB»

Module core
Parents model.pPart.editorial model.choicePart
Attributes In addition to global attributes
type allows the encoder to classify the abbreviation according to some convenient typology.

The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use.

Status Optional
Datatype data.enumerated
Sample values include:
suspension (the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.)
contraction (the abbreviation omits some letter(s) in the middle.)
brevigraph (the abbreviation comprises a special symbol or mark.)
superscription (the abbreviation includes writing above the line.)
acronym (the abbreviation comprises the initial letters of the words of a phrase.)
title (the abbreviation is for a title of address (Dr, Ms, Mr, …))
organization (the abbreviation is for the name of an organization.)
geographic (the abbreviation is for a geographic name.)
Declaration
element abbr
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type { data.enumerated }?,
   macro.phraseSeq
}
Example
 <abbr>SPQR</abbr>
Example
 <choice>
  <abbr>SPQR</abbr>
  <expan>senatus populusque romanorum</expan>
 </choice>
Note

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

For a typology of Middle English abbreviations, see A. G. Petty, English literary hands from Chaucer to Dryden (London: Edward Arnold, 1977), pp. 22–25.

add

<add> (addition) contains letters, words, or phrases inserted in the text by an author, scribe, annotator, or corrector. «#COEDADD»

Module core
Parents model.pPart.transcriptional
Attributes Global attributes and those inherited from [att.authorialIntervention att.editLike att.placement ]
Declaration
element add
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.authorialIntervention.attribute.hand,
   att.authorialIntervention.attribute.status,
   att.authorialIntervention.attribute.type,
   att.editLike.attribute.cert,
   att.editLike.attribute.resp,
   att.editLike.attribute.evidence,
   att.placement.attribute.place,
   macro.paraContent
}
Note

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

addrLine

<addrLine> contains one line of a postal address. «#CONAAD» «#HD24» «#COBICOI»

Module core
Parents model.addrPart
Attributes Global attributes only
Declaration
element addrLine
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <address>
  <addrLine>Computing Center, MC 135</addrLine>
  <addrLine>P.O. Box 6998</addrLine>
  <addrLine>Chicago, IL</addrLine>
  <addrLine>60680 USA</addrLine>
 </address>
Note

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

address

<address> contains a postal address, for example of a publisher, an organization, or an individual. «#CONAAD» «#HD24» «#COBICOI»

Module core
Parents model.addressLike model.publicationStmtPart
Attributes Global attributes only
Declaration
element address
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( model.global*, ( ( model.addrPart ), model.global* )+ )
}
Example
 <address>
  <street>via Marsala 24</street>
  <postCode>40126</postCode>
  <name>Bologna</name>
  <name n="I">Italy</name>
 </address>
Example
 <address>
  <addrLine>Computing Center, MC 135</addrLine>
  <addrLine>P.O. Box 6998</addrLine>
  <addrLine>Chicago, IL 60680</addrLine>
  <addrLine>USA</addrLine>
 </address>
Note

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

anchor

<anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. «#TSSAPA» «#SACS»

Module linking
Parents model.global
Attributes Global attributes and those inherited from [att.typed ]
Declaration
element anchor
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.typed.attribute.type,
   att.typed.attribute.subtype,
   empty
}
Example
 <s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s>
 <s>Help me find it.<ptr target="#A234"/>
 </s>
Note

On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.

argument

<argument> A formal list or prose description of the topics addressed by a subdivision of a text. «#DSCO» «#DSDTB»

Module textstructure
Parents opener model.divWrapper model.pLike.front
Attributes Global attributes only
Declaration
element argument
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   (
      model.global*,
      ( head, model.global* )?,
      ( ( model.common ), model.global* )+
   )
}
Example
 <argument>
  <p>Monte Video — Maldonado — Excursion to R Polanco — Lazo and Bolas — Partridges — Absence of Trees — Deer — Capybara, or River Hog — Tucutuco — Molothrus, cuckoo-like habits — Tyrant Flycatcher — Mocking-bird — Carrion Hawks — Tubes formed by Lightning — House struck</p>
 </argument>
Note

Often contains either a list or a paragraph

att

<att> (attribute) contains the name of an attribute appearing within running text. «#TD»

Module tagdocs
Parents model.xmlPhrase
Attributes In addition to global attributes
scheme supplies an identifier for the scheme in which this name is defined.
Status Optional
Datatype data.enumerated
Sample values include:
TEI (this attribute is part of the TEI scheme.) [Default]
DBK (this attribute is part of the Docbook scheme.)
XX (this attribute is part of an unknown scheme.)
Declaration
element att
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute scheme { data.enumerated }?,
   text
}
Example
 <p>The TEI defines four <soCalled>global</soCalled> attributes;
  their names are <att>xml:id</att>, <att>rend</att>,
  <att>xml:lang</att> and <att>n</att>.
  <att scheme="XX">type</att> is not among them.</p>
Note

A namespace prefix may be used in order to specify the scheme as an alternative to specifying it via the scheme attribute: it takes precedence

author

<author> in a bibliographic reference, contains the name of the author(s), personal or corporate, of a work; the primary statement of responsibility for any bibliographic item. «#COBICOR» «#HD21»

Module core
Parents titleStmt model.respLike
Attributes Global attributes only
Declaration
element author
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <author>British Broadcasting Corporation</author>
 <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
Note

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

In the case of a broadcast, use this element for the name of the company or network which broadcasts the program.

authority

<authority> (release authority) supplies the name of a person or other agency responsible for making an electronic file available, other than a publisher or distributor. «#HD24»

Module header
Parents model.publicationStmtPart
Attributes Global attributes only
Declaration
element authority
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq.limited
}
Example
 <authority>John Smith</authority>

availability

<availability> supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, etc. «#HD24»

Module header
Parents model.publicationStmtPart
Attributes In addition to global attributes
status supplies a code identifying the current availability of the text.
Status Optional
Legal values are:
free (the text is freely available.)
unknown (the status of the text is unknown.) [Default]
restricted (the text is not freely available.)
Declaration
element availability
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute status { "free" | "unknown" | "restricted" }?,
   model.pLike+
}
Example
 <availability status="restricted">
  <p>Available for academic research purposes only.</p>
 </availability>
 <availability status="free">
  <p>In the public domain</p>
 </availability>
 <availability status="restricted">
  <p>Available under licence from the publishers.</p>
 </availability>
Example
 <availability status="restricted">
  <p>Disponible uniquement à des fins de recherche et d’enseignement.</p>
 </availability>
 <availability status="free">
  <p>Domaine public</p>
 </availability>
 <availability status="restricted">
  <p>Disponible avec le consentement préalable des éditeurs.</p>
 </availability>
Note

A consistent format should be adopted

back

<back> (back matter) contains any appendixes, etc. following the main part of a text. «#DSBACK» «#DS»

Module textstructure
Parents text
Attributes Global attributes and those inherited from [att.declaring ]
Declaration
element back
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declaring.attribute.decls,
   (
      ( model.frontPart | model.global | model.divWrapper )*,
      (
         ( ( model.divLike ), ( model.global | model.frontPart )* )+
       | ( ( model.div1Like ), ( model.global | model.frontPart )* )+
      )?,
      model.divWrapper.bottom*
   )
}
Example
 <back>
  <div1 type="appendix">
   <head>The Golden Dream or, the Ingenuous Confession</head>
   <p>To shew the Depravity of human Nature</p>
  </div1>
  <div1 type="epistle">
   <head>A letter from the Printer, which he desires may be inserted</head>
   <salute>Sir.</salute>
   <p>I have done with your Copy, so you may return it to the Vatican, if you please</p>
  </div1>
  <div1 type="advert">
   <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr Newbery's at the Bible and Sun in St Paul's Church-yard.</head>
   <list>
    <item n="1">The Christmas Box, Price 1d.</item>
    <item n="2">The History of Giles Gingerbread, 1d.</item>
    <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations, 10 Vol, Pr. bound 1l.</item>
   </list>
  </div1>
  <div1 type="advert">
   <head>
    <hi rend="center">By the KING's Royal Patent,</hi>
    Are sold by J. NEWBERY, at the Bible and Sun in
    St. Paul's Church-Yard.</head>
   <list>
    <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &c. 2s. 6d</item>
    <item n="2">Dr. Hooper's Female Pills, 1s.</item>
   </list>
  </div1>
 </back>
Note

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

bibl

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. «#COBITY» «#HD3» «#CCAS2»

Module core
Parents relatedItem model.biblLike model.msItemPart model.personPart
Attributes Global attributes and those inherited from [att.declarable ]
Declaration
element bibl
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declarable.attribute.default,
   (
      text
    | model.gLikemodel.highlightedmodel.pPart.datamodel.pPart.editmodel.segLikemodel.ptrLikemodel.biblPartmodel.global
   )*
}
Example
 <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
 <bibl>
  <title level="a">The Interesting story of the Children in the Wood</title>.
  In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
  <publisher>OUP</publisher>
  <date>1968</date>.
 </bibl>
Note

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

biblFull

<biblFull> contains a fully-structured bibliographic citation, in which all components of the TEI file description are present. «#COBITY» «#HD3» «#CCAS2»

Module header
Parents model.biblLike
Attributes Global attributes and those inherited from [att.declarable ]
Declaration
element biblFull
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declarable.attribute.default,
   ( macro.fileDescPart, sourceDesc* )
}
Example
 <biblFull>
  <titleStmt>
   <title>The Feminist Companion to Literature in English: women writers from the middle ages to the present</title>
   <author>Blain, Virginia</author>
   <author>Clements, Patricia</author>
   <author>Grundy, Isobel</author>
  </titleStmt>
  <editionStmt>
   <edition>UK edition</edition>
  </editionStmt>
  <extent>1231 pp</extent>
  <publicationStmt>
   <publisher>Yale University Press</publisher>
   <pubPlace>New Haven and London</pubPlace>
   <date>1990</date>
  </publicationStmt>
  <sourceDesc>
   <p>No source: this is an original work</p>
  </sourceDesc>
 </biblFull>

biblScope

<biblScope> (scope of citation) defines the scope of a bibliographic reference, for example as a list of pagenumbers, or a named subdivision of a larger work. «#COBICOI»

Module core
Parents model.imprintPart
Attributes In addition to global attributes
type identifies the type of information conveyed by the element, e.g. pages, volume.

Status Optional
Datatype data.enumerated
Suggested values include:
vol (the element contains a volume number.)
issue (the element contains an issue number, or volume and issue numbers.)
pp (the element contains a page number or page range.)
cap (the element contains a chapter indication (number and/or title))
part (the element identifies a part of a book or collection.)
Declaration
element biblScope
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type { "vol" | "issue" | "pp" | "cap" | "part" | token }?,
   macro.phraseSeq
}
Example
 <biblScope>pp 12–34</biblScope>
 <biblScope type="vol">II</biblScope>
 <biblScope type="pp">12</biblScope>

body

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. «#DS»

Module textstructure
Parents text
Attributes Global attributes and those inherited from [att.declaring ]
Declaration
element body
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declaring.attribute.decls,
   (
      model.global*,
      ( ( model.divWrapper ), ( model.global | model.divWrapper )* )?,
      ( ( model.divGenLike ), ( model.global | model.divGenLike )* )?,
      (
         ( ( model.divLike ), ( model.global | model.divGenLike )* )+
       | ( ( model.div1Like ), ( model.global | model.divGenLike )* )+
       | (
            ( ( model.common ), model.global* )+,
            (
               ( ( model.divLike ), ( model.global | model.divGenLike )* )+
             | ( ( model.div1Like ), ( model.global | model.divGenLike )* )+
            )?
         )
      ),
      ( ( model.divWrapper.bottom ), model.global* )*
   )
}

byline

<byline> contains the primary statement of responsibility given for a work on its title page or at the head or end of the work. «#DSOC» «#DSFRONT»

Module textstructure
Parents opener model.divWrapper model.titlepagePart model.pLike.front
Attributes Global attributes only
Declaration
element byline
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( text | model.gLike | model.phrase | docAuthor | model.global )*
}
Example
 <byline>Written by a CITIZEN who continued all the while in London. Never made publick before.</byline>
Example
 <byline>Written from her own MEMORANDUMS</byline>
Example
 <byline>By George Jones, Political Editor, in Washington</byline>
Example
 <dateline>Zagreb:</dateline>
 <byline>de notre envoyé spécial.</byline>
Example
 <byline>BY <docAuthor>THOMAS PHILIPOTT,</docAuthor>
 Master of Arts,
 (Somtimes)
 Of Clare-Hall in Cambridge.</byline>
Note

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

cRefPattern

<cRefPattern> (defines how to convert a canonical reference into a URI) specifies an expression and replacement pattern for tranforming a canonical reference into a URI. «#HD54M» «#HD54» «#HD54S»

Module header
Parents refsDecl
Attributes In addition to global attributes
matchPattern specifies a regular expression against which the values of cRef attributes can be matched.

Parenthesised groups are used not only for establishing order of precedence and atoms for quantification, but also for creating subpatterns to be referenced by the pat attribute.

Status Required
Datatype data.pattern
Values must be a regular expression according to the W3C XML Schema Language
replacementPattern specifies a replacement pattern which, once subpattern substitution has been performed, provides a URI.

The strings ‘$1’ through ‘$9’ are references to the corresponding group in the regular expression specified by re (counting open parenthesis, left to right). Processors are expected to replace them with whatever matched the corresponding group in the regular expression.

If a digit preceded by a dollar sign is needed in the actual replacement pattern (as opposed to being used as a back reference), the dollar sign must be written as %24.

Status Required
Datatype text
Values Should be the skeleton of a relative or absolute URI, with references to groups in the matchPattern.
Declaration
element cRefPattern
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute matchPattern { data.pattern },
   attribute replacementPattern { text },
   model.pLike*
}
Example
 <cRefPattern
   matchPattern="([1-9A-Za-z]+)\s+([0-9]+):([0-9]+)"
   replacementPattern="#xpath(//div[@type='book'][@n='$1']/div[@type='chap'][@n='$2']/div[@type='verse'][@n='$3'])"/>
Note

The result of the substitution may be either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the cRef attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

catDesc

<catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal textDesc. «#HD55»

Module header
Parents category
Attributes Global attributes only
Declaration
element catDesc
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( text | model.limitedPhrase | model.catDescPart )*
}
Example
 <catDesc>Prose reportage</catDesc>
Example
 <catDesc>
  <textDesc n="novel">
   <channel mode="w">print; part issues</channel>
   <constitution type="single"/>
   <derivation type="original"/>
   <domain type="art"/>
   <factuality type="fiction"/>
   <interaction type="none"/>
   <preparedness type="prepared"/>
   <purpose type="entertaindegree="high"/>
   <purpose type="informdegree="medium"/>
  </textDesc>
 </catDesc>
Example
 <catDesc>
  <textDesc n="novel">
   <channel mode="w">print; part issues</channel>
   <constitution type="single"/>
   <derivation type="original"/>
   <domain type="art"/>
   <factuality type="fiction"/>
   <interaction type="none"/>
   <preparedness type="prepared"/>
   <purpose type="entertaindegree="high"/>
   <purpose type="informdegree="medium"/>
  </textDesc>
 </catDesc>
Example
 <catDesc>
  <textDesc n="novel">
   <channel mode="w">print; part issues</channel>
   <constitution type="single"/>
   <derivation type="original"/>
   <domain type="art"/>
   <factuality type="fiction"/>
   <interaction type="none"/>
   <preparedness type="prepared"/>
   <purpose type="entertaindegree="high"/>
   <purpose type="informdegree="medium"/>
  </textDesc>
 </catDesc>

catRef

<catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. «#HD43»

Module header
Parents textClass
Attributes In addition to global attributes
target identifies the categories concerned
Status Required
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values A series of one or more space-separated pointers (URIs) to <category> elements, typically located within a <taxonomy> element inside a TEI header
scheme identifies the classification scheme within which the set of categories concerned is defined
Status Optional
Datatype data.pointer
Values May supply the identifier of the associated <taxonomy> element.
Declaration
element catRef
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute target { list { data.pointer+ } },
   attribute scheme { data.pointer }?,
   empty
}
Example
 <catRef target="#news #prov #sales2"/>
 <taxonomy>
  <category xml:id="news">
   <catDesc>Newspapers</catDesc>
  </category>
  <category xml:id="prov">
   <catDesc>Provincial</catDesc>
  </category>
  <category xml:id="sales2">
   <catDesc>Low to average annual sales</catDesc>
  </category>
 </taxonomy>
Note

The scheme attribute need be supplied only if more than one taxonomy has been declared

category

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. «#HD55»

Module header
Parents category taxonomy
Attributes Global attributes only
Declaration
element category
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( ( catDesc | model.glossLike ), category* )
}
Example
 <category xml:id="b1">
  <catDesc>Prose reportage</catDesc>
 </category>
Example
 <category xml:id="b2-zh">
  <catDesc>Prose</catDesc>
  <category xml:id="b11-zh">
   <catDesc>reportage</catDesc>
  </category>
  <category xml:id="b12-zh">
   <catDesc>fiction</catDesc>
  </category>
 </category>
Example
 <category xml:id="b2-fr">
  <catDesc>Prose</catDesc>
  <category xml:id="b11-fr">
   <catDesc>reportage</catDesc>
  </category>
  <category xml:id="b12-fr">
   <catDesc>fiction</catDesc>
  </category>
 </category>
Example
 <category xml:id="b2">
  <catDesc>Prose</catDesc>
  <category xml:id="b11">
   <catDesc>reportage</catDesc>
  </category>
  <category xml:id="b12">
   <catDesc>fiction</catDesc>
  </category>
 </category>

cell

<cell> contains one cell of a table. «#FTTAB1»

Module figures
Parents row
Attributes Global attributes and those inherited from [att.tableDecoration ]
Declaration
element cell
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.tableDecoration.attribute.role,
   att.tableDecoration.attribute.rows,
   att.tableDecoration.attribute.cols,
   macro.paraContent
}
Example
 <row>
  <cell role="label">General conduct</cell>
  <cell role="data">Not satisfactory, on account of his great unpunctuality and inattention to duties</cell>
 </row>

change

<change> summarizes a particular change or correction made to a particular version of an electronic text which is shared between several researchers. «#HD6»

Module header
Parents revisionDesc
Attributes In addition to global attributes and those inherited from [att.ascribed ]
date supplies the date of the change in standard form, i.e. yyyy-mm-dd.
Status Mandatory when applicable
Datatype data.temporal.w3c
Values Any string representing a date in any of the formats defined in XML Schema Part 2: Datatypes Second Edition
Declaration
element change
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.ascribed.attribute.who,
   attribute date { data.temporal.w3c }?,
   ( text | model.limitedPhrase | model.inter | model.divPart | model.global )*
}
Example
 <change n="P2.2date="1991-12-21">LB Added examples to section 3</change>
 <change date="1991-11-11">MSM Deleted chapter 10</change>
Example
 <change n="P2.2date="1991-12-21"> Exemples ajoutés à la section 3 </change>
 <change date="1991-11-11"> Suppression du chapitre 10 </change>
Note

Changes should be recorded in a consistent order, for example with the most recent first.

choice

<choice> groups a number of alternative encodings for the same point in a text.

Module core
Parents choice model.pPart.editorial
Attributes Global attributes only
Declaration
element choice
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( model.choicePart | choice )*
}
Example

An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.

 <p>Lastly, That, upon his solemn oath to observe all the above articles, the said man-mountain shall have a daily allowance of meat and drink sufficient for the support of <choice>
   <sic>1724</sic>
   <corr>1728</corr>
  </choice> of our subjects,
  with free access to our royal person, and other marks of our
  <choice>
   <orig>favour</orig>
   <reg>favor</reg>
  </choice>.</p>
Note

Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

Note also that <choice> elements may self-nest.

For a specialized version of <choice> for encoding multiple witnesses of a single work, see section .

cit

<cit> A quotation from some other document, together with a bibliographic reference to its source. «#COHQQ» «#DSGRP» «#DITPEG»

Module core
Parents model.qLike
Attributes Global attributes only
Declaration
element cit
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( model.quoteLike | model.biblLike | model.ptrLike | model.global )+
}
Example
 <cit>
  <quote>and the breath of the whale is frequently attended with such an insupportable smell, as to bring on disorder of the brain.</quote>
  <bibl>Ulloa's South America</bibl>
 </cit>
Note

Must contain a single quote and a single bibliographic reference in either order

classCode

<classCode> contains the classification code used for this text in some standard classification system. «#HD43»

Module header
Parents textClass
Attributes In addition to global attributes
scheme identifies the classification system or taxonomy in use.
Status Required
Datatype data.pointer
Values may point to a local definition, for example in a <taxonomy> element, or more usually to some external location where the scheme is fully defined.
Declaration
element classCode
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute scheme { data.pointer },
   macro.phraseSeq.limited
}
Example
 <classCode scheme="http://www.udc.org">410</classCode>

classDecl

<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. «#HD55» «#HD5»

Module header
Parents model.encodingPart
Attributes Global attributes only
Declaration
element classDecl
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   taxonomy+
}

closer

<closer> groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. «#DSCO» «#DSDTB»

Module textstructure
Parents model.divWrapper.bottom
Attributes Global attributes only
Declaration
element closer
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   (
      text
    | model.gLikesigneddatelinesalutemodel.phrasemodel.global
   )*
}
Example
 <div type="letter">
  <p>perhaps you will favour me with a sight of it when convenient.</p>
  <closer>
   <salute>I remain, &c. &c.</salute>
   <signed>H. Colburn</signed>
  </closer>
 </div>
Example
 <div type="chapter">
  <p>and his heart was going like mad and yes I said yes I will Yes.</p>
  <closer>
   <dateline>
    <name type="place">Trieste-Zürich-Paris,</name>
    <date>1914–1921</date>
   </dateline>
  </closer>
 </div>

code

<code> contains literal code from some formal language such as a programming language

Module tagdocs
Parents model.emphLike
Attributes In addition to global attributes
lang a name identifying the formal language in which the code is expressed
Status Optional
Datatype data.word
Declaration
element code
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute lang { data.word }?,
   text
}

corr

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. «#COEDCOR»

Module core
Parents model.pPart.transcriptional model.choicePart
Attributes Global attributes and those inherited from [att.editLike ]
Declaration
element corr
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.editLike.attribute.cert,
   att.editLike.attribute.resp,
   att.editLike.attribute.evidence,
   macro.paraContent
}
Example

If all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone:

I don't know, Juan. It's so far in the past now — how  <corr>can we</corr> prove or disprove anyone's theories?
Example

It is also possible to identify the individual responsible for the correction, and, using the <choice> and <sic> elements, to provide a correct reading:

I don't know, Juan. It's so far in the past now — how  <choice>
  <sic>we can</sic>
  <corr>can we</corr>
 </choice> prove or
disprove anyone's theories?

creation

<creation> contains information about the creation of a text. «#HD4C» «#HD4»

Module header
Parents profileDesc
Attributes Global attributes only
Declaration
element creation
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq.limited
}
Example
 <creation>
  <date>Before 1987</date>
 </creation>
Example
 <creation>
  <date when="1988-07-10">10 July 1988</date>
 </creation>
Example
 <creation>
  <date>Avant 1987</date>
 </creation>
Example
 <creation>
  <date when="1988-07-10">10 juillet 1988</date>
 </creation>
Example
 <creation>
  <date when="1988-07-10">10 July 1988</date>
 </creation>
Note

Character data and phrase-level elements.

The <creation> element may be used to record details of a text's creation, e.g. the date and place it was composed, if these are of interest; it should not be confused with the <publicationStmt> element, which records date and place of publication.

date

<date> contains a date in any format. «#CONADA» «#HD24» «#HD6» «#COBICOI» «#CCAHSE» «#NDDATE»

Module core
Parents model.dateLike model.publicationStmtPart
Attributes In addition to global attributes and those inherited from [att.datable att.duration att.editLike att.typed ]
calendar indicates the system or calendar to which the date belongs.Example
He was born on  <date calendar="Gregorian">Feb. 22, 1732</date>
(
 <date calendar="Julianwhen="1732-02-22"> Feb. 11, 1731/32, O.S.</date>).
Status Optional
Datatype data.enumerated
Suggested values include:
Gregorian Gregorian calendar
Julian Julian calendar
Islamic Islamic or Muslim (hijri) lunar calendar
Hebrew Hebrew or Jewish lunisolar calendar
Revolutionary French Revolutionary calendar
Iranian Iranian or Persian (Jalaali) solar calendar
Coptic Coptic or Alexandrian calendar
Chinese Chinese lunisolar calendar
Declaration
element date
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.datable.w3c.attribute.period,
   att.datable.w3c.attribute.when,
   att.datable.w3c.attribute.notBefore,
   att.datable.w3c.attribute.notAfter,
   att.datable.w3c.attribute.from,
   att.datable.w3c.attribute.to,
   att.duration.w3c.attribute.dur,
   att.editLike.attribute.cert,
   att.editLike.attribute.resp,
   att.editLike.attribute.evidence,
   att.typed.attribute.type,
   att.typed.attribute.subtype,
   attribute calendar
   {
      "Gregorian"
    | "Julian"
    | "Islamic"
    | "Hebrew"
    | "Revolutionary"
    | "Iranian"
    | "Coptic"
    | "Chinese"
    | token
   }?,
   ( text | model.gLike | model.datePart | model.phrase | model.global )*
}
Example
 <date when="1980-02">early February 1980</date>
Example
Given on the  <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
 <date when="1990-09">September 1990</date>

dateline

<dateline> contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. «#DSCO» «#DSOC»

Module textstructure
Parents closer opener model.divWrapper
Attributes Global attributes only
Declaration
element dateline
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <dateline>Walden, this 29. of August 1592</dateline>
Example
 <div type="chapter">
  <p>and his heart was going like mad and yes I said yes I will Yes.</p>
  <closer>
   <dateline>
    <name type="place">Trieste-Zürich-Paris,</name>
    <date>1914–1921</date>
   </dateline>
  </closer>
 </div>

del

<del> (deletion) contains a letter, word or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, annotator, or corrector. «#COEDADD»

Module core
Parents model.pPart.transcriptional
Attributes Global attributes and those inherited from [att.editLike att.authorialIntervention ]
Declaration
element del
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.editLike.attribute.cert,
   att.editLike.attribute.resp,
   att.editLike.attribute.evidence,
   att.authorialIntervention.attribute.hand,
   att.authorialIntervention.attribute.status,
   att.authorialIntervention.attribute.type,
   macro.paraContent
}
Example
 <l>
  <del rend="overtyped">Mein</del> Frisch
 <del rend="overstriketype="primary">schwebt</del> weht der Wind</l>
Note

Cf. <gap>.

Degrees of uncertainty over what can still be read may be indicated by use of the <certainty> element (see ).

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

The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <del> tag should not be used. Rather, the <gap> tag should be employed to signal that text cannot be transcribed, with the value of the reason attribute giving the cause for the omission from the transcription as deletion. If it is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence. See further sections and, for the close association of the <del> tag with the <gap>, <damage>, <unclear> and <supplied> elements (the latter three tags available when using the additional tagset for transcription of primary sources), .

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

distributor

<distributor> supplies the name of a person or other agency responsible for the distribution of a text. «#HD24»

Module header
Parents model.biblPart model.publicationStmtPart
Attributes Global attributes only
Declaration
element distributor
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <distributor>Oxford Text Archive</distributor>
 <distributor>Redwood and Burn Ltd</distributor>

div

<div> (text division) contains a subdivision of the front, body, or back of a text. «#DSDIV» «#DSDIV1»

Module textstructure
Parents div model.divLike
Attributes Global attributes and those inherited from [att.divLike att.declaring ]
Declaration
element div
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.divLike.attribute.type,
   att.divLike.attribute.org,
   att.divLike.attribute.sample,
   att.divLike.attribute.part,
   att.declaring.attribute.decls,
   (
      ( model.divWrapper | model.global )*,
      (
         (
            ( ( ( div | divGen ), model.global* )+ )
          | (
               ( ( model.common ), model.global* )+,
               ( ( div | divGen ), model.global* )*
            )
         ),
         ( ( model.divWrapper | model.divWrapper.bottom ), model.global* )*
      )?
   )
}
Example
 <body>
  <div type="part">
   <head>Fallacies of Authority</head>
   <p>The subject of which is Authority in various shapes, and the object, to repress all exercise of the reasoning faculty.</p>
   <div n="1type="chapter">
    <head>The Nature of Authority</head>
    <p>With reference to any proposed measures having for their object the greatest happiness of the greatest number....</p>
    <div n="1.1type="section">
     <head>Analysis of Authority</head>
     <p>What on any given occasion is the legitimate weight or influence to be attached to authority ...</p>
    </div>
    <div n="1.2type="section">
     <head>Appeal to Authority, in What Cases Fallacious.</head>
     <p>Reference to authority is open to the charge of fallacy when...</p>
    </div>
   </div>
  </div>
 </body>
Note

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

divGen

<divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. «#CONOIX»

Module core
Parents div model.frontPart model.divGenLike
Attributes In addition to global attributes
type specifies what type of generated text division (e.g. index, table of contents, etc.) is to appear.

Valid values are application-dependent; those shown are of obvious utility in document production, but are by no means exhaustive.

Status Optional
Datatype data.enumerated
Sample values include:
index (an index is to be generated and inserted at this point.)
toc (a table of contents)
figlist (a list of figures)
tablist (a list of tables)
Declaration
element divGen
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type { data.enumerated }?,
   model.divWrapper*
}
Example

One use for this element is to allow document preparation software to generate an index and insert it in the appropriate place in the output. The example below assumes that the indexName attribute on <index> elements in the text has been used to specify index entries for the two generated indexes, named NAMES and THINGS:

 <back>
  <div1 type="backmat">
   <head>Bibliography</head>
   <listBibl>
    <bibl/>
   </listBibl>
  </div1>
  <div1 type="backmat">
   <head>Indices</head>
   <divGen n="Index Nominumtype="NAMES"/>
   <divGen n="Index Rerumtype="THINGS"/>
  </div1>
 </back>
Example

Another use for <divGen> is to specify the location of an automatically produced table of contents:

 <front>
  <divGen type="toc"/>
  <div>
   <head>Preface</head>
   <p>...</p>
  </div>
 </front>
Note

This element is intended primarily for use in document production or manipulation, rather than in the transcription of pre-existing materials; it makes it easier to specify the location of indices, tables of contents, etc., to be generated by text preparation or word processing software.

docAuthor

<docAuthor> (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline). «#DSTITL»

Module textstructure
Parents byline model.titlepagePart model.divWrapper model.pLike.front
Attributes Global attributes only
Declaration
element docAuthor
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Note

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

docDate

<docDate> (document date) contains the date of a document, as given (usually) on a title page. «#DSTITL»

Module textstructure
Parents docImprint model.titlepagePart model.divWrapper model.pLike.front
Attributes In addition to global attributes
value gives the value of the date in a standard form, generally YYYY-MM-DD.

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

Status Optional
Datatype data.temporal.w3c
Values a date in one of the formats specified in XML Schema Part 2: Datatypes Second Edition
Declaration
element docDate
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute value { data.temporal.w3c }?,
   macro.phraseSeq
}
Example
 <docImprint>Oxford, Clarendon Press, <docDate>1987</docDate>
 </docImprint>
Note

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

docEdition

<docEdition> (document edition) contains an edition statement as presented on a title page of a document. «#DSTITL»

Module textstructure
Parents model.titlepagePart model.pLike.front
Attributes Global attributes only
Declaration
element docEdition
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.paraContent
}
Example
 <docEdition>The Third edition Corrected</docEdition>
Note

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

docImprint

<docImprint> (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. «#DSTITL»

Module textstructure
Parents model.titlepagePart model.pLike.front
Attributes Global attributes only
Declaration
element docImprint
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   (
      text
    | model.gLikemodel.phrasepubPlacedocDatepublishermodel.global
   )*
}
Example
 <docImprint>Oxford, Clarendon Press, 1987</docImprint>
Imprints may be somewhat more complex:
 <docImprint>
  <pubPlace>London</pubPlace>
 Printed for <name>E. Nutt</name>,
 at
 <pubPlace>Royal Exchange</pubPlace>;
 <name>J. Roberts</name> in
 <pubPlace>wick-Lane</pubPlace>;
 <name>A. Dodd</name> without
 <pubPlace>Temple-Bar</pubPlace>;
 and <name>J. Graves</name> in
 <pubPlace>St. James's-street.</pubPlace>
  <date>1722.</date>
 </docImprint>
Note

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

docTitle

<docTitle> (document title) contains the title of a document, including all its constituents, as given on a title page. «#DSTITL»

Module textstructure
Parents model.titlepagePart model.pLike.front
Attributes Global attributes only
Declaration
element docTitle
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( model.global*, ( titlePart, model.global* )+ )
}
Example
 <docTitle>
  <titlePart type="main">The DUNCIAD, VARIOURVM. </titlePart>
  <titlePart type="sub">WITH THE PROLEGOMENA of SCRIBLERUS. </titlePart>
 </docTitle>

edition

<edition> (Edition) describes the particularities of one edition of a text. «#HD22»

Module header
Parents editionStmt model.biblPart
Attributes Global attributes only
Declaration
element edition
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <edition>First edition <date>Oct 1990</date>
 </edition>
 <edition n="S2">Students' edition</edition>
Example
 <edition>Première édition<date>Octobre 1990</date>
 </edition>
 <edition n="S2">Manuel de l'étudiant</edition>

editionStmt

<editionStmt> (edition statement) groups information relating to one edition of a text. «#HD22» «#HD2»

Module header
Parents macro.fileDescPart
Attributes Global attributes only
Declaration
element editionStmt
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( model.pLike+ | ( edition, respStmt* ) )
}
Example
 <editionStmt>
  <edition n="S2">Students' edition</edition>
  <respStmt>
   <resp>Adapted by</resp>
   <name>Elizabeth Kirk</name>
  </respStmt>
 </editionStmt>
Example
 <editionStmt>
  <p>First edition, <date>Michaelmas Term, 1991.</date>
  </p>
 </editionStmt>
Example
 <editionStmt>
  <edition n="S2">Manuel de l'étudiant</edition>
  <respStmt>
   <resp>adaptée par</resp>
   <name>Elizabeth Kirk</name>
  </respStmt>
 </editionStmt>
Example
 <editionStmt>
  <p>Première édition, <date>Michaelmas Term, 1991.</date>
  </p>
 </editionStmt>
Example
 <editionStmt>
  <p>First edition, <date>Michaelmas Term, 1991.</date>
  </p>
 </editionStmt>

editor

<editor> secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. «#COBICOR»

Module core
Parents titleStmt model.respLike
Attributes In addition to global attributes
role specifies the nature of the intellectual responsibility
Status Optional
Datatype data.enumerated
Values semi-open list (examples might include: translator, editor, compiler, illustrator, etc.)
Declaration
element editor
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute role { data.enumerated }?,
   macro.phraseSeq
}
Example
 <editor>Eric Johnson</editor>
 <editor role="illustrator">John Tenniel</editor>
Note

A consistent format should be adopted

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

editorialDecl

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. «#HD53» «#HD5» «#CCAS2»

Module header
Parents model.encodingPart
Attributes Global attributes and those inherited from [att.declarable ]
Declaration
element editorialDecl
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declarable.attribute.default,
   ( model.pLike+ | model.editorialDeclPart+ )
}
Example
 <editorialDecl>
  <normalization>
   <p>All words converted to Modern American spelling using Websters 9th Collegiate dictionary</p>
  </normalization>
  <quotation marks="allform="std">
   <p>All opening quotation marks converted to “ all closing quotation marks converted to &cdq;.</p>
  </quotation>
 </editorialDecl>
Example
 <editorialDecl>
  <normalization>
   <p>Tous les mots ont été convertis dans l’orthographe de l’américain moderne selon la 9e édition du Websters Collegiate dictionary</p>
  </normalization>
  <quotation marks="allform="std">
   <p>Toutes les marques ouvrantes de citation sont représentées par référence à l’entité ODQ “ ; toutes les marques fermantes de citation sont représentées par référence à l’entité CDQ &cdq;.</p>
  </quotation>
 </editorialDecl>

eg

<eg> contains any kind of illustrative example. «#TDTAG» «#TDATT»

Module tagdocs
Parents model.common model.egLike
Attributes Global attributes only
Declaration
element eg
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   text
}
Example
 <p>The <gi>term</gi> element is declared using the following syntax:
  <eg><![CDATA[<!ELEMENT term (%phrase.content;)>]]</eg>
 </p>
Note

If the example contains material in XML markup, either it must be enclosed within a CDATA marked section, or character entity references must be used to represent the markup delimiters. If the example contains well-formed XML, it should be marked using the more specific <egXML> element.

emph

<emph> (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. «#COHQHE» «#COHQH»

Module core
Parents model.emphLike
Attributes Global attributes only
Declaration
element emph
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.paraContent
}
Example
You took the car and did  <emph>what</emph>?!!
Example
 <q>What it all comes to is this,</q> he said.
 <q>
  <emph>What does Christopher Robin do in the morning nowadays?</emph>
 </q>

encodingDesc

<encodingDesc> (Encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. «#HD5» «#HD11»

Module header
Parents model.headerPart
Attributes Global attributes only
Declaration
element encodingDesc
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( ( model.encodingPart | model.pLike )+ )
}

epigraph

<epigraph> (epigraph) contains a quotation, anonymous or attributed, appearing at the start of a section or chapter, or on a title page. «#DSCO» «#DSDTB» «#DSTITL»

Module textstructure
Parents opener model.divWrapper model.titlepagePart model.pLike.front
Attributes Global attributes only
Declaration
element epigraph
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.componentSeq
}
Example
 <epigraph xml:lang="la">
  <cit>
   <bibl>Lucret.</bibl>
   <quote>
    <l part="F">petere inde coronam,</l>
    <l>Vnde prius nulli velarint tempora Musae.</l>
   </quote>
  </cit>
 </epigraph>

expan

<expan> (expansion) contains the expansion of an abbreviation. «#CONAAB»

Module core
Parents model.pPart.editorial model.choicePart
Attributes Global attributes and those inherited from [att.editLike ]
Declaration
element expan
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.editLike.attribute.cert,
   att.editLike.attribute.resp,
   att.editLike.attribute.evidence,
   macro.phraseSeq
}
Example
The address is Southmoor  <choice>
  <expan>Road</expan>
  <abbr>Rd</abbr>
 </choice>
Note

The <expan> tag is not required; if appropriate, the encoder may expand abbreviations in the source text silently, without tagging them. If this is done, the TEI header should so indicate.

extent

<extent> describes the approximate size of a text as stored on some carrier medium, whether digital or non-digital, specified in any convenient units. «#HD23» «#HD2» «#COBICOI»

Module header
Parents macro.fileDescPart model.biblPart
Attributes Global attributes only
Declaration
element extent
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <extent>3200 sentences</extent>
 <extent>between 10 and 20 Mb</extent>
 <extent>ten 3.5 inch high density diskettes</extent>
Example
 <extent>3 200 phrases</extent>
 <extent>entre 10 et 20 Mo</extent>
 <extent>10 disquettes haute densité 3.5"</extent>

figDesc

<figDesc> (Description of Figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. «#FTGRA»

Module figures
Parents figure
Attributes Global attributes only
Declaration
element figDesc
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.limitedContent
}
Note

This element is intended for use as an alternative to the content of its parent <figure> element; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

figure

<figure> contains a block containing graphics, illustrations, or figures. «#FT»

Module figures
Parents figure model.inter model.titlepagePart model.common
Attributes Global attributes and those inherited from [att.placement ]
Declaration
element figure
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.placement.attribute.place,
   ( model.pLike | model.global | figure | figDesc | model.graphicLike | head )*
}
Example
 <figure>
  <head>Figure One: The View from the Bridge</head>
  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a series of buoys strung out between them.</figDesc>
  <graphic url="http://www.somewhere.eu/fig1.pngscale="0.5"/>
 </figure>

fileDesc

<fileDesc> (File Description) contains a full bibliographic description of an electronic file. «#HD2» «#HD11»

Module header
Parents teiHeader
Attributes Global attributes only
Declaration
element fileDesc
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( macro.fileDescPart, sourceDesc+ )
}
Note

The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elswhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

foreign

<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. «#COHQHF»

Module core
Parents model.emphLike
Attributes Global attributes only
Declaration
element foreign
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
This is heathen Greek to you still? Your  <foreign xml:lang="la">lapis philosophicus</foreign>?
Note

The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere its value should be a language code from RFC 3066 or its successor that represents the language in question. It is strongly recommended that the xml:lang attribute be consistently specified on all <foreign> elements.

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

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

formula

<formula> contains a mathematical or other formula. «#FTFOR»

Module figures
Parents model.graphicLike
Attributes In addition to global attributes
notation supplies the name of a previously defined notation used for the content of the element.
Status Optional
Datatype data.code
Values The name of a formal notation previously declared in the document type declaration.
Declaration
element formula
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute notation { data.code }?,
   text
}
Note

The content model for this element is specified by the parameter entity formulaContent, the default value of which is #PCDATA.

front

<front> (front matter) contains any prefatory matter (headers, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. «#DSTITL» «#DS»

Module textstructure
Parents text
Attributes Global attributes and those inherited from [att.declaring ]
Declaration
element front
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declaring.attribute.decls,
   (
      ( model.frontPart | model.pLike.front | model.global )*,
      (
         (
            (
               ( model.div1Like ),
               ( model.frontPart | model.div1Like | model.global )*
            )
          | (
               ( model.divLike ),
               ( model.frontPart | model.divLike | model.global )*
            )
         )?
      )
   )
}
Example
 <front>
  <epigraph>
   <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla pendere, et cum illi pueri dicerent: <q xml:lang="grc">Sibylla ti weleis</q>; respondebat
    illa: <q xml:lang="grc">apowanein welo.</q>
   </quote>
  </epigraph>
  <div type="dedication">
   <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>
   </p>
  </div>
 </front>
Example
 <front>
  <div type="dedication">
   <p>To our three selves</p>
  </div>
  <div type="preface">
   <head>Author's Note</head>
   <p>All the characters in this book are purely imaginary, and if the author has used names that may suggest a reference to living persons she has done so inadvertently. ...</p>
  </div>
 </front>

funder

<funder> (Funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. «#HD21»

Module header
Parents titleStmt
Attributes Global attributes only
Declaration
element funder
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq.limited
}
Example
 <funder>The National Endowment for the Humanities, an independent federal agency</funder>
 <funder>Directorate General XIII of the Commission of the European Communities</funder>
 <funder>The Andrew W. Mellon Foundation</funder>
 <funder>The Social Sciences and Humanities Research Council of Canada</funder>
Example
 <funder>The National Endowment for the Humanities, agence fédérale indépendante</funder>
 <funder>Direction générale XIII de la Commission des Communautés européennes</funder>
 <funder>Fondation Andrew W. Mellon</funder>
 <funder>The Social Sciences and Humanities Research Council of Canada</funder>
Note

Funders provide financial support for a project; they are distinct from sponsors, who provide intellectual support and authority.

gap

<gap> (omitted material) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible or inaudible. «#COEDADD»

Module core
Parents model.global.edit
Attributes In addition to global attributes and those inherited from [att.editLike att.measured ]
reason gives the reason for omission. Sample values include sampling, illegible, inaudible, irrelevant, cancelled, cancelled and illegible.
Status Optional
Datatype 1–∞ occurrences of data.wordseparated by whitespace
Values any short indication of the reason for the omission.
hand in the case of text omitted from the transcription because of deliberate deletion by an identifiable hand, signifies the hand which made the deletion.
Status Optional
Datatype data.pointer
Values must be one of the hand identifiers declared in the document header (see section ).
agent In the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.
Status Optional
Datatype data.enumerated
Sample values include:
rubbing (damage results from rubbing of the leaf edges)
mildew (damage results from mildew on the leaf surface)
smoke (damage results from smoke)
Declaration
element gap
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.editLike.attribute.cert,
   att.editLike.attribute.resp,
   att.editLike.attribute.evidence,
   att.measured.attribute.unit,
   att.measured.attribute.extent,
   att.measured.attribute.commodity,
   att.measured.attribute.scope,
   attribute reason { list { data.word+ } }?,
   attribute hand { data.pointer }?,
   attribute agent { data.enumerated }?,
   macro.glossSeq
}
Note

The <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section for discussion of which element is appropriate for which circumstance.

gi

<gi> (generic identifier) contains the name (generic identifier) of an element. «#TD» «#TDTAG»

Module tagdocs
Parents model.xmlPhrase
Attributes In addition to global attributes
scheme supplies the name of the scheme in which this name is defined.
Status Optional
Datatype data.enumerated
Sample values include:
TEI (this element is part of the TEI scheme.) [Default]
DBK (this element is part of the Docbook scheme.)
XX (this element is part of an unknown scheme.)
Declaration
element gi
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute scheme { data.enumerated }?,
   text
}
Example
 <p>The <gi>xhtml:li</gi> element is roughly analogous to the
  <gi>item</gi> element, as is the <gi scheme="DBK">listItem</gi> element.</p>

This example shows the use of both a namespace prefix and the schema attribute as alternative ways of indicating that the gi in question is not a TEI element name: in practice only one method should be adopted.

gloss

<gloss> identifies a phrase or word used to provide a gloss or definition for some other word or phrase. «#COHQU»

Module core
Parents macro.glossSeq model.emphLike model.glossLike
Attributes In addition to global attributes and those inherited from [att.declaring att.translatable ]
target identifies the associated term element by an absolute or relative URI reference
Status Optional
Datatype data.pointer
Values should be a valid URI reference that resolves to a <term> element
cRef identifies the associated term element using a canonical reference from a scheme defined in a refsDecl element in the TEI header

The <refsDecl> to use may be indicated with the decls attribute.

Status Optional
Datatype data.pointer
Values the result of applying the algorithm for the resolution of canonical references (described in section ) should be a valid URI reference that resolves to a <term> element
Declaration
element gloss
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declaring.attribute.decls,
   att.translatable.attribute.version,
   ( attribute target { data.pointer }? | attribute cRef { data.pointer }? ),
   macro.phraseSeq.limited
}
Example
We may define  <term xml:id="tdpvrend="sc">discoursal point of view</term>
as
 <gloss target="#tdpv">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Note

The target and cRef attributes are mutually exclusive.

graphic

<graphic> indicates the location of an inline graphic, illustration, or figure. «#COGR»

Module core
Parents model.graphicLike model.titlepagePart
Attributes In addition to global attributes
width The display width of the image
Status Mandatory when applicable
Datatype data.outputMeasurement
height The display height of the image
Status Mandatory when applicable
Datatype data.outputMeasurement
scale A scale factor to be applied to the image to make it the desired display size
Status Mandatory when applicable
Datatype data.numeric
url The target URL
Status Mandatory when applicable
Datatype data.pointer
Values The name of a URL which provides the image.
mimeType The MIME type
Status Mandatory when applicable
Datatype data.word
Values The MIME type to be used for the object when it is decoded
Declaration
element graphic
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute width { data.outputMeasurement }?,
   attribute height { data.outputMeasurement }?,
   attribute scale { data.numeric }?,
   attribute url { data.pointer }?,
   attribute mimeType { data.word }?,
   empty
}
Example
 <figure>
  <graphic url="fig1.png"/>
  <head>Figure One: The View from the Bridge</head>
  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a series of buoys strung out between them.</figDesc>
 </figure>

group

<group> contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc. «#DS» «#DSGRP» «#CCDEF»

Module textstructure
Parents group text
Attributes Global attributes and those inherited from [att.declaring ]
Declaration
element group
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declaring.attribute.decls,
   (
      ( model.divWrapper | model.global )*,
      ( ( text | group ), ( text | group | model.global )* ),
      model.divWrapper.bottom*
   )
}

head

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. «#COLI» «#DSDTB»

Module core
Parents argument figure table model.divWrapper model.pLike.front
Attributes In addition to global attributes
type categorizes the heading in any way meaningful to the encoder.
Status Optional
Datatype data.enumerated
Values A set of user-defined keywords may be employed. Their significance should be documented in the header.
Declaration
element head
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type { data.enumerated }?,
   macro.paraContent
}
Example

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

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

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

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

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

hi

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. «#COHQHE» «#COHQH»

Module core
Parents model.hiLike
Attributes Global attributes only
Declaration
element hi
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.paraContent
}
Example
 <hi rend="gothic">And this Indenture further witnesseth</hi>
that the said
 <hi rend="italic">Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...

ident

<ident> contains an identifier or name for an object of some kind in a formal language

Module tagdocs
Parents model.emphLike
Attributes Global attributes and those inherited from [att.typed ]
Declaration
element ident
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.typed.attribute.type,
   att.typed.attribute.subtype,
   text
}
Example
 <ident type="namespace">http://www.tei-c.org/ns/Examples</ident>
Note

In running prose, this element may be used for any kind of identifier in any formal language.

idno

<idno> (identifying number) supplies any standard or non-standard number used to identify a bibliographic item. «#HD24» «#HD26» «#COBICOI»

Module header
Parents seriesStmt model.biblPart model.publicationStmtPart
Attributes In addition to global attributes
type categorizes the number, for example as an ISBN or other standard series.
Status Optional
Datatype data.enumerated
Values A name or abbreviation indicating what type of identifying number is given (e.g. ISBN, LCCN).
Declaration
element idno
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type { data.enumerated }?,
   text
}
Example
 <idno type="ISSN">0143-3385</idno>
 <idno type="OTA">116</idno>

imprint

<imprint> groups information relating to the publication or distribution of a bibliographic item. «#COBICOI»

Module core
Parents
Attributes Global attributes only
Declaration
element imprint
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( ( ( model.imprintPart ) | ( model.dateLike ) ), model.global* )+
}
Example
 <imprint>
  <pubPlace>Oxford</pubPlace>
  <publisher>Clarendon Press</publisher>
  <date>1987</date>
 </imprint>

index

<index> (index entry) marks a location to be indexed for whatever purpose. «#CONOIX»

Module core
Parents index model.global.meta
Attributes In addition to global attributes and those inherited from [att.spanning ]
indexName supplies a name to specify which index (of several) the index entry belongs to.

This attribute makes it possible to create multiple indexes for a text.

Status Optional
Datatype data.name
Values an application-specific name, consisting of Unicode characters only.
Declaration
element index
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.spanning.attribute.spanTo,
   attribute indexName { data.name }?,
   ( term, index? )*
}
Example
David's other principal backer, Josiah ha-Kohen  <index indexName="NAMES">
  <term>Josiah ha-Kohen b. Azarya</term>
 </index> b. Azarya, son of one of the last gaons of Sura

 <index indexName="PLACES">
  <term>Sura</term>
 </index> was David's own first cousin.

interp

<interp> (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. «#AISP»

Module analysis
Parents interpGrp model.global.meta
Attributes Global attributes and those inherited from [att.interpLike ]
Declaration
element interp
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.interpLike.attribute.resp,
   att.interpLike.attribute.type,
   att.interpLike.attribute.inst,
   macro.phraseSeq.limited
}
Example
 <interp type="structuralunit">aftermath</interp>

interpGrp

<interpGrp> (interpretation group) collects together a set of related interpretations which share responsibility or type. «#AISP»

Module analysis
Parents model.global.meta
Attributes Global attributes and those inherited from [att.interpLike ]
Declaration
element interpGrp
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.interpLike.attribute.resp,
   att.interpLike.attribute.type,
   att.interpLike.attribute.inst,
   interp+
}
Example
 <interpGrp resp="#TMAtype="structuralunit">
  <interp xml:id="I1">introduction</interp>
  <interp xml:id="I2">conflict</interp>
  <interp xml:id="I3">climax</interp>
  <interp xml:id="I4">revenge</interp>
  <interp xml:id="I5">reconciliation</interp>
  <interp xml:id="I6">aftermath</interp>
 </interpGrp>
 <bibl xml:id="TMA"/>
Note

Any number of <interp> elements.

item

<item> contains one component of a list. «#COLI» «#HD6»

Module core
Parents list
Attributes Global attributes only
Declaration
element item
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.specialPara
}
Example
 <list type="ordered">
  <head>Here begin the chapter headings of Book IV</head>
  <item n="4.1">The death of Queen Clotild.</item>
  <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
  <item n="4.3">The wives and children of Lothar.</item>
  <item n="4.4">The Counts of the Bretons.</item>
  <item n="4.5">Saint Gall the Bishop.</item>
  <item n="4.6">The priest Cato.</item>
  <item>...</item>
 </list>
Note

May contain simple prose or a sequence of chunks.

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

keywords

<keywords> contains a list of keywords or phrases identifying the topic or nature of a text. «#HD43»

Module header
Parents textClass
Attributes In addition to global attributes
scheme identifies the controlled vocabulary within which the set of keywords concerned is defined.
Status Required
Datatype data.pointer
Values Usually this will indicate an external website or other location where the scheme is documented.
Declaration
element keywords
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute scheme { data.pointer },
   ( term+ | list )
}
Example
 <keywords scheme="http://classificationweb.net">
  <list>
   <item>Babbage, Charles</item>
   <item>Mathematicians - Great Britain - Biography</item>
  </list>
 </keywords>
Example
 <keywords scheme="http://classificationweb.net">
  <list>
   <item>Babbage, Charles</item>
   <item>Mathématiciens - Grande Bretagne - Biographie</item>
  </list>
 </keywords>

l

<l> (verse line) contains a single, possibly incomplete, line of verse. «#COVE» «#CODV» «#DRPAL»

Module core
Parents model.divPart model.lLike
Attributes In addition to global attributes
part specifies whether or not the line is metrically complete.

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

Status Mandatory when applicable
Legal values are:
Y (the line is metrically incomplete)
N (either the line is complete, or no claim is made as to its completeness) [Default]
I (the initial part of an incomplete line)
M (a medial part of an incomplete line)
F (the final part of an incomplete line)
Declaration
element l
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute part { "Y" | "N" | "I" | "M" | "F" }?,
   macro.paraContent
}
Example
 <l met="-/-/-/-/-/part="Y"/>

label

<label> contains the label associated with an item in a list; in glossaries, marks the term being defined. «#COLI»

Module core
Parents list model.inter model.common model.labelLike
Attributes Global attributes only
Declaration
element label
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example

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

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

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

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

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

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

langUsage

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects etc. represented within a text. «#HD41» «#HD4» «#CCAS2»

Module header
Parents model.profileDescPart
Attributes Global attributes and those inherited from [att.declarable ]
Declaration
element langUsage
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declarable.attribute.default,
   language+
}
Example
 <langUsage>
  <language ident="fr-CAusage="60">Québecois</language>
  <language ident="en-CAusage="20">Canadian business English</language>
  <language ident="en-GBusage="20">British English</language>
 </langUsage>
Example
 <langUsage>
  <language ident="fr-CAusage="60">Québécois</language>
  <language ident="en-CAusage="20">Anglais canadien des affaires</language>
  <language ident="en-GBusage="20">Anglais britannique</language>
 </langUsage>

language

<language> characterizes a single language or sublanguage used within a text. «#HD41»

Module header
Parents langUsage
Attributes In addition to global attributes
ident Supplies a language code constructed as defined in RFC 3066 (or its successor) which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute.
Status Required
Datatype data.language
usage specifies the approximate percentage (by volume) of the text which uses this language.
Status Optional
Datatype xsd:nonNegativeInteger { maxInclusive = "100" }
Values a whole number between 0 and 100
Declaration
element language
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute ident { data.language },
   attribute usage { xsd:nonNegativeInteger { maxInclusive = "100" } }?,
   macro.phraseSeq.limited
}
Example
 <langUsage xml:lang="en-US">
  <language ident="en-USusage="75">modern American English</language>
  <language ident="i-az-Arabusage="20">Azerbaijani in Arabic script</language>
  <language ident="x-lapusage="05">Pig Latin</language>
 </langUsage>
Example
 <langUsage xml:lang="fr">
  <language ident="en-USusage="75">Anglais américain moderne</language>
  <language ident="i-az-Arabusage="20">Azerbaïdjanais en écriture arabe</language>
  <language ident="x-lapusage="05">Latin de cuisine</language>
 </langUsage>
Note

Particularly for sublanguages, an informal prose characterization should be supplied as content for the element.

lb

<lb> (line break) marks the start of a new (typographic) line in some edition or version of a text. «#CORS5» «#DRPAL»

Module core
Parents model.milestoneLike
Attributes In addition to global attributes
ed indicates the edition or version in which the line break is located at this point
Status Recommended
Datatype data.code
Values Any string of characters; usually a siglum conventionally used for the edition.
Declaration
element lb
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute ed { data.code }?,
   empty
}
Note

On this element, the global n attribute indicates the number or other value associated with the line which follows the point of insertion of this <lb>. Encoders should adopt a clear and consistent policy as to whether the numbers associated with line breaks relate to the physical sequence number of the line within the page, or to some aspect of the logical structure of the text. By convention, <lb> elements should appear at the start of the line to which they refer.

The <lb> tag is intended for making typographic line breaks in prose. It should be carefully distinguished from the <l> element, used to mark lines of verse.

lg

<lg> (line group) contains a group of verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. «#COVE» «#CODV» «#DRPAL»

Module core
Parents lg sp model.divPart
Attributes Global attributes and those inherited from [att.divLike ]
Declaration
element lg
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.divLike.attribute.type,
   att.divLike.attribute.org,
   att.divLike.attribute.sample,
   att.divLike.attribute.part,
   (
      ( model.divWrapper | model.global )*,
      ( model.lLike | lg ),
      ( model.lLike | lg | model.global )*,
      ( ( model.divWrapper.bottom ), model.global* )*
   )
}
Example
 <lg type="free">
  <l>Let me be my own fool</l>
  <l>of my own making, the sum of it</l>
 </lg>
 <lg type="free">
  <l>is equivocal.</l>
  <l>One says of the drunken farmer:</l>
 </lg>
 <lg type="free">
  <l>leave him lay off it. And this is</l>
  <l>the explanation.</l>
 </lg>
Note

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

list

<list> contains any sequence of items organized as a list. «#COLI»

Module core
Parents keywords revisionDesc model.listLike
Attributes In addition to global attributes
type describes the form of the list.

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

Status Optional
Datatype data.enumerated
Suggested values include:
ordered (list items are numbered or lettered.)
bulleted (list items are marked with a bullet or other typographic device.)
simple (list items are not numbered or bulleted.) [Default]
gloss (each list item glosses some term or concept, which is given by a label element preceding the list item.)
Declaration
element list
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type { "ordered" | "bulleted" | "simple" | "gloss" | token }?,
   (
      ( ( model.divWrapper ) | ( model.global ) )*,
      (
         ( item, model.global* )+
       | ( ( label, model.global*, item, model.global* )+ )
      ),
      ( ( model.divWrapper.bottom ), model.global* )*
   )
}
Example
 <list type="ordered">
  <item>a butcher</item>
  <item>a baker</item>
  <item>a candlestick maker, with <list type="bullets">
    <item>rings on his fingers</item>
    <item>bells on his toes</item>
   </list>
  </item>
 </list>
Example

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

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

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

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

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

listBibl

<listBibl> (citation list) contains a list of bibliographic citations of any kind. «#COBITY» «#HD3» «#CCAS2»

Module core
Parents sourceDesc model.listLike model.msItemPart
Attributes Global attributes and those inherited from [att.declarable ]
Declaration
element listBibl
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declarable.attribute.default,
   (
      ( ( model.divWrapper ) | ( model.global ) )*,
      ( ( model.biblLike ), model.global* )+,
      ( ( model.divWrapper.bottom ), model.global* )*
   )
}
Example
 <listBibl>
  <head>Works consulted</head>
  <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
  <biblStruct>
   <analytic>
    <title>The Interesting story of the Children in the Wood</title>
   </analytic>
   <monogr>
    <title>The Penny Histories</title>
    <author>Victor E Neuberg</author>
    <imprint>
     <publisher>OUP</publisher>
     <date>1968</date>
    </imprint>
   </monogr>
  </biblStruct>
 </listBibl>

measureGrp

<measureGrp> contains a group of dimensional specifications which relate to the same object, for example the height and width of a manuscript page «#msdim»

Module core
Parents model.measureLike
Attributes Global attributes and those inherited from [att.measured att.typed ]
Declaration
element measureGrp
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.measured.attribute.unit,
   att.measured.attribute.extent,
   att.measured.attribute.commodity,
   att.measured.attribute.scope,
   att.typed.attribute.type,
   att.typed.attribute.subtype,
   ( model.measureLike | text )*
}
Example
 <measureGrp type="leavesunit="mm">
  <height scope="range">157-160</height>
  <width extent="105"/>
 </measureGrp>
 <measureGrp type="ruledAreaunit="mm">
  <height scope="mostextent="90"/>
  <width scope="mostextent="48"/>
 </measureGrp>
 <measureGrp type="boxunit="in">
  <height extent="12"/>
  <width extent="10"/>
  <depth extent="6"/>
 </measureGrp>

mentioned

<mentioned> marks words or phrases mentioned, not used. «#COHQU»

Module core
Parents model.emphLike
Attributes Global attributes only
Declaration
element mentioned
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
There is thus a striking accentual difference between a verbal form like  <mentioned xml:id="X234xml:lang="el">eluthemen</mentioned>
 <gloss target="#X234">we were released,</gloss> accented on
the second syllable of the word, and its
participial derivative
 <mentioned xml:id="X235xml:lang="el">lutheis</mentioned>
 <gloss target="#X235">released,</gloss> accented on the last.

milestone

<milestone> marks a boundary point separating any kind of section of a text, as indicated by changes in a standard reference system, where the section is not represented by a structural element. «#CORS5»

Module core
Parents model.milestoneLike
Attributes In addition to global attributes
ed indicates the edition or version to which the milestone applies.
Status Recommended
Datatype data.code
Values Any string of characters; usually a siglum conventionally used for the edition.
unit provides a conventional name for the kind of section changing at this milestone.

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

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

Status Required
Datatype data.enumerated
Suggested values include:
page (physical page breaks (synonymous with the pb element).)
column (column breaks.)
line (line breaks (synonymous with the lb element).)
book (any units termed book, liber, etc.)
poem (individual poems in a collection.)
canto (cantos or other major sections of a poem.)
stanza (stanzas within a poem, book, or canto.)
act (acts within a play.)
scene (scenes within a play or act.)
section (sections of any kind.)
absent (passages not present in the reference edition.)
Declaration
element milestone
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute ed { data.code }?,
   attribute unit
   {
      "page"
    | "column"
    | "line"
    | "book"
    | "poem"
    | "canto"
    | "stanza"
    | "act"
    | "scene"
    | "section"
    | "absent"
    | token
   },
   empty
}
Example
 <milestone n="23ed="Launit="Dreissiger"/>
...

 <milestone n="24ed="AVunit="verse"/>
...
Note

For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme (e.g. chapter heads, poem numbers or titles, or speaker attributions in verse drama).

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

name

<name> (name, proper noun) contains a proper noun or noun phrase. «#CONARS»

Module core
Parents model.nameLike.agent
Attributes In addition to global attributes and those inherited from [att.naming ]
type indicates the type of the object which is being named by the phrase.
Status Recommended
Datatype data.enumerated
Values Values such as person, place, institution, product, acronym.
Declaration
element name
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.naming.attribute.key,
   att.naming.attribute.ref,
   att.naming.attribute.nymRef,
   attribute type { data.enumerated }?,
   macro.phraseSeq
}
Note

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

namespace

<namespace> supplies the formal name of the namespace to which the elements documented by its children belong. «#HD57»

Module header
Parents
Attributes In addition to global attributes
name the full formal name of the namespace concerned.
Status Required
Datatype data.namespace
Declaration
element namespace
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute name { data.namespace },
   tagUsage+
}
Example
 <namespace name="http://www.tei-c.org/ns/1.0">
  <tagUsage
    gi="hi"
    occurs="28"
    withId="2"
    render="#it">
Used only to mark English words italicised in the copy text </tagUsage>
 </namespace>
Example
 <namespace name="http://www.tei-c.org/ns/1.0">
  <tagUsage
    gi="hi"
    occurs="28"
    withId="2"
    render="#it">
Utilisé seulement pour marquer les mots anglais en italiques dans le texte de la copie. </tagUsage>
 </namespace>

note

<note> contains a note or annotation. «#CONONO» «#HD27» «#COBICON» «#DITPNO»

Module core
Parents model.noteLike
Attributes In addition to global attributes and those inherited from [att.placement ]
type describes the type of note.
Status Optional
Datatype data.enumerated
Values Values can be taken from any convenient typology of annotation suitable to the work in hand; e.g. annotation, gloss, citation, digression, preliminary, temporary
resp indicates who is responsible for the annotation: author, editor, translator, etc.

For specialized types of editorial annotation (e.g. for marking corrections, normalizations, cruxes, etc.), see chapter .

Status Required when applicable
Datatype data.pointer
Values a pointer to one of the identifiers declared in the document header, associated with a person asserted as responsible for some aspect of the text's creation, transcription, editing, encoding, or annotation
anchored indicates whether the copy text shows the exact place of reference for the note.

In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

Status Optional
Datatype data.enumerated
target indicates the point (or points) of attachment for a note, or the beginning of the span to which the note is attached.

If target and targetEnd are to be used to indicate where notes attach to the text, then elements at the appropriate locations (<anchor> elements if necessary) must be given xml:id values to be pointed at.

Status Required when applicable
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values reference to the xml:ids of element(s) which begin at the location in question (e.g. the xml:id of an <anchor> element).
targetEnd points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.

Status Required when applicable
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values reference to the xml:id(s) of element(s) which end at the location(s) in question, or to an empty element at the point in question.
Declaration
element note
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.placement.attribute.place,
   attribute type { data.enumerated }?,
   attribute resp { data.pointer }?,
   attribute anchored { data.enumerated }?,
   attribute target { list { data.pointer+ } }?,
   attribute targetEnd { list { data.pointer+ } }?,
   macro.specialPara
}
Example
And yet it is not only in the great line of Italian renaissance art, but even in the painterly  <note type="gloss">
  <term xml:lang="de">Malerisch</term>.
  This word has, in the German, two distinct meanings, one objective, a
  quality residing in the object, the other subjective, a mode of
  apprehension and creation. To avoid confusion, they have been
  distinguished in English as <mentioned>picturesque</mentioned> and
  <mentioned>painterly</mentioned> respectively. (Tr.)</note>
style of the Dutch genre painters of the seventeenth century that
drapery has this psychological significance.
Note
The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century,  <note n="126anchored="true"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note>
is well known from Geniza documents published by Jacob Mann.
However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.

notesStmt

<notesStmt> (Notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. «#HD27» «#HD2»

Module header
Parents macro.fileDescPart
Attributes Global attributes only
Declaration
element notesStmt
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   model.noteLike+
}
Example
 <notesStmt>
  <note>Historical commentary provided by Mark Cohen</note>
  <note>OCR scanning done at University of Toronto</note>
 </notesStmt>
Example
 <notesStmt>
  <note>Commentaire historique de Mark Cohen.</note>
  <note>Numérisation OCR faite à l’Université de Toronto.</note>
 </notesStmt>
Note

Information of different kinds should not be grouped together into the same note.

num

<num> (number) contains a number, written in any form. «#CONANU»

Module core
Parents model.measureLike
Attributes In addition to global attributes
type indicates the type of numeric value.

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

Status Optional
Datatype data.enumerated
Suggested values include:
cardinal (absolute number, e.g. 21, 21.5)
ordinal (ordinal number, e.g. 21st)
fraction (fraction, e.g. one half or three-quarters)
percentage (a percentage)
value supplies the value of the number in standard form.

The standard form used is defined by the TEI datatype data.numeric.

Status Optional
Datatype data.numeric
Values a numeric value.
Declaration
element num
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type
   {
      "cardinal" | "ordinal" | "fraction" | "percentage" | token
   }?,
   attribute value { data.numeric }?,
   macro.phraseSeq
}
Example
 <p>I reached <num type="cardinalvalue="21">twenty-one</num>
 on my <num type="ordinalvalue="21">twenty-first</num> birthday...
 light travels at <num value="10E10">10<hi rend="sup">10</hi>
  </num> cm per second.</p>
Note

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

opener

<opener> groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. «#DSCO» «#DSDTB»

Module textstructure
Parents model.divWrapper
Attributes Global attributes only
Declaration
element opener
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   (
      text
    | model.gLikemodel.phraseargumentbylinedatelineepigraphsalutesignedmodel.global
   )*
}
Example
 <opener>
  <dateline>Walden, this 29. of August 1592</dateline>
 </opener>
Example
 <opener>
  <dateline>
   <name type="place">Great Marlborough Street</name>
   <date>November 11, 1848</date>
  </dateline>
  <salute>My dear Sir,</salute>
 </opener>
 <p>I am sorry to say that absence from town and other circumstances have prevented me from earlier enquiring...</p>

orig

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. «#COEDREG» «#TC»

Module core
Parents model.pPart.transcriptional model.choicePart
Attributes Global attributes only
Declaration
element orig
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.paraContent
}
Example

If all that is desired is to call attention to the original version in the copy text, <orig> may be used alone:

 <l>But this will be a <orig>meere</orig> confusion</l>
 <l>And hardly shall we all be <orig>vnderstoode</orig>
 </l>
Example

More usually, an <orig> will be combined with a regularized form within a <choice> element:

 <l>But this will be a <choice>
   <orig>meere</orig>
   <reg>mere</reg>
  </choice> confusion</l>
 <l>And hardly shall we all be <choice>
   <orig>vnderstoode</orig>
   <reg>understood</reg>
  </choice>
 </l>

[Note: Kyd, Spanish Tragedy, (1592) Kv]

p

<p> (paragraph) marks paragraphs in prose. «#COPA» «#DRPAL»

Module core
Parents model.pLike model.divPart
Attributes Global attributes only
Declaration
element p
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.paraContent
}
Example
 <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said.
 <q>What have you done?</q>
 </p>
 <p>
  <q>I have now arranged that you can be married a second time,</q> replied Thjostolf.</p>
 <p>
  <q>Then you must mean that Thorvald is dead,</q> she said.</p>
 <p>
  <q>Yes,</q> said Thjostolf.
  <q>And now you must think up some plan for me.</q>
 </p>
Note

In some contexts, the paragraph may have a specialized meaning, e.g. in the tag set for dictionaries, <p> is used to enclose any running text, and thus does not imply text set off as is conventionally done in running prose.

pb

<pb> (page break) marks the boundary between one page of a text and the next in a standard reference system. «#CORS5»

Module core
Parents model.milestoneLike
Attributes In addition to global attributes
ed indicates the edition or version in which the page break is located at this point
Status Recommended
Datatype data.code
Values Any string of characters; usually a siglum conventionally used for the edition.
Declaration
element pb
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute ed { data.code }?,
   empty
}
Note

On this element, the global n attribute indicates the number or other value associated with the page which follows the point of insertion of this <pb>. Encoders should adopt a clear and consistent policy as to whether the numbers associated with page breaks relate to the physical sequence number of the page or the page number or signature printed on it. By convention, <pb> elements should appear at the start of the page to which they refer.

principal

<principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. «#HD21»

Module header
Parents titleStmt
Attributes Global attributes only
Declaration
element principal
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq.limited
}
Example
 <principal>Gary Taylor</principal>

profileDesc

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. «#HD4» «#HD11»

Module header
Parents model.headerPart
Attributes Global attributes only
Declaration
element profileDesc
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( creation?, model.profileDescPart* )
}
Example
 <profileDesc>
  <langUsage>
   <language ident="fr">French</language>
  </langUsage>
  <textDesc n="novel">
   <channel mode="w">print; part issues</channel>
   <constitution type="single"/>
   <derivation type="original"/>
   <domain type="art"/>
   <factuality type="fiction"/>
   <interaction type="none"/>
   <preparedness type="prepared"/>
   <purpose type="entertaindegree="high"/>
   <purpose type="informdegree="medium"/>
  </textDesc>
  <settingDesc>
   <setting>
    <name>Paris, France</name>
    <time>Late 19th century</time>
   </setting>
  </settingDesc>
 </profileDesc>
Example
 <profileDesc>
  <langUsage>
   <language ident="fr">Français</language>
  </langUsage>
  <textDesc n="novel">
   <channel mode="w">imprimé ; livraisons</channel>
   <constitution type="single"/>
   <derivation type="original"/>
   <domain type="art"/>
   <factuality type="fiction"/>
   <interaction type="none"/>
   <preparedness type="prepared"/>
   <purpose type="entertaindegree="high"/>
   <purpose type="informdegree="medium"/>
  </textDesc>
  <settingDesc>
   <setting>
    <name>Paris, France</name>
    <time>Fin du 19e siècle</time>
   </setting>
  </settingDesc>
 </profileDesc>

projectDesc

<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. «#HD51» «#HD5» «#CCAS2»

Module header
Parents model.encodingPart
Attributes Global attributes and those inherited from [att.declarable ]
Declaration
element projectDesc
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declarable.attribute.default,
   model.pLike+
}
Example
 <projectDesc>
  <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p>
 </projectDesc>
Example
 <projectDesc>
  <p>Textes rassemblés pour utilisation lors du Claremont Shakespeare Clinic, juin 1990</p>
 </projectDesc>

ptr

<ptr> defines a pointer to another location. «#COXR» «#SAPT»

Module core
Parents relatedItem model.ptrLike
Attributes In addition to global attributes and those inherited from [att.pointing att.declaring ]
target specifies the destination of the pointer by supplying one or more URI References
Status Required
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values One or more syntactically valid URI references, separated by white space. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.
cRef specifies the destination of the pointer by supplying a canonical reference from a scheme defined in a refsDecl element in the TEI header

The <refsDecl> to use may be indicated with the decls attribute.

Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.

Status Optional
Datatype 1–∞ occurrences of data.wordseparated by whitespace
Values the result of applying the algorithm for the resolution of canonical references (described in section ) should be a valid URI reference to the intended target
Declaration
element ptr
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.pointing.attribute.type,
   att.pointing.attribute.evaluate,
   att.declaring.attribute.decls,
   (
      attribute target { list { data.pointer+ } }
    | attribute cRef { list { data.word+ } }?
   ),
   empty
}
Example
 <ptr target="#p143 #p144"/>
 <ptr target="http://www.tei-c.org"/>
Note

The target and cRef attributes are mutually exclusive.

pubPlace

<pubPlace> contains the name of the place where a bibliographic item was published. «#COBICOI»

Module core
Parents docImprint model.imprintPart model.publicationStmtPart
Attributes Global attributes and those inherited from [att.naming ]
Declaration
element pubPlace
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.naming.attribute.key,
   att.naming.attribute.ref,
   att.naming.attribute.nymRef,
   macro.phraseSeq
}

publicationStmt

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. «#HD24» «#HD2»

Module header
Parents macro.fileDescPart
Attributes Global attributes only
Declaration
element publicationStmt
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( model.pLike+ | model.publicationStmtPart+ )
}
Example
 <publicationStmt>
  <publisher>C. Muquardt</publisher>
  <pubPlace>Bruxelles & Leipzig</pubPlace>
  <date when="1846"/>
 </publicationStmt>
Example
 <publicationStmt>
  <publisher>Chadwyck Healey</publisher>
  <pubPlace>Cambridge</pubPlace>
  <availability>
   <p>Available under licence only</p>
  </availability>
  <date when="1992">1992</date>
 </publicationStmt>
Example
 <publicationStmt>
  <publisher>Chadwyck Healey</publisher>
  <pubPlace>Cambridge</pubPlace>
  <availability>
   <p>Disponible uniquement sur autorisation</p>
  </availability>
  <date when="1992">1992</date>
 </publicationStmt>
Example
 <publicationStmt>
  <publisher>Chadwyck Healey</publisher>
  <pubPlace>Cambridge</pubPlace>
  <availability>
   <p>Available under licence only</p>
  </availability>
  <date when="1992">1992</date>
 </publicationStmt>
Note

Although not enforced by the schemas, it is a requirement for TEI conformance that information about publication place, address, identifier, availability, and date be given in that order, following the name of the publisher, distributor, or authority concerned

publisher

<publisher> provides the name of the organization responsible for the publication or distribution of a bibliographic item. «#COBICOI» «#HD24»

Module core
Parents docImprint model.imprintPart model.publicationStmtPart
Attributes Global attributes only
Declaration
element publisher
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <imprint>
  <pubPlace>Oxford</pubPlace>
  <publisher>Clarendon Press</publisher>
  <date>1987</date>
 </imprint>
Note

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

q

<q> (quoted speech, thought, or writing) contains material which is marked as (ostensibly) quoted from elsewhere; in narrative, this element is used to mark direct or indirect speech; in dictionaries, it may be used to mark real or contrived examples of usage; in manuscript descriptions or other metadata, to mark extracts quoted from the source being documented. «#COHQQ»

Module core
Parents model.qLike
Attributes In addition to global attributes and those inherited from [att.ascribed ]
type may be used to indicate whether the quoted matter is spoken or thought, or to characterize it more finely.
Status Required when applicable
Datatype data.enumerated
Sample values include:
spoken representation of direct speech, usually marked by quotation marks.
thought representation of thought, e.g. internal monologue.
written quotation from a written source.
Declaration
element q
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.ascribed.attribute.who,
   attribute type { data.enumerated }?,
   macro.specialPara
}
Example
And so, as Tiny Tim observed,  <q type="speech">God Bless Us, Every One!</q>

quote

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. «#COHQQ» «#DSGRP»

Module core
Parents model.qLike model.quoteLike
Attributes Global attributes only
Declaration
element quote
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.specialPara
}
Example
Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized in his slogan,  <quote>You shall know a word by the company it keeps</quote>
 <ref>(Firth, 1957)</ref>
Note

If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element.

ref

<ref> defines a reference to another location, possibly modified by additional text or comment. «#COXR» «#SAPT»

Module core
Parents relatedItem model.ptrLike
Attributes In addition to global attributes and those inherited from [att.pointing att.declaring ]
target specifies the destination of the reference by supplying one or more URI References
Status Optional
Datatype 1–∞ occurrences of data.pointerseparated by whitespace
Values One or more syntactically valid URI references, separated by white space. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.
cRef specifies the destination of the reference by supplying a canonical reference from a scheme defined in a refsDecl element in the TEI header

The <refsDecl> to use may be indicated with the decls attribute.

Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ref> element.

Status Optional
Datatype 1–∞ occurrences of data.wordseparated by whitespace
Values the result of applying the algorithm for the resolution of canonical references (described in section ) should be a valid URI reference to the intended target
Declaration
element ref
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.pointing.attribute.type,
   att.pointing.attribute.evaluate,
   att.declaring.attribute.decls,
   (
      attribute target { list { data.pointer+ } }?
    | attribute cRef { list { data.word+ } }?
   ),
   macro.paraContent
}
Example
 <ref
   target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">
See especially the second sentence</ref>
See also
 <ref>s.v. <term>locution</term>
 </ref>.>
Note

The target and cRef attributes are mutually exclusive.

refState

<refState> specifies one component of a canonical reference defined by the milestone method. «#HD54M» «#HD54»

Module header
Parents refsDecl
Attributes In addition to global attributes
ed indicates which edition or version the milestone applies to.

If ed is not specified, then any milestone tag with an appropriate unit attribute will be selected.

Status Optional
Datatype data.code
Values Any string of characters; usually a siglum conventionally used for the edition.
unit indicates what kind of state is changing at this milestone.
Status Required
Datatype data.enumerated
Suggested values include:
page (page breaks in the reference edition.)
column (column breaks.)
line (line breaks.)
book (any units termed book, liber, etc.)
poem (individual poems in a collection.)
canto (cantos or other major sections of a poem.)
stanza (stanzas within a poem, book, or canto.)
act (acts within a play.)
scene (scenes within a play or act.)
section (sections of any kind.)
absent (passages not present in the reference edition.)
length specifies the fixed length of the reference component.

When constructing a reference, if the reference component found is of numeric type, the length is made up by inserting leading zeros; if it is not, by inserting trailing blanks. In either case, reference components are truncated if necessary at the right hand side.

When seeking a reference, the length indicates the number of characters which should be compared. Values longer than this will be regarded as matching, if they start correctly.

Status Optional
Datatype data.count
Values Should be a positive integer; if no value is provided, the length is unlimited and goes to the next delimiter or to the end of the value.
delim supplies a delimiting string following the reference component.
Status Optional
Datatype text
Values If a single space is used it is interpreted as whitespace.
Declaration
element refState
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute ed { data.code }?,
   attribute unit
   {
      "page"
    | "column"
    | "line"
    | "book"
    | "poem"
    | "canto"
    | "stanza"
    | "act"
    | "scene"
    | "section"
    | "absent"
    | token
   },
   attribute length { data.count }?,
   attribute delim { text }?,
   empty
}
Example
 <refState unit="bookdelim=":"/>
 <refState unit="linelength="4"/>

refsDecl

<refsDecl> (references declaration) specifies how canonical references are constructed for this text. «#HD54M» «#HD5» «#HD54»

Module header
Parents model.encodingPart
Attributes In addition to global attributes and those inherited from [att.declarable ]
doctype identifies the document type within which this reference declaration is used.
Status Optional
Datatype data.name
Values must be the name of a document type
Declaration
element refsDecl
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declarable.attribute.default,
   attribute doctype { data.name }?,
   ( model.pLike+ | cRefPattern+ | refState+ )
}
Example
 <refsDecl>
  <cRefPattern
    matchPattern="([A-Za-z0-9]+) ([0-9]+):([0-9]+)"
    replacementPattern="#xpath(//body/div[@n='$1']/div[$2]/div3[$3])"/>

 </refsDecl>

This example is a formal representation for the referencing scheme described informally in the following example.

Example
 <refsDecl>
  <p>References are made up by concatenating the value for the <att>n</att> attribute on the
   highest level <gi>div</gi> element, followed by a space, followed by the sequential number
   of the next level <gi>div</gi> followed by a colon follwed by the sequential number of the
   next (and lowest) level <gi>div</gi>.</p>
 </refsDecl>
Example
 <refsDecl>
  <cRefPattern
    matchPattern="([A-Za-z0-9]+) ([0-9]+):([0-9]+)"
    replacementPattern="#xpath(//body/div[@n='$1']/div[$2]/div3[$3])"/>

 </refsDecl>

Cet exemple est la représentation formelle du système de reférences décrit en prose suivie dans l'exemple suivant.

Example
 <refsDecl>
  <p>Les références sont rendues par concaténation des éléments suivants : la valeur de l'attribut <att>n</att> de l'élément <gi>div</gi> de plus haut niveau, que l'on fait suivre d'un espace, puis du numéro séquentiel de l'élément <gi>div</gi> suivant, suivi de deux points, et enfin du numéro séquentiel de l'élément <gi>div</gi> suivant (du niveau le plus bas).</p>
 </refsDecl>
Example
 <refsDecl>
  <p>References are made up by concatenating the value for the <att>n</att> attribute on the highest level <gi>div</gi>
   element, followed by a space, followed by the sequential
   number of the next level <gi>div</gi> followed by a colon
   follwed by the sequential number of the next (and lowest)
   level <gi>div</gi>.</p>
 </refsDecl>

reg

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. «#COEDREG» «#TC»

Module core
Parents model.pPart.transcriptional model.choicePart
Attributes Global attributes and those inherited from [att.editLike ]
Declaration
element reg
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.editLike.attribute.cert,
   att.editLike.attribute.resp,
   att.editLike.attribute.evidence,
   macro.paraContent
}
Example

If all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone:

 <q>Please <reg>knock</reg> if an <reg>answer</reg>
  is <reg>required</reg>
 </q>
Example

It is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings:

 <q>Please <choice>
   <reg>knock</reg>
   <orig>cnk</orig>
  </choice> if an
  <choice>
   <reg>answer</reg>
   <orig>nsr</orig>
  </choice> is
  <choice>
   <reg>required</reg>
   <orig>reqd</orig>
  </choice>
 </q>

relatedItem

<relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it.

Module core
Parents model.biblPart
Attributes Global attributes and those inherited from [att.typed ]
Declaration
element relatedItem
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.typed.attribute.type,
   att.typed.attribute.subtype,
   ( bibl | ref | ptr )
}

rendition

<rendition> (rendition) supplies information about the intended rendition of one or more elements. «#HD57»

Module header
Parents
Attributes In addition to global attributes
mimeType supplies a MIME type for the content of this element.
Status Optional
Declaration
element rendition
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute mimeType { text }?,
   macro.limitedContent
}
Note

The present release of these Guidelines does not specify the content of this element in any further detail. It may be used to hold a description of the default rendition to be associated with the specified element, expressed in running prose, or in some more formal language such as CSS.

resp

<resp> contains a phrase describing the nature of a person's intellectual responsibility. «#COBICOR» «#HD21» «#HD22» «#HD26»

Module core
Parents respStmt
Attributes Global attributes only
Declaration
element resp
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq.limited
}
Example
 <respStmt>
  <resp>compiler</resp>
  <name>Edward Child</name>
 </respStmt>

respStmt

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. «#COBICOR» «#HD21» «#HD22» «#HD26»

Module core
Parents editionStmt seriesStmt titleStmt model.respLike model.recordingPart
Attributes Global attributes only
Declaration
element respStmt
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) )
}
Example
 <respStmt>
  <resp>transcribed from original ms</resp>
  <persName>Claus Huitfeldt</persName>
 </respStmt>
Example
 <respStmt>
  <resp>converted to SGML encoding</resp>
  <name>Alan Morrison</name>
 </respStmt>

revisionDesc

<revisionDesc> (revision description) summarizes the revision history for a file. «#HD6» «#HD11»

Module header
Parents teiHeader
Attributes Global attributes only
Declaration
element revisionDesc
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( list | change+ )
}
Example
 <revisionDesc>
  <change date="1991-11-11"> EMB deleted chapter 10 </change>
 </revisionDesc>
Example
 <revisionDesc>
  <change date="1991-11-11">Chapitre 10 supprimé par EMB</change>
 </revisionDesc>
Note

Record changes with most recent changes at the top of the list.

row

<row> contains one row of a table. «#FTTAB1»

Module figures
Parents table
Attributes Global attributes and those inherited from [att.tableDecoration ]
Declaration
element row
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.tableDecoration.attribute.role,
   att.tableDecoration.attribute.rows,
   att.tableDecoration.attribute.cols,
   ( ( cell | table ), model.global* )+
}
Example
 <row role="data">
  <cell role="label">Classics</cell>
  <cell>Idle listless and unimproving</cell>
 </row>

rs

<rs> (referencing string) contains a general purpose name or referring string. «#NDPER» «#CONARS»

Module core
Parents model.nameLike
Attributes In addition to global attributes and those inherited from [att.naming ]
type indicates more specifically the object referred to by the referencing string. Values might include person, place, ship, element etc.
Status Mandatory when applicable
Datatype data.enumerated
Values Any string of characters.
Declaration
element rs
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.naming.attribute.key,
   att.naming.attribute.ref,
   att.naming.attribute.nymRef,
   attribute type { data.enumerated }?,
   macro.phraseSeq
}
Example
 <q>My dear <rs type="person">Mr. Bennet</rs>, </q>
said
 <rs type="person">his lady</rs> to him one day,

 <q>have you heard that <rs type="place">Netherfield Park</rs> is let at last?</q>

s

<s> (s-unit) contains a sentence-like division of a text. «#AILC» «#TSSASE»

Module analysis
Parents model.segLike
Attributes Global attributes and those inherited from [att.segLike ]
Declaration
element s
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.segLike.attribute.type,
   att.segLike.attribute.function,
   att.segLike.attribute.part,
   macro.phraseSeq
}
Example
 <s>When are you leaving?</s>
 <s>Tomorrow.</s>
Note

May contain character data, phrase-level and segmentation class elements, other than <s>.

The <s> element may be used to mark orthographic sentences, or any other segmentation of a text, provided that the segmentation is end-to-end, complete, and non-nesting. For other kinds of segmentation, the <seg> element should be used.

salute

<salute> (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc. «#DSCO» «#DSOC»

Module textstructure
Parents closer opener model.divWrapper
Attributes Global attributes only
Declaration
element salute
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <salute>To all courteous mindes, that will voutchsafe the readinge.</salute>

samplingDecl

<samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection. «#HD52» «#HD5» «#CCAS2»

Module header
Parents model.encodingPart
Attributes Global attributes and those inherited from [att.declarable ]
Declaration
element samplingDecl
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declarable.attribute.default,
   model.pLike+
}
Note

This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest.

seg

<seg> (arbitrary segment) contains any arbitrary phrase-level unit of text (including other seg elements). «#SASE» «#VESE» «#DRPAL»

Module linking
Parents model.blockLike model.segLike model.choicePart
Attributes In addition to global attributes and those inherited from [att.segLike ]
subtype provides a sub-categorization of the segment marked.

The subtype attribute may be used to provide any classification for the <seg> elements tagged in a text suitable for the type given.

Status Optional
Datatype data.word
Values any string of characters.
Declaration
element seg
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.segLike.attribute.type,
   att.segLike.attribute.function,
   att.segLike.attribute.part,
   attribute subtype { data.word }?,
   macro.paraContent
}
Example
 <seg>When are you leaving?</seg>
 <seg>Tomorrow.</seg>
Example
 <s>
  <seg rend="capstype="partail_typographic-line">So father's only</seg>
 glory was the ballfield.
 </s>
Example
 <seg type="preamble">
  <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>,
   was a king in Frankish country.</seg>
  <seg>Sinfiotli was the eldest of his sons ...</seg>
  <seg>Borghild, Sigmund's wife, had a brother ...</seg>
 </seg>
Note

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

seriesStmt

<seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. «#HD26» «#HD2»

Module header
Parents macro.fileDescPart
Attributes Global attributes only
Declaration
element seriesStmt
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( model.pLike+ | ( title+, ( idno | respStmt )* ) )
}
Example
 <seriesStmt>
  <title>Machine-Readable Texts for the Study of Indian Literature</title>
  <respStmt>
   <resp>ed. by</resp>
   <name>Jan Gonda</name>
  </respStmt>
  <idno type="vol">1.2</idno>
  <idno type="ISSN">0 345 6789</idno>
 </seriesStmt>
Example
 <seriesStmt>
  <title>Textes électroniques pour l’étude de la littérature indienne</title>
  <respStmt>
   <resp>éd. par</resp>
   <name>Jan Gonda</name>
  </respStmt>
  <idno type="vol">1.2</idno>
  <idno type="ISSN">0345-6789</idno>
 </seriesStmt>

sic

<sic> contains text reproduced although apparently incorrect or inaccurate. «#COEDCOR»

Module core
Parents model.pPart.transcriptional model.choicePart
Attributes Global attributes only
Declaration
element sic
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.paraContent
}
Example
for his nose was as sharp as a pen, and  <sic>a Table</sic> of green fields.
Example

If all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone:

I don't know, Juan. It's so far in the past now — how  <sic>we can</sic> prove or disprove anyone's theories?
Example

It is also possible, using the <choice> and <corr> elements, to provide a correct reading and to identify the individual responsible for the correction:

I don't know, Juan. It's so far in the past now — how  <choice>
  <sic>we can</sic>
  <corr>can we</corr>
 </choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as a pen, and  <choice>
  <sic>a Table</sic>
  <corr>a' babbld</corr>
 </choice> of green fields.

signed

<signed> (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. «#DSCO» «#DSOC»

Module textstructure
Parents closer opener model.divWrapper.bottom
Attributes Global attributes only
Declaration
element signed
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <signed>Thine to command <name>Humph. Moseley</name>
 </signed>

soCalled

<soCalled> (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. «#COHQQ»

Module core
Parents model.emphLike
Attributes Global attributes only
Declaration
element soCalled
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
To edge his way along the crowded paths of life, warning all human sympathy to keep its distance, was what the knowing ones call  <soCalled>nuts</soCalled> to Scrooge.

sourceDesc

<sourceDesc> supplies a description of the source text(s) from which an electronic text was derived or generated. «#HD3»

Module header
Parents biblFull fileDesc
Attributes Global attributes and those inherited from [att.declarable ]
Declaration
element sourceDesc
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declarable.attribute.default,
   ( model.pLike+ | ( listBibl ) | ( model.biblLike | model.sourceDescPart )+ )
}
Example
 <sourceDesc>
  <p>No source: created in machine-readable form.</p>
 </sourceDesc>
Example
 <sourceDesc>
  <p>Sans source : créé sous forme électronique.</p>
 </sourceDesc>

sp

<sp> (speech) An individual speech in a performance text, or a passage presented as such in a prose or verse text. «#CODR» «#CODV» «#DRSP»

Module core
Parents model.divPart
Attributes Global attributes and those inherited from [att.ascribed ]
Declaration
element sp
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.ascribed.attribute.who,
   (
      model.global*,
      ( speaker, model.global* )?,
      (
         ( model.lLike | lg | model.pLike | model.blockLike | model.stageLike ),
         model.global*
      )+
   )
}
Example
 <sp>
  <speaker>The reverend Doctor Opimiam</speaker>
  <p>I do not think I have named a single unpresentable fish.</p>
 </sp>
 <sp>
  <speaker>Mr Gryll</speaker>
  <p>Bream, Doctor: there is not much to be said for bream.</p>
 </sp>
 <sp>
  <speaker>The Reverend Doctor Opimiam</speaker>
  <p>On the contrary, sir, I think there is much to be said for him. In the first place....</p>
  <p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I will forbear...</p>
 </sp>
Note

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

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

speaker

<speaker> A specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. «#CODR»

Module core
Parents sp
Attributes Global attributes only
Declaration
element speaker
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <sp who="#ni #rsa">
  <speaker>Nancy and Robert</speaker>
  <stage type="delivery">(speaking simultaneously)</stage>
  <p>The future? ...</p>
 </sp>
 <list type="speakers">
  <item xml:id="ni"/>
  <item xml:id="rsa"/>
 </list>
Note

This element is used to mark a speaker attribution as it appears in a dramatic text; the who attribute is used to point to another element which provides information about a speaker. Either or both may be used.

sponsor

<sponsor> specifies the name of a sponsoring organization or institution. «#HD21»

Module header
Parents titleStmt
Attributes Global attributes only
Declaration
element sponsor
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq.limited
}
Example
 <sponsor>Association for Computers and the Humanities</sponsor>
 <sponsor>Association for Computational Linguistics</sponsor>
 <sponsor>Association for Literary and Linguistic Computing</sponsor>
Note

Sponsors give their intellectual authority to a project; they are to be distinguished from funders, who provide the funding but do not necessarily take intellectual responsibility.

stage

<stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. «#CODR» «#CODV» «#DRSTA»

Module core
Parents model.stageLike
Attributes In addition to global attributes
type indicates the kind of stage direction.
Status Recommended
Datatype data.enumerated
Suggested values include:
setting (describes a setting.)
entrance (describes an entrance.)
exit (describes an exit.)
business (describes stage business.)
novelistic (is a narrative, motivating stage direction.)
delivery (describes how a character speaks.)
modifier (gives some detail about a character.)
location (describes a location.)
mixed (more than one of the above)
Declaration
element stage
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type
   {
      "setting"
    | "entrance"
    | "exit"
    | "business"
    | "novelistic"
    | "delivery"
    | "modifier"
    | "location"
    | "mixed"
    | token
   }?,
   macro.specialPara
}
Example
 <stage type="setting">A curtain being drawn.</stage>
 <stage type="setting">Music</stage>
 <stage type="entrance">Enter Husband as being thrown off his horse.</stage>
 <stage type="exit">Exit pursued by a bear.</stage>
 <stage type="business">He quickly takes the stone out.</stage>
 <stage type="delivery">To Lussurioso.</stage>
 <stage type="novelistic">Having had enough, and embarrassed for the family.</stage>
 <stage type="modifier">Disguised as Ansaldo.</stage>
 <stage type="location">At a window.</stage>
 <stage rend="inlinetype="delivery">Aside.</stage>

table

<table> contains text displayed in tabular form, in rows and columns. «#FTTAB1»

Module figures
Parents row model.inter model.common
Attributes In addition to global attributes
rows indicates the number of rows in the table.

Rows should be presented from top to bottom.

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

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

Status Optional
Datatype data.count
Values If no number is supplied, an application must calculate the number of columns.
Declaration
element table
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute rows { data.count }?,
   attribute cols { data.count }?,
   ( ( head | model.global )*, ( row, model.global* )+ )
}
Example
 <table rows="4cols="4">
  <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
  <row role="label">
   <cell role="data"/>
   <cell role="data">Dossing Cribs or Lodging Houses</cell>
   <cell role="data">Beds</cell>
   <cell role="data">Needys or Nightly Lodgers</cell>
  </row>
  <row role="data">
   <cell role="label">Bury St Edmund's</cell>
   <cell role="data">5</cell>
   <cell role="data">8</cell>
   <cell role="data">128</cell>
  </row>
  <row role="data">
   <cell role="label">Thetford</cell>
   <cell role="data">3</cell>
   <cell role="data">6</cell>
   <cell role="data">36</cell>
  </row>
  <row role="data">
   <cell role="label">Attleboro'</cell>
   <cell role="data">3</cell>
   <cell role="data">5</cell>
   <cell role="data">20</cell>
  </row>
  <row role="data">
   <cell role="label">Wymondham</cell>
   <cell role="data">1</cell>
   <cell role="data">11</cell>
   <cell role="data">22</cell>
  </row>
 </table>
Note

Contains an optional heading and a series of rows.

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

tagUsage

<tagUsage> (tag usage) supplies information about the usage of a specific element within a text. «#HD57»

Module header
Parents namespace
Attributes In addition to global attributes
gi the name (generic identifier) of the element indicated by the tag.
Status Required
Datatype data.name
Values the name of an element within the namespace indicated by the parent <namespace> element
occurs specifies the number of occurrences of this element within the text.
Status Recommended
Datatype data.count
Values an integer number greater than zero
withId specifies the number of occurrences of this element within the text which bear a distinct value for the global xml:id attribute.
Status Recommended
Datatype data.count
Values an integer number greater than zero
render specifies the identifier of a rendition element which defines how this element is to be rendered.
Status Optional
Datatype data.pointer
Values an identifier specified as the value of the xml:id attribute on some <rendition> element in the current document.
Declaration
element tagUsage
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute gi { data.name },
   attribute occurs { data.count }?,
   attribute withId { data.count }?,
   attribute render { data.pointer }?,
   macro.limitedContent
}
Example
 <tagsDecl>
  <rendition xml:id="it">Render using a slant or italic variant on the current font</rendition>
  <namespace name="http://www.tei-c.org/ns/1.0">
   <tagUsage
     gi="hi"
     occurs="28"
     withId="2"
     render="#it">
Used to mark English words italicised in the copy text.</tagUsage>
   <tagUsage gi="foreignrender="#it">Used to mark non-English words in the copy text.</tagUsage>
  </namespace>
 </tagsDecl>
Example
 <tagUsage
   gi="hi"
   occurs="28"
   withId="2"
   render="#it">
Utilisé seulement pour marquer les mots anglais en italiques dans le texte de la copie.</tagUsage>

taxonomy

<taxonomy> (taxonomy) defines a typology used to classify texts either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. «#HD55»

Module header
Parents classDecl
Attributes Global attributes only
Declaration
element taxonomy
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( model.glossLike* | category+ | ( ( model.biblLike ), category* ) )
}
Example
 <taxonomy xml:id="tax.b">
  <bibl>Brown Corpus</bibl>
  <category xml:id="tax.b.a">
   <catDesc>Press Reportage</catDesc>
   <category xml:id="tax.b.a1">
    <catDesc>Daily</catDesc>
   </category>
   <category xml:id="tax.b.a2">
    <catDesc>Sunday</catDesc>
   </category>
   <category xml:id="tax.b.a3">
    <catDesc>National</catDesc>
   </category>
   <category xml:id="tax.b.a4">
    <catDesc>Provincial</catDesc>
   </category>
   <category xml:id="tax.b.a5">
    <catDesc>Political</catDesc>
   </category>
   <category xml:id="tax.b.a6">
    <catDesc>Sports</catDesc>
   </category>
  </category>
  <category xml:id="tax.b.d">
   <catDesc>Religion</catDesc>
   <category xml:id="tax.b.d1">
    <catDesc>Books</catDesc>
   </category>
   <category xml:id="tax.b.d2">
    <catDesc>Periodicals and tracts</catDesc>
   </category>
  </category>
 </taxonomy>

teiCorpus

<teiCorpus> (TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more TEI elements, each containing a single text header and a text. «#DS» «#CCDEF»

Module core
Parents teiCorpus
Attributes In addition to global attributes
version The version of the TEI scheme
Status Optional
Datatype xsd:decimal
Values A number identifying the version of the TEI guidelines
Declaration
element teiCorpus
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute version { xsd:decimal }?,
   ( teiHeader, ( TEI | teiCorpus )+ )
}
Example
 <teiCorpus>
  <teiHeader/>
  <TEI>
   <teiHeader/>
   <text/>
  </TEI>
  <TEI>
   <teiHeader/>
   <text/>
  </TEI>
 </teiCorpus>
Note

Must contain one TEI header for the corpus, and a series of <TEI> elements, one for each text.

This element is mandatory when applicable.

teiHeader

<teiHeader> (TEI Header) supplies the descriptive and declarative information making up an electronic title page prefixed to every TEI-conformant text. «#HD11» «#CCDEF»

Module header
Parents TEI teiCorpus
Attributes In addition to global attributes
type specifies the kind of document to which the header is attached, for example whether it is a corpus or individual text.
Status Optional
Datatype data.enumerated
Sample values include:
text (the header is attached to a single text.) [Default]
corpus (the header is attached to a corpus.)
Declaration
element teiHeader
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type { data.enumerated }?,
   ( fileDesc, model.headerPart*, revisionDesc? )
}
Example
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>Shakespeare: the first folio (1623) in electronic form</title>
    <author>Shakespeare, William (1564–1616)</author>
    <respStmt>
     <resp>Originally prepared by</resp>
     <name>Trevor Howard-Hill</name>
    </respStmt>
    <respStmt>
     <resp>Revised and edited by</resp>
     <name>Christine Avern-Carr</name>
    </respStmt>
   </titleStmt>
   <publicationStmt>
    <distributor>Oxford Text Archive</distributor>
    <address>
     <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
    </address>
    <idno type="OTA">119</idno>
    <availability>
     <p>Freely available on a non-commercial basis.</p>
    </availability>
    <date when="1968">1968</date>
   </publicationStmt>
   <sourceDesc>
    <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile, 1968)</bibl>
   </sourceDesc>
  </fileDesc>
  <encodingDesc>
   <projectDesc>
    <p>Originally prepared for use in the production of a series of old-spelling concordances in 1968, this text was extensively checked and revised for use during the editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
   </projectDesc>
   <editorialDecl>
    <correction>
     <p>Turned letters are silently corrected.</p>
    </correction>
    <normalization>
     <p>Original spelling and typography is retained, except that long s and ligatured forms are not encoded.</p>
    </normalization>
   </editorialDecl>
   <refsDecl xml:id="ASLREF">
    <cRefPattern
      matchPattern="(\S+) ([^.]+)\.(.*)"
      replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">

     <p>A reference is created by assembling the following, in the reverse order as that listed here: <list>
       <item>the <att>n</att> value of the preceding <gi>lb</gi>
       </item>
       <item>a period</item>
       <item>the <att>n</att> value of the ancestor <gi>div2</gi>
       </item>
       <item>a space</item>
       <item>the <att>n</att> value of the parent <gi>div1</gi>
       </item>
      </list>
     </p>
    </cRefPattern>
   </refsDecl>
  </encodingDesc>
  <revisionDesc>
   <list>
    <item>
     <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
    <item>
     <date when="1989-03-01">1 Mar 89</date> LB made new file</item>
   </list>
  </revisionDesc>
 </teiHeader>
Example
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>Shakespeare: the first folio (1623) sous forme électronique</title>
    <author>Shakespeare, William (1564–1616)</author>
    <respStmt>
     <resp>Préparé par</resp>
     <name>Trevor Howard-Hill</name>
    </respStmt>
    <respStmt>
     <resp>Révisé et édité par</resp>
     <name>Christine Avern-Carr</name>
    </respStmt>
   </titleStmt>
   <publicationStmt>
    <distributor>Oxford Text Archive</distributor>
    <address>
     <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
    </address>
    <idno type="OTA">119</idno>
    <availability>
     <p>Disponible gratuitement à des fins non commerciales.</p>
    </availability>
    <date when="1968">1968</date>
   </publicationStmt>
   <sourceDesc>
    <bibl>The first folio of Shakespeare, préparé par Charlton Hinman (The Norton Facsimile, 1968)</bibl>
   </sourceDesc>
  </fileDesc>
  <encodingDesc>
   <projectDesc>
    <p>Préparé pour la production d'une collection de concordances old-spelling en 1968, ce texte a été profondément relu et révisé pour l'édition du new Oxford Shakespeare (Wells and Taylor, 1989).</p>
   </projectDesc>
   <editorialDecl>
    <correction>
     <p>Les caractères bloqués sont corrigés sans commentaire.</p>
    </correction>
    <normalization>
     <p>L'orthographe et la typographie originales sont conservées, à l'exception des s longs et des ligatures qui ne sont pas encodées.</p>
    </normalization>
   </editorialDecl>
   <refsDecl xml:id="ASLREF-FR">
    <cRefPattern
      matchPattern="(\S+) ([^.]+)\.(.*)"
      replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">

     <p>Une référence est créée en assemblant les éléments suivants dans l'ordre inverse de la liste suivante : <list>
       <item>la valeur de l'attribut <att>n</att> de l'élément <gi>lb</gi>précédent.</item>
       <item>un point</item>
       <item>la valeur de l'attribut <att>n</att> de l'élément <gi>div2</gi> ancêtre.</item>
       <item>un espace</item>
       <item>la valeur de l'attribut <att>n</att> de l'élément <gi>div1</gi> parent.</item>
      </list>
     </p>
    </cRefPattern>
   </refsDecl>
  </encodingDesc>
  <revisionDesc>
   <list>
    <item>
     <date when="1989-04-12">12 avril 1989</date> Dernière vérification par CAC</item>
    <item>
     <date when="1989-03-01">1er mars 1989</date> Nouveau fichier par LB</item>
   </list>
  </revisionDesc>
 </teiHeader>
Note

One of the few elements unconditionally required in any TEI document.

term

<term> contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. «#COHQU»

Module core
Parents index keywords model.emphLike
Attributes In addition to global attributes and those inherited from [att.declaring att.typed ]
sortKey supplies the sort key for this term in an index.Example
David's other principal backer, Josiah ha-Kohen  <index indexName="NAMES">
  <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term>
 </index> b. Azarya, son of one of the last gaons of Sura
was David's own first cousin.

The sort key is used to determine the sequence and grouping of entries in an index; if this attribute is not supplied, the textual content of the element is used for this purpose.

Status Optional
Datatype data.word
Values any string of Unicode characters.
target identifies the associated gloss element by an absolute or relative URI reference
Status Optional
Datatype data.pointer
Values should be a valid URI reference that resolves to a <gloss> element
cRef identifies the associated gloss element using a canonical reference from a scheme defined in a refsDecl element in the TEI header

The <refsDecl> to use may be indicated with the decls attribute.

Status Optional
Datatype data.pointer
Values the result of applying the algorithm for the resolution of canonical references (described in section ) should be a valid URI reference that resolves to a <gloss> element
Declaration
element term
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declaring.attribute.decls,
   att.typed.attribute.type,
   att.typed.attribute.subtype,
   attribute sortKey { data.word }?,
   ( attribute target { data.pointer }? | attribute cRef { data.pointer }? ),
   macro.phraseSeq
}
Example
A computational device that infers structure from grammatical strings of words is known as a  <term>parser</term>, and much
of the history of NLP over the last 20 years has been occupied
with the design of parsers.
Example
We may define  <term xml:id="TDPVrend="sc">discoursal point of view</term>
as
 <gloss target="#TDPV">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Note

This element is used to supply the form under which an index entry is to be made for the location of a parent <index> element.

In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion.

The target and cRef attributes are mutually exclusive.

text

<text> contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. «#DS» «#CCDEF»

Module textstructure
Parents TEI group measureGrp
Attributes Global attributes and those inherited from [att.declaring att.typed ]
Declaration
element text
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declaring.attribute.decls,
   att.typed.attribute.type,
   att.typed.attribute.subtype,
   (
      model.global*,
      ( front, model.global* )?,
      ( body | group ),
      model.global*,
      ( back, model.global* )?
   )
}
Example
 <text>
  <front>
   <docTitle>
    <titlePart>Autumn Haze</titlePart>
   </docTitle>
  </front>
  <body>
   <l>Is it a dragonfly or a maple leaf</l>
   <l>That settles softly down upon the water?</l>
  </body>
 </text>
Example

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

 <text>
  <front/>
  <group>
   <text>
    <front/>
    <body/>
    <back/>
   </text>
   <text/>
  </group>
 </text>
Note

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

textClass

<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. «#HD43»

Module header
Parents model.profileDescPart
Attributes Global attributes and those inherited from [att.declarable ]
Declaration
element textClass
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.declarable.attribute.default,
   ( classCode | catRef | keywords )*
}
Example
 <taxonomy>
  <category xml:id="acprose">
   <catDesc>Academic prose</catDesc>
  </category>
 </taxonomy>
 <textClass>
  <catRef target="#acprose"/>
  <classCode scheme="http://www.udcc.org">001.9</classCode>
  <keywords scheme="http://authorities.loc.gov">
   <list>
    <item>End of the world</item>
    <item>History - philosophy</item>
   </list>
  </keywords>
 </textClass>
Example
 <textClass>
  <catRef target="#acprose"/>
  <classCode scheme="http://www.udcc.org">001.9</classCode>
  <keywords scheme="http://authorities.loc.gov/">
   <list>
    <item>Fin du monde</item>
    <item>Histoire - philosophie</item>
   </list>
  </keywords>
 </textClass>

time

<time> contains a phrase defining a time of day in any format. «#CONADA»

Module core
Parents model.dateLike
Attributes Global attributes and those inherited from [att.datable att.duration att.editLike att.typed ]
Declaration
element time
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.datable.w3c.attribute.period,
   att.datable.w3c.attribute.when,
   att.datable.w3c.attribute.notBefore,
   att.datable.w3c.attribute.notAfter,
   att.datable.w3c.attribute.from,
   att.datable.w3c.attribute.to,
   att.duration.w3c.attribute.dur,
   att.editLike.attribute.cert,
   att.editLike.attribute.resp,
   att.editLike.attribute.evidence,
   att.typed.attribute.type,
   att.typed.attribute.subtype,
   ( text | model.gLike | model.datePart | model.phrase | model.global )*
}
Example
As he sat smiling, the quarter struck —  <time when="11:45:00">the quarter to twelve</time>.

title

<title> contains the full title of a work of any kind. «#COBICOR» «#HD21» «#HD26»

Module core
Parents seriesStmt titleStmt model.emphLike model.msItemPart
Attributes In addition to global attributes
level indicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.

If the title appears directly enclosed within an <analytic> element, the level, if given, must be ‘a’; if it appears directly enclosed within a <monogr> element, level must be ‘m’, ‘j’, or ‘u’; when <title> is directly enclosed by <series>, level must be ‘s’. If it appears within a <msItem>, this attribute should not be supplied.

Status Required when applicable
Legal values are:
a (analytic title (article, poem, or other item published as part of a larger item))
m (monographic title (book, collection, or other item published as a distinct item, including single volumes of multi-volume works))
j (journal title)
s (series title)
u (title of unpublished material (including theses and dissertations unless published by a commercial press))
type classifies the title according to some convenient typology.

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

Status Optional
Datatype data.enumerated
Sample values include:
main (main title)
sub (subtitle, title of part)
alt (alternate title, often in another language, by which the work is also known)
short (abbreviated form of title)
desc (descriptive paraphrase of the work functioning as a title)
Declaration
element title
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   attribute type { data.enumerated }?,
   macro.paraContent
}
Example
 <title>La vie mode d'emploi. Romans.</title>
Example
 <title>Synthese: an international journal for epistemology, methodology and history of science</title>
Example
 <title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title>
Example
 <title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title>

titlePage

<titlePage> (title page) contains the title page of a text, appearing within the front or back matter. «#DSTITL»

Module textstructure
Parents model.frontPart
Attributes In addition to global attributes
type classifies the title page according to any convenient typology.

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

Status Optional
Datatype data.enumerated
Values Any string, e.g. full, half, Series, etc.
Declaration
element titlePage
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type { data.enumerated }?,
   (
      model.global*,
      ( model.titlepagePart ),
      ( model.titlepagePart | model.global )*
   )
}
Example
 <titlePage>
  <docTitle>
   <titlePart type="main">THOMAS OF Reading.</titlePart>
   <titlePart type="alt">OR, The sixe worthy yeomen of the West.</titlePart>
  </docTitle>
  <docEdition>Now the fourth time corrected and enlarged</docEdition>
  <byline>By T.D.</byline>
  <figure>
   <head>TP</head>
   <p>Thou shalt labor till thou returne to duste</p>
   <figDesc>Printers Ornament used by TP</figDesc>
  </figure>
  <docImprint>Printed at <name type="place">London</name>
   for <name>T.P.</name>
   <date>1612.</date>
  </docImprint>
 </titlePage>

titlePart

<titlePart> (title part) contains a subsection or division of the title of a work, as indicated on a title page. «#DSTITL»

Module textstructure
Parents docTitle model.titlepagePart model.pLike.front
Attributes In addition to global attributes
type specifies the role of this subdivision of the title.
Status Optional
Datatype data.enumerated
Suggested values include:
main (main title of the work) [Default]
sub (subtitle of the work)
alt (alternative title of the work)
short (abbreviated form of title)
desc (descriptive paraphrase of the work)
Declaration
element titlePart
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   attribute type { "main" | "sub" | "alt" | "short" | "desc" | token }?,
   macro.paraContent
}
Example
 <docTitle>
  <titlePart type="main">THE FORTUNES AND MISFORTUNES Of the FAMOUS Moll Flanders, &c. </titlePart>
  <titlePart type="desc">Who was BORN in NEWGATE, And during a Life of continu'd Variety for Threescore Years, besides her Childhood, was Twelve Year a <hi>Whore</hi>, five times a <hi>Wife</hi> (wherof
   once to her own Brother) Twelve Year a <hi>Thief,</hi>
   Eight Year a Transported <hi>Felon</hi> in <hi>Virginia</hi>,
   at last grew <hi>Rich</hi>, liv'd <hi>Honest</hi>, and died a
   <hi>Penitent</hi>.</titlePart>
 </docTitle>

titleStmt

<titleStmt> (title statement) groups information about the title of a work and those responsible for its intellectual content. «#HD21» «#HD2»

Module header
Parents macro.fileDescPart
Attributes Global attributes only
Declaration
element titleStmt
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   ( title+, ( author | editor | sponsor | funder | principal | respStmt )* )
}
Example
 <titleStmt>
  <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
  <respStmt>
   <resp>compiled by</resp>
   <name>P.J. Lucas</name>
  </respStmt>
 </titleStmt>
Example
 <titleStmt>
  <title>Capgrave's Life of St. John Norbert : transcription électronique</title>
  <respStmt>
   <resp>compilée par</resp>
   <name>P.J. Lucas</name>
  </respStmt>
 </titleStmt>

trailer

<trailer> (trailer) contains a closing title or footer appearing at the end of a division of a text. «#DSCO» «#DSDTB»

Module textstructure
Parents model.divWrapper.bottom
Attributes Global attributes only
Declaration
element trailer
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   macro.phraseSeq
}
Example
 <trailer>Explicit pars tertia</trailer>

unclear

<unclear> contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. «#PHDA» «#COEDADD»

Module core
Parents model.pPart.transcriptional model.choicePart
Attributes In addition to global attributes and those inherited from [att.editLike ]
reason indicates why the material is hard to transcribe.
Status Optional
Datatype 1–∞ occurrences of data.wordseparated by whitespace
Values any phrase describing the difficulty, e.g. faded, ambient noise, passing truck, ill formed, eccentric ductus.
hand Where the difficulty in transcription arises from action (partial deletion, etc.) assignable to an identifiable hand, signifies the hand responsible for the action.
Status Optional
Datatype data.pointer
Values must be one of the hand identifiers declared in the document header (see section ).
agent Where the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
Status Optional
Datatype data.enumerated
Sample values include:
rubbing (damage results from rubbing of the leaf edges)
mildew (damage results from mildew on the leaf surface)
smoke (damage results from smoke)
Declaration
element unclear
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   att.editLike.attribute.cert,
   att.editLike.attribute.resp,
   att.editLike.attribute.evidence,
   attribute reason { list { data.word+ } }?,
   attribute hand { data.pointer }?,
   attribute agent { data.enumerated }?,
   macro.paraContent
}
Note

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

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

val

<val> (value) contains a single attribute value. «#TD» «#TDATT»

Module tagdocs
Parents model.xmlPhrase
Attributes Global attributes only
Declaration
element val
{
   att.global.attribute.xmlspace,
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.rend,
   att.global.attribute.xmlbase,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.analytic.attribute.ana,
   text
}
Example
 <val>unknown</val>

Macros defined

data.certainty

data.certainty defines the range of attribute values expressing a degree of certainty

Module tei
Declaration
data.certainty = "high" | "medium" | "low" | "unknown"
Note

Certainty may be expressed by one of the predefined symbolic values high, medium, or low. For more precise indication, data.probability may be used instead or in addition.

data.code

data.code defines the range of attribute values expressing a coded value by means of a pointer to some other element which contains a definition for it.

Module tei
Declaration
data.code = xsd:anyURI
Note

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

data.count

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

Module tei
Declaration
data.count = xsd:nonNegativeInteger
Note

Only positive integer values are permitted

data.duration.w3c

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

Module tei
Declaration
data.duration.w3c = xsd:duration
Example
 <time dur="PT45M">forty-five minutes</time>
Example
 <date dur="P1DT12H">a day and a half</date>
Example
 <date dur="P7D">a week</date>
Example
 <time dur="PT0.02S">20 ms</time>
Note

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

For complete details, see the W3C specification.

data.enumerated

data.enumerated defines the range of attribute values expressed as a single word or token taken from a list of documented possibilities

Module tei
Declaration
data.enumerated = data.name
Note

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

data.key

data.key defines the range of attribute values expressing a coded value by means of an arbitrary identifier, typically taken from a set of externally-defined possibilities

Module tei
Declaration
data.key = string
Note

Information about the set of possible values for an attribute using this datatype may (but need not) be documented in the document header. Externally defined constraints, for example that values should be legal keys in an external database system, cannot usually be enforced by a TEI system. Similarly, because the key is externally defined, no constraint other than a requirement that it consist of Unicode characters is possible.

data.language

data.language defines the range of attribute values used to identify a particular combination of human language and writing system

Module tei
Declaration
data.language = xsd:language
Note
The values for this attribute are language ‘tags’ as defined in RFC 3066 or its successor. Examples include
sn
Shona
zh-TW
Taiwanese
en-SL
English as spoken in Sierra Leone
pl
Polish
es-MX
Spanish as spoken in Mexico

data.name

data.name defines the range of attribute values expressed as an XML name or identifier

Module tei
Declaration
data.name = xsd:Name
Note

Attributes using this datatype must contain a single word which follows the rules defining a legal XML name: for example they cannot include whitespace or begin with digits.

data.namespace

data.namespace (an XML namespace) defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML technical recommendation

Module tei
Declaration
data.namespace = xsd:anyURI
Note

The range of syntactically valid values is defined by RFC 2396 Uniform Resource Identifier (URI) Reference

data.numeric

data.numeric defines the range of attribute values used for numeric values

Module tei
Declaration
data.numeric = xsd:double | xsd:decimal
Note

Any numeric value that can be represented as a decimal number.

In addition, the range of values that can be represented in an IEEE double precision (i.e., 64-bit) floating point number may be represented using scientific notation. Roughly that range is ±10⁻³²³ to ±10³⁰⁸.

To represent a number expressed in scientific notation, ‘exponential notation’ is used in the attribute value. The significand (sometimes called the mantissa) is written as a decimal number, followed by the letter E, followed by an integer exponent. The multiplication sign and the base itself (10) are implied. Either the significand or the exponent (or both) may be a negative number, in which case it should be preceded by a minus sign. There should be no whitespace separating the significand from the E from the exponent. E.g., 3×10⁸ can be expressed as 3E8.

Other examples of scientific notation include:
  • 10E10 (the speed of light in centimetres per second)
  • 9.12E-31 (the mass of an electron in Kg)
  • 4E11 (estimated number of stars in our galaxy)
  • -1.76E11 (electron charge to mass quotient in coulombs per Kg)

Either e or E may be used to separate the significand from the exponent, however these Guidelines recommend E be used both for consistency with other standards bodies and to avoid confusion with the mathematical constant e.

data.outputMeasurement

data.outputMeasurement (HTML dimension) defines a range of values for use in specifying the size of an object that is intended for display on the web

Module tei
Declaration
data.outputMeasurement =
   token
   {
      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)"
   }
Note

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

data.pattern

data.pattern defines a range of attribute values expressed as a regular expression

Module tei
Declaration
data.pattern = token
Note
A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndelmatches each of the three strings)
wikipedia

data.pointer

data.pointer defines the range of attribute values used to provide a single pointer to any other resource, either within the current document or elsewhere

Module tei
Declaration
data.pointer = xsd:anyURI
Note

The range of syntactically valid values is defined by RFC 2396 Uniform Resource Identifier (URI) Reference

data.temporal.w3c

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

Module tei
Declaration
data.temporal.w3c =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
Note

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

data.word

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

Module tei
Declaration
data.word = token { pattern = "(\p{L}|\p{N}|\p{P}|\p{S})+" }
Note

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

macro.componentSeq

macro.componentSeq (component-sequence) defines a sequence of component-level elements (such as paragraphs or lists) which can occur directly within text divisions and in similar positions.

Module tei
Used by epigraph
Declaration
macro.componentSeq = ( model.common | model.global )*
Note

This macro is used in each base tag set to define the content of <div> and similar elements.

macro.fileDescPart

macro.fileDescPart (file description elements) groups elements which occur inside fileDesc and biblFull

Module tei
Used by biblFull fileDesc
Declaration
macro.fileDescPart =
   titleStmt, editionStmt?, extent?, publicationStmt, seriesStmt?, notesStmt?

macro.glossSeq

macro.glossSeq (glossing sequence) defines a sequence of descriptive or identifying elements which characterize a markup object.

Module tei
Used by gap
Declaration
macro.glossSeq = gloss*
Note

This macro defines a standard content model for all occasions where some markup object is being explained or glossed.

macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials

Module tei
Used by figDesc rendition tagUsage
Declaration
macro.limitedContent = ( text | model.limitedPhrase | model.inter )*

macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements.

Module tei
Used by add cell corr del docEdition emph head hi l orig p ref reg seg sic title titlePart unclear
Declaration
macro.paraContent =
   ( text | model.gLike | model.phrase | model.inter | model.global )*

macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements.

Module tei
Used by abbr addrLine author biblScope dateline distributor docAuthor docDate edition editor expan extent foreign label mentioned name num pubPlace publisher rs s salute signed soCalled speaker term trailer
Declaration
macro.phraseSeq = ( text | model.gLike | model.phrase | model.global )*

macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents.

Module tei
Used by authority classCode creation funder gloss interp language principal resp sponsor
Declaration
macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*

macro.specialPara

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

Module tei
Used by item note q quote stage
Declaration
macro.specialPara =
   (
      text
    | model.gLikemodel.phrasemodel.intermodel.divPartmodel.global
   )*
Notes
1. The relevant standards are RFC 3066, and the lists of two and three language identifiers maintained as part of ISO 639 (see http://www.w3.org/WAI/ER/IG/ert/iso639.htm)
2. 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.
1. Kyd, Spanish Tragedy, (1592) Kv


Date:
This page is copyrighted