<!--* $Id: p2ds.odd,v 1.4 1998/01/28 11:44:14 cmsmcq Exp $ *-->
<!--*
    * $Log: p2ds.odd,v $
    * Revision 1.4  1998/01/28 11:44:14  cmsmcq
    * LB changes of Jan 1998 and RCS keywords added.
    *
    *-->
<!-- Revisions:                                               -->
<!-- 12 jan 98 : LB : fix egs -->
<!-- 93-06-03 : MSM : rename entities                         -->
<!-- 93-03-26 : MSM : one last typo corrected                 -->
<!-- 93-03-25 : MSM : final revision for publication          -->
<!--                  make new top file                       -->
<!-- 26 mar 93 : LB : added divn class                        -->
<!-- 14 Mar 93 : LB : added material on divtop elements       -->
<!--  9 Mar 93 : LB : cannibalized from old PR, CCGrp         -->

<div1 n='7' id=DS type='chapter'><head>Default Text Structure</head>

<p>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 <ptr
target=ST>.

<p>TEI texts may be regarded either as <term>unitary</term>, that is,
forming an organic whole, or as <term>composite,</term> 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.

<p>Whether unitary or composite, the text is marked with the
<gi>text</gi> tag and may contain front matter, a text body, and back
matter.  In unitary texts, the text body is tagged <gi>body</gi>; in
composite texts, where the text body consists of a series of subordinate
texts or groups, it is tagged <gi>group</gi>.  The overall structure of
any text, unitary or composite, is thus defined by the following
elements:

<list type=gloss>
<label><gi>text</gi></label>
<item>contains a single text of any kind, whether unitary or

composite, for example a poem or drama, a collection of 
essays, a novel,
a dictionary, or a corpus sample.</item>
<label><gi>front</gi></label>
<item>contains any prefatory matter (headers,
title page, 
prefaces, dedications, etc.)
found before the start of a 
text proper.</item>
<label><gi>body</gi></label>
<item>contains the whole body of a single unitary
text, 
excluding any front or back
matter.</item>
<label><gi>group</gi></label>
<item>contains the body of a composite text, grouping together a

sequence of distinct texts (or groups of such texts) which 
are regarded
as a unit for some purpose, for example the 
collected works of an
author, a sequence of prose essays, 
etc.</item>
<label><gi>back</gi></label>
<item>contains any appendixes, etc. following the main part of a

text.</item>
</list>


<p>The overall structure of a unitary text is:
<eg rend=skel>
<![ CDATA [
 <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>
]]>
</eg>
<p>The overall structure of a composite text made up of two unitary
texts is:
<eg rend=skel>
<![ CDATA [
 <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>
]]>
</eg>

<p>Each of these elements is further described in the following
subsections.  <gi>text</gi>, <gi>body</gi> and <gi>group</gi> are
formally declared as follows:

<eg id=ddstext>
<![ CDATA [
<!-- 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                        -->
]]>
</eg>


Elements <gi>front</gi> and <gi>back</gi> are declared separately, as
further discussed in sections <ptr target=DSfront> and <ptr
target=DSback>.  Textual elements, such as paragraphs, lists or phrases,
which nest within these major structural elements, are discussed in
chapter <ptr target=CO> (for elements common to all kinds of document)
and in part II (for elements specific to a particular base).  The
<gi>group</gi> element, used for composite texts, is further discussed
in section <ptr target=DSgrp>.

<!--* $Id: p2ds1.odd,v 1.7 1998/01/28 11:44:14 cmsmcq Exp $ *-->
<!--*
    * $Log: p2ds1.odd,v $
# Revision 1.7  1998/01/28  11:44:14  cmsmcq
# LB changes of Jan 1998 and RCS keywords added.
#
    *-->
<!-- Revisions:                                               -->
<!-- 12 jan 98 : fixing egs -->
<!-- 4 Jan 98: remove redundant comma before discussion of opener -->
<!-- 4 mar: dtb typos -->
<!-- 28 dec 93: LB : divn attrib is sample, not complete      -->
<!-- 93-06-05 : MSM : fix ]]>                                 -->
<!-- 1993-03-26 : MSM,LB : last-minute typos and revisions    -->
<!-- 1993-03-25 : MSM : light revision for publ               -->

<div2 id=DSdiv type='section'><head>Divisions of the Body</head>

<p>In some texts, the body consists simply of a sequence of low-level
structural items, referred to here as <term>components</term> or
<term>component-level elements</term> (see section <ptr
target=STec>).  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
<q>book</q>, that of a report is usually called a <q>part</q> or
<q>section</q>, that of a novel a <q>chapter</q> --- unless it is an
epistolary novel, in which case it may be called a <q>letter</q>.  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 <q>acts</q> and <q>scenes</q>; a reference book into
<q>sections</q>; a diary or day book into <q>entries</q>; a newspaper
into <q>issues</q> and <q>sections</q>, and so forth.

<p>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 <att>type</att> used to categorize elements
independently of their hierarchic level.  Two alternative styles are
provided for the marking of these neutral divisions:
<term>numbered</term> and <term>un-numbered</term>.  Numbered divisions
are named <gi>div0</gi>, <gi>div1</gi>, <gi>div2</gi>, etc., where the
number indicates the depth of this particular division within the
hierarchy, the largest such division being <q>div0</q>, any subdivision
within it being <q>div1</q>, any further sub-sub-division being
<q>div2</q> and so on.  Un-numbered divisions are simply named
<gi>div</gi>, and allowed to nest recursively to indicate their
hierarchic depth.  The two styles may <emph>not</emph> be combined
within a single <gi>front</gi>, <gi>body</gi> or <gi>back</gi> element.

<div3 id=DSdiv1><head>Un-numbered Divisions</head>

<p>The following element is used to identify textual subdivisions
in the un-numbered style:
<list type=gloss>
<label><gi>div</gi></label>
<item>contains a subdivision of the front, body, or back of a 
text.</item>
</list>


As a member of the class <term>divn</term>, this element has the
following additional attribute:

<list type=gloss>
<label><att>type</att></label>
<item>specifies a name conventionally used for this level of 
subdivision, e.g. <q>act</q>, <q>volume</q>, <q>book</q>, 
<q>section</q>, <q>canto</q>, etc.</item>
</list>

<p>Using this style, the body of a text containing two parts, each
composed of two chapters, might be represented as follows:

<eg rend=skel><![ CDATA[
 <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>
]]>
</eg>

<p>Note that end-tags are mandatory for un-numbered divisions, to avoid
ambiguity.  Note also that the <att>type</att> attribute must be
specified each time its value changes, for reasons discussed in section
<ptr target=DSdiv3> below.

<p>The <gi>div</gi> element has the following formal definition:

<eg id=ddsdiv>
<![ CDATA [
<!-- 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                        -->
]]>
</eg>


<div3 id=DSdiv2><head>Numbered Divisions</head>

<p>The following elements are used to identify textual subdivisions
in the numbered style:
<list type=gloss>
<label><gi>div0</gi></label>
<item>contains the largest possible subdivision of the body
of a 
text.</item>
<label><gi>div1</gi></label>
<item>contains a first-level subdivision of the front, body, or 
back
of a text (the largest, if
<gi>div0</gi> is not 
used, the second largest if it is).</item>
<label><gi>div2</gi></label>
<item>contains a second-level subdivision of the front, body, or 
back of a
 text.</item>
<label><gi>div3</gi></label>
<item>contains a third-level subdivision of the front, body, or 
back of a
 text.</item>
<label><gi>div4</gi></label>
<item>contains a fourth-level subdivision of the front, body, or 
back of a
 text.</item>
<label><gi>div5</gi></label>
<item>contains a fifth-level subdivision of the front, body, or 
back of a
 text.</item>
<label><gi>div6</gi></label>
<item>contains a sixth-level subdivision of the front, body, or 
back of a
 text.</item>
<label><gi>div7</gi></label>
<item>contains the smallest possible subdivision of the front, 
body or
back of a text, larger than a paragraph.</item>
</list>


As members of the class <term>divn</term> these elements all bear the
following additional attribute:

<list type=gloss>
<label><att>type</att></label>
<item>specifies a name conventionally used for this level of 
subdivision, e.g. <q>act</q>, <q>volume</q>, <q>book</q>, 
<q>section</q>, <q>canto</q>, etc.</item>
</list>

<p>The largest possible subdivision of the body may be regarded either
as a <gi>div0</gi> or as a <gi>div1</gi> element,
<note place=foot>This convention (corresponding with the idea that a
type-set document may begin either with a <q>level 0</q> or a <q>level
1</q> heading) is provided for convenience and compatibility with some
widely used formatting systems.</note>
and the smallest possible <gi>div7</gi>.  If numbered divisions are in
use, a division at any one level (say, <gi>div3</gi>), may contain only
numbered divisions at the next lowest level (in this case,
<gi>div4</gi>).

<p>Using this style, the body of a text containing two parts, each
composed of two chapters, might be represented as follows:

<eg rend=skel><![ CDATA[
 <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>
]]>
</eg>
<!-- Changed example:  the point of the div1/div0             -->
<!-- alternation in the body is to allow the scheme to        -->
<!-- handle Chapters at a consistent level with or without    -->
<!-- surrounding Parts, so the natural way to tag Part and    -->
<!-- Chapter here is div0 div1, not div1 div2, or at least    -->
<!-- so it seems to me.  -msm                                 -->
<!-- tough if you then want sections too (LB) -->
<!-- Also changed to agree with previous example in N values  -->
<!-- and comments. -msm                                       -->

<p>Formal definitions for these elements are as follows:
<eg id=ddsdivn>
<![ CDATA [
<!-- 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                        -->
]]>
</eg>


<div3 id=DSdiv3><head>Numbered or Un-numbered?</head>

<!-- added following para for clarification -->
<p>Within the same <gi>front</gi>, <gi>body</gi> or <gi>back</gi>
element, all hierarchic subdivisions must be marked either using
nested <gi>div</gi> elements, or using the <gi>div0</gi>,
<gi>div1</gi>, <gi>div2</gi> tag appropriate at each level; the two
styles may <emph>not</emph> be mixed.

<p>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.
<!-- LB added following sentence -->
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
<q>chapter</q> may be at level 1 in one work and level 3 in another.

<p>Whichever style is used, the global <att>n</att> and <att>id</att>
attributes (section <ptr target=STga>) 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 <ptr target=COrs>).

<p>As indicated above, the <att>type</att> attribute is used to
provide a name or description for the division.  Typical values might
be <q>book</q>, <q>chapter</q>, <q>section</q>, <q>part</q>, or (for
verse texts) <q>book</q>, <q>canto</q>, <q>stanza</q>, or (for
dramatic texts) <q>act</q>, <q>scene</q>.  This attribute has a
declared value of <code lang=sgml>#CURRENT</code>, 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 <q>down</q> and
<q>up</q> the document hierarchy.

<p>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
<ptr target=DSdtb> and the <gi>p</gi> element discussed in section
<ptr target=COpa>.

<!-- a long example but an irresistible one... -->

<eg><![ CDATA[
<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 ...

]]>
</eg>
<!--   Fielding, Joseph Andrews (ed Battestin, 1961) -->
<!-- Again, example changed to use div0, div1 not 1, 2. -msm  -->

<div3 id=DSdiv3x><head>Partial and Composite Divisions</head>

<p>In most situations, the textual subdivisions marked by <gi>div</gi>
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.

<p>To overcome these problems, the following additional attributes are
defined for all elements in the <term>divn</term> class:

<list type=gloss>
<label><att>org</att></label>
<item>specifies how the content of the division is organized.
Legal values are:
<list type=gloss>
<label><term>composite</term></label>
<item>composite content: i.e. no claim is made about the sequence 
in which the immediate contents of this division are to be 
processed, or their inter-relationships.</item>
<label><term>uniform</term></label>
<item>uniform content: i.e. the immediate contents of this 
element are regarded as forming a logical unit, to be 
processed in sequence.</item>
</list></item>
<label><att>sample</att></label>
<item>indicates whether this division is a sample of the original 
source and if so, from which part.
Legal values are:
<list type=gloss>
<label><term>final</term></label>
<item>division lacks material at start.</item>
<label><term>complete</term></label>
<item>division is not a sample.</item>
<label><term>medial</term></label>
<item>division lacks material at start and end.</item>
<label><term>unknown</term></label>
<item>position of sampled material within original unknown.</item>
<label><term>initial</term></label>
<item>division lacks material present at end in source.</item>
</list></item>
<label><att>part</att></label>
<item>specifies whether or not the division is fragmented by some 
other structural element, for example a speech which is 
divided between two or more verse stanzas.
Legal values are:
<list type=gloss>
<label><term>F</term></label>
<item>the final part of an incomplete division</item>
<label><term>Y</term></label>
<item>the division is incomplete in some respect</item>
<label><term>N</term></label>
<item>either the division is complete, or no claim is made as to 
its completeness.</item>
<label><term>I</term></label>
<item>the initial part of an incomplete division</item>
<label><term>M</term></label>
<item>a medial part of an incomplete division</item>
</list></item>
</list>

<p>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 <gi>div</gi> element in the following form:
<eg>
<![ CDATA [
 <div n='xx' sample=initial part=Y type=chapter>
 <p><!-- ... -->
 </div>
]]>
</eg>
where <q>xx</q> represents a number for the chapter.  The
<gi>sampling</gi> element in the TEI Header should also be used to
record the principles underlying the selection of incomplete samples, as
further described in section <ptr target=HD52>.

<p>The following example demonstrates how a newspaper column composed of
very short unrelated snippets may be encoded using these attributes:

<eg>
<![ CDATA [

<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>
]]>
</eg> <!-- Guardian 21 Dec 1992, p 2 -->

<p>The <att>org</att> attribute on the <gi>div1</gi> element is used
here to indicate that individual stories in this group, marked here as
<gi>div2</gi>, 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.

<p>This method of encoding composite texts as composite divisions has
some limitations compared with the more general and powerful mechanisms
discussed in section <ptr target=DSgrp>. However, it may be preferable
in some circumstances, notably where the individual texts are very
small.

<div2 id=DSdtb><head>Elements Common to All Divisions</head>

<p>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 <term>divtop</term> or <term>divbot</term>
respectively.

<p>The following special-purpose elements are provided to
mark features which may appear only at the start of a division:

<list type=gloss>
<label><gi>head</gi></label>
<item>contains any heading, for example, the title of a section,

or the heading of a list or glossary.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>categorizes the heading in some way meaningful to the 
encoder.</item>
</list>
</item>
<label><gi>epigraph</gi></label>
<item>contains a quotation, anonymous or attributed, appearing at
the start of a section or chapter, or on a title page. </item>
<label><gi>argument</gi></label>
<item>A formal list or prose description of the topics addressed 
by
a subdivision of a text.</item>
<label><gi>opener</gi></label>
<item>groups together dateline, byline, salutation, and similar

phrases appearing as a preliminary group at the start of a

division, especially of a letter.</item>
</list>


For further details of the <gi>head</gi> element, see section <ptr
target=DShd>; for <gi>epigraph</gi> and <gi>argument</gi>, see section
<ptr target=DSae>; for <gi>opener</gi>, see section <ptr target=DSoc>.

<p>The following special-purpose elements are provided to mark features
which may appear only at the end of a division:

<list type=gloss>
<label><gi>trailer</gi></label>
<item>contains a closing title or footer appearing at the end of

a division of a text. </item>
<label><gi>closer</gi></label>
<item>groups together dateline, byline, salutation, and similar

phrases appearing as a final group at the end of a

division, especially of a letter.</item>
</list>


For further details of the <gi>trailer</gi> element, see section <ptr
target=DShd>; for the <gi>closer</gi> element, section <ptr
target=DSoc>.

<div3 id=DShd><head>Headings and Trailers</head>

<p>The <gi>head</gi> 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:

<eg>
<![ CDATA [

<div1 n='Etym'>
<head>Etymology</head>
<head>(Supplied by a late consumptive usher to a
grammar school)</head>
<p>The pale Usher &mdash; threadbare in coat, heart,
body and brain; I see him now. He was ever
dusting his old lexicons and grammars....
]]>
</eg><!-- H Melville, M.Dick -->

<p>Unlike some other markup schemes, the TEI scheme does
<emph>not</emph> require that headings attached to textual subdivisions
at different hierarchic levels have different identifiers. All kinds of
heading are marked identically using the <gi>head</gi> tag; the type or
level of heading intended is implied by the immediate parent of the
<gi>head</gi> element, which may for example be a <gi>div1</gi>,
<gi>div2</gi>, etc., an un-numbered <gi>div</gi>, or a <gi>list</gi>.

<p>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 <q>main</q> headings, or <q>detail</q>
headings. Specific elements are provided for certain kinds of
heading-like features, (notably <gi>byline</gi>, <gi>dateline</gi> and
<gi>salute</gi>; see further section <ptr target=DSoc>),  but the
<att>type</att> attribute must be used to discriminate among other
forms of heading.

<p>In the following example, taken from a British newspaper, the lead
story and its associated headlines have been encoded  as a <gi>div</gi>
element, with appropriate <term>divtop</term> elements attached:

<eg> <![ CDATA [
<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....
]]>
</eg><!-- Daily Telegraph 21 Dec 1992 -->

<p>In older writings, the headings or <term>incipits</term> may be
longer than in modern works.
<!-- Heading-like features which appear in the middle of a    -->
<!-- text should normally be regarded either as < gi > quote  -->
<!-- < / gi > elements (if they have no connexion with the    -->
<!-- immediately surrounding text), or as starting new < gi   -->
<!-- > div < / gi > elements (if they are more closely        -->
<!-- connected with the text following than with the text     -->
<!-- preceding).                                              -->
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 <gi>head</gi> of a new <gi>div</gi> element.
If it appears to be simply inserted or superimposed --- as for example
the kind of <soCalled>pull quotes</soCalled> often found in newspapers
or magazines, then the <gi>quote</gi>, <gi>q</gi>, or <gi>cit</gi>
element may be more appropriate.

<p>The <gi>trailer</gi> 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:

<eg><![ CDATA [
 <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>
]]>
</eg>

<div3 id=DSoc><head>Openers and Closers</head>

<p>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 <ptr target=ND>.
<!-- To cater for the full -->
<!-- variety of such features, the elements described in chapter <ptr -->
<!-- target=LM> should also be used, but for many -->
For simple cases, the following elements should be adequate:

<list type=gloss>
<label><gi>byline</gi></label>
<item>contains the primary statement of responsibility given for 
a work
on its title page or at the head or end of the 
work.</item>
<label><gi>dateline</gi></label>
<item>contains a brief description of the place, date, time, etc. 
of
production of a letter, newspaper story, or other work, 
prefixed or
suffixed to it as a kind of heading or 
trailer. </item>
<label><gi>salute</gi></label>
<item>contains a salutation or greeting prefixed to a foreword,

dedicatory epistle or other division of a text, or the

salutation in the closing of a letter, preface, etc.</item>
<label><gi>signed</gi></label>
<item>contains the closing salutation, etc., appended to a 
foreword,
dedicatory epistle, or other division of a text. 
</item>
</list>



<p>The <gi>byline</gi> and <gi>dateline</gi> 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 <gi>dateline</gi> or <gi>byline</gi> elements apply
only to newspaper texts.  The following example illustrates use of the
<gi>dateline</gi> and <gi>signed</gi> elements at the end of the
preface to a novel:

<eg>
<![ CDATA [
<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>

]]>
</eg><!-- B Disraeli, Coningsby (Nelson, nd) -->

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

<list type=gloss>
<label><gi>opener</gi></label>
<item>groups together dateline, byline, salutation, and similar

phrases appearing as a preliminary group at the start of a

division, especially of a letter.</item>
<label><gi>closer</gi></label>
<item>groups together dateline, byline, salutation, and similar

phrases appearing as a final group at the end of a

division, especially of a letter.</item>
</list>


The following examples demonstrate the use of the <gi>opener</gi> and
<gi>closer</gi> grouping elements:

<eg>
<![ CDATA [
<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, &mdash;
  </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>
]]>
</eg><!-- W. Collins, The Moonstone, Penguin, pp 503, 513 -->


<eg>
<![ CDATA [
<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>
]]>
</eg><!-- S. Richardson 'Clarissa', (Dent, EML, vol 1, p62,64 -->

<p>For further discussion of the encoding of names of persons and places
and of dates, see section <ptr target=COnada> and chapter <ptr target=ND>.

<div3 id=DSae><head>Arguments and Epigraphs</head>
<!-- may have a head -->
<p>The <gi>argument</gi> 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:

<eg><![ CDATA [
<div type=chap n='6'>
<argument>
<p>Kingston &mdash; Instructive remarks on early English
history &mdash; Instructive observations on carved oak
and life in general &mdash; Sad case of Stivvings,
junior &mdash; Musings on antiquity &mdash; I forget
that I am steering &mdash; Interesting result &mdash;
Hampton Court Maze &mdash; Harris as a guide.
</argument>
<p> It was a glorious morning, late spring or early summer,
as you care to take it...
</div>
]]>
</eg><!-- Jerome, J.K. : Three men in a boat, ch 6 -->
<eg><![ CDATA [
<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>
]]>
</eg><!-- Jerome, J.K. : Three men in a boat, ch 6 -->

<p>An <term>epigraph</term> 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 <gi>epigraph</gi> element.  Its
content will generally be a <gi>q</gi> or <gi>quote</gi> element,
often associated with a bibliographic reference, as in the
following example:

<eg><![ CDATA [
<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 ...
]]>
</eg>
<!-- G. Eliot, D. Deronda, (1876) III.1 (Penguin, 1967, p. 245)  -->

<p>For discussion of quotations appearing other than as epigraphs refer
to section <ptr target=COhqq>.


<div3 id=DSco><head>Content of Textual Divisions</head>

<p>Other than its initial sequence of <term>divtop</term> elements,
and its closing sequence of <term>divbot</term> elements, every
textual division (numbered or un-numbered) consists of a sequence of
<!-- ungrouped lower-level structural elements, that is, a sequence of -->
ungrouped <term>component</term> elements (see <ptr
target=STec>).  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 <ptr target=DR>) will be available.  If the dictionary base
is in use, then dictionary entries, related entries, etc. (as defined
in chapter <ptr target=DI>) will also be available; if the tag set
for transcribed speech is in use, then utterances, pauses, vocals,
kinesics, etc., as defined in chapter <ptr target=TSba> will be
available; and so on.

<p>Where a text contains low level elements from more than one base, two
options are available.  The first option, selected by the
<soCalled>mixed</soCalled> 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 <soCalled>general</soCalled> 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 <ptr target=STco>.

<p>The elements discussed in this section are formally defined as
follows:

<eg id=ddsdivx>
<![ CDATA [
<!-- 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                        -->
]]>
</eg>



<!--* $Id: p2ds2.odd,v 1.6 1998/01/31 19:24:34 tei Exp $ *-->
<!--*
    **
    * $Log: p2ds2.odd,v $
    * Revision 1.6  1998/01/31 19:24:34  tei
    * tidying examples
    *
    * Revision 1.5  98/01/28  11:44:14  cmsmcq
    * LB changes of Jan 1998 and RCS keywords added.
    *
    *-->
<!-- Revisions:                                               -->
<!-- 12 jan 98 : LB : fixing egs -->
<!-- 1993-03-26 : LB, MSM : last-minute corrections, revs     -->
<!-- 1993-03-25 : MSM : revision for publication              -->

<div2 id=DSgrp><head>Groups of Texts</head>

<p>The <gi>group</gi> 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 <gi>group</gi>, though encoders may
choose to use this structure to represent other kinds of composite
texts as well.

<list type=gloss>
<label><gi>group</gi></label>
<item>contains the body of a composite text, grouping together a

sequence of distinct texts (or groups of such texts) which 
are regarded
as a unit for some purpose, for example the 
collected works of an
author, a sequence of prose essays, 
etc.</item>
</list>


<p>For example, the overall structure of a collection of
short stories might be encoded as follows:

<eg>
<![ CDATA [
 <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. &mdash;</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. &mdash;</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. &mdash;</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>
]]>
</eg><!-- Original Illustrated Sherlock Holmes (Castle Books, 1989) -->

<p>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 <title>Muses Library</title> 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:

<list>
<item><title>Steps to the Temple</title> (a collection of
verse first published in 1648)
<item><title>Carmen deo Nostro</title> (a second collection,
published in 1652)
<item><title>The Delights of the Muses</title> (a third
collection, published in 1648)
<item><title>Posthumous Poems,</title> I (a collection of
fragments all taken from a single manuscript)
<item><title>Posthumous Poems,</title> II (a further collection
of fragments, taken from a different manuscript)
</list>

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

<p>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
<gi>front</gi> element and its constituents (on which see further
section <ptr target=DSfront>), while the body of each collection should
be encoded as a single <gi>group</gi> element.  Each individual poem
within the collections should be encoded as a distinct <gi>text</gi>
element.  The beginning of the whole collection would thus appear as
follows (for further discussion of the use of the elements <gi>div</gi>
and <gi>lg</gi> for textual subdivision of verse, see section
<ptr target=COve> and chapter <ptr target=VE>):

<eg>
<![ CDATA [

<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>
]]>
</eg>

<p>The <gi>group</gi> 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
<title>The Norton Book of Travel</title>, an anthology edited by Paul
Fussell and published in 1987 by W.W. Norton.  This work comprises
the following major sections:

<list type=ordered>
<item>Front matter (title page, acknowledgments, introductory essay)
<item>The Beginnings
<item>The Eighteenth Century and the Grand Tour
<item>The Heyday
<item>Touristic Tendencies
<item>Post Tourism
<item>Back matter (permissions list, index)
</list>

Each titled section listed above comprises a group of extracts or
complete texts from writers of a given historical period, preceded by an
introductory essay.  For example, the second group listed above
contains, inter alia, the following:

<list type=ordered>
<item>Prefatory essay
<item>Five letters by Lady Mary Wortley Montagu
<item>An extract from Swift's Gullivers Travels
<item>Two poems by Alexander Pope
<item>Two extracts from Boswell's Journal
<item>A poem by William Blake
</list>

Each group of writings by a single author is preceded by a brief
biographical notice.  Some of the extracts are quite lengthy, containing
several chapters or other divisions; others are quite short.  As the
above list indicates, the texts included range across all kinds of
material:  verse, prose, journals and letters.

<p>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 <gi>group</gi> element within the larger
<gi>group</gi> 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 <gi>group</gi>
within the work.  Schematically:

<eg rend=skel>
<![ CDATA [
<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 -->
]]>
</eg>

<p>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 <gi>group</gi> containing one text
by Swift and one by the editor, or by treating the Montagu and Pope
sections as <gi>text</gi> elements containing the editor's essays as
front matter.  Marked in the second way, the Pope section of the book
would look like this:

<eg rend=skel>
<![ CDATA [
    <text><!-- Alexander Pope -->
        <front>
             <!-- biographical notice -->
        </front>
        <group>
             <text>  <!-- first poem  --> </text>
             <text>  <!-- second poem --> </text>
             <!-- ... -->
        </group>
    </text> <!-- end of Pope section -->
]]>
</eg>

<p>The essays on <q>The Eighteenth Century and the Grand Tour</q> and
other larger sections could also be tagged as <soCalled>front</soCalled>
matter in the same way, by treating the larger sections as <gi>text</gi>
elements rather than <gi>group</gi> elements.

<p>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
<ptr target=STco>.  The elements provided by the core tag set
described in chapter <ptr target=CO> should however prove adequate
for most simple purposes, where prose, drama, and verse are combined
in a single collection.

<p>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 <gi>cit</gi> element.  The following
component-level elements may be used to encode quotations of this kind:

<list type=gloss>
<label><gi>cit</gi></label>
<item>A quotation from some other document, together with a 
bibliographic
reference to its source.</item>
<label><gi>quote</gi></label>
<item>contains a phrase or passage attributed by the narrator or

author to some agency external to the text. </item>
</list>


For example, the chapter of <soCalled>extracts</soCalled> which appears
in the front matter of Melville's <title>Moby Dick</title> might be
encoded as follows:

<eg>
<![ CDATA [
<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 &dash; 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>
]]>
</eg>
For more information on the use of the <gi>quote</gi> and <gi>bibl</gi>
elements, see sections <ptr target=COhqq> and <ptr target=Cobi>
respectively.

<p>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 <gi>text</gi> element is
itself a <term>component</term>  element, and thus can appear
within any division level element in the same way as a paragraph.  For
example, texts such as the <title>Decameron</title> or the
<title>Arabian Nights</title> 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.

<!-- more detail needed here? -->



<!-- $Id: p2ds3.odd,v 1.9 1998/01/31 19:26:04 tei Exp $ -->
<!--*
    * $Log: p2ds3.odd,v $
    * Revision 1.9  1998/01/31 19:26:04  tei
    * examples fixed
    *
    * Revision 1.7  98/01/31  18:32:23  tei
    * added discussion of FMCHUNK class
    *
    *
    *-->
<!-- Revisions:                                               -->
<!-- 3 jan 94: LB: kill ornament -->
<!-- 30 dec 93: LB : fix up examples                          -->
<!-- 93-08-18 : MSM : suppress BYLINE definition              -->
<!-- 93-08-18 : MSM : add entdecls for front, back            -->
<!-- 1993-03-26 : LB, MSM : last-minute typos etc.            -->
<!-- 1993-03-25 : MSM : light revision for publ               -->

<div2 id=DSfront><head>Front Matter</head>

<p>By <term>front matter</term> 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 <ptr target=HD>, which serves as a kind of front matter for
the computer file itself, not the text it encodes.

<p>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
<gi>front</gi> element. <note>This decision should be recorded in the
<gi>sampling</gi> element of the header.</note>  With the exception of
the title page, (on which see section <ptr target=DStitl>), 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
<gi>div</gi> elements may be used.  The following suggested values
<note place=foot>As with all lists of <soCalled>suggested
values</soCalled> for attributes, it is recommended that software
written to handle TEI-conformant texts be prepared to recognize and
handle these values when they occur, without limiting the user to the
values in this list.
</note>
for the <att>type</att> attribute may be used to distinguish various
kinds of division characteristic of front matter:

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

<p>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 <ptr target=DStitl> below.
This is followed by a dedication and a preface, each of which is encoded
as a distinct <gi>div</gi>:

<eg><![ CDATA[

  <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>
]]>
</eg>

<p>The front matter concludes with another <gi>div</gi> element, shown
in the next example, this time containing a table of contents, which
contains a <gi>list</gi> element (as described in section <ptr
target=COli>).  Note the use of the <gi>ptr</gi> element to provide
page-references:  the implication here is that the target identifiers
supplied (P1, P68 etc.) may correspond with identifiers used either for
<gi>div</gi> elements representing chapters of the text, or for
<gi>pb</gi> elements marking page divisions of the text.  (For the
<gi>ptr</gi> element, see <ptr target=COxr>.)  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.

<eg><![ CDATA[
  <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>
]]>
</eg>

<p>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 <ptr
target=CHlon>.)  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 <att>type</att> attribute on the
<gi>div</gi> elements to indicate document elements comparatively
unusual in modern books such as the initial prayer:

 <eg><![ CDATA[
  <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, &amp; unto
  whome alle wille speki&th;, &amp; 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
  &amp; 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 &amp; of &th;e Sone &amp;
  of &th;e Holy Goost.
  <p>I charge &th;ee &amp; I beseeche &th;ee, wi&th; as moche
  power &amp; 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;
      &amp; 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 &amp; 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>&amp here eende&th; &th;e table of &th;e chapitres.
  </trailer>
  </front>
]]>
</eg>
<!-- Cloud of Unknowing, ed Phyllis Hodgson, EETS, 1944 -->

<div2 id=DStitl><head>Title Pages</head>

<p>Detailed analysis of the title page and other
<term>preliminaries</term> 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. <note>Definition of such a tag set remains
a work item for the TEI; such tag sets for contemporary printed matter
already exist or are being created within the publishing industry, for
example the Majour (Modular Application for Journals) Project of the
European Workgroup on SGML.  See for example <bibl><title>MAJOUR:
Modular Application for Journals:  DTD for Article Headers</title>
([n.p.]:  EWS, 1991).</bibl></note> 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:

<list type=gloss>
<label><gi>titlePage</gi></label>
<item>contains the title page of a text, appearing within the 
front
or back matter. </item>
<label><gi>docTitle</gi></label>
<item>contains the title of a document, including all its

constituents, as given on a title page.</item>
<label><gi>titlePart</gi></label>
<item>contains a subsection or division of the title of a work, 
as
indicated on a title page.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>specifies the role of this subdivision of the title.
Suggested values include:
<list type=gloss>
<label><term>desc</term></label>
<item>descriptive paraphrase of the work included in title</item>
<label><term>alt</term></label>
<item>alternative title of the work</item>
<label><term>main</term></label>
<item>main title of the work</item>
<label><term>sub</term></label>
<item>subtitle of the work</item>
</list></item>
</list>
</item>
<label><gi>argument</gi></label>
<item>A formal list or prose description of the topics addressed 
by
a subdivision of a text.</item>
<label><gi>byline</gi></label>
<item>contains the primary statement of responsibility given for 
a work
on its title page or at the head or end of the 
work.</item>
<label><gi>docAuthor</gi></label>
<item>contains the name of the author of the document, as given 
on the
title page (often but not always contained in a 
<gi>byline</gi>).</item>
<label><gi>epigraph</gi></label>
<item>contains a quotation, anonymous or attributed, appearing at
the start of a section or chapter, or on a title page. </item>
<label><gi>imprimatur</gi></label>
<item>contains a formal statement authorizing the publication of

a work, sometimes required to appear on a title page or its 
verso.</item>
<label><gi>docEdition</gi></label>
<item>contains an edition statement as presented on a title page 
of a
document.</item>
<label><gi>docImprint</gi></label>
<item>contains the imprint statement (place and date of 
publication,
publisher name), as given
(usually) at the 
foot of a title page.</item>
<label><gi>docDate</gi></label>
<item>contains the date of a document, as given
(usually) on a 
title page.</item>
</list>


<p>Together with the <gi>figure</gi> element described in chapter
<ptr target="FT">, these elements constitute the element class
<ident>tpParts</ident>, which is defined by the parameter entity
<ident>m.tpParts</ident>. Any number of elements from this class can
appear grouped together within a <gi>titlePage</gi> element. (The
<gi>figure</gi> 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 <ptr target="FT">).

<p>The elements listed above, together with the <gi>head</gi> element,
also constitute the element class <ident>fmchunk</ident>, which is
defined by the parameter entity <ident>m.fmchunk</ident>. The elements
in this class can appear within a <soCalled>minimal</soCalled>
<gi>front</gi> element without any need to group them together and
encode a complete title page.

<p>Encoders wishing to add new elements to either class may do so by
modifying or redefining this parameter entity, as further described in
chapter <ptr target=MD>.  Two examples of the use of these elements
follow.  First, the title page of the work discussed earlier in this
section:

<eg><![ CDATA[
  <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>
]]>
</eg>

<p>Second, a characteristically verbose 17th century example:
<eg><![ CDATA[
<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>
]]>
</eg>

<p>Those elements in the above list which are not defined elsewhere have
the following formal declarations:

<eg id=ddstpage>
<![ CDATA [
<!-- 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                        -->
]]>
</eg>


<!-- ornament and imprimat ought to go somewhere else, as     -->
<!-- they can occur outside the title page.  -->
<!-- Not sure that I agree about imprimat. It can't appear within -->
<!-- a div. It constitutes a kind of title page. So I propose to -->
<!-- leave it here. (LB)-->

<!-- ornament can      -->
<!-- occur anywhere and ought to be defined in PH or          -->
<!-- somewhere. left to fix later.  -msm                      -->

<!-- I agree;    (LB)                -->

<p>Where title pages are encoded, their physical rendition is
often of considerable importance.  One approach to this requirement
would be to use the <gi>seg</gi> tag, described in chapter <ptr
target=SA>, to segment the typographic content of each part of the
title page, and then use the global <att>rend</att> 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 <ptr target=PH>.


<p>Front matter elements are defined in a distinct DTD file
called <term>TEIfron2.dtd</term>.

<eg id=ddsfront>
<![ CDATA [
<!-- 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 ...                                          -->
]]>
</eg>


<div2 id=DSback><head>Back Matter</head>

<p>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
<gi>back</gi> and <gi>front</gi> elements are therefore identical.

<p>The following suggested values may be used for the <att>type</att>
attribute on all division elements, in order to distinguish various
kinds of division characteristic of back matter:
<list type=gloss>
<label><term>appendix</term><item>An ancillary self-contained section of
a work, often providing additional but in some sense extra-canonical
text.
<label><term>glossary</term>
<item>A list of terms associated with definition texts
(<q>glosses</q>): this should be encoded as a <gi>list type=gloss</gi>
(see section <ptr target=COli>).
<label><term>notes</term>
<item>A section in which textual or
other kinds of notes are gathered together.
<label><term>bibliogr</term>
<item>A list of bibliographic citations: this should be encoded
as a <gi>listBibl</gi> (see section <ptr target=CObi>).
<label><term>index</term>
<item>Any form of index to the work.
<label><term>colophon</term>
<item>A statement appearing at the end of a book describing the
conditions of its physical production.
</list>

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

<eg><![ CDATA[
<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>
]]>
</eg>
<!-- Smith, Wealth of Nations, 1776; index to vol 1 -->

<p>Next, a back-matter division in epistolary form:

<eg><![ CDATA[
<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>
]]>
</eg>
<!-- Greene, Groatsworth of witte, 1592 -->

<p>And finally, a list of corrigenda and addenda with pseudo-epistolary
features:

<eg><![ CDATA[
  <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&acirc;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>
]]>
</eg>
<!-- Pope, Dunciad Variorum, 1729 -->
<!--  end of draft -->

<p>The <gi>back</gi> element is defined in file
<term>TEIback2.dtd</term>; since there are no other specialized
back-matter tags, nothing else is defined there.

<eg id=ddsback>
<![ CDATA [
<!-- 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;                      >
]]>
</eg>


<!-- check filenames! -->

<div2 id=DSstruc><head>DTD Fragment for Default Text Structure</head>

<p>The DTD fragment described by the present chapter is found in file
<term>teistr2.dtd</term>; it has the following overall structure:

<eg id=dds>
<![ CDATA [
<!-- 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;
]]>
</eg>



<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
-->
            <!-- 7 Default structure -->
<!>
</div1>
