| Previous | Up | Next |
This chapter describes the default high level structure for all TEI documents. The majority of the different base tag sets described in part II simply embed the framework defined in this chapter while a few redefine it with some minor modifications. This chapter is therefore relevant to every kind of TEI document. For further details on the overall structure of the TEI document type definitions, in particular the use of base and additional tag sets, see chapter 3 .
TEI texts may be regarded either as unitary, that is, forming an organic whole, or as composite, that is, consisting of several components which are in some important sense independent of each other. The distinction is not always entirely obvious: for example a collection of essays might be regarded as a single item in some circumstances, or as a number of distinct items in others. In such borderline cases, the encoder must choose whether to treat the text as unitary or composite; each may have advantages and disadvantages in a given situation.
Whether unitary or composite, the text is marked with the <text> tag and may contain front matter, a text body, and back matter. In unitary texts, the text body is tagged <body> ; in composite texts, where the text body consists of a series of subordinate texts or groups, it is tagged <group> . The overall structure of any text, unitary or composite, is thus defined by the following elements:
The overall structure of a unitary text is:
<TEI.2>
<TeiHeader> ... </TeiHeader>
<text>
<front>
<!-- front matter of copy text goes here. -->
</front>
<body>
<!-- body of text goes here. -->
</body>
<back>
<!-- back matter of text, if any, here. -->
</back>
</text>
</TEI.2>
The overall structure of a composite text made up of two unitary texts is:
<TEI.2>
<TeiHeader> ... </TeiHeader>
<text>
<front>
<!-- front matter of composite text goes here. -->
</front>
<group>
<text>
<front>
<!-- front matter of first unitary text, if any -->
</front>
<body>
<!-- body of first unitary text -->
</body>
<back>
<!-- back matter of first unitary text, if any -->
</back>
</text>
<text>
<body>
<!-- body of second unitary text -->
</body>
</text>
</group>
<back>
<!-- back matter of composite text, if any -->
</back>
</text>
</TEI.2>
Each of these elements is further described in the following subsections. <text> , <body> and <group> are formally declared as follows:
<!-- 7: Top-level parts of default structure -->
<!ELEMENT text - - (front?, (body | group), back?)
+(%m.globincl;)
>
<!ATTLIST text %a.global;
%a.declaring; >
<!ELEMENT body - O ((%m.divtop;)*, ( ( divGen*, (
(div, (div | divGen)*) | (div0,
(div0 | divGen)*) | (div1, (div1 |
divGen)*) ) ) | ( (%component)+,
(divGen*, ( (div, (div | divGen)*)
| (div0, (div0 | divGen)*) |
(div1, (div1 | divGen)*) )? ))),
(%m.divbot;)*) >
<!ATTLIST body %a.global;
%a.declaring; >
<!ELEMENT group - O ((%m.divtop;)*, (text | group)+,
(%m.divbot;)*) >
<!ATTLIST group %a.global;
%a.declaring; >
<!-- This fragment is used in sec. 7.7 -->
Elements <front> and <back> are declared separately, as
further discussed in sections 7.4 and 7.6 . Textual elements, such as paragraphs, lists or phrases,
which nest within these major structural elements, are discussed in
chapter 6 (for elements common to all kinds of document)
and in part II (for elements specific to a particular base). The
<group> element, used for composite texts, is further discussed
in section 7.3 .
In some texts, the body consists simply of a sequence of low-level structural items, referred to here as components or component-level elements (see section 3.7 ). Examples in prose texts include paragraphs or lists; in dramatic texts, speeches and stage directions; in dictionaries, dictionary entries. In other cases sequences of such elements will be grouped together hierarchically into textual divisions and subdivisions, such as chapters or sections. The names used for these structural subdivisions of texts vary with the genre and period of the text, or even with the whim of the author, editor or publisher. For example, a major subdivision of an epic or of the Bible is generally called a ``book'', that of a report is usually called a ``part'' or ``section'', that of a novel a ``chapter'' --- unless it is an epistolary novel, in which case it may be called a ``letter''. Even texts which are not organized as linear prose narratives, or not as narratives at all, will frequently be subdivided in a similar way: a drama into ``acts'' and ``scenes''; a reference book into ``sections''; a diary or day book into ``entries''; a newspaper into ``issues'' and ``sections'', and so forth.
To cater for this variety, these Guidelines propose that all such textual divisions be regarded as occurrences of the same neutrally named elements, with an attribute type used to categorize elements independently of their hierarchic level. Two alternative styles are provided for the marking of these neutral divisions: numbered and un-numbered. Numbered divisions are named <div0> , <div1> , <div2> , etc., where the number indicates the depth of this particular division within the hierarchy, the largest such division being ``div0'', any subdivision within it being ``div1'', any further sub-sub-division being ``div2'' and so on. Un-numbered divisions are simply named <div> , and allowed to nest recursively to indicate their hierarchic depth. The two styles may not be combined within a single <front> , <body> or <back> element.
The following element is used to identify textual subdivisions in the un-numbered style:
Using this style, the body of a text containing two parts, each composed of two chapters, might be represented as follows:
<body>
<div type='part' n='1'>
<div type='chapter' n='1'>
<!-- text of part 1, chapter 1 -->
</div>
<div n='2'>
<!-- text of part 1, chapter 2-->
</div>
</div>
<div type='part' n='2'>
<div n='1' type='chapter'>
<!-- text of part 2, chapter 1 -->
</div>
<div n='2'>
<!-- text of part 2, chapter 2 -->
</div>
</div>
</body>
Note that end-tags are mandatory for un-numbered divisions, to avoid ambiguity. Note also that the type attribute must be specified each time its value changes, for reasons discussed in section 7.1.3 below.
The <div> element has the following formal definition:
<!-- 7.1.1: Un-numbered divisions -->
<!ELEMENT div - O ((%m.divtop;)*, ((div | divGen)+ |
((%component;)+, (div |
divGen)*)), (%m.divbot;)*) >
<!ATTLIST div %a.global;
%a.declaring;
%a.divn; >
<!-- This fragment is used in sec. 7.7 -->
The following elements are used to identify textual subdivisions in the numbered style:
The largest possible subdivision of the body may be regarded either as a <div0> or as a <div1> element, [ see note 53 ] and the smallest possible <div7> . If numbered divisions are in use, a division at any one level (say, <div3> ), may contain only numbered divisions at the next lowest level (in this case, <div4> ).
Using this style, the body of a text containing two parts, each composed of two chapters, might be represented as follows:
<body>
</div1>
<div1 type='Chapter' n='1'>
<!-- text of part 1, chapter 1 -->
<div1 n='2'>
<!-- text of part 1, chapter 2-->
</div1>
<div1 n='1'>
<!-- text of part 2, chapter 1 -->
<div1 n='2'>
<!-- text of part 2, chapter 2 -->
</body>
Formal definitions for these elements are as follows:
<!-- 7.1.2: Numbered divisions -->
<!ELEMENT div0 - O ((%m.divtop;)*, ( (div1 | divGen)+
| ( (%component;)+, (div1 |
divGen)*)), (%m.divbot;)*) >
<!ATTLIST div0 %a.global;
%a.declaring;
%a.divn; >
<!ELEMENT div1 - O ((%m.divtop;)*, ( (div2 | divGen)+
| ((%component;)+, (div2 |
divGen)*)), (%m.divbot;)*) >
<!ATTLIST div1 %a.global;
%a.declaring;
%a.divn; >
<!ELEMENT div2 - O ((%m.divtop;)*, ( (div3 | divGen)+
| ((%component;)+, (div3 |
divGen)*)), (%m.divbot;)*) >
<!ATTLIST div2 %a.global;
%a.declaring;
%a.divn; >
<!ELEMENT div3 - O ((%m.divtop;)*, ( (div4 | divGen)+
| ((%component;)+, (div4 |
divGen)*)), (%m.divbot;)*) >
<!ATTLIST div3 %a.global;
%a.declaring;
%a.divn; >
<!ELEMENT div4 - O ((%m.divtop;)*, ( (div5 | divGen)+
| ((%component;)+, (div5 |
divGen)*)), (%m.divbot;)*) >
<!ATTLIST div4 %a.global;
%a.declaring;
%a.divn; >
<!ELEMENT div5 - O ((%m.divtop;)*, ( (div6 | divGen)+
| ((%component;)+, (div6 |
divGen)*)), (%m.divbot;)*) >
<!ATTLIST div5 %a.global;
%a.declaring;
%a.divn; >
<!ELEMENT div6 - O ((%m.divtop;)*, ((div7 | divGen)+
| ((%component;)+, (div7 |
divGen)*)), (%m.divbot;)*) >
<!ATTLIST div6 %a.global;
%a.declaring;
%a.divn; >
<!ELEMENT div7 - O ((%m.divtop;)*, (%component;)+,
(%m.divbot;)*) >
<!ATTLIST div7 %a.global;
%a.declaring;
%a.divn; >
<!-- This fragment is used in sec. 7.7 -->
Within the same <front> , <body> or <back> element, all hierarchic subdivisions must be marked either using nested <div> elements, or using the <div0> , <div1> , <div2> tag appropriate at each level; the two styles may not be mixed.
The choice between numbered and un-numbered divisions will depend to some extent on the complexity of the material: un-numbered divisions allow for an arbitrary depth of nesting, while numbered divisions limit the depth of the tree which can be constructed. Where divisions at different levels should be processed differently (chapters, but not sections, for example, beginning on new pages), numbered divisions slightly simplify the task of defining the desired processing for each level. Some software may find numbered divisions easier to process, as there is no need to maintain knowledge of the whole document structure in order to know the level at which a division occurs; such software may however find it difficult to cope with some other aspects of the TEI scheme. On the other hand, in a collection of many works it may prove difficult or impossible to ensure that the same numbered division always corresponds with the same type of textual feature: a ``chapter'' may be at level 1 in one work and level 3 in another.
Whichever style is used, the global n and id attributes (section 3.5 ) may be used to provide reference strings or labels for each division of a text, where appropriate. Such labels should be provided for each section which is regarded as significant for referencing purposes (on reference systems, see further section 6.9 ).
As indicated above, the type attribute is used to provide a name or description for the division. Typical values might be ``book'', ``chapter'', ``section'', ``part'', or (for verse texts) ``book'', ``canto'', ``stanza'', or (for dramatic texts) ``act'', ``scene''. This attribute has a declared value of #CURRENT , which implies that if defaulted, the value used will be that most recently specified on any element of the same kind, scanning the text left to right. Hence, if un-numbered divisions are used, the appropriate value must be specified each time a change of level occurs, both ``down'' and ``up'' the document hierarchy.
The following extended example uses numbered divisions to indicate the structure of a novel, and illustrates the use of the attributes discussed above. It also uses some elements discussed in section 7.2 and the <p> element discussed in section 6.1 .
<div0 type='book' n='I' id=JA0100>
<head>Book I.</head>
<div1 type='chapter' n='1' id=JA0101>
<head>Of writing lives in general, and particularly of
Pamela, with a word by the bye of Colley
Cibber and others.</head>
<p>It is a trite but true observation, that examples work
more forcibly on the mind than precepts: ...
<!-- remainder of chapter 1 here -->
<div1 n='2' id=JA0102>
<head>Of Mr. Joseph Andrews, his birth, parentage,
education, and great endowments; with a word
or two concerning ancestors.</head>
<p>Mr. Joseph Andrews, the hero of our ensuing history,
was esteemed to be the only son of Gaffar and
Gammar Andrews, and brother to the illustrious
Pamela, whose virtue is at present so famous ...
<!-- remainder of chapter 2 here -->
<!-- remaining chapters of Book 1 here -->
<trailer>The end of the first Book
<div0 n='II' id=JA0100>
<head>Book II</head>
<div1 n='1' id=JA0201>
<head>Of divisions in authors</head>
<p>There are certain mysteries or secrets in all
trades, from the highest to the lowest, from
that of <term>prime-ministering</term>, to
this of <term>authoring</term>, which are
seldom discovered unless to members of
the same calling ...
<p>I will dismiss this chapter with the following
observation: that it becomes an author generally to
divide a book, as it does a butcher to joint his meat,
for such assistance is of great help to both the reader
and the carver. And now having indulged myself a little
I will endeavour to indulge the curiosity of my reader,
who is no doubt impatient to know what he will find
in the subsequent chapters of this book.
<div1 n='2' id=JA0202>
<head>A surprising instance of Mr. Adams's short memory, with
the unfortunate consequences which it brought on Joseph.
</head>
<p>Mr. Adams and Joseph were now ready to depart different
ways ...
In most situations, the textual subdivisions marked by <div> elements will be both complete and identically organized with reference to the original source. For some purposes however, in particular where dealing with unusually large or unusually small texts, encoders may find it convenient to present as textual divisions sequences of text which are incomplete with reference to the original text, or which are in fact an ad hoc agglomeration of tiny texts. Moreover, in some kinds of texts it is difficult or impossible to determine the order in which individual subdivisions should be combined to form the next higher level of subdivision, as noted below.
To overcome these problems, the following additional attributes are defined for all elements in the divn class:
For example, an encoder might choose to transcribe only the first two thousand words of each chapter from a novel. In such a case, each chapter might conveniently be regarded as a partial division, and tagged with a <div> element in the following form:
<div n='xx' sample=initial part=Y type=chapter> <p><!-- ... --> </div>where ``xx'' represents a number for the chapter. The <sampling> element in the TEI Header should also be used to record the principles underlying the selection of incomplete samples, as further described in section 5.3.2 .
The following example demonstrates how a newspaper column composed of very short unrelated snippets may be encoded using these attributes:
<div1 type=storylist org=composite> <head>News in brief</head> <div2 type=story> <head>Police deny <soCalled>losing</soCalled> bomb</head> <p>Scotland Yard yesterday denied claims in the Sunday Express that anti-terrorist officers trailing an IRA van loaded with explosives in north London had lost track of it 10 days ago. </div2> <div2 type=story> <head>Hotel blaze</head> <p>Nearly 200 guests were evacuated before dawn yesterday after fire broke out at the Scandic Crown hotel in the Royal Mile, Edinburgh. </div2> <div2 type=story> <head>Test match split</head> <p>Test Match Special next summer will be split between Radio 5 and Radio 3, after protests this year that it disrupted Radio 3's music schedule. </div2> <!-- other stories here --> </div1>
The org attribute on the <div1> element is used here to indicate that individual stories in this group, marked here as <div2> , are really quite independent of each other, although they are all marked as subdivisions of the whole group. They can be read in any order without affecting the sense of the piece; indeed, in some cases, divisions of this nature are printed in such a way as to make it impossible to determine the order in which they are intended to be read. Individual stories can be added or removed without affecting the existing components.
This method of encoding composite texts as composite divisions has some limitations compared with the more general and powerful mechanisms discussed in section 7.3 . However, it may be preferable in some circumstances, notably where the individual texts are very small.
The divisions of any kind of text may sometimes begin with a brief heading or descriptive title, with or without a byline, an epigraph or brief quotation, or a salutation such as one finds at the start of a letter. They may also conclude with a brief trailer, byline, or signature. Elements which may appear in this way, either at the start or at the end of a text division proper, are regarded as forming a class, known as divtop or divbot respectively.
The following special-purpose elements are provided to mark features which may appear only at the start of a division:
The following special-purpose elements are provided to mark features which may appear only at the end of a division:
The <head> element is used to identify a heading prefixed to the start of any textual division, at any level. A given division may of course contain more than one such element, as in the following example:
<div1 n='Etym'> <head>Etymology</head> <head>(Supplied by a late consumptive usher to a grammar school)</head> <p>The pale Usher — threadbare in coat, heart, body and brain; I see him now. He was ever dusting his old lexicons and grammars....
Unlike some other markup schemes, the TEI scheme does not require that headings attached to textual subdivisions at different hierarchic levels have different identifiers. All kinds of heading are marked identically using the <head> tag; the type or level of heading intended is implied by the immediate parent of the <head> element, which may for example be a <div1> , <div2> , etc., an un-numbered <div> , or a <list> .
In certain kinds of text (notably newspapers), there may be a need to categorize individual headings within the sequence at the start of a division, for example as ``main'' headings, or ``detail'' headings. Specific elements are provided for certain kinds of heading-like features, (notably <byline> , <dateline> and <salute> ; see further section 7.2.2 ), but the type attribute must be used to discriminate among other forms of heading.
In the following example, taken from a British newspaper, the lead story and its associated headlines have been encoded as a <div> element, with appropriate divtop elements attached:
<div type=story> <head rend='large underlined' type=sub> President pledges safeguards for 2,400 British troops in Bosnia</head> <head rend='very large bold' type=main> Major agrees to enforced no-fly zone </head> <byline>By George Jones, Political Editor, in Washington </byline> <p>Greater Western intervention in the conflict in former Yugoslavia was pledged by President Bush yesterday....
In older writings, the headings or incipits may be longer than in modern works. When heading-like material appears in the middle of a text, the encoder must decide whether or not to treat it as the start of a new division. If the phrase in question appears to be more closely connected with what follows than with what precedes it, then it may be regarded as a heading and tagged as the <head> of a new <div> element. If it appears to be simply inserted or superimposed --- as for example the kind of `pull quotes' often found in newspapers or magazines, then the <quote> , <q> , or <cit> element may be more appropriate.
The <trailer> element, which can appear at the end of a division only, is used to mark any heading-like feature appearing in this position, as in this example:
<div1 type=book n='I'><head>In the name of Christ here begins
the first book of the ecclesiastical history of Georgius
Florentinus, known as Gregory, Bishop of Tours.</head>
<div2><head>Chapter-Headings</head>
<list>
<!-- list of chapter heads omitted ... -->
</list>
<div2><head>In the name of Christ here begins Book I of the
history.</head>
<p>Proposing as I do ...
<p>From the Passion of our Lord until the death of Saint Martin
four hundred and twelve years passed.
<trailer>Here ends the first Book, which covers five thousand,
five hundred and ninety-six years from the beginning of the
world down to the death of Saint Martin.</trailer>
</div2>
</div1>
In addition to headings of various kinds, divisions sometimes include more or less formulaic opening or closing passages, typically conveying such information as the name and address of the person to whom the division is addressed, the place or time of its production, a salutation or exhortation to the reader, and so on. Divisions in epistolary form are particularly liable to include such features. Additional elements for the detailed encoding of personal names, dates and places are provided in chapter 20 . For simple cases, the following elements should be adequate:
The <byline> and <dateline> elements are used to encode headings which identify the authorship and provenance of a division. Although the terminology derives from newspaper usage, there is no implication that <dateline> or <byline> elements apply only to newspaper texts. The following example illustrates use of the <dateline> and <signed> elements at the end of the preface to a novel:
<div type=preface> <head>To Henry Hope.</head> <p>It is not because this volume was conceived and partly executed amid the glades and galleries of the Deepdene, that I have inscribed it with your name.... I shall find a reflex to their efforts in your own generous spirit and enlightened mind. </p> <closer> <signed lang=el>D.</signed> <dateline>Grosvenor Gate, May-Day, 1844</dateline> </closer> </div>
Where a sequence of such elements appear together, either at the beginning or end of an element, it may be convenient to group them together using one of the following elements:
<div type=narrative n='6'>
<head>Sixth Narrative</head>
<head>contributed by Sergeant Cuff</head>
<div type=fragment n='6.1'>
<opener>
<dateline><name type=place>Dorking, Surrey,</name>
<date>July 30th, 1849</date>
</dateline>
<salute>To <name>Franklin Blake, Esq.</name> Sir, —
</salute>
</opener>
<p>I beg to apologize for the delay that has occurred
in the production of the Report, with which I engaged
to furnish you. I have waited to make it a complete
Report ...
<!-- .... -->
<closer>
<salute>I have the honour to remain, dear sir, your
obedient servant </salute>
<signed> <name>RICHARD CUFF</name> (late sergeant in the
Detective Force, Scotland Yard, London).
</signed>
</closer>
</div>
<div type=letter n='14'> <head>Letter XIV: Miss Clarissa Harlowe to Miss Howe</head> <opener> <dateline>Thursday evening, March 2.</dateline> </opener> <p>On Hannah's depositing my long letter ... <p>An interruption obliges me to conclude myself in some hurry, as well as fright, what I must ever be, <closer> <salute>Yours more than my own,</salute> <signed>Clarissa Harlowe</signed> </closer> </div>
For further discussion of the encoding of names of persons and places and of dates, see section 6.4.4 and chapter 20 .
The <argument> element may be used to encode the prefatory list of topics sometimes found at the start of a chapter or other division. It is most conveniently encoded as a list, since this allows each item to be distinguished, but may also simply be presented as a paragraph. The following are thus both equally valid ways of encoding the same argument:
<div type=chap n='6'> <argument> <p>Kingston — Instructive remarks on early English history — Instructive observations on carved oak and life in general — Sad case of Stivvings, junior — Musings on antiquity — I forget that I am steering — Interesting result — Hampton Court Maze — Harris as a guide. </argument> <p> It was a glorious morning, late spring or early summer, as you care to take it... </div>
<div type=chap n='6'> <argument> <list type='inline'> <item>Kingston <item>Instructive remarks on early English history <item>Instructive observations on carved oak and life in general <item>Sad case of Stivvings, junior <item>Musings on antiquity <item>I forget that I am steering <item>Interesting result <item>Hampton Court Maze <item>Harris as a guide. </list> </argument> <p> It was a glorious morning, late spring or early summer, as you care to take it... </div>
An epigraph is a quotation from some other work appearing on a title page, or at the start of a division. It may be encoded using the special-purpose <epigraph> element. Its content will generally be a <q> or <quote> element, often associated with a bibliographic reference, as in the following example:
<div n='19'><head>Chapter 19</head>
<epigraph>
<cit><quote>I pity the man who can travel
from Dan to Beersheba, and say <q>'Tis all
barren;</q> and so is all the world to him
who will not cultivate the fruits it offers.
</quote>
<bibl>Sterne: Sentimental Journey.</bibl>
</cit></epigraph>
<p>To say that Deronda was romantic would be to
misrepresent him: but under his calm and somewhat
self-repressed exterior ...
For discussion of quotations appearing other than as epigraphs refer to section 6.3.3 .
Other than its initial sequence of divtop elements, and its closing sequence of divbot elements, every textual division (numbered or un-numbered) consists of a sequence of ungrouped component elements (see 3.7 ). The actual elements available will depend on the base tag set in use; in all cases, at least the component-level structural elements defined in the core will be available (paragraphs, lists, dramatic speeches, verse lines and line groups etc.). If the drama base has been selected, then additionally the low level dramatic structural elements (speeches or stage directions, as defined in chapter 10 ) will be available. If the dictionary base is in use, then dictionary entries, related entries, etc. (as defined in chapter 12 ) will also be available; if the tag set for transcribed speech is in use, then utterances, pauses, vocals, kinesics, etc., as defined in chapter 11.2 will be available; and so on.
Where a text contains low level elements from more than one base, two options are available. The first option, selected by the `mixed' base, allows for low level structural elements from any or all of the selected bases to appear at any point. The second option, selected by the `general' base, allows for low level structural elements from different bases to appear in different textual divisions of the same text, but requires that any one division use elements from only one base. For further information, refer to section 3.4 .
The elements discussed in this section are formally defined as follows:
<!-- 7.2.4: Tags for start and end of divisions -->
<!ELEMENT trailer - O (%phrase.seq;) >
<!ATTLIST trailer %a.global; >
<!ELEMENT byline - O (%phrase.seq; | docAuthor)* >
<!ATTLIST byline %a.global; >
<!ELEMENT dateline - O (#PCDATA | date | time | name |
address)* >
<!ATTLIST dateline %a.global; >
<!ELEMENT argument - - (head?, %component.seq;) >
<!ATTLIST argument %a.global; >
<!ELEMENT epigraph - - (%component.seq;) >
<!ATTLIST epigraph %a.global; >
<!ELEMENT opener - O (argument | byline | dateline |
epigraph | salute | signed |
%phrase.seq;)* >
<!ATTLIST opener %a.global; >
<!ELEMENT closer - O (signed | dateline | salute |
%phrase.seq;)* >
<!ATTLIST closer %a.global; >
<!ELEMENT salute - O (%phrase.seq;) >
<!ATTLIST salute %a.global; >
<!ELEMENT signed - O (%phrase.seq;) >
<!ATTLIST signed %a.global; >
<!-- The HEAD element is declared in the core tag set. -->
<!-- This fragment is used in sec. 7.7 -->
The <group> element should be used to represent a collection of independent texts which is to be regarded as a single unit for processing or other purposes. Examples of such composite texts include anthologies and other collections. The presence of common front matter referring to the whole collection, possibly in addition to front matter relating to each individual text, is a good indication that a given text might usefully be encoded as a <group> , though encoders may choose to use this structure to represent other kinds of composite texts as well.
For example, the overall structure of a collection of short stories might be encoded as follows:
<TEI.2>
<TEIHeader>
<!-- header information for the whole collection -->
</TEIHeader>
<text>
<front>
<docTitle><titlePart>
The Adventures of Sherlock Holmes
</titlePart></docTitle>
<docImprint>First published in <title>The Strand</title>
between July 1891 and December 1892</docImprint>
<!-- Any other front matter specific
to the collection here ... -->
</front>
<group>
<text>
<front>
<head rend=italic>Adventures of Sherlock
Holmes</head>
<docTitle><titlePart>Adventure I. —</titlePart>
<titlePart>A Scandal in Bohemia</titlePart></docTitle>
<byline>By A. Conan Doyle.</byline>
</front>
<body>
<div1 n='I.1'>
<p>To Sherlock Holmes she is always
<emph>the</emph> woman.
<!-- ... -->
</body>
</text>
<text>
<front>
<head rend=italic>Adventures
of Sherlock Holmes</head>
<docTitle><titlePart>Adventure II. —</titlePart>
<titlePart>The Red-Headed League</titlePart></docTitle>
<byline>By A. Conan Doyle.</byline>
</front>
<body>
<p> <!-- text of The Red-Headed League here -->
</body>
</text>
<!-- more texts here -->
<text>
<front>
<head rend=italic>
Adventures of Sherlock Holmes</head>
<docTitle><titlePart>Adventure XII. —</titlePart>
<titlePart>The Adventure of the Copper Beeches</titlePart>
</docTitle>
<byline>By A. Conan Doyle.</byline>
</front>
<body>
<p><q>&odq;To the man who loves art for
its own sake,&cdq;</q> remarked Sherlock
Holmes ...
<!-- rest of the the Copper Beeches here -->
... she is now the head of a private school
at Walsall, where I believe that she has
met with considerable success.</p>
</body>
</text> <!-- end of the Copper Beeches -->
</group>
</text> <!-- end of the Adventures of Sherlock Holmes -->
</TEI.2>
A text which is a member of a group may itself contain groups. This is quite common in collections of verse, but may happen in any kind of text. As an example, consider the overall structure of a typical collection, such as the Muses Library edition of Crashaw's poetry (ed. J.R. Tutin, [ca. 1900]). Following a critical introduction and table of contents, this work contains the following major sections:
Each of the three collections published in Crashaw's lifetime has a reasonable claim to be considered as a text in its own right, and may therefore be encoded as such. It is rather more arbitrary as to whether the two posthumous collections should be treated as two groups, following the practice of the Muses Library edition. An encoder might elect to combine the two into a single group, or simply to treat each fragment as an ungrouped unitary text.
The Muses Library edition reprints the whole of each of the three original collections, including their original front matter (title pages, dedications etc.). These should be encoded using the <front> element and its constituents (on which see further section 7.4 ), while the body of each collection should be encoded as a single <group> element. Each individual poem within the collections should be encoded as a distinct <text> element. The beginning of the whole collection would thus appear as follows (for further discussion of the use of the elements <div> and <lg> for textual subdivision of verse, see section 6.11.1 and chapter 9 ):
<text>
<front>
<titlePage>
<docTitle><titlePart>The poems of Richard Crashaw</titlePart></docTitle>
<byline>Edited by J.R. Tutin</byline>
<!-- ... -->
</titlePage>
<div type=preface><head>Editor's Note</head>
<p>A few words are necessary...
<!-- ... -->
</div>
</front>
<group>
<text>
<front>
<titlepage>
<docTitle>
<titlePart>Steps to the Temple, Sacred Poems</titlePart>
</docTitle>
<!-- ... -->
</titlepage>
<div type=address><head>The Preface to the Reader
<p>Learned Reader, The Author's friend will not usurp
much upon thy eye...
</div>
</front>
<group>
<text>
<front><docTitle><titlePart>Sospetto D'Herode</titlePart></docTitle>
</front>
<body>
<div1 type=book n='Herod I'>
<head>Libro Primo</head>
<epigraph>
<l>Casting the times with their strong signs
<!-- ... -->
</epigraph>
<lg n='I.1' type=stanza>
<l>Muse! now the servant of soft loves no more
<l>Hate is thy theme and Herod whose unblest
<l>Hand (O, what dares not jealous greatness?) tore
<l>A thousand sweet babes from their mothers' breast,
<l>The blooms of martyrdom...
<!-- ... -->
</text> <!-- end of Sospetto D'Herode -->
<text>
<front><docTitle><titlePart>The Tear</titlePart></docTitle></front>
<body>
<lg n='I'>
<l>What bright soft thing is this
<l>Sweet Mary, thy fair eyes' expense?
<!-- ... -->
</text> <!-- end of The Tear -->
<!-- the remaining poems of the Steps to the Temple appear -->
<!-- here, each within its own <text> element -->
</group>
<back> <!-- back matter for Steps to the Temple here -->
</back>
</text>
<text> <!-- Carmen deo Nostro -->
<front> <!-- ... --> </front>
<group>
<text><!-- ... --> </text>
<text><!-- ... --> </text>
<!-- more texts here -->
</group>
</text>
<text> <!-- The delights of the Muses -->
<group>
<text><!-- ... --> </text>
<text><!-- ... --> </text>
<!-- more texts here -->
</group>
</text>
<!-- ... -->
</group>
<back>
<!-- back matter for the whole collection -->
</back>
</text>
The <group> element may be used in this way to encode any kind of collection of which the constituents are regarded by the encoder as texts in their own right. Examples include anthologies of verse or prose by multiple authors, collections, florilegia or commonplace books, journals, day books, etc. As a fairly typical example, we consider The Norton Book of Travel , an anthology edited by Paul Fussell and published in 1987 by W.W. Norton. This work comprises the following major sections:
The easiest way of encoding such an anthology is to treat each individual extract as a text in its own right. A sequence of texts by a single author, together with the biographical note preceding it, can then be treated as a single <group> element within the larger <group> formed by the section. The sequence of single or composite texts making up a single section of the work is likewise treated, together with its prefatory essay, as a single <group> within the work. Schematically:
<text> <!-- the whole anthology -->
<front>
<!-- title page, acknowledgments, introductory
essay for anthology -->
</front>
<group> <!-- 'body' of the anthology -->
<group><head>The Beginnings</head>
<!-- sequence of texts or groups -->
</group>
<group> <!-- The Eighteenth Century and the Grand Tour -->
<text> <!-- prefatory essay by editor --> </text>
<group><!-- Lady Mary Wortley Montagu -->
<text> <!-- biographical notice, by
editor --> </text>
<text> <!-- first letter --> </text>
<text> <!-- second letter --> </text>
<!-- ... -->
</group> <!-- end of Montagu section -->
<text> <!-- single text by Jonathan Swift -->
<front> <!-- biographical notice,
by editor --> </front>
<body> <!-- ... --> </body>
</text> <!-- end of Swift section -->
<group> <!-- Alexander Pope -->
<text> <!-- biographical notice, by
editor --> </text>
<text> <!-- first poem --> </text>
<text> <!-- second poem --> </text>
</group> <!-- end of Pope section -->
<!-- ... -->
</group> <!-- end of 18th Century Section -->
<group><head>The Heyday</head>
<!-- texts and subgroups ... -->
</group>
<!-- ... -->
</group> <!-- end of 'body' of anthology -->
<back> <!-- back matter for whole anthology -->
</back>
</text> <!-- end of the anthology -->
Note that the editor's introductory essays on each author may be treated as texts in their own right, (as the essays on Lady Mary Wortley Montagu and Alexander Pope have been treated above), or as front matter to the embedded text, as the essay on Swift has been. The treatment in the example is intentionally inconsistent, to allow comparison of the two approaches. Consistency can be imposed either by treating the Swift section as a <group> containing one text by Swift and one by the editor, or by treating the Montagu and Pope sections as <text> elements containing the editor's essays as front matter. Marked in the second way, the Pope section of the book would look like this:
<text><!-- Alexander Pope -->
<front>
<!-- biographical notice -->
</front>
<group>
<text> <!-- first poem --> </text>
<text> <!-- second poem --> </text>
<!-- ... -->
</group>
</text> <!-- end of Pope section -->
The essays on ``The Eighteenth Century and the Grand Tour'' and other larger sections could also be tagged as `front' matter in the same way, by treating the larger sections as <text> elements rather than <group> elements.
Where, as in this case, an anthology contains different kinds of text (for example, mixtures of prose and drama, or transcribed speech and dictionary entries, or letters and verse), the elements to be encoded may well need to be drawn from more than one of the base tag sets described in part II. In such a situation, either the mixed or the general base should be specified, as further described in section 3.4 . The elements provided by the core tag set described in chapter 6 should however prove adequate for most simple purposes, where prose, drama, and verse are combined in a single collection.
For anthologies of short extracts such as commonplace books, it may often be preferable to regard each extract not as a text in its own right but simply as a quotation or <cit> element. The following component-level elements may be used to encode quotations of this kind:
<div type=chap n='2'> <head>Extracts</head> <head>(Supplied by a sub-sub-Librarian)</head> <p>It will be seen that this mere painstaking burrower and grubworm of a poor devil of a Sub-Sub appears to have gone through the long Vaticans and street-stalls of the earth, picking up whatever random allusions to whales he could anyways find... Here ye strike but splintered hearts together ‐ there, ye shall strike unsplinterable glasses!</p> <p><cit> <quote>And God created great whales.</quote> <bibl>Genesis</bibl> </cit> <cit><quote><l> Leviathan maketh a path to shine after him; </l><l> One would think the deep to be hoary. </l></quote> <bibl>Job</bibl></cit> <!-- ... --> <cit> <quote>By art is created that great Leviathan, called a Commonwealth or State &dash (in Latin, <mentioned lang=LAT>civitas</mentioned>), which is but an artificial man. </quote> <bibl>Opening sentence of Hobbes's Leviathan</bibl> </cit>For more information on the use of the <quote> and <bibl> elements, see sections 6.3.3 and 6.10 respectively.
Where one or more whole texts are embedded within other texts, without necessarily forming a composite, the encoder may also choose to represent the nested structure directly. The <text> element is itself a component element, and thus can appear within any division level element in the same way as a paragraph. For example, texts such as the Decameron or the Arabian Nights might be regarded as sequences of discrete texts embedded within another single text, the framing narrative, rather than as groups of discrete texts in which the fragments of framing narrative are regarded as front matter.
By front matter we mean distinct sections of a text (usually, but not exclusively, a printed one), prefixed to it by way of introduction or identification as a part of its production. Features such as title pages or prefaces are clear examples; a less definite case might be the prologue attached to a play. The front matter of an encoded text should not be confused with the TEI header described in chapter 5 , which serves as a kind of front matter for the computer file itself, not the text it encodes.
An encoder may choose simply to ignore the front matter in a text, if the original presentation of the work is of no interest, or for other reasons; alternatively some or all components of the front matter may be thought worth including with the text as components of the <front> element. [ see note 54 ] With the exception of the title page, (on which see section 7.5 ), front matter should be encoded using the same elements as the rest of a text. As with the divisions of the text body, no other specific tags are proposed here for the various kinds of subdivision which may appear within front matter: instead either numbered or un-numbered <div> elements may be used. The following suggested values [ see note 55 ] for the type attribute may be used to distinguish various kinds of division characteristic of front matter:
The following extended example demonstrates how various parts of the front matter of a text may be encoded. The front part begins with a title page, which is presented in section 7.5 below. This is followed by a dedication and a preface, each of which is encoded as a distinct <div> :
<div type='dedication'>
<p>To my parents, Ida and Max Fish
</div>
<div type='preface'>
<head>Preface</head>
<p>The answer this book gives to its title question is
<q>there is and there isn't</q>.
<!-- ... -->
<p>Chapters 1-12 have been previously published in the
following journals and collections:
<list>
<item>chapters 1 and 3 in <title>New literary
History</title></item>
<!-- ... -->
<item>chapter 10 in <title>Boundary II</title> (1980)</item>
</list>. I am grateful for permission to reprint.
<signed>S.F.</signed>
</div>
The front matter concludes with another <div> element, shown in the next example, this time containing a table of contents, which contains a <list> element (as described in section 6.7 ). Note the use of the <ptr> element to provide page-references: the implication here is that the target identifiers supplied (P1, P68 etc.) may correspond with identifiers used either for <div> elements representing chapters of the text, or for <pb> elements marking page divisions of the text. (For the <ptr> element, see 6.6 .) Alternatively, the literal page numbers present in the source text might be transcribed, but they are likely to be of little direct use in work with the electronic text.
<div type='contents'>
<head>Contents</head>
<list>
<item>Introduction, or How I stopped Worrying and Learned
to Love Interpretation <ptr target=p1>
</item>
<item><list><head>Part One: Literature in the Reader</head>
<item n='1'>Literature in the Reader: Affective
Stylistics <ptr target=p21>
<item n='2'>What is Stylistics and Why Are They
Saying Such Terrible Things About It? <ptr target=p68>
<!-- ... -->
</list></list>
</div>
The following example uses numbered divisions to mark up the front matter of a medieval text. (Entity references are used to represent the characters thorn, yogh, and ampersand, as discussed in section 4.1.2 .) Note that in this case no title page in the modern sense occurs; the title is simply given as a heading at the start of the front matter. Note also the use of the type attribute on the <div> elements to indicate document elements comparatively unusual in modern books such as the initial prayer:
<front>
<div1 type=incipit>
<p>Here bygynni&th; a book of contemplacyon, &th;e whiche
is clepyd <title>&Th;E CLOWDE OF VNKNOWYNG</title>,
in &th;e whiche a soule is onyd wi&th; GOD.
<div1 type='prayer'>
<head>Here biginne&th; &th;e preyer on &th;e prologe.</head>
<p>God, unto whom alle hertes ben open, & unto
whome alle wille speki&th;, & unto whom no priue
&th;ing is hid: I beseche &th;ee so for to clense &th;e
entent of myn hert wi&th; &th;e unspekable &yog;ift of
&th;i grace, &th;at I may parfiteliche loue &th;ee
& wor&th;ilich preise &th;ee. Amen.
<div1 type='preface'>
<head>Here biginne&th; &th;e prolog.</head>
<p>In &th;e name of &th;e Fader & of &th;e Sone &
of &th;e Holy Goost.
<p>I charge &th;ee & I beseeche &th;ee, wi&th; as moche
power & vertewe as &th;e bonde of charite is sufficient
to suffre, what-so-euer &th;ou be &th;at &th;is book schalt
haue in possession ...
<div1 type='contents'>
<head>Here biginne&th; a table of &th;e chapitres.</head>
<list>
<label>&th;e first chapitre </label>
<item>Of foure degrees of Cristen mens leuing;
& of &th;e cours of his cleping &th;at &th;is
book was maad vnto.</item>
<label>&th;e secound chapitre</label>
<item>A schort stering to meeknes & to &th;e
werk of &th;this book</item>
<!-- ... -->
<label>&th;e fiue and seuenti chapitre</label>
<item>Of somme certein tokenes bi &th;e whiche
a man may proue whe&th;er he be clepid of God
to worche in &th;is werk.</item>
</list>
<trailer>& here eende&th; &th;e table of &th;e chapitres.
</trailer>
</front>
Detailed analysis of the title page and other preliminaries of older printed books and manuscripts is of major importance in descriptive bibliography and the cataloguing of printed books; such analysis may require a rather more detailed tag set than that proposed here. [ see note 56 ] The following elements are therefore proposed as an interim measure; they constitute a useful descriptive tag set for the major features of most title pages:
Together with the <figure> element described in chapter 22 , these elements constitute the element class tpParts , which is defined by the parameter entity m.tpParts . Any number of elements from this class can appear grouped together within a <titlePage> element. (The <figure> element is included so as to enable encoders to record the presence of printers' ornaments or other illustrative material found within a title page; its use implies that the TEI tagset for figures and tables has been selected, as discussed in chapter 22 ).
The elements listed above, together with the <head> element, also constitute the element class fmchunk , which is defined by the parameter entity m.fmchunk . The elements in this class can appear within a `minimal' <front> element without any need to group them together and encode a complete title page.
Encoders wishing to add new elements to either class may do so by modifying or redefining this parameter entity, as further described in chapter 29 . Two examples of the use of these elements follow. First, the title page of the work discussed earlier in this section:
<front>
<titlePage>
<docTitle>
<titlePart type=main>Is There a Text in This Class?</>
<titlePart type=sub>The Authority of Interpretive Communities</>
</docTitle>
<docAuthor>Stanley Fish</>
<docImprint><publisher>Harvard University Press</>
<pubPlace>Cambridge, Massachusetts</>
<pubPlace>London, England</>
</docImprint>
</titlepage>
Second, a characteristically verbose 17th century example:
<titlepage> <docTitle> <titlepart type=main> THE Pilgrim's Progress FROM THIS WORLD, TO That which is to come:</> <titlepart type=sub> Delivered under the Similitude of a DREAM</> <titlepart type=desc> Wherein is Discovered, The manner of his setting out, His Dangerous Journey; And safe Arrival at the Desired Countrey.</> </docTitle> <epigraph> <cit><q>I have used Similitudes,</q><bibl>Hos. 12.10</bibl></cit> </epigraph> <byline> By <docAuthor>John Bunyan</>.</byline> <imprimatur>Licensed and Entred according to Order.</> <docImprint> <pubPlace>LONDON,</> Printed for <name>Nath. Ponder</> at the <name>Peacock</> in the <name>Poultrey</> near <name>Cornhil</>, <docDate>1678</>. </docImprint>
Those elements in the above list which are not defined elsewhere have the following formal declarations:
<!-- 7.5: Tags for title pages -->
<!ELEMENT titlePage - o (%m.tpParts;)+ >
<!ATTLIST titlePage %a.global;
type CDATA #IMPLIED >
<!ELEMENT docTitle - o (titlePart+) >
<!ATTLIST docTitle %a.global; >
<!ELEMENT titlePart - O (%paraContent;) >
<!ATTLIST titlePart %a.global;
type CDATA main >
<!ELEMENT docAuthor - O (%phrase.seq;) >
<!ATTLIST docAuthor %a.global; >
<!ELEMENT imprimatur - O (%paraContent;) >
<!ATTLIST imprimatur %a.global; >
<!ELEMENT docEdition - O (%paraContent;) >
<!ATTLIST docEdition %a.global; >
<!ELEMENT docImprint - O (%phrase.seq | pubPlace | docDate
| publisher)* >
<!ATTLIST docImprint %a.global; >
<!ELEMENT docDate - O (%phrase.seq;) >
<!ATTLIST docDate %a.global;
value %ISO-date #IMPLIED >
<!-- This fragment is used in sec. 7.5 -->
Where title pages are encoded, their physical rendition is often of considerable importance. One approach to this requirement would be to use the <seg> tag, described in chapter 14 , to segment the typographic content of each part of the title page, and then use the global rend attribute to specify its rendition. Another would be to use a tag set specialized for the description of typographic entities such as pages, lines, rules, etc., bearing special-purpose attributes to describe line height, leading, degree of kerning, font, etc. Further discussion of these problems is provided in chapter 18 .
Front matter elements are defined in a distinct DTD file called TEIfron2.dtd.
<!-- 7.5: Additional Tag Set for Front Matter -->
<!ELEMENT front - O ( (%m.front;)*, ( ( (%m.fmchunk;),
(%m.fmchunk; | titlePage)*) | (
(div), (div | (%m.front;) )*) | (
(div1), (div1 | (%m.front;) )*) )?
) >
<!ATTLIST front %a.global;
%a.declaring; >
<!ENTITY % x.tpParts '' >
<!ENTITY % m.tpParts '%x.tpParts byline | docAuthor | docDate |
docEdition | docImprint | docTitle | epigraph |
figure | imprimatur | titlePart' >
<!-- ... declarations from section 7.5 -->
<!-- (Tags for title pages) -->
<!-- go here ... -->
Conventions vary as to which elements are grouped as back matter and which as front. For example, some books place the table of contents at the front, and others at the back. Even title pages may appear at the back of a book as well as at the front. The content model for <back> and <front> elements are therefore identical.
The following suggested values may be used for the type attribute on all division elements, in order to distinguish various kinds of division characteristic of back matter:
No additional elements are proposed for the encoding of back matter at present. Some characteristic examples follow; first, an index (for the case in which a printed index is of sufficient interest to merit transcription):
<back>
<div type=index>
<head>Index</head>
<list type=index>
<item>Actors, public, paid for the contempt attending
their profession, <ptr target=p209>
<item>Africa, cause assigned for the barbarous state of
the interior parts of that continent, <ptr target=p125>
<item>Agriculture
<list type=indexentry>
<item>ancient policy of Europe unfavourable to, <ptr target=p371>
<item>artificers necessary to carry it on, <ptr target=p481>
<item>cattle and tillage mutually improve each other,
<ptr target=p325>
<!-- ... -->
<item>wealth arising from more solid than that which proceeds
from commerce <ptr target=p520>
</list>
<item>Alehouses, not the efficient cause of drunkenness,
<ptr target=p461>
<!-- ... -->
</list>
</div>
<!-- ... -->
</back>
Next, a back-matter division in epistolary form:
<back> <div type=letter> <head>A letter written to his wife, founde with this booke after his death.</head> <p>The remembrance of the many wrongs offred thee, and thy unreproued vertues, adde greater sorrow to my miserable state, than I can utter or thou conceiue.... ... yet trust I in the world to come to find mercie, by the merites of my Saiuour to whom I commend thee, and commit my soule. <signed>Thy repentant husband for his disloyaltie, <name>Robert Greene.</name></signed> <epigraph lang=LA><p>Faelicem fuisse infaustum</epigraph> <trailer>FINIS</trailer> </div> <!-- ... --> </back>
And finally, a list of corrigenda and addenda with pseudo-epistolary features:
<back> <div type=corrigenda> <head>Addenda</head> <salute lang=LA>M. Scriblerus Lectori</salute> <p>Once more, gentle reader I appeal unto thee, from the shameful ignorance of the Editor, by whom Our own Specimen of <name>Virgil</> hath been mangled in such miserable manner, that scarce without tears can we behold it. At the very entrance, Instead of <q lang=GR>prolego/mena</q>, lo! <q lang=GR>prolegw/mena</q> with an Omega! and in the same line <q lang=LA>consulâs</q> with a circumflex! In the next page thou findest <q lang=LA> leviter perlabere</>, which his ignorance took to be the infinitive mood of <q lang=LA>perlabor</> but ought to be <q lang=LA>perlabi</> ... Wipe away all these monsters, Reader, with thy quill.</p> </div> </back>
The <back> element is defined in file TEIback2.dtd; since there are no other specialized back-matter tags, nothing else is defined there.
<!-- 7.6: Tags for Back Matter -->
<!ELEMENT back - O ( (%m.front)*, ( ( (%m.divtop),
(%m.divtop | titlePage)*) | (
(div), (div | (%m.front))*) | (
(div1), (div1 | (%m.front))*) )? )
>
<!ATTLIST back %a.global;
%a.declaring; >
The DTD fragment described by the present chapter is found in file teistr2.dtd; it has the following overall structure:
<!-- 7.7: Default text structure -->
<!-- This definition of the basic text structure is used by -->
<!-- most TEI base tag sets; some bases, however, use slight -->
<!-- variations upon it. -->
<!ENTITY % x.divtop '' >
<!ENTITY % m.divtop '%x.divtop argument | byline | dateline |
docAuthor | docDate | epigraph | head | opener |
salute | signed' >
<!ENTITY % x.divbot '' >
<!ENTITY % m.divbot '%x.divbot byline | closer | dateline |
epigraph | salute | signed | trailer' >
<!-- ... declarations from section 7 -->
<!-- (Top-level parts of default structure) -->
<!-- go here ... -->
<!-- ... declarations from section 7.1.1 -->
<!-- (Un-numbered divisions) -->
<!-- go here ... -->
<!-- ... declarations from section 7.1.2 -->
<!-- (Numbered divisions) -->
<!-- go here ... -->
<!-- ... declarations from section 7.2.4 -->
<!-- (Tags for start and end of divisions) -->
<!-- go here ... -->
<!-- Front matter is defined in TEI.front file. -->
<!ENTITY % TEI.front.dtd system 'teifron2.dtd' >
%TEI.front.dtd;
<!-- Back matter is defined in TEI.back file. -->
<!ENTITY % TEI.back.dtd system 'teiback2.dtd' >
%TEI.back.dtd;
| Previous | Up | Next |