12 校本

Contents

Scholarly editions of texts, especially texts of great antiquity orimportance, often record some or all of the known variations amongdifferent witnesses to the text. Witnesses to a text mayinclude 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 inhighly structured form in a critical apparatus of variants. Thischapter defines a module for use in encoding such anapparatus of variants, which may be used in conjunction with any of themodules defined in these Guidelines. It also defines an elementclass which provides extra attributes for some elements of the core tagset when this module is selected.

Information about variant readings (whether or not represented by acritical apparatus in the source text) may be recorded in a series ofapparatus entries, each entry documenting onevariation, or set of readings, in the text. Tags for theapparatus entry and readings, and for the documentation of the witnesseswhose readings are included in the apparatus, are described insection 12.1 校合項目, 解釈, and Witnesses. Special tags for fragmentary witnesses aredescribed in section 12.1.5 断片的な文献. The available methods forembedding the apparatus in the rest of the text, or for linking anexternal apparatus to the base text, are described in section 12.2 校本とテキストの関連付け. Finally, several extra attributes for some tags of thecore tag set, made available when the additional tag set for textcriticism is selected, are documented in section 11.3.1 Core elements for Transcriptional Work.

Many examples given in this chapter refer to the following textsof the opening (usually just line 1) of Chaucer's Wife ofBath's Prologue, as it appears in each of the four differentmanuscripts
  • Ellesmere, Huntingdon Library 26.C.9 (El)
  • Hengwrt, National Library of Wales, Aberystwyth,Peniarth 392D (Hg)
  • (La)
  • Bodleian Library Rawlinson Poetic 149 (Ra2)

12.1 校合項目, 解釈, and Witnesses

This section introduces the fundamental markup methods used to encodetextual variations:

The app element is in one sense a more sophisticated andcomplex version of the choice element introduced in 3.4.1 明らかな間違い as a way of marking points where the encoding of a passagein a single source may be carried out in more than one way. Unlikechoice, however, the app element allows for therepresentation of many different versions of the same passage takenfrom different sources.

12.1.1 校合項目

Individual textual variations are encoded using the appelement, which groups together all the readings constituting thevariation. The identification of discrete textual variations orapparatus entries is not a purely mechanical process; different editorsmay group readings differently. No rules are given here as to how togroup readings into apparatus entries; the tags given here may be usedto group readings in whatever way the editor finds most perspicuous oruseful.

The individual apparatus entry is encoded with the appelement:
  • app (apparatus entry) contains one entry in a critical apparatus, with an optionallemma and at least one reading.
    typeclassifies the variation contained in this element according tosome convenient typology.
    fromidentifies the beginning of the lemma in the base text, ifnecessary.
    toidentifies the endpoint of the lemma in the base text, ifnecessary.
    loc(location) indicates the location of the variation, when thelocation-referenced method of apparatus markup is used.

The attributes loc, from, and to,are used to link the apparatus entry to the base text, if present. Insuch cases, several methodsmay be used for such linkage, each involving a slightly different usagefor these attributes. Linkage between text and apparatus is describedbelow in section 12.2 校本とテキストの関連付け. For the use of theapp element without a base text, see 12.2.3 併記法.

Each app element comprises one or more readings, which inturn are encoded using the rdg or other elements, as describedin the next section. A very simple partial apparatus for the first lineof the Wife of Bath's Prologue might take a formsomething like this:
<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>
Of course, in practice the apparatus will be somewhat more complex.Specifically, it may be desired torecord more obviously that manuscripts El and La agree on thewords ‘noon Auctoritee’, to indicate a preference for onereading, etc. The following sections onreadings, subvariation, and witness information describe some of themore important complications which can arise.

12.1.2 解釈

Individual readings are the crucial elements in any criticalapparatus of variants. The following elements should be used to tagindividual readings within an apparatus entry:
  • lem (lemma) contains the lemma, or base text, of a textual variation.
  • rdg (reading) contains a single reading within a textual variation.
N.B. the term lemma is used here in the text-criticalsense of ‘the reading accepted as that of the original or of thebase text’. This sense differs from that in which the word is usedelsewhere in the Guidelines, for example as in the attributelemma where the intended sense is ‘the root form ofan inflected word’, or ‘the headingof an entry in a reference book, especially a dictionary,’.

In recording readings within an apparatus entry, the rdgelement may always be used; each app must contain at least onerdg.

The lem element may also be used, under some circumstances,to record the base text of the source edition, to mark the readings of abase witness, to indicate the preference of an editor or encoder for aparticular reading, or to make clear, in cases of ambiguity, preciselywhich portion of the main text the variation applies to. Those whoprefer to work without the notion of a base text may prefer not to useit at all. How it is used depends in part on the method chosen forlinking the apparatus to the text; for more information, see section12.2 校本とテキストの関連付け.

解釈 may be encoded individually, or grouped for perspicuityusing the rdgGrp element described in section 12.1.3 校合項目の多様化.

As members of the attribute class att.textCritical,both of these elements inherit the following attributes. Some ofthese attributes are intelligible only if the reading is ascribed to asingle witness; others have no such restriction.
  • att.textCritical defines a set of attributes common to all elements representing variant readings in text critical work.
    wit(witness or witnesses) contains a list of one or more pointers indicating the witnesseswhich attest to a given reading.
    typeclassifies the reading according to some useful typology.
    causeclassifies the cause for the variant reading, according toany appropriate typology of possible origins.
    varSeq(variant sequence) provides a number indicating the position of this reading in asequence, when there is reason to presume a sequence to the variantson any one lemma.
    handsignifies the hand responsible for a particular reading in thewitness.
    resp(responsible party) identifies the editor responsible for asserting a particular reading in the witness.

The wit attribute identifies the witnesses which have thereading in question. It is required if the apparatus gathers togetherreadings from different witnesses, but may be omitted in an apparatusrecording the readings of only one witness, e.g. substitutions,divergent opinions on what is in the witness or on how to expandabbreviations, etc. Even in such a one-witness apparatus, however,the wit attribute may still be useful when it is desired torecord the occurrence of a particular reading in some other witness.For other methods of identifying the witnesses to a reading, seesection 12.1.4 実現形.

The type attribute allows the encoder to classify readingsin any convenient way, for example as substantive variants of the lemma:
<app>
 <lem wit="#El #Hg">Experience</lem>
 <rdg wit="#Latype="substantive">Experiment</rdg>
 <rdg wit="#Ra2type="substantive">Eryment</rdg>
</app>
or as orthographic variants:
<app>
 <lem wit="#El #Ra2">though</lem>
 <rdg wit="#Hgtype="orthographic">thogh</rdg>
 <rdg wit="#Latype="orthographic">thouh</rdg>
</app>
The varSeq and cause attributes may be used toconvey information on the sequence and cause of variation. In thefollowing apparatus fragment, the reading Eryment istagged as sequential to (derived from) the readingExperiment, and the causeis given as loss of the abbreviation for per.
<app>
 <rdg wit="#LavarSeq="1">Experiment</rdg>
 <rdg wit="#Ra2cause="abbreviation_lossvarSeq="2">Eryment</rdg>
</app>
If a manuscript is written in several hands, and it is desired toreport which hand wrote a particular reading, the handattribute should be used. For example, in the Munich manuscriptcontaining the Carmina Burana,the word alle has been changedto allen:
<l>Swaz hi gât umbe</l>
<l>daz sint alle megede,</l>
<l>die wellent ân man</l>
<l>
 <app>
  <rdg wit="#MuvarSeq="1hand="#m1">alle</rdg>
  <rdg
    wit="#Mu"
    cause="nachgetragen"
    varSeq="2"
    hand="#m2">
allen</rdg>
 </app>
disen sumer gân.
</l>
Similarly, if a witness is hard to decipher, it may be desired toindicate responsibility for the claim that a particular reading issupported by a particular witness. In line 2212a ofBeowulf, for example, the manuscript is read in differentways by different scholars; the editor Klaeber prints one text, usingparentheses to indicate his expansion, andrecords in the apparatus two different accounts of the manuscriptreading, by Zupitza and Chambers:38
<l>se ðe on
<app>
  <rdg wit="#Kl">hea(um) h(æþ)e</rdg>
  <rdg wit="#msresp="#Z">heaðo hlæwe</rdg>
  <rdg wit="#msresp="#Cha">heaum hope</rdg>
 </app>
</l>
<l>hord beweotode,</l>

The hand and resp attributes are intelligibleonly on an element recording a reading from a single witness, and shouldnot be used if more than one witness is given on the same rdgor lem element. If more than one witness is given for thereading, they are undefined. To convey this information when thewitness is one among several, the witDetail element should beused; see section 12.1.4 実現形.

Where there is a greater weight of editorial discussion andinterpretation than can conveniently be expressed through the attributesprovided on these tags (e.g. multiple causes for a single reading;multiple editorial responsibility for an emendation) this informationcan be attached to the apparatus in a note, or recorded in the featurestructure notation defined in chapter 18 素性構造. In particular,such recurring text-critical situations as palaeographic confusion ofparticular letters, or homœoarchy or homœoteleuton involving specificcharacter groups, may lend themselves to feature structure treatment.Information concerning these recurrent situations may be encoded intodatabase-like fragments within the text which would then be available tosophisticated computer-assisted analysis. Further work remains to bedone on such mechanisms, however, and so no examples are given here ofthe use of feature structures in text-critical apparatus.

The note element may also be used to record the specificwording of notes in the apparatus of the source edition, as here ina transcription of Friedrich Klaeber's note on Beowulf2207a:
<l n="2207a">syððan Beowulfe
<note resp="#Klplace="app">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>
注釈 providing details of the reading of one particular witness shouldbe encoded using the specialized witDetail element described insection 12.1.4 実現形.

Encoders should be aware of the distinct fields of use of theattribute values wit, hand, and resp.Broadly, wit identifies the physical entity in which thereading is found (manuscript, clay tablet, papyrus, printed edition);hand refers to the agent responsible for inscribing thatreading in that physical entity (scribe, author, inscriber, hand 1, hand2); resp indicates the scholar responsible for asserting theexistence of that reading in that physical entity. In some cases, thecategories may blur: a scholar may produce an edition introducingreadings for which he or she is responsible; that edition may itselfbecome a witness in a later critical apparatus. Thus, readingsintroduced as corrections in the earlier edition will be seen in thelater apparatus as witnessed by the earlier edition. As observed in thediscussion concerning the discrimination of hand andresp in transcription of primary sources in section 11.4.2 Hand, Responsibility, and Certainty Attributes, the division of layers of responsibility through variousscholars for particular aspects of a particular reading may require themore complex mechanisms for assigning responsibility described inchapter 21 確信度・責任.

12.1.3 校合項目の多様化

The rdgGrp element may be used to group readings, eitherbecause they have identical values on one or more attributes, or becausethey are seen as forming a self-contained variant sequence, or for someother reason. This grouping of readings is entirely optional: no suchgrouping of readings is required.
  • rdgGrp (reading group) within a textual variation,groups two or more readings perceived to have a geneticrelationship or other affinity.

The rdgGrp element is a member of class att.textCritical and therefore can carry thewit, type, cause, varSeq,hand, and resp attributes described in thepreceding section. When values for any of these attributes are givenon a rdgGrp element, the values given are inherited by therdg or lem elements nested within the reading group,unless overridden by a new specification on the individual readingelement.

To indicate that both Hg and La vary only orthographically from thelemma, one might tag both readings rdg type='orthographic',as shown in the preceding section. This fact can be expressed moreperspicuously, however, by grouping their readings into ardgGrp, thus:
<app>
 <lem wit="#El #Ra2">though</lem>
 <rdgGrp type="orthographic">
  <rdg wit="#Hg">thogh</rdg>
  <rdg wit="#La">thouhe</rdg>
 </rdgGrp>
</app>

Similarly, rdgGrp may be used to organize the substantivevariants of an apparatus entry. Editors may need to indicate that eachof a group of witnesses may be taken as all supporting a particularreading, even though there may be variation concerning the exact form ofthat reading in, or the degree of support offered by, those witnesses.For example: one may identify three substantive variants on the firstword of Chaucer's Wife of Bath's Prologue in themanuscripts: these might be expressed in regularized spelling asExperience, Experiment, and Eriment. In fact, themanuscripts display many different spellings of these words, and ascholar may wish both to show that the manuscripts have all thesevariant spellings and that these variant spellings actually support onlythe three regularized spelling forms. One may term these variantspellings as ‘subvariants’ of the regularizedspelling forms.

This subvariation can be expressed within an app elementby gathering the readings into three groups according to thenormalized form of their reading. All the readings within each groupmay be accounted subvariants of the main reading for the group, whichmay be indicated by tagging it as a lem element or asrdg type='group base'.

In this example, the different subvariants on Experience,Experiment, and Eriment are held within threerdgGrp elements nested within the enclosing appelement:
<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<g ref="#per"/>iment</rdg>
 </rdgGrp>
 <rdgGrp type="subvariants">
  <lem>Eriment<wit>[unattested]</wit>
  </lem>
  <rdg wit="#Ra2">Eryment</rdg>
 </rdgGrp>
</app>
From this, one may deduce that the regularized reading Experienceis supported by all three manuscripts El Hg Ha4, although the spellingdiffers in Ha4, and that the regularized reading Eriment issupported by Ra2, even though the form differs in that manuscript.Accordingly, an application which recognizes that these apparatusentries show subvariation may then assign all the witnesses instanced asattesting the sub-variants on that lemma as actually supporting thereading of the lemma itself at a higher level of classification. Thus,Ha4 here supports the reading Experience found in El and Hg, eventhough it is spelt slightly differently in Ha4.
Reading groups may nest recursively, so that variants can beclassified to any desired depth. Because apparatus entries may alsonest, the app element might also be used to group readings inthe same way. The example above is substantially identical to thefollowing, which uses app instead of rdgGrp:
<app n="a1type="substantive">
 <rdg wit="#El #Hg #Ha4">
  <app n="a2type="orthographic">
   <lem wit="#El #Hg">Experience</lem>
   <rdg wit="#Ha4">Experiens</rdg>
  </app>
 </rdg>
 <rdg wit="#Cp #Ld1 #La">
  <app n="a3type="orthographic">
   <lem wit="#Cp #Ld1">Experiment</lem>
   <rdg wit="#La">Ex<g ref="#per"/>iment</rdg>
  </app>
 </rdg>
 <rdg wit="#Ra2">
  <app n="a4type="orthographic">
   <lem>Eriment<wit>[unattested]</wit>
   </lem>
   <rdg wit="#Ra2">Eryment</rdg>
  </app>
 </rdg>
</app>
This expresses even more clearly than the previous encoding of thismaterial that at the highest level of classification (apparatus entryA1), this variation has three normalized readings, and that the first ofthese 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 ofnested apparatus entries less intuitive than the use of reading groups,however, so both methods of classifying the readings of a variation areallowed.
Reading groups may also be used to bring together variants which forman apparent developmental sequence, and to make clear that otherreadings are not part of that sequence, as in the following example,which makes clear that the variant sequence experiment toeriment says nothing about the relative priority ofexperiment and experience:
<app type="substantive">
 <rdgGrp type="subvariants">
  <lem wit="#El #Hg">Experience</lem>
  <rdg wit="#Ha4">Experiens</rdg>
 </rdgGrp>
 <rdgGrp type="sequence">
  <rdgGrp varSeq="1type="subvariants">
   <lem wit="#Cp #Ld1">Experiment</lem>
   <rdg wit="#La">Ex<g ref="#per"/>iment</rdg>
  </rdgGrp>
  <rdgGrp varSeq="2cause="abbreviation_lossresp="#PR">
   <lem>Eriment<wit>[unattested]</wit>
   </lem>
   <rdg wit="#Ra2">Eryment</rdg>
  </rdgGrp>
 </rdgGrp>
</app>

12.1.4 実現形

A given reading is associated with the set of witnesses attesting itby listing the witnesses in the wit attribute on therdg, lem, or rdgGrp element. Specialmechanisms, described in the following sections, are needed to associateannotation on a reading with one specific witness among several(section 12.1.4.1 実現形の詳細な情報), to transcribe witness information verbatim from asource edition (section 12.1.4.2 実現形 in the Source), and to identify theformal lists of witnesses typically provided in the front matter ofcritical editions (section 12.1.4.3 実現形リスト).

12.1.4.1 実現形の詳細な情報
When it is desired to give additional information about a particularwitness or witnesses for the reading, the information may be given in awitDetail element, pointing to the identifier for that readingand signalling in the value of its wit attribute thewitness or witnesses to which the additional information relates.
  • witDetail (witness detail) gives further information about a particular witness, orwitnesses, to a particular reading.
    targetindicates the identifier for the reading, or readings, to whichthe witness detail refers.
    wit(witnesses) indicates the sigil or sigla for the witnesses to which thedetail refers.
The witDetail element is a specialized form ofnote, which adds to the attributes of that element thespecialized attribute wit, which indicates which witness inparticular is being described. Like note, witDetailcan be included in the text at the point of attachment, or can point tothe reading(s) being annotated with its target attribute. Toindicate, on the authority of editor PR, that the Ellesmere manuscripthas an ornamental capital in the word Experience, forexample, one might write:
<app type="substantive">
 <rdgGrp type="subvariants">
  <lem xml:id="W026wit="#El #Hg">Experience</lem>
  <rdg wit="#Ha4">Experiens</rdg>
 </rdgGrp>
</app>
<witDetail target="#W026resp="#PRwit="#El">Ornamental capital.</witDetail>
This encoding makes clear that the ornamental capital mentioned is inthe Ellesmere manuscript, and not in Hengwrt or Ha4.
Like note, witDetail may be used torecord the specific wording of information in the source text, even whenthe information itself is captured in some more formal way elsewhere.The example from the Carmina Burana above (section 12.1.2 解釈), for example, might be extended thus, to record thewording of the note explaining the variant:
<l>Swaz hi gât umbe</l>
<l>daz sint alle megede,</l>
<l>die wellent ân man</l>
<l>
 <app>
  <rdg wit="#Muhand="#m1">alle</rdg>
  <rdg xml:id="anon.6.4wit="#Muhand="#m2">allen</rdg>
 </app>
disen sumer gân.
</l>
<witDetail target="#anon.6.4wit="#Mu">
 <ref>allen</ref>
 <mentioned>n</mentioned> nachgetragen.

</witDetail>

Observe that a single witness detail element may be linked to severaldifferent readings (noting, for example, a recurrent phenomena in aparticular manuscript) by having the target attribute pointat all the readings in question. Similarly, feature structurescontaining information about the text in a witness (whetherretroversion, regularization, or other) can also be linked to specificlem and rdg instances. See chapter 18 素性構造.

12.1.4.2 実現形 in the Source
In the transcription of printed critical editions, it may bedesirable to retain for future reference the exact form in which thesource edition records the witnesses to a particular reading; this isparticularly important in cases of ambiguity in the information, oruncertainty as to the correct interpretation. The witelement may be used to transcribe such lists of witnesses to aparticular reading.
  • wit contains a list of one or more sigla of witnesses attesting agiven reading, in a textual variation.
The wit list may appear following a rdg,rdgGrp, or lem element in any apparatus entry, andshould be used only to transcribe the witness information in the formfound in the source.The advantage of holding witness information in the witattribute of lem or rdg is that an application can check that every sigilidentifier has been declared elsewhere in the document. Because thewit attribute has declared datatype of one or more data.pointer values a check can be made thatreadings are assigned only to witness sigla which have been identified(using the xml:id attribute) within a listWitelement (see section 12.1.4.3 実現形リスト). Such checking is moredifficult for witness sigla held as the content of a witelement. For this reason, it is recommended that encoders always holdwitness information in the wit attribute of lemand rdg, where possible. Thus, as in the examples below, evenwhen a reference to a witness is exactly reproduced in thewit element, the corresponding sigil for that witness can be written into the wit attribute of the matching rdg orlem. However, in cases where it is uncertain how the witnessreference contained in the wit element should be interpreted,or where no witness exists, the wit attribute on thematching rdg or lem may be left empty.
<lg type="stanza">
 <l xml:id="Diet1.1">Slăfest du, vriedel ziere?</l>
 <l xml:id="Diet1.2">wan wecket uns leider schiere;</l>
 <l xml:id="Diet1.3">ein vogellīn sŏ wol getăn</l>
 <l xml:id="Diet1.4">daz ist der linden an daz zwī gegăn.</l>
</lg>
<app type="secondaryloc="Diet.1.1">
 <rdg wit="#Kb">slăfst</rdg>
 <wit>K(Ba)</wit>
</app>
<app type="secondaryloc="Diet.1.2">
 <rdg wit="#Kv">Man</rdg>
 <wit>K(V)</wit>
 <rdg wit="#K">weckt</rdg>
 <wit>K (Wackernagel 401)</wit>
 <rdg wit="#Ju">Ich waen ez taget uns schiere</rdg>
 <wit>Jungbluth, Festschr. Pretzel 1963, 122.</wit>
</app>
Of course, the siglum used for a particular witness in the source, as recorded in the wit element, may well differ fromthat used to indicated the same witness in the wit attribute, as shown particularly inthe apparatus for the second line of the poem (Diet.1.2).
12.1.4.3 実現形リスト

A list of all identified witnesses should normally be supplied inthe front matter of the edition, or in the sourceDesc elementof its header. This may be given either as a simple bibliographiclist, using the listBibl element described in 3.11 書誌項目の記述または参照, or as a listWit element, which contains a series of witness elements. Each witnesselement may contain a brief characterisation of the witness, given asone or more prose paragraphs. If more detailed information abouta manuscript witness is available, it should be represented using themsDesc element provided by the msdescriptionmodule; a msDesc may appear within a listBibl.

Whether information about a particular witness is supplied bymeans of a bibl, msDesc, or witnesselement, a unique sigil (siglum) for this source should always besupplied, using the global xml:id attribute. Thisidentifier can then be usedelsewhere to refer to this particular witness.
  • listWit (witness list) lists definitions for all the witnesses referred to by a critical apparatus, optionally grouped hierarchically.
  • witness contains either a description of a single witness referred towithin the critical apparatus, or a list of witnesses which is to bereferred to by a single sigil.
  • msDesc (manuscript description) contains a description of a single identifiablemanuscript.
  • bibl (bibliographic citation) contains a loosely-structured bibliographic citation of whichthe sub-components may or may not be explicitly tagged.
  • listBibl (citation list) contains a list of bibliographic citations of any kind.
The minimal information provided by a witness list is thus the set ofsigla for all the witnesses named in the apparatus. For example, thewitnesses referenced by the examples of thischapter might simply be listed thus:
<listWit>
 <witness xml:id="Chi3"/>
 <witness xml:id="Ha4"/>
 <witness xml:id="Ju"/>
 <witness xml:id="K"/>
 <witness xml:id="Kl"/>
 <witness xml:id="Ld1"/>
 <witness xml:id="Mu"/>
 <witness xml:id="Kb"/>
 <witness xml:id="Kv"/>
 <witness xml:id="Wa"/>
 <witness xml:id="X"/>
</listWit>
It is more helpful, however, for witness lists to be somewhatmore informative: each witness element should contain atleast a brief prosedescription of the witness, perhaps including a bibliographiccitation, as in the following examples:
<listWit>
 <witness xml:id="El">Ellesmere, Huntingdon Library 26.C.9</witness>
 <witness xml:id="Hg">Hengwrt, National Library of Wales,
   Aberystwyth, Peniarth 392D</witness>
<!-- <witness xml:id="La">British Library Lansdowne 851 </witness>-->
 <witness xml:id="Ra2">Bodleian Library Rawlinson Poetic 149
   (see further <ptr target="#MSRP149"/>)</witness>
</listWit>
As the last example shows, the witness description here may complementthe short characterisation provided with a reference to a fulldescription of the manuscript supplied elsewhere, typically as thecontent of a msDesc or bibl element. Alternatively, it may contains a whole paragraph ofcommentary for each witness :
<listWit>
 <witness xml:id="A">die sog. <soCalled>Kleine (oder alte)
     Heidelberger Liederhandschrift</soCalled>.
 <bibl>Universitätsbibliothek Heidelberg col. pal.
     germ. 357. Pergament, 45 Fll. 18,5 × 13,5 cm.</bibl>
   Wahrscheinlich die älteste der drei großen Hss. Sie
 <quote>datiert aus dem 123. Jahrhundert, etwa um 1275. Ihre Sprache
     weist ins Elsaß, evtl. nach Straßburg. Man geht wohl nicht
     fehl, in ihr eine Sammlung aus dem Stadtpatriziat zu sehen</quote>
   (<bibl>
   <author>Blank</author>, [vgl. <ref>Lit. z. Hss. Bd. 2,
       S. 39</ref>] S. 14</bibl>). Sie enthält 34 namentlich
   genannte Dichter. <quote>Zu den Vorzügen von A gehört, daß
     sie kaum je bewußt geändert hat, so daß sie für
     manche Dichter ... oft den besten Text liefert</quote> (so wohl mit
   Recht <bibl>
   <author>v. Kraus</author>
  </bibl>).</witness>
 <witness xml:id="a">Bezeichnung <bibl>
   <author>Lachmann</author>
  </bibl>s für die von einer 2. Hand auf bl. 40–43
   geschriebenen Strophen der Hs. A.</witness>
 <witness xml:id="B">die <soCalled>Weingartner (Stuttgarter)
     Liederhandschrift</soCalled>. <bibl>Württembergische
     Landesbibliothek Stuttgart, HB XIII poetae germanici 1.
     Pergament, 156 Bll. 15 × 11,5 cm; 25 teils ganzseitig,
     teils halbseitige Miniaturen.</bibl> Kaum vor 1306 in Konstanz
   geschrieben. Sie enthält Lieder von 25 namentlich genannten
   Dichtern. (Dazu kommen Gedichte von einigen ungenannten
   bzw. unbekannten Dichtern, ein Marienlobpreis und eine
   Minnelehre.)</witness>
</listWit>
It would however generally be preferable to represent such detailedinformation using an appropriately structured msDesc element,as discussed in chapter 10 Manuscript Description. Note also that if thewitnesses being recorded are not manuscripts but printed works, itmay be preferable to document them using the standard bibl orbiblStruct elements described in 3.11 書誌項目の記述または参照, as inthis example:
<listBibl>
 <bibl xml:id="bcn_1482">T.Kempis, De la imitació de Jesuchrist e del
   menyspreu del món (trad. Miquel Peres); Barcelona, 1482, Pere
   Posa. Editio princeps.</bibl>
 <bibl xml:id="val_1491">T.Kempis, Del menyspreu del món (trad. Miquel
   Peres); València, 1491.</bibl>
 <bibl xml:id="bcn_1518">T.Kempis, Libre del menysprey del món e de la
   imitació de nostre senyor Déu Jesucrist, (trad. Miquel Peres);
   Barcelona, 1518, Carles Amorós. </bibl>
</listBibl>
In text-critical work it is customary to refer to frequently occurringgroups of witnesses by means of a single common sigil. Such sigla maybe documented as pseudo-witnesses in their own right by including anested witness list within the witness list, which uses the sigil for the group as itsidentifier, and supplies a fuller name for the group in its optional childhead element, before listing the other witnesses contained by the group. For example, the Constance Group C of mss comprising witnesses Cp, La,and S12, might be represented as follows:
<listWit xml:id="Con">
 <head>Constant Group C</head>
 <witness xml:id="Cp">Corpus Christi Oxford MS 198</witness>
 <witness xml:id="La">British Library Lansdowne 851</witness>
 <witness xml:id="Sl2">British Library Sloane MS 1686</witness>
</listWit>
That the reading Experiment occurs in all three manuscriptscan now be indicated simply as follows:
<rdg wit="#Con">Experiment</rdg>
Note that a single witness cannot appear more than once in a witness list,and therefore cannot be assigned to more than one group of witnesses.

Situations commonly arise where there are many more or lessfragmentary witnesses, such that there may be quite distinct groups ofwitnesses for different parts of a text or collection of texts. Onemay treat this with distinct listWit elements for eachdifferent part. Alternatively, one may have a single listWitelement at the beginning of the file or in its header listing all thewitnesses, partial and complete, for the text, with the attestation offragmentary witnesses indicated within the apparatus by use of thewitStart and witEnd elements described in section12.1.5 断片的な文献.

If a witness list is provided, it may be unnecessary to give, in eachapparatus entry, an exhaustive list of the witnesses which agree withthe base text. An application program can — in principle — comparethe witnesses given for each variant found with those given in the fulllist of witnesses, subtracting from this list all the witnesses notactive at this point (perhaps because of lacuna, or because they containa variation on a different, overlapping lemma) and thence calculate allthe manuscripts agreeing with the base text. In practice, encoders mayfind it less error-prone to list all witnesses explicitly in eachapparatus entry.

12.1.5 断片的な文献

If a witness is incomplete (whether a single fragment, a series offragments, or a relatively complete text with one or more lacunae), itis usually desirable to record explicitly where its preserved portionsbegin and end. The following empty tags, which may occur within anylem or rdg element, indicate the beginning or end of afragmentary witness or of a lacuna within a witness:
  • witStart/ (fragmented witness start) indicates the beginning, or resumption, of the text of afragmentary witness.
  • witEnd/ (fragmented witness end) indicates the end, or suspension, of the text of a fragmentarywitness.
  • lacunaStart/ indicates the beginning of a lacuna in the text of a mostlycomplete textual witness.
  • lacunaEnd/ indicates the end of a lacuna in a mostly complete textualwitness.
These elements constitute the the class model.rdgPart, members of which are permittedwithin the elements lem and rdg when the moduledefined by this chapter is included in a schema.
Suppose a fragment of a manuscript X of the Wife of Bath'sPrologue has a physical lacuna, and the text of the manuscriptbegins with auctorite. In an apparatus this might appearthus, distinguished from the reading of other manuscripts by thepresence of the lacunaEnd element:
<app>
 <lem wit="#El #Hg">Auctoritee</lem>
 <rdg wit="#La #Ra2">auctorite</rdg>
 <rdg wit="#X">
  <lacunaEnd/>auctorite</rdg>
</app>
In some cases, the apparatus in the source may commence recording thereadings for a particular witness without its being clear whether theprevious absence of readings for this witness is due to a lacuna, or tosome other reason. The witStart element may be used in thiscircumstance:
<app>
 <lem wit="#El #Hg">Auctoritee</lem>
 <rdg wit="#La #Ra2">auctorite</rdg>
 <rdg wit="#X">
  <witStart/>auctorite</rdg>
</app>

12.2 校本とテキストの関連付け

Three different methods may be used to link a criticalapparatus to the text:
  • the location-referenced method,
  • the double-end-point-attached method, and
  • the parallel segmentation method.

Both the location-referenced and the double end-point methods may beused with either in-line or externalapparatus, the former dispersed within the base text, the latter held insome separate location, within or outside the document with the basetext. The parallel segmentation method does not use the concept of abase text and may only be used for in-line apparatus.

Any document containing app elements requires avariantEncoding declaration in the encodingDescelement of its TEI header, thus:
  • variantEncoding/ declares the method used to encode text-critical variants.
    methodindicates which method is used to encode the apparatus ofvariants.
    locationindicates whether the apparatus appears within the running textor external to it.

12.2.1 所在の参照方法

The location-referenced method of encoding apparatus provides aconvenient method for encoding printed apparatus; in this method as inmost printed editions, the apparatus is linked to the base text byindicating explicitly only the block of text on which there is a variant(noted usually by a canonical reference scheme, or by line number in theedition, such as A 137 or Page 15 line 1).

If the location-referenced method is used for an apparatus storedexternally to the base text, the TEI header must have thedeclaration:
<variantEncoding method="location-referencedlocation="external"/>
In the body of the document, the base text (here El) willappear:
<text>
 <body>
  <div n="WBPtype="prologue">
   <head>The Prologe of the Wyves Tale of Bathe</head>
   <l n="1">Experience though noon Auctoritee</l>
   <l>Were in this world ...</l>
  </div>
 </body>
</text>
Elsewhere in the document, or in a separate file, the apparatus willappear. On each app element, the loc attributeshould be specified to indicate where the variant occurs in the basetext.
<app loc="WBP 1">
 <rdg wit="#La">Experiment</rdg>
 <rdg wit="#Ra2">Eryment</rdg>
</app>
If the same text is encoded using in-line storage, the apparatus isdispersed 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 itoccurs.
<variantEncoding method="location-referencedlocation="internal"/>
<!-- ... -->
<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 ...</l>
Since the location is not required to be exact, the apparatus fora line might also appear at the end of the line:
<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 ...</l>
When the apparatus is linked to the text by means of locationreferences, as shown here, it is not possible to find automatically theprecise portion of text varied by the readings. In order to showexplicitly what portion of the base text is replaced by the variantreadings, the lem element may be used:
<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 ...</l>
Often the lemma will have no attributes, being simply the‘base-text reading’ and requiring no qualification,but it may optionally carry the normal attributes, as shown here. Sometext critics prefer to abbreviate or elide the lemma, in order to savespace or trouble; such practice is not forbidden by these Guidelines,but no recommendations are made for conventions of abbreviating thelemma, whether abbreviation of each word, or suppression of all but thefirst and last word, etc.

Where it is intended that the apparatus be complete enough to allowthe reconstruction of the witnesses (or at least oftheir non-orthographic variations), the location-reference method shouldbe avoided in favor of one of the other two methods, which allow theunambiguous reconstruction of the lemma from the encoding.

12.2.2 2点参照法

In the double end-point attachment method, the beginning and end ofthe lemma in the base text are both explicitly indicated. It thusdiffers from the location-referenced method, in which only the largerspan of text containing the lemma is indicated. Double end-pointattachment permits unambiguous matching of each variant reading againstits lemma. It or the parallel-segmentation method should be used in allcases where this is desired, for example where the apparatus is intendedto enable full reconstruction of the text, or of the substantives, ofevery witness.

When the double endpoint attachment method is used, thefrom and to attributes of the app elementare used to indicate the beginning and ending points of the reading inthe base text: their values are identifiers which occur at thelocations in question. If no other markup is present there, thebeginning and ending points should be marked using the anchorelement defined in chapter 16 Linking, Segmentation, and Alignment. In cases where it is notpossible to insert anchors within the base text (e.g. where the text ison a read-only medium) the beginning and end of the lemma may beindicated by using the ‘indirect pointing’ mechanismsdiscussed in chapter 16 Linking, Segmentation, and Alignment. Explicit anchors are more likelyto be reliable, and are therefore to be preferred.

The double end-point attachment method may be used with in-line orexternal apparatus. In the latter case, the base text (here El) willappear with anchor elements inserted at every place where avariant begins or ends (unless some element with an identifieralready begins or ends at that point):
<variantEncoding method="double-end-pointlocation="external"/>
<!-- ... -->
<div n="WBPtype="prologue">
 <head>The Prologe ... </head>
 <l n="1xml:id="WBP.1">Experience<anchor xml:id="WBP-A2"/> though noon Auctoritee</l>
 <l>Were in this world ...</l>
</div>
The apparatus will be separately encoded:
<app from="#WBP.1to="#WBP-A2">
 <rdg wit="#La">Experiment</rdg>
 <rdg wit="#Ra2">Eryment</rdg>
</app>
No anchor element is needed at the beginning of the line, sincethe from attribute can use the identifier for theline as a whole; the lemma is assumed to run from the beginning of theelement indicated by the from attribute, to the end of thatindicated by the to attribute. If no value isgiven for to, the lemma runs from the beginning to the end ofthe element indicated by the from attribute.
When the apparatus is encoded in-line, it is dispersed through thebase text. Only the beginning of the lemma need be marked with ananchor, since the app is inserted at the end of thelemma, and itself therefore marks the end of the lemma.
<variantEncoding method="double-end-pointlocation="internal"/>
<!-- ... -->
<l n="1xml:id="wbp.1">Experience
<app from="#wbp.1">
  <rdg wit="#La">Experiment</rdg>
  <rdg wit="#Ra2">Eryment</rdg>
 </app>
though noon Auctoritee</l>
<l>Were in this world ...</l>

The lemma need not be repeated within the app element inthis method, as it may be extracted reliably from the base text. If anexhaustive list of witnesses is available, it will also not be necessaryto specify just which manuscripts agree with the base-text to enablereconstruction of witnesses. An application will be able to determinethe manuscripts that witness the base reading, by noting which witnessesare attested as having a variant reading, and inferring the base-textreading for all others after adjusting for fragmentary witnesses and forwitnesses carrying overlapping variant readings.

Alternatively, if it is desired to make an explicit record of theattestation of the base text the lem element may be embeddedwithin app, carrying the witnesses to the base. Thus
<app from="#WBP.1to="#WBP-A2">
 <lem wit="#El #Hg">Experience</lem>
 <rdg wit="#La">Experiment</rdg>
 <rdg wit="#Ra2">Eryment</rdg>
</app>
This method is designed to cope with ‘overlappinglemmata’. For example, at line 117 of the Wife of Bath'sPrologue, the manuscripts Hg (Hengwrt), El (Ellesmere), and Ha4 (BritishLibrary Harleian 7334) read:
Hg
And of so parfit wys a wight ywroght
El
And for what profit was a wight ywroght
Ha4
And in what wise was a wight ywroght
In this case, one might wish to record in what wise was in Ha4as a single variant for of so parfit wys in Hg, and was awight in El and H4 as a variant on wys a wight in Hg. This methodcan readily cope with such difficult situations, typically found inlarge and complex traditions:
<l xml:id="WBP.117n="117"> And
<anchor xml:id="WBP-A117.1"/> of so parfit
<anchor xml:id="WBP-A117.2"/> wys
<anchor xml:id="WBP-A117.3"/> a wight
<anchor xml:id="WBP-A117.4"/> ywroght
<app from="#WBP-A117.1to="#WBP-A117.3">
  <lem wit="#Hg">of so parfit wys</lem>
  <rdg wit="#Ha4">in what wise was</rdg>
 </app>
 <app from="#WBP-A117.2to="#WBP-A117.4">
  <lem wit="#Hg">wys a wight</lem>
  <rdg wit="#El #Ha4">was a wight</rdg>
 </app>
</l>
The parallel segmentation method, to be discussed next, cannot handleoverlaps among variants, and would require the individual variants to besplit into pieces.

Because creation and interpretation of double end-point attachmentapparatus will be lengthy and difficult it is likely that they willusually be created and examined by scholars only with mechanicalassistance.

12.2.3 併記法

This method differs from the double end-point attachment method inthat all variants at any point of the text are expressed as variantson one another. In this method, no two variations can overlap,although they may nest. Thus, the concepts of a base text and of alemma become unnecessary: the texts compared are divided intomatching segments all synchronized with one another. This permitsdirect comparison of any span of text in any witness with that inany other witness. It is also very easy with this method for anapplication to extract the full text of any one witness from theapparatus.

This method will (by definition) always be satisfactory when thereare just two texts for comparison (assuming they are in the samelanguage and script). It will also be useful where editors do not wishto privilege a text as the ‘base’ or when editorswish to present parallel texts. It will become less convenient astraditions become more complex and tension develops between the need tosegment on the largest variation found and the need to express thefinest detail of agreement between witnesses.

In the parallel segmentation method, each segment of text on whichthere is variation is marked by an app element; each reading isgiven in a rdg element; if it is desired to single out onereading as preferred, it may be tagged lem:
<variantEncoding method="parallel-segmentationlocation="internal"/>
<!-- ... -->
<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 ...</l>

This method cannot be used with external apparatus: it must be usedin-line. Note that apparatus encoded with this method may be translatedinto the double end-point attachment method and back without loss ofinformation. Where double-end-point-attachment encodings have nooverlapping lemmata, translation of these to the parallel segmentationencoding and back will also be possible without loss of information.

For economy, the witnesses to the reading most widely attested neednot be stated. Since all manuscripts must be represented in allapparatus entries, it will be possible for an application to read alistWit declaring all the witnesses to the text and thencalculate which witnesses have not been named. In the example below,only La and Ra2 are identified explicitly with a reading; an applicationmight successfully infer from this that Experience,whose witnesses are not given, must be attested by El and Hg. To avoidconfusion, however, witnesses may be omitted only for a single reading.
<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 ...</l>

Alternatively, the witnesses for every reading may be stated, as inthe first example.

As noted, apparatus entries may nest in this method: if an imaginaryfifth manuscript of the text read Auctoritee, though noneexperience, the variation on the individual words of the line wouldnest within that for the line as a whole:
<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>

Parallel segmentation cannot, however, deal very gracefully withvariants which overlap without nesting: such variants must be broken upinto pieces in order to keep all witnesses synchronized.

12.3 転記中の校合要素

It is often desirable to record different transcriptions of the onestretch of text. These variant transcriptions may be grouped within asingle app element. An application may then constructdifferent ‘views’ of the transcription by extraction of theappropriate variant readings from the apparatus elements embedded in thetranscription.

For example, alternative expansions can be recorded in severaldifferent expan elements, all grouped within an appelement. Consider, for example, the three different transcriptionsgiven below of line 105 of the Hengwrt manuscript of Chaucer'sThe Wife of Bath's Prologue. The last word of the lineVirginite is grete perfection is written perfectiofollowed by two minims over which a bar has been drawn, which has beenread in different ways by different scholars. The firsttranscription, by Elizabeth Solopova, represents the two minims withbar above as a special composite character using the gelement. Thistranscription notes this as a mark of abbreviation but gives noexpansion for it. A second transcriber, F. J. Furnivall, regards thebar as an abbreviation of u, and therefore reads the two minims asan n. A third transcriber, P. G. Ruggiers, regards thebar as an abbreviation of n, reading the minims asu. This information may be held within an appstructure, as follows:
Virginite is grete
<app>
 <rdg resp="#ES">perfectio<am>
   <g ref="#ii"/>
  </am>
 </rdg>
 <rdg resp="#FJF">perfectio<ex>u</ex>n</rdg>
 <rdg resp="#PGR">perfectiou<ex>n</ex>
 </rdg>
</app>
This example uses special purpose elements am andex used to represent abbreviation marks and editorialexpansion respectively; these elements are provided by the transcr module documented in chapter 11 Representation of Primary Sources, which should be consulted for further discussion ofmethods of representing multiple readings of a source.
Editorial notes may also be attached to app structureswithin transcriptions. Here, editorial preference for Ruggiers'expansion and an explanation of that preference is given:
Virginite is grete
<app>
 <rdg resp="#ES">perfecti<am>
   <g ref="#ii"/>
  </am>
 </rdg>
 <rdg xml:id="f105resp="#FJF">perfectio<ex>u</ex>n</rdg>
 <rdg xml:id="r105resp="#PGR">perfectiou<ex>n</ex>
 </rdg>
</app>
<!-- ... <note> 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>

In most cases, elements used to indicate features of a primarytextual source may be represented within an app structuresimply by nesting them within its readings, just as the abbrand expan elements are nested within the rdg elementsin the example just given. However, in cases where the tagged featureextends across a span of text which might itself contain variantreadings which it is desired to represent by app structures,some adaptation of the tagging may be necessary. For example, a span oftext may be marked in the transcription of the primary source as asingle deletion but it may be desirable to represent just a few wordsfrom this source as individual deletions within the context of acritical apparatus drawing together readings from this and several otherwitnesses. In this case, the tagging of the span of words as onedeletion may need to be decomposed into a series of one-word deletionsfor encoding within the apparatus. If it is important to recordthe fact that all were deleted by the same act, the markup may usethe join element or the next and prevattributes defined by chapter 16 Linking, Segmentation, and Alignment.

12.4 Module for 校本

The module described in this chapter makes available the followingcomponents:The selection and combination of modules to form a TEI schema is described in1.2 TEIスキーマの定義.

Contents « 11 Representation of Primary Sources » 13 Names, Dates, People, and Places

注釈
38.
For the sake oflegibility in the example, long marksover vowels are omitted.


Copyright TEIコンソーシアム 2007 Licensed under the GPL. Copying and redistribution is permitted and encouraged.
Version 1.0.