<!-- $Id: p2co.odd,v 1.8 1998/01/30 16:38:43 tei Exp $ -->
<!--*
    * $Log: p2co.odd,v $
    * Revision 1.8  1998/01/30 16:38:43  tei
    * fix Log keyword.
    *
    * Revision 1.7  1994/03/27 21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    *
    * Revision 1.6  1994/03/01  03:53:06  msmcq
    * suppress decls of pointer, xpointer :  these are now
    * att classes only, not model classes.  Add clloc decl.
    *-->
<!-- P2 chapter 23:  Tags Available in All TEI DTDs           -->
<!-- (id=p2.23, file=P223, mixed)                             -->
<!-- Revisions:                                               -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- 94-03-24 : MSM : typos, etc. from the proofreading team  -->
<!--                  suppress class decls, etc.:  these are  -->
<!--                  done in teiclas2.ent, and doing them    -->
<!--                  again in teicore2.dtd is only confusing -->
<!-- 94-02-28 : MSM : suppress pointer as *model* class       -->
<!-- 94-02-25 : MSM : suppress xpointer class for now         -->
<!-- 94-02-25 : MSM : Added RCS id                            -->
<!-- 93-12-20 : LDB : seg class has id clseg not seg          -->
<!-- 93-02-11 : MSM : loc class has id clloc not loc          -->
<!-- 92-12-10 : MSM : correct cladecl:  clbibl, not bibl      -->
<!-- 92-12-10 : MSM : revamp toplevel dtd frags               -->
<!-- 92-12-09 : MSM : touchup for publication                 -->
<!-- 92-12-06 : MSM : comment comi out                        -->
<!-- 92-12-06 : MSM : minor changes to text                   -->
<!-- 92-12-06 : MSM : exclude concurrent dtd from dtd         -->
<!-- 92-11-09 : MSM : set N on DIV                            -->
<!--                  add references to subparts              -->
<!--                  remove leading spaces in P elements     -->
<!-- 18-19 Oct 92 : LB :  revised slightly                    -->
<!--                      reordered pace Chicago  TRC         -->
<!-- 26 May 92 : CMSMcQ : add p2.23tag (LB ref crystals)      -->
<!-- 24 Apr 92 : CMSMcQ : add 23.e                            -->
<!-- 21 Apr 92 : CMSMcQ : made this file                      -->
<!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  -->
<!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->

<!-- changed name : Documents not dtds(LB) -->
<!-- changed name : elements not tags (LB) -->

<div1 n=6 type=Chapter id=CO><head>Elements Available in All TEI Documents</head>

<p>This chapter describes elements which may appear in any kind of text
and the tags used to mark them in all TEI documents.  Most of these
elements are freely floating phrases, which can appear at any point
within the textual structure, although they must generally be contained
by a higher-level element of some kind (such as a paragraph).  A few of
the elements described in this chapter (for example, bibliographic
citations and lists) have a comparatively well-defined internal
structure, but most of them have no consistent inner structure of their
own.  In the general case, they contain only a few words, and are often
identifiable in a conventionally printed text by the use of typographic
conventions such as shifts of font, use of quotation or other
punctuation marks, or other changes in layout.

<p>To use the terminology introduced in section <ptr target=STecov>,
most of the elements described in this chapter are members of the class
<ident type=class>phrase</ident>, and a small number are members of the
classes <ident type=class>chunk</ident> or
<ident type=class>inter</ident>.

<p>This chapter begins by describing the <gi>p</gi> tag used to mark
paragraphs, which serve as the fundamental formal unit for running text
in many base tag sets, and are available in all.  This is followed, in
section <ptr target=COpu>, by a discussion of some specific problems
associated with the interpretation of conventional punctuation, and the
methods proposed by the current Guidelines for resolving ambiguities
therein.

<p>The next section (section <ptr target=COhq>) describes a number of
phrase-level elements commonly marked by typographic features (and thus
well-represented in conventional markup languages).  These include
features commonly marked by font shifts (section <ptr
target=COhqh>) and features commonly marked by quotation marks (section
<ptr target=COhqq>) as well as such features as terms, cited
words, and glosses (section <ptr target=COhqu>).

<p>The next section (section <ptr target=COna>) describes several
phrase-level and inter-level elements which, although often of interest
for analysis or processing, are rarely explicitly identified in
conventional printing.  These include names (section <ptr type=div2
target=COnars>), numbers and measures (section <ptr type=div2
target=COnanu>), dates and times (section <ptr type=div2
target=COnada>), abbreviations (section <ptr type=div2 target=COnaab>),
and addresses (section <ptr target=COnaad>).

<p>Section <ptr target=COed> introduces some phrase-level elements
which may be used to record simple editorial emendation or correction of
the encoded text.  The tags described here constitute a simple subset of
the full mechanisms for encoding such information (described in full in
chapter <ptr target=PH>), which should be adequate to most commonly
encountered situations.

<!-- changed target from TC to PH -->

<p>In the same way, the following section (section <ptr target=COxr>)
presents only a subset of the facilities available for the encoding
of cross-references or text-linkage.  The full story may be found in
chapter <ptr target=SA>; the tags presented here are intended to
be usable for a wide variety of simple applications.

<p>Sections <ptr target=COli>, and <ptr target=COno>, describe two
kinds of quasi-structural elements, lists and notes, which may appear
either within chunk-level elements such as paragraphs, or between them.
Several kinds of lists are catered for, of an arbitrary complexity.  The
section on notes discusses both notes found in the source and simple
mechanisms for adding annotations of an interpretive nature during
the encoding; again, only a subset of the facilities described in full
elsewhere (specifically, in chapter <ptr target=AI>) is discussed.

<p>Next, section <ptr type=div2 target=COrs>, describes methods of
encoding within a text the conventional system or systems used when
making references to the text.  Some reference systems have attained
canonical authority and must be recorded to make the text useable in
normal work; in other cases, a convenient reference system must be
created by the creator or analyst of an electronic text.

<p>Like lists and notes, the bibliographic citations discussed in
section <ptr target=CObi>, may be regarded as structural elements in
their own right.  A range of possibilities is presented for the encoding
of bibliographic citations or references, which may be treated as
simple phrases within a running text, or as highly-structured
components suitable for inclusion in a bibliographic database.

<p>Additional elements for the encoding of passages of verse or drama
(whether prose or verse) are discussed in section <ptr target=COdv>.

<!-- , and a simple method of segmenting any kind of text     -->
<!-- into <soCalled>orthographic sentences</soCalled> is      -->
<!-- discussed in section <ptr target=COse>.                 -->

<p>The chapter concludes with a technical overview of the structure and
organization of the tag set described here. This should be read in
conjunction with chapter <ptr target=ST>, describing the structure of
the TEI document type definition.

<!-- moved overview of tagset structure to end of chapter -->


<!-- COpa Paragraphs (P1 5.3.1)                               -->
<!-- $Id: p2copa.odd,v 1.3 1994/03/27 21:45:15 msmcq Exp $ -->
<!-- $Log: p2copa.odd,v $
# Revision 1.3  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# -->
<!-- P2COpa : Paragraphs                                      -->
<!-- Revisions:                                               -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-25 : MSM : corrections from John Lavagnino         -->
<!-- 94-03-24 : MSM : disambiguation of term, q (null)        -->
<!-- 92-12-09 : MSM : cosmetic copy editing                   -->
<!-- 92-12-09 : MSM : add space after some end-tags           -->
<!-- 92-12-06 : MSM : revisions for publication               -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<!-- 17 oct 92 : LB  revised initial discussion               -->
<!-- 2 oct 92  : LB checked; revised order slightly           -->
<!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     -->
<!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  -->
<!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->

<div2 type=section id=COpa><head>Paragraphs</head>

<p>The paragraph is the fundamental organizational unit for all prose
texts, being the smallest regular unit into which prose can be divided.
Prose can appear in all TEI texts, not simply in those using the prose
base (section <ptr target=PR>); the paragraph is therefore described
here, as an element which can appear in any kind of text.

<p>Paragraphs can contain any of the other elements described within
this chapter, as well as some other elements which are specific to
individual text types.  We distinguish <term>phrase-level</term>
elements, which must be entirely contained within a paragraph and cannot
appear except within one, from <term>chunks</term>, which can appear
between, but not within, paragraphs, and from <term>inter-level</term>
elements, which can appear either within a single paragraph or between
paragraphs.  The class of phrases includes emphasized or quoted phrases,
names, dates, etc.  The class of inter-level elements includes
bibliographic citations, notes, lists, etc.  The class of chunks
includes the paragraph itself.

<p>Because paragraphs may appear in different base or additional tag
sets, their possible contents may differ in different kinds of
documents.  In particular, additional elements not listed in this
chapter may appear in paragraphs in certain kinds of text.  However, the
elements described in this chapter are always by default available in
all kinds of text.

<p>The paragraph is marked using the <gi>p</gi> element:

<list type=gloss>
<label><gi>p</gi></label>
<item>marks paragraphs in prose.</item>
</list>


<p>If a consistent internal subdivision of paragraphs is desired, the
<gi>s</gi> or <gi>seg</gi> (<soCalled>segment</soCalled>) elements may
be used, as discussed in chapters <ptr target=SA> and <ptr target=AI>
respectively.  More usually, however, paragraphs have no firm internal
structure, but contain prose encoded as a mix of characters, entity
references, phrases marked as described in the rest of this chapter, and
embedded elements like lists, figures, or tables.

<p>Since paragraphs are usually explicitly marked in Western texts,
typically by indentation,  the application of the <gi>p</gi> tag
usually presents few problems.

<p>In some cases, the body of a text may comprise but a single
paragraph:

<eg>
<![ CDATA [
<body>
<p>I fully appreciate Gen. Pope's splendid achievements with their
invaluable results; but you must know that Major Generalships in the
Regular Army, are not as plenty as blackberries.
</body>
]]>
</eg>

<!-- A. Lincoln to Richard Yates and William Butler, 10 Apr 1862, -->
<!-- Library of America, Lincoln, v. 2 p. 315.                -- >

<p>This news story shows typically short journalistic paragraphs:

<eg>
<![ CDATA [
<head>SARAJEVO, Bosnia and Herzegovina, April 19</head>
<p>Serbs seized more territory in this struggling new
country today as the United States Air Force ended a
two-day airlift of humanitarian aid into the capital,
Sarajevo.
<p>International relief workers called on European
Community nations to step up their humanitarian aid to
the former Yugoslav republic, in conjunction with new
American aid flights if necessary.
<p>A special envoy from the European Community, Colin
Doyle, harshly condemned the decision by Serbs to shell
Sarajevo on Saturday night during a visit to the Bosnian
capital by a senior American official, Deputy Assistant
Secretary of State Ralph R. Johnson.
<p>...
]]>
</eg>

<p>The following extract from a Russian fairy tale demonstrates
how other phrase level elements (in this case <gi>q</gi> elements
representing direct speech; see section <ptr target=COhqq>)
may be nested within, but not across, paragraphs:

<!-- < bibl>< title>Russian Fairy Tales,< /title>         -->
<!-- translated by Norbert Guterman from the collections of   -->
<!-- Aleksandr Afanas'ev, illustrations by Alexander          -->
<!-- Alexeieff, folkloristic commentary by Roman Jakobson     -->
<!-- (New York:  Pantheon Books, 1947, rpt.  [n.d.]).< />     -->
<!-- opening paragraphs of < title>The Castle of the        -->
<!-- Fly< /title>, p. 25                                    -->

<!-- WWP proofer objects to the fact that "I, the             -->
<!-- Languishing Fly, and I the Crawling Louse" makes only    -->
<!-- one Q element instead of two.  Though not perfectly      -->
<!-- logical, this is the structure indicated by the          -->
<!-- punctuation of the source text, so the example was not   -->
<!-- changed.  (msm)                                          -->

<eg>
<![ CDATA [
<p>A fly built a castle, a tall and mighty castle.
There came to the castle the Crawling Louse.  <q>Who,
who's in the castle?  Who, who's in your house?</q>
said the Crawling Louse.  <q>I, I, the Languishing Fly.
And who art thou?</q> <q>I'm the Crawling Louse.</q>

<p>Then came to the castle the Leaping Flea.  <q>Who,
who's in the castle?</q> said the Leaping Flea.  <q>I,
I, the Languishing Fly, and I, the Crawling Louse.  And
who art thou?</q> <q>I'm the Leaping Flea.</q>

<p>Then came to the castle the Mischievous Mosquito.
<q>Who, who's in the castle?</q> said the Mischievous
Mosquito.  <q>I, I, the Languishing Fly, and I, the
Crawling Louse, and I, the Leaping Flea.  And who art
thou?</q> <q>I'm the Mischievous Mosquito.</q>
]]>
</eg>

<p>The <gi>p</gi> element is formally declared as follows:
<eg id=dcopa>
<![ CDATA [
<!-- 6.1:  Paragraph                                          -->
<!ELEMENT p             - O  (%paraContent;)                    >
<!ATTLIST p                  %a.global;                         >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>




<!-- COpu Ambiguous Punctuation                               -->
<!-- $Id: p2copu.odd,v 1.4 1994/03/27 21:45:15 msmcq Exp $ -->
<!-- $Log: p2copu.odd,v $
# Revision 1.4  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# -->
<!-- Revisions:                                               -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-26 : MSM : corrections from DB                     -->
<!-- 94-03-25 : MSM : corrections from JL                     -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- 14 mar 94 : change ref to AIse to point to SAse -->
<!-- 2 jan 94: LB: change title following DTL, provide hook for PAREN -->
<!-- 92-12-09 : MSM : cosmetic copy editing                   -->
<!-- 92-12-09 : MSM : bring remark about SHY into text        -->
<!-- 92-12-09 : MSM : add space after some end-tags           -->
<!-- 92-12-09 : MSM : add reference to teipunc2               -->
<!-- 92-12-06 : MSM : correct typo                            -->
<!-- 92-12-06 : MSM : revise for publication                  -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<!-- 5 Oct 92  : LB made new file from old P223d; redo IDs   -->

<div2 id=COpu><head>Treatment of Punctuation</head>

<p>Punctuation marks cause problems for text markup because they may
not be available in the character set used and because they are often
ambiguous.  In the former case entity names should be used to render
the punctuation mark (see <ptr type=div1 target=CH>).  In the latter
case, ambiguous punctuation may be treated as described below.

<p><term rend='noindex'>Full stop (period)</term>
<index level1='full stop' level2='functions'>
<index level1='period' level2='functions'>
may mark (orthographic) sentence boundaries, abbreviations, decimal
points, or serve as a visual aid in printing numbers.  These usages can
be distinguished by tagging S-units, abbreviations, and numbers, as
described in sections <ptr target=SAse>, <ptr target=COnaab>, and
<ptr target=COnanu>.  There are independent reasons for tagging these,
whether or not they are marked by full stops.  Alternatively, the
following TEI-specific entity names may be used to distinguish stops
(and other characters) used for these purposes:

<list type=gloss>
<label>stop.abbr <item>a stop used to end an abbreviation
<label>stop.sent <item>a stop used to end a sentence
<label>stop.abse <item>a stop used both to end an abbreviation
                        and to end a sentence
<label>stop.dec  <item>a stop used as a decimal point
<label>comma.dec <item>a comma used as a decimal point
<label>middot.dec <item>a midline dot used as a decimal point
<label>stop.space <item>a stop used as a numeric space character
<label>comma.space <item>a comma used as a numeric space character
</list>

These entities are defined in the file <ident
type='file'>teipunc2</ident>, which is documented in chapter <ptr
target=XW>.

<p><term rend='noindex'>Question mark</term>
<index level1='question mark' level2='functions'>
and <term rend='noindex'>exclamation mark</term>
<index level1='exclamation mark' level2='functions'>
typically mark the end of orthographic sentences, but may also be used
as a mid-sentence comment by the author (<mentioned>!</mentioned> to express
surprise or some other strong feeling, <mentioned>?</mentioned> to query a word
or expression or mark a sentence as dubious in linguistic discussion).
These uses may be distinguished by marking S-units, in which case the
mid-sentence uses of these punctuation marks may be left unmarked.

<p><term rend='noindex'>Hyphens</term>
<index level1='hyphen' level2='functions'>
<index level1='hyphen' level2='soft and hard'>

at line-end may or may not indicate permanent
(<soCalled>hard</soCalled>) hyphens in the word.  Where the lineation of
the machine-readable text differs from the original, the editor may
eliminate soft (line-end) hyphens or replace them by a reference to the
entity <ident type=ge>shy</ident> (<soCalled>soft hyphen</soCalled>),
which is defined in the standard public entity set <ident
type=entset>ISOnum</ident> defined in ISO 8879 (which should be
invoked in the DTD subset
if the entity <ident type=ge>shy</ident> is to be used).  The solution
chosen should be reported in the <tag>hyphenation</tag> tag of the
encoding declarations in the TEI header.  See chapter <ptr type=div1
target=HD> for discussion of the TEI header and encoding declarations.

<p>Creators of machine-readable texts are recommended to avoid soft
hyphens, as one cannot tell whether the hyphens are soft or hard in the
case of compounds or prefixed words which might or might not be
hyphenated in mid-sentence.

<p><term rend='noindex'>Dashes</term>
<index level1='dash' level2='functions'>
are best distinguished in form by using the entity names provided in the
public entity set <ident type=entset>ISOpub</ident>, defined in ISO
8879:  <ident type=ge>mdash</ident>, <ident type=ge>ndash</ident>, and
<ident type=ge>dash</ident> (the <soCalled>true</soCalled> hyphen).
Dashes are used for a variety of purposes:  insertion, interruption, new
speaker (in dialogue), list item.  In the latter two cases it is
preferable to mark the underlying feature using the elements
<tag>q</tag> or <tag>item</tag>, on which see section <ptr type=div2
target=COhqq>, and section <ptr type=div2 target=COli>, respectively.

<p><term rend='noindex'>Quotation marks</term>
<index level1='quotation marks' level2='functions'>
should generally be replaced by the tags <tag>q</tag> or
<tag>quote</tag>, especially as quotations are not always marked by
quotation marks (notably long quotations) or may be marked in a variety
of ways; see the discussion of quotation and related features in section
<ptr type=div1 target=COhqq>.

<p><term rend='noindex'>Apostrophes</term>
<index level1='apostrophe' level2='functions'>
must be distinguished from single quote marks.  This is best done by
tagging quotations or other uses of quotation marks (see above).
However, apostrophes have a variety of uses.  In English they mark
contractions, genitive forms, and (occasionally) plural forms.  Full
disambiguation of these uses belongs to the level of linguistic analysis
and interpretation.

<p><term rend='noindex'>Parentheses</term>
<index level1='parentheses' level2='functions'>
and other marks of suspension such as dashes or ellipses are often used
to signal information about the syntactic structure of a text fragment.
Full disambiguation of their uses also belongs to the level of
linguistic analysis and interpretation, and is therefore discussed in
chapter <ptr target=AI>.

<!-- could point to paren element here? -->

<p>Where punctuation marks are disambiguated by tagging the underlying
feature they signal, it may be debated whether they should be excluded
or left as part of the text.  In the case of quotation marks, it may
sometimes be more convenient to distinguish opening from closing marks
simply by using the appropriate entity reference, rather than using the
<gi>q</gi> element, with or without a <att>rend</att> attribute.  The
solution chosen will vary depending upon the feature and depending upon
the purpose of the project.



<!-- COhq Highlighting and Related Features (P1 5.3.2,5.3.4)  -->
<!-- $Id: p2cohq.odd,v 1.3 1994/03/27 21:45:15 msmcq Exp $ -->
<!-- $Log: p2cohq.odd,v $
# Revision 1.3  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# -->

<div2 id=COhq><head>Highlighting and Quotation</head>

<!-- Revisions:                                               -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-26 : MSM : corrections from DB                     -->
<!-- 94-03-25 : MSM : typos corrected as per J. Lavagnino     -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- 92-12-10 : MSM : change xref to SP (now TS)              -->
<!-- 92-12-09 : MSM : retag new citn using toy tag, not new tag -->
<!-- 92-12-09 : MSM : spellcheck for publication              -->
<!-- 92-12-09 : MSM : touchups for publication                -->
<!-- 92-12-09 : MSM : add space after some end-tags           -->
<!-- 92-12-09 : MSM : fixes as per LB, MSM agreements         -->
<!-- 92-12-07 : MSM : suppress Q/Free attribute               -->
<!-- 92-12-07 : MSM : correct syntax error in OED gloss       -->
<!-- 92-12-07 : MSM : come down handsomely with OED citation  -->
<!-- 92-12-06 : MSM : revise for publication                  -->
<!-- 92-11-09 : MSM : retag two EGs as Qs                     -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<!-- 25-7 Oct  LB : introduce quote, reorder                  -->
<!-- 19 Oct 92 LB : change ids to match EDW23                 -->
<!--           changed marked to distinct                     -->
<!-- 26 May 92 : MSM : fix div levels                         -->
<!-- 15 May 92 : LB : finish, check out to MSM                -->

<p>This section deals with a variety of textual features, all of
which have in common that they are frequently realized in conventional
printing practice by the use of such features as underlining, italic
fonts, or quotation marks, collectively referred to here as
<term>highlighting</term>.  After an initial discussion of this
phenomenon and alternate approaches to encoding it, this section
describes ways of encoding the following textual features, all
of which are conventionally rendered using some kind of highlighting:
<list>
<item>emphasis, foreign words and other linguistically distinct uses
of highlighting
<item>representation of speech and thought, quotation, etc.
<item>technical terms, glosses, etc.
</list>

<div3 id=COhqw><head>What Is Highlighting?</head>

<p>By <mentioned>highlighting</mentioned> we mean the use of any combination of
<index level1='highlighting'> typographic features (font, size, hue,
etc.) in a printed or written text in order to distinguish some passage
of a text from its surroundings.<note>Although the way in which a spoken
text is performed, (for example, the voice quality, loudness, etc.)
might be regarded as analogous to <soCalled>highlighting</soCalled> in
this sense, these Guidelines recommend distinct elements for the
encoding of such <socalled>highlighting</socalled> in spoken texts.  See
further section <ptr target=TSsash>.</note> The purpose of highlighting
is generally to draw the reader's attention to some feature or
characteristic of the passage highlighted; this section describes the
elements recommended by these Guidelines for the encoding of such
textual features.

<p>In conventionally printed modern texts, highlighting is often
employed to identify words or phrases which are regarded as being one or
more of the following:

<list type=bullets>
<item>distinct in some way --- as foreign, dialectal,
archaic, technical, etc.
<item>emphatic, and which would for example be stressed when spoken
<item>not part of the body of the text, for example cross references,
titles, headings, labels, etc.
<item>identified with a distinct narrative stream, for example an
internal monologue or commentary.
<item>attributed by the narrator to some other agency, either within the
text or outside it:  for example, direct speech or quotation.
<item>set apart from the text in some other way:  for example,
proverbial phrases, words mentioned but not used, names of persons and
places in older texts, editorial corrections or additions, etc.
</list>

<p>The textual functions signalled by highlighting may not be rendered
consistently in different parts of a text or in different texts.  (For
example, a foreign word may appear in italics if the surrounding text is
in roman, but in roman if the surrounding text is in italics.)  For this
reason, these Guidelines distinguish between the encoding of rendering
itself and the encoding of the underlying feature expressed by it.

<p>Highlighting as such may be encoded by using the global
<att>rend</att> attribute which can be specified for any element in the
TEI scheme.  This allows the encoder both to specify the function of a
highlighted phrase or word, by selecting the appropriate element
described here or elsewhere in the Guidelines, and to further describe
the way in which it is highlighted, by means of the <att>rend</att>
attribute.  If the encoder wishes to offer no interpretation of the
feature underlying the use of highlighting in the source text, then the
<gi>hi</gi> element may be used, which indicates only that the text so
tagged was highlighted in some way.

<p>The possible values carried by the <att>rend</att> attribute are not
formally defined in this version of the Guidelines.  Since the
<att>rend</att> attribute may be used to document any peculiarity of the
way a given segment of text was rendered in the original source text, it
may need to express a very large range of typographic features, by no
means restricted to type face, type size, etc.

<!-- For more discussion see the chapter on physical          -->
<!-- rendition (section <ptr target=PH>).                    -->

<p>Where it is both appropriate and feasible, these Guidelines recommend
that the textual feature marked by the highlighting should be encoded,
rather than just the simple fact of the highlighting.  This is for the
following reasons:

<list>
<item>the same kind of highlighting may be used for different purposes
in different contexts
<item>the same textual function may be highlighted in different ways in
different contexts
<item>for analytic purposes, it is in general more useful to know the
intended function of a highlighted phrase than simply that it is
distinct.
</list>

<p>In many, if not most, cases the underlying function of a highlighted
phrase will be obvious and non-controversial, since the distinctions
indicated by a change of highlighting correspond with distinctions
discussed elsewhere in these Guidelines.  It should be recognized,
however, that cases do exist in which is it not economically feasible to
mark the underlying function of highlighting (e.g. in the preparation of
large text corpora), as well as cases in which it is not intellectually
appropriate (as in the transcription of some older materials, or in the
preparation of material for the study of typographic practice).  In such
cases, the <gi>hi</gi> element should be used, as further discussed
below.

<p>Elements which are sometimes realized by typographic distinction but
which are not discussed in this section include <gi>title</gi>
(discussed in section <ptr target=CObi>) and <gi>name</gi> (discussed
in section <ptr target=COnars>).

<div3 id=COhqh><head>Emphasis, Foreign Words, and Unusual Language</head>

<p>This subsection discusses the following elements:

<list type=gloss>
<label><gi>foreign</gi></label>
<item>identifies a word or phrase as belonging to some language 
other
than that of the surrounding text. 
Attributes include:
<list type=gloss>
<label><att>lang</att></label>
<item>identifies the language of the word or phrase marked.</item>
</list>
</item>
<label><gi>emph</gi></label>
<item>marks words or phrases which are stressed or emphasized for
linguistic or rhetorical effect.</item>
<label><gi>hi</gi></label>
<item>marks a word or phrase as graphically distinct from the

surrounding text, for reasons concerning which no claim is 
made. 
Attributes include:
<list type=gloss>
<label><att>rend</att></label>
<item>describes the rendition or presentation of the word or 
phrase highlighted.</item>
</list>
</item>
<label><gi>distinct</gi></label>
<item>identifies any word or phrase which is regarded as 
linguistically
distinct, for example as archaic, 
technical, dialectal, non-preferred,
etc., or as forming 
part of a sublanguage. 
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>specifies the sublanguage or register to which the word or 
phrase is being assigned</item>
<label><att>time</att></label>
<item>specifies how the phrase is distinct diachronically</item>
<label><att>space</att></label>
<item>specifies how the phrase is distinct diatopically</item>
<label><att>social</att></label>
<item>specifies how the phrase is distinct diastatically</item>
</list>
</item>
</list>


<div4 id=COhqhf><head>Foreign Words or Expressions</head>

<p>Words or phrases which are not in the main language of the text
should be tagged as such, at least where the fact is indicated in the
text.  Where the word or phrase concerned is already distinguished from
the rest of the text by virtue of its function (for example, because it
is a name, a technical term, a quotation, a mentioned word, etc.) then
the global <att>lang</att> attribute should be used to specify
additionally that its language distinguishes it from the surrounding
text.  Any element in the TEI scheme may take a <att>lang</att>
attribute, which specifies both the writing system and the language used
by its content (see section <ptr target=CHsh> for discussion of this
attribute).  Where there is no other applicable element, the tag
<tag>foreign</tag> may be used to provide a peg onto which the
<att>lang</att> may be attached.

<eg> <![CDATA[
<q>Aren't you confusing <foreign lang=la>post hoc</foreign>
with <foreign lang=la>propter hoc</foreign>?</q> said the
Bee Master.  <q>Wax-moth only succeed when weak bees let
them in.</q>
]]>
</eg>
<!-- R Kipling 'The mother hive' in Actions and Reactions, 1909 -->
<!-- these could be tagged as TERM, of course. -MSM -->

<p>The <tag>foreign</tag> tag should not be used to encode foreign words
which are mentioned or glossed within the text:  for these use the
appropriate element from section <ptr target=COhqu> below.  Compare the
following example sentences:

<eg> <![ CDATA [
John eats a <foreign lang=fr>croissant</foreign> every morning.
]]>
</eg>

<eg> <![ CDATA [
<mentioned lang=fr>Croissant</mentioned> is difficult to
pronounce with your mouth full.
]]>
</eg>

<eg> <![ CDATA [
A <term lang=fr>croissant</term> is a crescent-shaped piece
of light, buttery, pastry that is usually eaten for
breakfast, especially in France.
]]>
</eg>

<!-- Collins COBUILD English Language Dictionary, ed. John    -->
<!-- Sinclair (London and Glasgow:  Collins, 1987), p. 337    -->
<!-- s.v. croissant.                                          -->

<p>The <gi>foreign</gi> element is formally defined as follows:

<eg id=dcohq>
<![ CDATA [
<!-- 6.3.2.1:  Highlighted phrases                            -->
<!ELEMENT foreign       - -  (%paraContent;)                    >
<!ATTLIST foreign            %a.analysis;
                             %a.linking;
                             %a.terminology;
          id                 ID                  #IMPLIED
          rend               CDATA               #IMPLIED
          n                  CDATA               #IMPLIED
          lang               IDREF               #IMPLIED       >
<!-- (continued in sec. 6.3.2.2, 6.3.2.3, 6.3.3, 6.3.4)       -->
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>


<div4 id=COhqhe><head>Emphatic Words and Phrases</head>

<p>The <gi>emph</gi> element is provided to mark words or phrases which
are <emph>linguistically</emph> emphatic or stressed.  Text which is
only typographically <soCalled>emphasized</soCalled> falls into the
class of highlighted text, and may be tagged with the <gi>hi</gi>
element.  In printed works, emphasis is generally indicated by devices
such as the use of an italic font, a large typeface or extra wide letter
spacing; in manuscripts and typescripts, it is usually indicated by the
use of underlining.

As the following examples demonstrate, an encoder may choose whether or
not to make explicit the particular type of rendition associated with
the emphasis, by use of the <att>rend</att> attribute.  If a source text
consistently renders a particular feature (e.g. emphasis or words in
foreign languages) in a particular way, the rendering associated with
that feature may be described in the TEI header and the <att>rend</att>
attribute used only to describe examples which deviate from the norm.

<eg><![ CDATA [
<q>Sex, sir, is <emph>purely</emph> a question of appetite!</q>
   Tarr exclaimed.
]]>
</eg><!-- Wyndham Lewis, Tarr (1928), Jupiter ed 1968, p.17 -->

<eg><![ CDATA [
<q>What it all comes to is this,</q> he said.
<q><emph rend=italic>What does Christopher
Robin do in the morning nowadays?</emph></q>
]]>
</eg><!-- Milne, House at Pooh Corner (1928), p83 -->

<eg><![ CDATA [
<l>Here Thou, great <name rend=italics>Anna</name>!
      whom three Realms obey,
<l>Doth sometimes Counsel take &mdash;
      and sometimes <emph rend=italic>Tea</emph>.
]]>
</eg><!-- Pope, Rape of the Lock (1744) III.8 -->

<p>The <gi>hi</gi> element is used to mark words or phrases which are
highlighted in some way, but for which identification of the intended
distinction is difficult, controversial or impossible.  It enables an
encoder simply to record the fact of highlighting, possibly describing
it by the use of a <att>rend</att> attribute, as discussed above,
without however taking a position as to the function of the
highlighting.  This may also be useful if the text is to be processed in
two stages:  representing simply typographic distinctions during a first
pass, and then replacing the <tag>hi</tag> tags with more specific tags
in a second pass.

<p>Some simple examples:

<eg><![ CDATA [
<hi rend=gothic>And this Indenture further witnesseth</hi>
that the said <hi rend=italic>Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...
]]>
</eg><!-- Sterne, Tristram Shandy (1760), p.82 -->

In this example, the first highlighted phrase uses black letter or
gothic print to mimic the appearance of a legal document, and italic to
mark <mentioned>Walter Shandy</mentioned> as a name.  In a second pass, the
elements <gi>head</gi> or <gi>label</gi> might be appropriate for the
first use, and the element <gi>name</gi> for the second.

<eg><![ CDATA [
The heaviest rain, and snow, and hail, and sleet, could
boast of the advantage over him in only one respect.  They
often <hi rend=quoted>came down</hi> handsomely, and
Scrooge never did.
]]>
</eg><!-- Dickens Xmas Carol  p 12 -->

In this example, the phrase <mentioned>came down</mentioned> uses inverted
commas to indicate a play on words.<note>The Oxford English Dictionary
documents the phrase <mentioned>to come down</mentioned> in the sense <gloss>to
bring or put down; <hi rend=it>esp.</hi> to lay down money; to
make a disbursement</gloss> as being in use, mostly in colloquial or
humorous contexts, from at least 1700 to the latter half of the 19th
century.
<!-- In early Victorian English slang,                        -->
<!-- < q >to come down handsomely< / q >                      -->
<!-- might be glossed as < q >to pay out                      -->
<!-- handsomely< / q >.                                       -->
</note>
<!-- a ref to OED would be handy here if you have time to find one -->
In a second pass, the element <gi>soCalled</gi> might be preferred.

<!-- WWP proofer asks why. (msm)                              -->

<p>The <gi>emph</gi> and <gi>hi</gi> elements are formally defined as
follows:

<eg id=dcohq1>
<![ CDATA [
<!-- 6.3.2.2:  Highlighted phrases (cont'd)                   -->
<!-- (continuation of sec. 6.3.2.1)                           -->
<!ELEMENT emph          - -  (%paraContent;)                    >
<!ATTLIST emph               %a.global;                         >
<!ELEMENT hi            - -  (%paraContent;)                    >
<!ATTLIST hi                 %a.analysis;
                             %a.linking;
                             %a.terminology;
          id                 ID                  #IMPLIED
          lang               IDREF               %INHERITED
          n                  CDATA               #IMPLIED
          rend               CDATA               #IMPLIED       >
]]>
</eg>


<div4 id=COhqhd><head>Other Linguistically Distinct Material</head>

<p>For some kinds of analysis, it may be desirable to encode the
linguistic distinctiveness of words and phrases with more delicacy than
is allowed by the <gi>foreign</gi> element.  The <gi>distinct</gi>
element is provided for this purpose.  Its attributes allow for
additional information characterizing the nature of the linguistic
distinction to be made in two distinct ways:  the <att>type</att>
attribute simply assigns a user-defined code of some kind to the word or
phrase which assigns it to some register, sub-language, etc.  No
recommendations as to the set of values for this attribute are provided
at this time, as little consensus exists in the field.

<p>Alternatively, the remaining three attributes may be used in
combination to place a word or phrase on a three-dimensional scale
sometimes used in descriptive linguistics.<note>See, for example,
<bibl><title>Sociolinguistics/Soziolinguistik (An international
handbook of the science of language and society.  Ein internationales
Handbuch zur Wissenschaft von Sprache und Gesellschaft)</title> (Berlin,
New York:  De Gruyter, 1988), I, pp. 271 and 274.</bibl></note>
The <att>time</att> attribute places a word
<term rend='noindex'>diachronically</term>,
<index level1='diachronic information'>
for example as archaic, old-fashioned, contemporary, futuristic, etc.;
the <att>space</att> attribute places a word
<term rend='noindex'>diatopically</term>,
<index level1='diatopic information'>
that is, with respect to a geographical classification, for example as
national, regional, international, etc.; the <att>social</att> attribute
places a word <term rend='noindex'>diastatically</term>,
<index level1='diastatic information'>
that is, with respect to a social classification, for example as
technical, polite, impolite, restricted, etc.  Again, no recommendations
are made for the values of these attributes at this time; the encoder
should provide a description of the scheme used in the appropriate
section of the header (see section <ptr target=HD5>).

<p>Examples:

<eg><![ CDATA [
Next morning a boy in that dormitory confided to his
bosom friend, a <distinct type=psSlang>fag</distinct> of
Macrea's, that there was trouble in their midst which
King <distinct type=archaic>would fain</distinct> keep
secret.
]]>
</eg><!-- Kipling, Stalky & Co. (1899), Library ed 1950, p.83) -->

<eg><![ CDATA[
Next morning a boy in that dormitory confided to his
bosom friend, a
<distinct time=1900 social=publicschool space=GB>fag</distinct>
of Macrea's, that there was trouble in their midst which
King <distinct time=archaic>would fain</distinct> keep
secret.
]]>
</eg>

Where more complex (or more rigorous) interpretive analyses of the
associations of a word are required, the more detailed and general
mechanisms described in chapter <ptr target=FS> should be preferred to
these simple characterizations.  It may also be preferable to record the
kinds of analysis suggested here by means of the simple annotation
element <gi>note</gi> described in section <ptr target=COno>, or the
<gi>span</gi> element described in section <ptr target=AIsp>.

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

<eg id=dcohq3>
<![ CDATA [
<!-- 6.3.2.3:  Highlighted phrases (cont'd)                   -->
<!-- (continuation of sec. 6.3.2.1)                           -->
<!ELEMENT distinct      - -  (%phrase.seq;)                     >
<!ATTLIST distinct           %a.global;
          social             CDATA               #IMPLIED
          space              CDATA               #IMPLIED
          time               CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
]]>
</eg>


<!>
<!-- P2, ch 23, sec 7.                                        -->
<!-- Revisions:                                               -->
<!-- 19 Oct 92 : LB change xrefs and div levels again        -->
<!-- 26 May 92 : MSM : fix div levels                         -->
<!-- 15 May 92 : LB : check out to MSM                        -->

<div3 id=COhqq><head>Quotation</head>

<p>This section discusses the following elements, all of which are often
rendered by the use of quotation marks:

<list type=gloss>
<label><gi>q</gi></label>
<item>contains a quotation or apparent quotation --- a 
representation of
speech or thought marked as being quoted 
from someone else (whether in
fact quoted or not); in 
narrative, the words are usually those of of a
character 
or speaker; in dictionaries, <gi>q</gi> may be used to mark
real or contrived examples of usage.
Attributes include:
<list type=gloss>
<label><att>who</att></label>
<item>identifies the speaker of a piece of direct speech.</item>
<label><att>type</att></label>
<item>may be used to indicate whether the quoted matter is spoken 
or thought, or to characterize it more finely.
Sample values include:
<list type=gloss>
<label><term>spoken</term></label>
<item>representation of direct speech, usually marked by 
quotation marks.</item>
<label><term>thought</term></label>
<item>representation of thought, e.g. internal monologue.</item>
</list></item>
<label><att>direct</att></label>
<item>may be used to indicate whether the quoted matter is 
regarded as direct or indirect speech.
Legal values are:
<list type=gloss>
<label><term>y</term></label>
<item>speech or thought is represented directly.</item>
<label><term>n</term></label>
<item>speech or thought is represented indirectly, e.g. by use of 
a marked verbal aspect.</item>
<label><term>unspecified</term></label>
<item>no claim is made.</item>
</list></item>
</list>
</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>
<label><gi>cit</gi></label>
<item>A quotation from some other document, together with a 
bibliographic
reference to its source.</item>
<label><gi>soCalled</gi></label>
<item>contains a word or phrase for which the author or narrator

indicates a disclaiming of responsibility, for example by 
the use
of scare quotes or italics.</item>
</list>


<p>One form of presentational variation found particularly frequently in
written and printed texts is the use of quotation marks.  As with the
typographic variations discussed in the preceding section, it is
generally helpful to separate the encoding of the underlying textual
feature (for example, a quotation or a piece of direct speech) from the
encoding of its rendering (for example, the use of a particular style of
quotation marks).

<p>The most common and important use of quotation marks is, of course,
to mark <term>quotation</term>, by which we mean simply any part of the
text attributed by the author or narrator to some agency other than the
narrative voice.  Typical examples include passages cited from other
works, for which the element <gi>quote</gi> may be used, and words or
phrases attributed to other voices within the current work, for which
the element <gi>q</gi> may be used.  If this distinction between
intra-textual and inter-textual voices cannot be made reliably, or is
not of interest, then all quoted matter may simply be marked using the
<gi>q</gi> tag.  The editorial policy in this respect should be stated
in the encoding description of the TEI Header.  The <gi>soCalled</gi>
element is used for cases where the author or narrator distances him or
herself from the words in question without however attributing them to
any other voice in particular.

<!-- The following discussion of rendering seems rather long-winded -->
<!-- to me, but I am not sure where else it goes. Maybe some of it  -->
<!-- should migrate to PH?                                          -->

<p>Quotation may be rendered by changes in type face, by special
punctuation marks (single or double or angled quotes, dashes, etc.) and
by layout (indented paragraphs, etc.).  If these characteristics are of
interest, an appropriate value for the <att>rend</att> attribute should
be given, to record how the <gi>q</gi> or <gi>quote</gi> element is
rendered.  For discussion of suggested values for this attribute, see
below.

<!-- , and also chapter <ptr target=PH>.                     -->

<p>Quotation marks themselves may, like other punctuation marks, be felt
for some purposes to be worth retaining within a text, quite
independently of their description by the <att>rend</att> attribute.
Where this is done, an appropriate entity reference should be chosen
from the standard entity sets listed in chapter <ptr target=XW>;
<!-- not sure if this is the right target: somewhere we should -->
<!-- reference the standard entity sets -->
this has the advantage that the entity may be redefined as null when the
punctuation is to be ignored for some analytic purpose.  Well-known
ambiguities, such as whether the character ' represents an apostrophe or
a closing single quotation mark, or whether the character " represents
an opening or closing double quotation mark may all be resolved by the
use of appropriate entity references, as discussed in section <ptr
target=COpu>.
<!-- This is not true.                                        -->

<p>Alternatively, the encoder may suppress all quotation marks, possibly
recording their form using the <att>rend</att> attribute.  Where this is
done, the following list of entity names (taken from the public entity
sets <ident type=entset>ISOpub</ident> and <ident
type=entset>ISOnum</ident>) may be found useful to describe
quotation-mark styles common in European and American typesetting:

<!-- list restored under (mild) protest and with one necessary  -->
<!-- addition                                     LB, oct 92    -->

<list type=gloss>
<label>ldquo  <item>double inverted comma (shaped like 66, superscript)
<label>lsquo  <item>single inverted comma (shaped like 6, superscript)
<label>rdquo  <item>double apostrophe (shaped like 99, superscript)
<label>rsquo  <item>single apostrophe (shaped like 9, superscript)
<label>ldquor <item>double comma (shaped like 99, printed on base line)
<label>lsquor <item>single comma (shaped like 9, printed on base line)
<label>laquo  <item>double guillemet open to the right
<label>lsaquo <item>single guillemet open to the right
<label>raquo  <item>double guillemet open to the left
<label>rsaquo <item>single guillemet open to the left
<label>mdash  <item>dash the width of a lowercase <mentioned>m</mentioned>
</list>

<!-- J.Lavagnino suggests revisiting the issue of mdash in    -->
<!-- P4:  perhaps this is too print-centered?  (msm)          -->

These may be used in the <att>rend</att> attribute to show how the
quotation was opened and closed.  For example, if the words
<mentioned>pre</mentioned> and <mentioned>post</mentioned> are used to indicate
preceding and following punctuation, then the following example would
describe a conventional American book printed using single quotation
marks:

<eg>
<![ CDATA [
<q rend='PRE lsquo POST rsquo'>Who-e debel you?</q>
&mdash he at last said &mdash <q
rend='PRE lsquo POST rsquo'>you no speak-e,
damme, I kill-e.</q>  And so saying,
the lighted tomahawk began flourishing
about me in the dark.
]]>
</eg><!-- Melville, Moby Dick (but where?) -->

The following example demonstrates alternative policies which may be
adopted with respect to encoding of the punctuation used to mark
quotation:

<eg>
<![ CDATA[

Adolphe se tourna vers lui :
<q>&mdash Alors, Albert, quoi de neuf?</q>
<q>&mdash Pas grand-chose.</q>
<q>&mdash Il fait beau,</q> dit Robert.
]]>
</eg><eg>
<![ CDATA[

Adolphe se tourna vers lui :
<q rend='PRE mdash'>Alors, Albert, quoi de neuf ?</q>
<q rend='PRE mdash'>Pas grand-chose.</q>
<q rend='PRE mdash'>Il fait beau,</q> dit Robert.
]]>
</eg><!-- Queneau, Exercices de style (1947) p.192 -->

To make explicit who is speaking, which is not always stated in the
above example, the <att>who</att> attribute should be used:

<eg>
<![ CDATA [
Adolphe se tourna vers lui :
<q who='Adolphe'>&mdash Alors, Albert, quoi de neuf?</q>
<q who='Albert'>&mdash Pas grand-chose.</q>
<q who='Robert'>&mdash Il fait beau,</q> dit Robert.
]]>
</eg>
<!-- should show QUOTATION declarations for these -->

The <att>who</att> attribute is also useful as a means of supplying a
normalized form of the speaker's name, to facilitate selection of text
by particular speakers.  As indicated above, it may be supplied whether
or not an indication of the speaker is given explicitly in the text.

<p>Where investigation of <soCalled>narrative voice</soCalled> is the
primary object of the encoding, it may be convenient to identify each
speaker as a <term rend=noindex>participant</term> in the work, and to
associate individual speeches with them by means of SGML's ID/IDREF
mechanism.  See section <ptr target=CCahpa> for discussion of the
<term>participant description</term> component of the TEI Header.

<p>For such analyses, it may also be useful to distinguish
representations of speech from representations of thought, in modern
printed texts often indicated by a change of typeface.  The
<att>type</att> attribute should be used for this purpose, as in this
example:

<eg>
<![ CDATA [
<q type=speech>Oh yes,</q> said Henry, <q type=speech>I mean
Gordon Macrae, for example...</q>
<q type=thought>Jungian Analyst with Winebox! That's what you
called him, you callous bastard, didn't you? Eh? Eh?</q>
]]>
</eg><!-- N Williams, The Wimbledon Poisoner, p 204 -->

<p>Quoted matter may be embedded within quoted matter, as when one
speaker reports the speech of another:

<eg>
<![ CDATA[
<q who=Wilson>Spaulding, he came down into the office just this
day eight weeks with this very paper in his hand, and he
says:&mdash;<q who=Spaulding>I wish to the Lord, Mr. Wilson, that
I was a red-headed man.</q></q>
]]>
</eg><!-- A C Doyle, Red headed league (but where?) -->

<p>Direct speech nested in this way is treated in the same way as
elsewhere:  a change of rendition may occur, but the same
element should be used.  An encoder may however choose to distinguish
between direct speech which contains quotations from extra-textual
matter and direct speech itself, as in the following example:

<eg>
<![ CDATA [
<p><q>The Lord! The Lord! It is Sakya Muni himself,</q> the
lama half sobbed; and under his breath began the wonderful
Buddhist invocation:-
<q><quote><l>To Him the Way -- the Law -- Apart --
<l>Whom Maya held beneath her heart
<l>Ananda's Lord -- the Bodhisat
</quote>
And He is here! The Most Excellent Law is here also.  My
pilgrimage is well begun.  And what work! What work!</q>
]]>
</eg> <!-- R.Kipling, Kim, Macmillan, 1917(1901) p9 -->

<p>Quotations from other works are often accompanied by a reference to
their source.  The <gi>cit</gi> element may be used to group together
the quotation and its associated bibliographic reference, which should
be encoded using the elements for bibliographic references discussed in
section <ptr target=CObi>, as in the following example.

<eg>
<![ CDATA [
<div id=MM01 type=chapter><head>Chapter 1</head>
<epigraph>
  <cit><quote><l>Since I can do no good because a woman
  <l>Reach constantly at something that is near it.</quote>
  <bibl><title>The Maid's Tragedy</title>
        <author>Beaumont and Fletcher</author></bibl>
  </cit>
</epigraph>
<p>Miss Brooke had that kind of beauty which seems to be thrown into
relief by poor dress...
]]>
</eg><!-- G. Eliot, Middlemarch, p 1 -->
<!-- apostrophe added to "Maid's" as per J. Lav, who says     -->
<!-- Penguin has it. (msm)                                    -->

Like other bibliographic references, the citation attached to a
quotation may be represented simply by a pointer, as in this example:

<eg><![ CDATA[
Lexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized
in his slogan, <cit><quote>You shall know a word by the company it
keeps.</quote> <ref target=FI57>(Firth, 1957)</ref></cit>
]]>
</eg>
<!-- Hanks, in Looking Up, ed Sinclair, (1987) p.121 -->

Unlike most of the other elements discussed in this chapter, direct
speech and quotations may frequently contain other high-level elements
such as paragraphs or verse lines, as well as being themselves contained
by such elements.  Three possible solutions exist for this well-known
structural problem:

<list type=bullets>
<item>the quotation is broken into segments, each of which
is entirely contained within a paragraph
<item>the quotation is marked up as part of a concurrent but
independent hierarchy
<item>the quotation boundaries are represented by empty milestone
tags
</list>

For further discussion, and several examples, see chapter <ptr
target=NH>.

<p>Finally, in this section, the element <gi>soCalled</gi> is provided
for all cases in which quotation marks are used to distance the quoted
text from the narrator or speaker.  Common examples include the
<soCalled>scare</soCalled> quotes often found in newspaper headlines and
advertising copy, where the effect is to cast doubts on the veracity of
an assertion:

<eg>
<![ CDATA [
<head>PM dodges <soCalled>election threat</soCalled>
in interview</head>
]]>
</eg><!-- The Guardian, p2, 26 Oct 1992  -->

<p>The same element should be used to mark a variety of special ironic
usages.  Some further examples follow:

<eg><![ CDATA[
He hated <soCalled>good</soCalled> books.

<soCalled>Croissants</soCalled> indeed! toast not good enough for you?
]]>
</eg><!-- some "real" examples would be better -->

<eg>
<![ CDATA [
Although Chomsky's decision that all NL sentences are finite
objects was never justified by arguments from the attested
properties of NLs, it did have a certain
<soCalled>social</soCalled> justification.  It was
commonly assumed in works on logic until fairly recently
that the notion <mentioned>language</mentioned> is
necessarily restricted to finite strings.
]]>
</eg><!-- Langendoen and Postal, Vastness of NLs, p. 24 note 12.        -->

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

<eg id=dcohqq>
<![ CDATA [
<!-- 6.3.3:  Highlighted phrases (cont'd)                     -->
<!-- (continuation of sec. 6.3.2.1)                           -->
<!ELEMENT q             - -  (%specialPara)                     >
<!ATTLIST q                  %a.global;
          who                CDATA               #IMPLIED
          type               CDATA               #IMPLIED
          direct             (y | n | unspecified) 
                                                 unspecified    >
<!ELEMENT quote         - -  (%specialPara;)                    >
<!ATTLIST quote              %a.global;                         >
<!ELEMENT cit           - -  (((q | quote), (bibl | loc)) | 
                             ((bibl | loc), (q | quote)))       >
<!ATTLIST cit                %a.global;                         >
<!ELEMENT soCalled      - -  (%phrase.seq;)                     >
<!ATTLIST soCalled           %a.global;                         >
]]>
</eg>


<!-- P2, ch 23, sec 8                                         -->
<!-- Revisions                                                -->
<!-- 24-27 Oct LB     reorganise slightly                     -->
<!-- 26 May 92 : MSM : fix div levels                         -->
<!-- 15 May 92 : LB : check out to MSM                        -->
<div3 id=COhqu><head>Terms, Glosses, and Cited Words</head>

<p>This section describes the following textual elements, all of which
have in common that they may be variously realized using italics,
quotation marks or other devices:

<list type=gloss>
<label><gi>term</gi></label>
<item>contains a single-word, multi-word or symbolic designation 
which
is regarded as a technical term.</item>
<label><gi>gloss</gi></label>
<item>identifies a phrase or word used to provide a gloss or

definition for some other word or phrase. </item>
<label><gi>mentioned</gi></label>
<item>marks words or phrases mentioned, not used.</item>
</list>


<p>Technical terms are often italicized or emboldened upon first mention
in printed texts; an explanation or gloss is sometimes given in
quotation marks.  Linguistic analyses conventionally cite words in
languages under discussion in italics, providing a gloss immediately
following marked with single quotation marks.  Other texts in which
individual words or phrases are <term rend=noindex>mentioned</term> (for
<index level1='mention' level2='vs. use'>
<index level1='use' level2='vs. mention'>
example, as examples) rather than <term rend=noindex>used</term> may
mark them either with italics or with quotation marks, and will gloss
them less regularly.

<p>A <gi>term</gi> may appear with or without a gloss, as may a
<gi>mentioned</gi> element.  Where the <gi>gloss</gi> is present, it may
be linked to the term it is glossing by means of SGML's ID/IDREF
mechanism.  To establish such a link, the encoder should give an
<att>id</att> value to the <gi>term</gi> or <gi>mentioned</gi> element
and provide that id as the value of the <att>target</att> attribute on
the <gi>gloss</gi> element.  The following examples demonstrate this
facility:  for more discussion of this and other kinds of linkage within
TEI documents, see chapter <ptr target=SA>.

<p>Examples:
<!>
<eg><![ CDATA [
We may define <term rend=sc id=tdpv>discoursal point of view</term>
as <gloss target=tdpv>the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss>
]]>
</eg>
<!-- Leech, Style in Fiction, (1981) p272 -->

<eg><![ CDATA [
<gloss target=T1 rend=unmarked>A computational device
that infers structure from grammatical strings of words</gloss>
is known as a <term id=T1>parser</term>, and much of the
history of NLP over the last 20 years has been occupied with
the design of parsers.
]]>
</eg>
<!-- Gazdar and Mellish, NLP in Prolog, p. 5   -->

<eg><![ CDATA [
There is thus a striking accentual difference between a
verbal form like <mentioned lang=grc
id=cw234>eluthemen</mentioned> <gloss target=cw234>we
were released,</gloss> accented on the second
syllable of the word, and its participial derivative
<mentioned id=cw235 lang=grc>lutheis</mentioned>
<gloss target=cw235>released,</gloss> accented on the last.
]]>
</eg>
<!-- Sapir, Language (HBJ paperback), p. 79                        -->

<!>
<p>The elements discussed in this section have the following formal
definitions:
<eg id=dcohqu>
<![ CDATA [
<!-- 6.3.4:  Highlighted phrases (cont'd)                     -->
<!-- (continuation of sec. 6.3.2.1)                           -->
<!ELEMENT term          - -  (%phrase.seq;)                     >
<!ATTLIST term               %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT mentioned     - -  (%phrase.seq;)                     >
<!ATTLIST mentioned          %a.global;                         >
<!ELEMENT gloss         - -  (%phrase.seq;)                     >
<!ATTLIST gloss              %a.global;
          target             IDREF               #IMPLIED       >
]]>
</eg>


<div3 id=COhqheg><head>Some Further Examples</head>

<p>As a simple example of the elements discussed here, consider the
following sentence:

<!-- Theodore M. Andersson, Preface to the Nibelungenlied, p. 3 -->
<q rend=display>
On the one hand the <title>Nibelungenlied</title> is
associated with the new rise of romance of twelfth-century
France, the <foreign>romans d'antiquit&eacute;</foreign>,
the romances of Chr&eacute;tien de Troyes, and the German
adaptations of these works by Heinrich van Veldeke,
Hartmann von Aue, and Wolfram von Eschenbach.
</q>
A first approximation to the encoding of this sentence, might be simply
to record the fact that the phrases printed above in italics are
highlighted, as follows:
<!>
<eg>
<![ CDATA[
On the one hand the <hi rend=italic>Nibelungenlied</hi> is
associated with the new rise of romance of twelfth-century
France, the <hi rend=italic lang=fr>romans
d'antiquit&eacute;</hi>, the romances of Chr&eacute;tien de
Troyes, ...
]]>
</eg>
This encoding would however lose the important distinction between
an italicized title and an italicized foreign phrase.  Many other
phrases might also be italicized in the text, and a retrieval
program seeking to identify foreign terms (for example) would not
be able to produce reliable results by simply looking for italicized
words.  Where economic and intellectual constraints permit, therefore,
it would be preferable to encode both the function of the
highlighted phrases and their appearance, as follows:
<!>
<eg>
<![ CDATA[
On the one hand the <title
rend=italic>Nibelungenlied</title> is associated with the
new rise of romance of twelfth-century France, the <foreign
rend=italic>romans d'antiquit&eacute;</foreign>, the
romances of Chr&eacute;tien de Troyes, ...
]]>
</eg>
<p>In this example, the decision as to which textual features
are distinguished by the highlighting is relatively
uncontroversial.  As a less straightforward example, consider the
use of italic font in the following passage
from Samuel Richardson's <title>Clarissa</title> (1747).
<!-- NB this is NOT a P2 example!! -->
<!-- replaced < ital > by < hilited rend=it > added entity ref -->
<q rend=display>
A pretty common case, I believe; in all
<hi rend=it>vehement</hi> debatings.  She says I am
<hi rend=it>too witty</hi>; Anglic&eacute;,
<hi rend=it>too pert</hi>; I, that she is
<hi rend=it>too wise</hi>; that is to say, being
likewise put into English, <hi rend=it>not so young as
she has been</hi>:  in short, she is grown so much into
a <hi rend=it>mother</hi>, that she had forgotten
she ever was a <hi rend=it>daughter</hi>. ...
</q>

<p>Clearly, the word <mentioned>vehement</mentioned> is not italicized for the
same reason as the phrase <mentioned>not so young as she has been</mentioned>;
the former is emphasized, while the latter is proverbial.  It also
provides an ironic gloss for the words <mentioned>too wise</mentioned>, in the
same way as <mentioned>too pert</mentioned> glosses <mentioned>too witty</mentioned>.
The glossed phrases are not however technical terms or cited words, but
quoted phrases, as if Clarissa were putting words into her own and her
mother's mouths.  Finally, the words <mentioned>mother</mentioned> and
<mentioned>daughter</mentioned> are apparently italicized simply to oppose them
in the sentence; certainly they do not fit into any of the categories so
far proposed as reasons for italicizing.  Note also that the word
<mentioned>Anglic&eacute</mentioned> is not italicized although it is not
generally considered an English word.

<p>The following sample encoding for the above passage attempts to take
into account all the above points:

<eg>
<![ CDATA [
A pretty common case, I believe; in all
<emph>vehement</emph> debatings.  She says I am
<q rend=italic>too witty</q>; <foreign lang=la
rend=roman>Anglic&egrave;</foreign>, <gloss rend=italic>too
pert</gloss>; I, that she is <q rend=italic>too wise</q>;
that is to say, being likewise put into English, <gloss
rend=italic>not so young as she has been</gloss>:  in short,
she is grown so much into a <hi rend=italic>mother</hi>,
that she had forgotten she ever was a
<hi rend=italic>daughter</hi>.
]]>
</eg>

<!-- WWP proofer points out inconsistency between tagging     -->
<!-- and commentary.  "too witty" and "too wise" retagged     -->
<!-- from TERM (which the prose says they are *not*) to Q     -->
<!-- (which the prose says they *are*).  WWP proofer also     -->
<!-- suggests EMPH for 'mother' and 'daughter', but our       -->
<!-- imaginary interpretation says we don't understand the    -->
<!-- italics there, so we leave it undisambiguated.  (msm)    -->


<!-- COna Names (P1 5.3.6)                                    -->
<!-- $Id: p2cona.odd,v 1.7 1998/01/28 11:09:58 cmsmcq Exp $ -->
<!-- $Log: p2cona.odd,v $
# Revision 1.7  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.6  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# -->
<!-- Revisions:                                               -->
<!-- 10 jan 98 : LB : fix eg -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-25 : MSM : typos corrected as per J. Lavagnino     -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- 3 jan 94: fixed up address again -->
<!-- 27 dec 93:LB: moved address section                      -->
<!-- 93-06-05 : MSM : fix type:  eg had no end-tag, two starts -->
<!-- 2 Jun 93: LB : incorporate and tidy up DG's Eynsham revisions -->
<!-- 92-12-09 : MSM : introduce NAMES class                   -->
<!--                  correct typo in 'practical' Chaucer     -->
<!-- 92-12-09 : MSM : spellcheck for publication              -->
<!-- 92-12-09 : MSM : cosmetic copy editing                   -->
<!-- 92-12-09 : MSM : add space after some end-tags           -->
<!-- 92-12-07 : MSM : change date/type to date/calendar       -->
<!-- 92-12-07 : MSM : finish run-through for publication      -->
<!-- 92-12-06 : MSM : begin revising for publication          -->
<!-- 92-12-06 : MSM : include addr in title, correct abbr div -->
<!-- 92-12-06 : MSM : include new p2conaad div                -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<!-- 92-11-09 : MSM : indent ellipsis for WGML's sake         -->

<div2 id=COna><head>Names, Numbers, Dates, Abbreviations, and Addresses</head>

<p>This section describes a number of  textual features which it is
often convenient to distinguish from their surrounding text.  Names,
dates and numbers are likely to be of particular importance to  the
scholar treating a text as source for a database; distinguishing such
items from the surrounding text is however equally important to the
scholar primarily interested in lexis.

<p>The treatment of these textual features proposed here is not
intended to be exhaustive: fuller treatments for names, numbers,
measures and dates are provided in the additional tag set for
names and dates (see chapter <ptr target=ND>).

<!-- fuller treatment of addresses in the base tag set for    -->
<!-- letters and memoranda (see chapter <ptr target=LM>).    -->

<!-- P2.239 : Referring Strings                                -->
<!-- Revisions:                                               -->
<!-- 16 May 92 : DG further revision                         -->
<!-- 13 oct 92 : LB further revision                          -->
<!-- 5-7 Oct 92 : (LB) reassemble; extensively revise; redo IDs  -->
<!-- 25 May 92 : CMSMcQ : drop components, add note on them   -->
<!-- 24 May 92 : CMSMcQ : add component parts for names       -->
<!-- 14 May 92 : CMSMcQ : revise.                             -->
<!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     -->
<!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  -->
<!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->

<div3 type='subsection' id=COnars><head>Referring Strings</head>

<p>A <term>referring string</term> is a phrase which refers to some
person, place, object etc. Two elements are provided to mark such
strings:

<list type=gloss>
<label><gi>rs</gi></label>
<item>contains a general purpose name or referring string.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates more specifically the object referred to by the 
referencing string. Values might include <q>person</q>, 
<q>place</q>, <q>ship</q>, <q>element</q> etc.</item>
</list>
</item>
<label><gi>name</gi></label>
<item>contains a proper noun or noun phrase.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates the type of the object which is being named by 
the phrase.</item>
</list>
</item>
</list>


Where it is thought useful to do so, the kind of object referred to may
be specified using the <att>type</att> attribute.

<p>Examples include:

<eg>
<![ CDATA [
<q>My dear <rs type=person>Mr. Bennet</rs>, </q>
said his lady to him one day, <q>have you heard
that <rs type=place>Netherfield Park</rs> is let
at last?</q>
]]>
</eg><!-- Austen Pride and Prejudice, chap 1 -->

<eg>
<![ CDATA [
Collectors of water-rents were appointed by the
<rs type=organization>Watering Committee</rs>.
They were paid a commission not exceeding four per
cent, and gave bond.
]]>
</eg><!-- Allinson and Penrose, Philadelphia 1681-1887, p138 -->

<eg> <![ CDATA [
It being one of the principles of the
<rs type=org>Circumlocution Office</rs> never, on any
account whatsoever, to give a straightforward answer,
<rs type=person>Mr Barnacle</rs> said, <q>Possibly.</q>
]]>
</eg>
<!-- Little Dorrit, peng ed, p 153 -->

<p>As the following example shows, the <gi>rs</gi> element may be used
for any reference to a person, place, etc., not only to references in
the form of a proper noun or noun phrase.

<eg><![ CDATA [
<q>My dear <rs type=person>Mr. Bennet</rs>,</q>
said <rs type=person>his lady</rs> to him
one day...
]]>
</eg>


<p>The <gi>name</gi> element by contrast is provided for the special
case of referencing strings which consist only of proper nouns; it may
be used synonymously with the <gi>rs</gi> element, or nested within it
if a referring string contains a mixture of common and proper nouns.
The following example shows an alternative way of encoding the short
sentence from <title>Pride and Prejudice</title> quoted above:

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

The following example shows how a proper name may be nested within a
referring string:

<eg><![ CDATA [
<rs>His Excellency the Life President,
<name>Ngwazi Dr H. Kamuzu Banda</name></rs>
<!-- ... -->
]]>
</eg>
<!-- any issue of the Malawi Daily Times -->


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

<p>The following attributes, common to all members of the
<ident type=class>names</ident>
element class, are provided to help overcome these difficulties:

<list type=gloss>
<label><att>key</att></label>
<item>provides an alternative identifier for the object being 
named, such as a database record key.</item>
<label><att>reg</att></label>
<item>gives a normalized or regularized form of the name used.</item>
</list>

<p>Either or both of these attributes may be specified, as appropriate.
The <att>key</att> attribute may be useful as a means of gathering
together all references to the same individual or location scattered
throughout a document:


<eg><![ CDATA [
<q>My dear <rs type=person key=BENM1>Mr. Bennet</rs>,
</q> said <rs type=person key=BENM2>his lady</rs>
to him one day, <q>have you heard that
<rs type=place key=NETP1>Netherfield Park</rs>
is let at last?</q>
]]>
</eg>

<p>This use should be distinguished from the case of the
<att>reg</att> (regularization) attribute, which provides a
means of marking the standard form of a referencing string as
demonstrated below:

<eg><![ CDATA [
My personal life during the administration of
<rs type=person key=POJA1 reg='Polk, James K.'>Col. Polk</rs>
has but poorly compensated me for the suspended
enjoyments and pursuits of private and professional spheres
]]>
</eg>
<!-- From the papers of George Mifflin Dallas, cited in -->
<!-- Philadelphia: A 300 Year History, p349 -->

<eg><![ CDATA [
<name type=person key=VOM1 reg='Volanges, Mme de'>
Mme. de Volanges</name>
marie sa fille: c'est encore un secret; mais elle m'en
a fait part hier.
]]>
</eg>  <!-- de Laclos: Les Liaisons dangereuses, 1963, p.13 -->

<eg><![ CDATA [
<name type=person key=WADLM1 reg='de la Mare, Walter'>
Walter de la Mare
</name>
was born at
<name key=Ch1 type=place>Charlton</name>, in
<name key=KT1 type=county>Kent</name>, in 1873.
]]>
</eg>
<!-- Frank Swinnerton, The Georgian Literary Scene, 1938, p. 195 -->

<eg><![ CDATA [
<name type=place>Montaillou</name> is not a large parish.
At the time of the events which led to
<name type=person reg='Benedict XII, Pope of Avignon
(Jacques Fournier)'>Fournier's</name> investigations,
the local population consisted of between 200 and
250 inhabitants.
]]>
</eg>

<!-- E.L Ladurie: Montaillou, Penguin 1980, p3 -->
<!-- but should we quote the French? (LB) -->

<p>This method is adequate for many simple applications. For more
complex applications, such as onomastics, or wherever a detailed
analysis of the component parts of a name is needed, the specialized
elements described in chapter <ptr target=ND> or the analytical
tools described in chapter <ptr target=FS> should be used.

<p>These elements are formally declared as follows:
<eg id=dcona>
<![ CDATA [
<!-- 6.4.1:  Proper Nouns                                     -->
<!ELEMENT name          - -  (%phrase.seq;)                     >
<!ATTLIST name               %a.global;
                             %a.names;
          type               CDATA               #IMPLIED       >
<!ELEMENT rs            - -  (%phrase.seq)                      >
<!ATTLIST rs                 %a.global;
                             %a.names;
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>


<!-- <claDecl type=atts classDoc=names>                       -->

<div3 id=COnaad><head>Addresses</head>

<p>The simplest way of encoding an address is to regard it as a series
of distinct lines, just as they might be printed on an envelope. The
following elements support this view:

<list type=gloss>
<label><gi>address</gi></label>
<item>contains a postal or other address, for example of a

publisher, an organization, or an individual.</item>
<label><gi>addrLine</gi></label>
<item>contains one line of a postal or other address.</item>
</list>


<p>Alternatively, an address may be encoded as a structure composed of
the following elements, which constitute the <ident
type=class>addrPart</ident> element class:

<list type=gloss>
<label><gi>street</gi></label>
<item>a full street address including any name or number 
identifying a
building as well as the name of the street 
or route on which it is
located.</item>
<label><gi>name</gi></label>
<item>contains a proper noun or noun phrase.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates the type of the object which is being named by 
the phrase.</item>
</list>
</item>
<label><gi>postCode</gi></label>
<item>contains a numerical or alphanumeric code used as part of a
postal address to simplify sorting or delivery of mail. </item>
<label><gi>postBox</gi></label>
<item>contains a number or other identifier for some postal 
delivery
point other than a street address. </item>
</list>


Any number of <ident type=class>addrPart</ident> elements may appear
within an address and in any order.  None of them is required.  Where
code letters are commonly used in addresses (for example, to identify
regions or countries) a useful practice is to supply the full name of
the region or country as the content of the element, but to supply the
abbreviatory code as the value of the global <att>n</att> attribute, so
that (for example) an application preparing formatted labels can readily
find the required information.  Other components of addresses should be
represented using the general-purpose <gi>name</gi> element.

<p>Some examples follow:
<eg>
<![ CDATA [
<address>
<addrLine>110 Southmoor Road, </>
<addrLine>Oxford, OX2 6RB,</>
<addrLine>UK</>
</address>
]]>
</eg>

<p>The above address could also be represented as follows :

<eg>
<![ CDATA [
<address>
<street>110 Southmoor Road</street>
<name type=city n=OX>Oxford</name>
<postCode>OX2 6RB</postCode>
<name type=country n=UK>United Kingdom</name>
</address>
]]>
</eg>

<p>The order of elements within an address is highly culture-specific,
and is therefore unconstrained:

<eg>
<![ CDATA [
<address>
<name type=org>Universit&agrave; di Bologna</name>
<name type=country n=I>Italy</name>
<postCode>40126</postcode>
<name type=city>Bologna</name>
<street>via Marsala 24</street>
</address>
]]>
</eg>

<p>For further discussion of ways of regularizing the names of places,
see section <ptr target=COna>.  A full postal address may also include
the name of the addressee, tagged as above using the general purpose
<gi>name</gi> element.  When the additional tag set for names and dates
is enabled, more specific elements such as <gi>publisher</gi> or
<gi>org</gi> may be used, as further discussed in chapter <ptr
target=ND>.

<!-- <p>A more detailed encoding of addresses is provided by  -->
<!-- the elements described in the base tag set for letters   -->
<!-- and memoranda described in chapter <ptr target=LM>,     -->
<!-- which also includes elements for the encoding of         -->
<!-- electronic mail addresses and other telecommunications   -->
<!-- facilities.                                              -->

<p>The <gi>address</gi> element and its components are formally
described as follows:

<eg id=dcoad>
<![ CDATA [
<!-- 6.4.2:  Addresses and their components                   -->
<!ELEMENT address       - O  (addrLine+ | (%m.addrPart)*)       >
<!ATTLIST address            %a.global;                         >
<!ELEMENT addrLine      - o  (%phrase.seq)                      >
<!ATTLIST addrLine           %a.global;                         >
<!ELEMENT street        - o  (%phrase.seq)                      >
<!ATTLIST street             %a.global;                         >
<!ELEMENT postCode      - o  (#PCDATA)                          >
<!ATTLIST postCode           %a.global;                         >
<!ELEMENT postBox       - o  (#PCDATA)                          >
<!ATTLIST postBox            %a.global;                         >
<!-- Other components of addresses should be represented      -->
<!-- using the general purpose NAME element                   -->

<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>


<!-- P2.23a : Numbers                                         -->
<!-- Revisions:                                               -->
<!-- 25 May 92 : CMSMcQ : revise                              -->

<div3 id=COnanu><head>Numbers and Measures</head>
<!-- h3 id=z63a>Numbers and Dates -->


<p>This section describes two elements provided for the simple encoding
of numbers and measures and gives some indication of circumstances in
which this may usefully be done.  The following phrase level elements
are provided for this purpose:

<list type=gloss>
<label><gi>num</gi></label>
<item>contains a number, written in any form.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates the type of numeric value.
Suggested values include:
<list type=gloss>
<label><term>fraction</term></label>
<item>fraction, e.g. <q>one half</q> or <q>three halves</q></item>
<label><term>ordinal</term></label>
<item>ordinal number, e.g. <q>21st</q></item>
<label><term>percentage</term></label>
<item>e.g. <q>ten percent</q></item>
<label><term>cardinal</term></label>
<item>absolute number, e.g. <q>21</q>, <q>21.5</q></item>
</list></item>
<label><att>value</att></label>
<item>supplies the value of the number in an 
application-dependent standard form.</item>
</list>
</item>
<label><gi>measure</gi></label>
<item>contains a word or phrase referring to some quantity of
an 
object or commodity, usually comprising a number, a unit 
and a
commodity name.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>specifies the type of unit in which the measure is 
expressed.
Sample values include:
<list type=gloss>
<label><term>count</term></label>
<item>unit of count, e.g. dozen, score.</item>
<label><term>currency</term></label>
<item>unit of currency e.g. ecu, escudo, mark.</item>
<label><term>weight</term></label>
<item>measure of weight e.g. kg, pound.</item>
<label><term>length</term></label>
<item>measure of length, e.g. pole, mm.</item>
<label><term>volume</term></label>
<item>measure of volume e.g. litre, gallon.</item>
<label><term>area</term></label>
<item>measure of area e.g. acre, hectare.</item>
</list></item>
</list>
</item>
</list>


<p>Like names or abbreviations, numbers can occur virtually anywhere in
a text.  Numbers are special in that they can be written with either
letters or digits (<mentioned>twenty-one</mentioned>, <mentioned>xxi</mentioned>, and
<mentioned>21</mentioned>) and their presentation is language-dependent (e.g.
English <mentioned>5th</mentioned> becomes Greek <mentioned>5.</mentioned>; English
<mentioned>123,456.78</mentioned> equals French <mentioned>123.456,78</mentioned>).

<p>For many kinds of application, e.g. natural-language processing or
machine translation, numbers are not regarded as
<soCalled>lexical</soCalled> in the same way as other parts of a text.
For these and other applications, the <gi>num</gi> element provides a
convenient method of distinguishing numbers from the surrounding text.
For other kinds of application, numbers are only useful if normalized:
here the <gi>num</gi> element is useful precisely because it provides a
standardized way of representing a numerical value.

<p>For example:
<!>
<eg><![ CDATA [
<num value='33'>xxxiii</num>
<num type=cardinal value='21'>twenty-one</num>
<num type=percentage value='10'>ten percent</num>
<num type=percentage value='10'>10%</num>
<num type=ordinal value='5'>5th</num>
]]>
</eg>

<eg><![ CDATA [
<num type=fraction value='0,5'>one half</num>
<num type=fraction value='0,5'>1/2</num>
]]>
</eg>


<p>The word <mentioned>measure</mentioned> is used here to refer to a special
kind of referring string, the referent of which is a <soCalled>virtual
object</soCalled>.  In its fullest form, a measure consists of a number,
a phrase expressing units of measure and a phrase expressing the
commodity being measured.  Not all of these components need be present
in every case.  For some applications, particularly quantitative ones,
the internal components of measure need to be marked so that their
values can be calculated.  Thus, in order to evaluate a monetary measure
according to some standard, it is necessary to mark its currency unit
(e.g.  US dollars, pounds sterling).  Similarly, the expression <mentioned>2
ounces</mentioned> will have a different meaning when it is associated with
<mentioned>flour</mentioned> from that which it has when associated with
<mentioned>water</mentioned>.

<p>Such applications will require the elements discussed in chapter
<ptr target=ND>, or the more powerful analytical tools discussed in
chapter <ptr target=FS>.  Elsewhere, it may be sufficient simply to
encode measures as such, perhaps also indicating their numeric content
with the <gi>num</gi> element, as in the following examples:

<eg><![ CDATA [
<l>I've measured it from side to side
<l>'Tis
<measure type=length reg='0.924m'>
    <num value=3>three</num>
    feet
</measure>
long, and
<measure type=length reg='0.616m'>
   <num value=2>two</num>
   feet
</measure>
wide.
</l>
]]>
</eg><!-- Wordsworth: The Thorn: Lyrical Ballads (1798) -->

As the above example also demonstrates, the <gi>measure</gi> element is
a member of the class <ident type=class>names</ident> like other
referencing strings, and may thus bear a <att>reg</att> attribute to
indicate a normalized value.  It may also carry a <att>key</att>
attribute to indicate a database key value as in the following example:


<eg><![ CDATA [
<list>
<item><measure key=BH2 type=volume>
         <num value=2>ii</num>
          bags hops
       </measure>
<item> <measure key=TW6 type=volume>
         <num value=6>six</num>
        trusses Woolen and linen goods
       </measure>
<item><measure  key=WC5 type=weight>
        5 tonnes coale
      </measure>
<!-- ... -->
</list>
]]>
</eg>
<!-- Gloucester Port Books -->

<p>These elements are formally defined as follows:

<eg id=dconu>
<![ CDATA [
<!-- 6.4.3:  Numbers and measures                             -->
<!ELEMENT num           - -  (%phrase.seq;)                     >
<!ATTLIST num                %a.global;
          value              CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
<!ELEMENT measure       - -  (%phrase.seq;)                     >
<!ATTLIST measure            %a.global;
                             %a.names;
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>


<!-- P2.23c : Dates                                           -->
<!-- Revisions:                                               -->
<!-- 25 May 92 : CMSMcQ : revise                              -->
<!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     -->
<!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  -->
<!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->

<div3 id=COnada><head>Dates and times</head>

<p>Dates and times, like numbers, can appear in widely varying
culture- and language-dependent forms, and can pose similar problems
in automatic language processing.  The following elements are provided
to identify them:

<!--  certainty attributes replaced by exact   -->
<!-- added time, on advice of Chicago meeting, but with reservns -->

<list type=gloss>
<label><gi>date</gi></label>
<item>contains a date in any format.
Attributes include:
<list type=gloss>
<label><att>calendar</att></label>
<item>indicates the system or calendar to which the date belongs.</item>
<label><att>value</att></label>
<item>gives the value of the date in some standard form, usually 
yyyy-mm-dd.</item>
</list>
</item>
<label><gi>time</gi></label>
<item>contains a phrase defining a time of day in any format.
Attributes include:
<list type=gloss>
<label><att>value</att></label>
<item>gives the value of the time in a standard form.</item>
</list>
</item>
<label><gi>dateRange</gi></label>
<item>contains two dates or another phrase delimiting a time 
period.
Attributes include:
<list type=gloss>
<label><att>calendar</att></label>
<item>indicates the system or calendar to which the date belongs.</item>
<label><att>from</att></label>
<item>indicates the starting point of the period in standard 
form.</item>
<label><att>to</att></label>
<item>indicates the ending point of the period in standard form.</item>
<label><att>exact</att></label>
<item>indicates the precision to be attached to either or both 
dates specified.
Legal values are:
<list type=gloss>
<label><term>from</term></label>
<item>the <att>from</att> date is exact</item>
<label><term>both</term></label>
<item>both dates are exact</item>
<label><term>to</term></label>
<item>the <att>to</att> date is exact</item>
<label><term>none</term></label>
<item>both dates are approximate or unspecified</item>
</list></item>
</list>
</item>
<label><gi>timeRange</gi></label>
<item>contains two times or another phrase indicating a time 
period.
Attributes include:
<list type=gloss>
<label><att>from</att></label>
<item>indicates the starting point of the time period in standard 
form.</item>
<label><att>to</att></label>
<item>indicates the ending point of the time period in standard 
form.</item>
<label><att>exact</att></label>
<item>indicates the precision to be attached to either or both 
times specified.
Legal values are:
<list type=gloss>
<label><term>from</term></label>
<item>the <att>from</att> time is exact</item>
<label><term>both</term></label>
<item>both times are exact</item>
<label><term>to</term></label>
<item>the <att>to</att> time is exact</item>
<label><term>none</term></label>
<item>both times are approximate or unspecified</item>
</list></item>
</list>
</item>
</list>


<p>Dates can occur virtually anywhere in a text, but in some contexts
(e.g. bibliographic citations) their encoding is recommended or
required rather than optional.  Times can also appear anywhere but
are generally optional.

<p>Partial dates or times (e.g. <mentioned>1990</mentioned>, <mentioned>September
1990</mentioned>, <mentioned>twelvish</mentioned>) can be expressed in the
<att>value</att> attribute by simply omitting a part of the value
supplied.  Imprecise dates or times (for example <mentioned>early
August</mentioned>, <mentioned>some time after ten and before twelve</mentioned>)
may be expressed as date or time ranges.  If either end of the date or
time range is known to be accurate (for example, <mentioned>at some time
before 1230</mentioned>, <mentioned>a few days after Hallowe'en</mentioned>), the
<att>exact</att> attribute may be used to specify this.

<p>Where the certainty (i.e. reliability) of the date or time itself is
in question, rather than its precision, the encoder should record this
fact using the mechanisms discussed in chapter <ptr target=CE>.

<p>These mechanisms are useful primarily for fully specified dates or
times known with certainty.  If component parts of dates or times are to
be marked up, or if a more complex analysis of the meaning of a temporal
expression is required, the techniques described in chapter <ptr
target=ND> should be used in preference to the simple method outlined
here.

<p>Examples:

<!>
<eg><![ CDATA [
<date value='1980-02-21'>21 Feb 1980</date>
]]>
</eg>

<eg><![ CDATA [
Given on the <date value='1977-06-12'>Twelfth Day of June
in the Year of Our Lord One Thousand Nine Hundred and
Seventy-seven of the Republic the Two Hundredth and first
and of the University the Eighty-Sixth.</date>
]]>
</eg>

<eg><![ CDATA [
<date value='1990'>1990</date>
<date value='1990-09'>September 1990</date>
]]>
</eg>

<eg>
<![ CDATA [
Those five years &mdash; <dateRange from=1918 to=1923>
1918 to 1923</dateRange> &mdash had been, he suspected,
somehow very important.
]]>
</eg><!-- Woolf, Mrs Dalloway, p. 65 -->
<eg>
<![ CDATA [
The Eddic poems are preserved in a unique
manuscript (Codex Regius 2365) from
<dateRange from=1250 to=1300>
the second half of the thirteenth
century</dateRange>, and <title>Hervarar
saga</title> dates from <date value=1300>
around 1300</date>.
]]>
</eg>
<!-- T. M. Andersson, A Preface to the Nibelungenlied         -->
<!-- (Stanford:  Stanford University Press, 1987) p. 4        -->

<p>These elements are formally defined as follows:

<eg id=dcoda>
<![ CDATA [
<!-- 6.4.4:  Dates and times                                  -->
<!ELEMENT date          - -  (%phrase.seq;)                     >
<!ATTLIST date               %a.global;
          value              CDATA               #IMPLIED
          calendar           CDATA               #IMPLIED
          certainty          CDATA               #IMPLIED       >
<!ELEMENT dateRange     - O  (%phrase.seq;)                     >
<!ATTLIST dateRange          %a.global;
          to                 CDATA               #IMPLIED
          exact              (to | from | both | none) 
                                                 #IMPLIED
          from               CDATA               #IMPLIED
          calendar           CDATA               #IMPLIED       >
<!ELEMENT time          - -  (%phrase.seq;)                     >
<!ATTLIST time               %a.global;
          value              CDATA               #IMPLIED
          type               (am | pm | 24hour | descriptive) 
                                                 #IMPLIED
          zone               CDATA               #IMPLIED       >
<!ELEMENT timeRange     - -  (%phrase.seq;)                     >
<!ATTLIST timeRange          %a.global;
          to                 CDATA               #IMPLIED
          exact              (to | from | both | none) 
                                                 #IMPLIED
          from               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>



<div3 id=COnaab><head>Abbreviations and Their Expansions</head>

<p>It is sometimes desirable to mark abbreviations in the copy text,
whether to trigger special processing for them, to provide the full form
of the word or phrase abbreviated, or to allow for different possible
expansions of the abbreviation.  Abbreviations may be transcribed as
they stand, or expanded; they may be left unmarked, or marked using
these tags:

<list type=gloss>
<label><gi>abbr</gi></label>
<item>contains an abbreviation of any sort.
Attributes include:
<list type=gloss>
<label><att>expan</att></label>
<item>gives an expansion of the abbreviation.</item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for 
supplying the expansion of the abbreviation held as the 
value of the <att>expan</att> attribute.</item>
<label><att>type</att></label>
<item>allows the encoder to classify the abbreviation according 
to some convenient typology.
Sample values include:
<list type=gloss>
<label><term>contraction</term></label>
<item>the abbreviation omits some letter(s) in the middle.</item>
<label><term>title</term></label>
<item>the abbreviation is for a title of address (Dr, Ms, Mr, 
...)</item>
<label><term>geographic</term></label>
<item>the abbreviation is for a geographic name.</item>
<label><term>suspension</term></label>
<item>the abbreviation provides the first letter(s) of the word 
or phrase, omitting the remainder.</item>
<label><term>organization</term></label>
<item>the abbreviation is for the name of an organization.</item>
<label><term>brevigraph</term></label>
<item>the abbreviation comprises a special symbol or mark.</item>
<label><term>superscription</term></label>
<item>the abbreviation includes writing above the line.</item>
<label><term>acronym</term></label>
<item>the abbreviation comprises the initial letters of the words 
of a phrase.</item>
</list></item>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to the expansion 
of the abbreviation.</item>
</list>
</item>
<label><gi>expan</gi></label>
<item>contains the expansion of an abbreviation.
Attributes include:
<list type=gloss>
<label><att>abbr</att></label>
<item>gives the abbreviation in its unexpanded form.</item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for 
supplying the expansion of the abbreviation held as the 
content of the <gi>expan</gi> element.</item>
<label><att>type</att></label>
<item>allows the encoder to classify the abbreviation according 
to some convenient typology.</item>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to the expansion 
of the abbreviation.</item>
</list>
</item>
</list>


<!-- resp and cert bearing elements should become a class before p3 -->

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

<eg>
<![ CDATA [
We can sum up the above discussion as follows:  the identity of a
<abbr>CC</abbr> is defined by that calibration of values which
motivates the elements of its <abbr>GSP</abbr>; ...
]]>
</eg>
<!-- Halliday and Hassan, Language, context, and text:        -->
<!-- aspects of language in a social-semiotic perspective     -->
<!-- (OUP, 1990), p 104                                       -->

<eg>
<![ CDATA [
Every manufacturer of <abbr>3GL</abbr> or <abbr>4GL</abbr>
languages is currently nailing on <abbr>OOP</abbr> extensions.
]]>
</eg> <!-- .EXE magazine Editorial, 6.11, (May 1992) p2 -->

<p>The <att>type</att> attribute may be used to distinguish types
of abbreviation by their function, and the <att>expan</att> attribute
may be used to supply an expansion:

<eg>
<![ CDATA [
 <abbr type=title>Dr.</abbr> <abbr type=initial>M.</abbr> Deegan
 is the Director of the <abbr expan='Computers in Teaching Initiative'
 type=acronym>CTI</abbr> Centre for Textual Studies.
]]>
</eg>

<p>Abbreviations such as <mentioned>Dr M</mentioned> above may be treated as two
abbreviations, as above, or as one:

<eg>
<![ CDATA [
 <abbr>Dr. M.</abbr> Deegan is the Director of the
 <abbr>CTI</abbr> Centre for Textual Studies.
]]>
</eg>

<p>This element is particularly useful where manuscript materials
in which abbreviation is very frequent are being transcribed.  For
example:

<eg>
<![ CDATA [
<l>Ex<abbr type=brevigraph expan='per'
           Resp=PG>&per;</abbr>ience, thogh noon auctoritee
<l>Were in this world, is right ynogh for me
<l>To speke of wo that is in mariage;
]]>
</eg>

<p>Here an entity reference <ident type=ge>per</ident> has been used to
represent the common manuscript symbol <mentioned>crossed-p</mentioned>, and its
expansion supplied in the associated <gi>abbr</gi> tag.  The same lines
might be transcribed, expanded, as follows:

<eg>
<![ CDATA [
<l>Ex<expan type=brevigraph abbr='&per;'
          resp=PG>per</expan>ience, thogh noon auctoritee
<l>Were in this world, is right ynogh for me
<l>To speke of wo that is in mariage;
]]>
</eg>

<p>In practice, it may be most convenient to transcribe the abbreviation
as an entity reference; this allows the entity reference itself to be
expanded either as an <gi>abbr</gi> or as an <gi>expan</gi> element,
depending on the processing to be done at the moment.  (For further
discussion of such documentation, see section <ptr target=WDcscc>.)
The text shown here:

<eg>
<![ CDATA [
<l>Ex&per;ience, thogh noon auctoritee
<l>Were in this world, is right ynogh for me
<l>To speke of wo that is in mariage;
]]>
</eg>

may be expanded as desired by providing the appropriate choice between
the two entity declarations:

<eg rend=decl>
<![ CDATA [
<!ENTITY per "<abbr type=brevigraph expan='per'
              Resp=PG>&p.crossed;</abbr>" >
<!ENTITY per "<expan type=brevigraph abbrev='&p.crossed;'
              Resp=PG>per</expan>" >
]]>
</eg>

For further discussion of manuscript abbreviations, see chapter <ptr
target=PH>.

<p>These elements are formally defined as follows:
<eg id=dcoab>
<![ CDATA [
<!-- 6.4.5:  Abbreviations                                    -->
<!ELEMENT abbr          - -  (%phrase.seq;)                     >
<!ATTLIST abbr               %a.global;
          cert               CDATA               #IMPLIED
          expan              CDATA               #IMPLIED
          resp               IDREF               %INHERITED
          type               CDATA               #IMPLIED       >
<!ELEMENT expan         - -  (%phrase.seq;)                     >
<!ATTLIST expan              %a.global;
          cert               CDATA               #IMPLIED
          abbr               CDATA               #IMPLIED
          resp               IDREF               %INHERITED
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>



<!-- COed Editorial Interventions                             -->
<!-- $Id: p2coed.odd,v 1.7 1998/02/01 17:55:08 tei Exp $ -->
<!--*
    * $Log: p2coed.odd,v $
    * Revision 1.7  1998/02/01 17:55:08  tei
    * fix log keyword (still need SGML normalization)
    *
    * Revision 1.6  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.5  1994/03/27  21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    * -->
<!-- Revisions:                                               -->
<!-- 10 jan 98 : LB : fix eg errors -->
<!-- 4 Jan 98 : LB : restored missing > preceding tagdesc for ADD -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-26 : MSM : corrections from DB                     -->
<!-- 94-03-25 : MSM : typos corrected as per J. Lavagnino     -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- 3 jan 94: LB : rename omit/gap; remove SUPPLIEd; add UNCLEAR -->
<!-- 21 dec Lb : removed cert from OMIT (not in tagdoc) -->
<!-- 93-06-05 : MSM : remove dot from col 1                   -->
<!-- 1 jun 93 : LB implement PR's suggestions of 28 may -->
<!-- 92-12-09 : MSM : normalize sentence-end spacing          -->
<!-- 92-12-09 : MSM : spellcheck for release                  -->
<!-- 92-12-09 : MSM : correct bad /gi and /att tags           -->
<!-- 92-12-09 : MSM : correct typo as per LB                  -->
<!-- 92-12-07 : MSM : revise for publicatn, add examples      -->
<!-- 92-11-09 : MSM : suppress leading blanks after some tags -->
<!-- 92-11-09 : MSM : change COedcorr to COedcor              -->
<!-- P2 CO edit:  core tags for editorial interventions       -->
<!-- Revisions:                                               -->
<!-- 5-8 Oct 92 : LB changed xrefs; fiddled with prose somewhat;  -->
<!--              completed examples at end                   -->
<!-- 13 Sep 92 : MSM : made file, extract text from P247.doc  -->
<!>

<div2 id=COed><head>Simple Editorial Changes</head>

<p>As in editing a printed text, so in encoding a text in electronic
form, it may be necessary to accommodate editorial comment on the text
and to render account of any changes made to the text in preparing it.
The tags described in this section may be used to record such editorial
interventions, whether made by the encoder, by the editor of a printed
edition used as a copy text, by earlier editors, or by the copyists of
manuscripts.

<p>The tags described here handle most common types of editorial
intervention and stereotyped comment; where less structured
commentary of other types is to be included, it should be marked using
the <gi>note</gi> element described in section <ptr target=COno>.
Systematic interpretive annotation is also possible using the
various methods described in chapter <ptr target=SA>.  The examples
given here illustrate only simple cases of editorial intervention; in
particular, they permit economical encoding of two alternative
readings of a text only.  To encode more than two views of any one
segment of text, the mechanisms described in chapters <ptr target=SA>
and <ptr target=TC> must be used.

<p>The first two pairs of elements here discussed (<gi>sic</gi> and
<gi>corr</gi>, <gi>reg</gi> and <gi>orig</gi>) may both be used to
record simultaneously a text in its <soCalled>original</soCalled>,
uncorrected and unaltered form and also in an
<soCalled>edited</soCalled> form.  In this way they resemble the pair
<gi>abbr</gi> and <gi>expan</gi>, described in section <ptr
target=COnaab>.  Such paired elements enable software to move
automatically from one <soCalled>view</soCalled> of the text to the
other.

<p>Three categories of editorial intervention are discussed in this
section:
<list type=bullets>
<item>correction (or non-correction) of apparent errors
<item>regularization (or non-regularization) of variant, irregular,
non-standard, or eccentric forms
<item>editorial additions, suppressions, and omissions
</list>

<p>A more extended treatment of the use of these tags in
transcriptional and editorial work is given in chapter
<ptr target=PH>.

<div3 id=COedcor><head>Correction of Apparent Errors</head>

<p>When the copy text is manifestly faulty, an encoder or transcriber
may elect simply to correct it without comment.  For scholarly purposes,
it will often be more generally useful to record both the correction and
the original state of the text.  The elements described here enable this
to be done is such a way as not to distract the reader.

<list type=gloss>
<label><gi>sic</gi></label>
<item>contains text reproduced although apparently incorrect or

inaccurate.
Attributes include:
<list type=gloss>
<label><att>corr</att></label>
<item>gives a correction for the apparent error in the copy text.</item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for 
suggesting the correction held as the value of the 
<att>corr</att> attribute.</item>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to the 
correction held as the value of the <att>corr</att> 
attribute.</item>
</list>
</item>
<label><gi>corr</gi></label>
<item>contains the correct form of a passage apparently erroneous 
in
the
copy text.
Attributes include:
<list type=gloss>
<label><att>sic</att></label>
<item>gives the original form of the apparent error in the copy 
text.</item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for 
suggesting the correction held as the content of the 
<gi>corr</gi> element.</item>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to the 
correction held as the content of the <gi>corr</gi> 
element.</item>
</list>
</item>
</list>


<p>The following examples show alternative treatment of the same
material.  The copy text reads:

<q rend='display'>Another property of computer-assisted historical
research is that data modelling must permit any one textual feature or
part of a textual feature to be a part of more than one information
model and to allow the researcher to draw on several such models
simultaneously, for example, to select from a machine-readable text
those marginal comments which indicate that the date's mentioned in the
main body of the text are incorrect.</q>

<!-- Daniel I. Greenstein, "Encoding Standards for            -->
<!-- Computer-Aided Historical Research", in Modeling         -->
<!-- Historical Data, p. 101.                                 -->

<p>An encoder may choose to correct the typographic error, either
silently or with an indication that a correction has been made, as
follows:

<eg>
<![ CDATA [
 ... marginal comments which indicate that the
 <corr>dates</corr> mentioned in
 the main body of the text are incorrect.
]]>
</eg>

<p>Alternatively, the encoder may simply record the typographic
error without correcting it, either without comment or with a
<gi>sic</gi> element to indicate the error is not a transcription error
in the encoding:
<eg>
<![ CDATA [
 ... marginal comments which indicate that the
 <sic>date's</sic> mentioned in
 the main body of the text are incorrect.
]]>
</eg>

<p>If the encoder elects both to record the original source text
and to provide a correction for the sake of word-search
and other programs, either <gi>sic</gi> or <gi>corr</gi> may be used
with the appropriate attribute:

<eg>
<![ CDATA [
 ... marginal comments which indicate that the
 <sic corr='dates' resp=MSM>date's</sic> mentioned in
 the main body of the text are incorrect.
]]>
</eg>

<eg>
<![ CDATA [
 ... marginal comments which indicate that the
 <corr sic="date's" resp='MSM'>dates</corr> mentioned in
 the main body of the text are incorrect.
]]>
</eg>

If both readings are given, the choice between <gi>sic</gi> and
<gi>corr</gi> is largely a question of individual preference; since
both record the same information, either may be mechanically
transformed into the other.  If the original reading contains SGML
tags, it will prove more convenient to use <gi>sic</gi> than
<gi>corr</gi> (and vice versa if there are tags within the corrected
reading), since SGML tags are not recognized in attribute values.  If
both readings contain subordinate tags, then recourse <!-- may --> must
be had to the methods described in chapter <ptr target=TC>.

<!-- new material from PR replaces following para -->

<!-- < p>The <gi>sic</gi> and <gi>corr</gi> tags imply a      -->
<!-- degree of editorial certainty about error and its        -->
<!-- correction and should be strictly limited in use to      -->
<!-- cases where such certainty exists.  They are not         -->
<!-- intended for use in cases where emendation is            -->
<!-- conjectural; for these cases, the mechanisms proposed    -->
<!-- in chapter <ptr target=TC> are recommended.             -->

<p>The <att>cert</att> attribute on the <gi>sic</gi> and
<gi>corr</gi> elements permits a statement of the degree of editorial
confidence in a particular correction.  For example, using a
confidence scale of one to ten, an editor may indicate the
conjectural status of a correction by assigning a value to this
attribute of less than ten.  In the following instance, some
uncertainty is expressed concerning a commonly-accepted emendation:

<eg><![ CDATA [
An <corr sic='Antony' cert=8>Autumn</corr> it was,
That grew the more by reaping
]]>
</eg>
<!-- Antony and Cleopatra, Act 5, scene 2 -->
See further the discussion in section <ptr target=PHcc>.

<p>Where the correction takes the form of adding text, the encoder
must choose whether to use the <gi>corr</gi> (or <gi>sic</gi>)
tag, the <gi>add</gi> tag (see section <ptr target=COedadd> below),
or the more detailed facilities provided by the additional tag set for
primary source description. The following discussion may be helpful
when making this decision:

<!-- described in chapter the <gi>supplied</gi> tag,          -->
<!-- available when using the additional tagset for primary   -->
<!-- source transcription described in chapter <ptr          -->
<!-- target=PH>.  The following rules may be given to aid     -->
<!-- this choice:                                             -->

<list>
<item>where the correction is an addition by a scribe or author
in a manuscript or other primary source (typescript, proof or galley,
etc.) then either <gi>corr</gi> (or <gi>sic</gi>) or <gi>add</gi> might be
appropriate, depending on the circumstances.  The <gi>add</gi> tag is
more expressive, and may convey information on just how the addition
was performed (hand, place, etc.) which the <gi>corr</gi> tag cannot.
See further the discussion in section <ptr target=PHsu>.

<item>where the correction is an addition by a transcriber or editor,
correcting a perceived deficiency in the text but in circumstances where
there is no clearly assertable reason for the deficiency (as a
manuscript lacuna, or damage to the page) the <gi>corr</gi> tag should
be used.  The <gi>add</gi> tag should not be used in this case.

<item>where the correction is an addition by a transcriber or editor,
correcting a perceived deficiency in the text and where there is a
clearly assertable reason for the deficiency (as a manuscript lacuna, or
damage to the page) which the encoder wishes to record, or when
supplying text from a parallel version of the text, the
<gi>supplied</gi> element provided by the additional tag set for primary
source description should be used (see section <ptr target=PHcc>).

<!-- the <gi>supplied</gi> tag should be used with the        -->
<!-- <att>reason</att> attribute carrying the reason for the  -->
<!-- deficiency and hence the supplying of text.  The         -->
<!-- <gi>supplied</gi> tag should also be used when           -->
<!-- supplying text from a parallel version of the text.      -->
<!-- Neither the <gi>add</gi> nor <gi>corr</gi> tag should    -->
<!-- be used in these cases.                                  -->

</list>

<!-- (also removed first example since it didn;t seem to add  -->
<!-- very much                                                -->

<!-- <p>In this example, an editor corrects the source text   -->
<!-- by supplying a word omitted apparently by mistake:       -->

<!-- <eg><![ CDATA [ -->
<!--  ...and a very great <corr sic='' resp=DW>slaughter</corr> of the -->
<!-- Danes was made, and the part that escaped were saved by flight. -->
<!-- ]]> -->
<!-- </eg> -->

<!-- Here, a passage omitted from one source but present in another, -->
<!-- <q>A</q>, is supplied: -->

<!-- <eg><![ CDATA [ -->
<!--  ...they went both together up along the Thames, and a great -->
<!-- reinforcement came up to them both from the East Angles and the -->
<!-- Northumbrians.  <supplied resp=DW source=A>They then went up along -->
<!-- the Thames until they reached the Severn, then up along the -->
<!-- Severn</supplied> -->
<!-- ]]> -->
<!-- </eg> -->

<p>The formal definition of these elements is as follows:

<eg id=dcoedc>
<![ CDATA [
<!-- 6.5.1:  Editorial tags for correction                    -->
<!ELEMENT sic           - -  (%specialPara;)                    >
<!ATTLIST sic                %a.global;
          cert               CDATA               #IMPLIED
          corr               CDATA               #IMPLIED
          resp               IDREF               %INHERITED     >
<!ELEMENT corr          - -  (%specialPara;)                    >
<!ATTLIST corr               %a.global;
          cert               CDATA               #IMPLIED
          sic                CDATA               #IMPLIED
          resp               CDATA               %INHERITED     >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>


<div3 id=COedreg><head>Regularization and Normalization</head>

<p>When the source text makes extensive use of variant forms or
non-standard spellings, it may be desirable for a number of reasons to
<term rend='noindex'>regularize</term> it:  that is, to provide
<index level1='regularization'>
<soCalled>standard</soCalled> or <soCalled>regularized</soCalled> forms
equivalent to the non-standard forms.<note>In some contexts, the term
<mentioned>regularization</mentioned> has a narrower and more specific
significance than that proposed here:  the <gi>reg</gi> element may be
used for any kind of regularization, including normalization,
standardization, and modernization.</note>

<p>As with other such changes to the copy text, the changes may be made
silently (in which case the TEI header should specify the types of
silent changes made) or may be explicitly marked using the following
elements:

<list type=gloss>
<label><gi>reg</gi></label>
<item>contains a reading which has been regularized or normalized
in some sense.
Attributes include:
<list type=gloss>
<label><att>orig</att></label>
<item>gives the unregularized form of the text as found in the 
source copy.</item>
<label><att>resp</att></label>
<item>identifies the individual responsible for the 
regularization of the word or phrase.</item>
</list>
</item>
<label><gi>orig</gi></label>
<item>contains the original form of a reading, for which a

regularized form is given in an attribute value.
Attributes include:
<list type=gloss>
<label><att>reg</att></label>
<item>gives a regularized (normalized) form of the text.</item>
<label><att>resp</att></label>
<item>identifies the individual responsible for the 
regularization of the word or phrase.</item>
</list>
</item>
</list>


<p>Typical applications for these elements include the production of
editions intended for student or lay readers, linguistic research in
which spelling or usage variation is not the main question at issue,
production of spelling dictionaries, etc.

<p>Consider this 16th-century text:
<q rend=display>
how godly a dede it is to overthrowe so wicked a race
the world may judge:  for my part I thinke there canot
be a greater sacryfice to God.
</q>

<p>An encoder may choose to preserve the original spelling of this
text, but simply flag it as nonstandard by using the <gi>orig</gi>
element with no attributes specified, as follows:

<eg>
<![ CDATA [
how godly a <orig>dede</orig> it is to
<orig>overthrowe</orig> so wicked a race the
world may judge:  for my part I <orig>thinke</orig>
there <orig>canot</orig> be a greater
<orig>sacryfice</orig> to God.
]]>
</eg>

<p>Alternatively, the encoder may simply indicate that certain words
have been modernized by using the <gi>reg</gi> element with no
attributes specified, as follows:

<eg>
<![ CDATA [
how godly a <reg>deed</reg> it is to
<reg>overthrow</reg> so wicked a race the
world may judge:  for my part I <reg>think</reg>
there <reg>cannot</reg> be a greater
<reg>sacrifice</reg> to God.
]]>
</eg>

<p>More usefully, the encoder may elect to record both old and new
spellings, so that (for example) the same electronic text may serve as
the basis of an old- or new-spelling edition:

<eg>
<![ CDATA [
how godly a <reg orig='dede'>deed</reg> it is to
<reg orig='overthrowe'>overthrow</reg> so wicked a race the
world may judge:  for my part I <reg orig='thinke'>think</reg>
there <reg orig='canot'>cannot</reg> be a greater
<reg orig='sacryfice'>sacrifice</reg> to God.
]]>
</eg>

<p>Or the <gi>orig</gi> tag might be preferred
<eg>
<![ CDATA [
how godly a <orig reg='deed'>dede</orig> it is to
<orig reg='overthrow'>overthrowe</orig> so wicked a race the
world may judge:  for my part I <orig reg='think'>thinke</orig>
there <orig reg='cannot'>canot</orig> be a greater
<orig reg='sacrifice'>sacryfice</orig> to God.
]]>
</eg>
<!-- Edward Barkley, describing how Essex drove the Irish     -->
<!-- from the plains into the woods to freeze or famish in    -->
<!-- winter; quoted by Nicholas P. Canny, "The Ideology of    -->
<!-- English Colonization:  From Ireland to America," in      -->
<!-- *Colonial America:  Essays in Politics and Social        -->
<!-- Development*, 3d edition, ed.  Stanley N. Katz and John  -->
<!-- M. Murrin (New York:  Knopf, 1983), p. 53; Canny's       -->
<!-- footnote reads "See Devereux, *Lives of Devereux*, I,    -->
<!-- 30-31, for Essex to Burghley, July 20, 1573, and         -->
<!-- *ibid*, 37-39, for Essex to Privy Council, Sept. 29,     -->
<!-- 1573.  Barkley to Burghley, May 14, 1574, S.P. 63/46,    -->
<!-- no. 15, P.R.O."                                          -->

<p>The <att>resp</att> attribute should be used to specify the agency
responsible for the regularization.  This may be an identifiable
individual, for example an editor, or a descriptive phrase such as
<mentioned>copyist</mentioned>.  For example, in the first stanza of the Old
Norse poem <title>Gr&oacute;galdr</title>, the manuscript form
<mentioned>dura</mentioned> is usually regularized in modern editions to
<mentioned>dyra</mentioned> <gloss>doors</gloss>.  The manuscript's <q>vek ek
&thorn;ik dau&eth;ra dura</q> might thus be recorded together with its
regularization in two ways, as follows:

<eg>
<![ CDATA [
 vek ek &thorn;ik dau&eth;ra <reg orig='dura' resp=ed>dyra</reg>
]]>
</eg>
or:
<eg>
<![ CDATA [
 vek ek &thorn;ik dau&eth;ra <orig reg='dyra' resp=ed>dura</orig>
]]>
</eg>

<p>These elements are formally defined as follows:

<eg id=dcoedr>
<![ CDATA [
<!-- 6.5.2:  Editorial tags for regularization                -->
<!ELEMENT reg           - -  (%phrase.seq;)                     >
<!ATTLIST reg                %a.global;
          orig               CDATA               #IMPLIED
          resp               CDATA               #IMPLIED       >
<!ELEMENT orig          - -  (%phrase.seq;)                     >
<!ATTLIST orig               %a.global;
          reg                CDATA               #IMPLIED
          resp               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>


<div3 id=COedadd><head>Additions, Deletions and Omissions</head>

<p>The following elements are used to indicate when words or phrases
have been omitted from, added to, or marked for deletion from, a text.
Like the other editorial elements, they allow for a wide range of
editorial practices:

<list type=gloss>
<label><gi>gap</gi></label>
<item>indicates a point where material has been omitted in a

transcription, whether for editorial reasons described in 
the TEI
header, as part of sampling practice, or because 
the material is
illegible or inaudible.
Attributes include:
<list type=gloss>
<label><att>desc</att></label>
<item>gives a description of the omitted text.</item>
<label><att>reason</att></label>
<item>gives the reason for omission. Sample values include 
<q>sampling</q>, <q>illegible</q>, <q>inaudible</q>, 
<q>irrelevant</q>, <q>canceled</q>, <q>canceled and 
illegible</q>.</item>
<label><att>extent</att></label>
<item>indicates approximately how much text has been omitted from 
the transcription, in letters, minims, inches, or any 
appropriate unit, either because of editorial policy or 
because a deletion, damage or other cause has rendered 
transcription impossible.</item>
<label><att>resp</att></label>
<item>indicates the editor, transcriber or encoder responsible 
for the decision not to provide any transcription of the 
text and hence the application of the <gi>gap</gi> tag.</item>
</list>
</item>
<label><gi>unclear</gi></label>
<item>contains a word, phrase, or passage which cannot be 
transcribed
with certainty because it is illegible or 
inaudible in the source.
Attributes include:
<list type=gloss>
<label><att>reason</att></label>
<item>indicates why the material is hard to transcribe.</item>
<label><att>resp</att></label>
<item>indicates the individual responsible for the transcription 
of the letter, word or passage contained with the 
<gi>unclear</gi> element.</item>
</list>
</item>
<label><gi>add</gi></label>
<item>contains letters, words, or phrases inserted in the text by 
an
author, scribe, annotator or corrector.
Attributes include:
<list type=gloss>
<label><att>place</att></label>
<item>if the the addition is written into the copy text, 
indicates where the additional text is written.
Suggested values include:
<list type=gloss>
<label><term>verso</term></label>
<item>addition is made on verso of sheet</item>
<label><term>inline</term></label>
<item>addition is made in a space left in the witness by an 
earlier scribe</item>
<label><term>infralinear</term></label>
<item>addition is made below the line</item>
<label><term>left</term></label>
<item>addition is made in left margin</item>
<label><term>right</term></label>
<item>addition is made in right margin</item>
<label><term>supralinear</term></label>
<item>addition is made above the line</item>
<label><term>bottom</term></label>
<item>addition is made in bottom margin</item>
<label><term>opposite</term></label>
<item>addition is made on opposite page</item>
<label><term>mixed</term></label>
<item>addition is made somewhere, one or more of other values</item>
<label><term>top</term></label>
<item>addition is made in top margin</item>
</list></item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for 
identifying the hand of the addition.</item>
<label><att>hand</att></label>
<item>signifies the hand of the agent which made the addition.</item>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to the 
identification of the hand of the addition.</item>
</list>
</item>
<label><gi>del</gi></label>
<item>contains a letter, word or passage deleted, marked as 
deleted,
or otherwise indicated as superfluous or spurious 
in the copy text by an
author, scribe, annotator or 
corrector.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the type of deletion using any convenient 
typology.</item>
<label><att>status</att></label>
<item>may be used to indicate faulty deletions, e.g. strikeouts 
which include too much or too little text.</item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for 
identifying the hand of the deletion.</item>
<label><att>hand</att></label>
<item>signifies the hand of the agent which made the deletion.</item>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to the 
identification of the hand of the deletion.</item>
</list>
</item>

</list>


<p>Encoders may choose to omit parts of the copy text for reasons
ranging from illegibility of the source or impossibility of transcribing
it, to editorial policy, e.g. a systematic exclusion of poetry or prose
from an encoding.  The full details of the policy decisions concerned
should be documented in the TEI Header (see section <ptr target=HD5>).
Each place in the text at which omission has taken place should be
marked with a <gi>gap</gi> element, with optionally further information
about the reason for the omission, its extent and the person or agency
responsible for it, as in the following examples:

<eg><![ CDATA [
 <gap desc="Prose commentary" reason="sampling"
       extent="120 lines" resp=PR>
]]>
</eg>

<eg><![ CDATA [
 ... Their arrangement with respect to Jupiter and to each
 other was as follows:
 <gap desc="diagram" reason="sampling" extent="2 cm x 1 col">
 That is, there were two starts on the easterly side and one
 to the west; ...
]]>
</eg>
<!-- Galileo, The Starry Messenger, quoted by Tufte,          -->
<!-- Envisioning Information, p. 97.  Siderevs Nuncivs ...    -->
<!-- (Venetiis:  Apud Thomam Baglionum, 1610).                -->
<!-- Figure looks like this:                                  -->
<!--                                                          -->
<!-- East         *        *  O      *                   West -->
<!--                                                          -->

<eg><![ CDATA [
 <gap reason="illegible" desc="ink blot" extent="two words">
]]>
</eg>

<eg><![ CDATA [
 <gap reason='overwriting, illegible'
       resp='H1'
       extent='8 chars'>
]]>
</eg>

<p>The <gi>add</gi> and <gi>del</gi> elements may be used to record
where words or phrases have been added or deleted in the copy text.
They are not appropriate where longer passages have been added or
deleted, which span several SGML elements; for these, the elements
<gi>addSpan</gi> and <gi>delSpan</gi>, or other mechanisms described in
section <ptr target=PH> must be used.

<p>Additions to a text may be recorded for a number of reasons.
Sometimes they are marked in a distinctive way in the source text, for
example by brackets or insertion above the line
(<term rend='noindex'>supralinear</term> insertion),
<index level1='additions' level2='supralinear'>
<index level1='insertions' level2='supralinear'>
<index level1='supralinear insertions'>
as in the following example, taken from a 19th century manuscript:

<eg>
<![ CDATA [
The story I am going to relate is true as to its main
facts, and as to the consequences <add
place='supralinear' resp='auth'>of these facts</add>
from which this tale takes its title.
]]>
</eg>
<!-- Mrs Gaskell, The Grey Woman, MS -->

<p>The <gi>add</gi> element should not be used to mark editorial
changes, such as supplying a word omitted by mistake from the source
text or a passage present in another version.  In these cases, either
the <gi>corr</gi> or <gi>supplied</gi> tags should be used, as discussed
above in section <ptr target=COedcor>, and in section <ptr
target=PHcc>, respectively.

<!-- LB added following discussion of unclear -->

<p>The <gi>unclear</gi> element is used to mark passages in the original
which cannot be read with confidence, or about which the transcriber is
uncertain for other reasons, as for example when transcribing a
partially inaudible or illegible source.  Its <att>reason</att> and
<att>resp</att> attributes are used, as with the <gi>gap</gi> element,
to indicate the cause of uncertainty and the person responsible for the
conjectured reading.

<p>For example:

<eg>
<![ CDATA [
<l>And where the sandy mountain Fenwick scald</>
<l><unclear reason="ink blot" resp=LB>The</unclear> sea between
   yet hence his pray'r prevail'd</>
]]>
</eg><!-- Marvell, Horatian ode, ms pages from Bod MS Eng Poet d.49 -->

or from a spoken text:

<eg>
<![ CDATA [

and then <unclear reason='passing truck'>marbled queen</unclear>

]]>
</eg>

Where the material affected is entirely illegible or inaudible, the
<gi>gap</gi> element discussed above should be used in preference.

<!-- material here cut at PR's suggestion -->

<p>The <gi>del</gi> element is used to mark material which is deleted in
the source but which can still be read with some degree of confidence,
as opposed to material which has been omitted by the encoder or
transcriber either because it is entirely illegible or for some other
reason.  This is of particular importance in transcribing manuscript
material, though deletion is also found in printed texts, sometimes for
humorous purposes:

<eg>
<![ CDATA [
<l>One day I will sojourn to your shores</>
<l>I live in the middle of England</>
<l>But!</>
<l>Norway! My soul resides in your watery
   <del type='overstrike'>fiords fyords fiiords</del></>
<l>Inlets.</>
]]>
</eg> <!-- S. Townsend: The growing pains of Adrian Mole (1984) p.43 -->

<p>The <att>type</att> attribute may be used to distinguish different
methods of deletion in manuscript or typescript material, as in this
line from the typescript of Eliot's <title>Waste Land</title>:

<eg>
<![ CDATA [
<l><del type=overtyped>Mein</del> Frisch
   <del type=overstrike>schwebt</del> weht der Wind</>
]]>
</eg>
<p>Deletion in manuscript or typescript is often associated with
addition:

<eg>
<![ CDATA [
<l><del type=overstrike>Inviolable</del>
   <add place=infralinear>Inexplicable</add>
   splendour of Corinthian white and gold</>
]]>
</eg> <!-- The Waste Land. a facsimile and transcript... edited by -->
      <!-- Valerie Eliot. Faber, 1971. p.37 -->


<p>The <gi>del</gi> element should not be used where the deletion is
such that material cannot be read with confidence, or read at all, or
where the material has been omitted by the transcriber or editor for
some other reason.  Where the material cannot be read with confidence
following deletion, the <gi>unclear</gi> tag should be used with the
<att>reason</att> attribute indicated that the difficulty of
transcription is due to deletion.  Where material has been omitted by
the transcriber or editor, this may be indicated by use of the
<gi>corr</gi> (or <gi>sic</gi>) and <gi>gap</gi> elements.  Observe that
the distinction between recommended uses of the <gi>del</gi>,
<gi>corr</gi> and <gi>gap</gi> tags parallels the distinction drawn
between the <gi>add</gi>, <gi>corr</gi> and <gi>supplied</gi> tags in
section <ptr target=Coedcor> and section <ptr target=PHcc>:

<list>
<item>where the correction is a deletion by a scribe or author in a
manuscript or other primary source (typescript, proof or galley, etc.)
then either <gi>corr</gi> (or <gi>sic</gi>) or <gi>del</gi> might be
appropriate, depending on the circumstances.  The <gi>del</gi> tag is
more expressive, and may convey information on just how the deletion
was performed (hand, place, etc.) which the <gi>corr</gi> tag cannot.
See further the discussion in section <ptr target=PHsu>.

<item>where the correction is a deletion by a transcriber or editor,
correcting a perceived superfluity in the text but in circumstances
where there is no clearly assertable reason for the superfluity (as a
spurious addition) the <gi>corr</gi> tag should be used.  The
<gi>del</gi> tag should not be used in this case.

<item>where the correction is a deletion by a transcriber or editor,
correcting a perceived superfluity in the text where there is a
clearly assertable reason for the superfluity (as a spurious
addition) the <gi>gap</gi> tag should be used with the
<att>reason</att> attribute carrying the reason for the superfluity
and hence the deletion of text.  Neither the <gi>del</gi> nor
<gi>corr</gi> tag should be used in these cases.
</list>


<p>For any detailed transcription of a manuscript or typescript with
more than trivial amounts of alteration, the reader should consult
chapter <ptr target=TC>, and chapter <ptr target=PH>.

<p>These elements are formally defined as follows:

<eg id=dcoeda>
<![ CDATA [
<!-- 6.5.3:  Other editorial tags                             -->
<!ELEMENT gap           - O  EMPTY                              >
<!ATTLIST gap                %a.global;
          desc               CDATA               #IMPLIED
          extent             CDATA               #IMPLIED
          resp               IDREF               %INHERITED
          hand               IDREF               %INHERITED
          reason             CDATA               #IMPLIED
          agent              CDATA               #IMPLIED       >
<!ELEMENT add           - -  (%specialPara;)                    >
<!ATTLIST add                %a.global;
          cert               CDATA               #IMPLIED
          place              CDATA               #IMPLIED
          resp               IDREF               %INHERITED
          hand               IDREF               %INHERITED     >
<!ELEMENT del           - -  (%phrase.seq;)                     >
<!ATTLIST del                %a.analysis;
                             %a.linking;
                             %a.terminology;
          id                 ID                  #IMPLIED
          lang               IDREF               %INHERITED
          n                  CDATA               #IMPLIED
          cert               CDATA               #IMPLIED
          resp               IDREF               %INHERITED
          hand               IDREF               %INHERITED
          status             CDATA               'unremarkable'
          rend               CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
<!ELEMENT unclear       - O  (%paraContent;)                    >
<!ATTLIST unclear            %a.global;
          cert               CDATA               #IMPLIED
          resp               CDATA               %INHERITED
          hand               IDREF               %INHERITED
          reason             CDATA               #IMPLIED
          agent              CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>



<!-- COxr Cross References                                    -->
<!-- $Id: p2coxr.odd,v 1.3 1998/01/28 11:09:58 cmsmcq Exp $ -->
<!-- $Log: p2coxr.odd,v $
# Revision 1.3  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.2  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# -->
<!-- Revisions:                                               -->
<!-- 94-03-25 : MSM : typos corrected as per J. Lavagnino     -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- 92-12-10 : MSM : correct references to Loc, now pointer  -->
<!-- 92-12-09 : MSM : introduce class Loc explicitly          -->
<!-- 92-12-09 : MSM : cosmetic copy editing                   -->
<!-- 92-12-09 : MSM : add space after some end-tags           -->
<!-- 92-12-09 : MSM : add (vacuous!) example of targOrder     -->
<!-- 92-12-07 : MSM : complete run-through for publication    -->
<!-- 92-12-07 : MSM : begin cleanup for publication           -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<div2 id=COxr><head>Simple Links and Cross References</head>

<p>Cross-references or links between one location in a document and
another, or between one location and several others, may be encoded
using the elements <gi>ptr</gi> and <gi>ref</gi>, as discussed in this
section.  These elements both <soCalled>point</soCalled> from one
location in a document, the place that the element itself appears, to
another (or to several), specified by the <att>target</att> attribute.
Linkages of several other kinds are also provided for in these
guidelines; see further chapter <ptr target=SA>.

<p>The pointing facility of these elements depends on the ability to
supply a unique identifier for any element in the TEI scheme, using the
global <att>id</att> attribute.  Where the object or objects of a
cross-reference are not identifiable in this way, either because they
are located in a distinct SGML document or because no <att>id</att>
attribute is available, the elements <gi>xptr</gi> or <gi>xref</gi> may
be used instead.<note>See chapter <ptr target=SA>, for a discussion of
these elements and the extended syntax they provide for <socalled>
hypertext</socalled> links.</note> Alternatively, if no explicit link is
to be encoded, but it is simply required to mark the phrase as a
cross-reference, the <gi>ref</gi> element may be used without a
<att>target</att> attribute.

<list type=gloss>
<label><gi>ptr</gi></label>
<item>defines a pointer to another location in the current 
document
in terms of one or more identifiable elements.
Attributes include:
<list type=gloss>
<label><att>target</att></label>
<item>specifies the destination of the pointer as one or more 
SGML identifiers</item>
</list>
</item>
<label><gi>ref</gi></label>
<item>defines a reference to another location in the current 
document,
in terms of one or more identifiable elements, 
possibly modified by
additional text or comment.
Attributes include:
<list type=gloss>
<label><att>target</att></label>
<item>specifies the destination of the reference as one or more 
SGML identifiers</item>
</list>
</item>
</list>


<p>The elements <gi>ptr</gi> and <gi>ref</gi> share, as members of the
element class <ident type=class>pointer</ident>, the following
attributes:

<list type=gloss>
<label><att>type</att></label>
<item>categorizes the pointer in some respect, using any 
convenient set of categories.</item>
<label><att>resp</att></label>
<item>specifies the creator of the pointer.</item>
<label><att>crdate</att></label>
<item>specifies when the pointer was created.</item>
<label><att>targType</att></label>
<item>specifies the kinds of elements to which this pointer may 
point.</item>
<label><att>targOrder</att></label>
<item>where more than one identifier is supplied as the value of 
the <att>target</att> attribute, this attribute specifies 
whether the order in which they are supplied is 
significant.
Legal values are:
<list type=gloss>
<label><term>U</term></label>
<item>Unspecified: the order in which IDREFs are specified as the 
value of a <att>target</att> attribute may or may not be 
significant.</item>
<label><term>Y</term></label>
<item>Yes: the order in which IDREFs are specified as the value 
of a <att>target</att> attribute should be followed when 
combining the targeted elements.</item>
<label><term>N</term></label>
<item>No: the order in which IDREFs are specified as the value of 
a <att>target</att> attribute has no significance when 
combining the targeted elements.</item>
</list></item>
<label><att>evaluate</att></label>
<item>specifies the intended meaning when the target of a pointer 
is itself a pointer.
Sample values include:
<list type=gloss>
<label><term>none</term></label>
<item>no further evaluation of targets is carried out beyond that 
needed to find the element specified in the pointer's 
target.</item>
<label><term>one</term></label>
<item>if the element pointed to is itself a pointer, then its 
target (whether a pointer or not) is taken as the target of 
this pointer.</item>
<label><term>all</term></label>
<item>if the element pointed to is itself a pointer, then the 
target of that pointer will be taken, and so on, until an 
element is found which is not a pointer.</item>
</list></item>
</list>

<p>The shared attributes of the two elements may be used in the same
way; the difference between the elements is that while the <gi>ptr</gi>
element is empty, the <gi>ref</gi> element may contain phrases
specifying, or defining more exactly, the target of a cross reference,
which form the content of the element.  Since its content thus serves as
a human-readable pointer, in the simplest case a <gi>ref</gi> element
need not identify its target in any other way.  For example:

<eg>
<![ CDATA [
    See <ref>section 12 on page 34</ref>.
]]>
</eg>

<p>More usually, it will be desirable to identify the target of the
cross-reference using the <att>target</att> attribute, so that
processing software can access it directly, for example to implement a
linkage or to generate an appropriate reference.  Assuming that section
12 in the previous example has been tagged <tag>div1 id=SEC12</tag>, the
same cross reference might more exactly be encoded as

<eg>
<![ CDATA [
    See especially <ref target=SEC12>section 12 on page 34</ref>.
]]>
</eg>

<p>If the text for the cross reference is to be generated according to a
fixed pattern, or if no text is to appear in the body of the cross
reference, the <gi>ptr</gi> element would be used as follows:

<eg>
<![ CDATA [
    See in particular <ptr target=sec12>.
]]>
</eg>

<p>A cross-reference may point to any number of locations simultaneously,
simply by giving more than one identifier as the value of its
<att>target</att> attribute.  This may be particularly useful where
an analytic index is to be encoded, as in the following example:
<eg>
<![ CDATA [
    <list>
    <item>Saints aid rejected in mel. <ptr target=p299></item>
    <item>Sallets censured <ptr target="p143 p144"></item>
    <item>Sanguine mel. signs <ptr target="p263 p312 p332"></item>
    <item>Scilla or sea onyon, a purger of mel. <ptr target=p442></item>
   <!-- ... -->
    </list>
]]>
</eg>
<!-- Burton: Anatomy of Melancholy, 16th ed 1651, reprinted   -->
<!-- 1846, p743                                               -->

Here the targets of the cross references are simply page numbers; it is
assumed that corresponding elements with identifiers <code
type=val>p299</code> <code type=val>p143</code>, etc. have been provided
in the body of the text.  If it is desired to check that the target
elements are of a particular type, the <att>targType</att> (target type)
attribute may be specified:

<eg>
<![ CDATA [
    <list>
    <item>Saints aid rejected in mel <ptr target=p299 targType=pb></item>
    <item>Sallets censured <ptr target="p143 p144" targType=pb></item>
    <!-- ... -->
    </list>
]]>
</eg>

Here, a processing application can check that the elements with
identifiers <code type=val>p299</code>, <code type=val>p143</code>, and
<code type=val>p144</code> are all <gi>pb</gi> (page-break) elements.
It is a semantic error in a text if the targets given do not match the
values specified on a <att>targType</att> attribute.

<p>The <att>type</att> and <att>resp</att> attributes may be used, as
elsewhere, to categorize the cross reference according to any system of
importance to the encoder and to supply a code identifying the person or
agency responsible for the cross reference.  If bibliographic references
require special processing (e.g. in order to provide a consistent
short-form reference), they might be tagged thus:

<eg>
<![ CDATA [
 Similar forms, often called <term rend='ldquo
 rdquo'>rewriting systems</term>, have a long
 history among mathematicians, but the specific form
 of <ptr targType=fig target=Fig22> was first
 studied extensively by Chomsky <ptr type=bibliog
 targType='bibl bibl.struct bibl.full' target=Chom59>.
]]>
</eg>

<!-- Dick Grune and Ceriel J. H. Jacobs, Parsing              -->
<!-- Techniques:  A Practical Guide (New York, London:        -->
<!-- Ellis Horwood, 1990), p. 24.                             -->

Here <code type=frag>type=bibliog</code> signals for the processing
appropriate to a bibliographic reference, while <q>targType='bibl
bibl.struct bibl.full'</q> restricts the legal targets to bibliographic
elements, and <code type=frag>target=Chom59</code> indicates which
bibliographic element actually is being referred to.  For further
discussion of bibliographic references, see section <ptr
target=CObixr>.

<p>If the order in which the objects of a multi-headed cross reference
are specified is of importance, the <att>targOrder</att> (target order)
attribute should be specified.

<!-- example needed -->

<eg>
<![ CDATA [
<p>The following discussions of this topic should
be consulted for further information:
<ptr target='ch3 sec332 sec45 sec722' targOrder=Y>
]]>
</eg>

<p>The <gi>ptr</gi> and <gi>ref</gi> tags have many applications in
addition to the simple cross-referencing facilities illustrated in this
section.  In conjunction with the analytic tools discussed in chapters
<ptr target=SA>, <ptr target=AI>, and <ptr target=FS>, they may be
used to link analyses of a text to their object, to combine
corresponding segments of a text, or to align segments of a text with a
temporal or other axis or with each other.

<p>These elements are formally defined as follows:
<eg id=dcoxr>
<![ CDATA [
<!-- 6.6:  Simple cross references                            -->
<!ENTITY % a.pointer '
          crdate             CDATA               #IMPLIED
          evaluate           (all | one | none)  #IMPLIED
          resp               CDATA               #IMPLIED
          targOrder          (Y | N | U)         U
          type               CDATA               #IMPLIED
          targType           NAMES               #IMPLIED'      >
<!ELEMENT ptr           - O  EMPTY                              >
<!ATTLIST ptr                %a.global;
                             %a.pointer;
          target             IDREFS              #REQUIRED      >
<!ELEMENT ref           - -  (%paraContent)                     >
<!ATTLIST ref                %a.global;
                             %a.pointer;
          target             IDREFS              #IMPLIED       >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>




<!-- COli Lists (P1 5.3.8)                                    -->
<!-- $Id: p2coli.odd,v 1.3 1994/03/27 21:45:15 msmcq Exp $ -->
<!-- $Log: p2coli.odd,v $
# Revision 1.3  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# -->
<!-- P2.COli: Lists                                           -->
<!-- Revisions:                                               -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- 92-12-09 : MSM : cosmetic copy editing                   -->
<!-- 92-12-09 : MSM : add space after some end-tags           -->
<!-- 92-12-07 : MSM : revise for release                      -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<!-- 92-11-09 : MSM : defang < note > in comment              -->
<!-- 20 oct : LB:   add some examples; reorder somewhat       -->
<!-- 1-7 oct 92 : LB : change ids to new scheme               -->
<!-- 24 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     -->
<!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  -->
<!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0 sec. 5.3.8       -->

<div2 id=COli><head>Lists</head>

<p>The following elements are provided for the encoding of lists,
their constituent items, and the labels or headings associated
with them:

<list type=gloss>
<label><gi>list</gi></label>
<item>contains any sequence of items organized as a list.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>describes the form of the list.
Suggested values include:
<list type=gloss>
<label><term>ordered</term></label>
<item>list items are numbered or lettered.</item>
<label><term>bulleted</term></label>
<item>list items are marked with a <socalled>bullet</socalled> or 
other typographic device.</item>
<label><term>gloss</term></label>
<item>each list item glosses some term or concept, which is given 
by a <gi>label</gi> element preceding the list item.</item>
<label><term>simple</term></label>
<item>list items are not numbered or bulleted.</item>
</list></item>
</list>
</item>
<label><gi>item</gi></label>
<item>contains one component of a list.
Attributes include:
<list type=gloss>
<label><att>n</att></label>
<item>indicates the number (or letter, or other enumerator) borne 
by this list item in the copy text.</item>
</list>
</item>
<label><gi>label</gi></label>
<item>contains the label associated with an item in a list; in

glossaries, marks the term being defined.</item>
<label><gi>head</gi></label>
<item>contains any heading, for example, the title of a section,

or the heading of a list or glossary.</item>
<label><gi>headLabel</gi></label>
<item>contains the heading for the label or term column in a

glossary list or similar structured list.</item>
<label><gi>headItem</gi></label>
<item>contains the heading for the item or gloss column in a

glossary list or similar structured list.</item>
</list>


<p>The <gi>list</gi> element should be used to mark any kind of
<term rend='noindex'>list</term>:
numbered, lettered, bulleted, or unmarked.  Lists formatted as such in
the copy text should in general be encoded using this element, with an
appropriate value for the <att>type</att> attribute.  Lists given as
run-on text may also be encoded using this element, where this is felt
to be appropriate.

<p>Each distinct item in the list should be encoded as a distinct
<gi>item</gi> element.  If the numbering or other identification for the
items in a list is unremarkable and may be reconstructed by any
processing program, no enumerator need be specified.  If however an
enumerator is retained in the encoded text, it may be supplied either by
using the <att>n</att> attribute on the <gi>item</gi> element, or by
using a <gi>label</gi> element.  The following examples are thus
equivalent:

<eg><![ CDATA [
I will add two facts, which have seldom occurred in
the composition of six, or at least of five quartos.
<list type=ordered rend=runon>
<label>(1)</><item>My first rough manuscript, without any
intermediate copy, has been sent to the press.</item>
<label>(2)</><item>Not a sheet has been seen by any human
eyes, excepting those of the author and the printer:
the faults and the merits are exclusively my own.</item>
</list>
]]>
</eg>
<eg><![ CDATA [
I will add two facts, which have seldom occurred in
the composition of six, or at least of five quartos.
<list type=ordered rend=runon>
<item n='1'>My first rough manuscript, without any
intermediate copy, has been sent to the press.</>
<item n='2'>Not a sheet has been seen by any human
eyes, excepting those of the author and the printer:
the faults and the merits are exclusively my own.</>
</list>
]]>
</eg>

The two styles may not be mixed in the same list:  if one item is
preceded by a label, all must be.

<p>A list need not necessarily be displayed in list format.  For
example,

<eg>
<![ CDATA [
On those remote pages it is written that animals are
divided into <list><item n='a'>those that belong to the
Emperor,</><item n='b'> embalmed ones, </><item n='c'> those
that are trained, </><item n='d'> suckling pigs, </><item n='e'>
mermaids,  </><item n='f'> fabulous ones, </><item n='g'> stray
dogs, </><item n='h'> those that are included in this
classification, </><item n='i'> those that tremble as if they
were mad, </><item n='j'> innumerable ones, </><item n='k'> those
drawn with a very fine camel's-hair brush, </><item n='l'>
others, </><item n='m'> those that have just broken a flower
vase, </><item n='n'> those that resemble flies from a
distance.</></list>
]]>
</eg>
<!-- Borges, tr. R. Simms 'The analytical language of John Wilkins' -->
<!-- in Monegal & Reid, Borges: a reader, (Dutton, 1981), p 141 -->

<p>A list may be given a heading or title, for which the <gi>head</gi>
element should be used, as in the next example, which also demonstrates
simple use of the <gi>label</gi> element to mark a tabular or glossary
list in which each item is associated with a word or phrase rather than
a numeric or alphabetic enumerator:

<eg>
<![ CDATA [
<list type=gloss>
<head>Report of the conduct and progress of Ernest Pontifex.
Upper Vth form &mdash half term ending Midsummer 1851</head>
<label>Classics</><item>Idle listless and unimproving</>
<label>Mathematics</><item>ditto</>
<label>Divinity</><item>ditto</>
<label>Conduct in house</><item>Orderly</>
<label>General conduct</><item>Not satisfactory, on account
of his great unpunctuality and inattention to duties</>
</list>
]]>
</eg><!-- S Butler, Way of all Flesh, -->

<p>In such a list, the individual items have internal structure.  In
complex cases, where list items contain many components, the list is
better treated as a <term rend='noindex'>table</term>, <index
level1='tables' level2='and lists'> on which see chapter <ptr type=div1
target=FT>.  A particularly important instance of the simple two-column
table is the <soCalled>glossary list</soCalled>, which should be marked
by the tag <tag>list type=gloss</tag>.  In such lists, each
<gi>label</gi> element contains a term and each <gi>item</gi> its gloss;
it is a semantic error for a list tagged with <code
type=frag>type=gloss</code> not to have labels.  For example:

<!-- Moreland and Fleischer, Latin:  An Intensive Course, 53. -->

<eg>
<![ CDATA [
<list type=gloss>
<head>Unit Three -- Vocabulary</head>
<label lang=la>acerbus, -a, -m       </><item>bitter, harsh</>
<label lang=la>ager, agr&imacr;, M.  </><item>field</>
<label lang=la>audi&omacr;, &imacr;re,
       &imacr;v&imacr;, &imacr;tus   </><item>hear, listen (to)</>
<label lang=la>bellum, -&imacr;, N.  </><item>war</>
<label lang=la>bonus, -a, -um        </><item>good</>
<!-- etc. -->
</list>
]]>
</eg>

Additionally, the  <gi>term</gi> and <gi>gloss</gi> elements discussed
in section <ptr target=COhqu> might be used to make explicit the role
that each column in the glossary list has, as follows:

<eg>
<![ CDATA [
<list type=gloss>
<head>Unit Three -- Vocabulary</head>
<label><term lang=la>acerbus, -a, -m</term></>
<item><gloss>bitter, harsh</gloss></item>
<label><term lang=la>ager, agr&imacr;, M. </term></>
<item><gloss>field</gloss></item>
<label><term lang=la>audi&omacr;, &imacr;re,
       &imacr;v&imacr;, &imacr;tus  </term></>
<item><gloss>hear, listen (to)</gloss></item>
<label><term lang=la>bellum, -&imacr;, N. </term></>
<item><gloss>war</gloss></item>
<label><term lang=la>bonus, -a, -um</term></>
<item><gloss>good</gloss></item>
<!-- etc. -->
</list>
]]>
</eg>

Note in the above examples the use of the global <att>lang</att>
attribute to specify on the <gi>label</gi> (or <gi>term</gi>) element
what language the term is from.  For further discussion of the
<att>lang</att> attribute see section <ptr type=div2 target=STga>, and
section <ptr type=div2 target=CHsh>.  A more elaborate markup for this
glossary would distinguish the headword forms from the grammatical
information (principal parts and gender), using tags described more
fully in chapters <ptr type=div1 target=TE> or <ptr type=div1
target=DI>.

<p>In addition to the <gi>head</gi> element used to supply
a title or heading for the whole list, headings for the two
columns of a glossary-style list may be specified using
the two special elements <gi>headLabel</gi> and <gi>headItem</gi>:

<eg><![ CDATA [
The simple, straightforward statement of an idea is
preferable to the use of a worn-out expression.
<list type=gloss>
<headLabel>TRITE</>
<headItem>SIMPLE, STRAIGHTFORWARD</>
<label>bury the hatchet  </><item>stop fighting, make peace</>
<label>at loose ends     </><item>disorganized</>
<label>on speaking terms </><item>friendly</>
<label>fair and square   </><item>completely honest</>
<label>at death's door   </><item>near death</>
</list>
]]>
</eg><!-- Warriner's English Composition p. 280                    -->

<p>The elements <gi>label</gi>, <gi>head</gi>, <gi>headLabel</gi>, and
<gi>headItem</gi> may contain only phrase-level elements.  The
<gi>item</gi> element however may contain paragraphs or other
<soCalled>chunks</soCalled>, including other lists.  In this example, a
glossary list contains two items, each of which is itself a simple list:

<eg>
<![ CDATA [
<list type=gloss><label>EVIL</label>
<item><list type=simple>
   <item>I am cast upon a horrible desolate island, void
          of all hope of recovery.</item>
   <item>I am singled out and separated as it were from
         all the world to be miserable.</item>
   <item>I am divided from mankind &mdash a solitaire; one
           banished from human society.</item>
     </list> <!-- end of first nested list --></item>
<label>GOOD</label>
<item><list type=simple>
     <item>But I am alive; and not drowned, as all my
              ship's company were.</item>
     <item>But I am singled out, too, from all the ship's
             crew, to be spared from death...</item>
     <item>But I am not starved, and perishing on a barren place,
            affording no sustenances....</item>
     </list><!-- end of second nested list --></item>
</list><!-- end of glossary list -->
]]>
</eg>
<!-- D Defoe,  Robinson Crusoe  -->

<p>Lists of different types may be nested to arbitrary depths in this
way.

<p>The formal declarations for lists and list items are as follows.
<eg id=dcoli>
<![ CDATA [
<!-- 6.7:  Lists and List Items                               -->
<!ELEMENT list          - -  (head?, ( (item*) | (headLabel?, 
                             headItem?, (label, item)*)))       >
<!ATTLIST list               %a.global;
          type               CDATA               simple         >
<!ELEMENT item          - O  (%specialPara;)                    >
<!ATTLIST item               %a.analysis;
                             %a.linking;
                             %a.terminology;
          id                 ID                  #IMPLIED
          lang               IDREF               %INHERITED
          rend               CDATA               #IMPLIED
          n                  CDATA               #IMPLIED       >
<!ELEMENT label         - o  (%phrase.seq;)                     >
<!ATTLIST label              %a.global;                         >
<!ELEMENT head          - O  (%paraContent;)                    >
<!ATTLIST head               %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT headLabel     - O  (%phrase.seq;)                     >
<!ATTLIST headLabel          %a.global;                         >
<!ELEMENT headItem      - O  (%phrase.seq;)                     >
<!ATTLIST headItem           %a.global;                         >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>



<!-- COno Notes (P1 5.3.9)                                    -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- $Id: p2cono.odd,v 1.9 1998/01/28 11:09:58 cmsmcq Exp $ -->
<!-- $Log: p2cono.odd,v $
# Revision 1.9  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.8  1994/08/29  15:43:52  cmsmcq
# Fixes for unreachability problems
#
# Revision 1.7  1994/04/01  16:18:13  msmcq
# Suppress SPAN (moved to AI)
#
# Revision 1.6  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
#
# Revision 1.5  1994/03/01  03:53:49  msmcq
# suppress FILE attribute (was causing double declarations)
# -->
<!-- P2.234 : Notes                                           -->
<!-- Revisions:                                               -->
<!-- 10 jan 98 : LB : fix egs -->
<!-- 94-08-04 : MSM : add note that INDEX is member of        -->
<!-- 94-08-04 : MSM : METADATA class.                         -->
<!-- 94-03-30 : MSM : suppress span (has moved to AI)         -->
<!-- 94-02-28 : MSM : suppress FILE att on dCOno              -->
<!-- 21 dec : LB : change target /target.end on span to from/to -->
<!-- 93-06-02 : L B : rename div.gen as divGen                -->
<!-- 92-12-10 : MSM : correct typo in level3/level4 on index  -->
<!-- 92-12-09 : MSM : marginalia are not all notes            -->
<!-- 92-12-09 : MSM : spell check for publication             -->
<!-- 92-12-09 : MSM : add space after some end-tags           -->
<!-- 92-12-09 : MSM : add documentation of divGen            -->
<!-- 92-12-06 : MSM : add index tags                          -->
<!-- 92-11-17 : MSM : remove non-SGML eof character           -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<!-- 5 Oct 92: LB : change IDs, move taglist to start, add eg -->
<!-- 14 May 92 : CMSMcQ : revise.                             -->
<!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     -->
<!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  -->
<!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->

<div2 id=COno><head>Notes, Annotation, and Indexing</head>
<div3 id=COnono><head>Notes and Simple Annotation</head>

<p>The following elements are provided for the encoding of
discursive notes, either already present in the copy text or
supplied by the encoder:

<list type=gloss>
<label><gi>note</gi></label>
<item>contains a note or annotation.
Attributes include:
<list type=gloss>
<label><att>n</att></label>
<item>indicates the symbol or number used to mark the note's 
point of attachment to the main text.</item>
<label><att>type</att></label>
<item>describes the type of note.</item>
<label><att>resp</att></label>
<item>indicates who is responsible for the annotation: author, 
editor, translator, etc.
Sample values include:
<list type=gloss>
<label><term>auth[or]</term></label>
<item>note originated with the author of the text.</item>
<label><term>ed[itor]</term></label>
<item>note added by the editor of the text.</item>
<label><term>(initials)</term></label>
<item>note added by the individual indicated by the initials.</item>
<label><term>comp[iler]</term></label>
<item>note added by the compiler of a collection.</item>
<label><term>tr[anslator]</term></label>
<item>note added by the translator of a text.</item>
<label><term>transcr[iber]</term></label>
<item>note added by the transcriber of a text into electronic 
form.</item>
</list></item>
<label><att>place</att></label>
<item>indicates where the note appears in the source text.
Sample values include:
<list type=gloss>
<label><term>inline</term></label>
<item>note appears as a marked paragraph in the body of the text.</item>
<label><term>left</term></label>
<item>note appears in left margin.</item>
<label><term>foot</term></label>
<item>note appears at foot of page.</item>
<label><term>right</term></label>
<item>note appears in right margin.</item>
<label><term>app[aratus]</term></label>
<item>note appears in the apparatus at the foot of the page.</item>
<label><term>interlinear</term></label>
<item>note appears between lines of the text.</item>
<label><term>end</term></label>
<item>note appears at end of chapter or volume.</item>
</list></item>
<label><att>anchored</att></label>
<item>indicates whether the copy text shows the exact place of 
reference for the note.
Legal values are:
<list type=gloss>
<label><term>yes</term></label>
<item>copy text indicates the place of attachment for the note.</item>
<label><term>no</term></label>
<item>copy text indicates no place of attachment for the note.</item>
</list></item>
<label><att>target</att></label>
<item>indicates the point of attachment of a note, or the 
beginning of the span to which the note is attached.</item>
<label><att>targetEnd</att></label>
<item>points to the end of the span to which the note is 
attached, if the note is not embedded in the text at that 
point.</item>
</list>
</item>
</list>

<!-- <tagDesc tagDoc=span                                     -->
<!--          atts='resp type value from to'>                 -->

<p>A <term rend='noindex'>note</term>
<index level1='notes'>
is any additional comment found in a text, marked in some way as being
out of the main textual stream.  All notes should be marked using the
same tag, <gi>note</gi>, whether they appear as block notes in the main
text area, at the foot of the page, at the end of the chapter or volume,
in the margin, or in some other place.

<p>Notes may be in a different hand or typeface, may be authorial or
editorial, and may have been added later.  Attributes may be used to
specify these and other characteristics of notes, as detailed below.

<p>Where possible, the body of a note should be inserted in the text at
the point at which its identifier or mark first appears.  This may not
be possible for example with marginal notes, which may not be anchored
to an exact location.  For simplicity, it may be adequate to position
marginal notes before the relevant paragraph or other element.  In some
cases, however, it may be desirable to transcribe notes not at their
point of attachment to the text but at their point of appearance (at the
end of the volume, or the end of the chapter --- not, in general, when
the notes appear at the foot of the page); in this case the
<att>target</att> and <att>targetEnd</att> attributes should be used to
specify the point of attachment.  In some cases, the note is explicitly
attached not to a point but to a span of text; for a full discussion of
pointing to points and spans in the text, see section <ptr type=div1
target=COxr>.


<p>Examples:
<eg>
<![ CDATA [
<l>The self-same moment I could pray
<l>And from my neck so free
<l>The albatross fell off, and sank
<l>Like lead into the sea.
<note type=auth place=margin>The spell begins to break</note>
]]>
</eg><!-- STC, Anc Mar -->

<eg>
<![CDATA[
Collections are ensembles of distinct entities or objects
of any sort.<note place=foot n=1>We explain below why we use
the uncommon term <mentioned>collection</mentioned>
instead of the expected <mentioned>set</mentioned>.
Our usage corresponds to the <mentioned>aggregate</mentioned> of many
mathematical writings and to the sense of <mentioned>class</mentioned>
found in older logical writings.
</note>
The elements ...
]]>
</eg>

<p>In addition to transcribing notes from the copy text, researchers may
wish to annotate the electronic text itself, by attaching analytic notes
in some structured vocabulary to particular passages of text, e.g. to
specify the topics or themes of a text.  The empty <gi>span</gi> element
is provided for such applications; it is available only when the
additional tag set for simple analysis is selected (see section
<ptr target=AIsp>).

<!-- <p>The <gi>span</gi> tag may be used to mark any span    -->
<!-- of text; for example, the structural divisions           -->
<!-- assigned to a narrative by an interpreter:               -->

<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->

<!-- <p id=P1><anchor id=A1>Sigmund, the son of Volsung,      -->
<!-- was a king in Frankish country.  Sinfiotli was the       -->
<!-- eldest of his sons ...  <anchor id=A2> <s id=S4a>But     -->
<!-- Sinfiotli ... wooed the same woman</s> <s id=s4b> and    -->
<!-- Sinfiotli killed him over it.</s> <anchor id=A4>And      -->
<!-- when he came home, Borghild asked him to go away, but    -->
<!-- Sigmund offered her weregild, and she was obliged to     -->
<!-- accept it.  At the funeral feast Borghild was serving    -->
<!-- beer.  She took poison, a big drinking horn full, and    -->
<!-- brought it to Sinfiotli.  ...  Sinfiotli drank it off    -->
<!-- and at once fell dead.  <anchor=A5>                      -->

<!-- <p id=P2>Sigmund carried him a long way in his arms      -->
<!-- and came to a long, narrow fjord, and there was a        -->
<!-- small boat there and a man in it.  ...                   -->
<!--                                                          -->
<!-- <p id=P3>King Sigmund lived a long time in Denmark ...   -->
<!--                                                          -->
<!-- <p id=P4>Sigmund and all his sons were tall ...          -->
<!--                                                          -->
<!-- <s id=nil></s>                                           -->

<!-- <span resp=TMA type='structural unit' value='introduction' -->
<!--         from=A1 to=A2>                                   -->
<!-- <span resp=TMA type='structural unit' value='conflict'   -->
<!--         from=s4a>                                        -->
<!-- <span resp=TMA type='structural unit' value='climax'     -->
<!--         from=s4b>                                        -->
<!-- <span resp=TMA type='structural unit' value='revenge'    -->
<!--         from=A4 to=A5>                                   -->
<!-- <span resp=TMA type='structural unit' value='reconciliation' -->
<!--         from=nil>                                        -->
<!-- <span resp=TMA type='structural unit' value='aftermath'  -->
<!--         from=P2 to=P4>                                   -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

<p>The formal declarations for the <gi>note</gi> element is this:

<eg id=dcono>
<![ CDATA [
<!-- 6.8.1:  Annotation                                       -->
<!ELEMENT note          - O  (%specialPara;)                    >
<!ATTLIST note               %a.analysis;
                             %a.linking;
                             %a.terminology;
          id                 ID                  #IMPLIED
          lang               IDREF               %INHERITED
          rend               CDATA               #IMPLIED
          target             IDREFS              #IMPLIED
          place              CDATA               'unspecified'
          targetEnd          IDREFS              #IMPLIED
          resp               CDATA               #IMPLIED
          anchored           (yes | no)          yes
          n                  CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
<!-- ... declarations from section 6.8.2                      -->
<!--     (Index Entries)                                      -->
<!--     go here ...                                          -->
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>

<!-- <tagDecl tagDoc=span>                                    -->

<!-- P2.23e : Other stuff                                     -->
<!-- Revisions:                                               -->
<!-- 92-12-06 : MSM : move to p2cono from p2comi              -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<!-- 92-10-23 : MSM : new name                                -->
<!-- 25 May 92 : CMSMcQ : revise                              -->
<!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     -->
<!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  -->
<!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->

<div3 id=COnoix><head>Index Entries</head>

<p>Machine-readable versions of existing texts rarely reproduce any
index published with the copy text.  Should a printed index be
transcribed, the <gi>div1</gi> tag or a <gi>div</gi> tag at an
appropriate level should be used to demarcate the index, and the index
itself may be transcribed as a structured list or table.

<p>It is convenient, however, to be able to generate a new index
from a machine-readable text, whether the text is being written for the
first time with the tags here defined or was transcribed from some other
source.  The <gi>index</gi> tag is provided for this purpose; it
may be useful for marking points of particular interest for whatever
reason, and not merely for generating printed indexes for a printed
version of the text.  The <gi>divGen</gi> element indicates the
point at which an index, or any other generated text (e.g. a table
of contents), is to appear in the output of a text production process.
<list type=gloss>
<label><gi>index</gi></label>
<item>marks a location to be indexed for whatever purpose.
Attributes include:
<list type=gloss>
<label><att>level1</att></label>
<item>gives the form under which the index entry is to be made.</item>
<label><att>level2</att></label>
<item>gives the second-level form, if any.</item>
<label><att>level3</att></label>
<item>gives the third-level form, if any.</item>
<label><att>level4</att></label>
<item>gives the fourth-level form, if any.</item>
<label><att>index</att></label>
<item>indicates which index (of several) the index entry belongs 
to.</item>
</list>
</item>
<label><gi>divGen</gi></label>
<item>indicates the location at which a textual division 
generated
automatically by a text-processing application 
is to appear.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>specifies what type of generated text division (e.g. index, 
table of contents, etc.) is to appear.
Sample values include:
<list type=gloss>
<label><term>toc</term></label>
<item>a table of contents</item>
<label><term>index</term></label>
<item>an index is to be generated and inserted at this point.</item>
<label><term>tablist</term></label>
<item>a list of tables</item>
<label><term>figlist</term></label>
<item>a list of figures</item>
</list></item>
</list>
</item>
</list>


<p>The tag <tag>index</tag> associates up to four levels of index
terms with a specific point in the text.  The index terms are supplied
in attributes named <att>level1</att>, <att>level2</att>,
<att>level3</att>, and <att>level4</att>.  An <att>index</att>
attribute associates the entry with a particular index, so multiple
indices are possible.

<p>All index terms must be supplied as attribute values; no part of the
text itself is taken as a term.  This may require words or phrases to be
repeated, as illustrated below; it also allows spelling to be
normalized, as the example shows:

<eg> <![ CDATA [
The students understand procedures for Arabic lemmatisation
<index level1='Arabic lemmatization'>and are beginning
to build parsers.
]]>
</eg>

<p>The <gi>divGen</gi> element marks the place at which an index
generated from the <gi>index</gi> elements should be inserted into the
output of a processing program; typically, this will be at some point
within the back matter of the document; its <att>type</att> attribute
should be used to specify which index is to be generated, and its
<att>n</att> attribute to specify a name for the index:

<eg>
<![ CDATA [
<back>
<div><head>Examples</head>
<p> ...
</div>
<div><head>Bibliography</head>
<listBibl>
  <bibl> ... </bibl>
</listBibl>
</div>
<divGen type='index 1' n='Index Nominum'>
<divGen type='index 2' n='Index Rerum'  >
</back>
]]>
</eg>

<p>The formal declaration for these elements is as follows.
The <gi>index</gi> element is a member of the element class
<ident type='class'>metadata</ident> and may thus be used
anywhere within the <gi>text</gi> element.
<eg id=dconoix>
<![ CDATA [
<!-- 6.8.2:  Index Entries                                    -->
<!ELEMENT index         - O  EMPTY                              >
<!ATTLIST index              %a.global;
          level1             CDATA               #REQUIRED
          index              CDATA               #IMPLIED
          level3             CDATA               #IMPLIED
          level4             CDATA               #IMPLIED
          level2             CDATA               #IMPLIED       >
<!ELEMENT divGen        - O  EMPTY                              >
<!ATTLIST divGen             %a.global;
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 6.8.1                      -->
]]>
</eg>




<!-- COrs Reference Systems (P1 5.6)                          -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- $Id: p2cors.odd,v 1.10 1998/01/30 16:41:14 tei Exp $ -->
<!--*
    * $Log: p2cors.odd,v $
    * Revision 1.10  1998/01/30 16:41:14  tei
    * Fix log format.
    *
    * Revision 1.9  1998/01/30 15:54:50  tei
    * more eg typos
    *
    * Revision 1.8  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.7  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    *
    * Revision 1.6  1994/03/27  21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    *
    * Revision 1.5  1994/02/17  20:31:08  msmcq
    * revision for SC review
    *-->
<!-- P2COrs : Reference Systems                               -->
<!-- Revisions:                                               -->
<!-- 10 jan 98 : LB : fix egs -->
<!-- 94-04-07 : MSM : trivial typos                           -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-26 : MSM : corrections from DB                     -->
<!-- 94-03-26 : MSM : typos from JL et al.                    -->
<!-- 94-02-17 : MSM : Added RCS id                            -->
<!-- 94-02-15 : MSM : supply missing /eg                      -->
<!-- 25 dec 93: LB: change milestone tags; add exx.           -->
<!-- 92-12-09 : MSM : correct two typos, one important        -->
<!-- 92-12-09 : MSM : cosmetic copy editing                   -->
<!-- 92-12-09 : MSM : add space after some end-tags           -->
<!-- 92-12-07 : MSM : revise for publication                  -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elements -->
<!-- 19 Oct 92 : LB some stylistic changes                    -->
<!-- 1 oct 92 : LB : change IDs to new scheme                 -->
<!-- 14 May 92 : CMSMcQ : assign numeric IDs to sections.     -->
<!-- 29-30 Apr 92 : CMSMcQ : reorder, revise somewhat.        -->
<!-- 21 Apr 92 : CMSMcQ : retag for TEI P2.                   -->
<!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  -->
<!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0 (z69, sec. 5.6)  -->
<!-- Mar-Apr 89 : EM : drafted                                -->

<div2 id=COrs><head>Reference Systems</head>

<p>By <mentioned>reference system</mentioned> we mean the system by which names
or references are associated with particular passages of a text (e.g.
<mentioned>Ps. 23:3</mentioned> for the third verse of Psalm 23 or <mentioned>Amores
2.10.7</mentioned> for Ovid's <title>Amores</title>, book 2, poem 10, line
7).  Such names make it possible to mark a place within a text and
enable other readers to find it again.  A reference system may be based
on structural units (chapters, paragraphs, sentences; stanza and verse),
typographic units (page and line numbers), or divisions created
specifically for reference purposes (chapter and verse in Biblical
texts).  Where one exists, the traditional reference system for a text
should be preserved in an electronic transcript of it, if only to make
it easier to compare electronic and non-electronic versions of the text.

<p>Reference systems may be recorded in TEI-encoded texts in any of the
following ways:

<list type=bullets>

<item>where a reference system exists, and is based on the same
logical structure as that of the text's SGML markup, the reference for
a passage may be recorded as the value of the global <att>id</att> or
<att>n</att> attribute on an appropriate tag, or may be constructed by
combining attribute values from several levels of tags, as described
below in section <ptr type=div3 target=COrs1>.

<item>where there is no pre-existing reference system, the global
<att>id</att> or <att>n</att> attributes may be used to construct one
(e.g. collections and corpora created in electronic form), as described
below in section <ptr type=div3 target=COrs2>.

<item>where a reference system exists which is not based on the same
logical structure as that of the text's SGML markup, (for example, one
based on the page and line numbers of particular editions of the text
rather than on the structural divisions of it), then a distinct logical
structure representing the reference system may be encoded as a
concurrent markup stream, as described in section <ptr target=NHrs>.

<item>where a reference system exists which does not correspond to any
particular logical structure, or where the logical structure concerned
is of no interest to the encoder except as a means of supporting the
referencing system, then references may be encoded by means of
<gi>milestone</gi> elements, which simply mark points in the text at
which values in the reference system change, as described below in
section <ptr type=div3 target=COrs5>.

</list>

The specific method used to record traditional or new reference systems
for a text should be declared in the TEI header, as further described in
section <ptr type=div3 target=COrs6> and in chapter <ptr target=cr>.

<p>When a text has no pre-existing associated reference system of any
kind, these Guidelines recommend as a minimum that at least the page
boundaries of the source text be marked using one of the methods
outlined in this section.  Retaining page breaks in the markup is also
recommended for texts which have a detailed reference system of their
own.  Line breaks in prose texts may be, but need not be, tagged.
<note place=foot>
Many encoders find it convenient to retain the line breaks of
the original during data entry, to simplify proof-reading,
but this may be done without inserting a tag for each line
break of the original.
<!-- For further discussion of tagging for pagination,        -->
<!-- lineation, and other physical characteristics of the     -->
<!-- copy text, see chapter <ptr type=div1 target=PH >.      -->
</note>

<div3 id=COrs1><head>Using the ID and N Attributes</head>

<p>When traditional reference schemes represent a hierarchical
structuring of the text which mirrors that of the SGML document, the
<att>n</att> attribute defined for all elements may be used to indicate
the traditional identifier of the relevant structural units.  The
<att>n</att> attribute may also be used to record the numbering of
sections or list items in the copy text if the copy-text numbering is
important for some reason, for example because the numbers are out of
sequence.

<p>For example, a traditional reference to Ovid's <title>Amores</title>
might be <mentioned>Amores 2.10.7</mentioned>---book 2, poem 10, line 7. Book,
poem, and line are structural units of the work and will therefore be
tagged in any case.  (See chapter <ptr type=div1 target=VE> for a
discussion of structural units in verse collections.)  In such cases, it
is convenient to record traditional reference numbers of the structural
units using the <att>n</att> attribute.  The relevant tags for our
example would be:

<eg>
<![ CDATA [
<div0 n=Amores type=volume>
    <div1 n='2' type=book>
         <div2 n='10' type=poem>
              <l n='7'> ...
]]>
</eg>

<p>One may also place the entire standard reference for each portion of
the text into the appropriate value for the <att>n</att> attribute,
though for obvious reasons this takes more space in the file:

<eg>
<![ CDATA [
<div0 n=Amores type=volume>
    <div1 n='Amores 2' type=book>
         <div2 n='Amores 2.10' type=poem>
              <l n='Amores 2.10.7'> ...
]]>
</eg>

<p>If the names used by the traditional reference system can be
formulated as SGML identifiers, then the references can be given as
values for the <att>id</att> attribute; this requires that the reference
be given without internal spaces, begin with a letter, and contain no
characters other than letters, digits, hyphens, and full
stops.<note place=foot>
The legal form of identifiers depends in part on the SGML
declaration.  With appropriate modifications in the declaration,
other characters may be made legal in identifiers; this is allowed
though not encouraged in TEI-conformant documents.
</note>
Unlike values for the <att>n</att> attribute, values for the
<att>id</att> attribute must be unique throughout the document.
Our example then looks like this:

<eg>
<![ CDATA [
<div0 id=Amores type=volume>
    <div1 id='Am.2' type=book>
         <div2 id='Am.2.10' type=poem>
              <l id='Am.2.10.7'> ...
]]>
</eg>

<p>To document the usage and to allow automatic processing of these
standard references, it is recommended that the TEI header be used to
declare whether standard references are recorded in the <att>n</att> or
<att>id</att> attributes and which elements may carry standard
references or portions of them.  For examples of declarations for the
reference systems just shown, see section <ptr type=div3 target=COrs6>.

<p>Using the <att>n</att> attribute one can specify only a single
standard referencing system, a limitation not without problems, since
some editions may define structural units differently and thus create
alternative reference systems.  For example, another edition of the
<title>Amores</title> considers poem 10 a continuation of poem 9, and
therefore would specify the same line as <mentioned>Amores 2.9.31</mentioned>.
In order to record both of these reference systems, one must either use
the <att>id</att> or <att>n</att> attribute for one, with competing
systems in concurrent markup hierarchies, as discussed below in section
<ptr type=div3 target=NHrs>, or else use the <gi>milestone</gi> tags
described in section <ptr type=div1 target=COrs5>.

<div3 id=COrs2><head>Creating New Reference Systems</head>

<p>If a text has no canonical reference system of its own, a reference
system, if needed, may be derived from the structure of the electronic
text, specifically from the SGML markup of the text.  As with any
reference system intended for long-term use, it is important to see the
reference as an established, unchanging point in the text.  Should the
text be revised or rearranged, the reference-system identifiers
associated with any bit of text must stay with that bit of text, even if
it means the reference numbers fall out of sequence.  (A new reference
system may always be created beside the old one if out-of-sequence
numbers must be avoided.)

<p>The global attributes <att>n</att> and <att>id</att> may be used to
assign reference identifiers to segments of the text.  Identifiers
specified by either attribute apply to the entire element for which they
are given.  SGML enforces uniqueness on ID attributes within a single
document, and ID values must begin with a letter.  No such restrictions
are made on the values of <att>n</att> attributes.

<!-- <p>A convenient method of mechanically generating        -->
<!-- unique values for <att>id</att> or <att>n</att>          -->
<!-- attributes, based on the SGML structure of the document  -->
<!-- is to use the <soCalled>typed path</soCalled> or         -->
<!-- <term>untyped path</term> methods described in section   -->
<!-- <ptr type=div1 target=SA> to identify elements within   -->
<!-- the <gi>text</gi> segment of a TEI document.             -->

<!-- The discussion referred to no longer exists; following   -->
<!-- paragraphs (through example) added as substitute.        -->
<!-- (msm)                                                    -->

<p>A convenient method of mechanically generating unique values for
<att>id</att> or <att>n</att> attributes based on the SGML structure of
the document is to construct, for each element, a <term>domain-style
address</term> comprising a series of components separated by full
stops, with one component for each level of the SGML document hierarchy.
Two methods may be used.  In the <term>typed path</term> form of
identifier, each component in the identifier takes the form <ident
type=var>element-type</ident> <mentioned>-</mentioned> <ident
type=var>number</ident>.  The element name specifies what type of
element to be sought, and the number specifies which occurrence of that
element type is to be selected.  (The hyphen and number may be omitted
if there is only one element of the given type.)  In the <term>untyped
path</term> form of identifier, each component consists of a number,
indicating which element in the sequence of nodes at each level is to be
selected.  A fixed prefix beginning with a letter may be used to make
the untyped path legal as an SGML <code type=kw>ID</code> value.

<p>Identifiers generated with these methods should use the <gi>text</gi>
element as their starting point, rather than the <gi>tei.2</gi> or
<gi>body</gi> elements. The <gi>tei.2</gi> element may be taken
as a starting point only if identifiers need to be generated for the
<gi>teiHeader</gi>, which is not usually the case;  using the
<gi>body</gi> element as a root would prevent assignment of identifiers
for the front and back matter.  The component corresponding to the root
element can be omitted from identifiers, if no confusion will result.
In collections and corpora, the component corresponding to the root may
be replaced by the unique identifier assigned to the text or sample.

<p>In the following example, each element within the <gi>text</gi>
element has been given a typed-path identifier as its <att>id</att>
value, and an untyped-path identifier as its <att>n</att> value; the
latter are prefixed with the string <mentioned>AB</mentioned>, which may be
imagined to be the general identifier for this text.

<eg>
<![ CDATA [
   <text id='text-1' n='AB'>
     <front id='front' n='AB.1'>
       <div       id='front.div-1'     n='AB.1.1'><p> ... </div>
       <titlePage id='front.titlePage' n='AB.1.2'>
                 <titlePart> ... </titlePart>       </titlePage>
       <div       id='front.div-2'     n='AB.1.3'><p> ... </div>
     </front>
     <body id='body' n='AB.2'>
       <p id='body.p-1' n='AB.2.1'> ... </p>
       <p id='body.p-1' n='AB.2.2'> ... </p>
       <div id='body.div-1' n='AB.2.3'>
         <head id='body.div-1.head' n='AB.2.3.1'> ... </head>
         <p    id='body.div-1.p-1'  n='AB.2.3.2'> ... </p>
         <p    id='body.div-1.p-2'  n='AB.2.3.3'> ... </p>
         </div>
       <div id='body.div-2' n='AB.2.4'>
         <head id='body.div-2.head' n='AB.2.4.1'> ... </head>
         <p    id='body.div-2.p-1'  n='AB.2.4.2'> ... </p>
         <p    id='body.div-2.p-2'  n='AB.2.4.3'> ... </p>
         </div>
     </body>
  </text>
]]>
</eg>


The typed and untyped path methods are convenient, but are in no way
required for anyone creating a reference system.

<p>If the <att>id</att> attribute is used to record the reference
identifiers generated, each value should record the entire path.  If the
<att>n</att> attribute is used, each value may record either the entire
path or only the subpath from the SGML parent element.  The attribute
used, the elements which can bear standard reference identifiers, and
the method for constructing standard reference identifiers, should all
be declared in the header as described in section <ptr target=HD54>.

<p>When the hierarchy of the SGML-encoded document and that of the
reference system differ (e.g. for reference systems based on page and
line numbers) or when more than one reference system is to be encoded,
the encoder may choose to represent the alternative reference system(s)
as elements in one or more concurrent document hierarchies.  For an
introduction to the concept of concurrent hierarchies, see the
discussion of the <code type=kw>CONCUR</code> feature in section <ptr
type=div1 target=SG152>.  For further discussion of this and other
mechanisms, see chapter <ptr target=NH>.

<div3 id=COrs5><head>Milestone Tags</head>

<p>If concurrent markup is not desired (e.g. because the available SGML
parser does not support the CONCUR feature), or if the desired reference
system does not correspond to any particular structural hierarchy, it
may be more convenient to mark up changes in the reference system by using
one or more of the following <term>milestone</term> elements:

<list type=gloss>
<label><gi>milestone</gi></label>
<item>marks the boundary between sections of a text, as indicated 
by
changes in a standard reference system.
Attributes include:
<list type=gloss>
<label><att>ed</att></label>
<item>indicates which edition or version the milestone applies 
to.</item>
<label><att>n</att></label>
<item>indicates the new number or other value for the unit which 
changes at this milestone.</item>
<label><att>unit</att></label>
<item>indicates what kind of section is changing at this 
milestone.
Suggested values include:
<list type=gloss>
<label><term>line</term></label>
<item>line breaks.</item>
<label><term>poem</term></label>
<item>individual poems in a collection.</item>
<label><term>book</term></label>
<item>any units termed <mentioned>book</mentioned>, <mentioned>liber</mentioned>, 
etc.</item>
<label><term>scene</term></label>
<item>scenes within a play or act.</item>
<label><term>page</term></label>
<item>page breaks in the reference edition.</item>
<label><term>stanza</term></label>
<item>stanzas within a poem, book, or canto.</item>
<label><term>absent</term></label>
<item>passages not present in the reference edition.</item>
<label><term>column</term></label>
<item>column breaks.</item>
<label><term>canto</term></label>
<item>cantos or other major sections of a poem.</item>
<label><term>act</term></label>
<item>acts within a play.</item>
<label><term>section</term></label>
<item>sections of any kind.</item>
</list></item>
</list>
</item>
<label><gi>pb</gi></label>
<item>marks the boundary between one page of a text and the next

in a standard reference system.
Attributes include:
<list type=gloss>
<label><att>ed</att></label>
<item>indicates the edition or version in which the page break is 
located at this point</item>
<label><att>n</att></label>
<item>indicates the number or other value associated with the 
page which follows the point of insertion of this 
<gi>pb</gi>.</item>
</list>
</item>
<label><gi>lb</gi></label>
<item>marks the start of a new (typographic) line in some

edition or version of a text.
Attributes include:
<list type=gloss>
<label><att>ed</att></label>
<item>indicates the edition or version in which the line break is 
located at this point</item>
<label><att>n</att></label>
<item>indicates the number or other value associated with the 
line which follows the point of insertion of this 
<gi>lb</gi>.</item>
</list>
</item>
<label><gi>cb</gi></label>
<item>marks the boundary between one column of a text and the 
next
in a standard reference system.
Attributes include:
<list type=gloss>
<label><att>ed</att></label>
<item>indicates the edition or version in which the column break 
is located at this point</item>
<label><att>n</att></label>
<item>indicates the number or other value associated with the 
column which follows the point of insertion of this 
<gi>cb</gi> element.</item>
</list>
</item>
</list>


<p>These elements simply mark the points in a text at which some
category in a reference system changes.  They have no content but
subdivide the text into regions, rather in the same way as milestones
divide a road into segments.  The elements <gi>pb</gi>, <gi>cb</gi>,
and <gi>lb</gi> are provided to mark specific types of milestone,
namely page, column, and line boundaries, as further described in
chapter <ptr type=div1 target=PH>.  No SGML validation of a reference
system based on <gi>milestone</gi> tags is possible, so it will be the
responsibility of the encoder or the application software to ensure
that milestone tags occur in a correct order.

<p>Milestone tags may be useful where a text has two competing
structures. For example, many English novels were first published as
serial works, individual parts of which do not always contain a whole
number of chapters. An encoder may decide to represent the
chapter-based  structure using <gi>div1</gi> elements, with
<gi>milestone</gi> elements to mark the points at which individual
parts end; or the reverse. Thus, an encoding in which chapters are
regarded as more important than parts might encode some work in which
chapter three begins in part one and is concluded in part two as
follows:

<eg rend=skel>
<![ CDATA [
<text><body>
  <milestone unit=part>
  <div1 n=1 type=chapter>
  <!-- text of chapter 1 here -->
  </div1>
  <div1 n=2 type=chapter>
  <!-- text of chapter 2 here -->
  </div1>
  <div1 n=3>
  <!-- part of text of chapter 3 here -->
  <milestone unit=part>
  <!-- remainder of text of chapter 3 here -->.
  </div1>
</body></text>
]]>
</eg>

An encoding of the same work in which parts are regarded as more
important than chapters might begin as follows:

<eg> <![ CDATA [
<text><body>
  <div1 n=1 type=part>
  <milestone unit=chapter>
  <p><!-- text of chapter 1 here -->
  <milestone unit=chapter>
  <p><!-- text of chapter 2 here -->
  <milestone unit=chapter>
  <p><!-- part of text of chapter 3 here -->
  </div1><div1 n=2 type=part>
  <p><!-- remainder of text of chapter 3 here -->
  <milestone unit=chapter>
  <!-- ... -->
</body></text>
]]>
</eg>

<p>Milestone tags also make it possible to record the reference systems
used in a number of different editions of the same work. The reference
system of any one edition can be recreated from a text in which all are
marked by simply ignoring all elements that do not specify that edition
on their <att>ed</att> attribute.

<p>As a simple example, assuming that edition E1 of some collection of
poems regards the first two poems as constituting the first book, while
edition E2 regards the first poem as prefatory, a markup scheme like
the following might be adopted:

<eg>
<![ CDATA [

 <milestone ed=E1 unit=work>
 <milestone ed=E2 unit=work>
 <milestone ed=E1 unit=book>
 <milestone ed=E1 unit=poem>
 <milestone ed=E2 unit=poem>
  <!-- text of first poem here -->
 <milestone ed=E2 unit=book>
 <milestone ed=E1 unit=poem>
 <milestone ed=E2 unit=poem>
  <!-- text of second poem here -->

]]>
</eg>

<p>In this case no <att>n</att> value is specified, since the numbers
rise predictably and the application can keep a count from the start of
the document, if desired.

<p>The value of the <att>n</att> attribute may but need not include the
identifiers used for any larger sections.  That is, either of the
following styles is legitimate:
<eg>
<![CDATA[
 <milestone ed=E1 unit=work n='Amores'>
 <milestone ed=E1 unit=book n=1>
 <milestone ed=E1 unit=poem n=1>
  <!-- text of Amores 1.1 -->
 <milestone ed=E1 unit=poem n=2>
  <!-- text of Amores 1.2 -->
 <milestone ed=E1 unit=book n=3>
]]>
</eg>
or
<eg>
<![CDATA[
 <milestone ed=E1 unit=work n='Amores'>
 <milestone ed=E1 unit=book n=1>
 <milestone ed=E1 unit=poem n='1.1'>
 <!-- text of Amores 1.1 -->
 <milestone ed=E1 unit=poem n='1.2'>
  <!-- text of Amores 1.2 -->
 <milestone ed=E1 unit=book n='1.3'>
]]>
</eg>

<p>
When using <gi>milestone</gi> tags, line numbers may be supplied for
every line or only periodically (every fifth, every tenth line).  The
latter may be simpler; the former is more reliable.

<p>The style of numbering used in the values of <att>n</att> is
unrestricted:  for the example above, <code type=val>I.i</code>, <code
type=val>I.ii</code>, and <code type=val>I.iii</code> could have been
used equally well if preferred.  The special value <code
type=val>unnumbered</code> should be reserved for marking sections of
text which fall outside the normal numbering system (e.g. chapter heads,
poem numbers, titles, or speaker attributions in a verse drama).

<!-- dropped second reference pace Eynsham -->
<!-- p>No automatic validation of any hierarchical ordering   -->
<!-- can be defined for the various types of <                -->
<!-- gi>milestone</ gi> tag; it is the encoder's              -->
<!-- responsibility to ensure that milestone values are       -->
<!-- valid.                                                   -->

<p>Because the <att>ed</att> attribute is unrestricted, no change need be
made to the document type declaration of a file before adding tags to
describe a new reference system.  (The value of <att>ed</att> may be
restricted to a defined set of edition symbols by using the techniques
described in chapter <ptr type=div1 target=MD>.)

<p>See below, section <ptr type=div3 target=COrs6>, for examples of
declarations for the reference systems just shown.

<p>The milestone elements are formally defined
as follows:
<!--  tag has the following formal declaration: -->
<eg id=dcorsm>
<![ CDATA [
<!-- 6.9.3:  Milestone tags                                   -->
<!ELEMENT milestone     - O  EMPTY                              >
<!ATTLIST milestone          %a.analysis;
                             %a.linking;
                             %a.terminology;
          id                 ID                  #IMPLIED
          lang               IDREF               %INHERITED
          rend               CDATA               #IMPLIED
          ed                 CDATA               #IMPLIED
          n                  CDATA               #IMPLIED
          unit               CDATA               #REQUIRED      >
<!ELEMENT pb            - O  EMPTY                              >
<!ATTLIST pb                 %a.analysis;
                             %a.linking;
                             %a.terminology;
          id                 ID                  #IMPLIED
          lang               IDREF               %INHERITED
          rend               CDATA               #IMPLIED
          ed                 CDATA               #IMPLIED
          n                  CDATA               #IMPLIED       >
<!ELEMENT lb            - O  EMPTY                              >
<!ATTLIST lb                 %a.analysis;
                             %a.linking;
                             %a.terminology;
          id                 ID                  #IMPLIED
          lang               IDREF               %INHERITED
          rend               CDATA               #IMPLIED
          ed                 CDATA               #IMPLIED
          n                  CDATA               #IMPLIED       >
<!ELEMENT cb            - O  EMPTY                              >
<!ATTLIST cb                 %a.analysis;
                             %a.linking;
                             %a.terminology;
          id                 ID                  #IMPLIED
          lang               IDREF               %INHERITED
          rend               CDATA               #IMPLIED
          ed                 CDATA               #IMPLIED
          n                  CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>


<div3 id=COrs6><head>Declaring Reference Systems</head>

<p>Whatever kind of reference system is used in an electronic text, it
is recommended that the TEI header contain a description of its
construction in the <gi>refsDecl</gi> element described in section <ptr
type=div3 target=HD54>.  As described there, the declaration may consist
either of a formal declaration using the <gi>step</gi> tag or an
informal description in prose.  The former is recommended because unlike
prose it can be processed by software.

<p>The three examples given in section <ptr type=div3 target=COrs1>
would be declared as follows.  The first example encodes the standard
references for Ovid's <title>Amores</title> one level at a time, using
the <att>n</att> attribute on the <gi>div0</gi>, <gi>div1</gi>,
<gi>div2</gi>, and <gi>l</gi> tags.  The header for such an encoding
should look something like this:

<eg rend=skel>
<![ CDATA [
<teiHeader>
    <fileDesc> ...
    </fileDesc>
    <encodingDesc>
         ...
         <refsDecl>
              <step refunit='work' delim=' '
                    from='DESCENDANT (1 DIV0 N %1)' to='DITTO' >
              <step refunit='book' delim='.'
                    from='CHILD (1 DIV1 N %1)' to='DITTO' >
              <step refunit='poem' delim='.'
                    from='CHILD (1 DIV2 N %1)' to='DITTO' >
              <step refunit='line'
                    from='CHILD (1 L N %1)' to='DITTO' >
         </refsDecl>
         ...
    </encodingDesc>
</teiHeader>
]]>
</eg>

<p>The second example encodes the same reference system, again using the
<att>n</att> attribute on the <gi>div0</gi>, <gi>div1</gi>,
<gi>div2</gi>, and <gi>l</gi> tags, but giving the reference string in
full on each tag.  If canonical references are made only to lines, the
reference system could be declared as follows:

<eg>
<![ CDATA [
 <refsDecl>
   <step refunit='line'
         from='DESCENDANT (1 L N %1)' to='DITTO' >
 </refsDecl>
]]>
</eg>

Since no delimiter is specified, the entire canonical reference string
is sought as the value of the <att>n</att> attribute on an <gi>l</gi>
element.

<p>In order to handle references to works, books, and poems as well as
to individual lines, the declaration for the reference system must be
more complicated:

<eg>
<![ CDATA [
 <refsDecl>
   <step from='DESCENDANT (1 (DIV[012]|L) N %1)' to='DITTO' >
 </refsDecl>
]]>
</eg>

This declaration indicates that the entire reference string must be
sought as the value of the <att>n</att> attribute on a <gi>div0</gi>,
<gi>div1</gi>, <gi>div2</gi>, or <gi>l</gi> element.

<p>The third example encodes the same reference system, this time giving
the entire reference string as the value of the <att>id</att> attribute
on the relevant tags.  The reference system declaration for such an
encoding would be:

<eg>
<![ CDATA [
<refsDecl>
    <step from="ID (%1)" to="DITTO">
</refsDecl>
]]>
</eg>

<p>As in the previous example, no single value can be given for the
<att>refunit</att> attribute in this declaration, as the single step
handles references to works, books, and poems, as well as to lines.  The
<att>type</att> attribute on the <gi>div0</gi>, <gi>div1</gi>, and
<gi>div2</gi> elements may be used, however, to indicate the type of the
result returned from a match.

<!-- , or the declaration can be expanded:                    -->
<!--                                                          -->
<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <refsDecl>                                               -->
<!--     <step refunit='work' from="ID (%1)" to="DITTO">      -->
<!--     <step refunit='book' from="ID (%1)" to="DITTO">      -->
<!--     <step refunit='poem' from="ID (%1)" to="DITTO">      -->
<!--     <step refunit='line' from="ID (%1)" to="DITTO">      -->
<!-- </refsDecl>                                              -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

<p>Reference systems recorded by means of milestone tags can also be
declared; the following prose description could be used to declare
the example given in section <ptr type=div3 target=COrs5>.

<eg>
<![ CDATA [
<refsDecl>
    <p>Standard references to work, book, poem, and line may be
    constructed from the Milestone tags in the text.
</refsDecl>
]]>
</eg>

Or in this way, using a formal declaration for this reference scheme
derived from edition <code type=value>E1</code>.

<eg>
<![ CDATA [
<refsDecl>
    <state delim=' ' unit=work ed='E1'>
    <state delim='.' unit=book ed='E1'>
    <state delim=':' unit=poem ed='E1'>
    <state unit=line ed='E1'>
</refsDecl>
]]>
</eg>

<p>This is synonymous with the following declaration using the
<gi>step</gi> element:

<eg>
<![ CDATA [
<refsDecl>
    <step refunit='work' delim=' '
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT work N %1)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT work)' >
    <step refunit='book' delim='.'
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT book N %2)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT book)' >
    <step refunit='poem' delim='.'
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT poem N %3)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT poem)' >
    <step refunit='line'
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT line N %4)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT line)' >
</refsDecl>
]]>
</eg>

<!-- JL:  question for P4:  can we specify the edition in     -->
<!-- some way as a parameter?                                 -->


<!-- CObi Bibliographic Citations (P1 5.5)                    -->
<!--* $Id: p2cobi.odd,v 1.14 1999/05/15 18:09:12 tei Exp $ *-->
<!--*
    *
    * $Log: p2cobi.odd,v $
    * Revision 1.14  1999/05/15 18:09:12  tei
    * remove ED attribute from <note> (only one in P3...)
    *
    * Revision 1.13  1998/02/01 17:55:08  tei
    * fix log keyword (still need SGML normalization)
    *
    * Revision 1.12  98/01/28  11:44:14  cmsmcq
    * LB changes of Jan 1998 and RCS keywords added.
    *
    * Revision 1.11  1994/03/27  21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    *
    * Revision 1.10  1994/02/12  21:37:58  msmcq
    * strip ^Z
    * -->
<!-- ******************************************************** -->
<!-- P2 Cobi (old P2235)                                      -->
<!>
<!-- ******************************************************** -->
<!-- Revision History (add lines at top)                      -->
<!-- 10 jan 98 : LB : fix egs -->
<!-- 94-03-26 : MSM : corrections, changes from WWP team      -->
<!-- 94-03-26 : MSM : corrections from DB                     -->
<!-- 94-03-26 : MSM : typos from JL et al.                    -->
<!-- 9 jan: fixed spurious <items> element; change TeiH to teiH  -->
<!-- 29 dec 93 : fixed many erroneous  examples               -->
<!-- 27 dec 93: LB : removed individual, org etc -->
<!-- 25 dec 93: LB : resp/respstmt, city/pubPlace fixes       -->
<!--            added meeting, doubtfully                     -->
<!-- 92-12-09 : MSM : spelling corrections                    -->
<!-- 92-12-09 : MSM : date takes VALUE att, not STDVAL        -->
<!-- 92-12-07 : MSM : clean dtdFrag ids, contins              -->
<!-- 92-12-06 : MSM : clean up dtdfrag ids, refs              -->
<!-- 92-12-06 : MSM : correct minor syntax errors             -->
<!-- 92-12-06 : MSM : correct ref to fileDesc, TeiHeader      -->
<!-- 92-12-05 : MSM : finish (hard slog), add equiv list      -->
<!-- 92-12-03 : MSM : further changes, in part as per LB      -->
<!-- 92-12-02 : MSM : continued revisions                     -->
<!-- 92-12-01 : MSM : revise for release of CO                -->
<!-- 92-11-17 : MSM : change IDs to CObi*                     -->
<!-- 92-11-09 : MSM : suppress leading blanks in some elems   -->
<!-- 92-11-09 : MSM : rename BIBL from CITN                   -->
<!-- 26 May 92 MSM make comments all one line long for Script -->
<!--               modify dtdfrag ids                         -->
<!--  2 May 92 LB  added loadsa discussion; killed some tags; -->
<!--               added citn.full, address and its parts     -->
<!-- 26 Feb 92 LB     ODDified from TEI P1, sec.  6.6         -->
<!--       (last revision: 16 Oct 90 CMSMcQ  for Version 1.1) -->

<div2 id=CObi><head>Bibliographic Citations and References</head>

<p>Bibliographic references (that is, full descriptions of bibliographic
items such as books, articles, films, broadcasts, songs, etc.) or
pointers to them may appear at various places in a TEI text.  They are
required at several points within the TEI Header's source description,
as discussed in section <ptr target=HD3>; they may also appear within
the body of a text, either singly, (for example within a footnote), or
collected together in a list as a distinct part of a text.

<p>In printed texts, the individual constituents of a bibliographic
reference are conventionally marked off from each other and from the
flow of text by such features as bracketing, italics, special
punctuation conventions, underlining, etc.  In electronic texts, such
distinctions are also important, whether in order to produce acceptably
formatted output or to facilitate intelligent retrieval processing,<note
place=foot>For example, to distinguish <mentioned>London</mentioned> as an
author's name from <mentioned>London</mentioned> as a place of publication or as
a component of a title.</note> quite apart from the need to distinguish
the reference itself as a textual object with particular linguistic
properties.

<p>It should be emphasized that for references as for other textual
features, the primary or sole consideration is not how the text should
be formatted when it is printed.  The distinctions permitted by the
scheme outlined here may not necessarily be all that particular
formatters or bibliographic styles require, although they should prove
adequate to the needs of many such commonly used software systems.<note
place=foot>Among the bibliographic software systems and
subsystems consulted in the design of the <gi>biblStruct</gi> structure
were BibTeX, Scribe, and ProCite.  The distinctions made by all three
may be preserved in <gi>biblStruct</gi> structures, though the nature of
their design prevents a simple one-to-one mapping from their data
elements to TEI elements.  For further information, see section <ptr
target=CObiot>.</note> The features distinguished and described below
(in section <ptr target=CObico>) constitute a set which has been useful
for a wide range of bibliographic purposes and in many applications, and
which moreover corresponds to a great extent with existing bibliographic
and library cataloguing practice.  For a fuller account of that practice
as applied to electronic texts see section <ptr target=HD3>; for a
brief mention of related library standards see section <ptr
target=HD8>.

<div3 id=CObity><head>Elements of Bibliographic References</head>

<p>The following elements are used to mark individual bibliographic
references as wholes, or in groups:

<list type=gloss>
<label><gi>bibl</gi></label>
<item>contains a loosely-structured bibliographic citation of 
which
the sub-components may or may not be explicitly 
tagged. </item>
<label><gi>biblStruct</gi></label>
<item>contains a structured bibliographic citation, in which only
bibliographic subelements appear and in a specified order. </item>
<label><gi>biblFull</gi></label>
<item>contains a fully-structured bibliographic citation, in 
which all
components of the TEI file description
are 
present.
<!-- except maybe the source.desc? --></item>
<label><gi>listBibl</gi></label>
<item>contains a list of bibliographic citations of any kind. </item>
</list>


These elements all share a number of possible component sub-elements.
For the <gi>bibl</gi> and <gi>biblStruct</gi> elements, exactly the
same sub-elements are concerned, and they are described together in
section <ptr target=CObico>; for the <gi>biblFull</gi> element, the
sub-elements concerned are fully described in section <ptr target=HD2>.

<p>Different levels of specific tagging may be appropriate in different
situations.  In some cases, it may be felt necessary to mark just the
extent of the reference itself, with perhaps a few distinctions being
made within it (for example, between the part of the reference which
identifies a title or author and the rest).  Such references, containing
a mixture of text with specialized bibliographic elements, are regarded
as <gi>bibl</gi> elements, and tagged accordingly.  For example:

<eg><![ CDATA[
<p>A book which had a great influence on him
was <bibl>Tufte's <title>Envisioning
Information</title></bibl>, although he may
never have actually read it.
]]>
</eg>

Indeed, some encoders may find it unnecessary to mark the bibliographic
reference at all:

<eg><![ CDATA[
<p>A book which had a great influence on him
was Tufte's <title>Envisioning Information</title>,
although he may never have actually read it.
]]>
</eg>

<p>Some bibliographic references are extremely elliptical, often only a
string of the form <mentioned>Baxter, 1983</mentioned>.  If no further details of
Baxter's book are given in the source text and none are supplied by the
encoder, then the reference thus given should be tagged as a
<gi>bibl</gi>:

<eg>
<![ CDATA [
All of this is of course much more fully treated
in <bibl>Baxter, 1983</bibl>.
]]>
</eg>

In general, however, normal modern bibliographic practice, and these
Guidelines, distinguish between a bibliographic
<term rend='noindex'>reference</term>,
<index level1='references' level2='bibliographic'>
<index level1='bibliographic references'>

which is a self-sufficient description of a bibliographic item, and a
bibliographic <term rend='noindex'>pointer</term>,
<index level1='bibliographic pointers'>
<index level1='pointers' level2='bibliographic'>

which is a short-form citation (such as <mentioned>Baxter, 1983</mentioned>)
which serves usually as a place-holder or pointer to a full long-form
reference found elsewhere in the text.  The usual encoding of short-form
references such as <mentioned>Baxter, 1983</mentioned> is not as <gi>bibl</gi>
elements but as cross-references to such elements; see section <ptr
target=CObixr> below.

<p>In cases where the encoder wishes to impose more structure on the
bibliographic information, for example to make sure it conforms to a
particular style-sheet or retrieval processor, the <gi>biblStruct</gi>
element should be used.  Note that several of the features in this and
later examples are explained later in the current section.

<eg><![ CDATA[
<biblStruct>
    <monogr>
    <author>Edward R. Tufte</>
    <title>Envisioning Information</>
    <imprint>
         <pubPlace>Cheshire, Conn.</>
         <publisher>Graphics Press</>
         <date>1990</>
    </imprint></monogr>
</biblStruct>
]]>
</eg>

<p>The highest level of detail and the most complex structure supported
by the current proposals is provided by the <gi>biblFull</gi> element,
which closely resembles the <gi>fileDesc</gi> element of the TEI Header
(section <ptr target=HD2>).

<!-- biblFull needs an analytic level. -MSM -->
 <!-- titstmt requires title first -->
<eg><![ CDATA[
<biblFull>
    <titleStmt>
         <title>Envisioning Information</title>
         <author>Tufte, Edward R[olf]</author>
      </titleStmt>
    <extent>126 pp.</extent>
    <publicationStmt>
         <publisher>Graphics Press</publisher>
         <pubPlace>Cheshire, Conn. USA</pubPlace>
         <date>1990</date>
    </publicationStmt>
</biblFull>
]]>
</eg>
<!-- MSM! please check/expand on these details: you have the book!  -->
<!-- Done.  Robinson corrected to Rolf, bracketed (titlep has R.)   -->

<p>A list of bibliographic items, of whatever kind, may be treated in
the same way as any other list (see section <ptr target=COli>).
Alternatively, the specialized <gi>listBibl</gi> element may be used.
The difference between the two is that a <gi>list</gi> contains
<gi>item</gi> elements, within which bibliographic elements (<gi>bibl</gi>,
<gi>biblStruct</gi> or <gi>biblFull</gi>) may appear, as well as other
phrase- and paragraph-level elements, whereas the <gi>listBibl</gi> may
contain only bibliographic elements, optionally preceded by a heading and a
series of introductory paragraphs.  The former would be appropriate
for a list of bibliographic elements in which descriptive prose
predominated, and the latter for a more formal bibliography.  The
following are thus both legal encodings of a list of bibliographic
entries:  a <gi>listBibl</gi>:

<!-- <note place=foot>In these examples, white space has      -->
<!-- been liberally used to help indicate the structure of    -->
<!-- the entries; it is not required and is not necessarily   -->
<!-- used in practice.  </note>                               -->

<eg><![ CDATA[
<listBibl>
<head>Bibliography</head>
<biblStruct id=NEL80>
    <analytic>
         <author>Nelson, T. H.</>
         <title>Replacing the printed word:
                a complete literary system.</>
    </analytic>
    <monogr>
         <title>Information Processing '80:  Proceedings of the IFIPS
                Congress, October 1980</>
         <editor>Simon H. Lavington</>
         <imprint>
              <publisher>North-Holland</>
              <pubPlace>Amsterdam</>
              <date>1980</>
         </imprint>
         <biblScope>pp 1013-23
    </monogr>
    <note>Apparently a draft of section 4 of <title>Literary
          Machines</title>.</note>
</biblStruct>
<bibl id=NEL88>Ted Nelson:  <title>Literary Machines</title>
    (privately published, 1987)</bibl>
<bibl id=BAX88>
    <author>Baxter, Glen</author>
    <title>Glen Baxter His Life: the years of struggle</title>
    London: Thames and Hudson, 1988.
    </bibl>
</listBibl>
]]>
</eg>
or a simple <gi>list</gi>:
<eg><![ CDATA[
<list><head>Bibliography</>
<item><bibl id=NEL80>
        <author>Nelson, T. H.</>
        <title level=a>Replacing the printed word:
             a complete literary system.</>
        <title level=m>Information Processing '80:
             Proceedings of the IFIPS Congress, October 1980</>
        <editor>Simon H. Lavington</>
        <publisher>North-Holland</>
        <pubPlace>Amsterdam</>
        <date>1980</>
        <biblScope>pp 1013-23
        <note>Apparently a draft of section 4 of <title>Literary
         Machines</title>.</note>
    </bibl></item>
<item><bibl id=NEL88>Ted Nelson:  <title>Literary Machines</title>
    (privately published, 1987)</bibl></item>
<item><bibl id=BAX88>
    <author>Baxter, Glen</author>
    <title>Glen Baxter His Life: the years of struggle</title>
    London: Thames and Hudson, 1988.
    </bibl></item>
</list>
]]>
</eg>

<p>The formal declarations for these elements are as follows:

<eg id=dcobi>
<![ CDATA [
<!-- 6.10.1:  Tags for Bibliographic References               -->
<!ELEMENT bibl          - o  (#PCDATA | %m.phrase; | 
                             %m.biblPart;)*                     >
<!ATTLIST bibl               %a.global;
                             %a.declarable;                     >
<!ELEMENT biblStruct    - o  (analytic?, (monogr, series*)+, 
                             (note | idno)*)                    >
<!ATTLIST biblStruct         %a.global;
                             %a.declarable;                     >
<!ELEMENT biblFull      - o  (titleStmt, editionStmt?, extent?, 
                             publicationStmt, seriesStmt?, 
                             notesStmt?, sourceDesc*)           >
<!ATTLIST biblFull           %a.global;
                             %a.declarable;                     >
<!ELEMENT listBibl      - -  (head?, (bibl | biblStruct | 
                             biblFull)+, trailer?)              >
<!ATTLIST listBibl           %a.global;
                             %a.declarable;                     >
<!-- (continued in sec. 6.10.2.1, 6.10.2.2, 6.10.2.3)         -->
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>

<!>

<div3 id=CObico><head>Components of Bibliographic References</head>

<p>This section discusses a number of very commonly occurring component
elements of bibliographic references.  They fall into four groups:
<list type=bullets>
<item>elements for grouping components of the

<term rend='noindex'>analytic</term>,
<term rend='noindex'>monographic</term>,
and <term rend='noindex'>series</term>
<index level1='analytic level' level2='bibliographic'>
<index level1='monographic level' level2='bibliographic'>
<index level1='series level' level2='bibliographic'>
<index level1='bibliographic references' level2='analytic level'>
<index level1='bibliographic references' level2='monographic level'>
<index level1='bibliographic references' level2='series level'>
levels in a structured bibliographic reference
<item>titles of various kinds, and statements of intellectual
responsibility (authorship, etc.)
<item>information relating to the publication, pagination, etc. of an
item
<item>annotation, commentary and further detail
</list>

The following sections describe the elements which may be used to
represent such information within a <gi>bibl</gi> or
<gi>biblStruct</gi> element.  Within the former, any or all of these
may be used and in any order.  Within the latter, such of these elements
as exist for a given reference must be distinguished, and must also be
presented in a specific order, discussed further below (section <ptr
target=CObicoo>).

<div4 id=CObicol><head>Analytic, Monographic, and Series Levels</head>

<p>In common library practice a clear distinction is made between an
individual item within a larger collection and a free-standing book,
journal, or collection.  Similarly a book in a series is distinguished
sharply from the series within which it appears.  An article forming
part of a collection which itself appears in a series thus has a
bibliographic description with three quite distinct levels of
information:

<list type=ordered>

<item>the <term rend='noindex'>analytic</term>
<index level1='analytic level' level2='bibliographic'>
level, giving the title, author, etc., of the article;

<item>the <term rend='noindex'>monographic</term>
<index level1='monographic level' level2='bibliographic'>
level, giving the title, editor, etc., of the collection;

<item>the <term rend='noindex'>series</term>
<index level1='series level' level2='bibliographic'>
level, giving the title of the series, possibly the names of its
editors, etc., and the number of the volume within that series.

</list>

In the same way, an article in a journal requires at least two levels of
information:  the analytic level describing the article itself, and the
monographic level describing the journal.

<p>These three levels may be distinguished within a <gi>bibl</gi>
element, and must be distinguished within a <gi>biblStruct</gi> element
if present, by means of the following tags:

<list type=gloss>
<label><gi>analytic</gi></label>
<item>contains bibliographic elements describing an item (e.g. an
article or poem) published within a monograph or journal 
and not as an
independent publication.</item>
<label><gi>monogr</gi></label>
<item>contains bibliographic elements describing an item (e.g. a 
book
or journal) published as an independent item (i.e. as 
a separate
physical object).</item>
<label><gi>series</gi></label>
<item>contains information about the series in which a book or 
other
bibliographic item has appeared.</item>
</list>


<p>For purposes of TEI encoding, journals and anthologies are both
treated as monographs; a journal title will thus be tagged <tag>title
level=j</tag> or <tag>monogr</tag><tag>title</tag> ...
<tag>/title</tag> ...  <tag>/monogr</tag>.  Individual articles in the
journal or collected texts should be treated at the
<soCalled>analytic</soCalled> level.  When an article has been printed
in more than one journal or collection, the bibliographic reference may
have more than one <gi>monogr</gi> element, each possibly followed by
one or more <gi>series</gi> elements.  A <gi>series</gi> element always
relates to the most recently preceding <gi>monogr</gi> element.
(Whether reprints of an article are treated in the same bibliographic
reference or a separate one varies among different styles.  Library
lists typically use a different entry for each publication, while
academic footnoting practice typically treats all publications of the
same article in a single entry.)

<p>For example, the article cited in this example has been published
twice, once in a journal and once in a collection which appeared in a
series:

<eg>
<![ CDATA [
    <biblStruct>
         <analytic>
              <author>Thaller, Manfred</author>
              <title level=a>A Draft Proposal for a Standard for the
                     Coding of Machine Readable Sources</>
         </analytic>
         <monogr>
              <!-- In -->
              <title level=j>Historical Social Research</title>
              <imprint>
                    <biblScope type=vol>40</>
                    <date>October 1986</>
                    <biblScope type=pages>3-46</>
              </imprint>
         </monogr>
         <monogr>
              <!-- Rpt. in -->
              <title level=m>Modelling Historical Data:
                     Towards a Standard for Encoding and Exchanging
                     Machine-Readable Texts</title>
              <editor>Daniel I. Greenstein</editor>
              <imprint>
                   <pubPlace>St. Katharinen</pubPlace>
                   <publisher>Max-Planck-Institut f&uuml;r Geschichte
                         In Kommission bei
                         Scripta Mercaturae Verlag</publisher>
                   <date>1991</date>
              </imprint>
         </monogr>
         <series>
              <title level=s>Halbgraue Reihe
                   zur Historischen Fachinformatik</title>
              <respStmt><resp>Herausgegeben von</resp>
                    <name type=person>Manfred Thaller</>
                    <name type=org>Max-Planck-Institut f&uuml;r
                        Geschichte</>
              </respStmt>
              <title level=s>Serie A:  Historische Quellenkunden</>
              <biblScope>Band 11</biblScope>
         </series>
    </biblStruct>
]]>
</eg>

<p>Punctuation may not appear between the elements within a structured
bibliographic entry; if punctuation is to be given explicitly in the
encoding, it must be contained within the elements it delimits.  As the
example shows, it is possible to encode the entry without any
inter-element punctuation:  this facilitates use of the
<gi>biblStruct</gi> element in systems which can render bibliographic
references in any of several styles.

<p>The formal declarations for the elements defined in this section are
as follows:

<eg id=dcobilv>
<![ CDATA [
<!-- 6.10.2.1:  Tags for Bibliographic References (cont'd)    -->
<!-- (continuation of sec. 6.10.1)                            -->
<!ELEMENT analytic      - O  (author | editor | respStmt | 
                             title)*                            >
<!ATTLIST analytic           %a.global;                         >
<!ELEMENT monogr        - O  ( ( ((author | editor | 
                             respStmt)+, title+, (editor | 
                             respStmt)*) | (title+, (author | 
                             editor | respStmt)*))?, (note | 
                             meeting)*, (edition, (editor | 
                             respStmt)*)*, imprint, (imprint | 
                             extent | biblScope)* )             >
<!ATTLIST monogr             %a.global;                         >
<!ELEMENT series        - O  (title | editor | respStmt | 
                             biblScope | #PCDATA)*              >
<!ATTLIST series             %a.global;                         >
]]>
</eg>


<div4 id=CObicor><head>Authors, Titles, and Editors</head>

<p>Bibliographic references typically begin with a statement of the
title being cited and the names of those intellectually responsible for
it.  For articles in journals or collections, such statements should
appear both for the analytic and for the monographic level.  The
following elements are provided for tagging such elements:

<list type=gloss>
<label><gi>title</gi></label>
<item>contains the title of a work, whether article, book, 
journal, or
series, including any alternative titles or 
subtitles.
Attributes include:
<list type=gloss>
<label><att>level</att></label>
<item>indicates whether this is the title of an article, book, 
journal, series, or unpublished material.
Legal values are:
<list type=gloss>
<label><term>m</term></label>
<item>monographic title (book, collection, or other item 
published as a distinct item, including single volumes of 
multi-volume works)</item>
<label><term>s</term></label>
<item>series title</item>
<label><term>j</term></label>
<item>journal title</item>
<label><term>u</term></label>
<item>title of unpublished material (including theses and 
dissertations unless published by a commercial press)</item>
<label><term>a</term></label>
<item>analytic title (article, poem, or other item published as 
part of a larger item)</item>
</list></item>
<label><att>type</att></label>
<item>classifies the title according to some convenient typology.
Sample values include:
<list type=gloss>
<label><term>abbreviated</term></label>
<item>abbreviated form of title</item>
<label><term>main</term></label>
<item>main title</item>
<label><term>subordinate</term></label>
<item>subtitle, title of part</item>
<label><term>parallel</term></label>
<item>alternate title, often in another language, by which the 
work is also known</item>
</list></item>
</list>
</item>
<label><gi>author</gi></label>
<item>in a bibliographic reference, contains the name of the 
author(s),
personal or corporate,
of a work; the primary 
<term>statement of responsibility</term> for any

bibliographic item. </item>
<label><gi>editor</gi></label>
<item>secondary <term>statement of responsibility</term> for a

bibliographic item, for example the name of an individual, 
institution
or organization, (or of several such) acting 
as editor, compiler,
translator, etc. </item>
<label><gi>respStmt</gi></label>
<item>supplies a statement of responsibility for someone 
responsible for
the intellectual content of a text, 
edition, recording, or series, where
the specialized 
elements for authors, editors, etc. do
not suffice or do 
not apply.</item>
<label><gi>resp</gi></label>
<item>contains a phrase describing the nature of a person's

intellectual responsibility.</item>
<label><gi>name</gi></label>
<item>contains a proper noun or noun phrase.</item>
<label><gi>meeting</gi></label>
<item>in bibliographic references,
contains a description of the 
meeting or conference from which
the bibliographic item 
derives.</item>
</list>


<!-- some discussion of meeting shd be added but not sure where -->

<p>In bibliographic references, all titles should be tagged as such,
whether analytic, monographic, or series titles.  The single element
<gi>title</gi> is used for all these cases.  When it appears directly
within an <gi>analytic</gi>, <gi>monogr</gi>, or <gi>series</gi>
element, <gi>title</gi> is interpreted as belonging to the appropriate
level.  When it appears elsewhere, its <att>level</att> attribute should
be used to signal its bibliographic level.  It is a semantic error to
give a value for the <att>level</att> attribute which is inconsistent
with the context; such values may be ignored.  The <att>level</att>
value <code type=val>a</code> implies the analytic level; the values
<code type=val>m</code>, <code type=val>j</code>, and <code
type=val>u</code> imply the monographic level; the value <code
type=val>s</code> implies the series level.  Note, however, that the
semantic error occurs only if the nested title is directly enclosed by
the <gi>analytic</gi>, <gi>monogr</gi>, or <gi>series</gi> element; if
it is enclosed only indirectly, no semantic error need be present.  For
example, the analytic title may contain a monographic title:

<eg><![ CDATA [
<biblStruct>
    <analytic><author>Lucy Allen Paton</>
              <title>Notes on Manuscripts
                   of the <title level=m>Proph&eacute;cies
                   de Merlin</title></title>
    </analytic>
    <monogr><title level=j>PMLA</>
          <imprint><biblscope type=vol>8</>
            <date>1913</date>
            <biblscope type=pages>122</>
      </imprint>
    </monogr>
</biblStruct>
]]>
</eg>

In this case, the analytic title <q>Notes on Manuscripts of the
<title>Proph&eacute;cies de Merlin</title></q> needs no <att>level</att>
attribute because it is directly contained by the <gi>analytic</gi>
level; the monographic title contained within it, <q>Proph&eacute;cies
de Merlin,</q> does not create a semantic error because it is not
directly contained by the <gi>analytic</gi> element.

<p>In some bibliographic applications, it may prove useful to
distinguish main titles from subordinate titles, parallel titles, etc.
The <att>type</att> attribute is provided to allow this distinction to
be recorded.

<p>The following reference, from a national standard for bibliographic
references,<note place=foot><bibl>American National Standard for
Bibliographic References, ANSI Z39.29-1977 (New York:  American
National Standards Institute, 1977), p. 34 (sec.
A.2.2.1).</bibl></note>
illustrates this type of analysis with its distinction between main
and subordinate titles.

<eg><![ CDATA [
<bibl>Saarikoski, Pirkko-Liisa, and Paavo Suomalainen,
<title level=a type=main>Studies on the physiology of
the hibernating hedgehog, 15</title>
<title level=a type=subordinate>Effects of seasonal
and temperature changes on the in vitro
glycerol release from brown adipose tissue</>
<title level=j>Ann. Acad. Sci. Fenn., Ser. A4</>
<date>1972</> <biblScope type='vol: pp'>187: 1-4</>
</bibl>
]]>
</eg>
<!-- example from ANSI Z39.29, sec. A.2.2.1, p.34 -->

<p>Slightly more complex is the distinction made below among main,
subordinate, and parallel titles, in an example from the same source (p.
63).  The punctuation and the bibliographic analysis are those given in
ANSI Z39.29-1977; the punctuation is in the style prescribed by the
International Standard Bibliographic Description (ISBD).<note
place=foot>The analysis is not wholly unproblematic:  as the text of the
standard points out, the first subordinate title is subordinate only to
the parallel title in French, while the second is subordinate to both
the English main title and the French parallel title, without this
relationship being made clear, either in the markup given in the example
or in the reference structure offered by the standard.</note>

<eg><![ CDATA [
<bibl>Tchaikovsky, Peter Ilich.
<title level=m type=main>The swan lake ballet</>
= <title level=m type=parallel>Le lac des cygnes</>
: <title level=m type=subordinate>grand ballet en 4 actes</>
: <title level=m type=subordinate>op. 20</>
[Score].
New York:  Broude Brothers; [1951] (B.B. 59). vi, 685 p.
</bibl>
]]>
</eg>
<!-- example from ANSI Z39.29, sec. A.12.2, p.63 -->

<p>The elements <gi>author</gi> and <gi>editor</gi> have, for printed
books and articles, a fairly obvious significance; for other kinds of
bibliographic items their proper usage may be less obvious.  The
<gi>author</gi> element should be used for the person or agency with
primary responsibility for a work's intellectual content, and the
element <gi>editor</gi> for an editor of the work.  Thus an organization
such as a radio or television station is usually accounted
<soCalled>author</socalled> of a broadcast, for example, while the
author of a Government report will usually be the agency which produced
it.

<p>For anyone else with responsibility for the work, the
<gi>respStmt</gi> element should be used.  The nature of the
responsibility is indicated by means of a <gi>resp</gi> element, and the
person, organization etc. responsible by a <gi>name</gi> element.  At
least one of each of these must be given within the <gi>respStmt</gi>
element, followed optionally by any number of either.  Examples of
secondary responsibility of this kind include the roles of illustrator,
translator, editor, annotator.  The <gi>respStmt</gi> element may also
be used for editors, if it is desired to record the specific terms in
which their role is described.

<p>Examples of <gi>author</gi> and <gi>editor</gi> may be found in
sections <ptr target=CObity>, and <ptr target=CObicol>; wherever
<gi>author</gi> and <gi>editor</gi> may occur, the <gi>respStmt</gi>
element may also occur.  When one of these elements precedes or
immediately follows a title, it applies to that title; when it follows
an <gi>edition</gi> element or occurs within an edition statement, it
applies to the edition in question.

<p>In this example, the <gi>respStmt</gi> elements apply to the work as
a whole, not merely to the first edition:

<eg><![ CDATA [ <bibl>
    <author>Lominadze, D. G.</>
    <title level=m>Cyclotron waves in plasma.</title>
    <respStmt><resp>translated by</> <name>A. N. Dellis;</name>
              <resp>edited by</> <name>S. M. Hamberger.</name>
    </respStmt>
    <edition>1st ed.</>
    <imprint><pubPlace>Oxford:</> <publisher>Pergamon Press,</>
       <date>1981.</></imprint>
    <extent>206 p.</>
    <title level=s>International series in natural philosophy.</>
    <note place=inline>Translation of:
      <title level=m lang=RU>Ciklotronnye volny v plazme.</></>
</bibl>
]]>
</eg>
<!-- from ISO 690: 1987, clause 4.1, p. 2. -->

<p>In this example, by contrast, the <gi>respStmt</gi> element applies
to the edition, and not to the collection per se (Moser and Tervooren
were not responsible for the first thirty-five printings); the elements
of the reference have been reordered from their appearance on the title
page of the volume in order to ensure the correct relationship of the
collection title, the edition statement, and the statement of
responsibility.

<eg><![ CDATA [
<biblStruct>
<monogr>
    <title>Des Minnesangs Fr&uuml;hling</title>
    <note place=inline>Mit 1 Faksimile</note>
    <edition>36., neugestaltete und erweiterte Auflage</edition>
    <respStmt>
         <resp>Unter Benutzung der Ausgaben
         von <name>Karl Lachmann</> und <name>Moriz Haupt</>,
         <name>Friedrich Vogt</> und <name>Carl von Kraus</>
         bearbeitet von
         </resp>
         <name>Hugo Moser</>
         <!-- und -->
         <name>Helmut Tervooren</>
    </respStmt>
    <imprint>
         <biblScope type=volume>I</>
         <biblScope type='volume title'>Texte</>
         <pubPlace>Stuttgart</>
         <publisher>S. Hirzel Verlag</>
         <date>1977</>
    </imprint>
</monogr>
</biblStruct>
]]>
</eg>

<!-- reference taken from book in hand by MSM. -->
<!-- note that from the book it is impossible to -->
<!-- tell whether this is the 36th edition of -->
<!-- MF or of Moser/Tervooren's edition.  -->

<!-- <p>The formal definition of the <gi>name</gi>,           -->
<!-- <gi>person</gi>, <gi>individual</gi>, <gi>org</gi>, and  -->
<!-- <gi>organization</gi> elements may be found in section   -->
<!-- <ptr target=COna>.  Definitions for the                 -->
<!-- <gi>respStmt</gi> and <gi>role</gi> elements are         -->
<!-- provided in section <ptr target=HD6>.                   -->
<!-- This is a fat lie! (LB)                                  -->

With the exception of the <gi>name</gi> element (for which see section
<ptr target=COna>), the elements described in this section are defined
as follows:

<eg id=dcobicor>
<![ CDATA [
<!-- 6.10.2.2:  Tags for Bibliographic References (cont'd)    -->
<!-- (continuation of sec. 6.10.1)                            -->
<!ELEMENT author        - o  (%phrase.seq)                      >
<!ATTLIST author             %a.global;                         >
<!ELEMENT editor        - o  (%phrase.seq)                      >
<!ATTLIST editor             %a.global;
          role               CDATA               editor         >
<!ELEMENT respStmt      - o  (resp | name)+                     >
<!ATTLIST respStmt           %a.global;                         >
<!ELEMENT resp          - o  (%phrase.seq;)                     >
<!ATTLIST resp               %a.global;                         >
<!ELEMENT title         - o  (%paraContent)                     >
<!ATTLIST title              %a.global;
          level              (a | m | j | s | u) #IMPLIED
          type               CDATA               #IMPLIED       >
<!ELEMENT meeting       - -  (%paraContent)                     >
<!ATTLIST meeting            %a.global;                         >
]]>
</eg>


<div4 id=CObicoi><head>Imprint, Pagination, and Other Details</head>

<p>By <mentioned>imprint</mentioned> is meant all the information relating to the
publication of a work:  the person or organization by whose authority
and in whose name a bibliographic entity such as a book is made public
or distributed (whether a commercial publisher or some other
organization), the place of publication, and a date.  It may also
include a full address for the publisher or organization.
Full bibliographic references usually specify either the number of pages
in a print publication (or equivalent information for non-print
materials), or the specific location of the material being cited within
its containing publication.  The following elements are provided to hold
this information:

<list type=gloss>
<label><gi>imprint</gi></label>
<item>groups information relating to the publication or 
distribution
of a bibliographic item.  </item>
<label><gi>address</gi></label>
<item>contains a postal or other address, for example of a

publisher, an organization, or an individual.</item>
<label><gi>pubPlace</gi></label>
<item>contains the name of the place where a bibliographic item 
was
published.</item>
<label><gi>publisher</gi></label>
<item>provides the name of the organization responsible for
the 
publication or distribution of a bibliographic item.</item>
<label><gi>date</gi></label>
<item>contains a date in any format.</item>
<label><gi>idno</gi></label>
<item>supplies any standard or non-standard number used to 
identify a
bibliographic item.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>categorizes the number, for example as an ISBN or other 
standard series.</item>
</list>
</item>
<label><gi>extent</gi></label>
<item>describes the approximate size of the electronic text as 
stored on
some carrier medium, specified in any convenient 
units.</item>
<label><gi>biblScope</gi></label>
<item>defines the scope of a bibliographic reference, for example 
as a
list of pagenumbers, or a named subdivision of a 
larger work.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>identifies the type of information conveyed by the element, 
e.g. <q>pages</q>, <q>volume</q>.
Suggested values include:
<list type=gloss>
<label><term>pages</term></label>
<item>the element contains a page number or page range.</item>
<label><term>part</term></label>
<item>the element identifies a part of a book or collection.</item>
<label><term>volume</term></label>
<item>the element contains a volume number.</item>
<label><term>issue</term></label>
<item>the element contains an issue number, or volume and issue 
numbers.</item>
<label><term>chapter</term></label>
<item>the element contains a chapter indication (number and/or 
title)</item>
</list></item>
</list>
</item>
</list>


<p>For bibliographic purposes, usually only the place (or places) of
publication are required, possibly including the name of the country,
rather than a full address; the element <gi>pubPlace</gi> is provided
for this purpose.
<!-- for this reason, the element <gi>city</gi> may be supplied on -->
<!-- its own (outside of an <gi>address</gi> element) in this context.  -->
Where however the full postal address is likely to be of importance in
identifying or locating the bibliographic item concerned, it may be
supplied and tagged using the <gi>address</gi> element described in
section <ptr target=COnaad>.  Alternatively, if desired, the
<!-- <gi>place</gi> element described in section <ptr target=COnana> may be -->
<gi>rs</gi> or <gi>name</gi> elements described in section <ptr
target=COnars> may be used; this involves no claim that the information
given is either a full address or the name of a city.

<!-- <p>The name of the publisher of an item may be marked    -->
<!-- using the <gi>publisher</gi> tag; if the item is made    -->
<!-- public (<soCalled>published</soCalled>) by an            -->
<!-- organization other than a conventional publisher, it     -->
<!-- may be preferable to identify that organization using    -->
<!-- the <gi>org</gi> or <gi>organization</gi> element.       -->
<!-- This is frequently the case with technical reports:      -->

<p>The name of the publisher of an item should be marked using the
<gi>publisher</gi> tag even if the item is made public
(<soCalled>published</soCalled>) by an organization other than a
conventional publisher, as is frequently the case with technical
reports:

<eg><![ CDATA [
<biblStruct>
<monogr>
    <author>Nicholas, Charles K.</author>
    <author>Welsch, Lawrence A.</author>
    <title>On the interchangeability of SGML and ODA</title>
    <imprint>
         <pubPlace>Gaithersburg, MD</pubPlace>
         <publisher>National Institute of Standards and Technology
         </publisher>
         <date value='1992-01'>January 1992</date>
    </imprint>
    <extent>19 pp.</extent>
</monogr>
<idno type='NIST'>NISTIR 4681</idno>
</biblStruct>
]]>
</eg>

and with dissertations:

<eg><![ CDATA [
<biblStruct>
<monogr>
    <author>Hansen, W.</>
    <title level=u>Creation of hierarchic text
         with a computer display</>
    <note place=inline>Ph.D. dissertation</>
    <imprint>
         <publisher>Dept. of Computer Science, Stanford Univ.</>
         <pubPlace>Stanford, CA</>
         <date value='1971-06'>June 1971</>
    </imprint>
</monogr>
</biblStruct>
]]>
</eg>

<!-- reference is from p. 304, bibliography, of Reps and       -->
<!-- Teitelbaum, The Synthesizer Generator:  A system for     -->
<!-- constructing language-based editors.                     -->
<!-- or could maybe use a respStmt - if this were allowed in imprint -->

<p>When an item has been reprinted, especially reprinted without change
from a specific earlier edition, the reprint may appear in a
<gi>monogr</gi> element with only the <gi>imprint</gi> and other details
of the reprint.  In the following example, a microform reprint has been
issued without any change in the title or authorship.  The series
statement here applies only to the second <gi>monogr</gi> element.

<eg><![ CDATA [
<biblStruct>
<monogr>
    <author>Shirley, James</>
    <title type=main>The gentlemen of Venice</>
    <title type=subordinate>a tragi-comedie presented at
         the private house in Salisbury Court by
         Her Majesties servants</>
    <note place=inline>[Microform]</>
    <imprint>
         <pubPlace>London</>
         <publisher>H. Moseley</>
         <date>1655</>
    </imprint>
    <extent>78 p.</>
</monogr>
<monogr>
    <imprint>
         <pubPlace>New York</>
         <publisher>Readex Microprint</>
         <date>1953</>
    </imprint>
   <extent>1 microprint card, 23 x 15 cm.</>
</monogr>
<series>
    <title>Three centuries of drama:  English, 1642-1700</>
</series>
 </biblStruct>
]]>
</eg>
<!-- example from ANSI Z39.29, sec. A.3.12.1, p.41 -->

<p>A bibliographic description, particularly for an analytic title, will
often include some additional information specifying its location, for
example as a volume number, page number, range of page numbers, or name
or number of a subdivision of the host work.  The element
<gi>biblScope</gi> may be used to identify such information if it is
present.  Where it is desired to distinguish different classes of such
information (volume number, page number, chapter number, etc.), the
<att>type</att> attribute may be used with any convenient typology.

<p>When the item being cited is a journal article, the <gi>imprint</gi>
element describing the issue in which it appeared will typically contain
<gi>biblScope</gi> elements for volume and page numbers, together with a
<gi>date</gi> element.

<p>For example:

<eg><![ CDATA [
<biblStruct>
<analytic>
    <author>Wrigley, E. A.</>
    <title>Parish registers and the historian</>
</analytic>
<!-- in -->
<monogr>
    <editor>Steel, D. J.</>
    <title>National index of parish registers</>
    <imprint>
         <pubPlace>London</pubPlace>
         <publisher>Society of Genealogists</>
         <date value='1968'>1968</>
    </imprint>
    <biblScope type=volume>vol. 1</>
    <biblScope type=pages>pp. 155-167.</>
</monogr>
</biblStruct>
]]>
</eg>

<p>The <att>type</att> attribute on <gi>biblScope</gi> is optional:
both the following are legal examples:

<eg><![ CDATA [
<biblStruct>
<analytic>
    <author>Boguraev, Branimir</>
    <author>Neff, Mary</>
    <title>Text Representation, Dictionary Structure,
         and Lexical Knowledge</>
</analytic>
<!-- in -->
<monogr>
    <title level=j>Literary & Linguistic Computing</>
    <imprint>
         <biblScope type=volume>7</>
         <biblScope type=issue>2</>
         <date>1992</>
         <biblScope type=pages>110-112</>
    </imprint>
</monogr>
</biblStruct>
]]>
</eg>

<eg><![ CDATA [
<biblStruct>
<analytic>
    <author>Chesnutt, David</>
    <title>Historical Editions in the States</>
</analytic>
<!-- in -->
<monogr>
    <title level=j>Computers and the Humanities</>
    <imprint>
         <biblScope>25.6</>
         <date value='1991-12'>(December, 1991):</>
         <biblScope>377-380</>
    </imprint>
</monogr>
</biblStruct>
]]>
</eg>

<!-- TYPE attribute dropped from biblScope in Chesnutt        -->
<!-- example, as per WWP suggestion (otherwise lead-in makes  -->
<!-- no sense) (msm)                                          -->

<p>Formal definitions for the elements described in this section are as
follows:

<eg id=dcopub>
<![ CDATA [
<!-- 6.10.2.3:  Tags for Bibliographic References (cont'd)    -->
<!-- (continuation of sec. 6.10.1)                            -->
<!ELEMENT imprint       - O  (pubPlace | publisher | date | 
                             biblScope)*                        >
<!ATTLIST imprint            %a.global;                         >
<!ELEMENT publisher     - o  (%phrase.seq)                      >
<!ATTLIST publisher          %a.global;                         >
<!ELEMENT biblScope     - o  (%phrase.seq)                      >
<!ATTLIST biblScope          %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT pubPlace      - -  (%phrase.seq;)                     >
<!ATTLIST pubPlace           %a.global;
                             %a.names;                          >

<!-- Note and date are defined elsewhere, as are extent,      -->
<!-- address, and idno.                                       -->

]]>
</eg>


<div4 id=CObicos><head>Series Information</head>

<p>Series information may (in <gi>bibl</gi> elements) or must (in
<gi>biblStruct</gi> elements) be enclosed in a <gi>series</gi> element
or (in a <gi>biblFull</gi> element) a <gi>seriesStmt</gi> element.  The
title of the series may be tagged <tag>title level=s</tag>, the
volume number <tag>biblScope type=volume</tag>, and responsibility
statements for the series (e.g. the name and affiliation of the editor,
as in the example in section <ptr target=CObicol>) may be tagged
<tag>editor</tag> or <tag>respStmt</tag>.

<div4 id=CObicon><head>Notes and Other Additional Information</head>

<p>Explanatory notes about the publication of unusual items, the form of
an item (e.g.  <mentioned>[Score]</mentioned> or <mentioned>[Microform]</mentioned>), or
its provenance (e.g.  <mentioned>translation of ...</mentioned>) may be tagged
using the <gi>note</gi> element.  The same element may be used for any
descriptive annotation of a bibliographic entry in a database.

<list type=gloss>
<label><gi>note</gi></label>
<item>contains a note or annotation.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>describes the type of note.</item>
<label><att>place</att></label>
<item>indicates where the note appears in the source text.
Sample values include:
<list type=gloss>
<label><term>inline</term></label>
<item>note appears as a marked paragraph in the body of the text.</item>
<label><term>left</term></label>
<item>note appears in left margin.</item>
<label><term>foot</term></label>
<item>note appears at foot of page.</item>
<label><term>right</term></label>
<item>note appears in right margin.</item>
<label><term>app[aratus]</term></label>
<item>note appears in the apparatus at the foot of the page.</item>
<label><term>interlinear</term></label>
<item>note appears between lines of the text.</item>
<label><term>end</term></label>
<item>note appears at end of chapter or volume.</item>
</list></item>
</list>
</item>
</list>


<p>For example:

<eg><![ CDATA[
<bibl><author>Coombs, James H., Allen H. Renear,
       and Steven J. DeRose.</author>
       <title level=a>Markup Systems and the Future of Scholarly
       Text Processing.</title>
       <title level=j>Communications of the ACM</title>
       <biblScope>30.11 (November 1987):  933-947.</biblScope>
       <note>Classic polemic supporting descriptive over procedural
            markup in scholarly work.</note>
]]>
</eg>

<div4 id=CObicoo><head>Order of Components within References</head>

<p>The order of elements in <gi>bibl</gi> elements is not constrained.

<p>In <gi>biblStruct</gi> elements, the <gi>analytic</gi> element, if
it occurs, must come first, followed by one or more <gi>monogr</gi> and
<gi>series</gi> elements, which may appear intermingled (as long as a
<gi>monogr</gi> element comes first).  Within <gi>analytic</gi>, the
title(s), author(s), editor(s), and other statements of responsibility
may appear in any order; it is recommended that all forms of the title
be given together.  Within <gi>monogr</gi>, the author, editor, and
statements of responsibility may either come first or else follow the
monographic title(s).  Following these, the elements must appear in the
following order:

<list>
<item><gi>note</gi>s on the publication (and <gi>meeting</gi> elements
describing the conference, in the case of a proceedings volume)
<item><gi>edition</gi> elements, each followed by any related
<gi>editor</gi> or <gi>respStmt</gi> elements
<item><gi>imprint</gi>
<item><gi>biblScope</gi>
</list>
Within <gi>imprint</gi>, the elements allowed may appear in any
order.
<p>Finally, within the <gi>series</gi> information in a
<gi>biblStruct</gi>, the sequence of elements is not constrained.

<p>If more detailed structuring of a bibliographic description is
required, the <gi>biblFull</gi> element should be used.  This is not
further described here, as its contents are essentially equivalent to
those of the <gi>fileDesc</gi> element in the <gi>teiHeader</gi>, which
is fully described in section <ptr target=HD2>.

<div3 id=CObixr><head>Bibliographic Pointers </head>

<p>References which are pointers to bibliographic items, of whatever
kind, should be treated in the same way as other cross-references (see
section <ptr target='COxr'>).  As discussed in that section, cross
referencing within TEI texts is in general represented by means of
<gi>ptr</gi> or <gi>ref</gi> elements.  A <att>target</att> attribute on
these elements is used to supply an identifying value for the target of
the cross reference, which should be, in the case of bibliographic
elements, a bibliographic reference of some kind.  Where the form of the
reference itself is unimportant, or may be reconstructed mechanically,
or is not to be encoded, the <gi>ptr</gi> element is used, as in the
following example:

<eg><![ CDATA[
As shown above (<ptr target=NEL80>)...
]]>
</eg>

<p>Where the form of the reference is important, or contains additional
qualifying information which is to be kept but distinguished from the
surrounding text, the <gi>ref</gi> element should be used, as in the
following example:

<eg><![ CDATA[
Nelson claims <ref target=NEL80>(ibid, passim)</ref> ...
]]>
</eg>

<!--Following suggestion is only possible if <biblscope> becomes a phrase. -->
<!--Which it currently isnt.  -->


<!--<p>When it is desired to distinguish the short form of the reference -->
<!--itself from the additional qualifying information added to it, the -->
<!--additional information may be marked as a <gi>biblScope</gi> element: -->
<!--  -->
<!--<eg><![ CDATA[ -->
<!--Nelson claims (<ref target=NEL80>Nelson [1980], <biblScope>especially -->
<!--pages 13-37</ref>) ... -->
<!--]]> -->
<!--</eg> -->
<!--  -->
<!--(This distinction between the short form and the qualifying information -->
<!--may be useful in the context of document production or normalization of -->
<!--bibliographic references.) -->

It may be important to distinguish between the short form of a
bibliographic reference and some qualifying or additional information.
The latter should not appear within the scope of the <gi>ref</gi>
element when this is the case, as for example in an application
concerned to normalize bibliographic references:

<eg><![ CDATA[
Nelson claims (<ref target=NEL80>Nelson [1980]</ref>, pages 13-37) ...
]]>
</eg>

<div3 id=CObiot><head>Relationship to Other Bibliographic Schemes</head>

<p>The bibliographic tagging defined here can capture the distinctions
required by most bibliographic encoding systems; for the benefit of
users of some commonly used systems, the following lists of equivalences
are offered, showing the relationship of the markup defined here to the
fields defined for bibliographic records in the Scribe, BibTeX, and
ProCite systems.

<p>The various bibliographic fields defined for use in the Scribe and
BibTeX systems of bibliographic databases have the following equivalents
in the scheme presented here:<note place=foot>The BibTeX scheme is
intentionally compatible with that of Scribe, although it omits some
fields used by Scribe.  Hence only one list of fields is given
here.</note>
<!-- need bibliographic references for Scribe and BibTeX. -msm -->
Elements and structures available in the tag set defined here which
have no analogues in Scribe and BibTeX are not noted.

<list type=gloss>
<label>address     <item>tag as <tag>city</tag>, <tag>place</tag>,
or <tag>address</tag>
<label>annote      <item>tag as <tag>note</tag>
<label>author      <item>tag as <tag>author</tag>
<label>booktitle   <item>tag as <tag>title level=m</tag>
or <tag>title</tag> within <tag>monogr</tag>
<label>chapter     <item>tag as <tag>biblScope type=chapter</tag>
<label>date        <item>used only to record date entry was made in the
bibliographic database; not supported
<label>edition     <item>tag as <tag>edition</tag>
<label>editor      <item>tag as <tag>editor</tag> or <tag>respStmt</tag>
<label>editors     <item>tag as multiple <tag>editor</tag>
or <tag>respStmt</tag> elements
<label>fullauthor  <item>use the <att>reg</att> attribute
on <tag>author</tag> or <tag>name</tag>
<label>fullorganization <item>use the <att>reg</att> attribute
on <tag>name type=org</tag>
<label>howpublished  <item>tag as <tag>note</tag>, possibly using
the form <tag>note place=inline</tag>
<label>institution <item>used only for issuer of technical reports;
tag as <tag>publisher</tag>
<!-- , <tag>org</tag>,  or <tag>organization</tag> -->
<label>journal     <item>tag as <tag>title level=j</tag>
or <tag>title</tag> within <tag>monogr</tag>
<label>key         <item>used to specify an alternate sort key for
the bibliographic item, for use instead of
author's or editor's name; not supported
<label>meeting     <item>tag as <tag>meeting</tag> or as <tag>note</tag>
<label>month       <item>use <tag>date</tag>; if the date is not in a
trivially parseable form, use the <att>value</att>
attribute to provide an ISO-format equivalent
<label>note        <item>tag as <tag>note</tag>
<label>number      <item>tag as <tag>biblScope type=issue</tag>
or <tag>biblScope type=number</tag>; for
technical report numbers, use <tag>idno
type=docno</tag>
<label>organization <item>used only for sponsor of conference;
use <tag>name type=org</tag>
within <tag>respStmt</tag>
within <tag>meeting</tag> element
<label>pages       <item>tag as <tag>biblScope type=pages</tag>
<label>publisher   <item>tag as <tag>publisher</tag>
<label>school      <item>used only for institutions at which
thesis work is done; tag as <tag>publisher</tag>
<!-- org</tag>  or <tag>organization</tag> -->
<label>series      <item>tag as <tag>title level=s</tag>
or <tag>title</tag> within <tag>series</tag>
<label>title       <item>tag as <tag>title</tag> in appropriate
context or with appropriate <att>level</att>
value
<label>volume      <item>tag as <tag>biblScope type=volume</tag>
<label>year        <item>tag as <tag>date</tag>; if the date is not in a
trivially parseable form, use the <att>value</att>
attribute to provide an ISO-format equivalent
</list>
<!-- need similar list for ProCite -->


<!-- COdv Verse and Drama elements (new)                      -->
<!-- $Id: p2codv.odd,v 1.9 1998/02/01 17:55:08 tei Exp $ -->
<!--*
    * $Log: p2codv.odd,v $
    * Revision 1.9  1998/02/01 17:55:08  tei
    * fix log keyword (still need SGML normalization)
    *
    * Revision 1.8  98/02/01  17:51:31  tei
    * No changes made; this is a vacuous checkin
    *
    * Revision 1.7  94/03/27  21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    * -->
<!-- Revisions:                                               -->
<!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) -->
<!-- 93-11-18 : MSM : Change titles on divs for Verse, Drama  -->
<!-- 92-12-10 : MSM : add fix for partial LGs, from LB        -->
<!-- 92-12-09 : MSM : add clarifying comment on LB            -->
<!-- 92-12-09 : MSM : normalize sentence-end spacing          -->
<!-- 92-12-09 : MSM : rename metre as met                     -->
<!-- 92-12-09 : MSM : add blank after /speaker                -->
<!-- 92-12-07 : MSM : correct botched /eg                     -->
<!-- 92-12-07 : MSM : revise for publication                  -->
<!-- 92-12-07 : MSM : add example from Q1                     -->
<!-- 92-12-07 : MSM : do not change PCDATA in Tempest         -->
<!-- 92-12-06 : MSM : change dtdfrag ids, scan for long lines in eg -->
<!-- 92-12-06 : MSM : correct xref to COrs, idref in dtdfrags -->

<div2 id=COdv><head>Passages of Verse or Drama</head>

<p>The following elements are included in the core tag set for the
convenience of those encoding texts which include mixtures of prose,
verse and drama.

<list type=gloss>
<label><gi>l</gi></label>
<item>contains a single, possibly incomplete, line of verse.
Attributes include:
<list type=gloss>
<label><att>part</att></label>
<item>specifies whether or not the line is metrically complete.
Legal values are:
<list type=gloss>
<label><term>F</term></label>
<item>the final part of an incomplete line</item>
<label><term>Y</term></label>
<item>the line is metrically incomplete</item>
<label><term>N</term></label>
<item>either the line is complete, or no claim is made as to its 
completeness</item>
<label><term>I</term></label>
<item>the initial part of an incomplete line</item>
<label><term>M</term></label>
<item>a medial part of an incomplete line</item>
</list></item>
</list>
</item>
<label><gi>lg</gi></label>
<item>contains a group of verse lines functioning as a formal 
unit
e.g. a stanza, refrain, verse paragraph, etc.</item>
<label><gi>sp</gi></label>
<item>An individual speech in a performance text, or a passage

presented as such in a prose or verse text.</item>
<label><gi>speaker</gi></label>
<item>A specialized form of heading or label, giving the name of

one or more speakers in a dramatic text or fragment.</item>
<label><gi>stage</gi></label>
<item>contains any kind of stage direction within a dramatic text 
or
fragment.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates the kind of stage direction.
Suggested values include:
<list type=gloss>
<label><term>delivery</term></label>
<item>describes how a character speaks.</item>
<label><term>mixed</term></label>
<item>more than one of the above</item>
<label><term>location</term></label>
<item>describes a location.</item>
<label><term>entrance</term></label>
<item>describes an entrance.</item>
<label><term>business</term></label>
<item>describes stage business.</item>
<label><term>exit</term></label>
<item>describes an exit.</item>
<label><term>modifier</term></label>
<item>gives some detail about a character.</item>
<label><term>setting</term></label>
<item>describes a setting.</item>
<label><term>novelistic</term></label>
<item>is a narrative, motivating stage direction.</item>
</list></item>
</list>
</item>
</list>


<p>Full details of other, more specialized, elements for the encoding of
texts which are predominantly verse or drama are described in the
appropriate chapter of part three (for verse, see the verse base
described in chapter <ptr target=VE>; for performance texts, see the
drama base described in chapter <ptr target=DR>).  In this section, we
describe only the elements listed above, all of which can appear in any
text, whichever of the three modes prose, verse, or drama may predominate
in it.

<div3 id=COve><head>Core Tags for Verse</head>

<p>Like other written texts, verse texts or poems may be hierarchically
subdivided, for example into books or cantos.  These structural
subdivisions should be encoded using the general purpose <gi>div</gi>
or <gi>div1</gi> (etc.) elements described below in chapters <ptr
target=PR> and <ptr target=VE>.  The fundamental unit of a verse text
is the verse line rather than the paragraph, however.

<p>The <gi>l</gi> element is used to mark up verse lines, that is
metrical rather than typographic lines.  Where a metrical line is
interrupted by a typographic line break, the encoder may choose to
ignore the fact entirely or to use the empty <gi>lb</gi> (line break)
element discussed in <ptr target=COrs>.  In the copy text, the
following example is printed on four typographic lines, beginning with
the words <mentioned>There</mentioned>, <mentioned>From</mentioned>, <mentioned>The</mentioned>,
and <mentioned>the</mentioned>.

<eg><![ CDATA [
<l>There they lie, in the largest, in an
   open space in the woods,
<l>From 500 to 600 poor fellows &mdash; the groans
   and screams &mdash;
<l>The odor of blood, mixed with the fresh scent
   of the night, <lb>the grass, the trees &mdash;
   that Slaughter-house!
]]>
</eg>
<!-- Walt Whitman, 1863, cited by Daniel Aaron, The           -->
<!-- Unwritten War:  American Writers and the Civil War       -->
<!-- (London:  OUP, 1973).  Aaron doesn't give any more       -->
<!-- detailed citation.  Need to replace this with an         -->
<!-- example from a more important edition, one about whose   -->
<!-- line breaks one might reasonably care.                   -->

<p>Where verse lines are not properly nested within the enclosing
hierarchy (for example where verse lines cross larger boundaries such
as verse paragraphs or speeches) the encoder may choose to use one of
the techniques discussed in chapter <ptr target=NH>, or to use the
<att>part</att> attribute to indicate that the verse line is
incomplete, as in the following example:

<eg><![ CDATA [
 <l>Thou fumblest <name>Eros</>, and my Queenes a Squire
 <l>More tight at this, then thou:  Dispatch. O Loue,
 <l>That thou couldst see my Warres to day, and knew'st
 <l>The Royall Occupation, thou should'st see
 <l part=i>A Workeman in't.
 <stage>Enter an Armed Soldier.</stage>
 <l part=f>Good morrow to thee, welcome. ...
]]>
</eg>
<!-- Better example needed here -->
<!-- W. Shakespeare, Antony and Cleopatra, 4.4.14-21, cited   -->
<!-- from A New Variorum Edition of Shakespeare:  A & C,      -->
<!-- ed. Martin Spevack (NY:  MLA, 1990), p. 242.             -->
<!-- I have not had time to find a better example.  -MSM      -->

<p>In some verse forms, regular groupings of lines are regarded as units
of some kind, often identified by a regular verse scheme.  In stichic
verse and couplets, groups of lines analogous to paragraphs are often
indicated by indentation.  In other verse forms, lines are grouped into
irregular sequences indicated simply by white space.  The neutral
<gi>lg</gi> or line group element may be used to mark any such grouping
of lines; the <att>type</att> is available to further categorize the
line group where this is felt desirable, as in the following example.
This example also demonstrates the <att>rend</att> attribute to indicate
whether or not a line is indented.

<!-- rhyme is only enabled if you have the verse base   -->

<eg><![ CDATA [
<lg type=stanza>
<l>Come fill up the Glass,
<l rend=indent>Round, round let it pass,
<l>'Till our Reason be lost in our Wine:
<l rend=indent>Leave Conscience's Rules
<l rend=indent>To Women and Fools,
<l>This only can make us divine.
</lg>
<lg type=refrain n='Chorus'>
<l>Then a Mohock, a Mohock I'll be,
<l>No Laws shall restrain
<l>Our Libertine Reign,
<l>We'll riot, drink on, and be free.
</lg>
]]>
</eg><!-- from Gay's Beggars Opera -->

<p>For some kinds of analysis, it may be useful to identify different
kinds of line group within the same piece of verse.  Such line groups
may self-nest, in much the same way as the un-numbered <gi>div</gi>
element described in chapter <ptr target=PR>.  For example:

<!-- quote stanza from Sir Gawayn -->

<p>The <att>part</att> attribute may also be attached to a <gi>lg</gi>
element to indicate that it is incomplete, for example because it forms
part of a group that is divided between two speakers, as in the
following example:

<eg>
<![ CDATA [
<sp><speaker>First Voice</>
<lg type=stanza part=I>
<l>But why drives on that ship so fast
<l>Withouten wave or wind?
</lg>
<sp><speaker>Second Voice</speaker>
<lg part=F>
<l>The air is cut away before,
<l>And closes from behind.
</lg>
]]>
</eg><!-- Rime of the Ancient Marynere from Lyrical Ballads 1798 -->

<p>For alternative methods of aligning groups of lines which do not form
simple hierarchic groups, or which are discontinuous, see the more
detailed discussion in chapter <ptr target=SA>.  For discussion of
other elements and attributes specific to the encoding of verse, see
chapter <ptr target=VE>.

<p>These elements are defined as follows:
<eg id=dcove>
<![ CDATA [
<!-- 6.11.1:  Verse                                           -->
<!ELEMENT l             - O  (%paraContent)                     >
<!ATTLIST l                  %a.global;
                             %a.enjamb;
                             %a.metrical;
          part               (Y | N | I | M | F) N              >
<!ELEMENT lg            - O  ((%m.divtop)*, (l | lg)+, 
                             (%m.divbot)*)                      >
<!ATTLIST lg                 %a.global;
                             %a.divn;
                             %a.metrical;                       >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>


<div3 id=COdr><head>Core Tags for Drama</head>

<p>Like other written texts, dramatic and other <term>performance
texts</term> such as cinema or TV scripts are often hierarchically
organized, for example into acts and scenes.  These structural
subdivisions should be encoded using the general purpose <gi>div</gi> or
<gi>div1</gi> (etc.) elements described below in chapters <ptr
target=PR> and <ptr target=DR>.  Within these divisions, the body of a
performance text typically consists of <term
rend='noindex'>speeches</term>, often prefixed by a phrase indicating
who is speaking, and occasionally interspersed with stage directions of
various kinds.

<p>In the following simple example, each speech consists of a single
paragraph:

<eg><![ CDATA [
<div2 type=scene n='I.2'>
<head>Scene 2.</head>
<stage type=setting>Peachum, Filch.</stage>
<sp><speaker>FILCH.</speaker><p>Sir, Black Moll hath sent word her
Trial comes on in the Afternoon, and she hopes you will order Matters
so as to bring her off.
<sp><speaker>PEACHUM.</speaker><p>Why, she may plead her Belly
at worst; to my Knowledge she hath taken care of that Security.
But, as the Wench is very active and industrious, you may satisfy
her that I'll soften the Evidence.
<sp><speaker>FILCH.</speaker><p>Tom Gagg, sir, is found guilty.
]]>
</eg><!-- Gay's Beggars Opera -->

<p>In the following example, each speech consists of a sequence of verse
lines, some of them being marked as metrically incomplete:

<eg><![ CDATA [
<div1 type='Act' n='I'><head>ACT I</>
<div2 type='Scene' n='1'><head>SCENE I</head>
<stage rend=italic>
Enter Barnardo and Francisco, two Sentinels, at several doors</stage>
<sp><speaker>Barn</><l part=Y>Who's there?
<sp><speaker>Fran</><l>Nay, answer me.  Stand and unfold yourself.
<sp><speaker>Barn</><l part=i>Long live the King!
<sp><speaker>Fran</><l part=m>Barnardo?
<sp><speaker>Barn</><l part=f>He.
<sp><speaker>Fran</><l>You come most carefully upon your hour.
<sp><speaker>Barn</><l>'Tis now struck twelve.  Get thee to bed,
 Francisco.
<sp><speaker>Fran</><l>For this relief much thanks.'Tis bitter cold,
<l part=i>And I am sick at heart.
]]>
</eg><!-- Wells & Taylor, Hamlet I.i -->

<p>In some cases, as here in the First Quarto of <title>Hamlet</title>,
the printed speaker attributions need to be supplemented by use of the
<att>who</att> attribute; again, the lines are marked as complete or
incomplete:

<eg><![ CDATA [
<stage>Enter two Centinels.
<add place=right resp=ms>
Now call'd Bernardo & Francesco.
</add></stage>
<sp who='Francisco'><speaker>1.</>
    <l part=y>STand:  who is that?</sp>
<sp who='Barnardo'><speaker>2.</>
    <l part=y>Tis I.</sp>
<sp who='Francisco'><speaker>1.</>
    <l>O you come most carefully vpon your
       watch,</sp>
<sp who='Barnardo'><speaker>2.</>
    <l>And if you meete Marcellus and Horatio,
    <l>The partners of my watch, bid them make haste.</sp>
<sp who='Francisco'><speaker>1.</>
    <l part=y>I will:  See who goes there.</sp>
<stage>Enter Horatio and Marcellus.</>
<sp who='Horatio'><speaker>Hor.</>
    <l part=i>Friends to this ground.</sp>
<sp who='Marcellus'><speaker>Mar.</>
    <l part=f>And leegemen to the Dane,
    <l>O farewell honest souldier, who hath
    releeued you?</sp>
<sp who='Francisco'><speaker>1.</>
    <l>Barnardo hath my place, giue you good night.</sp>
]]>
</eg><!-- Hamlet I.i, Q1 (edited, from old file) -->

<p>By contrast with the preceding examples, the following encodes an
early printed edition without making any assumption about which parts
are prose or verse:

<eg><![ CDATA [
<div1 type=act n='I'>
<div2 type=scene n='1'>
<head rend=italic>Actus primus, Scena prima.</head>
<stage type=setting rend=italic>
A tempestuous noise of Thunder and Lightning heard:  Enter
a Ship-master, and a Boteswaine.</stage>
<sp><speaker>Master.</speaker><p> Bote-swaine.</sp>
<sp><speaker>Botes.</speaker><p> Heere Master: What cheere?</sp>
<sp><speaker>Mast.</speaker><p> Good: Speake to th' Mariners: fall
too't, yarely, or we run our selues a ground,
bestirre, bestirre.  <stage type=move>Exit.</stage></sp>
<stage type=move>Enter Mariners.</stage>
<sp><speaker>Botes.</speaker>
<p>Heigh my hearts, cheerely, cheerely my harts:
yare, yare: Take in the toppe-sale: Tend to th' Masters
whistle: Blow till thou burst thy winde, if roome e-nough.</sp>
]]>
</eg><!-- Tempest first folio -->

<p>The <gi>sp</gi> and <gi>stage</gi> elements should also be used to
mark parts of a text otherwise in prose which are presented as if they
were dialogue in a play.  For example:

<eg>
<![ CDATA [
<sp><speaker>The reverend Doctor Opimiam</speaker>
<p>I do not think I have named a single unpresentable
fish. </sp>
<sp><speaker>Mr Gryll</speaker><p>Bream, Doctor: there
is not much to be said for bream.</sp>
<sp><speaker>The Reverend Doctor
Opimiam</speaker><p>On the contrary, sir, I think
there is much to be said for him.  In the first
place....
<p>Fish, Miss Gryll -- I could discourse to you on
fish by the hour:  but for the present I will
forbear...
</sp>
]]>
</eg><!-- Peacock, Gryll Grange, p 778 -->

<eg>
<![ CDATA [
<sp><speaker>Lord Curryfin</speaker>
<stage>(after a pause).</stage>
<p><q>Mass</q> as the second grave-digger
says in <title>Hamlet</title>,
<q>I cannot tell.</q>
</sp>
<p>A chorus of laughter dissolved the sitting.
]]>
</eg><!-- ib. p 885 -->

<p>These elements are defined as follows:
<eg id=dcodr>
<![ CDATA [
<!-- 6.11.2:  Drama                                           -->
<!ELEMENT sp            - O  (speaker?, (p | l | lg | ab | seg 
                             | stage)+)                         >
<!ATTLIST sp                 %a.global;
          who                IDREFS              #IMPLIED       >
<!ELEMENT speaker       - O  (%phrase.seq)        -(speaker)    >
<!ATTLIST speaker            %a.global;                         >
<!ELEMENT stage         - -  (%specialPara)       -(stage)      >
<!ATTLIST stage              %a.global;
          type               CDATA               mix            >
<!-- This fragment is used in sec. 6.12                       -->
]]>
</eg>




<!-- COse Arbitrary Segments (P1 5.8.1 plus)                  -->
<!-- &p2.COse;  -->

<!-- 23e Other Tags for all Text Types                        -->
<!-- (id=p2.23E, file=P223E, MSM) (index)                     -->
<!-- &p2.COmi; -->


<div2 id=COov><head>Overview of the Core Tag Set

<p>Except for those tags designed to be used in concurrent markup
streams, all the elements described in this chapter occur in the
<term>core</term> of TEI tags, defined by the following DTD fragment.

<!-- First, the DTD defines a number of element classes used  -->
<!-- in the content models:                                   -->

<!-- <dtdFrag id=DCO                                          -->
<!--          file=teicore2                                   -->
<!--          n='Elements available in all TEI dtds'>         -->

<!-- <commDecl>TEIcore2:  Core Elements Available in All TEI  -->
<!-- DTDs</commDecl> &dtdstart;                               -->

<!-- <commDecl>Definition of useful element classes, for use  -->
<!-- in defining content models.</commDecl>                   -->

<!-- <claDecl classDoc=hqinter  type=model>                   -->
<!-- <claDecl classDoc=hqphrase type=model>                   -->
<!-- <claDecl classDoc=data     type=model>                   -->
<!-- <claDecl classDoc=edit     type=model>                   -->
<!-- <claDecl classDoc=refsys   type=model>                   -->
<!-- <claDecl classDoc=lists    type=model>                   -->
<!-- <claDecl classDoc=notes    type=model>                   -->
<!-- <claDecl classDoc=clbibl   type=model>                   -->
<!-- <claDecl classDoc=clseg    type=model>                   -->
<!-- <claDecl classDoc=clloc    type=model>                   -->
<!--                                                          -->
<!-- <claDecl classDoc=phrase   type=model>                   -->
<!-- <claDecl classDoc=inter    type=model>                   -->
<!-- <claDecl classDoc=chunk    type=model>                   -->
<!-- </dtdFrag>                                               -->

<!-- <p>Next, some useful basic content models are defined;   -->
<!-- these will be used in the formal declaration of many     -->
<!-- elements:                                                -->

<!-- <dtdFrag id=DCO2                                         -->
<!--          file=teicore2                                   -->
<!--          contin=DCO>                                     -->

<!-- <commDecl>Definition of useful content                   -->
<!-- models.</commDecl>                                       -->

<!-- <entDecl entDoc=phrseq>                                  -->
<!-- <entDecl entDoc=chkseq>                                  -->
<!-- <entDecl entDoc=peparac>                                 -->
<!-- <entDecl entDoc=pespecp>                                 -->
<!-- </dtdFrag>                                               -->

<!-- <p>Finally, the elements of the TEI core are themselves  -->
<!-- defined:                                                 -->

<eg id=dco>
<![ CDATA [
<!-- 6.12: Elements available in all forms of the TEI main    -->
<!-- DTD                                                      -->
<!-- Definition of elements, sub-group by sub-group.          -->

<!-- ... declarations from section 6.1                        -->
<!--     (Paragraph)                                          -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.3.2.1                    -->
<!--     (Highlighted phrases)                                -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.4.1                      -->
<!--     (Proper Nouns)                                       -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.4.3                      -->
<!--     (Numbers and measures)                               -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.4.4                      -->
<!--     (Dates and times)                                    -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.4.5                      -->
<!--     (Abbreviations)                                      -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.5.1                      -->
<!--     (Editorial tags for correction)                      -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.5.2                      -->
<!--     (Editorial tags for regularization)                  -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.5.3                      -->
<!--     (Other editorial tags)                               -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.4.2                      -->
<!--     (Addresses and their components)                     -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.6                        -->
<!--     (Simple cross references)                            -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.7                        -->
<!--     (Lists and List Items)                               -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.8.1                      -->
<!--     (Annotation)                                         -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.9.3                      -->
<!--     (Milestone tags)                                     -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.10.1                     -->
<!--     (Tags for Bibliographic References)                  -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.11.1                     -->
<!--     (Verse)                                              -->
<!--     go here ...                                          -->
<!-- ... declarations from section 6.11.2                     -->
<!--     (Drama)                                              -->
<!--     go here ...                                          -->
]]>
</eg>


<!-- dtdRef dtdFrag=DCOse -->
            <!-- 6 Tags in All TEI DTDs -->
