TEIガイドラインP5

11.3.1 Core elements for Transcriptional WorkTEI: Core elements for Transcriptional Work¶

The following sections describe how the core elements just named maybe used in the transcription of primary source materials.

11.3.2 Abbreviation and ExpansionTEI: Abbreviation and Expansion¶

The writing of manuscripts by hand lends itself to the use ofabbreviation to shorten scribal labour. Commonly occurring letters,groups of letters, words, or even whole phrases, may be represented bysignificant marks. This phenomenon of manuscript abbreviation is sowidespread and so various that no taxonomy of it is here attempted.Instead, methods are shown which allow abbreviations to be encoded usingthe core elements mentioned above.

A manuscript abbreviation may be viewed in two ways. One maytranscribe it as a particular sequence of letters or marks upon thepage: thus, a ‘p with a bar through the descender’, a‘superscript hook’, a ‘macron’. One may also interpret theabbreviation in terms of the letter or letters it is seen as standingfor: thus, ‘per’, ‘re’, ‘n’. Both of these views aresupported by these Guidelines.

In many cases the glyph found in the manuscript source also existsin the Unicode character set: for example the common Latin brevigraph⁊, standing for et and often known asthe ‘Tironian et’ can be directly represented inany XML document as the Unicode character with code pointU+204A (see further Character References and vi.i Language identification). In cases where it does not, these Guidelinesrecommend use of the g element provided by the gaiji module described in chapter 5 Representation of Non-standard Characters and Glyphs. This module allows the encoder great flexibility bothin processing and in documenting non-standard characters or glyphs,including the ability to provide detailed documentation and images forthem.

As implied in the preceding discussion, making decisions aboutwhich of these various methods of representing abbreviation to usewill form an important part of an encoder's practice. As a rule, theabbr and am elements should be preferred where it is wished tosignify that the content of the element is an abbreviation, withoutnecessarily indicating what the abbreviation may stand for. Theex and expan elements should be used where it is wished to signify thatthe content of the element is not present in the source but has beensupplied by the transcriber, without necessarily indicating theabbreviation used in the original. The decision as to which course ofaction is appropriate may vary from abbreviation to abbreviation;there is no requirement that the one system be used throughout atranscription, although doing so will generally simplifyprocessing. The choice is likely to be a matter of editorial policy.If the highest priority is to transcribe the text literatim, whileindicating the presence of abbreviations, the choice will be to useabbr or am throughout. If the highest priority is to present areading transcription, while indicating that some letters or words arenot actually present in the original, the choice will be to useex or expanthroughout.

If more than one expansion for the same abbreviation is to berecorded, multiple notes may be supplied. It may also be appropriateto use the markup for critical apparatus; an example is given insection 12.3 転記中の校合要素.

11.3.3 Correction and ConjectureTEI: Correction and Conjecture¶

Note that the corr element is used to provide a correctedform which is not present in the source; in the case of acorrection made in the source itself, whether scribal, authorial, orby some other hand, the add, del,and subst elements described in 11.3.4 Additions and Deletions should beused.

As with expan and abbr, thechoice as to whether to record simply that there is an apparent error,or simply that a correction has been applied, or to record bothpossible readings within a choice element isleft to the encoder. The decision is likely to be a matter of editorial policy,which might be applied consistently throughout or decided case by case.If the highest priority is to present an uncorrected transcription whilenoting perceived errors in the original, the choice will typicallybe to use only sic throughout. If the highest priority is topresent a reading transcription, while indicating that perceived errorsin the original have been corrected, the choice will be to useonly corr throughout.

Further information may be attached to instances of these elements bythe note element and resp and certattributes. Instances of these elements may also be classifiedaccording to any convenient typology using the typeattribute.

For a given project, it may well be desirable to limit the possiblevalues for the type or subtype attributes automatically. This is easilydone but requires customization of the TEI system using techniquesdescribed in 23.2 Personalization and Customization, in particular 23.2.1.4 Modification of Attribute and AttributeValue リスト, which should be consulted for further informationon this topic.

Like the resp attribute, the cert attributemay be used with both corr and rdg elements. Whenused on the rdg element, these attributes indicate confidencein and responsibility for identifying the reading within the sourcesspecified; when used on the corr element they indicateconfidence in and responsibility for the use of the reading to correctthe base text. If no other source is indicated (either by thesource attribute, or by the wit attribute of aparent rdg), the reading supplied within a corr hasbeen provided by the person indicated by the respattribute.

If it is desired to express aspects of certainty and responsibilityfor some other aspect of the use of these elements, then themechanisms discussed in chapter 21 確信度・責任 may be founduseful. See also 11.4.2 Hand, Responsibility, and Certainty Attributes for further discussion of theissues of certainty and responsibility in the context oftranscription.

11.3.4 Additions and DeletionsTEI: Additions and Deletions¶

If deletions are classified systematically, the typeattribute may be useful to indicate the classification; when they areclassified by the manner in which they were effected, or by theirappearance, however, this will lead to a certain arbitrariness indeciding whether to use the type or the rendattribute to hold the information. In general, it is recommended thatthe rend attribute be used for description of theappearance or method of deletion, and that the typeattribute be reserved for higher level or more abstractclassifications.

The place attribute is also available to indicate thelocation of an addition. For example, consider the following passagefrom a draft letter by Robert Graves:

At the end of this extract, the writerinserts the word ‘cant,’ above the line, with a stroke toindicate insertion: this might be encoded as follows:

参考文献

The O.E.D. is not a dictionary so much as a corpus of
precedents <del hand="RG">in the</del>: current,
obsolete, <add hand="RG" place="supralinear">cant,</add>
cataphretic and nonce-words are all included.

A little earlier in the same extract, Graves writes ‘for anabridgement’ above the line, and then deletes it. This may beencoded similarly:

参考文献

As for 'significant artist.' You quote the O.E.D <add hand="RG" place="supralinear">
 <del>for an abridgement</del>
</add>in
explanation...

Similarly, in the margin, the word ‘Norton’ has been added and then deleted:

参考文献

You quote the <add hand="RG" place="left">
 <del>Norton</del>
</add>
O.E.D...

The word ‘O.E.D.’ in this first sentence has also clearly beenthe result of some redrafting: it may be that Graves started to write‘Oxford’, and then changed it; it may be that he inserted otherpunctuation marks between the letters before replacing them with thecentre dots used elsewhere to represent this acronym. We do not dealwith these possibilities here, and mention them only to indicate thatany encoding of manuscript material of this complexity will need tomake decisions about what is and is not worth mentioning.

The add and del elements defined in the core modulesuffice only for the description of additions and deletions which fitwithin the structure of the text being transcribed, that is, whicheach deletion or addition is completely contained by the structuralelement (paragraph, line, division) within which it occurs. Where thisis not the case, for example because an individual addition or deletioninvolves severaldistinct structural subdivisions, such as poems or prose items, orotherwisecrosses a structural boundary in the text being encoded, specialtreatment is needed. The addSpan anddelSpan elements are provided by this module for thatpurpose. (For a general discussion of the issue see further 20 Non-hierarchical Structures).

The text deleted must be at least partially legible, in order forthe encoder to be able to transcribe it. If it is not legible at all,the gap element should be used to signal that the text wasnot transcribed, because it could not be; the reasonattribute can give the cause of the omission from the transcription as‘deletion, illegible’. If the deletedtext is partially legible, the unclear element described insection 11.5.1 Damage, Illegibility, and Supplied Text may be used to indicate areas oftext which cannot be read with confidence. See further section 11.3.7 Text Omitted from or Supplied in the Transcription and section 11.5.1 Damage, Illegibility, and Supplied Text.

11.3.5 SubstitutionsTEI: Substitutions¶

Substitution of one word or phrase for another is perhaps the mostcommon of all phenomena requiring special treatment in transcriptionof primary textual sources. It may be simply one word overwritinganother, or deletion of one word and its replacement by anotherwritten above it by the same hand at the one time; the deletion andreplacement may be done by different hands at different times; theremay be a long chain of substitutions on the one stretch of text, withuncertainty as to the order of substitution and as to which of manypossible readings should be preferred.

As a more complex example, consider the following passage in one ofthe manuscripts of Wilfred Owen's Dulce et decorumest

This passage might be encoded as follows:

参考文献

<l>And towards our distant rest began to trudge,</l>
<l>
 <subst>
  <del>Helping the worst amongst us</del>
  <add>Dragging the
     worst amongt us</add>
 </subst>, who'd no boots
</l>
<l>But limped on, blood-shod. All went lame;
<subst>
  <del status="shortEnd">half-</del>
  <add>all</add>
 </subst> blind;</l>
<l>Drunk with fatigue ; deaf even to the hoots</l>
<l>Of tired, outstripped <del>fif</del> five-nines that dropped behind.</l>

In this representation,

• the false start fif in the last line is simply marked asa deletion;
• the other two authorial corrections are marked assubstitutions, each combining a deletion and an addition.
• the authorial slip (amongt foramongst) is retained without comment.

11.3.6 Cancellation of Deletions and Other MarkingsTEI: Cancellation of Deletions and Other Markings¶

This element bears the same attributes as the other transcriptionalelements. These may be used to supply further information such asthe hand in which the restoration is carried out, the type ofrestoration, and the personrsponsible for identifying the restoration as such, in the same way aselsewhere.

Another feature commonly encountered in manuscripts is the use ofcircles, lines, or arrows to indicate transposition of material fromone point in the text to another. No specific markup for thisphenomenon is proposed at this time. Such cases are most simplyencoded as additions at the point of insertion and deletions at thepoint of encirclement or other marking.

11.3.7 Text Omitted from or Supplied in the TranscriptionTEI: Text Omitted from or Supplied in the Transcription¶

As noted above, the gap element should only be used wheretext has not been transcribed; if partially legible text has beentranscribed, one of the elements damage and unclearshould be used instead. These elements are described in section 11.5.1 Damage, Illegibility, and Supplied Text.

11.4.1 Document HandsTEI: Document Hands¶

For many text-critical purposes it is important to signal theperson responsible (the hand) for the writing of a wholedocument, a stretch of text within a document, or a particular featurewithin the document. A hand, as the name suggests, need notnecessarily be identified with a particular known (or unknown) scribeor author; it may simply indicate a particular combination of writingfeatures recognized within one or more documents. The examples givenabove of the use of the hand attribute with coding ofadditions and deletions illustrate this.

A handNote element, with an identifier given by itsxml:id attribute, may appear in either of two places in theTEI Header, depending on which modules are included in a schema. Whenthe transcr module defined by the presentchapter is used, the element hand注釈 is available, withinthe profileDesc element of the Header, to hold one or morehandNote elements. When the msdescription module defined in chapter 10 Manuscript Description is included, the handDesc element described in10.7.2 Writing, Decoration, and Other Notations also becomes available as part of a structuredmanuscript description. The encoder may choose to placehandNote elements identifying individual hands in eitherlocation without affecting their accessibility since the element isalways addressed by means of its xml:id attribute. ThehandDesc element may be more appropriate when a fullcataloguing of each manuscript is required; the hand注釈element if only a brief characterization of each hand is needed. Itis also possible to use the two elements together if, for example, thehandDesc element contains a single summary describing all thehands discursively, while the hand注釈 element givesspecific details of each. The choice will depend on individualencoders' priorities.

A single hand may employ different writing styles and inks within adocument, or may change character. For example, the writing stylemight shift from ‘anglicana’ to ‘secretary’, or the ink fromblue to brown, or the character of the hand may change. Simplechanges of this kind may be indicated by assigning a new value to theappropriate attribute within the handShift element. It isfor the encoder to decide whether a change in these properties of thewriting style is so marked as to require treatment as a distincthand.

Where such a change is to be identified, the newattribute is used to indicate the hand applicable to the materialfollowing the handShift. This will ordinarily, but notnecessarily, be the order in which the material was originallywritten.

As might be expected, one hand may employ different renditionswithin the one writing style, for example medieval scribes oftenindicate a structural division by emboldening all the words within aline. These should be indicated by use of the rendattribute on an element, in the same manner as underlining,emboldening, font shifts, etc. are represented in transcription of a printed text,rather than by introducing a new handShift element.

11.4.2 Hand, Responsibility, and Certainty AttributesTEI: Hand, Responsibility, and Certainty Attributes¶

The resp attribute, by contrast, indicate the person responsible for deciding to apply the elementcarrying it to this part of the text, and hence has a slightlydifferent interpretation. In the case of theadd element, for example, the resp attribute willindicate the responsibility for identifying that the addition isindeed an addition, and also (if the hand attribute issupplied) to which hand it should be attributed. In this case, Bowers is credited with identifying the hand as that of WilliamJames. In the case of the corr element, the respattribute indicates who is responsible for supplying theintellectual content of the correction reported in the transcription:here, Bowers' correction of ‘One’ to ‘one’. In the case of adeletion, the resp attribute will similarly indicate whobears responsibility for identifying or categorising the deletion itself,while other attributes (hand most obviously) attributeresponsibility for the deletion itself.

As these examples show, the field of application of theresp attributes varies from element to element. In somecases, it applies to the content of the element (corr, ex, and supplied); in others it applies to the value of a particularattribute (sic, abbr, del, etc.). In allcases where both the resp and cert attributes aredefined for a particular element, the two attributes refer to the sameaspect of the markup. The one indicates who is intellectuallyresponsible for some item of information, the other indicates the degreeof confidence in the information. Thus, for acorrection, the resp attribute signifies the personresponsible for supplying the correction, while the certattribute signifies the degree of editorial confidence felt in thatcorrection. For the expansion of an abbreviation, theresp attribute signifies the person responsible for supplyingthe expansion and the cert attribute signifies the degree ofeditorial confidence felt in the expansion.

This close definition of the use of the resp andcert attributes with each element is intended to provide forthe most frequent circumstances in which encoders might wish to makeunambiguous statements regarding the responsibility for and certainty ofaspects of their encoding. The resp and certattributes, as so defined, give a convenient mechanism for this.However, there will be cases where it is desired to state responsibilityfor and certainty concerning other aspects of the encoding. Forexample, one may wish in the case of an apparent addition to state theresponsibility for the use of the add element, rather than theresponsibility for identifying the hand of the addition. It may also bethat one editor may make an electronic transcription of another editor'sprinted transcription of a manuscript text — here, one will wish toassign layers of responsibility, so as to allow the reader to determineexactly what in the final transcription was theresponsibility of each editor. In these complex cases of dividededitorial responsibility for and certainty concerning the content,attributes, and application of a particular element, the more generalmechanisms for representing certainty and responsibility described inchapter 21 確信度・責任 should be used.

The above discussion supposes that in each case an encoder is able tospecify exactly what it is that one wishes to state responsibility forand certainty about. Situations may arise when an encoder wishes tomake a statement concerning certainty or responsibility but is unable orunwilling to specify so precisely the domain of the certainty orresponsibility. In these cases, the note element may be usedwith the type attribute set to ‘cert’ or ‘resp’and the content of the note giving a prose description of the state ofaffairs.