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 —

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 Edward (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 faà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 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 honeymoon 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 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.

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. div (text division) contains a subdivision of the front, body, or back of a text.type [att.typed]characterizes the element in some sense, using any convenient classification scheme or typology.

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

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

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:

Every <div> may have a title or heading at its start, and (less commonly) a trailer such as End of Chapter 1 at its end. The following elements may be used to transcribe them: head (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc.trailer contains a closing title or footer appearing at the end of a division of a text. Some other elements which may be found at the beginning or ending of text divisions are discussed below in section .

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

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: p (paragraph) marks paragraphs in prose.ab (anonymous block) contains any component-level unit of text, acting as a container for phrase or inter level elements analogous to, but without the same constraints as, a paragraph.l (verse line) contains a single, possibly incomplete, line of verse.lg (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc.sp (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text.speaker contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment.stage (stage direction) contains any kind of stage direction within a dramatic text or fragment.

We discuss each of these kinds of component separately below.

Page and line breaks etc. may be marked with the following elements:pb (page beginning) marks the beginning of a new page in a paginated document.lb (line beginning) marks the beginning of a topographic line in some edition or version of a text.cb (column beginning) marks the beginning of a new column of a text on a multi-column page.milestone (milestone) marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element.fw (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. 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: Mary had a little lambIts fleece was white as snow The <pb> element should be placed ahead of all the text encoded on the 13th page. Contrast this with the following less accurate encoding: Mary had a little lambIts fleece was white as snow 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):

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

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: He also fix'd the wandering QUEEN OF NIGHT,Ii 2WhetherWhether she wanes into a scanty orb...

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:

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 Mary approved the step unreservedly...

A more powerful approach, discussed in section 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.

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. note (note) contains a note or annotation.

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:

...some text a note about some text ....

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:

...some text 7 .... a note about some text

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.

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 .

The following elements may be used to mark corrections, that is editorial changes introduced where the editor believes the original to be erroneous: corr (correction) contains the correct form of a passage apparently erroneous in the copy text.sic (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate.

The following elements may be used to mark normalization, that is editorial changes introduced for the sake of consistency or modernization of a text: orig (original form) contains a reading which is marked as following the original, rather than being normalized or corrected.reg (regularization) contains a reading which has been regularized or normalized in some sense.

Consider, for example, the following famous passage as it appears in the first quarto printing of Shakespeare's :

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 sharp as a Pen and hebabbl'd 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 sharpe as a Pen, and aTable of green fields

Finally, a modern digital editor may decide to combine both possibilities in a single composite text, using the <choice> element. choice (choice) groups a number of alternative encodings for the same point in a text. This allows an editor to indicate where alternative encodings are possible: ... for his Nose was as sharpesharp as a Pen, and ahebabbl'dTable of green fields

In addition to correcting or normalizing words and phrases, editors and transcribers may also supply missing material, omit material, or transcribe material deleted or crossed out in the source. In addition, some material may be particularly hard to transcribe because it is hard to make out on the page. The following elements may be used to record such phenomena: add (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector.gap (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.del (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector.unclear (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source.supplied (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe.subst (substitution) groups one or more deletions (or surplus text) with one or more additions when the combination is to be regarded as a single intervention in the text.

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 for 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 are 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:

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:

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:

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 & twenty good regulars joined to me and 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:

... An example of a list appearing in a fief ledger of Koldinghus1611/12 is given below. It shows cash income from a sale of honey.

A description of the overall structure of the account is once again ...

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

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

Like names, dates, and numbers, abbreviations may be transcribed as they stand or expanded; they may be left unmarked, or encoded using the following elements: abbr (abbreviation) contains an abbreviation of any sort.expan (expansion) contains the expansion of an abbreviation.

The <abbr> element is useful as a means of distinguishing semi-lexical items such as acronyms or jargon: Every manufacturer of 3GL or 4GL languages is currently nailing on OOP 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: per

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

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.

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: rs (referencing string) contains a general purpose name or referring string.name (name, proper noun) contains a proper noun or noun phrase.

The type attribute is used to distinguish amongst (for example) names of persons, places and organizations, where this is possible: My dear Mr. Bennet, said his lady to him one day, have you heard that Netherfield Park is let at last? It being one of the principles of the Circumlocution Office never, on any account whatsoever, to give a straightforward answer, Mr Barnacle said, Possibly.

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: My dear Mr. Bennet, said his lady 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: My dear Mr. Bennet, said his lady to him one day, have you heard that Netherfield Park is let at last?

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 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: Walter de la Marede la Mare, Walter was born at Charlton, in Kent, in 1873.

The following elements may be useful when marking up sequences of text that represent mathematical expressions, chemical formulae, and the like: formula (formula) contains a mathematical or other formula.g (character or glyph) represents a glyph, or a non-standard character.

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: E=mc² 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 [air] and ... The TEI header provides a number of additional elements for the definition of such non-Unicode characters, as further discussed in section below.

The following elements are useful for stretches of code or similar formal language appearing within a text: code contains literal code from some formal language such as a programming language.email (electronic mail address) contains an email address identifying a location to which email messages can be delivered.

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

The element <ref> discussed in section 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:

Further discussion of the Text Encoding Initiative website may be found at http://www.tei-c.org/

The following elements are provided for the detailed encoding of times and dates: date (date) contains a date in any format.time (time) contains a phrase defining a time of day in any format.

These elements have a number of attributes which can be used to provide normalized versions of their values in various ways. att.datable provides attributes for normalization of elements that contain dates, times, or datable events.periodsupplies pointers to one or more definitions of named periods of time (typically <category>s, <date>s, or events) within which the datable item is understood to have occurred.when [att.datable.w3c]supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.notBefore [att.datable.w3c]specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.notAfter [att.datable.w3c]specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd. The when attribute specifies a normalized form for the date or time, using one of the standard formats defined by ISO 8601. Partial dates or times (e.g. 1990, September 1990, twelvish) can be expressed by omitting a part of the value supplied, as in the following examples: 21 Feb 19801990September 1990SeptemberSept 11th, 12 minutes before 9 am

These attributes are typically used to make a date or time more easily processable, as in the following examples: Given on the 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. specially when it's nine below zeroand three o'clock in the afternoon They are also useful in cases where the date concerned is uncertain or only vaguely specified:

... during the second empire

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: num (number) contains a number, written in any form.typeindicates the type of numeric value.valuesupplies the value of the number in standard form.measure (measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name.quantity [att.measurement](quantity) specifies the number of the specified units that comprise the measurementunit [att.measurement](unit) indicates the units used for the measurement, usually using the standard symbol for the desired units.commodity [att.measurement](commodity) indicates the substance that is being measured

For example: xxxiiitwenty-oneten percent10%5th 2 score hh rum1 doz. rosesa yellow tulip

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

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

Tokenization, that is, the identification of lexical or non-lexical tokens within a text, is a very common requirement for all kinds of textual analysis, and not an entirely trivial one. The decision as to whether, for example, can't in English or du in French should be treated as one word or two is not simple. Consequently it is often useful to make explicit the preferred tokenization in a marked up text. The following elements are available for this purpose: w (word) represents a grammatical (not necessarily orthographic) word.c (character) represents a character.pc (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark.

For example, the output from a part of speech tagger might be recorded in TEI simplePrint as follows: Marleywasdead:tobeginwith.

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

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

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.

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

A minimal TEI header has the following structure:

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: projectDesc (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected.samplingDecl (sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource.editorialDecl (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text.tagsDecl (tagging declaration) provides detailed information about the tagging applied to a document.refsDecl (references declaration) specifies how canonical references are constructed for this text.listPrefixDef (list of prefix definitions) contains a list of definitions of prefixing schemes used in teidata.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs.prefixDef (prefix definition) defines a prefixing scheme used in teidata.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs.classDecl (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text.charDecl (character declarations) provides information about nonstandard characters and glyphs.

The <profileDesc> element gathers together information about various descriptive aspects of a text. It has the following optional components: creation (creation) contains information about the creation of a text.abstract contains a summary or formal abstract prefixed to an existing source document by the encoder.particDesc (participation description) describes the identifiable speakers, voices, or other participants in any kind of text or other persons named or otherwise referred to in a text, edition, or metadata.settingDesc (setting description) describes the setting or settings within which a language interaction takes place, or other places otherwise referred to in a text, edition, or metadata.langUsage (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text.textClass (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc.

The <creation> element documents where a work was created, even though it may not have been published or recorded there:

Example: August 1992Taos, New Mexico

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:

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.

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.listPerson (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source.person (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. For example:

Dr Opimian: named for the famous Roman fine wine.

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. listPlace (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them.place (place) contains data about a geographic location. For example: Houses mentioned in

Netherfield Park: home of the Bingleys

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: language (language) characterizes a single language or sublanguage used within a text. For example, a text containing predominantly text in French as spoken in Quebec, but also smaller amounts of British and Canadian English might be documented as follows: QuébecoisCanadian Business EnglishBritish English

The <textClass> element classifies a text. This may be done with reference to a classification system locally defined by means of the <classDecl> element, or by reference to some externally defined established scheme such as the Universal Decimal Classification. Texts may also be classified using lists of keywords, which may themselves be drawn from locally or externally defined control lists. The following elements are used to supply such classifications: classCode (classification code) contains the classification code used for this text in some standard classification system.catRef (category reference) specifies one or more defined categories within some taxonomy or text typology.keywords (keywords) contains a list of keywords or phrases identifying the topic or nature of a text.

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

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:

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: English literatureHistory and criticismData processing.

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

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: xenoData (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed.

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 <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: change (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file.listChange groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text.

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: deleted chapter 10completed first draft

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.