TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

1. Introduction

Previous i. Prefatory note

Next 2. A Short Example

Home

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

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

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

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

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

suffice to represent the textual features needed for research;

be simple, clear, and concrete;

be easy for researchers to use without special-purpose software;

allow the rigorous definition and efficient processing of texts;

provide for user-defined extensions;

conform to existing and emergent standards.

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

the common core of textual features be easily shared;

additional specialist features be easy to add to (or remove from) a text;

multiple parallel encodings of the same feature should be possible;

the richness of markup should be user-defined, with a very small minimal requirement;

adequate documentation of the text and its encoding should be provided.

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

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

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

it should be able to handle adequately a reasonably wide variety of texts, at the level of detail found in existing practice (as demonstrated in, for example, the holdings of the Oxford Text Archive);

it should be useful for the production of new documents (such as this one) as well as the encoding of existing texts;

it should be usable with a wide range of existing XML software;

it should be a pure subset of the full TEI scheme and defined using the customizaticon methods described in the TEI Guidelines;

it should be as small and simple as is consistent with the other goals.

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

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

15. Interpretation and Analysis

Table of contents

15.1. Orthographic Sentences

15.2. Words and punctuation

15.3. General-Purpose Interpretation Elements

Previous 14. Figures and Graphics

Next 16. Technical Documentation

Home

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.

Next 15.2. Words and punctuation

Home

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

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

Previous 15.1. Orthographic Sentences

Next 15.3. General-Purpose Interpretation Elements

Home

TEI: Words and punctuation¶15.2. Words and punctuation

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

w (word) represents a grammatical (not necessarily orthographic) word.

pc (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark.

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

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

In this example, each word has been decorated with an automatically generated part of speech code, using the ana attribute discussed in section 8.3. Special kinds of Linking above. The w also provides for each word to be associated with a root form or lemma, either explicitly using the lemma attribute, or by reference, using the lemmaRef attribute, as in this example:

...<w ana="#VBD" lemma="be"
 lemmaRef="http://www.myLexicon.com/be">was</w> ...

Previous 15.2. Words and punctuation

Home

TEI: General-Purpose Interpretation Elements¶15.3. General-Purpose Interpretation Elements

The w element is a specialisation of the seg element which has already been introduced for use in identifying otherwise unmarked targets of cross references and hypertext links (see section 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 other provision in the published TEI Guidelines.

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

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

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

A seg element of one type (unlike the s element which it superficially resembles) can be nested within a seg element of the same or another type. This enables quite complex structures to be represented; some examples were given in section 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 allow the encoder to specify both the class of an interpretation, and the particular instance of that class which the interpretation involves. Thus, whereas with seg one can say simply that something is an apostrophe, with interp one can say that it is an instance (apostrophe) of a larger class (rhetorical figures).

Moreover, interp is a ‘stand off’ element: it does not surround the segments of text which it describes, but instead is linked to the passage in question either by means of the ana attribute discussed in section 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, independently of the document hierarchy, as well as facilitating the grouping of analyses of a particular type together. A special purpose interpGrp element is provided for the latter purpose.

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

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

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

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

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

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

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

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

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

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

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

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

12. Bibliographic Citations

Previous 11. Lists

Next 13. Tables

Home

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.

bibl (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.

author in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority.

biblScope (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work.

date contains a date in any format.

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

publisher provides the name of the organization responsible for the publication or distribution of a bibliographic item.

pubPlace (publication place) contains the name of the place where a bibliographic item was published.

title contains a title for any kind of work.

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.

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

4. Encoding the Body

Table of contents

4.1. Text Division Elements

4.2. Headings and Closings

4.3. Prose, Verse and Drama

Previous 3. The Structure of a TEI Text

Next 5. Page and Line Numbers

Home

As indicated above, a simple TEI document at the textual level consists of the following elements:

front (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body.

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.

body (text body) contains the whole body of a single unitary text, excluding any front or back matter.

back (back matter) contains any appendixes, etc. following the main part of a text.

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.

Next 4.2. Headings and Closings

Home

TEI: Text Division Elements¶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, divs, 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. It is particularly useful to supply such identifiers if the resource concerned is to be made available over the web, since they make it much easier for other web-based applications to link directly to the corresponding parts of your text.

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

The xml:lang attribute may be used to specify the language of the division. Languages are identified by an internationally defined code, as further discussed in section 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="WN1" n="I" type="book">
  <div xml:id="WN101" n="I.1" type="chapter">
<!-- ... -->
  </div>
  <div xml:id="WN102" n="I.2" type="chapter">
<!-- ... -->
  </div>
<!-- ... -->
  <div xml:id="WN110" n="I.10"
   type="chapter">
   <div xml:id="WN1101" n="I.10.1"
    type="part">
<!-- ... -->
   </div>
   <div xml:id="WN1102" n="I.10.2"
    type="part">
<!-- ... -->
   </div>
  </div>
<!-- ... -->
 </div>
 <div xml:id="WN2" n="II" type="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="TS01" n="1" type="volume">
  <div xml:id="TS011" n="1" type="chapter">
<!-- ... -->
  </div>
  <div xml:id="TS012" n="2" type="chapter">
<!-- ... -->
  </div>
 </div>
 <div xml:id="TS02" n="2" type="volume">
  <div xml:id="TS021" n="3" type="chapter">
<!-- ... -->
  </div>
  <div xml:id="TS022" n="4" type="chapter">
<!-- ... -->
  </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.

Previous 4.1. Text Division Elements

Next 4.3. Prose, Verse and Drama

Home

TEI: Headings and Closings¶4.2. Headings and Closings

Every div may have a title or heading at its start, and (less commonly) a trailer such as ‘End of Chapter 1’ at its end. The following elements may be used to transcribe them:

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

Previous 4.2. Headings and Closings

Home

TEI: Prose, Verse and Drama¶4.3. Prose, Verse and Drama

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

l (verse line) contains a single, possibly incomplete, line of verse.

lg (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc.

sp (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text.

speaker contains 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 might additionally be used to mark typographic lines if so desired.

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

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

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

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

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

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

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

<div>
 <sp who="#OPI">
  <speaker>The reverend Doctor Opimian</speaker>
  <p>I do not think I have named a single unpresentable fish.</p>
 </sp>
 <sp who="#GRM">
  <speaker>Mr Gryll</speaker>
  <p>Bream, Doctor: there is not much to be said for bream.</p>
 </sp>
 <sp who="#OPI">
  <speaker>The Reverend Doctor Opimian</speaker>
  <p>On the contrary, sir, I think there is much to be said for him. In the first
     place....</p>
  <p>Fish, Miss Gryll -- I could discourse to you on fish by the hour: but for the present I
     will forbear.</p>
 </sp>
</div>

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

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

17. Character Sets, Diacritics, etc.

Previous 16. Technical Documentation

Next 18. Front and Back Matter

Home

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.

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

9. Editorial Interventions

Table of contents

9.1. Correction and Normalization

9.2. Omissions, Deletions, and Additions

9.3. Abbreviations and their Expansion

Previous 8. Cross References and Links

Next 10. Names, Dates, and Numbers

Home

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.

Next 9.2. Omissions, Deletions, and Additions

Home

TEI: Correction and Normalization¶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 (Latin for thus or so) 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 Shakespearian scholar Lewis Theobald. The following encoding would then be appropriate:

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

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

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

Finally, a modern digital editor may decide to combine both possibilities in a single composite text, using the choice element.

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>

Previous 9.1. Correction and Normalization

Next 9.3. Abbreviations and their Expansion

Home

TEI: Omissions, Deletions, and Additions¶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 source text by an author, scribe, or a previous annotator or corrector.

gap indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.

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

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 is used to point to a fuller definition (typically in a respStmt element) for the agency responsible for correcting the duplication of for.

If the source read ‘The following elements provided for simple editorial interventions.’ (i.e. if the verb had been inadvertently dropped) then the corrected text might read:

The following elements <add resp="#LB">are</add> provided for simple editorial interventions.

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

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

Again, the code #DHL points to another location where more information about the hand concerned is to be found³.

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

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

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

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

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

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

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

Previous 9.2. Omissions, Deletions, and Additions

Home

TEI: Abbreviations and their Expansion¶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. One simple means of achieving that would be an encoding such as the follow

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

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

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

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

Notes

3

The full TEI provides a range of elements for encoding metadata about manuscript production and description, which are not however included in TEI Lite

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

2. A Short Example

Previous 1. Introduction

Next 3. The Structure of a TEI Text

Home

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

            CHAPTER 38

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

            474

            JANE EYRE                      475

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

This transcription suffers from a number of shortcomings:

the page numbers and running titles are intermingled with the text in a way which makes it difficult for software to disentangle them;

no distinction is made between single quotation marks and apostrophe, so it is difficult to know exactly which passages are in direct speech;

the preservation of the copy text's hyphenation means that simple-minded search programs will not find the broken words;

the accented letter in faàl and the long dash have been rendered by ad hoc keying conventions which follow no standard pattern and will be processed correctly only if the transcriber remembers to mention them in the documentation;

paragraph divisions are marked only by the use of white space, and hard carriage returns have been introduced at the end of each line. Consequently, if the size of type used to print the text changes, reformatting will be problematic.

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

Paragraph and chapter divisions are now marked explicitly.

Apostrophes are distinguished from quotation marks; direct speech is explicitly marked.

The accented letter and the long dash are correctly represented.

Page divisions have been marked with an empty pb element alone.

The lineation of the original has not been retained and words broken by typographic accident at the end of a line have been re-assembled without comment.

For convenience of proof reading, a new line has been introduced at the start of each paragraph, but the indentation is removed.

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

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

a regularized form of the passages in dialect could be provided;

footnotes glossing or commenting on any passage could be added;

pointers linking parts of this text to others could be added;

proper names of various kinds could be distinguished from the surrounding text;

detailed bibliographic information about the text's provenance and context could be prefixed to it;

a linguistic analysis of the passage into sentences, clauses, words, etc., could be provided, each unit being associated with appropriate category codes;

the text could be segmented into narrative or discourse units;

systematic analysis or interpretation of the text could be included in the encoding, with potentially complex alignment or linkage between the text and the analysis, or between the text and one or more translations of it;

passages in the text could be linked to images or sound held on other media.

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

detailed analysis of the components of names;

detailed meta-information providing thesaurus-style information about the text's origins or topics;

information about the printing history or manuscript variations exhibited by a particular series of versions of the text.

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

14. Figures and Graphics

Previous 13. Tables

Next 15. Interpretation and Analysis

Home

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

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

graphic indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it.

figure groups elements representing or containing graphic information such as an illustration, formula, or figure.

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.

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

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

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

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

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

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

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

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

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

<text>
 <pb facs="page1.png" n="1"/>
<!-- text contained on page 1 is encoded here -->
 <pb facs="page2.png" n="2"/>
<!-- text contained on page 2 is encoded here -->
</text>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

18. Front and Back Matter

Table of contents

18.1. Front Matter

18.2. Back Matter

Previous 17. Character Sets, Diacritics, etc.

Next 19. The Electronic Title Page

Home

TEI: Front 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.

Next 18.1.2. Prefatory Matter

Home

TEI: Title Page¶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 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 on a title page or in a dateline.

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 contains a quotation, anonymous or attributed, appearing at the start or end of a section 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 xml:lang attribute or the foreign element, as necessary. Names of people, places, or organizations, may be tagged using the name element wherever they appear if no other more specific element is available.

Two example title pages follow:

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

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

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

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

Previous 18.1.1. Title Page

Home

TEI: Prefatory Matter¶18.1.2. Prefatory Matter

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

preface

A foreword or preface addressed to the reader in which the author or publisher explains the content, purpose, or origin of the text

dedication

A formal offering or dedication of a text to one or more persons or institutions by the author.

abstract

A summary of the content of a text as continuous prose

ack

A formal declaration of acknowledgment by the author in which persons and institutions are thanked for their part in the creation of a text

contents

A table of contents, specifying the structure of a work and listing its constituents. The list element should be used to mark its structure.

frontispiece

A pictorial frontispiece, possibly including some text.

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

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

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 contains a formal list or prose description of the topics addressed by a subdivision of a text.

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

imprimatur contains a formal statement authorizing the publication of a work, sometimes required to appear on a title page or its verso.

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, &amp;c.</head>
 <salute>MY LORD,</salute>
 <p>THis <hi>Poem</hi>, which receiv'd its first occasion of Birth from your Self, and
   others of your Noble Family .... and as in this representation your attendant
 <name>Thyrsis</name>, so now in all reall expression</p>
 <closer>
  <salute>Your faithfull, and most humble servant</salute>
  <signed>
   <name>H. LAWES.</name>
  </signed>
 </closer>
</div>

Previous 18.1. Front Matter

Home

TEI: Back Matter¶18.2. Back Matter

TEI: Structural Divisions of 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 ancillary self-contained section of a work, often providing additional but in some sense extra-canonical text.

glossary

A list of terms associated with definition texts (‘glosses’): this should be encoded as a <<list type="gloss">> element

notes

A section in which textual or other kinds of notes are gathered together.

bibliogr

A list of bibliographic citations: this should be encoded as a listBibl

index

Any form of pre-existing index to the work (An index may also be generated for a document by using the index element described above).

colophon

A statement appearing at the end of a book describing the conditions of its physical production.

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

19. The Electronic Title Page

Table of contents

19.1. The File Description

19.2. The Encoding Description

19.3. The Profile Description

19.4. The Revision Description

Previous 18. Front and Back Matter

Next Appendix A List of Elements Described

Home

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:

fileDesc (file description) contains a full bibliographic description of an electronic file.

encodingDesc (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived.

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.

revisionDesc (revision description) summarizes the revision history for a file.

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

Some of the header elements contain running prose which consists of one or more ps. Others are grouped:

Elements whose names end in Stmt (for statement) usually enclose a group of elements recording some structured information.

Elements whose names end in Decl (for declaration) enclose information about specific encoding practices.

Elements whose names end in Desc (for description) contain a prose description.

Next 19.2. The Encoding Description

Home

TEI: The File Description¶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 content.

editionStmt (edition statement) groups information relating to one edition of a text.

extent describes the approximate size of a text stored on some carrier medium or of some other object, 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 (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence.

A minimal header has the following structure:

<teiHeader>
 <fileDesc>
  <titleStmt>
<!-- bibliographic description of the digital resource -->
  </titleStmt>
  <publicationStmt>
<!-- information about how the resource is distributed -->
  </publicationStmt>
  <sourceDesc>
<!-- information about the sources from which the digital resource is derived -->
  </sourceDesc>
 </fileDesc>
</teiHeader>

Next 19.1.2. The Edition Statement

Home

TEI: The Title Statement¶19.1.1. The Title Statement

The following elements can be used in the titleStmt:

title contains a title for any kind of work.

author in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority.

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. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work.

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

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

The respStmt element contains the following subcomponents:

resp (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work.

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>

Previous 19.1.1. The Title Statement

Next 19.1.3. The Extent Statement

Home

TEI: The Edition Statement¶19.1.2. The Edition Statement

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

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. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work.

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.

Previous 19.1.2. The Edition Statement

Next 19.1.4. The Publication Statement

Home

TEI: The Extent Statement¶19.1.3. The Extent Statement

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

Example:

<extent>4532
 bytes</extent>

Previous 19.1.3. The Extent Statement

Next 19.1.5. Series and Notes Statements

Home

TEI: The Publication Statement¶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 a work 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 (publication place) 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 (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way.

availability supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc.

licence contains information about a licence or other legal agreement applicable to the text.

date contains a date in any format.

Example:

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

Previous 19.1.4. The Publication Statement

Next 19.1.6. The Source Description

Home

TEI: Series and Notes Statements¶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.

Previous 19.1.5. Series and Notes Statements

Home

TEI: The Source Description¶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.

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>
 <bibl>
  <author>CNN Network News</author>
  <title>News headlines</title>
  <date>12 Jun
     1989</date>
 </bibl>
</sourceDesc>

Previous 19.1. The File Description

Next 19.3. The Profile Description

Home

TEI: The Encoding Description¶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.

Next 19.2.2. Editorial Declarations

Home

TEI: Project and Sampling Descriptions¶19.2.1. Project and Sampling Descriptions

Examples of projectDesc and <samplingDesc>:

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

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

Previous 19.2.1. Project and Sampling Descriptions

Next 19.2.3. Reference and Classification Declarations

Home

TEI: Editorial Declarations¶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>
</editorialDecl>

Previous 19.2.2. Editorial Declarations

Home

TEI: Reference and Classification Declarations¶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 <att>n</att>
   attribute on each <gi>div</gi> contains the canonical reference for each division in the
   form XX.yyy where XX is the book number in roman numeral and yyy is the section number in
   arabic.</p>
 <p>Milestone tags refer to the edition of 1830 as E30 and that of 1850 as E50.
 </p>
</refsDecl>

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

taxonomy defines a typology 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 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="LC-SH">
  <bibl>Library of Congress Subject Headings
  </bibl>
 </taxonomy>
</classDecl>

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

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

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

Previous 19.2. The Encoding Description

Next 19.4. The Revision Description

Home

TEI: The Profile Description¶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 when="1992-08">August 1992</date>
 <name type="place">Taos, New Mexico</name>
</creation>

The langUsage element is useful where a text contains many different languages. It may contain language elements to document each particular language used:

language characterizes a single language or sublanguage used within a text.

For example, a text containing predominantly text in French as spoken in Quebec, but also smaller amounts of British and Canadian English might be documented as follows:

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

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

classCode (classification code) 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.

keywords contains a list of keywords or phrases identifying the topic or nature of a text.

The simplest way of classifying a text is by means of the classCode element. For example, a text with classification 410 in the Universal Decimal Classification might be documented as follows:

<classCode scheme="http://www.udc.org">410</classCode>

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

<catRef target="#B.A3 #B.D"/>

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

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

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

Previous 19.3. The Profile Description

Home

TEI: The Revision Description¶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 the change. The attributes when and who may be used to identify when the change was carried out and the agency responsible for it.

Example:

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

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

6. Marking Highlighted Phrases

Table of contents

6.1. Changes of Typeface, etc.

6.2. Quotations and Related Features

6.3. Foreign Words or Expressions

Previous 5. Page and Line Numbers

Next 7. Notes

Home

TEI: Changes of Typeface, etc.¶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 in the source. For example, a heading rendered in bold might be tagged <head rend="bold">, and one in italic <head rend="italic">.

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

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

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 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 any label or heading used to identify part of a text, typically but not exclusively in a list or glossary.

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 a title for any kind of work.

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

As an example of the elements defined here, consider the following sentence:

On the one hand the Nibelungenlied is associated with the new rise of romance of twelfth-century France, the romans d'antiquité, the romances of Chrétien de Troyes, and the German adaptations of these works by Heinrich van Veldeke, Hartmann von Aue, and Wolfram von Eschenbach.

Interpreting the role of the highlighting, the sentence might look like this:

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

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

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

Previous 6.1. Changes of Typeface, etc.

Next 6.3. Foreign Words or Expressions

Home

TEI: Quotations and Related Features¶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) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used.

mentioned marks words or phrases mentioned, not used.

soCalled 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 this is explicit in the text, as in the following example:

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

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

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

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

Previous 6.2. Quotations and Related Features

Home

TEI: Foreign Words or Expressions¶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="fr">savoir-faire</foreign>.</p>
<p>Have you read <title xml:lang="de">Die
   Dreigroschenoper</title>?</p>
<p>
 <mentioned xml:lang="fr">Savoir-faire</mentioned> is French
 for know-how.
</p>
<p>The court issued a writ of <term xml:lang="la">mandamus</term>.</p>

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

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

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

Notes

2

The relevant standard is Best Current Practice 47 (http://tools.ietf.org/html/bcp47). The authoritative list of registered subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a general overview of the construction of language tags, see http://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see http://www.w3.org/International/questions/qa-choosing-language-tags.

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

11. Lists

Previous 10. Names, Dates, and Numbers

Next 12. Bibliographic Citations

Home

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

list contains any sequence of items organized as a list.

item contains one component of a list.

label contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary.

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

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

The styles should not be mixed in the same list.

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

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

Where the internal structure of a list item is more complex, it may be preferable to regard the list as a table, for which special-purpose tagging is defined below (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.

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

10. Names, Dates, and Numbers

Table of contents

10.1. Names and Referring Strings

10.2. Dates and Times

10.3. Numbers

Previous 9. Editorial Interventions

Next 11. Lists

Home

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.

Next 10.2. Dates and Times

Home

TEI: Names and Referring Strings¶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="person" key="BENM1">Mr.
   Bennet</rs>, </q> said <rs type="person" key="BENM2">his lady</rs> to him one day,
<q>have
 you heard that <rs type="place" key="NETP1">Netherfield Park</rs> is let at
 last?</q>

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

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

The index element discussed in 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.

Previous 10.1. Names and Referring Strings

Next 10.3. Numbers

Home

TEI: Dates and Times¶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.

These elements have a number of attributes which can be used to provide normalised versions of their values.

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

period | supplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred.
when [att.datable.w3c] | supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.

The when attribute specifies a normalized form for the date or time, using one of the standard formats defined by ISO 8601. Partial dates or times (e.g. ‘1990’, ‘September 1990’, ‘twelvish’) can be expressed by omitting a part of the value supplied, as in the following examples:

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

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

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

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

Previous 10.2. Dates and Times

Home

TEI: Numbers ¶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="cardinal" value="21">twenty-one</num>
<num type="percentage" value="10">ten percent</num>
<num type="percentage" value="10">10%</num>
<num type="ordinal" value="5">5th</num>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

7. Notes

Previous 6. Marking Highlighted Phrases

Next 8. Cross References and Links

Home

All notes, whether printed as footnotes, endnotes, marginalia, or elsewhere, should be marked using the same element:

note contains a note or annotation.

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

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

Examples:

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

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

5. Page and Line Numbers

Previous 4. Encoding the Body

Next 6. Marking Highlighted Phrases

Home

Page and line breaks etc. may be marked with the following elements.

pb (page beginning) marks the beginning of a new page in a paginated document.

lb (line beginning) marks the beginning of a new (typographic) line in some edition or version of a text.

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

These elements mark a single point in the text, not a span of text. The global n attribute should be used to supply the number of the page or line beginning at the tag.

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

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

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

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

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

i. Prefatory note

Next 1. Introduction

Home

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

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

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

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

Lou Burnard, August 2012

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

8. Cross References and Links

Table of contents

8.1. Simple Cross References

8.2. Pointing to other documents

8.3. Special kinds of Linking

Previous 7. Notes

Next 9. Editorial Interventions

Home

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.

Next 8.2. Pointing to other documents

Home

TEI: Simple Cross References¶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 (reference) defines a reference to another location, possibly modified by additional text or comment.

ptr (pointer) 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 identifying the target of the cross reference. The ptr element would be used for a cross reference which is to be indicated by some non-verbal means such as a symbol or icon, or in an electronic text by a button. It is also useful in document production systems, where the formatter can generate the correct verbal form of the cross reference.

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

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

See especially <ptr target="#SEC12"/>.

The value of the target attribute on either element may be the identifier of some other element within the current document. The passage or phrase being pointed at must bear an identifier, and must therefore be tagged as an element of some kind. In the following example, the cross reference is to a div element:

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

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

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

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

anchor (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element.

seg (arbitrary segment) represents any segmentation of text below the ‘chunk’ level.

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

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

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

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

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

Previous 8.1. Simple Cross References

Next 8.3. Special kinds of Linking

Home

TEI: Pointing to other documents¶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)Note: A full definition of this term, defined by the W3C (the consortium which manages the development and maintenance of the World Wide Web), is beyond the scope of this tutorial: however, the most frequently encountered version of a URI is the familiar ‘URL’ used to indicate a web page, such as http://www.tei-c.org/index.xml.

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

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

Previous 8.2. Pointing to other documents

Home

TEI: Special kinds of Linking¶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="sentence" ana="SVO">
 <seg type="lex" ana="#NP1">John</seg>
 <seg type="lex" ana="#VVI">loves</seg>
 <seg type="lex" ana="#NP1">Nancy</seg>
</seg>

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

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

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

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

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

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

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

3. The Structure of a TEI Text

Previous 2. A Short Example

Next 4. Encoding the Body

Home

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

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 xmlns="http://www.tei-c.org/ns/1.0">
 <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 xmlns="http://www.tei-c.org/ns/1.0">
 <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 complete TEI texts, each with its own header. Such a collection is known as a TEI corpus, and may itself have a header:

<teiCorpus xmlns="http://www.tei-c.org/ns/1.0">
 <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 also possible to create a composite of corpora -- that is, one teiCorpus element may contain many nested teiCorpus elements rather than many nested TEI elements, to any depth considered necessary.

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

For example, here are the elements discussed so far:

TEI (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resourceLike class. Multiple TEI elements may be combined to form a teiCorpus element.

teiHeader (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources.

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.

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

Notes

1

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

13. Tables

Previous 12. Bibliographic Citations

Next 14. Figures and Graphics

Home

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:

table contains text displayed in tabular form, in rows and columns.

row contains one row of a table.

cell contains one cell of a table.

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

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

16. Technical Documentation

Table of contents

16.1. Additional Elements for Technical Documents

16.2. Generated Divisions

16.3. Index Generation

16.4. Addresses

Previous 15. Interpretation and Analysis

Next 17. Character Sets, Diacritics, etc.

Home

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.

Next 16.2. Generated Divisions

Home

TEI: Additional Elements for Technical Documents¶16.1. Additional Elements for Technical Documents

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

eg (example) contains any kind of illustrative example.

code contains literal code from some formal language such as a programming language.

ident (identifier) contains an identifier or name for an object of some kind in a formal language. ident is used for tokens such as variable names, class names, type names, function names etc. in formal programming languages.

gi (element name) 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 xml:space="preserve"> CHAR*12 GRTG
          GRTG = 'HELLO WORLD'
          PRINT *, GRTG
          END
        </eg>
</p>
<p>This simple example first declares a variable <ident>GRTG</ident>, in the line
<code>CHAR*12 GRTG</code>, which identifies <ident>GRTG</ident> as consisting of 12 bytes
 of type <ident>CHAR</ident>. To this variable, the value <val>HELLO WORLD</val> is then
 assigned.</p>

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

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

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

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

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

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

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

Previous 16.1. Additional Elements for Technical Documents

Next 16.3. Index Generation

Home

TEI: Generated Divisions¶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>
  <head>Preface</head>
<!-- ... -->
 </div>
</front>
<body>
<!-- ... -->
</body>
<back>
 <div>
  <head>Appendix</head>
<!-- ... -->
 </div>
 <divGen type="index" n="Index"/>
</back>

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

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

Previous 16.2. Generated Divisions

Next 16.4. Addresses

Home

TEI: Index Generation¶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.⁴

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

Previous 16.3. Index Generation

Home

TEI: Addresses¶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 (address line) 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>

Notes

4

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <TEI> (TEI document)

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

3. The Structure of a TEI Text

3. The Structure of a TEI Text

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- [ TEI Header information ]  -->
 </teiHeader>
 <text>
  <front>
<!-- [ front matter ... ] -->
  </front>
  <body>
<!-- [ body of text ... ]  -->
  </body>
  <back>
<!--  [ back matter ...  ] -->
  </back>
 </text>
</TEI>

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <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>

3. The Structure of a TEI Text

<teiCorpus xmlns="http://www.tei-c.org/ns/1.0">
 <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>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <abbr> (abbreviation)

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

9. Editorial Interventions

9. Editorial Interventions

9. Editorial Interventions

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

9. Editorial Interventions

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

9. Editorial Interventions

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <add> (addition)

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

9. Editorial Interventions

9. Editorial Interventions

9.2. Omissions, Deletions, and Additions

The following elements <add resp="#LB">are</add> provided for simple editorial interventions.

9.2. Omissions, Deletions, and Additions

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

9.2. Omissions, Deletions, and Additions

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <addrLine> (address line)

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

16. Technical Documentation

16. Technical Documentation

16. Technical Documentation

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

16. Technical Documentation

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <address>

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

16. Technical Documentation

16. Technical Documentation

16. Technical Documentation

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

16. Technical Documentation

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <anchor> (anchor point)

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

8. Cross References and Links

8. Cross References and Links

8.1. Simple Cross References

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <argument>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <att> (attribute)

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

19. The Electronic Title Page

19. The Electronic Title Page

19.2.3. Reference and Classification Declarations

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <author>

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

12. Bibliographic Citations

19. The Electronic Title Page

12. Bibliographic Citations

12. Bibliographic Citations

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

19. The Electronic Title Page

19. The Electronic Title Page

<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. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <authority> (release authority)

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <availability>

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <back> (back matter)

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

3. The Structure of a TEI Text

15. Interpretation and Analysis

16. Technical Documentation

3. The Structure of a TEI Text

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- [ TEI Header information ]  -->
 </teiHeader>
 <text>
  <front>
<!-- [ front matter ... ] -->
  </front>
  <body>
<!-- [ body of text ... ]  -->
  </body>
  <back>
<!--  [ back matter ...  ] -->
  </back>
 </text>
</TEI>

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <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>

15. Interpretation and Analysis

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

16. Technical Documentation

16. Technical Documentation

<front>
 <titlePage>
<!-- ... -->
 </titlePage>
 <divGen type="toc"/>
 <div>
  <head>Preface</head>
<!-- ... -->
 </div>
</front>
<body>
<!-- ... -->
</body>
<back>
 <div>
  <head>Appendix</head>
<!-- ... -->
 </div>
 <divGen type="index" n="Index"/>
</back>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <bibl> (bibliographic citation)

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

12. Bibliographic Citations

18. Front and Back Matter

19. The Electronic Title Page

12. Bibliographic Citations

12. Bibliographic Citations

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

18. Front and Back Matter

18.1.1. Title Page

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

19. The Electronic Title Page

19. The Electronic Title Page

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

19. The Electronic Title Page

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

19.2.3. Reference and Classification Declarations

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

19.2.3. Reference and Classification Declarations

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <biblScope> (scope of bibliographic reference)

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

12. Bibliographic Citations

12. Bibliographic Citations

12. Bibliographic Citations

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <body> (text body)

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

3. The Structure of a TEI Text

4. Encoding the Body

16. Technical Documentation

3. The Structure of a TEI Text

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- [ TEI Header information ]  -->
 </teiHeader>
 <text>
  <front>
<!-- [ front matter ... ] -->
  </front>
  <body>
<!-- [ body of text ... ]  -->
  </body>
  <back>
<!--  [ back matter ...  ] -->
  </back>
 </text>
</TEI>

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <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>

4. Encoding the Body

4.1. Text Division Elements

<body>
 <div xml:id="WN1" n="I" type="book">
  <div xml:id="WN101" n="I.1" type="chapter">
<!-- ... -->
  </div>
  <div xml:id="WN102" n="I.2" type="chapter">
<!-- ... -->
  </div>
<!-- ... -->
  <div xml:id="WN110" n="I.10"
   type="chapter">
   <div xml:id="WN1101" n="I.10.1"
    type="part">
<!-- ... -->
   </div>
   <div xml:id="WN1102" n="I.10.2"
    type="part">
<!-- ... -->
   </div>
  </div>
<!-- ... -->
 </div>
 <div xml:id="WN2" n="II" type="book">
<!-- ... -->
 </div>
</body>

4.1. Text Division Elements

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

16. Technical Documentation

16. Technical Documentation

<front>
 <titlePage>
<!-- ... -->
 </titlePage>
 <divGen type="toc"/>
 <div>
  <head>Preface</head>
<!-- ... -->
 </div>
</front>
<body>
<!-- ... -->
</body>
<back>
 <div>
  <head>Appendix</head>
<!-- ... -->
 </div>
 <divGen type="index" n="Index"/>
</back>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <byline>

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

18. Front and Back Matter

18. Front and Back Matter

18.1.1. Title Page

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

18.1.1. Title Page

<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.1. Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <catDesc> (category description)

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

19. The Electronic Title Page

19. The Electronic Title Page

19.2.3. Reference and Classification Declarations

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <catRef> (category reference)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

<catRef target="#B.A3 #B.D"/>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <category>

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

19. The Electronic Title Page

19. The Electronic Title Page

19.2.3. Reference and Classification Declarations

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <cell>

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

13. Tables

13. Tables

13. Tables

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <change>

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <choice>

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

9. Editorial Interventions

10. Names, Dates, and Numbers

9. Editorial Interventions

9. Editorial Interventions

... 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. Editorial Interventions

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

10. Names, Dates, and Numbers

10.1. Names and Referring Strings

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <cit> (cited quotation)

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <classCode> (classification code)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

<classCode scheme="http://www.udc.org">410</classCode>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <classDecl> (classification declarations)

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

19. The Electronic Title Page

19. The Electronic Title Page

19.2.3. Reference and Classification Declarations

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <closer>

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

18. Front and Back Matter

18. Front and Back Matter

18.1.2. Prefatory Matter

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <code>

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

16. Technical Documentation

16. Technical Documentation

16. Technical Documentation

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <corr> (correction)

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

9. Editorial Interventions

9. Editorial Interventions

9. Editorial Interventions

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

9. Editorial Interventions

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <creation>

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <date>

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

9. Editorial Interventions

10. Names, Dates, and Numbers

19. The Electronic Title Page

9. Editorial Interventions

9.2. Omissions, Deletions, and Additions

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

10. Names, Dates, and Numbers

10. Names, Dates, and Numbers

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

10. Names, Dates, and Numbers

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>

19. The Electronic Title Page

19. The Electronic Title Page

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

19. The Electronic Title Page

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

19. The Electronic Title Page

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

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <dateline>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <del> (deletion)

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

9. Editorial Interventions

9. Editorial Interventions

9.2. Omissions, Deletions, and Additions

The following elements are provided for <del resp="#LB">for</del> simple editorial interventions.

9.2. Omissions, Deletions, and Additions

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <desc> (description)

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

9. Editorial Interventions

9. Editorial Interventions

9.2. Omissions, Deletions, and Additions

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

9.2. Omissions, Deletions, and Additions

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <distributor>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <div> (text division)

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

2. A Short Example

4. Encoding the Body

8. Cross References and Links

15. Interpretation and Analysis

16. Technical Documentation

18. Front and Back Matter

2. A Short Example

2. A Short Example

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

4. Encoding the Body

4.1. Text Division Elements

<body>
 <div xml:id="WN1" n="I" type="book">
  <div xml:id="WN101" n="I.1" type="chapter">
<!-- ... -->
  </div>
  <div xml:id="WN102" n="I.2" type="chapter">
<!-- ... -->
  </div>
<!-- ... -->
  <div xml:id="WN110" n="I.10"
   type="chapter">
   <div xml:id="WN1101" n="I.10.1"
    type="part">
<!-- ... -->
   </div>
   <div xml:id="WN1102" n="I.10.2"
    type="part">
<!-- ... -->
   </div>
  </div>
<!-- ... -->
 </div>
 <div xml:id="WN2" n="II" type="book">
<!-- ... -->
 </div>
</body>

4.1. Text Division Elements

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

4.2. Headings and Closings

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

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

<div>
 <sp who="#OPI">
  <speaker>The reverend Doctor Opimian</speaker>
  <p>I do not think I have named a single unpresentable fish.</p>
 </sp>
 <sp who="#GRM">
  <speaker>Mr Gryll</speaker>
  <p>Bream, Doctor: there is not much to be said for bream.</p>
 </sp>
 <sp who="#OPI">
  <speaker>The Reverend Doctor Opimian</speaker>
  <p>On the contrary, sir, I think there is much to be said for him. In the first
     place....</p>
  <p>Fish, Miss Gryll -- I could discourse to you on fish by the hour: but for the present I
     will forbear.</p>
 </sp>
</div>

8. Cross References and Links

8.1. Simple Cross References

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

15. Interpretation and Analysis

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

16. Technical Documentation

16. Technical Documentation

<front>
 <titlePage>
<!-- ... -->
 </titlePage>
 <divGen type="toc"/>
 <div>
  <head>Preface</head>
<!-- ... -->
 </div>
</front>
<body>
<!-- ... -->
</body>
<back>
 <div>
  <head>Appendix</head>
<!-- ... -->
 </div>
 <divGen type="index" n="Index"/>
</back>

18. Front and Back Matter

18.1.2. Prefatory Matter

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <divGen> (automatically generated text division)

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

16. Technical Documentation

16. Technical Documentation

16. Technical Documentation

<front>
 <titlePage>
<!-- ... -->
 </titlePage>
 <divGen type="toc"/>
 <div>
  <head>Preface</head>
<!-- ... -->
 </div>
</front>
<body>
<!-- ... -->
</body>
<back>
 <div>
  <head>Appendix</head>
<!-- ... -->
 </div>
 <divGen type="index" n="Index"/>
</back>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <docAuthor> (document author)

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

18. Front and Back Matter

18. Front and Back Matter

18.1.1. Title Page

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

18.1.1. Title Page

<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.1. Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <docDate> (document date)

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

18. Front and Back Matter

18. Front and Back Matter

18.1.1. Title Page

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

18.1.1. Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <docEdition> (document edition)

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

18. Front and Back Matter

18. Front and Back Matter

18.1.1. Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <docImprint> (document imprint)

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

18. Front and Back Matter

18. Front and Back Matter

18.1.1. Title Page

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

18.1.1. Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <docTitle> (document title)

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

18. Front and Back Matter

18. Front and Back Matter

18.1.1. Title Page

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

18.1.1. Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <edition>

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <editionStmt> (edition statement)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <editor>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <editorialDecl> (editorial practice declaration)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <eg> (example)

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

16. Technical Documentation

16. Technical Documentation

16. Technical Documentation

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <emph> (emphasized)

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

4. Encoding the Body

4. Encoding the Body

4.3. Prose, Verse and Drama

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <encodingDesc> (encoding description)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <epigraph>

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

18. Front and Back Matter

18. Front and Back Matter

18.1.1. Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <expan> (expansion)

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

9. Editorial Interventions

9. Editorial Interventions

9. Editorial Interventions

<expan>per</expan>

9. Editorial Interventions

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

9. Editorial Interventions

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <extent>

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

<extent>4532
 bytes</extent>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <figDesc> (description of figure)

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

14. Figures and Graphics

14. Figures and Graphics

14. Figures and Graphics

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <figure>

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

14. Figures and Graphics

14. Figures and Graphics

14. Figures and Graphics

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

14. Figures and Graphics

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <fileDesc> (file description)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

<teiHeader>
 <fileDesc>
  <titleStmt>
<!-- bibliographic description of the digital resource -->
  </titleStmt>
  <publicationStmt>
<!-- information about how the resource is distributed -->
  </publicationStmt>
  <sourceDesc>
<!-- information about the sources from which the digital resource is derived -->
  </sourceDesc>
 </fileDesc>
</teiHeader>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <foreign>

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

6. Marking Highlighted Phrases

6. Marking Highlighted Phrases

6.1. Changes of Typeface, etc.

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

6.3. Foreign Words or Expressions

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <formula>

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

16. Technical Documentation

16. Technical Documentation

16. Technical Documentation

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <front> (front matter)

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

3. The Structure of a TEI Text

16. Technical Documentation

3. The Structure of a TEI Text

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- [ TEI Header information ]  -->
 </teiHeader>
 <text>
  <front>
<!-- [ front matter ... ] -->
  </front>
  <body>
<!-- [ body of text ... ]  -->
  </body>
  <back>
<!--  [ back matter ...  ] -->
  </back>
 </text>
</TEI>

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <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>

16. Technical Documentation

16. Technical Documentation

<front>
 <titlePage>
<!-- ... -->
 </titlePage>
 <divGen type="toc"/>
 <div>
  <head>Preface</head>
<!-- ... -->
 </div>
</front>
<body>
<!-- ... -->
</body>
<back>
 <div>
  <head>Appendix</head>
<!-- ... -->
 </div>
 <divGen type="index" n="Index"/>
</back>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <funder> (funding body)

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <gap>

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

9. Editorial Interventions

9. Editorial Interventions

9.2. Omissions, Deletions, and Additions

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

9.2. Omissions, Deletions, and Additions

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

9.2. Omissions, Deletions, and Additions

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <gi> (element name)

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

16. Technical Documentation

19. The Electronic Title Page

16. Technical Documentation

16.3. Index Generation

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

19. The Electronic Title Page

19.2.3. Reference and Classification Declarations

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <gloss>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <graphic>

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

14. Figures and Graphics

14. Figures and Graphics

14. Figures and Graphics

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

14. Figures and Graphics

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

14. Figures and Graphics

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <group>

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

3. The Structure of a TEI Text

3. The Structure of a TEI Text

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <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>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <head> (heading)

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

4. Encoding the Body

8. Cross References and Links

11. Lists

14. Figures and Graphics

16. Technical Documentation

18. Front and Back Matter

4. Encoding the Body

4.2. Headings and Closings

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

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

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

8. Cross References and Links

8.1. Simple Cross References

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

11. Lists

11. Lists

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

11. Lists

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

14. Figures and Graphics

14. Figures and Graphics

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

14. Figures and Graphics

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

16. Technical Documentation

16. Technical Documentation

<front>
 <titlePage>
<!-- ... -->
 </titlePage>
 <divGen type="toc"/>
 <div>
  <head>Preface</head>
<!-- ... -->
 </div>
</front>
<body>
<!-- ... -->
</body>
<back>
 <div>
  <head>Appendix</head>
<!-- ... -->
 </div>
 <divGen type="index" n="Index"/>
</back>

18. Front and Back Matter

18.1.2. Prefatory Matter

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <hi> (highlighted)

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

6. Marking Highlighted Phrases

9. Editorial Interventions

18. Front and Back Matter

6. Marking Highlighted Phrases

6.1. Changes of Typeface, etc.

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

6.1. Changes of Typeface, etc.

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

9. Editorial Interventions

9. Editorial Interventions

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

18. Front and Back Matter

18.1.1. Title Page

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

18.1.2. Prefatory Matter

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ident> (identifier)

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

16. Technical Documentation

16. Technical Documentation

16. Technical Documentation

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <idno> (identifier)

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <imprimatur>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <index> (index entry)

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

10. Names, Dates, and Numbers

16. Technical Documentation

10. Names, Dates, and Numbers

10.1. Names and Referring Strings

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

16. Technical Documentation

16.3. Index Generation

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

16.3. Index Generation

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <interp> (interpretation)

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

15. Interpretation and Analysis

15. Interpretation and Analysis

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <interpGrp> (interpretation group)

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

15. Interpretation and Analysis

15. Interpretation and Analysis

15. Interpretation and Analysis

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <item>

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

4. Encoding the Body

11. Lists

19. The Electronic Title Page

4. Encoding the Body

4.3. Prose, Verse and Drama

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

11. Lists

11. Lists

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

11. Lists

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

11. Lists

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

11. Lists

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

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <keywords>

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <l> (verse line)

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

4. Encoding the Body

7. Notes

10. Names, Dates, and Numbers

16. Technical Documentation

4. Encoding the Body

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

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

7. Notes

7. Notes

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

10. Names, Dates, and Numbers

10. Names, Dates, and Numbers

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

16. Technical Documentation

16.3. Index Generation

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

16.3. Index Generation

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <label>

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

11. Lists

11. Lists

11. Lists

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

11. Lists

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

11. Lists

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <langUsage> (language usage)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <language>

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <lb> (line beginning)

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <lg> (line group)

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

4. Encoding the Body

7. Notes

4. Encoding the Body

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

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

7. Notes

7. Notes

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <licence>

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <list>

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

4. Encoding the Body

11. Lists

19. The Electronic Title Page

4. Encoding the Body

4.3. Prose, Verse and Drama

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

11. Lists

11. Lists

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

11. Lists

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

11. Lists

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

11. Lists

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

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <listBibl> (citation list)

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <mentioned>

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

6. Marking Highlighted Phrases

7. Notes

6. Marking Highlighted Phrases

6.3. Foreign Words or Expressions

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

7. Notes

7. Notes

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <milestone>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <name> (name, proper noun)

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

4. Encoding the Body

8. Cross References and Links

9. Editorial Interventions

10. Names, Dates, and Numbers

16. Technical Documentation

18. Front and Back Matter

19. The Electronic Title Page

4. Encoding the Body

4.3. Prose, Verse and Drama

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

8. Cross References and Links

8.3. Special kinds of Linking

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

9. Editorial Interventions

9.2. Omissions, Deletions, and Additions

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

10. Names, Dates, and Numbers

10.1. Names and Referring Strings

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

10.1. Names and Referring Strings

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

16. Technical Documentation

16. Technical Documentation

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

18. Front and Back Matter

18.1.1. Title Page

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

18.1.1. Title Page

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

18.1.2. Prefatory Matter

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

19. The Electronic Title Page

19. The Electronic Title Page

<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. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <note>

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

7. Notes

7. Notes

7. Notes

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

7. Notes

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <notesStmt> (notes statement)

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <num> (number)

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

10. Names, Dates, and Numbers

10. Names, Dates, and Numbers

10. Names, Dates, and Numbers

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <opener>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <orig> (original form)

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

9. Editorial Interventions

9. Editorial Interventions

9. Editorial Interventions

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

9. Editorial Interventions

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <p> (paragraph)

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

2. A Short Example

4. Encoding the Body

5. Page and Line Numbers

6. Marking Highlighted Phrases

7. Notes

8. Cross References and Links

9. Editorial Interventions

10. Names, Dates, and Numbers

11. Lists

13. Tables

15. Interpretation and Analysis

16. Technical Documentation

18. Front and Back Matter

19. The Electronic Title Page

2. A Short Example

2. A Short Example

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

4. Encoding the Body

4.2. Headings and Closings

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

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

<div>
 <sp who="#OPI">
  <speaker>The reverend Doctor Opimian</speaker>
  <p>I do not think I have named a single unpresentable fish.</p>
 </sp>
 <sp who="#GRM">
  <speaker>Mr Gryll</speaker>
  <p>Bream, Doctor: there is not much to be said for bream.</p>
 </sp>
 <sp who="#OPI">
  <speaker>The Reverend Doctor Opimian</speaker>
  <p>On the contrary, sir, I think there is much to be said for him. In the first
     place....</p>
  <p>Fish, Miss Gryll -- I could discourse to you on fish by the hour: but for the present I
     will forbear.</p>
 </sp>
</div>

5. Page and Line Numbers

5. Page and Line Numbers

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

6. Marking Highlighted Phrases

6.1. Changes of Typeface, etc.

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

6.1. Changes of Typeface, etc.

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

6.1. Changes of Typeface, etc.

<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

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

6.2. Quotations and Related Features

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

6.3. Foreign Words or Expressions

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

7. Notes

7. Notes

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

8. Cross References and Links

8.1. Simple Cross References

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

8.3. Special kinds of Linking

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

9. Editorial Interventions

9.2. Omissions, Deletions, and Additions

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

9.2. Omissions, Deletions, and Additions

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

10. Names, Dates, and Numbers

10.1. Names and Referring Strings

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

11. Lists

11. Lists

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

13. Tables

13. Tables

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

15. Interpretation and Analysis

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

16. Technical Documentation

16. Technical Documentation

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

18. Front and Back Matter

18.1.2. Prefatory Matter

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

19. The Electronic Title Page

19. The Electronic Title Page

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

19. The Electronic Title Page

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

19. The Electronic Title Page

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

19.2.3. Reference and Classification Declarations

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <pb> (page beginning)

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

2. A Short Example

5. Page and Line Numbers

14. Figures and Graphics

15. Interpretation and Analysis

2. A Short Example

2. A Short Example

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

5. Page and Line Numbers

5. Page and Line Numbers

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

14. Figures and Graphics

14. Figures and Graphics

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

14. Figures and Graphics

<text>
 <pb facs="page1.png" n="1"/>
<!-- text contained on page 1 is encoded here -->
 <pb facs="page2.png" n="2"/>
<!-- text contained on page 2 is encoded here -->
</text>

15. Interpretation and Analysis

15. Interpretation and Analysis

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <pc> (punctuation character)

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

15. Interpretation and Analysis

15. Interpretation and Analysis

15. Interpretation and Analysis

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <postscript>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <principal> (principal researcher)

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <profileDesc> (text-profile description)

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <projectDesc> (project description)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ptr> (pointer)

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

8. Cross References and Links

8. Cross References and Links

8.1. Simple Cross References

See especially <ptr target="#SEC12"/>.

8.1. Simple Cross References

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <pubPlace> (publication place)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <publicationStmt> (publication statement)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

<teiHeader>
 <fileDesc>
  <titleStmt>
<!-- bibliographic description of the digital resource -->
  </titleStmt>
  <publicationStmt>
<!-- information about how the resource is distributed -->
  </publicationStmt>
  <sourceDesc>
<!-- information about the sources from which the digital resource is derived -->
  </sourceDesc>
 </fileDesc>
</teiHeader>

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <publisher>

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <q> (quoted)

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

2. A Short Example

6. Marking Highlighted Phrases

8. Cross References and Links

10. Names, Dates, and Numbers

15. Interpretation and Analysis

18. Front and Back Matter

2. A Short Example

2. A Short Example

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

6. Marking Highlighted Phrases

6.2. Quotations and Related Features

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

6.2. Quotations and Related Features

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

6.2. Quotations and Related Features

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

8. Cross References and Links

8.3. Special kinds of Linking

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

10. Names, Dates, and Numbers

10.1. Names and Referring Strings

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

10.1. Names and Referring Strings

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>

10.1. Names and Referring Strings

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

10.1. Names and Referring Strings

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

15. Interpretation and Analysis

15. Interpretation and Analysis

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

18. Front and Back Matter

18.1.1. Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <ref> (reference)

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

8. Cross References and Links

8. Cross References and Links

8.1. Simple Cross References

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

8.1. Simple Cross References

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

8.1. Simple Cross References

 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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <refsDecl> (references declaration)

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

19. The Electronic Title Page

19. The Electronic Title Page

19.2.3. Reference and Classification Declarations

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <reg> (regularization)

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

9. Editorial Interventions

10. Names, Dates, and Numbers

9. Editorial Interventions

9. Editorial Interventions

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

9. Editorial Interventions

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

10. Names, Dates, and Numbers

10.1. Names and Referring Strings

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <relatedItem>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <resp> (responsibility)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <respStmt> (statement of responsibility)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <revisionDesc> (revision description)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <row>

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

13. Tables

13. Tables

13. Tables

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <rs> (referencing string)

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

10. Names, Dates, and Numbers

10. Names, Dates, and Numbers

10.1. Names and Referring Strings

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

10.1. Names and Referring Strings

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>

10.1. Names and Referring Strings

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

10.1. Names and Referring Strings

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <s> (s-unit)

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

15. Interpretation and Analysis

15. Interpretation and Analysis

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

15. Interpretation and Analysis

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <salute> (salutation)

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

18. Front and Back Matter

18. Front and Back Matter

18.1.2. Prefatory Matter

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <samplingDecl> (sampling declaration)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <seg> (arbitrary segment)

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

8. Cross References and Links

15. Interpretation and Analysis

8. Cross References and Links

8.1. Simple Cross References

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

8.3. Special kinds of Linking

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

8.3. Special kinds of Linking

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

8.3. Special kinds of Linking

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

15. Interpretation and Analysis

15. Interpretation and Analysis

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <seriesStmt> (series statement)

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <sic> (Latin for thus or so)

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

9. Editorial Interventions

10. Names, Dates, and Numbers

9. Editorial Interventions

9. Editorial Interventions

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

9. Editorial Interventions

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

10. Names, Dates, and Numbers

10.1. Names and Referring Strings

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <signed> (signature)

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

18. Front and Back Matter

18. Front and Back Matter

18.1.2. Prefatory Matter

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <soCalled>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <sourceDesc> (source description)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

<teiHeader>
 <fileDesc>
  <titleStmt>
<!-- bibliographic description of the digital resource -->
  </titleStmt>
  <publicationStmt>
<!-- information about how the resource is distributed -->
  </publicationStmt>
  <sourceDesc>
<!-- information about the sources from which the digital resource is derived -->
  </sourceDesc>
 </fileDesc>
</teiHeader>

19. The Electronic Title Page

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

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <sp> (speech)

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

4. Encoding the Body

4. Encoding the Body

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

<div>
 <sp who="#OPI">
  <speaker>The reverend Doctor Opimian</speaker>
  <p>I do not think I have named a single unpresentable fish.</p>
 </sp>
 <sp who="#GRM">
  <speaker>Mr Gryll</speaker>
  <p>Bream, Doctor: there is not much to be said for bream.</p>
 </sp>
 <sp who="#OPI">
  <speaker>The Reverend Doctor Opimian</speaker>
  <p>On the contrary, sir, I think there is much to be said for him. In the first
     place....</p>
  <p>Fish, Miss Gryll -- I could discourse to you on fish by the hour: but for the present I
     will forbear.</p>
 </sp>
</div>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <speaker>

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

4. Encoding the Body

4. Encoding the Body

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

<div>
 <sp who="#OPI">
  <speaker>The reverend Doctor Opimian</speaker>
  <p>I do not think I have named a single unpresentable fish.</p>
 </sp>
 <sp who="#GRM">
  <speaker>Mr Gryll</speaker>
  <p>Bream, Doctor: there is not much to be said for bream.</p>
 </sp>
 <sp who="#OPI">
  <speaker>The Reverend Doctor Opimian</speaker>
  <p>On the contrary, sir, I think there is much to be said for him. In the first
     place....</p>
  <p>Fish, Miss Gryll -- I could discourse to you on fish by the hour: but for the present I
     will forbear.</p>
 </sp>
</div>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <sponsor>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <stage> (stage direction)

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

4. Encoding the Body

4. Encoding the Body

4.3. Prose, Verse and Drama

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

4.3. Prose, Verse and Drama

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <table>

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

13. Tables

13. Tables

13. Tables

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <taxonomy>

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

19. The Electronic Title Page

19. The Electronic Title Page

19.2.3. Reference and Classification Declarations

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

19.2.3. Reference and Classification Declarations

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <teiCorpus>

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

3. The Structure of a TEI Text

3. The Structure of a TEI Text

3. The Structure of a TEI Text

<teiCorpus xmlns="http://www.tei-c.org/ns/1.0">
 <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>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <teiHeader> (TEI header)

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

3. The Structure of a TEI Text

19. The Electronic Title Page

3. The Structure of a TEI Text

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- [ TEI Header information ]  -->
 </teiHeader>
 <text>
  <front>
<!-- [ front matter ... ] -->
  </front>
  <body>
<!-- [ body of text ... ]  -->
  </body>
  <back>
<!--  [ back matter ...  ] -->
  </back>
 </text>
</TEI>

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <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>

3. The Structure of a TEI Text

<teiCorpus xmlns="http://www.tei-c.org/ns/1.0">
 <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>

19. The Electronic Title Page

19. The Electronic Title Page

<teiHeader>
 <fileDesc>
  <titleStmt>
<!-- bibliographic description of the digital resource -->
  </titleStmt>
  <publicationStmt>
<!-- information about how the resource is distributed -->
  </publicationStmt>
  <sourceDesc>
<!-- information about the sources from which the digital resource is derived -->
  </sourceDesc>
 </fileDesc>
</teiHeader>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <term>

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

6. Marking Highlighted Phrases

9. Editorial Interventions

10. Names, Dates, and Numbers

16. Technical Documentation

6. Marking Highlighted Phrases

6.3. Foreign Words or Expressions

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

9. Editorial Interventions

9.2. Omissions, Deletions, and Additions

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

10. Names, Dates, and Numbers

10.1. Names and Referring Strings

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

16. Technical Documentation

16.3. Index Generation

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

16.3. Index Generation

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <text>

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

3. The Structure of a TEI Text

14. Figures and Graphics

3. The Structure of a TEI Text

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- [ TEI Header information ]  -->
 </teiHeader>
 <text>
  <front>
<!-- [ front matter ... ] -->
  </front>
  <body>
<!-- [ body of text ... ]  -->
  </body>
  <back>
<!--  [ back matter ...  ] -->
  </back>
 </text>
</TEI>

3. The Structure of a TEI Text

<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <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>

3. The Structure of a TEI Text

<teiCorpus xmlns="http://www.tei-c.org/ns/1.0">
 <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>

14. Figures and Graphics

14. Figures and Graphics

<text>
 <pb facs="page1.png" n="1"/>
<!-- text contained on page 1 is encoded here -->
 <pb facs="page2.png" n="2"/>
<!-- text contained on page 2 is encoded here -->
</text>

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <textClass> (text classification)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <time>

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

10. Names, Dates, and Numbers

10. Names, Dates, and Numbers

10. Names, Dates, and Numbers

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <title>

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

6. Marking Highlighted Phrases

8. Cross References and Links

12. Bibliographic Citations

18. Front and Back Matter

19. The Electronic Title Page

6. Marking Highlighted Phrases

6.1. Changes of Typeface, etc.

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

6.3. Foreign Words or Expressions

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

8. Cross References and Links

8.3. Special kinds of Linking

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

12. Bibliographic Citations

12. Bibliographic Citations

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

18. Front and Back Matter

18.1.1. Title Page

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

19. The Electronic Title Page

19. The Electronic Title Page

<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. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <titlePage> (title page)

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

16. Technical Documentation

18. Front and Back Matter

16. Technical Documentation

16. Technical Documentation

<front>
 <titlePage>
<!-- ... -->
 </titlePage>
 <divGen type="toc"/>
 <div>
  <head>Preface</head>
<!-- ... -->
 </div>
</front>
<body>
<!-- ... -->
</body>
<back>
 <div>
  <head>Appendix</head>
<!-- ... -->
 </div>
 <divGen type="index" n="Index"/>
</back>

18. Front and Back Matter

18.1.1. Title Page

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

18.1.1. Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <titlePart>

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

18. Front and Back Matter

18. Front and Back Matter

18.1.1. Title Page

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

18.1.1. Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <titleStmt> (title statement)

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

19. The Electronic Title Page

19. The Electronic Title Page

19. The Electronic Title Page

<teiHeader>
 <fileDesc>
  <titleStmt>
<!-- bibliographic description of the digital resource -->
  </titleStmt>
  <publicationStmt>
<!-- information about how the resource is distributed -->
  </publicationStmt>
  <sourceDesc>
<!-- information about the sources from which the digital resource is derived -->
  </sourceDesc>
 </fileDesc>
</teiHeader>

19. The Electronic Title Page

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <trailer>

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <unclear>

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

9. Editorial Interventions

9. Editorial Interventions

9.2. Omissions, Deletions, and Additions

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <val> (value)

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

16. Technical Documentation

16. Technical Documentation

16. Technical Documentation

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

P5: Guidelines for Electronic Text Encoding and Interchange

§

Home

Example: <w> (word)

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

15. Interpretation and Analysis

15. Interpretation and Analysis

15. Interpretation and Analysis

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

15. Interpretation and Analysis

...<w ana="#VBD" lemma="be"
 lemmaRef="http://www.myLexicon.com/be">was</w> ...

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

Appendix A List of Elements Described

Home

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

Schema tei_lite: changed components

Schema tei_lite: unchanged components

abbr: (abbreviation) contains an abbreviation of any sort. [3.5.5. Abbreviations and Their Expansions]

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

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

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

anchor: (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.5. Correspondence and Alignment]

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

att: (attribute) contains the name of an attribute appearing within running text. [22. Documentation Elements]

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

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

att.breaking: provides an attribute to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.10.3. Milestone Elements]

att.canonical: provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]

att.citing: provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]

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

att.datcat: provides the dcr:datacat and dcr:ValueDatacat attributes which are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by the ISO 12620:2009 standard and stored in the Web repository called ISOCat at http://www.isocat.org/. [9.5.2. Lexical View 18.3. Other Atomic Feature Values]

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

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. [15.3. Associating Contextual Information with a Text]

att.dimensions: provides attributes for describing the size of physical objects.

att.divLike: provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure]

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

att.edition: provides attributes identifying the source edition from which some encoded feature derives.

att.editLike: provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.4. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]

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

att.global.analytic: provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations]

att.global.facs: provides an attribute used to express correspondence between an element containing transcribed text and all or part of an image representing that text. [11.1. Digital Facsimiles]

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

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

att.interpLike: provides attributes for elements which represent a formal analysis or interpretation. [17.2. Global Attributes for Simple Analyses]

att.linguistic: provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically w and pc in the analysis module. [17.4.2. Lightweight Linguistic Annotation]

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

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

att.naming: provides attributes common to elements which refer to named persons, places, organizations etc. [3.5.1. Referring Strings 13.3.6. Names and Nyms]

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

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

att.placement: provides attributes for describing where on the source page or object a textual element appears. [3.4.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions]

att.pointing: provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.6. Simple Links and Cross-References]

att.ranging: provides attributes for describing numerical ranges.

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

att.segLike: provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]

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

att.spanning: provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [11.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]

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

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

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

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

att.typed: provides attributes which can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.5.1. Referring Strings 3.6. Simple Links and Cross-References 3.5.5. Abbreviations and Their Expansions 3.12.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.4. Modification of Attribute and Attribute Value Lists]

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

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

authority: (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]

availability: supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]

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

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

biblScope: (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.5. Scopes and Ranges in Bibliographic Citations]

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

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

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>. [2.3.7. The Classification Declaration]

category: contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]

catRef: (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]

cell: contains one cell of a table. [14.1.1. TEI Tables]

change: documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]

choice: groups a number of alternative encodings for the same point in a text. [3.4. Simple Editorial Changes]

classCode: (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]

classDecl: (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]

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

code: contains literal code from some formal language such as a programming language. [22.1.1. Phrase Level Terms]

corr: (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.4.1. Apparent Errors]

creation: contains information about the creation of a text. [2.4.1. Creation 2.4. The Profile Description]

date: contains a date in any format. [3.5.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.3.7. Dates and Times]

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

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

desc: (description) contains a brief description of the object documented by its parent element, typically a documentation element or an entity. [22.4.1. Description of Components]

distributor: supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]

div: (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]

divGen: (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.8.2. Index Entries]

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

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

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

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

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

edition: describes the particularities of one edition of a text. [2.2.2. The Edition Statement]

editionStmt: (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]

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

eg: (example) contains any kind of illustrative example. [22.5. Element Specifications 22.5.3. Attribute List Specification]

emph: (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]

encodingDesc: (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]

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

expan: (expansion) contains the expansion of an abbreviation. [3.5.5. Abbreviations and Their Expansions]

extent: describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]

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. [14.4. Specific Elements for Graphic Images]

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

fileDesc: (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]

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

formula: contains a mathematical or other formula. [14.2. Formulæ and Mathematical Expressions]

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

funder: (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]

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

gi: (element name) contains the name (generic identifier) of an element. [22. Documentation Elements 22.5. Element Specifications]

gloss: identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.3.4. Terms, Glosses, Equivalents, and Descriptions 22.4.1. Description of Components]

graphic: indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.9. Graphics and Other Non-textual Components 11.1. Digital Facsimiles]

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

head: (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]

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

ident: (identifier) contains an identifier or name for an object of some kind in a formal language. ident is used for tokens such as variable names, class names, type names, function names etc. in formal programming languages. [22.1.1. Phrase Level Terms]

idno: (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.11.2.4. Imprint, Size of a Document, and Reprint Information]

imprimatur: contains a formal statement authorizing the publication of a work, sometimes required to appear on a title page or its verso. [4.6. Title Pages]

index: (index entry) marks a location to be indexed for whatever purpose. [3.8.2. Index Entries]

interp: (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. [17.3. Spans and Interpretations]

interpGrp: (interpretation group) collects together a set of related interpretations which share responsibility or type. [17.3. Spans and Interpretations]

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

keywords: contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]

l: (verse line) contains a single, possibly incomplete, line of verse. [3.12.1. Core Tags for Verse 3.12. Passages of Verse or Drama 7.2.5. Speech Contents]

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

language: characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]

langUsage: (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]

lb: (line beginning) marks the beginning of a new (typographic) line in some edition or version of a text. [3.10.3. Milestone Elements 7.2.5. Speech Contents]

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

licence: contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]

list: contains any sequence of items organized as a list. [3.7. Lists]

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

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

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

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

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

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

mentioned: marks words or phrases mentioned, not used. [3.3.3. Quotation]

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

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

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

model.availabilityPart: groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]

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

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

model.catDescPart: groups component elements of the TEI header Category Description.

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

model.choicePart: groups elements (other than choice itself) which can be used within a choice alternation. [3.4. Simple Editorial Changes]

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

model.dateLike: groups elements containing temporal expressions. [3.5.4. Dates and Times 13.3.7. Dates and Times]

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

model.div1Like: groups top-level structural divisions.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

model.pLike: groups paragraph-like elements.

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

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

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

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

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

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

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

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

model.publicationStmtPart.agency: groups the child elements of a publicationStmt element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]

model.publicationStmtPart.detail: groups the agency-specific child elements of the publicationStmt element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]

model.qLike: groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. Highlighting and Quotation]

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

model.resourceLike: groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]

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

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

model.sourceDescPart: groups elements which may be used inside sourceDesc and appear multiple times.

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

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

model.teiHeaderPart: groups high level elements which may appear more than once in a TEI header.

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

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

note: contains a note or annotation. [3.8.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.11.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]

notesStmt: (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description]

num: (number) contains a number, written in any form. [3.5.3. Numbers and Measures]

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

orig: (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.4.2. Regularization and Normalization 12. Critical Apparatus]

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

pb: (page beginning) marks the beginning of a new page in a paginated document. [3.10.3. Milestone Elements]

pc: (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [17.1.2. Below the Word Level 17.4.2. Lightweight Linguistic Annotation]

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

principal: (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement]

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. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]

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. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]

ptr: (pointer) defines a pointer to another location. [3.6. Simple Links and Cross-References 16.1. Links]

publicationStmt: (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]

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

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

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

ref: (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. Simple Links and Cross-References 16.1. Links]

refsDecl: (references declaration) specifies how canonical references are constructed for this text. [2.3.6.3. Milestone Method 2.3. The Encoding Description 2.3.6. The Reference System Declaration]

reg: (regularization) contains a reading which has been regularized or normalized in some sense. [3.4.2. Regularization and Normalization 12. Critical Apparatus]

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. [3.11.2.7. Related Items]

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

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

revisionDesc: (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]

row: contains one row of a table. [14.1.1. TEI Tables]

rs: (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.5.1. Referring Strings]

s: (s-unit) contains a sentence-like division of a text. [17.1. Linguistic Segment Categories 8.4.1. Segmentation]

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

samplingDecl: (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]

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

seriesStmt: (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]

sic: (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.4.1. Apparent Errors]

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

soCalled: 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. [3.3.3. Quotation]

sourceDesc: (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]

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

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

sponsor: specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]

stage: (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.12.2. Core Tags for Drama 3.12. Passages of Verse or Drama 7.2.4. Stage Directions]

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

taxonomy: defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]

teiCorpus: 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. [4. Default Text Structure 15.1. Varieties of Composite Text]

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

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

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

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

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

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

teidata.name: defines the range of attribute values expressed as an XML Name.

teidata.namespace: defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.

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

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

teidata.pattern: defines attribute values which are expressed as a regular expression.

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

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

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

teidata.replacement: defines attribute values which contain a replacement template.

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

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

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

teidata.unboundedInt: defines an attribute value which can be either any non-negative integer or the string "unbounded".

teidata.version: defines the range of attribute values which may be used to specify a TEI or Unicode version number.

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

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

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

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

teidata.xTruthValue: (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.

teiHeader: (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]

term: contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4. Terms, Glosses, Equivalents, and Descriptions]

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

textClass: (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]

time: contains a phrase defining a time of day in any format. [3.5.4. Dates and Times]

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

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

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

titleStmt: (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]

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

unclear: contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. Damage, Illegibility, and Supplied Text 3.4.3. Additions, Deletions, and Omissions]

val: (value) contains a single attribute value. [22. Documentation Elements 22.5.3. Attribute List Specification]

w: (word) represents a grammatical (not necessarily orthographic) word. [17.1. Linguistic Segment Categories 17.4.2. Lightweight Linguistic Annotation]

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

Table of contents

i. Prefatory note

1. Introduction

2. A Short Example

3. The Structure of a TEI Text

4. Encoding the Body

4.1. Text Division Elements

4.2. Headings and Closings

4.3. Prose, Verse and Drama

5. Page and Line Numbers

6. Marking Highlighted Phrases

6.1. Changes of Typeface, etc.

6.2. Quotations and Related Features

6.3. Foreign Words or Expressions

7. Notes

8. Cross References and Links

8.1. Simple Cross References

8.2. Pointing to other documents

8.3. Special kinds of Linking

9. Editorial Interventions

9.1. Correction and Normalization

9.2. Omissions, Deletions, and Additions

9.3. Abbreviations and their Expansion

10. Names, Dates, and Numbers

10.1. Names and Referring Strings

10.2. Dates and Times

10.3. Numbers

11. Lists

12. Bibliographic Citations

13. Tables

14. Figures and Graphics

15. Interpretation and Analysis

15.1. Orthographic Sentences

15.2. Words and punctuation

15.3. General-Purpose Interpretation Elements

16. Technical Documentation

16.1. Additional Elements for Technical Documents

16.2. Generated Divisions

16.3. Index Generation

16.4. Addresses

17. Character Sets, Diacritics, etc.

18. Front and Back Matter

18.1. Front Matter

18.1.1. Title Page

18.1.2. Prefatory Matter

18.2. Back Matter

18.2.1. Structural Divisions of Back Matter

19. The Electronic Title Page

19.1. The File Description

19.1.1. The Title Statement

19.1.2. The Edition Statement

19.1.3. The Extent Statement

19.1.4. The Publication Statement

19.1.5. Series and Notes Statements

19.1.6. The Source Description

19.2. The Encoding Description

19.2.1. Project and Sampling Descriptions

19.2.2. Editorial Declarations

19.2.3. Reference and Classification Declarations

19.3. The Profile Description

19.4. The Revision Description

Appendix A List of Elements Described

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 http://www.tei-c.org/.

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

§

Home

<TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resourceLike class. Multiple TEI elements may be combined to form a teiCorpus element. [4. Default Text Structure 15.1. Varieties of Composite Text]

Module | textstructure

Attributes
Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)

version version¶

Status
Optional

Contained by | core: teiCorpus
May contain | header: teiHeader textstructure: text
Note | This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute.

Example

<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>The shortest TEI Document Imaginable</title>
   </titleStmt>
   <publicationStmt>
    <p>First published as part of TEI P2, this is the P5
         version using a name space.</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>

Show all

Example

<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>A TEI Document containing four page images </title>
   </titleStmt>
   <publicationStmt>
    <p>Unpublished demonstration file.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <facsimile>
  <graphic url="page1.png"/>
  <graphic url="page2.png"/>
  <graphic url="page3.png"/>
  <graphic url="page4.png"/>
 </facsimile>
</TEI>

Show all

Schematron

<s:ns prefix="tei"
 uri="http://www.tei-c.org/ns/1.0"/>
<s:ns prefix="xs"
 uri="http://www.w3.org/2001/XMLSchema"/>

Schematron

<s:ns prefix="rng"
 uri="http://relaxng.org/ns/structure/1.0"/>

Content model

<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="teiHeader"/>
  <classRef key="model.resourceLike"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>

Schema Declaration

element TEI { attribute version { text }?, ( teiHeader, model.resourceLike+ ) }

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

§

Home

att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.5.4. Dates and Times 13.3.7. Dates and Times]
Module | tei
Members | change creation date idno licence name resp time title

Attributes
Attributes att.datable.w3c (@when)

period 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
teidata.pointer

Note

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

§

Home

att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.5.4. Dates and Times 13.3.7. Dates and Times]
Module | tei
Members | att.datable [change creation date idno licence name resp time title]

Attributes
Attributes

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

Status
Optional

Datatype
teidata.temporal.w3c

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

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

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

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

Schematron

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

Schematron

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

Schematron

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

Example

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

Note

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

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

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

§

Home

att.global

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

Module | tei

Members
TEI abbr add addrLine address anchor argument att author authority availability back bibl biblScope body byline catDesc catRef category cell change choice cit classCode classDecl closer code corr creation date dateline del desc distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl eg emph encodingDesc epigraph expan extent figDesc figure fileDesc foreign formula front funder gap gi gloss graphic group head hi ident idno imprimatur index interp interpGrp item keywords l label langUsage language lb lg licence list listBibl mentioned milestone name note notesStmt num opener orig p pb pc postscript principal profileDesc projectDesc ptr pubPlace publicationStmt publisher q ref refsDecl reg relatedItem resp respStmt revisionDesc row rs s salute samplingDecl seg seriesStmt sic signed soCalled sourceDesc sp speaker sponsor stage table taxonomy teiCorpus teiHeader term text textClass time title titlePage titlePart titleStmt trailer unclear val w

Attributes
Attributes att.global.rendition (@rend) att.global.linking (@corresp, @next, @prev) att.global.analytic (@ana) att.global.facs (@facs) att.global.responsibility (@cert, @resp) att.global.source (@source)

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

Status
Optional

Datatype
ID

Note

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

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

Status
Optional

Datatype
teidata.text

Note

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

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

Status
Optional

Datatype
teidata.language

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

Note

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

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

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

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

Status
Optional

Datatype
teidata.enumerated

Legal values are:

default

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

preserve

indicates the intent that applications preserve all white space

Note

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

§

Home

att.global.linking

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

Module | linking

Members
att.global [TEI abbr add addrLine address anchor argument att author authority availability back bibl biblScope body byline catDesc catRef category cell change choice cit classCode classDecl closer code corr creation date dateline del desc distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl eg emph encodingDesc epigraph expan extent figDesc figure fileDesc foreign formula front funder gap gi gloss graphic group head hi ident idno imprimatur index interp interpGrp item keywords l label langUsage language lb lg licence list listBibl mentioned milestone name note notesStmt num opener orig p pb pc postscript principal profileDesc projectDesc ptr pubPlace publicationStmt publisher q ref refsDecl reg relatedItem resp respStmt revisionDesc row rs s salute samplingDecl seg seriesStmt sic signed soCalled sourceDesc sp speaker sponsor stage table taxonomy teiCorpus teiHeader term text textClass time title titlePage titlePart titleStmt trailer unclear val w]

Attributes
Attributes

corresp corresp¶
(corresponds) points to elements that correspond to the current element in some way.

Status
Optional

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

<group>
 <text xml:id="t1-g1-t1" xml:lang="mi">
  <body xml:id="t1-g1-t1-body1">
   <div type="chapter">
    <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>
    <p>…</p>
   </div>
  </body>
 </text>
 <text xml:id="t1-g1-t2" xml:lang="en">
  <body xml:id="t1-g1-t2-body1"
   corresp="#t1-g1-t1-body1">
   <div type="chapter">
    <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>
    <p>…</p>
   </div>
  </body>
 </text>
</group>

In this example a group contains two texts, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.

<!-- In a placeography called "places.xml" --><place xml:id="LOND1"
 corresp="people.xml#LOND2 people.xml#GENI1">
 <placeName>London</placeName>
 <desc>The city of London...</desc>
</place>
<!-- In a literary personography called "people.xml" -->
<person xml:id="LOND2"
 corresp="places.xml#LOND1 #GENI1">
 <persName type="lit">London</persName>
 <note>
  <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>
 </note>
</person>
<person xml:id="GENI1"
 corresp="places.xml#LOND1 #LOND2">
 <persName type="lit">London’s Genius</persName>
 <note>
  <p>Personification of London’s genius. Appears as an
     allegorical character in mayoral shows.
  </p>
 </note>
</person>

In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.

next next¶
points to the next element of a virtual aggregate of which the current element is part.

Status
Optional

Datatype
teidata.pointer

Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

prev prev¶
(previous) points to the previous element of a virtual aggregate of which the current element is part.

Status
Optional

Datatype
teidata.pointer

Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

§

Home

att.global.rendition

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

Module | tei

Members
att.global [TEI abbr add addrLine address anchor argument att author authority availability back bibl biblScope body byline catDesc catRef category cell change choice cit classCode classDecl closer code corr creation date dateline del desc distributor div divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl eg emph encodingDesc epigraph expan extent figDesc figure fileDesc foreign formula front funder gap gi gloss graphic group head hi ident idno imprimatur index interp interpGrp item keywords l label langUsage language lb lg licence list listBibl mentioned milestone name note notesStmt num opener orig p pb pc postscript principal profileDesc projectDesc ptr pubPlace publicationStmt publisher q ref refsDecl reg relatedItem resp respStmt revisionDesc row rs s salute samplingDecl seg seriesStmt sic signed soCalled sourceDesc sp speaker sponsor stage table taxonomy teiCorpus teiHeader term text textClass time title titlePage titlePart titleStmt trailer unclear val w]

Attributes
Attributes

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

Status
Optional

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

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

Note

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

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

§

Home

<cit>

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

Module | core
Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
Member of | model.quoteLike

Contained by

analysis: s

core: abbr add addrLine author biblScope cit corr del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q ref reg rs sic soCalled sp speaker stage term title unclear

figures: cell figDesc figure

header: change distributor edition extent licence

linking: seg

tagdocs: eg

textstructure: argument body div docAuthor docDate docEdition epigraph imprimatur postscript salute signed titlePart trailer

May contain

analysis: interp interpGrp

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

figures: figure

linking: anchor

tagdocs: eg

Example

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

Show all

Content model

<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.qLike"/>
  <classRef key="model.egLike"/>
  <classRef key="model.biblLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.global"/>
  <classRef key="model.entryPart"/>
 </alternate>
</content>

Schema Declaration

element cit
{
   (
      model.qLike
    | model.egLike
    | model.biblLike
    | model.ptrLike
    | model.global
    | model.entryPart
   )+
}

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

§

Home

<editorialDecl>

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
Module | header
Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@rend)) (att.global.linking (@corresp, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
Member of | model.encodingDescPart
Contained by | header: encodingDesc
May contain | core: p

Example

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

Show all

Content model

<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
 </alternate>
</content>

Schema Declaration

element editorialDecl { model.pLike+ }

TEI Guidelines . This page generated on 2019-07-16T15:14:53Z.

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

Lou Burnard and C. M. Sperberg-McQueen

TEI Lite: Encoding for Interchange: an introduction to the TEI

Final revised edition for TEI P5

Lou Burnard

C. M. Sperberg-McQueen

August 2012

Information about this book

Title statement

Encoding for Interchange: an introduction to the TEI

Publication

Publisher

TEI Consortium

Availability

Distributed under a Creative Commons Attribution-ShareAlike 3.0 Unported License

Copyright 2013 TEI Consortium.

All rights reserved.

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

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

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

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

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

Source

— TEI U5 (derived from TEI U1: An Introduction to TEI Tagging (derived from TEI ED W21: Living with the Guidelines)