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 these paragraphs may be grouped together into chapters, sections, subsections, etc. Each paragraph is tagged using the <p> tag. The <div> element is used to represent any such grouping of paragraphs. p (paragraph) marks paragraphs in prose.div (text division) contains a subdivision of the front, body, or back of a text.

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

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

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

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

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

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

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

The value of every xml:id attribute should be unique within a document. One simple way of ensuring that this is so is to make it reflect the hierarchic structure of the document. For example, Smith's 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 necessary 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:

As in the Bronte example above, the paragraphs making up a textual division are tagged with the <p> tag. In poetic or dramatic texts different tags are needed, to represent verse lines and stanzas in the first case, or individual speeches and stage directions in the second. : l (verse line) contains a single, possibly incomplete, line of verse.lg (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc.sp (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text.speaker contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment.stage (stage direction) contains any kind of stage direction within a dramatic text or fragment.

Here, for example, is the start of a poetic text in which verse lines and stanzas are tagged: I Sing the progresse of a deathlesse soule,Whom Fate, with God made, but doth not controule,Plac'd in most shapes; all times before the lawYoak'd us, and when, and since, in this I sing.And the great world to his aged evening;From infant morne, through manly noone I draw.What the gold Chaldee, of silver Persian saw,Greeke brass, or Roman iron, is in this one;A worke t'out weare Seths pillars, bricke and stone,And (holy writs excepted) made to yeeld to none,

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

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

Pull on your trousers.

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

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

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:

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

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

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

It is not always possible or desirable to interpret the reasons for such changes of rendering in a text. In such cases, the element <hi> may be used to mark a sequence of highlighted text without making any claim as to its status. hi (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made.

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

And this Indenture further witnesseth that the said Walter Shandy, merchant, in consideration of the said intended marriage ...

Alternatively, where the cause for the highlighting can be identified with confidence, a number of other, more specific, elements are available. emph (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect.foreign identifies a word or phrase as belonging to some language other than that of the surrounding text.gloss identifies a phrase or word used to provide a gloss or definition for some other word or phrase.label contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary.mentioned marks words or phrases mentioned, not used.term contains a single-word, multi-word, or symbolic designation which is regarded as a technical term.title contains a title for any kind of work.

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

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

On the one hand the is associated with the new rise of romance of twelfth-century France, the romans d'antiquité, the romances of Chrétien de Troyes, ...

Like changes of typeface, quotation marks are conventionally used to denote several different features within a text, of which the most frequent is quotation. When possible, we recommend that the underlying feature be tagged, rather than the simple fact that quotation marks appear in the text, using the following elements: q (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used.mentioned marks words or phrases mentioned, not used.soCalled contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics.gloss identifies a phrase or word used to provide a gloss or definition for some other word or phrase.

Here is a simple example of a quotation:

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

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

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

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

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

John has real savoir-faire.

Have you read ?

Savoir-faire is French for know-how.

The court issued a writ of mandamus.

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

The codes used to identify languages, supplied on the xml:lang attribute, must be constructed in a particular way, and must conform to common Internet standardsThe relevant standard is (). 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 ., as further explained in the relevant section of the TEI Guidelines. Some simple example codes for a few languages are given here: zhChinesegrcAncient GreekenEnglishelGreekenmMiddle EnglishjaJapanesefrFrenchlaLatindeGermansaSanskrit

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

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

The following two forms, for example, are logically equivalent : See especially section 12 on page 34. See especially . The value of the target attribute on either element may be the identifier of some other element within the current document. The passage or phrase being pointed at must bear an identifier, and must therefore be tagged as an element of some kind. In the following example, the cross reference is to a <div> element: ... see especially . ...

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 the paragraph on links ...

Links may be made to any kind of element ...

Sometimes the target of a cross reference does not correspond with any particular feature of a text, and so may not be tagged as an element of some kind. If the desired target is simply a point in the current document, the easiest way to mark it is by introducing an <anchor/> element at the appropriate spot. If the target is some sequence of words not otherwise tagged, the <seg> element may be introduced to mark them. These two elements are described as follows: anchor/ (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element.seg (arbitrary segment) represents any segmentation of text below the chunk level.

In the following (imaginary) example, <ref> elements have been used to represent points in this text which are to be linked in some way to other parts of it; in the first case to a point, and in the second, to a sequence of words: Returning to the point where I dozed off, I noticed that three words 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: .... .... .... ... ...

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

So far, we have shown how the elements <ptr/> and <ref> may be used for cross-references or links whose targets occur within the same document as their source. However, the same elements may also be used to refer to elements in any other XML document or resource, such as a document on the web, or a database component. This is possible because the value of the target attribute may be any valid universal resource indicator (URI)A full definition of this term, defined by the W3C (the consortium which manages the development and maintenance of the World Wide Web), is beyond the scope of this tutorial: however, the most frequently encountered version of a URI is the familiar URL used to indicate a web page, such as http://www.tei-c.org/index.xml.

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

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

The following special purpose linking attributes are defined for every element in the TEI Lite scheme: analinks an element with its interpretation.corresplinks an element with one or more other corresponding elements.nextlinks an element to the next element in an aggregate.prevlinks 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 . For example, a linguistic analysis of the sentence John loves Nancy might be encoded as follows: JohnlovesNancy 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 Jean aime NancyJohn loves Nancy

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:

, which made its Friday night debut only a month ago, was not listed on NBC's new schedule, although the network says the show still is being considered.

The next and prev attributes provide a simple way of linking together the components of a discontinuous element, as in the following example: Who-e debel you? — he at last said — you no speak-e, damme, I kill-e. And so saying, the lighted tomahawk began flourishing about me in the dark.

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

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

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

A modern editor might wish to make a number of interventions here, specifically to modernize (or normalise) the Elizabethan spellings of a' and feelds for he and fields respectively. He or she might also want to emend table to babbl'd, following an editorial tradition that goes back to the 18th century Shakespearian scholar Lewis Theobald. The following encoding would then be appropriate: ... for his nose was as sharp as a pen and 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 sharp as a pen and atable of green feelds

Finally, a modern digital editor may decide to combine both possibilities in a single composite text, using the <choice> element. choice groups a number of alternative encodings for the same point in a text. This allows an editor to mark where alternative readings are possible: ... for his nose was as sharp as a pen and ahebabbl'dtable of green feeldsfields

In addition to correcting or normalizing words and phrases, editors and transcribers may also supply missing material, omit material, or transcribe material deleted or crossed out in the source. In addition, some material may be particularly hard to transcribe because it is hard to make out on the page. The following elements may be used to record such phenomena: add (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector.gap indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.del (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector.unclear contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source.

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

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

These elements are also used to record authorial changes in manuscripts. A manuscript in which the author has first written How it galls me, what a galling shadow, then crossed out the word galls and inserted dogs might be encoded thus: How it gallsdogs me, what a galling shadow Again, the code #DHL points to another location where more information about the hand concerned is to be foundThe full TEI provides a range of elements for encoding metadata about manuscript production and description, which are not however included in TEI Lite.

Similarly, the <unclear> and <gap> elements may be used together to indicate the omission of illegible material; the following example also shows the use of <add> for a conjectural emendation: One hundred & twenty good regulars joined to me & instantly, would aid me signally in? an enterprise against Wilmington.

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

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

Other corpora (particular those constructed before the widespread use of scanners) 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

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

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

The <abbr> element is useful as a means of distinguishing semi-lexical items such as acronyms or jargon: We can sum up the above discussion as follows: the identity of a CC is defined by that calibration of values which motivates the elements of its GSP; 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

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

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

A referring string is a phrase which refers to some person, place, object, etc. Two elements are provided to mark such strings: rs (referencing string) contains a general purpose name or referring string.name (name, proper noun) contains a proper noun or noun phrase.

The type attribute is used to distinguish amongst (for example) names of persons, places and organizations, where this is possible: 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 any reference to a person, place, etc, not necessarily one in the form of a proper noun or noun phrase. My dear Mr. Bennet, said his lady to him one day...

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

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

The key attribute provides an alternative normalized identifier for the object being named, like a database record key. It may thus be useful as a means of gathering together all references to the same individual or location scattered throughout a document: My dear Mr. Bennet, said his lady to him one day, have you heard that Netherfield Park is let at last?

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 <index> element discussed in may be more appropriate if the function of the regularization is to provide a consistent index:

Montaillou is not a large parish. At the time of the events which led to Fournier's Benedict XII, Pope of Avignon (Jacques Fournier) investigations, the local population consisted of between 200 and 250 inhabitants.

Tags for the more detailed encoding of times and dates include the following: date contains a date in any format.time contains a phrase defining a time of day in any format.

These elements have a number of attributes which can be used to provide normalised versions of their values. att.datable provides attributes for normalization of elements that contain dates, times, or datable events.calendarindicates the system or calendar to which the date represented by the content of this element belongs.periodsupplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred.when [att.datable.w3c]supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd. The when attribute specifies a normalized form for the date or time, using one of the standard formats defined by ISO 8601. Partial dates or times (e.g. 1990, September 1990, twelvish) can be expressed by omitting a part of the value supplied, as in the following examples: 21 Feb 19801990September 1990SeptemberSept 11th, 12 minutes before 9 amNote in the last example the use of a normalized representation for the date string which includes a time: this example could thus equally well be tagged using the <time> element.

Given on the 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

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

For example: xxxiiitwenty-oneten percent10%5th

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.pc (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark.

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

In this example, each word has been decorated with an automatically generated part of speech code, using the ana attribute discussed in section above. The <w> also provides for each word to be associated with a root form or lemma, either explicitly using the lemma attribute, or by reference, using the lemmaRef attribute, as in this example: ...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 identifies some phrase-level portion of text to which the encoder may assign a user-specified type, as well as a unique identifier; it may thus be used to tag textual features for which there is no other provision in the published TEI Guidelines.

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

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

Neither restriction applies to the <interp> element, which provides powerful features for the encoding of quite complex interpretive information in a relatively straightforward manner. interp (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text.interpGrp (interpretation group) collects together a set of related interpretations which share responsibility or type. These elements allow the encoder to specify both the class of an interpretation, and the particular instance of that class which the interpretation involves. Thus, whereas with <seg> one can say simply that something is an apostrophe, with <interp> one can say that it is an instance (apostrophe) of a larger class (rhetorical figures).

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

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

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

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

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

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

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

The following elements may be used to mark particular features of technical documents: eg (example) contains any kind of illustrative example.code contains literal code from some formal language such as a programming language.ident (identifier) contains an identifier or name for an object of some kind in a formal language. <ident> is used for tokens such as variable names, class names, type names, function names etc. in formal programming languages.gi (element name) contains the name (generic identifier) of an element.att (attribute) contains the name of an attribute appearing within running text.formula contains a mathematical or other formula.val (value) contains a single attribute value.

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

It is traditional to introduce a language with a program like the following: CHAR*12 GRTG GRTG = 'HELLO WORLD' PRINT *, GRTG END

This simple example first declares a variable GRTG, in the line CHAR*12 GRTG, which identifies GRTG as consisting of 12 bytes of type CHAR. To this variable, the value HELLO WORLD is then assigned.

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

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

A particular problem arises when XML encoding is the subject of discussion within a technical document, itself encoded in XML. In such a document, it is clearly essential to distinguish clearly the markup occurring within examples from that marking up the document itself, and end-tags are highly likely to occur. One simple solution is to use the predefined entity reference < to represent each < character which marks the start of an XML tag within the examples. A more general solution is to mark off the whole body of each example as containing data which is not to be scanned for XML mark-up by the parser. This is achieved by enclosing it within a special XML construct called a CDATA marked section, as in the following example: <p>A list should be encoded as follows: <eg><![ CDATA [ <list> <item>First item in the list</item> <item>Second item</item> </list> ]]> </eg> The <gi>list</gi> element consists of a series of <gi>item</gi> elements.

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

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

Most modern document production systems have the ability to generate automatically whole sections such as a table of contents or an index. The TEI Lite scheme provides an element to mark the location at which such a generated section should be placed. divGen (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear.

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

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

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

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

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

For example, the second paragraph of this section might include the following:... TEI lite also provides a special purpose index tag indexingindex (tag)use in index generation which may be used ...

The <index> element can also be used to provide a form of interpretive or analytic information. For example, in a study of Ovid, it might be desired to record all the poet's references to different figures, for comparative stylistic study. In the following lines of the , such a study would record the poet's references to Jupiter (as deus, se, and as the subject of confiteor [in inflectional form number 227]), to Jupiter-in-the-guise-of-a-bull (as imago tauri fallacis and the subject of teneo), and so on.The analysis is taken, with permission, from Willard McCarty and Burton Wright, (Princeton: Princeton University Press, forthcoming). Some simplifications have been undertaken. iamque deus posita fallacis imagine taurise confessus erat Dictaeaque rura tenebat This need might be met using the <note> element discussed in section in , or with the <interp> element discussed in section . Here we demonstrate how it might also be satisfied by using the <index> element.

We assume that the object is to generate more than one index: one for names of deities (called dn), another for onomastic references (called on), a third for pronominal references (called pr) and so forth. One way of achieving this might be as follows: iamque deus posita fallacis imagine tauri IuppiterdeusIuppiter (taurus)imago tauri fallacisse confessus erat Dictaeaque rura tenebat IuppiterseIuppiterconfiteor (v227) For each <index> element above, an entry will be generated in the appropriate index, using as headword the content of the <term> element it contains; the <term> elements nested within the secondary <index> element in each case provide a secondary keyword. The actual reference will be taken from the context in which the <index> element appears, i.e. in this case the identifier of the <l> element containing it.

The <address> element is used to mark a postal address of any kind. It contains one or more <addrLine> elements, one for each line of the address. address contains a postal address, for example of a publisher, an organization, or an individual.addrLine (address line) contains one line of a postal address.

Here is a simple example:

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

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

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

A minimal header has the following structure:

The <encodingDesc> element specifies the methods and editorial principles which governed the transcription of the text. Its use is highly recommended. It may be prose description or may contain elements from the following list: projectDesc (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected.samplingDecl (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection.editorialDecl (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text.refsDecl (references declaration) specifies how canonical references are constructed for this text.classDecl (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text.

The <profileDesc> element enables information characterizing various descriptive aspects of a text to be recorded within a single framework. It has three optional components: creation contains information about the creation of a text.langUsage (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text.textClass (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc.

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

Example: August 1992Taos, New Mexico

The <langUsage> element is useful where a text contains many different languages. It may contain <language> elements to document each particular language used: language characterizes a single language or sublanguage used within a text. For example, a text containing predominantly text in French as spoken in Quebec, but also smaller amounts of British and Canadian English might be documented as follows: 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 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 a list of keywords or phrases identifying the topic or nature of a text. As usual, the attribute scheme identifies the source from which these terms are taken. For example, if the LC Subject Headings are used, following declaration of that classification system in a <taxonomy> element as above : English literature -- History and criticism -- Data processing.English literature -- History and criticism -- Theory etc.English language -- Style -- Data processing.

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

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

Example: File format updatedStuart's corrections entered

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.