<!-- $Id: p2tc.odd,v 1.13 1998/02/05 17:14:35 tei Exp $ -->
<!--*
    **
    * $Log: p2tc.odd,v $
    * Revision 1.13  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.12  98/02/01  17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.11  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.10  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    *
    * Revision 1.9  1994/04/07  16:33:44  msmcq
    * Typos from WWP reader
    *
    * Revision 1.8  1994/04/01  16:38:10  msmcq
    * changes / fixes during validation of DTD
    *
    * Revision 1.7  1994/03/27  16:31:35  lou
    * smefinal check
    *
    * Revision 1.4  1994/03/08  03:13:48  msmcq
    * revision for P3
    *
    * Revision 1.3  1994/02/11  23:04:12  msmcq
    * add RCS id, log keywords
    * -->
<!-- Revisions:                                               -->
<!-- 7 jan 98 : LB : tag "wit" as attribute -->
<!-- 4 Jan 98 : LB : change "has to" to "need" per MSM        -->
<!-- 94-04-07 : MSM : remove line break in a div head         -->
<!-- 94-03-30 : MSM : make .ent file                          -->
<!-- 94-03-29 : MSM : add TYPE to cladecl for fragment tags   -->
<!-- 94-03-29 : MSM : add declaration for class fragment(ary) -->
<!-- 94-03-07 : MSM : changes from CH                         -->
<!-- 94-03-03 : MSM : changes from RC                         -->
<!-- 94-02-11 : MSM : Added RCS id                            -->
<!-- 94-02-04 : MSM : catch wit/ness renaming slip            -->
<!-- 94-02-04 : MSM : fix tag slip, idref error               -->
<!-- 94-02-04 : MSM : complete 2d pass                        -->
<!-- 94-02-03 : MSM : 2d pass                                 -->
<!-- 94-01-25 : MSM : mess around with ids, idrefs            -->
<!-- 94-01-25 : MSM : finish first pass for P3                -->
<!-- 94-01-25 : MSM : fix tagging error                       -->
<!-- 94-01-23 : MSM : through line 1130 (end of locref meth)  -->
<!-- 94-01-22 : MSM : begin revision for P3                   -->
<!-- 93-06-05 : MSM : remove . from col 1                     -->
<!-- 93-06-03 : MSM : add editorial note                      -->
<!-- 27 May: LB fixed tagging -->

<div1 id="TC" n="19"><head>Critical Apparatus</head>

<p>Scholarly editions of texts, especially texts of great antiquity or
importance, often record some or all of the known variations among
different <term>witnesses</term> to the text.  Witnesses to a text may
include authorial or other manuscripts, printed editions of the work,
early translations, or quotations of a work in other texts.
Information concerning variant readings of a text may be accumulated in
highly structured form in a critical apparatus of variants.  This
chapter defines an additional tag set for use in encoding such an
apparatus of variants, which may be used in conjunction with any of the
base tag sets defined in these Guidelines.  It also defines an element
class which provides extra attributes for some elements of the core tag
set when this additional tag set is selected.</p>

<p>This tag set is selected as described in <ptr target="STin">; in a
document which uses the markup described in this chapter, the document
type declaration should contain the following declaration of the entity
<ident type="pe">TEI.textcrit</ident>, or an equivalent one:

<eg>
<![ CDATA [
<!ENTITY % TEI.textcrit 'INCLUDE'>
]]>
</eg>

The entire document type declaration for a document using this
additional tag set together with the base tag set for prose might look
like this:

<eg>
<![ CDATA [
 <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
    <!ENTITY TEI.prose     'INCLUDE' >
    <!ENTITY TEI.textcrit  'INCLUDE' >
 ]>
]]>
</eg></p>

<p>The overall document type declaration for this additional tag set
has the following structure.  First, the file
<ident type="file">teitc2.ent</ident> defines some element classes
relevant to this tag set:

<eg id=dtce>
<![ CDATA [
<!-- 19:  Entity classes for text criticism                   -->
<!-- Text Encoding Initiative: Guidelines for Electronic      -->
<!-- Text Encoding and Interchange. Document TEI P3, 1994.    -->

<!-- Copyright (c) 1994 ACH, ACL, ALLC. Permission to copy    -->
<!-- in any form is granted, provided this notice is          -->
<!-- included in all copies.                                  -->

<!-- These materials may not be altered; modifications to     -->
<!-- these DTDs should be performed as specified in the       -->
<!-- Guidelines in chapter "Modifying the TEI DTD."           -->

<!-- These materials subject to revision. Current versions    -->
<!-- are available from the Text Encoding Initiative.         -->

<!ENTITY % x.fragmentary ''                                     >
<!ENTITY % m.fragmentary '%x.fragmentary lacunaEnd | 
           lacunaStart | witEnd | witStart'                     >
<!ENTITY % a.fragmentary '
          wit                CDATA               #IMPLIED'      >
<!ENTITY % a.readings '
          wit                CDATA               #IMPLIED
          cause              CDATA               #IMPLIED
          varSeq             NUMBER              #IMPLIED
          resp               CDATA               %INHERITED
          hand               IDREF               %INHERITED
          type               CDATA               #IMPLIED'      >
]]>
</eg>


The file <ident type="file">teitc2.dtd</ident> defines the elements
themselves:

<eg id=dtc>
<![ CDATA [
<!-- 19:  Tags for text criticism                             -->
<!-- Text Encoding Initiative: Guidelines for Electronic      -->
<!-- Text Encoding and Interchange. Document TEI P3, 1994.    -->

<!-- Copyright (c) 1994 ACH, ACL, ALLC. Permission to copy    -->
<!-- in any form is granted, provided this notice is          -->
<!-- included in all copies.                                  -->

<!-- These materials may not be altered; modifications to     -->
<!-- these DTDs should be performed as specified in the       -->
<!-- Guidelines in chapter "Modifying the TEI DTD."           -->

<!-- These materials subject to revision. Current versions    -->
<!-- are available from the Text Encoding Initiative.         -->

<!-- ... declarations from section 19.1.1                     -->
<!--     (Apparatus entry)                                    -->
<!--     go here ...                                          -->
<!-- ... declarations from section 19.1.2                     -->
<!--     (Readings)                                           -->
<!--     go here ...                                          -->
<!-- ... declarations from section 19.1.3                     -->
<!--     (Reading Groups)                                     -->
<!--     go here ...                                          -->
<!-- ... declarations from section 19.1.4.1                   -->
<!--     (Witness Details)                                    -->
<!--     go here ...                                          -->
<!-- ... declarations from section 19.1.4.2                   -->
<!--     (Source-text Witness Lists in Apparatus)             -->
<!--     go here ...                                          -->
<!-- ... declarations from section 19.1.4.3                   -->
<!--     (Witness Lists in Front Matter)                      -->
<!--     go here ...                                          -->
<!-- ... declarations from section 19.1.5                     -->
<!--     (Fragmentary witnesses)                              -->
<!--     go here ...                                          -->
]]>
</eg>
</p>

<p>Information about variant readings (whether or not represented by a
critical apparatus in the source text) may be recorded in a series of
<term>apparatus entries</term>, each entry documenting one
<term>variation</term>, or set of readings, in the text.  Tags for the
apparatus entry and readings, and for the documentation of the witnesses
whose readings are included in the apparatus, are described in section
<ptr target="TCapll">.  Special tags for fragmentary witnesses are
described in section <ptr target="TCapmi">.  The available methods for
embedding the apparatus in the rest of the text, or for linking an
external apparatus to the base text, are described in section <ptr
target="TCaplk">.  Finally, several extra attributes for some tags of the
core tag set, made available when the additional tag set for text
criticism is selected, are documented in section <ptr target="PHco">.

<!-- <p>An apparatus is composed of a series of apparatus     -->
<!-- (<gi>app</gi>) elements.  The tags used within           -->
<!-- apparatus are presented in three sections.  Tags for     -->
<!-- the low-level elements contained within each             -->
<!-- <gi>app</gi> element are discussed in section <ptr      -->
<!-- target=TCapll>:  lemma (<gi>lem</gi>); reading           -->
<!-- (<gi>rdg</gi>), reading group (<gi>rdgGrp</gi>),        -->
<!-- witness (<gi>wit</gi>) and witness detail                -->
<!-- (<gi>wit.detail</gi>) tags.  The <gi>app</gi> element    -->
<!-- itself is discussed in section <ptr target=TCapen>.     -->
<!-- Finally, in section <ptr target=TCaplk>, mechanisms     -->
<!-- are presented for relating each variant within an        -->
<!-- apparatus to other variants within the apparatus and to  -->
<!-- the base text on which they express variation.           --></p>

<p>Many examples given in this chapter refer to the following texts
of the opening (usually just line 1) of Chaucer's <title>Wife of
Bath's Prologue</title>:

<list type="gloss">

<label>El</label> <item>Ellesmere, Huntingdon Library 26.C.9:
<q rend="display">
Experience though noon Auctoritee /
Were in this world, were right ynogh to me /
To speke of wo that is in mariage; ...
</q></item>

<label>Hg</label> <item>Hengwrt, National Library of Wales, Aberystwyth,
Peniarth 392D:
<q rend="display">
Experience thogh noon Auctoritee /
Were in this world, is right ynogh for me /
To speke of wo that is in mariage; ...
</q></item>

<label>La</label> <item>British Library Lansdowne 851:
<q rend="display">
Experiment thouh none auctorite /
Were in this world, is right ynohe for me /
To speke of wo that is in mariage; ...
</q></item>

<label>Ra2</label><item>Bodleian Library Rawlinson Poetic 149:
<q rend="display">
Eryment though none auctorite /
Were in this world, it is right ynow for me /
To speke of wo that is in mariage; ...
</q></item>

</list></p>

<div2 id="TCapll"><head>The Apparatus Entry, Readings, and Witnesses</head>

<p>This section introduces the fundamental markup methods used to encode
textual variations:

<list type="bullets">
<item>the <gi>app</gi> element for entries in the critical apparatus:
see section <ptr target="TCapen">.</item>
<item>elements for identifying individual readings: see section <ptr
target="TCaplr">.</item>
<item>ways of grouping readings together: see section <ptr
target="TCapsu">.</item>
<item>methods of identifying which witnesses support a particular
reading, and for describing the witnesses included in the
apparatus: see section <ptr target="TCaplw">.</item>
<item>elements for indicating which portions of a text are covered by
fragmentary witnesses: see section <ptr target="TCapmi">.</item>
</list></p>

<div3 id="TCapen"><head>The Apparatus Entry</head>

<p>Individual textual variations are encoded using the <gi>app</gi>
element, which groups together all the readings constituting the
variation.  The identification of discrete textual variations or
apparatus entries is not a purely mechanical process; different editors
may group readings differently.  No rules are given here as to how to
group readings into apparatus entries; the tags given here may be used
to group readings in whatever way the editor finds most perspicuous or
useful.</p>

<p>The individual apparatus entry is encoded with the <gi>app</gi>
element:
<list type=gloss>
<label><gi>app</gi></label>
<item>contains one entry in a critical apparatus, with an 
optional
lemma and at least one reading.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the variation contained in this element 
according to some convenient typology.</item>
<label><att>from</att></label>
<item>identifies the beginning of the lemma in the base text, if 
necessary.</item>
<label><att>to</att></label>
<item>identifies the endpoint of the lemma in the base text, if 
necessary.</item>
<label><att>loc</att></label>
<item>indicates the location of the variation, when the 
location-referenced method of apparatus markup is used.</item>
</list>
</item>
</list>
</p>

<p>The attributes <att>loc</att>, <att>from</att>, and <att>to</att>,
are used to link the apparatus entry to the base text.  Several methods
may be used for such linkage, each involving a slightly different usage
for these attributes.  Linkage between text and apparatus is described
below in section <ptr target="TCaplk">.</p>

<p>Each <gi>app</gi> element comprises one or more readings, which in
turn are encoded using the <gi>rdg</gi> or other elements, as described
in the next section.  A very simple partial apparatus for the first line
of the <title>Wife of Bath's Prologue</title> might take a form
something like this:

<eg>
<![ CDATA [
<app>
  <rdg wit='El'>Experience though noon Auctoritee</rdg>
  <rdg wit='La'>Experiment thogh noon Auctoritee</rdg>
  <rdg wit='Ra2'>Eryment though none auctorite</rdg>
</app>
]]>
</eg>

Of course, in practice the apparatus will be somewhat more complex.
Specifically, it may be desired to
record more obviously that manuscripts El and La agree on the
words <q>noon Auctoritee</q>, to indicate a preference for one
reading, etc.  The following sections on
readings, subvariation, and witness information describe some of the
more important complications which can arise.</p>

<p>The structure of an <gi>app</gi> element is formally defined as
follows:

<eg id=dtcapen>
<![ CDATA [
<!-- 19.1.1:  Apparatus entry                                 -->
<!ELEMENT app           - O  ((lem, wit?)?, ((rdg, wit?) | 
                             (rdgGrp, wit?))+)                  >
<!ATTLIST app                %a.global;
          to                 IDREF               #IMPLIED
          from               IDREF               #IMPLIED
          loc                CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 19                         -->
]]>
</eg>
</p></div3>

<div3 id="TCaplr"><head>Readings</head>

<p>Individual readings are the crucial elements in any critical
apparatus of variants.  The following elements should be used to tag
individual readings within an apparatus entry:

<list type=gloss>
<label><gi>lem</gi></label>
<item>contains the lemma, or base text, of a textual variation.</item>
<label><gi>rdg</gi></label>
<item>contains a single reading within a textual variation.</item>
</list>


N.B. the term <term>lemma</term> is used here in the text-critical
sense of <gloss>the reading accepted as that of the original or of the
base text</gloss> --- it is not to be confused with <gloss>the heading
of an entry in a reference book, especially a dictionary,</gloss> or
<gloss>a subsidiary proposition introduced in the proof of some other
proposition; a helping theorem.</gloss></p>

<p>In recording readings within an apparatus entry, the <gi>rdg</gi>
element may always be used; each <gi>app</gi> must contain at least one
<gi>rdg</gi>.</p>

<p>The <gi>lem</gi> element may also be used, under some circumstances,
to record the base text of the source edition, to mark the readings of a
base witness, to indicate the preference of an editor or encoder for a
particular reading, or to make clear, in cases of ambiguity, precisely
which portion of the main text the variation applies to.  Those who
prefer to work without the notion of a base text may prefer not to use
it at all.  How it is used depends in part on the method chosen for
linking the apparatus to the text; for more information, see section
<ptr target="TCaplk">.</p>

<p>Readings may be encoded individually, or grouped for perspicuity
using the <gi>rdgGrp</gi> element described in section <ptr
target="TCapsu">.</p>

<p>As members of the attribute class <ident type="class">readings</ident>,
both of these elements inherit the following attributes.  Some of
these attributes are intelligible only if the reading is ascribed to a
single witness; others have no such restriction.

<list type=gloss>
<label><att>wit</att></label>
<item>contains a list of one or more sigla of witnesses attesting 
a given reading.</item>
<label><att>type</att></label>
<item>classifies the reading according to some useful typology.
Sample values include:
<list type=gloss>
<label><term>substantive</term></label>
<item>the reading offers a substantive variant.</item>
<label><term>orthographic</term></label>
<item>the reading differs only orthographically, not in 
substance, from other readings.</item>
</list></item>
<label><att>cause</att></label>
<item>classifies the reading as original or non-original, 
according to some typology of possible origins.</item>
<label><att>varSeq</att></label>
<item>provides a number indicating the position of this reading 
in a sequence, when there is reason to presume a sequence 
to the variants on any one lemma.</item>
<label><att>hand</att></label>
<item>signifies the hand responsible for a particular reading in 
the witness.</item>
<label><att>resp</att></label>
<item>identifies the editor responsible for asserting a 
particular reading in the witness.</item>
</list>
</p>

<p>The <att>wit</att> attribute identifies the witnesses which have the
reading in question.  It is required if the apparatus gathers together
readings from different witnesses, but may be omitted in an apparatus
recording the readings of only one witness, e.g. substitutions,
divergent opinions on what is in the witness or on how to expand
abbreviations, etc.  Even in such a one-witness apparatus, however,
the <att>wit</att> attribute may still be useful when it is desired to
record the occurrence of a particular reading in some other witness.
For other methods of identifying the witnesses to a reading, see section
<ptr target="TCaplw">.

<!-- For example of wit in single-witness app, see PHcc.      -->

<!-- <p>The <att>wit</att> attribute is required in an        -->
<!-- apparatus gathering readings from different witnesses.   -->
<!-- It is optional in an apparatus gathering variant         -->
<!-- readings in the transcription of a single witness.       -->
<!-- Where the transcription records only variant readings    -->
<!-- within this witness (as substitutions, different         -->
<!-- editorial expansions, etc) then the <att>wit</att>       -->
<!-- attribute is redundant.  However, it may still be        -->
<!-- useful where it is desired to indicate within the        -->
<!-- transcription the occurrence of a particular reading in  -->
<!-- another witness (as in the example in section <ptr      -->
<!-- target=PHcc>).                                           --></p>

<p>The <att>type</att> attribute allows the encoder to classify readings
in any convenient way, for example as substantive variants of the lemma:

<eg>
<![ CDATA [
<app>
<lem wit='El Hg'>Experience</lem>
<rdg wit='La'  type='substantive'>Experiment</rdg>
<rdg wit='Ra2' type='substantive'>Eryment</rdg>
</app>
]]>
</eg>

or as orthographic variants:

<eg>
<![ CDATA [
<app>
  <lem wit='El Ra2'>though</lem>
  <rdg wit='Hg' type='orthographic'>thogh</rdg>
  <rdg wit='La' type='orthographic'>thouh</rdg>
</app>
]]>
</eg></p>

<p>The <att>varSeq</att> and <att>cause</att> attributes may be used to
convey information on the sequence and cause of variation.  In the
following apparatus fragment, the reading <mentioned>Eryment</mentioned> is
tagged as sequential to (derived from) the reading
<mentioned>Experiment</mentioned>, and the cause
is given as loss of the abbreviation for <mentioned>per</mentioned>.

<eg>
<![ CDATA [
<app>
    <rdg varSeq=1 wit='La'>Experiment</rdg>
    <rdg varSeq=2 cause='abbreviation loss'
                  wit='Ra2'>Eryment</rdg>
</app>
]]>
</eg></p>

<p>If a manuscript is written in several hands, and it is desired to
report which hand wrote a particular reading, the <att>hand</att>
attribute should be used.  For example, in the Munich manuscript
containing the <title>Carmina Burana</title>,
the word <mentioned>alle</mentioned> has been changed
to <mentioned>allen</mentioned>:

<eg>
<![ CDATA [
<l>Swaz hi g&a;t umbe
<l>daz sint alle megede,
<l>die wellent &a;n man
<l><app>
     <rdg wit='M' hand='m1'
                  varSeq=1>alle</rdg>
     <rdg wit='M' hand='m2'
                  varSeq=2
                  cause='nachgetragen'>allen</rdg>
   </app>
   disen sumer g&a;n.

<!-- entity &a; is used here for &acirc; -->
]]>
</eg>

<!-- Des Minnesangs Fr&uuml;hling, ed.  Hugo Moser and        -->
<!-- Helmut Tervooren (Stuttgart:  Hirzel, 1977), I, 20.      -->
<!-- (Anonymous VI).                                          --></p>

<p>Similarly, if a witness is hard to decipher, it may be desired to
indicate responsibility for the claim that a particular reading is
supported by a particular witness.  In line 2212a of
<title>Beowulf</title>, for example, the manuscript is read in different
ways by different scholars; the editor Klaeber prints one text, and
records in the apparatus two different accounts of the manuscript
reading, by Zupitza and Chambers:
<note place="foot">For the sake of legibility in the example, long marks
over vowels are omitted.  The non-standard entities <mentioned>ae</mentioned>,
<mentioned>d</mentioned> and <mentioned>th</mentioned> refer to a-e ligature, eth, and
thorn respectively.  </note>

<eg>
<![ CDATA [
<l>se &eth;e on
<app>
  <rdg wit='Kl'>hea(um) h(&ae;&th;)e</rdg>
  <rdg wit='MS' resp='Z'>hea&d;o hl&ae;we</rdg>
  <rdg wit='MS' resp='Cha'>heaum hope</rdg>
</app></l>
<l>hord beweotode,</l>
]]>
</eg>

<!-- He also records the fact that Holthausen, editions 1-5,  -->
<!-- and Sch&uuml;cking follow Zupitza's reading of the ms.   -->
<!-- So in 'real life' this will require a witDetail          -->
<!-- element, I think.                                        --></p>

<p>The <att>hand</att> and <att>resp</att> attributes are intelligible
only on an element recording a reading from a single witness, and should
not be used if more than one witness is given on the same <gi>rdg</gi>
or <gi>lem</gi> element.  If more than one witness is given for the
reading, they are undefined.  To convey this information when the
witness is one among several, the <gi>witDetail</gi> element should be
used; see section <ptr target="TCaplw">.</p>

<p>Where there is a greater weight of editorial discussion and
interpretation than can conveniently be expressed through the attributes
provided on these tags (e.g. multiple causes for a single reading;
multiple editorial responsibility for an emendation) this information
can be attached to the apparatus in a note, or recorded in the feature
structure notation defined in chapter <ptr target="FS">.  In particular,
such recurring text-critical situations as palaeographic confusion of
particular letters, or homoeoarchy or homoeoteleuton involving specific
character groups, may lend themselves to feature structure treatment.
Information concerning these recurrent situations may be encoded into
database-like fragments within the text which would then be available to
sophisticated computer-assisted analysis.  Further work remains to be
done on such mechanisms, however, and so no examples are given here of
the use of feature structures in text-critical apparatus.</p>

<p>The <gi>note</gi> element may also be used to record the specific
wording of notes in the apparatus of the source edition, as here in
a transcription of Friedrich Klaeber's note on <title>Beowulf</title>
2207a:

<eg>
<![ CDATA [
<l n='2207a'>sy&d;&d;an Beowulfe
  <note place='app' resp='Kl'>Fol. 179a <mentioned>beowulfe</mentioned>.
Folio 179, with the last page (Fol. 198b), is the worst
part of the entire MS.  It has been freshened up by a
later hand, but not always correctly.  Information on
doubtful readings is in the notes of Zupitza and Chambers.
</note>
</l>
<l n='2207b'>brade rice</l>
<!-- ... -->
]]>
</eg>

<!-- Klaeber, app. to 2207.                                   -->

Notes providing details of the reading of one particular witness should
be encoded using the specialized <gi>witDetail</gi> element described in
section <ptr target="TCaplw">.</p>

<p>Encoders should be aware of the distinct fields of use of the
attribute values <att>wit</att>, <att>hand</att>, and <att>resp</att>.
Broadly, <att>wit</att> identifies the physical entity in which the
reading is found (manuscript, clay tablet, papyrus, printed edition);
<att>hand</att> refers to the agent responsible for inscribing that
reading in that physical entity (scribe, author, inscriber, hand 1, hand
2); <att>resp</att> indicates the scholar responsible for asserting the
existence of that reading in that physical entity.  In some cases, the
categories may blur:  a scholar may produce an edition introducing
readings for which he or she is responsible; that edition may itself
become a witness in a later critical apparatus.  Thus, readings
introduced as corrections in the earlier edition will be seen in the
later apparatus as witnessed by the earlier edition.  As observed in the
discussion concerning the discrimination of <att>hand</att> and
<att>resp</att> in transcription of primary sources in section <ptr
target="PHhr">, the division of layers of responsibility through various
scholars for particular aspects of a particular reading may require the
more complex mechanisms for assigning responsibility described in
chapter <ptr target="CE">.</p>

<p>The formal declaration of the <gi>rdg</gi> and <gi>lem</gi> elements
is this:

<!-- should these allow %component ? (msm) -->
<eg id=dtcaplr>
<![ CDATA [
<!-- 19.1.2:  Readings                                        -->
<!ELEMENT lem           - O  (%paraContent)        
                                                 +(%m.fragmentary)
                                                                >
<!ATTLIST lem                %a.global;
                             %a.readings;                       >
<!ELEMENT rdg           - O  (%paraContent)       
                                                 +(%m.fragmentary)
                                                                >
<!ATTLIST rdg                %a.global;
                             %a.readings;                       >
<!-- This fragment is used in sec. 19                         -->
]]>
</eg>
</p></div3>

<div3 id="TCapsu"><head>Indicating Subvariation in Apparatus Entries</head>

<p>The <gi>rdgGrp</gi> element may be used to group readings, either
because they have identical values on one or more attributes, or because
they are seen as forming a self-contained variant sequence, or for some
other reason.  This grouping of readings is entirely optional:  no such
grouping of readings is required.

<list type=gloss>
<label><gi>rdgGrp</gi></label>
<item>within a textual variation,
groups two or more readings 
perceived to have a genetic
relationship or other 
affinity.</item>
</list>
</p>

<p>The <gi>rdgGrp</gi> element is a member of class <ident
type="class">readings</ident> and therefore can carry the
<att>wit</att>, <att>type</att>, <att>cause</att>, <att>varSeg</att>,
<att>hand</att>, and <att>resp</att> attributes described in the
preceding section.  When values for any of these attributes are given
on a <gi>rdgGrp</gi> element, the values given are inherited by the
<gi>rdg</gi> or <gi>lem</gi> elements nested within the reading group,
unless overridden by a new specification on the individual reading
element.</p>

<p>To indicate that both Hg and La vary only orthographically from the
lemma, one might tag both readings <tag>rdg type='orthographic'</tag>,
as shown in the preceding section.  This fact can be expressed more
perspicuously, however, by grouping their readings into a
<gi>rdgGrp</gi>, thus:

<eg>
<![ CDATA [
<app>
    <lem wit='El Ra2'>though</lem>
    <rdgGrp type=orthographic>
         <rdg wit='Hg'>thogh</rdg>
         <rdg wit='La'>thouhe</rdg>
    </rdgGrp>
</app>
]]>
</eg></p>

<p>Similarly, <gi>rdgGrp</gi> may be used to organize the substantive
variants of an apparatus entry.  Editors may need to indicate that each
of a group of witnesses may be taken as all supporting a particular
reading, even though there may be variation concerning the exact form of
that reading in, or the degree of support offered by, those witnesses.
For example:  one may identify three substantive variants on the first
word of Chaucer's <title>Wife of Bath's Prologue</title> in the
manuscripts:  these might be expressed in regularized spelling as
<q>Experience</q>, <q>Experiment</q>, and <q>Eriment</q>.  In fact, the
manuscripts display many different spellings of these words, and a
scholar may wish both to show that the manuscripts have all these
variant spellings and that these variant spellings actually support only
the three regularized spelling forms.  One may term these variant
spellings as <socalled>subvariants</socalled> of the regularized
spelling forms.</p>

<p>This subvariation can be expressed within an <gi>app</gi> element by
gathering the readings into three groups according to the normalized
form of their reading.  All the readings within each group may be
accounted subvariants of the main reading for the group, which may be
signaled by tagging it <tag>lem</tag> or <tag>rdg type='group
base'</tag>.</p>

<p>In this example, the different subvariants on <q>Experience</q>,
<q>Experiment</q>, and <q>Eriment</q> are held within three
<gi>rdgGrp</gi> elements nested within the enclosing <gi>app</gi>
element:

<eg>
<![ CDATA [
<app type='substantive'>
    <rdgGrp type='subvariants'>
        <lem wit='El Hg'>Experience</lem>
        <rdg wit='Ha4'>Experiens</rdg>
    </rdgGrp>
    <rdgGrp type='subvariants'>
        <lem wit='Cp Ld1'>Experiment</lem>
        <rdg wit='La'>Ex&p-underbar;iment</rdg>
    </rdgGrp>
    <rdgGrp type='subvariants'>
        <lem wit='[unattested]'>Eriment</lem>
        <rdg wit='Ra2'>Eryment</rdg>
    </rdgGrp>
</app>
]]>
</eg>

From this, one may deduce that the regularized reading <q>Experience</q>
is supported by all three manuscripts El Hg Ha4, although the spelling
differs in Ha4, and that the regularized reading <q>Eriment</q> is
supported by Ra2, even though the form differs in that manuscript.
Accordingly, an application which recognizes that these apparatus
entries show subvariation may then assign all the witnesses instanced as
attesting the sub-variants on that lemma as actually supporting the
reading of the lemma itself at a higher level of classification.  Thus,
Ha4 here supports the reading <q>Experience</q> found in El and Hg, even
though it is spelt slightly differently in Ha4.</p>

<p>Reading groups may nest recursively, so that variants can be
classified to any desired depth.  Because apparatus entries may also
nest, the <gi>app</gi> element might also be used to group readings in
the same way.  The example above is substantially identical to the
following, which uses <gi>app</gi> instead of <gi>rdgGrp</gi>:

<eg>
<![ CDATA [
<app id=A1 type='substantive' >
    <rdg wit='El Hg Ha4'>
        <app id=A2 type='orthographic'>
             <lem wit='El Hg'>Experience</lem>
             <rdg wit='Ha4'>Experiens</rdg>
        </app>
    </rdg>
    <rdg wit='Cp Ld1 La'>
        <app id=A3 type='orthographic'>
             <lem wit='Cp Ld1'>Experiment</lem>
             <rdg wit='La'>Ex&p-underbar;iment</rdg>
        </app>
    </rdg>
    <rdg wit='Ra2'>
        <app id=A4 type='orthographic'>
             <lem wit='[unattested]'>Eriment</lem>
             <rdg wit='Ra2'>Eryment</rdg>
        </app>
    </rdg>
</app>
]]>
</eg>

This expresses even more clearly than the previous encoding of this
material that at the highest level of classification (apparatus entry
A1), this variation has three normalized readings, and that the first of
these is supported by manuscripts El, Hg, and Ha4; the second by Cp,
Ld1, and La; and the third by Ra2.  Some encoders may find the use of
nested apparatus entries less intuitive than the use of reading groups,
however, so both methods of classifying the readings of a variation are
allowed.</p>

<p>Reading groups may also be used to bring together variants which form
an apparent developmental sequence, and to make clear that other
readings are not part of that sequence, as in the following example,
which makes clear that the variant sequence <q>experiment</q> to
<q>eriment</q> says nothing about the relative priority of
<q>experiment</q> and <q>experience</q>:

<eg>
<![ CDATA [
<app type='substantive'>
    <rdgGrp type='subvariants'>
        <lem wit='El Hg'>Experience</lem>
        <rdg wit='Ha4'>Experiens</rdg>
    </rdgGrp>
    <rdgGrp type='sequence'>
        <rdgGrp varSeq=1 type='subvariants'>
            <lem wit='Cp Ld1'>Experiment</lem>
            <rdg wit='La'>Ex&p-underbar;iment</rdg>
        </rdgGrp>
        <rdgGrp varSeq=2 cause='loss of abbrev for PER' resp=PR>
            <lem wit='[unattested]'>Eriment</lem>
            <rdg wit='Ra2'>Eryment</rdg>
        </rdgGrp>
    </rdgGrp>
</app>
]]>
</eg></p>

<p>Reading groups are defined formally as follows:

<eg id=dtcapsu>
<![ CDATA [
<!-- 19.1.3:  Reading Groups                                  -->
<!ELEMENT rdgGrp        - O  (((rdgGrp, wit?) | ((lem, wit?)?, 
                             (rdg, wit?)*))+)                   >
<!ATTLIST rdgGrp             %a.global;
                             %a.readings;                       >
<!-- This fragment is used in sec. 19                         -->
]]>
</eg>
</p></div3>

<div3 id="TCaplw"><head>Witness Information</head>

<p>A given reading is associated with the set of witnesses attesting it
by listing the witnesses in the <att>wit</att> attribute on the
<gi>rdg</gi>, <gi>lem</gi>, or <gi>rdgGrp</gi> element.  Special
mechanisms, described in the following sections, are needed to associate
annotation on a reading with one specific witness among several (section
<ptr target="TCapwd">), to transcribe witness information verbatim from a
source edition (section <ptr target="TCscwl">), and to identify the
formal lists of witnesses typically provided in the front matter of
critical editions (section <ptr target="TCapwl">).</p>

<div4 id="TCapwd"><head>Witness Detail Information</head>

<p>When it is desired to give additional information about a particular
witness or witnesses for the reading, the information may be given in a
<gi>witDetail</gi> element, pointing to the identifier for that reading
and signalling in the value of its <att>wit</att> attribute the
witnesses or witnesses to which the additional information relates.

<list type=gloss>
<label><gi>witDetail</gi></label>
<item>gives further information about a particular witness, or

witnesses, to a particular reading.
Attributes include:
<list type=gloss>
<label><att>target</att></label>
<item>indicates the identifier for the reading, or readings, to 
which the witness detail refers.</item>
<label><att>wit</att></label>
<item>indicates the sigil or sigla for the witnesses to which the 
detail refers.</item>
</list>
</item>
</list>
</p>

<p>The <gi>witDetail</gi> element is a specialized form of
<gi>note</gi>, which adds to the attributes of that element the
specialized attribute <att>wit</att>, which indicates which witness in
particular is being described.  Like <gi>note</gi>, <gi>witDetail</gi>
can be included in the text at the point of attachment, or can point to
the reading(s) being annotated with its <att>target</att> attribute.  To
indicate, on the authority of editor PR, that the Ellesmere manuscript
has an ornamental capital in the word <mentioned>Experience</mentioned>, for
example, one might write:

<eg>
<![ CDATA [
<app type='substantive'>
    <rdgGrp type='subvariants'>
        <lem id=W026 wit='El Hg'>Experience</lem>
        <rdg wit='Ha4'>Experiens</rdg>
    </rdgGrp>
    <!-- ... -->
</app>

<!-- elsewhere in the text, perhaps in a separate section
     of notes ... -->
<witDetail target=w026 resp=PR wit='El'>Ornamental capital.</witDetail>
]]>
</eg>

This encoding makes clear that the ornamental capital mentioned is in
the Ellesmere manuscript, and not in Hengwrt or Ha4.</p>

<p>Like <gi>note</gi>, <gi>witDetail</gi> may be used to
record the specific wording of information in the source text, even when
the information itself is captured in some more formal way elsewhere.
The example from the Carmina Burana above (section <ptr
target="TCaplr">), for example, might be extended thus, to record the
wording of the note explaining the variant:

<eg>
<![ CDATA [
<l>Swaz hi g&a;t umbe
<l>daz sint alle megede,
<l>die wellent &a;n man
<l><app>
     <rdg wit='M' hand='m1'>alle</rdg>
     <rdg id='Anon.6.4' wit='M' hand='m2'>allen</rdg>
   </app>
   disen sumer g&a;n.

<!-- ... -->
<witDetail target='Anon.6.4' wit='M'><ref>allen</ref>
   <mentioned>n</mentioned> nachgetragen.</witDetail>
<!-- ... -->
]]>
</eg>

<!-- Des Minnesangs Fr&uuml;hling, ed.  Hugo Moser and        -->
<!-- Helmut Tervooren (Stuttgart:  Hirzel, 1977), I, 20.      -->
<!-- (Anonymous VI).                                          --></p>

<p>Observe that a single witness detail element may be linked to several
different readings (noting, for example, a recurrent phenomena in a
particular manuscript) by having the <att>target</att> attribute point
at all the readings in question.  Similarly, feature structures
containing information about the text in a witness (whether
retroversion, regularization, or other) can also be linked to specific
<gi>lem</gi> and <gi>rdg</gi> instances.  See chapter <ptr
target="FS">.</p>

<p>The <gi>witDetail</gi> element is formally declared thus:

<eg id=dtcapwd>
<![ CDATA [
<!-- 19.1.4.1:  Witness Details                               -->
<!ELEMENT witDetail     - O  (%paraContent)                     >
<!ATTLIST witDetail          %a.global;
          wit                CDATA               #REQUIRED
          target             IDREFS              #REQUIRED
          place              CDATA               'apparatus'
          resp               CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 19                         -->
]]>
</eg>
</p></div4>

<div4 id="TCscwl"><head>Witness Information in the Source</head>
<!-- delete this section?  added 1994-01-23 CMSMcQ -->

<p>In the transcription of printed critical editions, it may be
desirable to retain for future reference the exact form in which the
source edition records the witnesses to a particular reading; this is
particularly important in cases of ambiguity in the information, or
uncertainty as to the correct interpretation.  The <gi>wit</gi>
element may be used to transcribe such lists of witnesses to a
particular reading.

<list type=gloss>
<label><gi>wit</gi></label>
<item>contains a list of one or more sigla of witnesses attesting 
a
given reading, in a textual variation.</item>
</list>


The <gi>wit</gi> list may appear following a <gi>rdg</gi>,
<gi>rdgGrp</gi>, or <gi>lem</gi> element in any apparatus entry, and
should be used only to transcribe the witness information in the form
found in the source.
<!-- In particular, it should not be used as a substitute     -->
<!-- for the <att>wit</att> attribute:  where present, the    -->
<!-- information in the <gi>wit</gi> element and the          -->
<!-- <att>wit</att> attribute should agree, unless the        -->
<!-- encoder is uncertain about the interpretation of the     -->
<!-- witness information in the source, or the encoder has    -->
<!-- corrected an error in the source.                        -->
The advantage of holding witness information in the <att>wit</att>
attribute of <gi>lem</gi> or <gi>rdg</gi> is that this may make it more
convenient for an
SGML application to check that every sigil identifier has been declared
elsewhere in the document.  By giving the <att>wit</att> attribute a
declared value of <code type="kw">IDREFS</code>, for example,
one could more easily ensure that readings are
assigned only to witness sigla given as <code type="kw">ID</code> values
for witnesses in a <gi>witList</gi> element
(see section <ptr target="TCapwl">).  Such checking is somewhat more
difficult for
witness sigla held as the content of a <gi>wit</gi> element:  an
application program can check them, but SGML parsers will not.
For this reasons, it is
recommended that encoders always hold witness information in the
<att>wit</att> attribute of <gi>lem</gi> and <gi>rdg</gi>, where
possible.  Thus, as in the examples below, even when a reference to a
witness is exactly reproduced in the <gi>wit</gi> element, the
corresponding sigil for that witness can be written into the wit
attribute of the matching <gi>rdg</gi> or <gi>lem</gi>.  However, in
cases where it is uncertain how the witness reference contained in the
<gi>wit</gi> element should be interpreted, the <att>wit</att>
attribute on the
matching <gi>rdg</gi> or <gi>lem</gi> may be left empty.

<eg>
<![ CDATA [
<lg type=stanza>
<l id=Diet1.1>Sl&a-;fest du, vriedel ziere?
<l id=Diet1.2>wan wecket uns leider schiere;
<l id=Diet1.3>ein vogell&i-;n s&o-; wol get&a-;n
<l id=Diet1.3>daz ist der linden an daz zw&i-; geg&a-;n.
</lg>

<!-- ... -->
<app type='secondary' loc=Diet.1.1>
    <rdg wit='K Ba'>sl&a-;fst</rdg> <wit>K(Ba)</wit>
    </app>
<app type='secondary' loc=Diet.1.2>
    <rdg wit='K V'>Man</rdg> <wit>K(V)</wit>
    <rdg wit='K Wa'>weckt</rdg> <wit>K (Wackernagel 401)</wit>
    <rdg wit='Ju'>Ich waen ez taget uns schiere</rdg>
       <wit><bibl>Jungbluth, Festschr. Pretzel 1963, 122.</bibl></wit>
    </app>
<!-- ... -->

<!-- (The non-standard entities &a-; &o-; and &i-; are used   -->
<!-- here to indicate vowels with circumflexes.)              -->
<!-- The edition in question has two apparatus:  one of       -->
<!-- manuscript readings, and one of readings from editions   -->
<!-- and the secondary literature; hence the attribute        -->
<!-- value type='secondary'.                                  -->
]]>
</eg>

<!-- MF 39,18, ed. Moser/Tervooren, p. 66.                    -->

Of course, the sigla used for different witnesses need not be the same
in the source and the <att>wit</att> attribute, as shown particularly in
the apparatus for the second line of the poem (Diet.1.2).</p>

<p>The formal declaration for <gi>wit</gi> is as follows:

<eg id=dtcscwl>
<![ CDATA [
<!-- 19.1.4.2:  Source-text Witness Lists in Apparatus        -->
<!ELEMENT wit           - O  (%paraContent;)                    >
<!ATTLIST wit                %a.global;                         >
<!-- This fragment is used in sec. 19                         -->
]]>
</eg>
</p></div4>

<div4 id="TCapwl"><head>The Witness List</head>

<p>In the front matter of the edition, a list of all witnesses may be
given if desired, in the form of a witness list, held within a
<gi>witList</gi> element.  This witness list must contain a series of
<gi>witness</gi> elements.  Each <gi>witness</gi> element may optionally
contain text describing that witness in detail and must have an
attibute holding as its value the sigil (siglum) or identifier for a
particular witness.

<list type=gloss>
<label><gi>witList</gi></label>
<item>contains a list of all the witnesses referred to in

<gi>wit</gi> elements or <att>wit</att> attributes
within 
the critical apparatus.</item>
<label><gi>witness</gi></label>
<item>contains either a description of a single witness referred 
to
within the critical apparatus, or a list of witnesses 
which is to be
referred to by a single sigil.
Attributes include:
<list type=gloss>
<label><att>sigil</att></label>
<item>indicates the sigil for one witness or for one group of 
witnesses to which readings are assigned in a critical 
apparatus.</item>
<label><att>included</att></label>
<item>indicates which other witnesses are included in a witness 
group.</item>
</list>
</item>
</list>
</p>

<p>The minimal information provided by a witness list is thus the set of
sigla for all the witnesses named in the apparatus.  For example, a
simple list of the four Chaucer manuscripts used in the examples of this
chapter could appear thus:

<eg>
<![ CDATA [
<witlist>
    <witness sigil='El'>
    <witness sigil='Hg'>
    <witness sigil='La'>
    <witness sigil='Ra2'>
</witlist>
]]>
</eg></p>

<p>It is common, however, for witness lists to be somewhat
more informative:  each <gi>witness</gi> element may contain a prose
description of the witness, or a bibliographic citation:
<eg>
<![ CDATA [
<witlist>
    <witness sigil='El' >Ellesmere, Huntingdon Library 26.C.9</witness>
    <witness sigil='Hg' >Hengwrt, National Library of Wales, Aberystwyth,
                  Peniarth 392D</witness>
    <witness sigil='La' >British Library Lansdowne 851</witness>
    <witness sigil='Ra2'>Bodleian Library Rawlinson Poetic 149</witness>
</witlist>
]]>
</eg>

In some cases, the witness list contains a whole paragraph of commentary
for each witness:

<eg>
<![ CDATA [
<witList>
<witness sigil='A'>die sog. <soCalled>Kleine (oder alte)
        Heidelberger Liederhandschrift</soCalled>.
        <bibl>Universit&auml;tsbibliothek Heidelberg col. pal.
        germ. 357.  Pergament, 45 Fll. 18,5 &times 13,5 cm.</bibl>
        Wahrscheinlich die &ae;lteste der drei gro&ss;en Hss.
        Sie <q>datiert aus dem 123. Jahrhundert, etwa um 1275.
        Ihre Sprache weist ins Elsa&ss;, evtl. nach Stra&ss;burg.
        Man geht wohl nicht fehl, in ihr eine Sammlung aus dem
        Stadtpatriziat zu sehen</q> (<bibl><author>Blank</author>,
        [vgl. <ref>Lit. z. Hss. Bd. 2, S. 39</ref>] S. 14</bibl>).
        Sie enth&ae;lt 34 namentlich genannte Dichter.  <q>Zu
        den Vorz&ue;gen von A geh&oe;rt, da&ss; sie kaum je
        bewu&ss;t ge&ae;ndert hat, so da&ss; sie f&ue;r manche
        Dichter ... oft den besten Text liefert</q> (so wohl
        mit Recht <bibl><author>v. Kraus</author></bibl>).</witness>
<witness sigil='a'>Bezeichnung <bibl><author>Lachmann</author></bibl>s f&ue;r
        die von einer 2. Hand auf bl. 40-43 geschriebenen
        Strophen der Hs. A.</witness>
<witness sigil='B'>die <soCalled>Weingartner (Stuttgarter)
        Liederhandschrift</soCalled>.  <bibl>W&ue;rttembergische
        Landesbibliothek Stuttgart, HB XIII poetae germanici
        1.  Pergament, 156 Bll.  15 &times 11,5 cm; 25 teils
        ganzseitig, teils halbseitige Miniaturen.</bibl>  Kaum
        vor 1306 in Konstanz geschrieben.  Sie enth&ae;lt Lieder
        von 25 namentlich genannten Dichtern.  (Dazu kommen
        Gedichte von einigen ungenannten bzw. unbekannten
        Dichtern, ein Marienlobpreis und eine Minnelehre.)</witness>
<!-- etc. ... -->
</witList>

<!-- &ae; &oe; &ue; = a, o, u umlaut. ss = esszett            -->
]]>
</eg></p>

<p>It is common, in text-critical work, to refer to frequently occurring
groups of witnesses by means of a single common sigil.  Such sigla may
be documented as pseudo-witnesses in their own right by including, in
the witness list, a <gi>witness</gi> element giving the sigil for the group
and listing the other witnesses included in the group in the value of
the <att>included</att> attribute.  In this example, the group of
manuscripts of the <q>Canterbury Tales</q> which make up <q>Constant
Group c</q> are themselves first allocated sigla in individual
<gi>witness</gi> elements, and then those sigla are given as the
<att>included</att> value of a further <gi>witness</gi> element.  All the
manuscripts of this group may thereafter be referred to as <q>c</q>:

<eg>
<![ CDATA [
<witlist>
    <witness sigil='Cp'>Corpus Christi Oxford MS 198</witness>
    <witness sigil='La'>British Library Lansdowne 851</witness>
    <witness sigil='Sl2'>British Library Sloane MS 1686</witness>
     <witness sigil='c' included='Cp La Sl2'>Constant Group c</witness>
</witlist>
]]>
</eg>

That the reading <q>Experiment</q> occurs in all three manuscripts
can now be indicated simply as follows:

<eg>
<![ CDATA [
<rdg wit='c'>Experiment</rdg>
]]>
</eg>

<!-- What happens if both 'c' and 'La' are given, on two      -->
<!-- different readings?  Needs clarification for next        -->
<!-- revision.  Allow single-ms readings to override a        -->
<!-- group?  What, then, about groups of groups, or about     -->
<!-- overlapping groups?  Perhaps better to say that 'c'      -->
<!-- *always* is the same as 'Cp La Sl2', with no             -->
<!-- exceptions.  (msm)                                       --></p>

<p>Situations commonly arise where there are many more or less
fragmentary witnesses, such that there may be quite distinct groups of
witnesses for different parts of a text or collection of texts.  One may
treat this with distinct <gi>witList</gi> elements for each different
part.  Alternatively, one may have a single <gi>witList</gi> element at
the beginning of the file listing all the witnesses, partial and
complete, for the text, with the attestation of fragmentary witnesses
indicated within the apparatus by use of the <gi>witStart</gi>
and <gi>witEnd</gi> elements described in section <ptr
target="TCapmi">.</p>

<p>If a witness list is provided, it may be unnecessary to give, in each
apparatus entry, an exhaustive list of the witnesses which agree with
the base text.  An application program can --- in principle --- compare
the witnesses given for each variant found with those given in the full
list of witnesses, subtracting from this list all the witnesses not
active at this point (perhaps because of lacuna, or because they contain
a variation on a different, overlapping lemma) and thence calculate all
the manuscripts agreeing with the base text.  In practice, encoders may
find it less error-prone to list all witnesses explicitly in each
apparatus entry.</p>

<p>The formal declaration of <gi>witList</gi> and <gi>witness</gi> is as
follows:

<eg id=dtcaplw>
<![ CDATA [
<!-- 19.1.4.3:  Witness Lists in Front Matter                 -->
<!ELEMENT witList       - O  (witness+)                         >
<!ATTLIST witList            %a.global;                         >
<!ELEMENT witness       - O  (%paraContent)                     >
<!ATTLIST witness            %a.global;
          sigil              CDATA               #REQUIRED
          included           CDATA               ''             >
<!-- This fragment is used in sec. 19                         -->
]]>
</eg>
</p></div4></div3>

<div3 id="TCapmi"><head>Fragmentary Witnesses</head>

<p>If a witness is incomplete (whether a single fragment, a series of
fragments, or a relatively complete text with one or more lacunae), it
is usually desirable to record explicitly where its preserved portions
begin and end.  The following empty tags, which may occur within any
<gi>lem</gi> or <gi>rdg</gi> element, indicate the beginning or end of a
fragmentary witness or of a lacuna within a witness:

<list type=gloss>
<label><gi>witStart</gi></label>
<item>indicates the beginning, or resumption, of the text of a

fragmentary witness.</item>
<label><gi>witEnd</gi></label>
<item>indicates the end, or suspension, of the text of a 
fragmentary
witness.</item>
<label><gi>lacunaStart</gi></label>
<item>indicates the beginning of a lacuna in the text of a mostly
complete textual witness.</item>
<label><gi>lacunaEnd</gi></label>
<item>indicates the end of a lacuna in a mostly complete textual

witness.</item>
</list>


All are members of the model class <ident type="class">fragmentary</ident>.</p>

<p>Suppose a fragment of a manuscript X of the <title>Wife of Bath's
Prologue</title> has a physical lacuna, and the text of the manuscript
begins with <mentioned>auctorite</mentioned>.  In an apparatus this might appear
thus, distinguished from the reading of other manuscripts by the
presence of the <gi>lacunaEnd</gi> element:

<eg>
<![ CDATA [
<app>
    <lem wit='El Hg'>Auctoritee</lem>
    <rdg wit='La Ra2'>auctorite</rdg>
    <rdg wit='X'><lacunaEnd>auctorite</rdg>
</app>
]]>
</eg>

In some cases, the apparatus in the source may commence recording the
readings for a particular witness without its being clear whether the
previous absence of readings for this witness is due to a lacuna, or to
some other reason.  The <gi>witStart</gi> element may be used in this
circumstance:

<eg>
<![ CDATA [
<app>
    <lem wit='El Hg'>Auctoritee</lem>
    <rdg wit='La Ra2'>auctorite</rdg>
    <rdg wit='X'><witStart>auctorite</rdg>
</app>
]]>
</eg></p>

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

<eg id=dtcfw>
<![ CDATA [
<!-- 19.1.5:  Fragmentary witnesses                           -->
<!ELEMENT witStart      - O  EMPTY                              >
<!ATTLIST witStart           %a.global;
                             %a.fragmentary;                    >
<!ELEMENT witEnd        - O  EMPTY                              >
<!ATTLIST witEnd             %a.global;
                             %a.fragmentary;                    >
<!ELEMENT lacunaStart   - O  EMPTY                              >
<!ATTLIST lacunaStart        %a.global;
                             %a.fragmentary;                    >
<!ELEMENT lacunaEnd     - O  EMPTY                              >
<!ATTLIST lacunaEnd          %a.global;
                             %a.fragmentary;                    >
<!-- This fragment is used in sec. 19                         -->
]]>
</eg>
</p></div3></div2>

<div2 id="TCaplk"><head>Linking the Apparatus to the Text</head>

<p>Three different methods may be used to link a critical
apparatus to the text:

<list type="bullets">
<item>the location-referenced method,</item>
<item>the double-end-point-attached method, and</item>
<item>the parallel segmentation method.</item>
</list></p>

<p>Both the location-referenced and the double end-point methods may be
used with either <term>in-line</term> or <term>external</term>
apparatus, the former dispersed within the base text, the latter held in
some separate location, within or outside the document with the base
text.  The parallel segmentation method does not use the concept of a
base text and may only be used for in-line apparatus.</p>

<p>Any document containing <gi>app</gi> elements requires a
<gi>variantEncoding</gi> declaration in the <gi>editorialDecl</gi>
element of its TEI header, thus:

<list type=gloss>
<label><gi>variantEncoding</gi></label>
<item>declares the method used to encode text-critical variants.
Attributes include:
<list type=gloss>
<label><att>method</att></label>
<item>indicates which method is used to encode the apparatus of 
variants.
Legal values are:
<list type=gloss>
<label><term>double-end-point</term></label>
<item>apparatus indicates the precise locations of the beginning 
and ending of each lemma relative to a base text.</item>
<label><term>parallel-segmentation</term></label>
<item>alternate readings of a passage are given in parallel in 
the text; no notion of a base text is necessary.</item>
<label><term>location-referenced</term></label>
<item>apparatus uses line numbers or other canonical reference 
scheme referenced in a base text.</item>
</list></item>
<label><att>location</att></label>
<item>indicates whether the apparatus appears within the running 
text or external to it.
Legal values are:
<list type=gloss>
<label><term>external</term></label>
<item>apparatus appears outside the base text.</item>
<label><term>internal</term></label>
<item>apparatus appears within the running text.</item>
</list></item>
</list>
</item>
</list>
</p>

<p>For examples of this element, see the following sections.  The formal
declaration is given in section <ptr target="HD53">.</p>


<div3 id="TCaplo"><head>The Location-referenced Method</head>

<p>The location-referenced method of encoding apparatus provides a
convenient method for encoding printed apparatus; in this method as in
most printed editions, the apparatus is linked to the base text by
indicating explicitly only the block of text on which there is a variant
(noted usually by a canonical reference scheme, or by line number in the
edition, such as <q>A 137</q> or <q>Page 15 line 1</q>).</p>


<p>If the location-referenced method is used for an apparatus stored
externally to the base text, the TEI header must have the
declaration:

<eg>
<![ CDATA [
 <variantEncoding method='location-referenced' location='external'>
]]>
</eg></p>

<p>In the <gi>body</gi> of the document, the base text (here El) will
appear:

<eg>
<![ CDATA [
 <text>
 <body> ...
 <div n=WBP><head>The Prologe of the Wyves Tale of Bathe</head>
 <l n=1>Experience though noon Auctoritee</l>
 <l>Were in this world ...
 </div>
 </body>
 </text>
]]>
</eg></p>

<p>Elsewhere in the document, or in a separate file, the apparatus will
appear.  On each <gi>app</gi> element, the <att>loc</att> attribute
should be specified to indicate where the variant occurs in the base
text.

<eg>
<![ CDATA [
 <app loc="WBP 1">
    <rdg wit='La'>Experiment</rdg>
    <rdg wit='Ra2'>Eryment</rdg>
 </app>
]]>
</eg></p>

<p>If the same text is encoded using in-line storage, the apparatus is
dispersed through the base text block to which it refers.  In this case,
the location of the variant can be read from the line in which it
occurs.

<eg rend=skel>
<![ CDATA [
<TEI.2>
<TeiHeader>
  <!-- ... -->
  <encodingDesc>
    <!-- ... -->
    <editorialDecl>
      <!-- ... -->
      <variantEncoding method='location-referenced' location='internal'>
      <!-- ... -->
    </editorialDecl>
    <!-- ... -->
  </encodingDesc><!-- ... -->
</TeiHeader>
<text>
<body>
  <!-- ... -->
  <div n=WBP><head>The Prologe ... </head>
     <l n=1>Experience
     <app>
          <rdg wit='La'>Experiment</rdg>
          <rdg wit='Ra2'>Eryment</rdg>
     </app>
     though noon Auctoritee</l>
     <l>Were in this world ...
</body>
</text>
</TEI.2>
]]>
</eg></p>

<p>Since the location is not required to be exact, the apparatus for
a line might also appear at the end of the line:

<eg>
<![ CDATA [
 <l n=1>Experience though noon Auctoritee
 <app>
     <rdg wit='La'> Experiment</rdg>
     <rdg wit='Ra2'> Eryment</rdg>
 </app></l>
 <l>Were in this world ...
]]>
</eg></p>

<p>When the apparatus is linked to the text by means of location
references, as shown here, it is not possible to find automatically the
precise portion of text varied by the readings.  In order to show
explicitly what portion of the base text is replaced by the variant
readings, the <gi>lem</gi> element may be used:

<eg>
<![ CDATA [
 <l n=1>Experience though noon Auctoritee
 <app>
     <lem wit='El' >Experience</lem>
     <rdg wit='La' >Experiment</rdg>
     <rdg wit='Ra2'>Eryment</rdg>
 </app></l>
 <l>Were in this world ...
]]>
</eg>

Often the lemma will have no attributes, being simply the
<socalled>base-text reading</socalled> and requiring no qualification,
but it may optionally carry the normal attributes, as shown here.  Some
text critics prefer to abbreviate or elide the lemma, in order to save
space or trouble; such practice is not forbidden by these Guidelines,
but no recommendations are made for conventions of abbreviating the
lemma, whether abbreviation of each word, or suppression of all but the
first and last word, etc.</p>

<p>Where it is intended that the apparatus be complete enough to allow
the <socalled>reconstruction</socalled> of the witnesses (or at least of
their non-orthographic variations), the location-reference method should
be avoided in favor of one of the other two methods, which allow the
unambiguous reconstruction of the lemma from the encoding.</p></div3>

<div3 id="TCapde"><head>The Double End-Point Attachment Method</head>

<p>In the double end-point attachment method, the beginning and end of
the lemma in the base text are both explicitly indicated.  It thus
differs from the location-referenced method, in which only the larger
span of text containing the lemma is indicated.  Double end-point
attachment permits unambiguous matching of each variant reading against
its lemma.  It or the parallel-segmentation method should be used in all
cases where this is desired, for example where the apparatus is intended
to enable full reconstruction of the text, or of the substantives, of
every witness.</p>

<p>When the double endpoint attachment method is used, the
<att>from</att> and <att>to</att> attributes of the <gi>app</gi> element
are used to indicate the beginning and ending points of the reading in
the base text:  their values are SGML identifiers which occur at the
locations in question.  If no other markup is present there, the
beginning and ending points should be marked using the <gi>anchor</gi>
element defined in chapter <ptr target="SA">.  In cases where it is not
possible to insert anchors within the base text (e.g. where the text is
on a read-only medium) the beginning and end of the lemma may be
indicated by using the <socalled>indirect pointing</socalled> mechanisms
discussed in chapter <ptr target="SA">.  Explicit anchors are more likely
to be reliable, and are therefore to be preferred.</p>

<p>The double end-point attachment method may be used with in-line or
external apparatus.  In the latter case, the base text (here El) will
appear with <gi>anchor</gi> elements inserted at every place where a
variant begins or ends (unless some element with an SGML identifier
already begins or ends at that point):

<eg rend=skel>
<![ CDATA [
<TEI.2>
<teiHeader>
    <!-- ... -->
    <variantEncoding method='double-end-point' location='external'>
    <!-- ... -->
</TeiHeader>
<text>
<body>
 <!-- ... -->
 <div n=WBP><head>The Prologe ... </head>
 <l n=1 id='WBP.1'>Experience <anchor id=a2> though noon
        Auctoritee</l>
 <l>Were in this world ...
  <!-- ... -->
</text>
</TEI.2>
]]>
</eg>

The apparatus will be separately encoded:

<eg>
<![ CDATA [
<app from=wbp.1 to=a2>
    <rdg wit='La'>Experiment</rdg>
    <rdg wit='Ra2'>Eryment</rdg>
</app>
]]>
</eg>

No <gi>anchor</gi> element is needed at the beginning of the line, since
the <att>from</att> attribute can use the SGML identifier for the
line as a whole; the lemma is assumed to run from the beginning of the
element indicated by the <att>from</att> attribute, to the end of that
indicated by the <att>to</att> attribute.  If no value is
given for <att>to</att>, the lemma runs from the beginning to the end of
the element indicated by the <att>from</att> attribute.</p>

<p>When the apparatus is encoded in-line, it is dispersed through the
base text.  Only the beginning of the lemma need be marked with an
<gi>anchor</gi>, since the <gi>app</gi> is inserted at the end of the
lemma, and itself therefore marks the end of the lemma.

<eg rend=skel>
<![ CDATA [
<TEI.2>
<teiHeader>
    <!-- ... -->
    <variantEncoding method='double-end-point' location='internal'>
    <!-- ... -->
</TEI.Header>
<text>
<body>
<!-- ... -->
<div><head>The Prologe ...</head>
<l n=1 id=WBP.1>Experience
     <app from=WBP.1>
          <rdg wit='La'>Experiment</rdg>
          <rdg wit='Ra2'>Eryment</rdg>
     </app>
though noon Auctoritee
<l>Were in this world ...
<!-- ... -->
</body>
</TEI.2>
]]>
</eg></p>

<p>The lemma need not be repeated within the <gi>app</gi> element in
this method, as it may be extracted reliably from the base text.  If an
exhaustive list of witnesses is available, it will also not be necessary
to specify just which manuscripts agree with the base-text to enable
reconstruction of witnesses.  An application will be able to determine
the manuscripts that witness the base reading, by noting which witnesses
are attested as having a variant reading, and inferring the base-text
reading for all others after adjusting for fragmentary witnesses and for
witnesses carrying overlapping variant readings.</p>

<p>Alternatively, if it is desired to make an explicit record of the
attestation of the base text the <gi>lem</gi> element may be embedded
within <gi>app</gi>, carrying the witnesses to the base.  Thus

<eg>
<![ CDATA [
<app  from=wbp.1 to=a2>
    <lem wit='El Hg'>Experience</lem>
    <rdg wit='La'>Experiment</rdg>
    <rdg wit='Ra2'>Eryment</rdg>
</app>
]]>
</eg></p>

<p>This method is designed to cope with <socalled>overlapping
lemmata</socalled>.  For example,  at line 117 of the Wife of Bath's
Prologue, the manuscripts Hg (Hengwrt), El (Ellesmere) and Ha4 (British
Library Harleian 7334) read:

<list type="simple">
<item>Hg: And of so parfit wys a wight ywroght</item>
<item>El: And for what profit was a wight ywroght</item>
<item>Ha4: And in what wise was a wight ywroght</item>
</list></p>

<p>In this case, one might wish to record <q>in what wise was</q> in Ha4
as a single variant for <q>of so parfit wys</q> in Hg, and <q>was a
wight</q> in El and H4 as a variant on <q>wys a wight</q> in Hg.  This method
can readily cope with such difficult situations, typically found in
large and complex traditions:

<eg>
<![ CDATA [
<text><body>
<l n=117 id='WBP.117' > And
   <anchor id='a117.1'> of so parfit
   <anchor id='a117.2'> wys
   <anchor id='a117.3'> a wight
   <anchor id='a117.4'> ywroght
<!-- ... -->
<app from=a117.1 to=a117.3>
     <lem wit='Hg' >of so parfit wys</lem>
     <rdg wit='Ha4'>in what wise was</rdg>
</app>
<app from=a117.2 to=a117.4>
     <lem wit='Hg'>wys a wight</lem>
     <rdg wit='El Ha4'>was a wight</rdg>
</app>
</l>
</body></text>
]]>
</eg>

The parallel segmentation method, to be discussed next, cannot handle
overlaps among variants, and would require the individual variants to be
split into pieces.</p>

<p>Because creation and interpretation of double end-point attachment
apparatus will be lengthy and difficult it is likely that they will
usually be created and examined by scholars only with mechanical
assistance.</p></div3>

<div3 id="TCapps"><head>The Parallel Segmentation Method</head>

<p>This method differs from the double end-point attachment method in
that all variants at any point of the text are expressed as variants
on one another.  In this method, no two variations can overlap,
although they may nest.  Thus, the concepts of a base text and of a
lemma become unnecessary:  the texts compared are divided into
matching segments all synchronized with one another.  This permits
direct comparison of any span of text in any witness with that in
any other witness.  It is also very easy with this method for an
application to extract the full text of any one witness from the
apparatus.</p>

<p>This method will (by definition) always be satisfactory when there
are just two texts for comparison (assuming they are in the same
language and script).  It will also be useful where editors do not wish
to privilege a text as the <socalled>base</socalled> or when editors
wish to present parallel texts.  It will become less convenient as
traditions become more complex and tension develops between the need to
segment on the largest variation found and the need to express the
finest detail of agreement between witnesses.</p>

<p>In the parallel segmentation method, each segment of text on which
there is variation is marked by an <gi>app</gi> element; each reading is
given in a <gi>rdg</gi> element; if it is desired to single out one
reading as preferred, it may be tagged <gi>lem</gi>:

<eg rend=skel>
<![ CDATA [
<TEI.2><teiHeader>
<!-- ... -->
    <variantEncoding method='parallel-segmentation'
                     location='internal'>
    <!-- ... -->
</teiHeader>
<text>
<body>
<!-- ... -->
    <l n=1>
    <app><lem wit='El Hg'>Experience</lem>
         <rdg wit='La'>Experiment</rdg>
         <rdg wit='Ra2'>Eryment</rdg>
    </app>
    though noon Auctoritee</l>
    <l>Were in this world ...
]]>
</eg></p>

<p>This method cannot be used with external apparatus:  it must be used
in-line.  Note that apparatus encoded with this method may be translated
into the double end-point attachment method and back without loss of
information.  Where double-end-point-attachment encodings have no
overlapping lemmata, translation of these to the parallel segmentation
encoding and back will also be possible without loss of information.</p>

<p>For economy, the witnesses to the reading most widely attested need
not be stated.  Since all manuscripts must be represented in all
apparatus entries, it will be possible for an application to read a
<gi>witList</gi> declaring all the witnesses to the text and then
calculate which witnesses have not been named.  In the example below,
only La and Ra2 are identified explicitly with a reading; an application
might successfully infer from this that <mentioned>Experience</mentioned>,
whose witnesses are not given, must be attested by El and Hg.  To avoid
confusion, however, witnesses may be omitted only for a single reading.

<eg>
<![ CDATA [
    <l n=1>
    <app><lem>Experience</lem>
         <rdg wit='La'>Experiment</rdg>
         <rdg wit='Ra2'>Eryment</rdg>
    </app>
    though noon Auctoritee</l>
    <l>Were in this world ...
]]>
</eg></p>

<p>Alternatively, the witnesses for every reading may be stated, as in
the first example.</p>

<p>As noted, apparatus entries may nest in this method:  if an imaginary
fifth manuscript of the text read <q>Auctoritee, though none
experience</q>, the variation on the individual words of the line would
nest within that for the line as a whole:

<eg>
<![ CDATA [
<l n=1>
<app>
  <rdg wit=Chi3>Auctoritee, though none experience</rdg>
  <rdg>
    <app><rdg wit='El Hg'>Experience</rdg>
         <rdg wit='La'>Experiment</rdg>
         <rdg wit='Ra2'>Eryment</rdg>
    </app>
    <app><rdg wit='El Ra2'>though</rdg>
         <rdg wit='Hg'>thogh</rdg>
         <rdg wit='La'>thouh</rdg>
    </app>
    <app><rdg wit='El Hg'>noon Auctorite</rdg>
         <rdg wit='La Ra2'>none auctorite</rdg>
    </app>
  </rdg>
  </app>
</l>
]]>
</eg></p>

<p>Parallel segmentation cannot, however, deal very gracefully with
variants which overlap without nesting:  such variants must be broken up
into pieces in order to keep all witnesses synchronized.

<!-- cut following at PR's suggestion (the imaginary example is -->
<!-- no longer there) -->

<!-- The imaginary example at the end of the previous section -->
<!-- might be tagged thus using this method: -->

<!-- <eg> -->
<!-- <![ CDATA [ -->
<!-- <l n=3 id=WBP.3>To -->
<!--     <app> -->
<!--         <rdg>speke</> -->
<!--         <rdg wit=Chi1>sigh</> -->
<!--     </app> -->
<!--     of -->
<!--     <app> -->
<!--         <rdg>wo</> -->
<!--         <rdg wit=Chi1>wailing</> -->
<!--         <rdg wit=Chi2>blisse</> -->
<!--     </app> -->
<!--     that -->
<!--     <app> -->
<!--         <rdg>is</> -->
<!--         <rdg wit=Chi2>wanes</> -->
<!--     </app> -->
<!--     in mariage; -->
<!-- </l> -->
<!-- ]]> -->
<!-- </eg> --></p></div3></div2>

<div2 id="TCtr"><head>Using Apparatus Elements in Transcriptions</head>

<p>It is often desirable to record different transcriptions of the one
stretch of text.  These variant transcriptions may be grouped within a
single <gi>app</gi> element.  An application may then construct
different <q>views</q> of the transcription by extraction of the
appropriate variant readings from the apparatus elements embedded in the
transcription.</p>

<p>For example, alternative expansions can be recorded in several
different <gi>expan</gi> elements, all grouped within an <gi>app</gi>
element.  Consider, for example, the three different transcriptions
given below of line 105 of the Hengwrt manuscript of Chaucer's
<title>The Wife of Bath's Prologue</title>.  The last word of the line
<q>Virginite is grete perfection</q> is written <q>perfectio</q>
followed by two minims over which a bar has been drawn, which has been
read in different ways by different scholars.  The first
transcription, by Elizabeth Solopova, represents the two minims with
bar above by reference to an entity <ident type="ent">i-i</ident>.  This
transcription notes this as a mark of abbreviation but gives no
expansion for it.  A second transcriber, F. J. Furnivall, regards the
bar as an abbreviation of <mentioned>u</mentioned>, reading the two minims as
an <mentioned>n</mentioned>.  A third transcriber, P. G. Ruggiers, regards the
bar as an abbreviation of <mentioned>n</mentioned>, reading the minims as
<mentioned>u</mentioned>.  This information may be held within an <gi>app</gi>
structure, as follows:

<eg>
<![ CDATA [
Virginite is grete
<app>
   <rdg resp=ES >perfectio<abbr>&i-i;</abbr></rdg>
   <rdg resp=FJF>perfectio<expan>u</expan>n</rdg>
   <rdg resp=PGR>perfectiou<expan>n</expan></rdg>
</app>
]]>
</eg>

This example illustrates the adaptation of the <gi>rdg</gi> element for
use within the transcription of a particular witness.  The
<att>wit</att> attribute, which may be compulsory in recording variant
readings of many witnesses within a critical apparatus, is redundant
when recording variant readings relating to a single witness.  However,
it may be desirable to specify the editorial responsibility for a
particular reading within a transcription.  For all three readings, the
<att>resp</att> attribute on <gi>rdg</gi> assigns this responsibility.
Using this system, it will be straightforward for an application to
extract from the one file the three different transcriptions done by
these scholars.  To do this, the application need look only at the
<att>resp</att> attribute on each <gi>rdg</gi> element.</p>

<p>Observe too that in this example the <att>resp</att> attribute is
attached to the outer <gi>rdg</gi> element and is not repeated for the
inner <gi>expan</gi> elements.  There is no need for repetition of the
<att>resp</att> attribute values, as the <gi>expan</gi> elements
contained within each <gi>rdg</gi> element will inherit the value of the
<att>resp</att> from the outer <gi>rdg</gi> element.  Thus, the
processor will know that the responsibility for the expansion
<q>perfectio<tag>expan</tag>u<tag>/</tag>n</q> lies with <q>FJF</q>, as
<q>FJF</q> was responsible for the reading containing this expansion.
This simplifies the processing of the information, as the application
has only to look at the attribute values for each reading in turn and
not for those for elements nested within.</p>

<p>Editorial notes may also be attached to <gi>app</gi> structures
within transcriptions.  Here, editorial preference for Ruggiers'
expansion and an explanation of that preference is given:

<eg>
<![ CDATA [
Virginite is grete
<app>
   <rdg resp=ES>perfecti<abbr>o&i-i;</abbr></rdg>
   <rdg id=F105 resp=FJF>perfectio<expan>u</expan>n</rdg>
   <rdg id=R105 resp=PGR>perfectiou<expan>n</expan></rdg>
</app>

<!-- ... note element appearing elsewhere in the document ... -->

<note target="R105 F105">Furnivall's expansion implies
that the bar is an abbreviation for 'u'.  There are no
certain instances of this mark as an abbreviation for 'u'
in these MSS and it is widely used as an abbreviation
for 'n'.  Ruggiers' expansion is to be accepted.</note>
]]>
</eg></p>

<p>In most cases, elements used to indicate features of a primary
textual source may be represented within an <gi>app</gi> structure
simply by nesting them within its readings, just as the <gi>abbr</gi>
and <gi>expan</gi> elements are nested within the <gi>rdg</gi> elements
in the example just given.  However, in cases where the tagged feature
extends across a span of text which might itself contain variant
readings which it is desired to represent by <gi>app</gi> structures,
some adaptation of the tagging may be necessary.  For example, a span of
text may be marked in the transcription of the primary source as a
single deletion but it may be desirable to represent just a few words
from this source as individual deletions within the context of a
critical apparatus drawing together readings from this and several other
witnesses.  In this case, the tagging of the span of words as one
deletion may need to be decomposed into a series of one-word deletions
for encoding within the apparatus.  If it is important to record
the fact that all were deleted by the same act, the markup may use
the <gi>join</gi> element or the <att>next</att> and <att>prev</att>
attributes defined by chapter <ptr target="SA">.
</p></div2></div1>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
-->
             <!-- 19 Text Criticism ... -->
