An Introduction to TEI simplePrint

An Introduction to TEI simplePrint

Lou Burnard
Martin Mueller
Sebastian Rahtz
James Cummings
Magdalena Turska
January 2017

Preface

This document is the formal specification for TEI simplePrint, an entry-level customization of the Text Encoding Initiative (TEI) Guidelines, intended to be generally useful to a large variety of encoders attempting to cope with the standardized representation of a variety of documents in digital form.

Like every other TEI customization, TEI simplePrint was designed for use with a particular type of material. If the material you are planning to encode matches the following criteria, then TEI simplePrint is for you. If it does not, it may not be.

- You are encoding print material, rather than manuscript: simplePrint provides no way of encoding manuscript features such as correction, deletion, or scribal variation
- You are encoding material from the Early Modern period (i.e., up to the end of the nineteenth century): some of the features for which simplePrint provides encodings are rarely found in modern materials.
- You are encoding material written, broadly speaking, within the Western European tradition, using largely Western European characters. simplePrint does provide facilities for encoding short passages in non Western European languages, but many features needed to cope with Asian or ancient scripts are missing.
- Your intention is to provide a relatively simple encoding for a large amount of material, rather than a rich encoding of a small amount of material: simplePrint is intended to help libraries and archives wishing to go beyond basic digital facsimiles, rather than to support specialist research. It does not, for example, include features for detailed linguistic tagging beyond simple word-level tagging, nor for specialised text types such as dictionaries, historical or biographical databases, etc.

If your needs go beyond those summarized here, simplePrint may still be a good point of departure, and may be very useful as a basis for the creation of your own TEI customisation. We don't however discuss the creation of a TEI customization in this document: the TEI website provides a number of links to tutorial material and tools which may assist in this process.

The present document is intended to be generally comprehensible and accessible, but does assume some knowledge of XML (the encoding language used by the TEI), and of the way it is used by the TEI. Further information on both these topics are available from many places, not least the TEI's own web site at .

The TEI simplePrint schema was first elaborated as a part of the TEI Simple project funded by the Andrew W. Mellon Foundation (2012-2014). The project sought to define a new highly-constrained and prescriptive subset of the Text Encoding Initiative (TEI) Guidelines suited to the representation of early modern print materials, a formally-defined set of processing rules which permit modern web applications to easily present and analyze the encoded texts, mapping to other ontologies, and processes to describe the encoding status and richness of a TEI digital text. Its choice of elements reflected the practices followed in the encoding of large-scale literary archives, notably those produced by the Text Creation Partnership. Practice of other comparable archives such as the German Text Archive was also taken into account.

The most distinctive feature of TEI simplePrint is its use of the TEI Processing Model, which provides explicit and recommended options for the display or processing of every textual element. Programmers developing systems to handle texts encoded with TEI simplePrint do not have to look beyond this when building stylesheets or other components. This greatly reduces the complexity of developing applications that will work reliably and consistently for many users and across large corpora of documents.

The TEI simplePrint schema and the TEI Processing Model were first defined by a working group led by Martin Mueller (Northwestern University) and Sebastian Rahtz (Oxford University). Major contributions to the project were made by Magdalena Turska (Oxford University), James Cummings (Oxford University), and Brian Pytlik Zillig. The changes to the TEI scheme needed to support the TEI Processing Model were reviewed and approved by the TEI Technical Council for inclusion in release 3.0.0 of TEI P5 in February 2016. The present document was extensively revised and extended by Lou Burnard in July 2016 for submission to the TEI Technical Council.

A Short Example

We begin with a short example. How should we go about transferring into a computer a passage of prose, such as the start of the last chapter of Charlotte Brontë's novel Jane Eyre? We might start by simply copying what we see on the printed page, typing it in such a way that what appears on the screen looks as similar as possible, for example, by retaining the original line breaks, by introducing blanks to represent the layout of the original headings, page breaks, and paragraphs, and so forth. Of course, the possibilities are limited by the nature of the computer program we use to capture the text: it may not be possible for example to reflect accurately the typographic characteristics of our source with all such software. Some characters in the printed text (such as the accented letter a in faàl or the long dash) may not be available on the keyboard; some typographic distinctions (such as that between small capitals and full capitals) may not be readily accessible. Our first attempt tries to mimic the appearance of the former, and simply ignores the latter.

                                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 distinguish them;
- no distinction is made between single quotation marks and apostrophe, so it is difficult to be certain exactly which passages are in direct speech;
- the preservation of the copy text's hyphenation means that simple-minded search programs will not find words broken across a line;
- the accented letter in faàl and the long dash have been rendered by ad hoc keying conventions (faa\l) 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 display the text changes, reformatting will be problematic.

We now present the same passage, as it might be encoded in TEI simplePrint. 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 in a standardized way:

- Paragraph and chapter divisions are now marked explicitly by means of tags rather than implicitly by white space.
- Apostrophes are retained, but the quotation marks indicating direct speech have been removed, and direct speech is now marked explicitly by means of a tag.
- The accented letter and the long dash are accurately represented, using the appropriate Unicode character.
- Page divisions have been marked with an empty <pb> tag; the page heading and running text have been suppressed.
- The lineation of the original has also been suppressed 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 encoding is expressed in TEI XML, a very widely used and standardized method of representing information about a document within the document itself. The transcribed words are complemented by special flags within angle brackets, called tags, which both characterise and mark the beginning and end of a string of characters. For example, each paragraph is marked by a tag <p> at its start, and a corresponding </p> at its end. We don't elaborate further on the syntax of TEI XML here.[^1]

[^1: Many introductory tutorials on XML are available on the web, for example at . The way the TEI uses XML is fully documented in section v of the TEI Guidelines; a very basic introduction to TEI XML is also available at . The formal specification of the XML language is at .]

Aside from its syntax, it is important to note that this particular encoding represents a set of choices or priorities. We have chosen to prioritize and simplify the representation of the words of the text over the representation of the typographic layout associated with them in this source document. This makes it easier for a computer to answer questions about the words in the document than about its typesetting, reflecting our research priorities. This priority also leads us to suppress end-of-line hyphenation. 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. Similarly, our decision makes it impossible to use this transcription as a means of statistically analysing hyphenation practice. An encoding makes explicit all and 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 to address other research priorities. 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;
- names could be classified as personal, geographical, or institutional
- 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.

In the remainder of this document, we present a number of TEI-recommended ways of supporting these and other encoding requirements. These ways generally involve the application of specific TEI XML elements, selected from the full range of possibilities documented in the TEI Guidelines. Like every other TEI project, TEI Simple proposes a view of the TEI Guidelines. This document defines and documents that view.

The Structure of a TEI simplePrint Document

A TEI-conformant text contains (a) a TEI header (marked up as a <teiHeader> element) and (b) one or more representations of a text. These representations may be of three kinds: a transcribed text, marked up as a <text> element; a collection of digital images representing the text, marked up using a <facsimile> element; or a literal transcription of one or more documents instantiating the text, marked up using the <sourceDoc> element.

These elements are combined together to form a single <TEI> element, which must be declared within the TEI namespace, and therefore usually takes the form <TEI xmlns="http://www.tei-c.org/ns/1.0">[^2].

[^2: 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 TEI elements is "http://www.tei-c.org/ns/1.0"]

Some aspects of the TEI header are described in more detail in section The Electronic Title Page. In what follows, we will focus chiefly on the use of the <text> element, though we describe one way of using the <facsimile> element in combination with it or alone in section Encoding a Digital Facsimile. We do not consider the <sourceDoc> element further, since it is mainly used in very specialised applications for which TEI simplePrint would not be appropriate.

A 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 optional front or back matter such as title pages, prefaces, appendixes etc. We use the term body for whatever comes between these in the source document. We discuss various kinds of composite text in section Composite and Floating Texts below.

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

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

In each of the following sections we include a short list of the TEI elements under discussion, along with a brief description, and in most cases an example of how they are used. Throughout the text, element names are linked to their detailed reference documentation, as given in the TEI Guidelines. Note that most of the examples provided by the reference documentation, and all of the links, are not specific to TEI simplePrint.

For example, here are the elements discussed so far:

Encoding the Body

As indicated above, a unitary text is encoded by means of a <text> element, which may contain the following elements: Elements specific to front and back matter are described below in section Front and Back Matter. In this section we discuss the elements making up the body of a text. A text must always have a body.

Text Division Elements and Global Attributes

The body of a prose text may be just a series of paragraphs or similar blocks of text, or these may be grouped together into chapters, sections, subsections, etc. The <div> element is used to represent any such grouping of blocks.

The @type attribute on the <div> element may be used to supply a conventional name for this category of text division in order to distinguish them. Typical values might be "book", "chapter", "section", "part", "poem", "song", etc. TEI simplePrint does not constrain the range of values that may be used here.

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

Here as elsewhere the @xml:id attribute may be used to supply a unique identifier for the division, which may be used for cross references or other links to it, such as a commentary, as further discussed in section Cross References and Links. It is good practice to provide an @xml:id attribute for every major structural unit in a text, and to derive its values in some systematic way, for example by appending a section number to a short code for the title of the work in question, as in the examples below.

The @n attribute may be used to supply (additionally or alternatively) a short mnemonic name or number for 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 the @xml:id attribute, it does not need to be unique.

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

The @rendition attribute may be used to supply information about the rendition (appearance) of a division, or any other element, as further discussed in section Marking Highlighted Phrases below. Note that this attribute is used to describe the appearance of the source text, rather than the appearance of any intended output when the encoded text is displayed. The two may of course be similar, or identical, but the TEI does not assume or require this.

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

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

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

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

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

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

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

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

Headings and Closings

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

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

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

Textual Components

In prose texts such as the Brontë example above, the divisions are generally composed of paragraphs, represented as <p> elements, though in some circumstances it may be preferred to use the anonymous block element <ab>. In poetic or dramatic texts different elements are used, representing stanzas and verse lines in the first case, and individual speeches or stage directions in the second:

We discuss each of these kinds of component separately below.

Verse

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>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: as elsewhere the original lineation of the source text is not therefore preserved by this encoding. The <lb> element described in section Page and Line Numbers might additionally be used to mark typographic lines if so desired.

In a poetic text it may also be considered useful to identify the rhymes, for which the following element may be used: The following example shows how this element might be used both to identify rhyming words or word parts and to assign each rhyme to a part of a rhyming pattern by means of its @label attribute. The rhyming pattern here is specified by the @rhyme attribute supplied on the <lg> representing the stanza within which the pattern operates:

<lg rhyme="AABCCBBA">
  <l>The sunlight on the <rhyme label="A">garden</rhyme></l>
  <l><rhyme label="A">Harden</rhyme>s and grows <rhyme label="B">cold</rhyme>,</l>
  <l>We cannot cage the <rhyme label="C">minute</rhyme></l>
  <l>Wi<rhyme label="C">thin it</rhyme>s nets of <rhyme label="B">gold</rhyme>
  </l>
  <l>When all is <rhyme label="B">told</rhyme>
  </l>
  <l>We cannot beg for <rhyme label="A">pardon</rhyme>.</l>
</lg>

The @rhyme attribute may be used independently of the <rhyme> element, or in combination with it, as above.

Drama

A dramatic text contains speeches, which may be in prose or verse, and will also contain stage directions. The <sp> element is used to represent each identified speech. It contains an optional speaker indication, marked with the <speaker> element, which can be followed by one or more <l> or <p> elements, depending on whether the speech is considered to be in prose or in verse. Stage directions, whether within or between speeches, are marked using the <stage> element.

For example:

<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 <hi>on</hi> 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>

In a verse drama, 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 rendition="#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 value of the @part attribute may indicate just that the element bearing is fragmented in some (unspecified) respect rather than a complete verse line (part="Y"); alternatively it may indicate whether this is an initial (I), medial (M) or F (final) fragment.

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 type="stanza" 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 items in a list of the characters in the novel. In the case of a play, this list of characters might appear in the original source as a cast list or dramatic personae, which might be marked up using the <castList> element described in section Specialized Front and Back Matter below. Such a list would not, of course, be appropriate to provide descriptive information about each character, much of which does not appear in the original source. Instead a <particDesc> (participant description) element should be provided in the TEI header, as further discussed in section The Profile Description below.

Other Kinds of Text Block

As mentioned above, the <ab> element may also be used in preference to the <p> element. It should be used for blocks of text which are not clearly paragraphs, verse lines, or dramatic speeches. Typical examples include the canonical verses of the Bible, and the textual blocks of other ancient documents which predate the invention of the paragraph, such as Greek inscriptions or Egyptian hieroglyphs. The element is also useful as a means of encoding more specialized kinds of textual block, such as the question and answer structure of a catechism, or the highly formalized substructure of a legal document (if <div> is not considered appropriate for these). In more modern documents, it can be used to encode semi-organized or fragmentary materials such as an artist's notebook or work in progress; or to faithfully capture the substructure of a file produced by an OCR system.

Page and Line Numbers

Page and line breaks etc. may be marked with the following elements: The <pb>, <lb>, and <cb> elements are special cases of a general class of elements known as milestones because they 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, a change of author or style, or in general any significant change in the text not enclosed by an XML element. Unlike other elements, milestone elements do not enclose a piece of text and make an assertion about it; instead they indicate a point in the text where something changes, as indicated by a change in the values of the milestone's attributes @unit, which indicates the something concerned, and @n which indicates the new value.

The <pb>, <lb>, and <cb> elements are shortcuts or syntactic sugar for <milestone unit="page"/> <milestone unit="line"/> and <milestone unit="column"/> respectively.

When working from a paginated original, it is often useful to record its pagination, whether to simplify later proof-reading, or to align the transcribed text with a set of page images, as further discussed below.

Because <pb> and other milestone elements are empty, they may be placed freely within or between other elements. However, it is recommended practice always to put them at the beginning of whatever unit it is that their presence implies, and not to nest them within elements contained by that unit. For example, in the following example a page break occurs between two lines of a poem:

<l>Mary had a little lamb</l>
<pb n="13"/>
<l>Its fleece was white as snow</l>

The <pb> element should be placed ahead of all the text encoded on the 13th page. Contrast this with the following less accurate encoding:

<l>Mary had a little lamb</l>
<l>
  <pb n="13"/>Its fleece was white as snow</l>

This is less accurate because it implies that the second verse line actually begins before the page break.

Similar considerations apply to line breaks (<lb>), though these are less frequently considered useful when encoding modern printed textual sources. When transcribing manuscripts or early printed books, however, it is often helpful to retain them in an encoding, if only to facilitate alignment of transcription and original. Like <pb>, the <lb> element should appear before the text of the line whose start it signals.

If features such as pagination or lineation are marked for more than one edition, the edition in question may be specified by the @ed attribute. 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>

When transcribing from a paginated source, the encoder must decide whether to suppress such features as running titles, page signatures, catch words etc., to replace them by a simplified representation using the <pb> element, perhaps using the @n attribute to preserve some of the information, or to preserve them entirely using the <fw> element. The latter strategy is appropriate in encodings which aim to retain as much information as possible about the original typography; it will however make more complex the processing of the source for other purposes, as in the following example:

<l>He also fix'd the wandering
  QUEEN OF NIGHT,</l>
<fw type="sig">Ii 2</fw>
<fw type="catch">Whether</fw>
<pb n="244"/>
<l>Whether she wanes into a scanty orb</l>...

The <pb> element is also used to align parts of a transcription with a digital image of the page concerned. This may be done in a very simple but inflexible way by using the @facs attribute to point to each page image concerned:

<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" facs="ed1p475.png"/> Mary approved the step
unreservedly... </p>

The @facs attribute can supply (as here) a filename, or any other form of URI, if for example the page image is stored remotely. One drawback of this simplistic approach is that there must be exactly one image file per page of text. It is not therefore suitable in the case where the available page images represent double page spreads, or where there are multiple images of the same page (for example at different resolutions).

A more powerful approach, discussed in section Encoding a Digital Facsimile below, is to use the <facsimile> element to define the organisation of the set of images representing the text, and then use the @facs attribute to point to individual components of that representation.

Marking Highlighted Phrases

Changes of Typeface, etc.

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

The global @rendition 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 rendition="simple:bold">, and one in italic <head rendition="simple:italic">.

The values used for the @rendition attribute point to definitions provided for the formatting concerned. These definitions are typically provided by a <rendition> element in the document's header, as further discussed in section Tagging Declaration.

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

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

<p><hi rendition="simple:blackletter">And
  this Indenture further witnesseth</hi> that the said <hi rendition="simple:italic">Walter Shandy</hi>, merchant, in consideration of the
said intended marriage ...</p>

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

Some features (notably quotations, titles, and foreign words) may be found in a text either marked by highlighting, or with quotation marks. In either case, the element <q> (as discussed in the following section) should be used. Again, the global @rendition attribute can be used to record details of the highlighting used in the source if this is thought useful.

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 be encoded as follows:

<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 be encoded like this:

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

Quotations and Related Features

Like changes of typeface, quotation marks are conventionally used to denote several different features within a text, of which the most frequent is quotation, though many other features are possible. The full TEI Guidelines provide additional elements such as <mentioned> or <said> to distinguish some of these features, but these more specialised elements are not included in TEI simplePrint. In TEI Simple however, we use the <quote> element for quotation only, and the <q> element for all other material found within quotation marks in the text.

Here is a simple example of a quotation:

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

As elsewhere, the way that a citation or quotation was printed (for example, in-line or set off as a display or block quotation), may be represented using the @rendition attribute. 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 <q> element and beginning it again after the interruption, as in the following example:

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

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

Direct speech 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 @rendition attribute may be used to record the way in which they were rendered in the copy text.

Foreign Words or Expressions

Words, phrases, or longer stretches of text that are not in the main language of the texts may be tagged as such in one of two ways. 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. 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>

As these examples show, the <foreign> element should not be used to tag foreign words if some other more specific element such as <title>, or <div> applies.

The value of the @xml:lang attribute on an element applies hierarchically to everything contained by that element, unless overridden:

<div xml:lang="la">
  <p>Pars haec Latine composita est.</p>
  <p xml:lang="en">Except that this sentence is in English.</p>
  <p>Vita brevis, ars longa.</p>
</div>

Here we specify that the whole <div> element uses the language with the coded identifier "la" i.e., Latin. Since it is contained by that <div> there is no need to supply this information again for the first <s> element. The second <s> element however overrides this value, and indicates that its content is in English (the language with identifier "en"). The third <s> element is again in Latin.

The codes used to identify languages, supplied on the @xml:lang attribute, are defined by an international standard[^3], 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

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

Notes

A note is any additional comment found in a text, marked in some way as being out of the main textual stream. A note is always attached to some part of the text, implicitly or explicitly: we call this its target, or its point of attachment. The element <note> should be used to mark any kind of note whether it appears as a separate block of text in the main text area, at the foot of the page, at the end of the chapter or volume, in the margin, or in some other place.

Notes may be in a different hand or typeface, may be authorial or editorial, and may have been added later. The attributes @type and @resp can be used to distinguish between different kinds of notes or identify their authors.

In a printed or written text, the point of attachment for a note is typically represented by a siglum such as an alphanumerical or other character, often in superscripted form. When encoding such a text, it is conventional to replace this siglum by a note element containing the annotation itself, as in the following example: <p>...some text <note xml:id="n6">a note about some text</note> .... </p>

An alternative approach is to encode the point of attachment wherever it appears in the text, using for example the <ref> element discussed in the next section, and to place the <note> element anywhere convenient. The two can then be associated by using the @target attribute on the <ref> element to point to the <note> element, as in the following example, in which the superscripted 7 indicating the point of attachment has been retained as part of the encoding: <p>...some text <ref target="#n7" rendition="simple:superscript">7</ref> .... <note xml:id="n7">a note about some text</note></p>

It may however be problematic to determine the precise position of the point of attachment, particularly in the case of marginal notes. A marginal note may also be hard to distinguish from a label or subheading which introduces the text with which it is associated. Where the purpose of the note is clearly to label the associated text, rather than to comment on it, the element <label> may be preferable. Where it is clearly a subheading attached to a distinct subdivision, it may be preferable to start a new element <div> and encode the subheading as a <head>. Note however that a <head> cannot be inserted anywhere except at the beginning of a <div>. And where (as in some Early Modern English plays) marginal annotation is systematically used to identify speakers, it may be better to represent these using the <speaker> element introduced above. In cases of doubt, the encoder should decide on a clear policy and preferably document it for the use of others.

Cross References and Links

Any kind of cross reference or link found at one point in a text which points to another part of the same or another document may be encoded using the <ref> element discussed in this section. Implicit links (such as the association between two parallel texts, or that between a text and its interpretation) may be encoded using the linking attributes discussed in section Special Kinds of Linking.

Simple Cross References

Usually, the presence of a cross-reference or link will be indicated by some text or symbol in the source being encoded, which will then become the content of the <ref> element. Occasionally, however, and frequently in the case of a born digital document, the exact form and appearance of the cross reference text will be determined dynamically by the software processing the document. In such cases, the <ref> element will have no content, and serve simply to mark a point from which a link is to be made, along with the target of the link.

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

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

See especially <ref target="#SEC12"/>. In both cases, there is a cross reference from the position in the source document immediately following the word especially to whatever element in the encoded document has the identifier "SEC12". In the first case, the encoder has supplied the original form of the cross reference section 12 on page 34; in the second, the task of generating an appropriate form of cross reference has been left to the formatting software. Perhaps the pagination and section numbers of the document in question are not yet determined; perhaps the cross reference should be replaced by a big red button. In either case, however, the value of the @target attribute must be the identifier of some other element within the current document. Since the passage or phrase being pointed at must bear an identifier, it must be an element of some kind. In the following example, the cross reference is to a <div> element:

... see especially <ref 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 used to mark them. These two elements are described as follows:

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

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

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

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

Pointing to other documents

So far, we have shown how the <ref> element may be used for cross-references or links whose targets occur within the same document as their source. The element 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 Uniform Resource Identifier (URI)[^4].

[^4: 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 hash 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.

It is also possible to define an abbreviated form of the URI, using a predefined prefix separated from the rest of the code by a colon, as for example "cesr:SEC2". This is known as a private URI, since the prefix is not standardized (except that the prefix "xml:" is reserved for use by XML itself). A <prefixDef> element should be supplied within the TEI header specifying how the prefix (here "cesr") should be translated to give a full URL for the link. This is particularly useful if a document contains many references to an external document such as an authority file.

Parts of an XML document can be specified by means of other more sophisticated mechanisms using a language called Xpointer, also defined by the W3C. This is useful when, for example, the elements to be linked to do not bear identifiers. Further information about this and other forms of link addressing is provided in chapter 16 of the TEI Guidelines but is beyond the scope of the present document.

Special Kinds of Linking

The following special purpose linking attributes are defined for every element in the TEI simplePrint schema:

@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 Analysis. For example, a linguistic analysis of the sentence John loves Nancy might be encoded as follows:

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

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

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

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

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

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

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

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

Editorial Interventions

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

Correction and Normalization

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

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

Consider, for example, the following famous passage as it appears in the first quarto printing of Shakespeare's Henry V: [Detail from Henry V, first quarto (1600)] in particular the phrase we might transcribe directly as

... for his Nose
             was as sharpe as a Pen, and a Table of greene fields

A modern editor might wish to make a number of interventions here, specifically to modernize (or normalize) the Elizabethan spellings of a' and sharpe for he and sharp respectively. They 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 <reg>sharp</reg> as a
Pen and <reg>he</reg>
<corr resp="#Theobald">babbl'd</corr> of green fields

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
  <orig>sharpe</orig> as a Pen, and <orig>a</orig>
<sic>Table</sic> of green fields

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

... for his Nose was as <choice>
  <orig>sharpe</orig>
  <reg>sharp</reg>
</choice> 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 fields

Omissions, Deletions, and Additions

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

These elements may be used to record changes made by an editor, by the transcriber, or (in manuscript material) by the author or scribe. For example, if the source for an electronic text read The following elements are provided for for simple editorial interventions. then it might be felt desirable to correct the obvious error, but at the same time to record the deletion of the superfluous second for, thus:

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

The attribute value "#LB" on the @resp attribute is used to point to a fuller definition (typically in a <respStmt> element) of the person or other agency responsible for correcting the duplication of for.

If the source read The following elements provided for simple editorial interventions. (i.e. if the word are had been inadvertently dropped) then the scholar identified as "LB" might choose to encode the corrected text as follows:

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

These elements may also be used to record the actual writing process, for example to record passages which have been deleted, added, corrected etc., whether by the author of a literary text or by a scribe copying out a manuscript. An analysis of such documentary modifications may be essential before a reading text can be presented, and is clearly of importance in the editorial process.

The example is taken from the surviving authorial manuscript of a poem by the English writer Wilfred Owen, a part of which is shown here:

Detail from Dulce et decorum est autograph manuscript in the English Faculty Library, Oxford University.

Owen first wrote Helping the worst amongst us, but then deleted it, adding Dragging the worst amongt us over the top. In the same way, he revised the phrase half–blind by deleting the half– and adding all above it. In the last line, he started a word beginning fif before deleting it and writing the word five–nines. We can encode all of this as follows:

<l>And towards our distant rest began to trudge,</l>
<l><subst>
    <del>Helping the worst amongst us</del>
    <add>Dragging the worst amongt us</add>
  </subst>, who’d no boots </l>
<l>But limped on, blood–shod. All went lame; <subst>
    <del status="shortEnd">half–</del>
    <add>all</add>
  </subst> blind;</l>
<l>Drunk with fatigue ; deaf even to the hoots</l>
<l>Of tired, outstripped <del>fif</del> five–nines that dropped behind.</l>

The tags <add> and <del> elements are used to enclose passages added or deleted respectively. Additional attributes are available such as @resp to indicate responsibility for the modification, or @place to indicate where in the text (for example, above or below the line) the modification has been made. Where the encoder wishes to assert that the addition and deletion make up a single editorial act of substitution, these elements can be combined within a <subst> element as shown above.

A very careful examination of Owen’s second modification shows that he really did write amongt rather than amongst, presumably in error. An equally careful editor wishing to restore the missing s might use the <supplied> element to indicate that they have done so:

<add>Dragging the worst among<supplied resp="#ED">s</supplied>t us</add>

Here the @resp attribute has been used to indicate that the s was not supplied by Owen but by someone else, specifically the person documented elsewhere by an element with the identifier "ED".

The <unclear> element is useful where material in the source is so hard to read that the transcriber is uncertain as to whether they have done so correctly. The <gap> element by contrast should be used where the material is so illegible that the transcriber does not wish even to attempt it. The two may however be used together as in the following example:

One hundred &amp; twenty good regulars joined <unclear>to me <gap extent="2 words" reason="indecipherable"/> and </unclear> instantly, would aid me signally in an
enterprise against Wilmington.

The <del> element marks material which is deleted in a source, but has been transcribed as part of the electronic text all the same, while <gap> marks the location of source 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. An @extent attribute is available on the <gap> element to indicate how much material has been omitted. The <desc> element can be used inside the <gap> element to provide a brief characterisation of the omitted material, as in the following examples:

<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 extent="50 lines">
  <desc>quotation from ledger (in Danish)</desc>
</gap><p>A description of the overall structure of the account is once again ...
</p>

(The <name> and <date> elements used in this example are discussed further below)

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

<p>At the bottom of your screen below the
  mode line is the <hi>minibuffer</hi>. 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>

Abbreviation and their Expansion

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

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

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>

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>

The elements <expan> and <abbr> should contain a full word, or the abbreviated form of a full word respectively. For a fuller discussion of abbreviations and the intricacies of representing them consult the section on Abbreviation and Expansion in the TEI Guidelines.

Names, Codes, and Numbers

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

Names and Referring Strings

A referring string is any phrase which refers to some person, place, object, etc. A name is a referring string which contains proper nouns and honorifics only. Two elements are provided to mark such strings:

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

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

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

As the following example shows, the <rs> element may be used for a reference to a person, place, etc., which does not contain a proper noun or noun phrase:

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

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 @ref attribute provides a way of linking a name with a description of the object being named, and may thus act as a normalized identifier for it. It is also very useful as a means of gathering together all references to the same individual or location scattered throughout a document:

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

The values used for the @ref attribute here ("#BENM1" etc.) are pointers; in this case indicating an element with the identifier "BENM1" etc. somewhere in the current document, though any form of URI could be used. The element indicated will typically (for a person) be a <person> element, listed within a <particDesc> element, or (for a place) a <place> element, listed within a <settingDesc> element in the TEI header, as further discussed in The Profile Description below.

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" ref="#WADLM1"><choice>
    <orig>Walter de la Mare</orig>
    <reg>de la Mare, Walter</reg>
  </choice></name> was born at <name ref="https://en.wikipedia.org/wiki/Charlton,_London" type="place">Charlton</name>,
in <name type="place">Kent</name>, in 1873.

Formulae, Codes, and Special Characters

The following elements may be useful when marking up sequences of text that represent mathematical expressions, chemical formulae, and the like:

In many cases, a simple Unicode character suffices to represent the superscript or subscript digits and other symbols which may appear inside a mathematical formula: <formula>E=mc²</formula> In other more complex cases, the encoder may choose to use a different XML scheme (such as MathML) to encode the content of a formula, or a non-XML notation. These possibilities are not discussed further here.

The <g> element is useful in the case that no Unicode character exists to represent the character or glyph required. Its @ref attribute can be used to point to a definition of the symbol intended, while its content (if any) represents a Unicode approximation to it:

...Thereto
<g ref="#air">[air]</g> and ...

The TEI header provides a number of additional elements for the definition of such non-Unicode characters, as further discussed in section The character declaration below.

The following elements are useful for stretches of code or similar formal language appearing within a text:

This can be expressed in XML as follows:
             <code>&amp;lt;date notBefore="2016-06-23"/&gt;</code> Contact the author at
             <email>lou.burnard@gmail.com</email>

Note in this example that characters which have a syntactic function in XML (such as the ampersand or the angle bracket) must be represented within a TEI simplePrint document by means of an entity reference such as &lt; or &amp;.

The element <ref> discussed in section Cross References and Links should be used to represent a coded reference such as a link given as a URL within a text, either as content or as an attribute value:

<p>Further discussion of <ref target="http://www.tei-c.org/">the Text Encoding
    Initiative website</ref> may be found at <ref>http://www.tei-c.org/</ref></p>

Dates and Times

The following elements are provided for the detailed encoding of times and dates:

These elements have a number of attributes which can be used to provide normalized versions of their values in various ways. 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>

These attributes are typically used to make a date or time more easily processable, as in the following examples:

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>

They are also useful in cases where the date concerned is uncertain or only vaguely specified: <p>... <date period="secondEmpire">during the second empire</date></p>

<date notAfter="1946-12-09" notBefore="1946-11-01">in the weeks shortly before my
  birth</date>

Numbers and Measurements

Like dates, both numbers and quantities can be written with either letters or digits and may therefore need to be normalized for ease of processing. Their presentation is also highly language-dependent (e.g. English 5th becomes Greek 5.; English 123,456.78 equals French 123.456,78).

The following elements are provided for the detailed encoding of numbers and quantities:

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>

<measure quantity="40" unit="hogshead" commodity="rum">2 score hh rum</measure>
<measure quantity="1" unit="dozen" commodity="blooms">1 doz. roses</measure>
<measure quantity="1" unit="count" commodity="blooms">a yellow tulip</measure>

Lists

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

Individual list items are tagged with <item>. The first <item> may optionally be preceded by a <head>, which gives a heading for the list. The numbering of items within the 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.

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

</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 in section 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>

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

Bibliographic Citations

It is often useful to distinguish bibliographic citations where they occur within texts being transcribed for research, if only so that they will be properly formatted when the text is printed out. The element <bibl> is provided for this purpose. Where the components of a bibliographic reference are to be distinguished, the following elements may be used as appropriate. It is generally useful to distinguish 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:

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

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> 5. 88ff</bibl>).

The bibliographic elements listed above are particularly useful in a born digital document which contains a bibliography encoded using the <listBibl> element. Entries in the bibliography should be given an identifier, which can then be used as the target of cross references from elsewhere in the document:

<p>Perec citing, amongst others <ref target="#MK_73">Sturm und Drang, 1973</ref>,
  concludes ... </p>

A <bibl> element may contain simply text, with possibly a few of its components distinguished by tagging, and much use of conventionalized punctuation, as in this example:

<bibl xml:id="MK_73">Sturm, U. &amp; Drang, F. : <title>Musikalische
  Katastrophe</title>. (Berlin, W. de Gruyter, 1973)</bibl>

Alternatively, each of the components of the bibliographic reference may be clearly distinguished by tagging; in this case there is no requirement for conventionalized punctuation, since the processor will be able to generate this appropriately:

<bibl xml:id="MK73"><author>Sturm, U.</author>
  <author>Drang, F.</author>
  <title xml:lang="de" level="m">Musikalische Katastrophe</title>
  <pubPlace>Berlin</pubPlace>
  <publisher>W. de Gruyter</publisher>
  <date>1973</date></bibl>

The element <biblFull> is also provided for convience in cases where bibliographic citations following a more sophisticated model have been used; it is permitted only in the TEI header.

The <listBibl> element is used to group lists of bibliographic citations. It may contain a series of <bibl> or <biblFull> elements.

Tables

The following elements are provided for the description of tabular matter, commonly found in many kinds of narrative text. Note that TEI simplePrint provides no sophisticated ways of describing the detailed layout of a table beyond its organization into rows and columns.

The @role attribute may be used on either <cell> or <row>to indicate the function of a cell, or of a row of cells. Its values should be taken from the following list:

"data"
- data cell
"label"
- label cell
"sum"
- row or column sum data
"total"
- table total data

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

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

Figures and Graphics

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

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

Any textual information accompanying the graphic, such as a heading and/or caption, may be included within the <figure> element itself, in a <head> and one or more <p> elements, as 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="images/p412fig.png" width="40%"/>
</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, as in the following example: [Mr Fezziwig's Ball: illustration by George Cruikshank from Dickens' A Christmas Carol (1843)] The <figure> element provides a means of wrapping one or more such elements together as a kind of graphic block. It may also include a brief description of the image:

<figure>
  <graphic url="images/fezzipic.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 simplest case, the @facs attribute on the <pb> element may be used to supply a location for an image file corresponding with that point in the text:

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

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

</div>

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 multiple images are provided for each page, or more detailed alignment of image and transcription is required, for example because the image files actually represent double page spreads, more sophisticated mechanisms are needed, as further discussed in Encoding a Digital Facsimile below.

Analysis

Orthographic Sentences

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

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

<div type="chapter" n="38">
  <pb n="474"/>
  <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 analyzed 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 attribute used in the above example.

Words and Punctuation

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

For example, the output from a part of speech tagger might be recorded in TEI simplePrint 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 ana="#SENT">.</pc>
</s>

In this example, each token in the input has been decorated with an automatically generated part of speech code, using the @ana attribute discussed in section Special Kinds of Linking above. The system has also distinguished between tokens to be treated as words (tagged <w>) and tokens considered to be punctuation (tagged <pc>). It may also sometimes be useful to distinguish tokens which consist of a single letter or character: the <c> element is provided for this purpose.

The <w> also provides for each word to be associated with a root form or lemma, either explicitly using the @lemma attribute, or by reference, using the @lemmaRef attribute, as in this example: ...<w ana="#VBD" lemma="be" lemmaRef="http://www.myLexicon.com/be">was</w> ...

General-Purpose Interpretation Elements

The <w> element is a specialisation of the <seg> element which has already been introduced for use in identifying otherwise unmarked targets of cross references and hypertext links (see section Cross References and Links); it can be used to distinguish any portion of text to which the encoder wishes to assign a user-specified @type or 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 TEI 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 distinguish phrase-level phenomena of any kind; it is good practice to record the values used and their significance in the TEI header or in the documentation of the encoding system.

Common Attributes

Some attributes are available on many elements, though not on all. These attributes are defined using a TEI attribute class, a concept which is discussed further in the TEI Guidelines. We list here some attribute classes which have been adapted or customized for use in TEI simplePrint.

The elements <add>, <figure>, <fw>, <label>, <note> and <stage> all take the attribute @place to indicate whereabouts on the page they appear. In TEI simplePrint the possible values for this attribute are limited as indicated below:

above
- above the line
below
- below the line
top
- at the top of the page
top-right
- at the top right of the page
top-left
- at the top left of the page
top-centre
- at the top center of the page
bottom-right
- at the bottom right of the page
bottom-left
- at the bottom left of the page
bottom-centre
- at the bottom centre of the page
bottom
- at the foot of the page
tablebottom
- underneath a table
margin-right
- in the right-hand margin
margin
- in the outer margin
margin-inner
- in the inner margin
margin-left
- in the left-hand margin
opposite
- on the opposite, i.e. facing, page
overleaf
- on the other side of the leaf
overstrike
- superimposed on top of the current context
end
- at the end of the volume
divend
- at the end of the current division
parend
- at the end of the current paragraph
inline
- within the body of the text
inspace
- in a predefined space, for example left by an earlier scribe
block
- formatted as an indented paragraph

The elements <add>, <am>, <corr>, <date>, <del>, <ex>, <expan>, <gap>, <name>, <reg>, <space>, <subst>, <supplied>, <time> and <unclear> all use the attribute @unit to indicate the units in which the size of the feature concerned is expressed. In TEI simplePrint the possible values for this attribute are limited as indicated below:

chars
- characters
lines
- lines
pages
- pages
words
- words
cm
- centimetres
mm
- millimetres
in
- inches

Very many TEI elements take the value @type (see the specification for att.typed for a full list). In most cases, no constraint is placed on the possible values for this attribute. In the case of the element <name> however, the possible values for this attribute are limited as indicated below:

person
- person
forename
- forename
surname
- surname
personGenName
- generational name component
personRoleName
- role or position in society
personAddName
- additional name component (e.g. nickname)
nameLink
- connecting link within a name (e.g. van der)
org
- organization
country
- country
placeGeog
- geographical name
place
- place

Composite and Floating Texts

A composite text, like a simple text, has an optional front and back matter. In between however, instead of a single body, it contains one or more discrete texts, each with its own optional front and back matter. The following elements are provided to handle composite texts of various kinds.

A typical example might be an anthology containing several distinct works, or any other kind of collection, encoded using an overall structure like this:

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

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

A different kind of composite text occurs when one text is embedded within another, as for example in the Arabian Nights or similar collections of stories, or in other cases where one narrative is interrupted by another. The element <floatingText> may be preferred to encode such materials as the following:

<p>The Gentleman having finish'd his Story, Galecia waited on him to the Stairs-head;
  and at her return, casting her Eyes on the Table, she saw lying there an old dirty
  rumpled Book, and found in it the following story:</p>
<floatingText>
  <body>
    <p>IN the time of the Holy War when Christians from all parts went into the Holy
      Land to oppose the Turks; Amongst these there was a certain English Knight...</p>

    <p>The King graciously pardoned the Knight; Richard was kindly receiv'd into his
      Convent, and all things went on in good order: But from hence came the Proverb, We
      must not strike <hi>Robert</hi> for <hi>Richard.</hi>
    </p>
  </body>
</floatingText>
<pb n="43"/>
<p>By this time Galecia's Maid brought up her Supper; after which she cast her Eyes
  again on the foresaid little Book, where she found the following Story ....</p>

Note that there is only a single TEI header for composite texts of either kind, since the assumption is that the composite is at some level describable as a single work. However, it is also possible to define a composite of complete TEI texts, each with its own TEI header. Such a collection is known as a TEI corpus, and must itself have a TEI header:

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

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

Front and Back Matter

Front Matter

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

Title Page

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

Typeface distinctions should be marked with the @rendition attribute when necessary, as described above though a very detailed description of the letter spacing and sizing used in ornamental titles is not easily done. 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>
  <docTitle>
    <titlePart type="main">PARADISE REGAIN'D. A POEM In IV
      <hi>BOOKS</hi>.</titlePart>
    <titlePart>To which is added <title>SAMSON AGONISTES</title>.</titlePart>
  </docTitle>
  <byline>The Author <docAuthor>JOHN MILTON</docAuthor></byline>
  <docImprint><name>LONDON</name>, Printed by <name>J.M.</name> for <name>John
      Starkey</name> at the <name>Mitre</name> in <name>Fleetstreet</name>, near
      <name>Temple-Bar.</name></docImprint>
  <docDate>MDCLXXI</docDate>
</titlePage>

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

As elsewhere, the @ref attribute may be used to link a name with a canonical definition of the entity being named. For example: <byline>By <docAuthor><name ref="http://en.wikipedia.org/wiki/Agnes_Strickland">Agnes Strickland</name></docAuthor></byline>

Prefatory Matter

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

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

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

Liminal Elements

All text divisions, whether in front matter or elsewhere, may begin and end with one or more components which we term liminal elements, because they begin or end the division. A typical example is a heading or title of some kind which should be tagged using the <head> element; but there are many other possibilities:

As an example, the beginning and end of the dedication to Milton's Comus might be marked up as follows:

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

Back Matter

Structural Divisions of Back Matter

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

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

Specialized Front and Back Matter

TEI simplePrint also provides elements for some additional components of front or back matter which are characteristic of particular kinds of text, in particular old play texts. These often include lists of dramatis personae and notes about the setting of a play, for which the following elements are provided:

Note that these elements are intended for use in marking up cast lists and setting notes as they appear in a source document. They are not intended for use when marking up definitive lists of the different roles identified in a play, except in so far as that may have been their original purpose.

The following example shows one way of encoding the last part of Shakespeare's Tempest, as printed in the first folio:

<back>
  <div type="epilogue">
    <head>Epilogue, spoken by Prospero.</head>
    <sp>
      <l>Now my Charmes are all ore-throwne,</l>
      <l>And what strength I have's mine owne</l>
      <l>As you from crimes would pardon'd be,</l>
      <l>Let your Indulgence set me free.</l>
    </sp>
    <stage>Exit</stage>
  </div>
  <set>
    <p>The Scene, an un-inhabited Island.</p>
  </set>
  <castList>
    <head>Names of the Actors.</head>
    <castItem>Alonso, K. of Naples</castItem>
    <castItem>Sebastian, his Brother.</castItem>
    <castItem>Prospero, the right Duke of Millaine.</castItem>

  </castList>
  <trailer>FINIS</trailer>
</back>

Encoding a Digital Facsimile

The following elements may be used to encode a text represented by a collection of digital images, either alone or in conjunction with a textual transcription.

As mentioned in section Figures and Graphics above, a TEI simplePrint document may reference a set of page images, alone, or in combination with a transcription. For ease of management, it is strongly recommended that the <graphic> elements representing those page images be grouped together within a <facsimile> element, as in the following example:

<facsimile>
  <graphic url="page1.png" xml:id="pg1"/>
  <graphic url="page2.png" xml:id="pg2"/>
</facsimile>

If a transcription is supplied in addition, the @xml:id values can be used to align the page breaks within it with the relevant image, rather than using the URL given on the <graphic> element.

<text>

  <pb facs="#page1"/>

  <pb facs="#page2"/>

</text>

The <surface> element is useful in two situations: when it is desired to group different images of the same page, for example of different resolutions; and when it is desired to align parts of a page image with parts of a transcription. The <zone> element is used to define (and hence provide an identifier for) the location of a part of an image with reference to the surface on which it appears.

In this example, a thumbnail and a high resolution image are associated with the same surface:

<facsimile>
  <surface>
    <graphic xml:id="page1T" url="thumbs/page1.png"/>
    <graphic xml:id="page1" url="page1.png"/>
  </surface>
</facsimile>

In this example, the <head> element in the transcription is aligned with the top half of a square image:

<facsimile>
  <surface ulx="1" uly="1" lrx="4" lry="4">
    <graphic url="page1.png" xml:id="page1"/>
    <zone xml:id="topHalfP1" ulx="1" uly="1" lrx="2" lry="4"/>
  </surface>
</facsimile>
<text>
  <body>

    <pb facs="#page1"/>
    <head facs="#topHalfP1">Text of Heading</head>

  </body>
</text>

A more detailed explanation of the use of these attributes and other associated elements is given in the full TEI Guidelines.

The Electronic Title Page

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

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

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

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

The File Description

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

A minimal TEI header has the following structure:

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

The Title Statement

The following elements can be used in the <titleStmt> to provide information about the title of a work and those responsible for its content:

The title of a digital resource derived from a non-digital original may be similar to that of its source but should be distinct from it, for example:
[title of
               source]: TEI XML edition
or
A machine readable version of: [title of
                source]

The generic <respStmt> element may be used to indicate any kind of responsibility, ranging from a funder or sponsor to an illustrator or editor. It contains the following subcomponents: Example:

<titleStmt>
  <title>Two stories by Edgar Allen Poe </title>
  <author>Poe, Edgar Allen (1809-1849)</author>
  <respStmt>
    <resp>TEI encoding</resp>
    <name>James D. Benson</name>
  </respStmt>
  <respStmt>
    <resp>Funding </resp>
    <name>Getty Foundation</name>
  </respStmt>
</titleStmt>

The Edition Statement

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

Example:

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

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

The Extent Statement

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

Example:

<extent>15 Mb
</extent>

The Publication Statement

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

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

Example:

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

Series and Notes Statements

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

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

The Source Description

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

Examples:

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

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

The Encoding Description

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

Project Description and Sampling Declaration

Examples of <projectDesc> and <samplingDecl>:

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

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

Editorial Declarations

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

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

Example:

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

The full TEI Guidelines provide specialized elements for each of the topics above; these are not however included in TEI simplePrint.

Tagging Declaration

When it does not consist simply of a prose description, the <tagsDecl> element may contain a number of more specialized elements providing additional information about how the document concerned has been marked up. The following elements may be used:

Here is a simple example, showing how these elements may be used. It indicates the number of times the elements <hi> and <title> from the TEI namespace have been used in the document. It also documents how the way that the source document was originally printed has been represented using TEI tagging:

<tagsDecl partial="true">
  <rendition xml:id="rend-bo">font-weight:bold</rendition>
  <rendition xml:id="rend-it" selector="hi, title">font-style:italic</rendition>
  <namespace name="http://www.tei-c.org/ns/1.0">
    <tagUsage gi="hi" occurs="467"/>
    <tagUsage gi="title" occurs="45"/>
  </namespace>
</tagsDecl>

The <rendition> elements here contain fragments expressed in the W3C standard Cascading Stylesheets language (CSS). Their function here is to associate the particular styles concerned with an identifier (for example rend-bo) which can then be pointed to from elsewhere within the document by means of the @rendition attribute mentioned in section Changes of Typeface, etc. above. To indicate, for example, that a particular name in the document was rendered in a bold font it might be tagged <name rendition="#rend-bo">. The @selector attribute used in the preceding example is used to indicate once for all a default rendition value to be associated with several elements: in this example, unless otherwise indicated, it is assumed that the content of each <hi> and each <title> element was originally rendered using an italic font.

For TEI simplePrint, a large set of such rendition definitions has been predefined. The encoder is not therefore required to supply any detailed declarations, but can refer to the predefined list using the following list:

simple:allcaps
- all capitals
simple:blackletter
- black letter or gothic typeface
simple:bold
- bold typeface
simple:bottombraced
- marked with a brace under the bottom of the text
simple:boxed
- border around the text
simple:centre
- centred text
simple:cursive
- cursive typeface
simple:display
- block display
simple:doublestrikethrough
- strikethrough with double line
simple:doubleunderline
- underlined with double line
simple:dropcap
- initial letter larger or decorated
simple:float
- floated out of main flow
simple:hyphen
- with a hyphen here (e.g. in line break)
simple:inline
- inline rendering
simple:justify
- justified text
simple:italic
- italic typeface
simple:larger
- larger type
simple:left
- aligned to the left or left-justified
simple:leftbraced
- marked with a brace on the left side of the text
simple:letterspace
- larger-than-normal spacing between letters, usually for emphasis
simple:literal
- fixed-width typeface, spacing preserved
simple:normalstyle
- upright shape and default weight of typeface
simple:normalweight
- normal typeface weight
simple:right
- aligned to the right or right-justified
simple:rightbraced
- marked with a brace to the right of the text
simple:rotateleft
- rotated to the left
simple:rotateright
- rotated to the right
simple:smallcaps
- small caps
simple:smaller
- smaller type
simple:strikethrough
- strikethrough
simple:subscript
- subscript
simple:superscript
- superscript
simple:topbraced
- marked with a brace above the text
simple:typewriter
- fixed-width typeface, like typewriter
simple:underline
- underlined with single line
simple:wavyunderline
- underlined with wavy line

The "simple:" prefix used here must be mapped to a location at which the full rendition declaration can be found, by default the XML source of the present document.

Full details of the way these elements may be used are provided in the relevant section of the TEI Guidelines ().

Reference, Prefix, and Classification Declarations

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

Example:

<refsDecl>
  <p>The @n attribute on each &lt;div&gt; element 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 <listPrefixDef> element contains one or more <prefixDef> elements, each defining a prefix which has been used to abbreviate references to other documents, for example as the value of a @target or other pointing attribute. The definition provides information about how the prefix can be translated automatically into a full URL, as in the following example:

<listPrefixDef>
  <prefixDef ident="psn" matchPattern="([A-Z]+)" replacementPattern="http://www.example.com/personography.xml#$1"/>
</listPrefixDef>

In this case, a pointer value in the form "psn:MDH" would be translated to http://www.example.com/personography.xml#MDH.

The <classDecl> element groups together definitions or sources for any descriptive classification schemes or taxonomies used by other parts of the header. These schemes may be defined in a number of different ways, using one or more of the following elements:

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

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

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

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

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

The character declaration

As mentioned in section Formulae, Codes, and Special Characters above, the element <g> is used to indicate the presence of a nonstandard character or glyph in a transcription, and to reference a definition or description of it in the Header. These definitions are provided by means of the following specialised elements given within the <charDecl> component of the <encodingDesc>: For example, the alchemical symbol for air might be encoded where it appears in a text using a <g> element, whose @ref attribute might have a value "#air" to link to the following simple definition for the symbol concerned:

<char xml:id="air">
  <unicodeProp name="Name" value="ALCHEMICAL SYMBOL FOR AIR"/>
  <mapping type="standard">🜁</mapping>
</char>

Further details of these and related elements are provided in section of the TEI Guidelines.

The Profile Description

The <profileDesc> element gathers together information about various descriptive aspects of a text. It has the following optional components:

The <creation> element documents 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 <abstract> element may be used to provide a brief summary or abstract of the document concerned. It is most usually applied to texts born digital:

<profileDesc>
  <abstract>
    <p>This paper is a draft studying various aspects of using the TEI as a reference
      serialization framework for LMF. Comments are welcome to bring this to a useful
      document for the community.</p>
  </abstract>
</profileDesc>

The <particDesc> element is used to list descriptive information about the real or fictional participants in a text, for example the characters in a novel or a play. It contains at least one <listPerson> element, which contains individual <person> elements. For example:

<profileDesc>
  <particDesc>
    <listPerson>
      <person xml:id="OPI">
        <p><name>Dr Opimian</name>: named for the famous Roman fine wine.</p>
      </person>
      <person xml:id="GRM">
        <p><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.</p>
      </person>
    </listPerson>
  </particDesc>
</profileDesc>

In the same way, the <settingDesc> element can be used to list descriptive information about the real or fictional places mentioned in a text. It contains at least one <listPlace> element, which contains individual <place> elements. For example:

<profileDesc>
  <settingDesc>
    <listPlace>
      <head>Houses mentioned in <title>Pride and Prejudice</title></head>
      <place xml:id="NETF1">
        <p><name>Netherfield Park</name>: home of the Bingleys</p>
      </place>
      <place xml:id="PEMB1">
        <p><name>Pemberley</name>: home of Mr Darcy</p>
      </place>
    </listPlace>
  </settingDesc>
</profileDesc>

The full TEI Guidelines provide a rich range of additional elements to define more structured information about persons and places; these are not however available in TEI Simple.

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

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

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

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

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

The element <keywords> contains one or more keywords or phrases identifying the topic or nature of a text, each tagged as a <term>. 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">
    <term>English literature</term>
    <term>History and criticism</term>
    <term>Data processing.</term>
  </keywords>
</textClass>

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

Other forms of metadata

The TEI header was one of the first attempts to provide a full range of metadata elements, but it is by no means the only standard now used for this purpose. To facilitate the management of large digital collections and to simplify interoperability of TEI and non-TEI resources, the following element may be found useful:

A typical use for this element might be to store a set of descriptors conforming to the Dublin Core standard in the TEI header rather than to generate them automatically from the corresponding TEI elements. For examples and discussion, see the TEI Guidelines at

The Revision Description

The <revisionDesc> element provides a change log in which each significant change made to a text may be recorded. It is always the last element in a <teiHeader> and contains the following elements:

Each <change> element contains a brief description of a significant change. The attributes @when and @who may be used to identify when the change was carried out and the person responsible for it.

It is good practice (but not required) to group changes together within a <listChange> element.

Example:

<revisionDesc>
  <listChange>
    <change when="1991-11-11" who="#LB">deleted chapter 10</change>
    <change when="1991-11-02" who="#MSM">completed first draft</change>
  </listChange>
</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.

The Simple Processing Model

Unlike most other TEI customizations, TEI simplePrint includes documentation of the intended processing associated with the majority of elements. As noted above, the TEI provides components such as the @rendition attribute to indicate the appearance of particular parts of a document in the non-digital source from which it is derived. With TEI simplePrint, it is also possible to indicate how in general an element should be processed, in particular its intended appearance when processed for display on a screen or on paper. This ability derives from a number of capabilities recently added to the TEI architecture for the specification of processing, which were developed as part of the project that defined the TEI simplePrint schema.

The key feature of this Processing Model is a notation that allows the encoder to associate each element with one or more categories, which we call its behaviours. In addition, the Processing Model indicates how the element should be rendered, possibly differently in differing circumstances, using the W3C Cascading Style Sheets (CSS) mentioned above. It is consequently much easier to develop processors for documents conforming to TEI simplePrint, since the complexity of the task is much reduced.

Twenty-five different behaviours are currently defined by the TEI Processing Model. Their names indicate informally the categorization concerned, and should be readily comprehensible for most programmers. The following table indicates the TEI simplePrint elements associated with each:

Behaviour	Used by	Effect
alternate	choice date	support display of alternative visualizations, for example by displaying the preferred content, by displaying both in parallel, or by toggling between the two.
anchor	anchor	create an identifiable anchor point in the output.
block	address addrLine argument back body byline closer dateline div docTitle epigraph figure floatingText formula front fw group head imprimatur l lg listBibl note opener postscript q quote role roleDesc salute signed sp speaker spGrp stage titlePage titlePart trailer	create a block structure
body	text	create the body of a document
break	cb lb pb	create a line, column, or page break according to the value of type
cell	cell	create a table cell
cit	cit	show the content, with an indication of the source
document	TEI	start a new output document
glyph	g	show a character by looking up reference to a chardesc at the given URI
graphic	graphic	if URL is present, use it to display graphic, else display a placeholder image
heading	head	creates a heading
index	body	generate list according to type
inline	abbr actor add am author bibl biblScope c choice code corr date del desc docAuthor docDate docEdition docImprint editor email ex expan figDesc figure foreign formula fw g gap hi label measure milestone name note num orig pc q quote ref reg relatedItem rhyme rs s salute seg sic signed subst supplied time title unclear w	creates inline element out of content if there's something in <outputRendition>, use that formatting; otherwise just show text of selected content
link	ref	create hyperlink
list	castGroup castList list listBibl	create a list
listItem	bibl castItem item	create a list item
metadata	teiHeader	create metadata section
note	note	create a note, often out of line, depending on the value of place; could be margin, footnote, endnote, inline
omit	author editor publisher pubPlace profileDesc revisionDesc encodingDesc	do nothing, do not process children
paragraph	ab p	create a paragraph out of content
row	row	create a table row
section	div	create a new section of the output document
table	table	create a table
text	title	create literal text
title	fileDesc	create document title

Full documentation of the Processing Model is provided in section of the TEI Guidelines, and we do not describe it further here.

The TEI simplePrint schema

Like other TEI customizations, TEI simplePrint is defined by reference to the TEI Guidelines. The following reference documentation provides formal specifications for each element, model class, attribute class, macro and datatype it uses. These concepts are further explained in the TEI Guidelines.

Specifications are provided here for each component which has been modified for inclusion in TEI simplePrint. Almost every textual element has been modified, if only to include a processing model component. Note that the cross references included in these specifications are to the section of the full TEI Guidelines where the subject is treated, and not to sections of the present document.

Summary of changes

The TEI simplePrint schema uses the TEI infrastructure and gaiji modules unchanged.

A subset of 45 elements is selected from the TEI header module. In addition, elements <particDesc> and <settingDesc> are provided from the corpus module. The class membership of <particDesc> is changed to ensure that it can only appear inside <profileDesc>. Secondly, a Schematron rule is added to the <text> element to ensure that elements <term> and <biblFull> can appear only in the header element, even though the schema permits them additionally in text.

Some attributes and attribute classes are removed. The range of values available for several attributes is constrained.

att.datcat

att.declarable

att.declaring

att.ranging

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

att.canonical
@key

att.editLike
@evidence
@instant

att.pointing
@target
Error: Every local pointer in "" must point to an ID in this document ()

att.global.rendition
Error: Each of the rendition values in "" must point to a local ID or to a token in the Simple scheme () Error: Every local pointer in "" must point to an ID in this document ()
@rend
@style
@rendition
"simple:allcaps"
all capitals
"simple:blackletter"
black letter or gothic typeface
"simple:bold"
bold typeface
"simple:bottombraced"
marked with a brace under the bottom of the text
"simple:boxed"
border around the text
"simple:centre"
centred
"simple:cursive"
cursive typeface
"simple:display"
block display
"simple:doublestrikethrough"
strikethrough with double line
"simple:doubleunderline"
underlined with double line
"simple:dropcap"
initial letter larger or decorated
"simple:float"
floated out of main flow
"simple:hyphen"
with a hyphen here (eg in line break)
"simple:inline"
inline rendering
"simple:justify"
justified text
"simple:italic"
italic typeface
"simple:larger"
larger type
"simple:left"
aligned to the left or left-justified
"simple:leftbraced"
marked with a brace on the left side of the text
"simple:letterspace"
larger-than-normal spacing between letters, usually for emphasis
"simple:literal"
fixed-width typeface, spacing preserved
"simple:normalstyle"
upright shape and default weight of typeface
"simple:normalweight"
normal typeface weight
"simple:right"
aligned to the right or right-justified
"simple:rightbraced"
marked with a brace to the right of the text
"simple:rotateleft"
rotated to the left
"simple:rotateright"
rotated to the right
"simple:smallcaps"
small caps
"simple:smaller"
smaller type
"simple:strikethrough"
strike through
"simple:subscript"
subscript
"simple:superscript"
superscript
"simple:topbraced"
marked with a brace above the text
"simple:typewriter"
fixed-width typeface, like typewriter
"simple:underline"
underlined with single line
"simple:wavyunderline"
underlined with wavy line

att.placement
@place
"above"
above the line
"below"
below the line
"top"
at the top of the page
"top-right"
at the top right of the page
"top-left"
at the top left of the page
"top-centre"
at the top center of the page
"bottom-right"
at the bottom right of the page
"bottom-left"
at the bottom left of the page
"bottom-centre"
at the bottom centre of the page
"bottom"
at the foot of the page
"tablebottom"
underneath a table
"margin-right"
in the right-hand margin
"margin"
in the outer margin
"margin-inner"
in the inner margin
"margin-left"
in the left-hand margin
"opposite"
on the opposite, i.e. facing, page.
"overleaf"
on the other side of the leaf.
"overstrike"
superimposed on top of the current context
"end"
at the end of the volume.
"divend"
at the end the current division.
"parend"
at the end the current paragraph.
"inline"
within the body of the text.
"inspace"
in a predefined space, for example left by an earlier scribe.
"block"
formatted as an indented paragraph

att.dimensions
@unit
"chars"
characters
"lines"
lines
"pages"
pages
"words"
words
"cm"
centimetres
"mm"
millimetre
"in"
inches
@precision

The following unused model classes are removed.

model.certLike

model.egLike

model.entryPart

model.glossLike

model.oddDecl

model.offsetLike

model.pPart.msdesc

model.placeNamePart

model.placeStateLike

model.specDescLike

The following elements are modified by the TEI simplePrint specification, mostly by the addition of a processing model, but in other cases by additional constraints on the attributes they may have, or the values those attributes may take. Additional examples are also provided for some of them.

<ab>

<abbr>
@type

<actor>

<add>
color: green; text-decoration: underline;

<address>
margin-top: 2em; margin-left: 2em; margin-right: 2em; margin-bottom: 2em;

<addrLine>
white-space: nowrap;

<am>

<anchor>

<argument>
margin-bottom: 0.5em;

<argument>
  <l>With ſighs and tears her love he doth deſire,</l>
  <l>Since Cupid hath his ſenſes ſet on fire;</l>
  <l>His torment and his pain to her he ſhews,</l>
  <l>With all his proteſtations and his vows:</l>
  <l>At laſt ſhe yields to grant him ſome relief,</l>
  <l>And make him joyful after all his grief.</l>
</argument>

<author>

<back>

<bibl>
Element "" may not be empty.

<epigraph>
  <bibl>Deut. Chap. 5.</bibl>
  <q>11 Thou ſhalt not take the name of the Lord thy God in vaine, for the Lord
    will not hold him guiltleſſe which ſhall take his name in vaine.</q>
</epigraph>

<biblFull>

<sourceDesc>
  <biblFull>
    <titleStmt>
      <title>Buxom Joan of Lymas's love to a jolly sailer: or, The maiden's
        choice: being love for love again. To an excellent new play-house
        tune.</title>
      <author>Congreve, William, 1670-1729.</author>
    </titleStmt>
    <extent>1 sheet ([1] p.) : music. </extent>
    <publicationStmt>
      <publisher>printed for P[hilip]. Brooksby, at the Golden-ball, in
        Pye-corner.,</publisher>
      <pubPlace>London: :</pubPlace>
      <date>[between 1693-1695]</date>
    </publicationStmt>
    <notesStmt>
      <note>Attributed to William Congreve by Wing.</note>
      <note>Date of publication and publisher's name from Wing.</note>
      <note>Verse: "A soldier and a sailer ..."</note>
      <note>Printed in two columns.</note>
      <note>Reproduction of original in the British Library.</note>
    </notesStmt>
  </biblFull>
</sourceDesc>

<biblScope>

<body>

<byline>

<c>

<castGroup>
Insert list.

<castItem>
Insert item, rendered as described in parent list rendition.

<castList>
list-style: ordered;

<cb>

<cell>
@role
"data"
data cell
"label"
label cell
"sum"
row or column sum data
"total"
table total data
Insert table cell.

<choice>
Element "" must have corresponding corr/sic, expand/abbr, reg/orig

<cit>
Insert citation

<closer>
margin-top: 1em; margin-left: 1em; margin-left: 1em;

<code>
font-family:monospace

<corr>
simple inline, if in parent choice. content: '['; content: ']';

<date>

<dateline>

<del>
text-decoration: line-through;

<desc>

<div>
border: 1px solid black; padding: 5px;

<docAuthor>

<docDate>

<docEdition>

<docImprint>

<docTitle>
font-size: larger;

<editor>

<editorialDecl>

<encodingDesc>
  <editorialDecl>
    <p>EEBO-TCP is a partnership between the Universities of Michigan and Oxford
      and the publisher ProQuest to create accurately transcribed and encoded
      texts based on the image sets published by ProQuest via their Early English
      Books Online (EEBO) database (http://eebo.chadwyck.com). The general aim of
      EEBO-TCP is to encode one copy (usually the first edition) of every
      monographic English-language title published between 1473 and 1700 available
      in EEBO.</p>
    <p>EEBO-TCP aimed to produce large quantities of textual data within the usual
      project restraints of time and funding, and therefore chose to create
      diplomatic transcriptions (as opposed to critical editions) with
      light-touch, mainly structural encoding based on the Text Encoding
      Initiative (http://www.tei-c.org).</p>
    <p>The EEBO-TCP project was divided into two phases. The 25,363 texts created
      during Phase 1 of the project have been released into the public domain as
      of 1 January 2015. Anyone can now take and use these texts for their own
      purposes, but we respectfully request that due credit and attribution is
      given to their original source.</p>
    <p>Users should be aware of the process of creating the TCP texts, and
      therefore of any assumptions that can be made about the data.</p>
    <p>Text selection was based on the New Cambridge Bibliography of English
      Literature (NCBEL). If an author (or for an anonymous work, the title)
      appears in NCBEL, then their works are eligible for inclusion. Selection was
      intended to range over a wide variety of subject areas, to reflect the true
      nature of the print record of the period. In general, first editions of a
      works in English were prioritized, although there are a number of works in
      other languages, notably Latin and Welsh, included and sometimes a second or
      later edition of a work was chosen if there was a compelling reason to do
      so.</p>
    <p>Image sets were sent to external keying companies for transcription and
      basic encoding. Quality assurance was then carried out by editorial teams in
      Oxford and Michigan. 5% (or 5 pages, whichever is the greater) of each text
      was proofread for accuracy and those which did not meet QA standards were
      returned to the keyers to be redone. After proofreading, the encoding was
      enhanced and/or corrected and characters marked as illegible were corrected
      where possible up to a limit of 100 instances per text. Any remaining
      illegibles were encoded as &lt;gap&gt;s. Understanding these processes
      should make clear that, while the overall quality of TCP data is very good,
      some errors will remain and some readable characters will be marked as
      illegible. Users should bear in mind that in all likelihood such instances
      will never have been looked at by a TCP editor.</p>
    <p>The texts were encoded and linked to page images in accordance with level 4
      of the TEI in Libraries guidelines.</p>
    <p>Copies of the texts have been issued variously as SGML (TCP schema; ASCII
      text with mnemonic sdata character entities); displayable XML (TCP schema;
      characters represented either as UTF-8 Unicode or text strings within
      braces); or lossless XML (TEI P5, characters represented either as UTF-8
      Unicode or TEI g elements).</p>
    <p>Keying and markup guidelines are available at the <ref target="http://www.textcreationpartnership.org/docs/.">Text Creation
        Partnership web site</ref>.</p>
  </editorialDecl>
</encodingDesc>

<email>
font-family:monospace

<epigraph>

<epigraph>
  <bibl>Deut. Chap. 5.</bibl>
  <q>11 Thou ſhalt not take the name of the Lord thy God in vaine, for the Lord
    will not hold him guiltleſſe which ſhall take his name in vaine.</q>
</epigraph>

<ex>

<expan>

<figDesc>
content: '[..'; content: '..]'; color: grey;font-style:italic;

<figure>
display: block; border-top: solid 1pt blue; border-bottom: solid 1pt blue;

<floatingText>
margin: 6pt; border: solid black 1pt;

<foreign>
font-style:italic;

<formula>
@notation
"TeX"
Using TeX or LaTeX notation

<front>

<fw>

<g>

<gap>
@hand
color: grey; content: '[..'; content: '..]'; color: grey; content: '[...]';

<graphic>

<group>

<head>
font-style: italic; font-style: italic; font-style: italic; font-weight: bold;

<hi>
font-style: italic; font-style: italic;

<imprimatur>

<item>

<l>
margin-left: 1em;

<argument>
  <l>With ſighs and tears her love he doth deſire,</l>
  <l>Since Cupid hath his ſenſes ſet on fire;</l>
  <l>His torment and his pain to her he ſhews,</l>
  <l>With all his proteſtations and his vows:</l>
  <l>At laſt ſhe yields to grant him ſome relief,</l>
  <l>And make him joyful after all his grief.</l>
</argument>

<label>

<lb>

<lg>

<list>

<listBibl>

<measure>

<milestone>

<name>
@type
"person"
"forename"
"surname"
"personGenName"
"personRoleName"
"personAddName"
"nameLink"
"org"
"country"
"placeGeog"
"place"

<note>
margin-left: 10px;margin-right: 10px; font-size:smaller; content:" ["; content:"] "; font-size:small;

<num>

<opener>

<orig>

<p>
text-align: justify;

<particDesc>

<particDesc>
  <listPerson>
    <person xml:id="Trinder" sex="m">
      <p>
        <name type="surname">Trinder</name>
        <name type="forename">William</name>
        <name type="forename">Martin</name>
      </p>
    </person>
    <person xml:id="Leland" sex="m">
      <p>
        <name type="surname">Leland</name>
        <name type="forename">Thomas</name>
      </p>
    </person>
  </listPerson>
</particDesc>

<pb>
display: block; margin-left: 4pt; color: grey; float: right; content: '[Page '; content: ']';

<pc>

<person>

<person sex="1">
  <p>William Shakespeare, born in Stratford-upon-Avon, 26 April 1564, died in
    Stratford-upon-Avon, 23 April 1616, English playwright and poet</p>
</person>

<person xml:id="Stevenson" sex="m" role="writer">
  <p>
    <name type="surname">Stevenson</name>
    <name type="forename">Robert</name>
    <name type="forename">Louis</name>
  </p>
</person>

<place>

<place xml:id="Hereford">
  <p>
    <name type="place">Hereford</name>
    <name type="country">England</name>
  </p>
</place>

<place xml:id="Lithuania">
  <p>
    <name type="country">Lithuania</name>
    <name type="country" xml:lang="lt">Lietuva</name>
  </p>
  <place xml:id="Vilnius">
    <p>
      <name>Vilnius</name>
    </p>
  </place>
  <place xml:id="Kaunas">
    <p>
      <name>Kaunas</name>
    </p>
  </place>
</place>

<postscript>

<profileDesc>

<profileDesc>
  <creation>
    <date notAfter="1623"/>
  </creation>
  <langUsage>
    <language ident="eng">English</language>
  </langUsage>
  <textClass>
    <keywords scheme="#LCSH">
      <term type="genre">Plays -- England -- 16th century</term>
      <term type="genre">Plays -- England -- 17th century</term>
      <term type="genre">Comedies -- England -- 16th century</term>
      <term type="genre">Comedies -- England -- 17th century</term>
      <term type="genre">Tragedies -- England -- 16th century</term>
      <term type="genre">Tragedies -- England -- 17th century</term>
    </keywords>
  </textClass>
</profileDesc>

Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.

<publisher>
Omit if located in teiHeader.

<pubPlace>
Omit if located in teiHeader.

<q>
margin-left: 10px; margin-right: 10px; content: '‘'; content: '’'; margin-left: 10px; margin-right: 10px;

<quote>
If it is inside a paragraph then it is inline, otherwise it is block level content: '‘'; content: '’'; If it is inside a paragraph then it is inline, otherwise it is block level margin-left: 10px; margin-right: 10px;

<ref>

<reg>

<relatedItem>

<bibl xml:id="Shirley1953">
  <author>Shirley, James</author>
  <title type="main">The gentlemen of Venice</title>
  <pubPlace>New York</pubPlace>
  <publisher>Readex Microprint</publisher>
  <date>1953</date>
  <extent>1 microprint card, 23 x 15 cm.</extent>
  <relatedItem type="otherForm">
    <bibl>
      <author>Shirley, James</author>
      <title type="main">The gentlemen of Venicd</title>
      <title type="sub">a tragi-comedie presented at the private house in
        Salisbury Court by Her Majesties servants</title>
      <pubPlace>London</pubPlace>
      <publisher>H. Moseley</publisher>
      <date>1655</date>
      <extent>78 p.</extent>
    </bibl>
  </relatedItem>
</bibl>

<relatedItem type="otherForm" target="http://www.example.com/bibliography.xml#Shirley1655"/>

If the @target attribute is used to reference the related bibliographic item, the element must be empty.

<rhyme>

<role>

<roleDesc>

<row>
@role
"data"
data cell
"label"
label cell
"sum"
row or column sum data
"total"
table total data
font-weight: bold; Insert table row.

<rs>

<s>

<salute>

<seg>

<set>

Contains paragraphs or phrase level tags.

This element should not be used outside the front or back matter; for similar contextual descriptions within the body of the text, use the <stage> element.

<sic>
content: '{'; content: '}';

<signed>
text-align: right; font-style: italic;

<sp>

<speaker>
font-style:italic;

<div type="Act" n="I">
  <head>ACT I</head>
  <div type="Scene" n="1">
    <head>SCENE I</head>
    <stage rendition="#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>

<spGrp>

<stage>
font-style: italic;

<subst>

<supplied>
content:"<"; content:">"; content:"["; content:"]"; content:"("; content:")"; content:"{"; content:"}";

<table>
font-size: smaller; background-color: #F0F0F0;

<taxonomy>

<classDecl>
  <taxonomy xml:id="OTASH">
    <bibl>University of Oxford Text Archive Subject Headings</bibl>
  </taxonomy>
</classDecl>

<taxonomy>
  <category xml:id="literature">
    <catDesc>Literature</catDesc>
    <category xml:id="poetry">
      <catDesc>Poetry</catDesc>
      <category xml:id="sonnet">
        <catDesc>Sonnet</catDesc>
        <category xml:id="shakesSonnet">
          <catDesc>Shakespearean Sonnet</catDesc>
        </category>
        <category xml:id="petraSonnet">
          <catDesc>Petrarchan Sonnet</catDesc>
        </category>
      </category>
      <category xml:id="haiku">
        <catDesc>Haiku</catDesc>
      </category>
    </category>
    <category xml:id="drama">
      <catDesc>Drama</catDesc>
    </category>
  </category>
  <category xml:id="meter">
    <catDesc>Metrical Categories</catDesc>
    <category xml:id="feet">
      <catDesc>Metrical Feet</catDesc>
      <category xml:id="iambic">
        <catDesc>Iambic</catDesc>
      </category>
      <category xml:id="trochaic">
        <catDesc>trochaic</catDesc>
      </category>
    </category>
    <category xml:id="feetNumber">
      <catDesc>Number of feet</catDesc>
      <category xml:id="pentameter">
        <catDesc>Pentameter</catDesc>
      </category>
      <category xml:id="tetrameter">
        <catDesc>Tetrameter</catDesc>
      </category>
    </category>
  </category>
</taxonomy>

<lg ana="#shakesSonnet #iambic #pentameter">
  <l>Shall I compare thee to a summer's day</l>

</lg>

<fileDesc>

<revisionDesc>

<encodingDesc>

<teiHeader>
@type

<teiHeader>
  <fileDesc>
    <titleStmt>
      <title>THE TEMPEST.</title>
      <author>Shakespeare, William, 1564-1616</author>
    </titleStmt>
    <publicationStmt>
      <distributor>
        <name>University of Oxford Text Archive</name>
        <address>
          <addrLine>Oxford University Computing Services</addrLine>
          <addrLine>13 Banbury Road</addrLine>
          <addrLine>Oxford</addrLine>
          <addrLine>OX2 6NN</addrLine>
        </address>
        <email>ota@oucs.ox.ac.uk</email>
      </distributor>
      <idno type="ota">http://ota.ox.ac.uk/id/5725</idno>
      <idno type="isbn10">1106027248</idno>
      <idno type="isbn13">9781106027245</idno>
      <availability status="free">
        <licence target="http://creativecommons.org/licenses/by-sa/3.0/">
          Distributed by the University of Oxford under a Creative Commons
          Attribution-ShareAlike 3.0 Unported License </licence>
      </availability>
    </publicationStmt>
    <sourceDesc>
      <bibl>Revised version of <relatedItem type="older" target="http://ota.ox.ac.uk/id/0119"/>
      </bibl>
      <bibl>The texts were originally prepared by Trevor Howard-Hill for use in
        his single volume concordances to Shakespeare (OUP, 1969f). They have
        since been reformatted to modern standards and carefully proofread by
        staff of Oxford University Press' Shakespeare Department for use in the
        new "Old Spelling" Oxford Shakespeare, under the general editorship of Dr
        Stanley Wells: <title>The complete works / William Shakespeare</title>;
        general editors, Stanley Wells and Gary Taylor ; editors Stanley Wells ...
        [et al.] ; with introductions by Stanley Wells. -- Oxford : Clarendon
        Press, 1986. -- (Oxford Shakespeare). -- ISBN 0-19-812926-2</bibl>
      <biblFull>
        <titleStmt>
          <title>THE TEMPEST.</title>
          <author>Shakespeare, William, 1564-1616</author>
          <editor role="editor">Lee, Sidney, Sir, 1859-1926</editor>
        </titleStmt>
        <extent>xxxv, 908 p. : facsims. ; 39 cm.</extent>
        <publicationStmt>
          <publisher>Clarendon Press</publisher>
          <pubPlace>Oxford</pubPlace>
          <date>1902</date>
        </publicationStmt>
      </biblFull>
    </sourceDesc>
  </fileDesc>
  <encodingDesc>
    <classDecl>
      <taxonomy xml:id="OTASH">
        <bibl>University of Oxford Text Archive Subject Headings</bibl>
      </taxonomy>
      <taxonomy xml:id="LCSH">
        <bibl>Library of Congress Subject Headings</bibl>
      </taxonomy>
    </classDecl>
  </encodingDesc>
  <profileDesc>
    <creation>
      <date notAfter="1623"/>
    </creation>
    <langUsage>
      <language ident="eng">English</language>
    </langUsage>
    <textClass>
      <keywords scheme="#LCSH">
        <term type="genre">Plays -- England -- 16th century</term>
        <term type="genre">Plays -- England -- 17th century</term>
        <term type="genre">Comedies -- England -- 16th century</term>
        <term type="genre">Comedies -- England -- 17th century</term>
        <term type="genre">Tragedies -- England -- 16th century</term>
        <term type="genre">Tragedies -- England -- 17th century</term>
      </keywords>
    </textClass>
  </profileDesc>
  <revisionDesc>
    <change when="2010-08-31">Header normalised</change>
  </revisionDesc>
</teiHeader>

<TEI>
@version

<term>

<keywords>
  <term>huntin</term>
  <term>shootin</term>
  <term>fishin</term>
</keywords>

This element should only be used in the TEI Header

<text>
Error: The element is not permitted outside the header max-width: 80%; margin: auto; font-family: Verdana, Tahoma, Geneva, Arial, Helvetica, sans-serif;

<time>

<title>
color: red; font-size: 2em; font-style: italic; font-style: italic; font-style: italic; font-style: italic;

<titlePage>
text-align: center;

<titlePart>

<trailer>
color: green;

<unclear>
@hand
content: ' [?] ';

<w>

<s n="1">
  <w ana="#NP0" type="open" lemma="Marley">Marley</w>
  <w ana="#VBD" type="verb" lemma="be">was</w>
  <w ana="#AJ0" type="complement" lemma="die">dead</w>
</s>