TEI TEIガイドラインP5: 10 Manuscript Description

10 Manuscript Description

Contents

10.1 OverviewTEI: Overview¶

This module defines a special purpose element which can be used toprovide detailed descriptive information about handwritten primarysources. Although originally developed to meet the needs ofcataloguers and scholars working with medieval manuscripts in theEuropean tradition, the scheme presented here is general enough thatit can also be extended to other traditions and materials, and ispotentially useful for any kind of inscribed artefact.

The scheme described here is also intended to accommodate the needs ofmany different classes of encoders. On the one hand, encoders may beengaged in retrospective conversion of existing detaileddescriptions and catalogues into machine tractable form; on the other,they may be engaged in cataloguing ex nihilo, thatis, creating new detailed descriptions for materials never beforecatalogued. Some may be primarily concerned torepresent accurately the description itself, as opposed to the ideasand interpretations the description represents; others may haveentirely opposite priorities. At oneextreme, a project may simply wish to capture an existing catalogue ina form that can be displayed on the web, and which can be searched forliteral strings, or for such features such as titles, authors anddates; at the other, a project may wish to create in highly structuredand encoded form a detailed database of information about the physicalcharacteristics, history, interpretation, etc. of the material, ableto support practitioners of quantitative codicology aswell as librarians.

To cater for this diversity, here as elsewhere, these Guidelinespropose a flexible approach, in which encoders must choose forthemselves the degree of prescription appropriate to their needs, andare provided with a choice of encoding mechanisms to support thosediffering degrees.

10.2 The Manuscript Description ElementTEI: The Manuscript Description Element¶

The msDesc element will normally appear within thesourceDesc element of the header of a TEI conformantdocument, where the document being encoded is a digital representationof some manuscript original, whether as an encoded transcription, as acollection of digital images (as described in 11.1 Digital Facsimiles),or as some combination of the two. However, in cases where thedocument being encoded is essentially a collection of manuscriptdescriptions, the msDesc element may be used in the same wayas the bibliographic elements (bibl biblStruct, andbiblItem) making up the TEI element class model.biblLike. These typically appear within thelistBibl element.

msDesc (manuscript description) contains a description of a single identifiablemanuscript.

The msDesc element has the following components,which provide more detailed information under a number ofheadings. Each of these component elements is further described in theremainder of this chapter.

msIdentifier (manuscript identifier) contains the information required to identifythe manuscript being described.
head (heading) contains any type of heading, for example the title of a section,or the heading of a list, glossary, manuscript description, etc.
msContents (manuscript contents) describes the intellectual content of a manuscript or manuscript part, either as a series of paragraphs or as a series of structured manuscript items.
physDesc (physical description) contains a full physical description of amanuscript or manuscript part, optionally subdivided using morespecialised elements from the model.physDescPart class.
history groups elementsdescribing the full history of a manuscript or manuscript part.
additional groups additional information, combiningbibliographic information about a manuscript, or surrogate copies ofit with curatorial or administrative information.
msPart (manuscript part) contains information about an originallydistinct manuscript or part of a manuscript, now forming part of a composite manuscript.

The first of these components, msIdentifier, is the onlyone which is mandatory; it is described in more detail in 10.4 The Manuscript Identifier below. It is followed optionally by one or morehead elements, each holding a brief heading (see 10.5 The Manuscript Heading), and then either one or more paragraphs, marked upas a series of p elements, or one or more of the specializedelements msContents (10.6 Intellectual Content),physDesc (10.7 Physical Description), history (10.7.4 History), and additional (10.7.5 Additional information).These elements are all optional, but if used they must appear in theorder given here. Finally, in the case of a composite manuscript, afull description may also contain one or more msPart elements(10.7.6 Manuscript Parts).

To demonstrate the use of this module, consider the followingsample manuscript description, chosen more or less at random from theBodleian Library's Summary catalogue ([132])

参考文献

Figure 1. Entry for Bodleian MS. Add. A. 61 in Madan et al. 1895-1953

The simplest way of digitizing this catalogue entry would simply beto key in the text, tagging the relevant parts of it which make upthe mandatory msIdentifier element, as follows:

参考文献

<msDesc>
<msIdentifier>
 <settlement>Oxford</settlement>
 <repository>Bodleian Library</repository>
 <idno>MS. Add. A. 61</idno>
 <altIdentifier type="SC">
 <idno>28843</idno>
 </altIdentifier>
</msIdentifier>
In Latin, on parchment: written in more than one hand of the 13th
 cent. in England: 7¼ x 5⅜ in., i + 55 leaves, in double columns: with
 a few coloured capitals.
'Hic incipit Bruitus Anglie,' the De origine et gestis Regum
 Angliae of Geoffrey of Monmouth (Galfridus Monumetensis: beg. 'Cum
 mecum multa &amp; de multis.'
On fol. 54v very faint is 'Iste liber est fratris guillelmi de
 buria de ... Roberti ordinis fratrum Pred[icatorum],' 14th cent. (?):
 'hanauilla' is written at the foot of the page (15th cent.). Bought
 from the rev. W. D. Macray on March 17, 1863, for £1 10s.
</msDesc>

With a suitable stylesheet, this encoding would be as readable as theoriginal; it would not, however, be very useful for search purposessince only shelfmarks and other identifiers are distinguished. Toimprove on this, one might wrap the paragraphs in the appropriatespecial-purpose first-child-level elements of msDesc and addsome of the phrase-level elements available when the manuscriptdescription module is in use:

参考文献

<msDesc>
<msIdentifier>
 <settlement>Oxford</settlement>
 <repository>Bodleian Library</repository>
 <idno>MS. Add. A. 61</idno>
 <altIdentifier type="SC">
 <idno>28843</idno>
 </altIdentifier>
</msIdentifier>
<msContents>
 
 <quote>Hic incipit Bruitus Anglie,</quote> the
 <title>De origine et gestis Regum Angliae</title>
 of Geoffrey of Monmouth (Galfridus Monumetensis):
 beg. <quote>Cum mecum multa & de multis.</quote>
 In Latin.
</msContents>
<physDesc>
 
 <material>Parchment</material>: written in
 more than one hand: 7¼ x 5⅜ in., i + 55 leaves, in double
 columns: with a few coloured capitals.
</physDesc>
<history>
 Written in
 <origPlace>England</origPlace> in the
 <origDate>13th cent.</origDate> On fol. 54v very faint is
 <quote>Iste liber est fratris guillelmi de buria de ... Roberti
 ordinis fratrum Pred[icatorum],</quote> 14th cent. (?):
 <quote>hanauilla</quote> is written at the foot of the page
 (15th cent.). Bought from the rev. W. D. Macray on March 17, 1863, for
 £1 10s.
</history>
</msDesc>

Note that in this version the text has been slightly reorganized, butno actual rewriting has been necessary. The encoding now allows theuser to search for such features as title, material, and date andplace of origin; it is also possible to distinguish quoted materialfrom descriptive passages and to search within descriptions relatingto a particular topic (for example, history as distinct frommaterial).

This process could be continued further, restructuring the wholeentry so as to take full advantage of many more of the encodingpossibilities provided by the module described in this chapter:

参考文献

<msDesc>
<msIdentifier>
 <settlement>Oxford</settlement>
 <repository>Bodleian Library</repository>
 <idno>MS. Add. A. 61</idno>
 <altIdentifier type="SC">
 <idno>28843</idno>
 </altIdentifier>
</msIdentifier>
<msContents>
 <msItem>
 <author xml:lang="en">Geoffrey of Monmouth</author>
 <author xml:lang="la">Galfridus Monumetensis</author>
 <title type="uniform" xml:lang="la">De origine et
 gestis Regum Angliae</title>
 <rubric xml:lang="la">Hic incipit Bruitus Anglie</rubric>
 <incipit xml:lang="la">Cum mecum multa & de multis</incipit>
 <textLang mainLang="la">Latin</textLang>
 </msItem>
</msContents>
<physDesc>
 <objectDesc form="codex">
 <supportDesc material="perg">
 <support>
 Parchment.
 </support>
 <extent>i + 55 leaves
 <dimensions scope="all" type="leaf" unit="inch">
 <height>7¼</height>
 <width>5⅜</width>
 </dimensions>
 </extent>
 </supportDesc>
 <layoutDesc>
 <layout columns="2">
 In double columns.
 </layout>
 </layoutDesc>
 </objectDesc>
 <handDesc>
 Written in more than one hand.
 </handDesc>
 <decoDesc>
 With a few coloured capitals.
 </decoDesc>
</physDesc>
<history>
 <origin>
 Written in <origPlace>England</origPlace> in the <origDate notAfter="1300" notBefore="1200">13th cent.</origDate>
 
 </origin>
 <provenance>
 On fol. 54v very faint is
 <quote xml:lang="la">Iste liber est fratris guillelmi de buria de <gap/>
 Roberti ordinis fratrum
 Pred<ex>icatorum</ex>
 </quote>, 14th cent. (?):
 <quote>hanauilla</quote> is written at the foot of the page
 (15th cent.).
 </provenance>
 <acquisition>
 Bought from the rev. <name key="MCRAYWD">W. D. Macray</name> on
 <date when="1863-03-17">March 17, 1863</date>, for £1 10s.
 </acquisition>
</history>
</msDesc>

In the remainder of this chapter we discuss all of the encodingfeatures demonstrated above, together with many other relatedmatters.

10.3 Phrase-level ElementsTEI: Phrase-level Elements¶

When the msdescription module is in use, several extra elements are added tothe phrase level class, and thus become available within paragraphsand elsewhere in the document. These elements are listed below inalphabetical order:

catchwords describes the system used to ensurecorrect ordering of the quires making up a codex or incunable,typically by means of annotations at the foot of the page.
dimensions contains a dimensional specification.
heraldry contains a heraldic formulaor phrase, typically found as part of a blazon, coat of arms, etc.
locus defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references.
material contains a word or phrase describing the material of which a manuscript (or part of a manuscript) is composed.
watermark contains a word or phrase describing awatermark or similar device.
origDate (origin date) contains any form of date, used to identify the date of origin for a manuscript or manuscript part.
origPlace (origin place) contains any form of place name, used to identify theplace of origin for a manuscript or manuscript part.
secFol (secundo folio) The word or words taken from a fixed pointin a codex (typically the beginning of thesecond leaf) in orderto provide a unique identifier for it.
signatures contains discussion of the leaf or quire signatures found within a codex.

Within a manuscript description, many otherstandard TEI phrase level elements are available, notably thosedescribed in the Core module (3 コアモジュール). Additional elementsof particular relevance to manuscript description, such as those fornames and dates, may also be made available by including the relevantmodule in one's schema.

» 10.3.2 Material
Home | 目次

10.3.1 OriginationTEI: Origination¶

The following elements may be used to provide information about theorigins of any aspect of a manuscript:

origDate (origin date) contains any form of date, used to identify the date of origin for a manuscript or manuscript part.
origPlace (origin place) contains any form of place name, used to identify theplace of origin for a manuscript or manuscript part.

The origDate and origPlace elements arespecialized forms of the existing date and nameelements respectively, used to indicate specifically the date andplace of origin of a manuscript or manuscript part. Such informationwould normally be encoded within the history element,discussed in section 10.7.4 History. origDate andorigPlace can also be used to identify the place or date oforigin of any aspect of the manuscript, such as its decoration orbinding, when these are not of the same date as the manuscriptitself. Both these elements are members of theatt.editLike class, from which they inherit thefollowing attributes:

att.editLike provides attributes describing the nature of a encoded scholarly intervention or interpretation of any kind.

The origDate element is a member of theatt.datable class, and may thus also carry the followingattributes:

att.datable provides attributes for normalization of elements that contain dates, times, or datable events.

10.3.2 MaterialTEI: Material¶

The material element can be used to tag any specific termused for the material of which a manuscript (or binding, seal, etc.)is composed.

material contains a word or phrase describing the material of which a manuscript (or part of a manuscript) is composed.

The element may appear wherever a term regarded as significant bythe encoder occurs, as in the following example:

<binding>
Brown <material>calfskin</material>, previously with two clasps.
</binding>

10.3.3 Watermarks and StampsTEI: Watermarks and Stamps¶

Two further elements are provided tomark up other decorative features characteristic of manuscript leaves andbindings:

watermark contains a word or phrase describing awatermark or similar device.
stamp contains a word or phrase describing astamp or similar device.

These element may appearwherever a term regarded as significant by the encoder occurs. Thewatermark element is most likely to be of use within thesupport element, as in the following example:

<support>
<material>Rag
paper</material> with <watermark>anchor</watermark>
watermark
</support>

The stamp element will typically appear when text from the sourceis being transcribed, for example within a rubric in the following case:

<rubric>Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV<lb/>
SI NON LICET<lb/>
NOBIS RO<lb/>
manii imperii <stamp>Bodleian stamp</stamp>
<lb/>
</rubric>

It may also appear as part of the detailed description of a binding :

<binding>
Modern calf recasing with original armorial stamp <stamp>Ex
Bibliotheca J. Richard D.M.</stamp>

</binding>

10.3.4 DimensionsTEI: Dimensions¶

The dimensions element can be used to specify the size ofsome aspect of the manuscript, and thus may be thought of as aspecialized form of the existing TEI measure element.

dimensions contains a dimensional specification.
type indicates which aspect of the object is being measured.

The dimensions element will normally occur within theelement describing the particular feature or aspect of a manuscriptwhose dimensions are being given; thus the size of the leaves would bespecified within the support or extent element (partof the physDesc element discussed in 10.7.1 Object Description),while the dimensions of other specific parts of a manuscript, such asaccompanying materials, binding, etc., would be given in other partsof the description, as appropriate.

The following three elements are available within the dimensions element:

height contains a measurement measured along the axis parallel to the spine.
width contains a measurement measured along the axis perpendicular to the spine.
depth specifies a length measured across the spine.

These three elements, as well as dimensions itself, areall members of the att.dimensions class,and thus all carry the following attributes:

att.dimensions provides attributes for describing the size of physical objects.
unit names the unit used for the measurement
scope specifies the applicability of this measurement, where more than one object is being measured.
quantity specifies the length in the units specified

Each of these elements, if present, must be given in the orderspecified. The dimensions element may be repeated as often asnecessary, with appropriate attribute values to indicate the natureand scope of the measurement concerned. For example, in the followingcase the leaf size and ruled space of the leaves of the manuscript arespecified:

This indicates that for most leaves of the manuscript being describedthe ruled space is 90 mm high and 48 mm wide, while the leaves throughout are between 157 and 160 mm in height and 105 mm in width.

10.3.5 References to Locations within a ManuscriptTEI: References to Locations within a Manuscript¶

The locus element is a specialized form of the ref element.

locus defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references.

from	specifies the starting point of the location in a normalized form.
to	specifies the end-point of the location in a normalized form.
scheme	identifies the foliation scheme in terms of which the location is being specified.

The locus element is used to specify the location in themanuscript occupied by the element within which it appears. If, forexample, it is used as the first component of a msItem or msItemStructelement, or of any of the more specific elements appearing within one(see further section 10.6 Intellectual Content below) then it is understoodto specify the location of that item within the manuscript beingdescribed.

A locus element can be used to identify any reference toone or more folios within a manuscript, wherever such a reference isappropriate. Locations are conventionally specified as a sequence offolio or page numbers, but may also be a discontinuous list, or acombination of the two. This specification should be given as thecontent of the locus element, using the conventionsappropriate to the individual scholar or holding institution, as inthe following example:

<msItem n="1">
<locus>ff. 1-24r</locus>
<title>Apocalypsis beati Ioannis Apostoli</title>
</msItem>

A normalized form of the location can also besupplied, using special purpose attributes on the locuselement, as in the following revision of the above example:

<msItem n="1">
<locus from="1r" to="24r">ff. 1-24r</locus>
<title>Apocalypsis beati Ioannis Apostoli</title>
</msItem>

When the trans module described inchapter 11 Representation of Primary Sources is included in a schema, an additionalattribute facs is available, which may be used to associate alocus element with a digitized image, as in the following example:

<decoDesc>
Several of the miniatures in this section have been damaged and
 overpainted at a later date (e.g. the figure of Christ on
<locus
 facs="http://www.example.com/images.fr#F33R">fol. 33r</locus>; the face of the
 Shepherdess on <locus
 facs="http://www.example.com/images.fr#F59V">fol. 59v</locus>,
 etc.).
</decoDesc>

Here, the facs attribute uses a URI reference to point directly to images of therelevant pages, held presumably in an image archive not forming partof the resource containing the manuscript description in question. Inthe case where such images do form part of a single virtual document,along with transcriptions and metadata, the methods described in 11.1 Digital Facsimiles should be used in preference.

Where a manuscript contains more than one foliation, thescheme attribute may be used to distinguish them. Forexample, MS 65 Corpus Christi College, Cambridge contains two flyleaves bearing music. These leaves have modern foliation 135 and136 respectively, but are also marked with an older foliation. Thismay be preserved in an encoding such as the following:

<locus scheme="#original">XCIII</locus>
<locus scheme="#modern">135</locus>

Here the scheme attribute points to afoliation element providing more details about the schemeused, as further discussed in 10.7.1.4 Foliation below.

10.3.6 Names of Persons, Places, and OrganizationsTEI: Names of Persons, Places, and Organizations¶

The standard TEI element name may be used to identifynames of any kind occurring within a description:

name (name, proper noun) contains a proper noun or noun phrase.
type indicates the type of the object which is being named by the phrase.

As further discussed in 3.5.1 参照文字, this element is a member ofthe TEI class att.naming, from which itinherits the following attributes:

att.naming provides attributes common to elements which refer to named persons, places, organizations etc.

key	provides an external means of locating a full definition for the entity being named, such as a database record key or other token.
ref	(reference) provides an explicit means of locating a full definition for the entity being named by means of a URI.

Here are some examples of the use of the name element:

<name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name type="person" ref="#HOC001">Occleve</name>

Note that the name element is defined as providinginformation about a name, not the person, place, or organization to which that name refers. In the last example above, the ref attribute is used toassociate the name with a more detailed description of the personnamed. This is provided by means of the person element, whichbecomes available when the namesdatesmodule described in chapter 13 Names, Dates, People, and Places is included in aschema. An element such as the following might then be used to providedetailed information about the person indicated by the name:

<person xml:id="HOC001">
<persName>
<surname>Hoccleve</surname>
<forename>Thomas</forename>
</persName>
<birth notBefore="1368"/>
<occupation>poet</occupation>

</person>

Note that an instance of the person element must be provided for each distinctref value specified. In the example above, the valueHOC001 must be found as the xml:id attribute ofsome person; the samevalue will be used as the ref attribute of every referenceto Hoccleve in the document (however spelled), but there will only beone person element with this identifier.

Alternatively, the key attribute may be used to supplyan unique identifying code for the person referenced by the nameindependently of both the existence of a person element andthe use of the standard URI reference mechanism. If, for example, aproject maintains as its authority file some non-digital resource, oruses a database which cannot readily beintegrated with other digital resources for this purpose, the uniquecodes used by such ‘offline’ resources may be usedas values for the key attribute. Although such practices clearlyreduce the interchangeability of the resulting encoded texts, they maybe judged more convenient or practical in certain situations.

All the person elements referenced by a particulardocument set should be collected together within a listPersonelement, located in the TEI Header. This functions as a kindof prosopography for all the people referenced by the set ofmanuscripts being described, in much the same way as alistBibl element in the back matter may be used to holdbibliographic information for all the works referenced.

When the namesdates module describedin chapter 13 Names, Dates, People, and Places is included in a schema, similar mechanisms are used to maintain and reference canonicallists of places or organizations, as further discussed in sections13.2.3 地名 and 13.2.2 組織名 respectively.

10.3.7 Catchwords, Signatures, Secundo FolioTEI: Catchwords, Signatures, Secundo Folio¶

The catchwords element is used to describe one method bywhich correct ordering of the quires of a codex is ensured. Typically,this takes the form of a word or phrase written in the lower margin ofthe last leaf verso of a gathering, which provides a preview of thefirst recto leaf of the successive gathering. This may be a simplephrase such as the following:

<catchwords>Quires signed on the last leaf verso in roman numerals.</catchwords>

Alternatively, it may contain more details:

<catchwords>Vertical catchwords in the hand of the scribe placed along
the inner bounding line, reading from top to bottom.</catchwords>

The ‘Signatures’ element is used, in a similarway, to describe a similar system in which quires or leaves aremarked progressively in order to facilitate arrangement duringbinding. For example:

<signatures>At the bottom of the first four leaves of quires 1-14 are
the remains of a series of quire signatures a-o plus roman figures in
a cursive hand of the fourteenth century.</signatures>

The signatures element can be used for either leafsignatures, or a combination of quire and leaf signatures, whether themarking is alphabetic, alphanumeric, or some ad hoc system, as in thefollowing more complex example:

<signatures>Quire and leaf signatures in letters, [b]-v, and roman numerals;
those in quires 10 (1) and 17 (s) in red ink and different from others;
every third quire also signed with red crayon in arabic numerals in the
centre lower margin of the first leaf recto: "2" for quire 4 (f. 19),
"3" for quire 7 (f. 43); "4", barely visible, for quire 10 (f. 65), "5",
in a later hand, for quire 13 (f. 89), "6", in a later hand, for quire
16 (f. 113).</signatures>

The secFol element (for ‘secundofolio’) is used to record an identifying phrase (alsocalled dictio probatoria) taken from aspecific known point in a codex (for example the first few words onthe second leaf). Since these words will differ from one copy ofa text to another, the practice originated in the middle ages of usingthem when cataloguing a manuscript in order to distinguish individualcopies of a work in a way which its opening words could not.

<secFol>(ando-)ssene in una villa</secFol>

10.3.8 HeraldryTEI: Heraldry¶

Descriptions of heraldic arms, supporters, devices, and mottos mayappear at various points in the description of a manuscript, usually in the context of ownershipinformation, binding descriptions, or detailed accounts ofillustrations. A full description may also contain a detailed account of theheraldic components of a manuscript independently considered. Frequently, however, heraldic descriptions willbe cited as short phrases within other parts of the record. The phraselevel element heraldry is provided to allow such phrases tobe marked for further analysis, as in the followingexamples:

Ownership stamp (xvii cent.) on i recto with the arms <heraldry>A bull
passant within a bordure bezanty, in chief a crescent for difference</heraldry>
[Cole], crest, and the legend <quote>Cole Deum</quote>.

A c. 8r fregio su due lati, <heraldry>stemma e imprese medicee</heraldry>
racchiudono l'inizio dell'epistolario di Paolino.

10.4 The Manuscript IdentifierTEI: The Manuscript Identifier¶

The msIdentifier element is intended to provide anunambiguous means of uniquely identifying a particularmanuscript. This may be done in a structured way, by providing information about the holding institution and the call number,shelfmark, or other identifier used to indicate its location withinthat institution. Alternatively, or in addition, a manuscript may beidentified simply by a commonly used name.

msIdentifier (manuscript identifier) contains the information required to identifythe manuscript being described.

A manuscript's actual physical location may occasionally bedifferent from its place of ownership; at Cambridge University, forexample, manuscripts owned by various colleges are kept in the centralUniversity Library. Normally, it is the ownership of the manuscript which shouldbe specified in the manuscript identifier, while additional or moreprecise information on the physical location of the manuscript can begiven within the adminInfo element, discussed in section 10.7.5.1 Administrative information below.

The following elements are available within msIdentifierto identify the holding institution:

country contains the name of a geo-political unit, such as a nation,country, colony, or commonwealth, larger than or administratively superiorto a region and smaller than a bloc.
region contains the name of an administrative unit such as a state,province, or county, larger than a settlement, but smaller than a country.
settlement contains the name of a settlement such as a city, town, orvillage identified as a single geo-political oradministrative unit.
institution contains the name of an organization such as a university or library, with which a manuscript is identified, generally its holding institution.
repository contains the name of a repository within which manuscripts are stored, possibly forming part of an institution.

These elements are all structurally equivalent to the standard TEIname element with an appropriate value for itstype attribute; however the use of this ‘syntacticsugar’ enables the model for msIdentifier to beconstrained rather more tightly than would otherwise bepossible. Specifically, only one of each of the elements listed abovemay appear within the msIdentifier and they must, if present,appear in the order given.

These elements are all also members of the attribute classatt.naming, from which they inherit the followingattribute:

att.naming provides attributes common to elements which refer to named persons, places, organizations etc.

The following elements are used within msIdentifier toprovide different ways of identifying the manuscript within its holding institution:

collection contains the name of a collection ofmanuscripts, not necessarily located within a single repository.
idno (identifying number) supplies any standard or non-standard number used to identify abibliographic item.
altIdentifier (alternative identifier) contains an alternative or former structured identifier used fora manuscript, such as a former catalogue number.
msName (alternative name) contains any form of unstructured alternativename used for a manuscript, such as an ‘ocellusnominum’, or nickname.

Major manuscript repositories will usually have a preferredform of citation for manuscript shelfmarks, including rulesabout punctuation, spacing, abbreviation, etc., which should beadhered to. Where such a format also contains information which mightadditionally be supplied as a distinct subcomponent of themsIdentifier, for example a collection name,a decision must be taken as to whether to use the more specificelement, or to include within the idno element. Forexample, the manuscript formally identified as ‘El 26 C 0’ formsa part of the Ellesmere (‘El’) collection. Either of thefollowing encodings is therefore feasible:

<msIdentifier>
<country>USA</country>
<region>California</region>
<settlement>San Marino</settlement>
<repository>Huntington Library</repository>
<collection>El</collection>
<idno>26 C 9</idno>
<msName>The Ellesmere Chaucer</msName>
</msIdentifier>

<msIdentifier>
<country>USA</country>
<region>California</region>
<settlement>San Marino</settlement>
<repository>Huntington Library</repository>
<idno>El 26 C 9</idno>
<msName>The Ellesmere Chaucer</msName>
</msIdentifier>

In the former example, the preferred form of the identifier can beretrieved by prefixing the content of the idno element withthat of the collection element, while in the latter it isgiven explicitly. The advantage of the former is that it it simplifiesaccurate retrieval of all manuscripts from a given collection; thedisadvantage is that encoded abbreviations of this kind may not be asimmediately comprehensible. Care should be taken to avoid redundancy:for example

would clearly be inappropriate. Equally clearly,

<collection>Ellesmere</collection>
<idno>El 26 C 9</idno>

might be considered helpful in some circumstances (if, forexample, some of the items in the Ellsemere collection had shelfmarkswhich did not begin ‘El’)

In cases where the shelfmark contains no information about thecollection, it may be necessary to provide this explicitly, as inthe following example:

<msIdentifier>
<country>USA</country>
<region>New Jersey</region>
<settlement>Princeton</settlement>
<repository>Princeton University Library</repository>
<collection>Scheide Library</collection>
<idno>MS 71</idno>
<msName>Blickling Homiliary</msName>
</msIdentifier>

In these examples, msName has been used to providea common name other than the shelfmark by which a manuscript isknown. Where a manuscript has several such names, more than one of these elements may be used, as in the followingexample:

<msIdentifier>
<country>Danmark</country>
<settlement>København</settlement>
<repository>Det Arnamagnæanske Institut</repository>
<idno>AM 45 fol.</idno>
<msName xml:lang="la">Codex Frisianus</msName>
<msName xml:lang="is">Fríssbók</msName>
</msIdentifier>

Here the globally available xml:lang attribute has beenused to specify the language of the alternative names.

In very rare cases a repository may have only one manuscript (oronly one of any significance), which will have no shelfmark as suchbut will be known by a particular name or names. In suchcircumstances, the idno element may be omitted, and themanuscript identified by the name or names used for it, usingone or more msName elements, as in the following example:

<msIdentifier>
<settlement>Rossano</settlement>
<repository xml:lang="it">Biblioteca arcivescovile</repository>
<msName xml:lang="la">Codex Rossanensis</msName>
<msName xml:lang="la">Codex purpureus</msName>
<msName xml:lang="en">The Rossano Gospels</msName>
</msIdentifier>

Where manuscripts have moved from one institution to another, oreven within the same institution, they may have identifiers additionalto the ones currently used, such as former shelfmarks, which aresometimes retained even after they have been officially superseded. Insuch cases it may be useful to supply an alternative identifier, witha detailed structure similar to that of the msIdentifieritself. The following example shows a manuscript which had shelfmarkII-M-5 in the collection of the Duque de Osuna, but whichnow has the shelfmark MS 10237 in the National Library inMadrid:

<msIdentifier>
<settlement>Madrid</settlement>
<repository>Biblioteca Nacional</repository>
<idno>MS 10237</idno>
<altIdentifier>
 <region>Andalucia</region>
 <settlement>Osuna</settlement>
 <repository>Duque de Osuna</repository>
 <idno>II-M-5</idno>
</altIdentifier>
</msIdentifier>

Normally, such information would be dealt with under history, except incases where a manuscript is likely still to be referred to or known byits former identifier. For example, an institution may have changedits call number system but still wish to retain a record of the earliernumber, perhaps because the manuscript concerned is frequently cited in printunder its previous number:

<msIdentifier>
<settlement>Berkeley</settlement>
<institution>University of California</institution>
<repository>Bancroft Library</repository>
<idno>UCB 16</idno>
<altIdentifier>
<idno>2MS BS1145 I8</idno>
</altIdentifier>
</msIdentifier>

Where (as in this example) no repository is specified for thealtIdentifier, it is assumed to be the same as that of theparent msIdentifier. Where the holding institution has onlyone preferred form of citation but wishes to retain the other forinternal administrative purposes, the secondary could be given withinaltIdentifier with an appropriate value on thetype attribute:

<msIdentifier>
<settlement>Oxford</settlement>
<repository>Bodleian Library</repository>
<idno>MS. Bodley 406</idno>
<altIdentifier type="SC">
<idno>2297</idno>
</altIdentifier>
</msIdentifier>

It might, however, be preferable to include such information withinthe adminInfo element discussed in section 10.7.5.1 Administrative information below.

Cases of such changed or alternative identifiers should be clearlydistinguished from cases of ‘scattered’manuscripts, that is to say manuscripts which although physicallydisjoint are nevertheless generally treated as single units. Onewell-known example is the Old Church Slavonic manuscript known asCodex Suprasliensis, substantial parts of which are tobe found in three separate repositories, in Ljubljana, Warsaw, andSt. Petersburg. This should be represented using three distinctaltIdentifier elements, using an appropriate value on thetype attribute to indicate that these three identifiers are notalternate ways of referring to the same physical object, but threeparts of the same entity.

<msIdentifier>
<msName xml:lang="la">Codex Suprasliensis</msName>
<altIdentifier type="partial">
 <settlement>Ljubljana</settlement>
 <repository>Narodna in univerzitetna knjiznica</repository>
 <idno>MS Kopitar 2</idno>
 <note>Contains ff. 10 to 42 only</note>
</altIdentifier>
<altIdentifier type="partial">
 <settlement>Warszawa</settlement>
 <repository>Biblioteka Narodowa</repository>
 <idno>BO 3.201</idno>
</altIdentifier>
<altIdentifier type="partial">
 <settlement>Sankt-Peterburg</settlement>
 <repository>Rossiiskaia natsional'naia biblioteka</repository>
 <idno>Q.p.I.72</idno>
</altIdentifier>
</msIdentifier>

As mentioned above, the smallest possible description is one thatcontains only the element msIdentifier; good practice in allbut exceptional circumstances requires the presence within it of thethree subelements settlement, repository, andidno, since they provide what is, by common consent, theminimum amount of information necessary to identify a manuscript.

10.5 The Manuscript HeadingTEI: The Manuscript Heading¶

Historically, the briefest possible meaningful description of amanuscript consists of no more than a title,e.g. Polychronicon. This will often have beenenough to identify a manuscript in a small collection because theidentity of the author is implicit. Where a title does not imply theauthor, and is thus insufficient to identify the main text of amanuscript, the author should be stated explicitly(e.g. Augustinus, Sermones or Cicero,Letters). Many inventories of manuscripts consist of nomore than an author and title, with some form of copy-specificidentifier, such as a shelfmark or ‘secundo folio’ reference(e.g. Arch. B. 3. 2: Evangelium Matthei cumglossa, 126. Isidori Originum libriocto, Biblia Hieronimi, 2o fo. opusest); information on date and place of writing willsometimes also be included. The standard TEI element headelement can be used to provide a brief description of this kind.

head (heading) contains any type of heading, for example the title of a section,or the heading of a list, glossary, manuscript description, etc.

In this way the cataloguer or scholar can supply in one place aminimum of essential information, such as might be displayed orprinted as the heading of a full description. For example:

<head>Marsilius de Inghen, Abbreviata phisicorum Aristotelis; Italy, 1463.</head>

Any phrase-level elements, such as title, name,date, or the specialized elements origPlace andorigDate, can also be used within a head element,but it should be remembered that the head element is intendedprincipally to contain a heading. Morestructured information concerning the contents, physical form, orhistory of the manuscript should be given within the specializedelements described below, msContents, physDesc,history, etc. However, in simple cases, the pelement may also be used to supply an unstructured collection ofsuch information, as in the example given above (10.2 The Manuscript Description Element.

10.6 Intellectual ContentTEI: Intellectual Content¶

The msContents element is used to describe theintellectual content of a manuscript or manuscript part. It compriseseither a series of informal prose paragraphsor a series of msItem or msItemStructelements, each of which provides a more detailed description of asingle item contained within the manuscript. These may be prefaced, ifdesired, by a summary element, which is especially usefulwhere one wishes to provide an overview of a manuscript's contents anddescribe only some of the items in detail.

msContents (manuscript contents) describes the intellectual content of a manuscript or manuscript part, either as a series of paragraphs or as a series of structured manuscript items.
msItem (manuscript item) describes an individual work or item within the intellectual content of a manuscript or manuscript part.
msItemStruct (structured manuscript item) contains a structured description for an individual work or item within the intellectual content of a manuscript or manuscript part.

In the simplest case, only a brief description may be provided, asin the following examples:

<msContents>
A collection of Lollard sermons
</msContents>
<msContents>
Atlas of the world from Western Europe and Africa to Indochina,
 containing 27 maps and 26 tables
</msContents>
<msContents>
Biblia sacra: Antiguo y Nuevo Testamento, con prefacios, prólogos
 y argumentos de san Jerónimo y de otros. Interpretaciones de los
 nombres hebreos.
</msContents>

This description may of course be expanded to include any of theTEI elements generally available within a p element, such astitle, bibl, or list. More usually,however, each individual work within a manuscript will be given itsown description, using the msItem or msItemStructelement described in the next section, as in the following example:

<msContents>
<msItem n="1">
 <locus>fols. 5r -7v</locus>
 <title>An ABC</title>
 <bibl>
 <title>IMEV</title>
 <biblScope>239</biblScope>
 </bibl>
</msItem>
<msItem n="2">
 <locus>fols. 7v -8v</locus>
 <title xml:lang="fr">Lenvoy de Chaucer a Scogan</title>
 <bibl>
 <title>IMEV</title>
 <biblScope>3747</biblScope>
 </bibl>
</msItem>
<msItem n="3">
 <locus>fol. 8v</locus>
 <title>Truth</title>
 <bibl>
 <title>IMEV</title>
 <biblScope>809</biblScope>
 </bibl>
</msItem>
<msItem n="4">
 <locus>fols. 8v-10v</locus>
 <title>Birds Praise of Love</title>
 <bibl>
 <title>IMEV</title>
 <biblScope>1506</biblScope>
 </bibl>
</msItem>
<msItem n="5">
 <locus>fols. 10v -11v</locus>
 <title xml:lang="la">De amico ad amicam</title>
 <title xml:lang="la">Responcio</title>
 <bibl>
 <title>IMEV</title>
 <biblScope>16 & 19</biblScope>
 </bibl>
</msItem>
<msItem n="6">
 <locus>fols. 14r-126v</locus>
 <title>Troilus and Criseyde</title>
 <note>Bk. 1:71-Bk. 5:1701, with additional losses due to
 mutilation throughout</note>
</msItem>
</msContents>

» 10.6.2 Authors and Titles
Home | 目次

10.6.1 The msItem and msItemStruct ElementsTEI: The msItem and msItemStruct Elements¶

Each discrete item in a manuscript or manuscript part can be described within a distinct msItem or msItemStruct element, and may be classified using the class attribute.

These are the possible component elements of msItem and msItemStruct.

author in a bibliographic reference, contains the name of the author(s),personal or corporate,of a work; the primary statement of responsibility for anybibliographic item.
respStmt (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply.
title contains the full title of a work of any kind.
type classifies the title according to some convenient typology.
rubric contains the text of any rubric or heading attached to a particular manuscript item, that is, a string of words through which amanuscript signals the beginning of a text division, often with an assertion as to its author and title, which is in some way set off from the text itself, usually in red ink, or by use of different size or type of script, or some other such visual device.
incipit contains the incipit of a manuscript item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipts were, in fomer times, frequently used a means of reference to a work, in place of a title.
quote (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text.
explicit contains the explicit of amanuscript item, that is, the closing words of the text proper,exclusive of any rubric or colophon which might follow it.
finalRubric contains the string of words that denotes the end of a text division, often with an assertion as to its author and title, usually set off from the text itself by red ink, by a different size or type of script, or by some other such visual device.
colophon contains the colophonof a manuscript item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript.
decoNote (note on decoration) contains a note describing either adecorative component of a manuscript, or a fairly homogenous class ofsuch components.
listBibl (citation list) contains a list of bibliographic citations of any kind.
bibl (bibliographic citation) contains a loosely-structured bibliographic citation of whichthe sub-components may or may not be explicitly tagged.
filiation contains information concerning the manuscript's filiation, i.e. its relationship to other surviving manuscripts of the same text, its protographs, antigraphs and apographs.
note contains a note or annotation.
type describes the type of note.
textLang (text language) describes the languages and writing systems used by amanuscript (as opposed to its description, which is described in the langUsage element).

In addition, a msItemStruct may contain nestedmsItemStruct elements, just as an msItem may containnested msItem elements.

The main difference between msItem and msItemStruct isthat in the former, the order and number of child elements is notconstrained; any element, in other words, may be given in any order,and repeated as often as is judged necessary. In the latter, however, thesubelements, if used, must be given in the order specified above andonly some of theymay be repeated; specifically, rubric,finalRubric. incipit, textLang andexplicit can appear only once.

While neithermsItem nor msItemStruct may contain untagged runningtext, both permit an unstructured description to be provided in theform of oneor more paragraphs of text. They differ in this respect also: ifparagraphs are supplied as the content of an msItem, thennone of the other component elements listed above is permitted; in themsItemStruct case, however, paragraphs may appear anywhere inas an alternative to any of the component elements listed above.

As noted above, bothmsItem and msItemStruct elements mayalso nest, where a number of separate items in a manuscript aregrouped under a single title or rubric, as is the case, for example,with a work like The Canterbury Tales.

The elements msContents, msItem,msItemStruct, incipit, and explicit are allmembers of the class att.msExcerpt fromwhich they inherit the defective attribute.

att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof.
defective indicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.

This attribute can be used for example for collectionsof fragments, where each fragment is given as a separatemsItem and the first and last words of each transcribed asdefective incipits and explicits, as in the following example, amanuscript containing four fragments of a single work:

<msContents>
<msItem defective="true">
 <locus from="1r" to="9v">1r-9v</locus>
 <title>Knýtlinga saga</title>
 <msItem n="1.1">
 <locus from="1r:1" to="2v:30">1r:1-2v:30</locus>
 <incipit defective="true">dan<ex>n</ex>a a
 engl<ex>an</ex>di</incipit>
 <explicit defective="true">en meðan <expan>haraldr</expan>
 hein hafði k<ex>onung</ex>r v<am>
 <g
 ref="http://www.examples.com/abbrevs.xml#er"/>
 </am>it
 yf<ex>ir</ex> danmork</explicit>
 </msItem>

</msItem>
</msContents>

The elements ex, am, andexpan used in the above example are further discussed insection 11.3.2 Abbreviation and Expansion; they are available only when the transcr module defined by that chapter isselected. Similarly, the g element used in this example torepresent the abbreviation mark is defined by the gaiji module documented in chapter 5 Representation of Non-standard Characters and Glyphs.

10.6.2 Authors and TitlesTEI: Authors and Titles¶

The title element should be used to supply a regularizedform of the item's title, as distinct from any rubric quoted from themanuscript. If the item concerned has a standardized distinctivetitle, e.g. Roman de la Rose, then this shouldbe the form given as content of the title element, with thevalue of the type attribute given asuniform. If no uniform title exists for an item, or nonehas been yet identified, or if one wishes to provide a generaldesignation of the contents, then a ‘supplied’title can be given, e.g. missal, in which casethe type attribute on the title should be giventhe value supplied.

The author element, if used, should alwayscontain the normalized form of an author's name, irrespective of how(or whether) this form of the name is cited in the manuscript. If itis desired to retain the form of the author's name as given in themanuscript, this may be tagged as a distinct name element,within the text at the point where it occurs.

Note that the key attribute can also be used, as onnames in general, to specify the identifier of a personelement carrying full details of the person concerned (see further10.3.6 Names of Persons, Places, and Organizations).

The respStmt element can be used to supply the name and role of a person other than the author who is responsible for some aspect of the intellectual content of the manuscript:

<author>Diogenes Laertius</author>
<respStmt>
<resp>in the translation of</resp>
<name>Ambrogio Traversari</name>
</respStmt>

The respStmt element can also be used where there is a discrepancy between the author of an item as given in the manuscript and the accepted scholarly view, as in the following example:

<title type="supplied">Sermons on the Epistles and the Gospels</title>
<respStmt>
<resp>here erroneously attributed to</resp>
<name>St. Bonaventura</name>
</respStmt>

Note that such attributions of authorship, both correct and incorrect, are frequently found in the rubric or final rubric (and occasionally also elsewhere in the text), and can therefore be transcribed and included in the description, if desired, using the rubric, finalRubric, or quote elements, as appropriate.

10.6.3 Rubrics, Incipits, Explicits, and Other 引用s from the TextTEI: Rubrics, Incipits, Explicits, and Other 引用s from the Text¶

It is customary in a manuscript description to record the openingand closing words of a text as well as any headings or colophons itmight have, and the specialised elements rubric,incipit, explicit, finalRubric, andcolophon are available within msItem for doing so,along with the more general quote, for recording other bits ofthe text not covered by these elements. Each of these elements has thesame substructure, containing a mixture of phrase-level elements andplain text. A locus element can be included within each, inorder to specify the location of the component, as in the followingexample:

<msContents>
<msItem>
 <locus>f. 1-223</locus>
 <author>Radulphus Flaviacensis</author>
 <title>Expositio super Leviticum </title>
 <incipit>
 <locus>f. 1r</locus>
 Forte Hervei monachi</incipit>
 <explicit>
 <locus>f. 223v</locus>
 Benedictio salis et aquae</explicit>
</msItem>
</msContents>

In the following example, standard TEI elements for the transcription of primary sources have been used to markthe expansion of abbreviations and other features present in the original:

<msItem defective="true">
<locus>ff. 1r-24v</locus>
<title type="uniform">Ágrip af Noregs konunga sǫgum</title>
<incipit defective="true">regi oc h<expan>ann</expan> seti
 ho<gap reason="illegible" extent="7" unit="mm"/>
 <lb/>sc heim se<expan>m</expan> þio</incipit>
<explicit defective="true">h<expan>on</expan> hev<expan>er</expan>
 <expan>oc</expan> þa buit hesta .ij. <lb/>annan viþ fé en
 h<expan>on</expan>o<expan>m</expan> annan til reiþ<expan>ar</expan>
</explicit>
</msItem>

Note here also the use of the defective attribute on incipit and explicit to indicate that the text begins and ends defectively.

The xml:lang attribute for colophon, explicit, incipit, quote, and rubric may always be used to identify the language of the text quoted, if this is different from the default language specified by the mainLang attribute on textLang.

10.6.4 FiliationTEI: Filiation¶

The filiation element can be used to provide information on the relationship between the manuscript and other surviving manuscripts of the same text, either specifically or in a general way, as in the following example:

<msItem>
<locus>118rb</locus>
<incipit>Ecce morior cum nichil horum ... <ref>[Dn 13, 43]</ref>. Verba ista dixit Susanna de illis</incipit>
<explicit>ut bonum comune conservatur.</explicit>
<bibl>Schneyer 3, 436 (Johannes Contractus OFM)</bibl>
<filiation>weitere Überl. Uppsala C 181, 35r.</filiation>
</msItem>

10.6.5 Text ClassificationTEI: Text Classification¶

One or more text classification or text-type codes may bespecified, either for the whole of the msContents element, orfor one or more of its constituent msItem elements, using theclass attribute as specified above:

<msContents>
<msItem n="1" defective="false" class="#law">
 <locus from="1v" to="71v">1v-71v</locus>
 <title type="uniform">Jónsbók</title>
 <incipit>Magnus m<expan>ed</expan> guds miskun Noregs
 k<expan>onungu</expan>r</incipit>
 <explicit>en<expan>n</expan> u<expan>ir</expan>da
 þo t<expan>il</expan> fullra aura</explicit>
</msItem>
</msContents>

The value of the class attributeshould specify the identifier used for the appropriate classificationwithin a taxonomy element, defined in the classDeclelement of the TEI Header (2.3.6 分類法宣言), asshown here:

« 10.6.5 Text Classification
Home | 目次

10.6.6 Languages and Writing SystemsTEI: Languages and Writing Systems¶

The textLang element should be used to provideinformation about the languages used within a manuscript item. It may takethe form of a simple note, as in the following example:

<textLang>Old Church Slavonic, written in Cyrillic script.</textLang>

Where, for validation and indexing purposes, it is thoughtconvenient to add keywords identifying the particular languages used,the mainLang attribute may be used. This attribute takesthe same range of values as the global xml:lang attribute,on which see further vi.i Language identification. In the followingexample a manuscript written chiefly in Old Church Slavonic is described:

<textLang mainLang="OCS">Old Church Slavonic</textLang>

A manuscript item will sometimes contain material in more than one language. The mainLang attribute should be used only for the chief language. Other languages used may be specified using the otherLangsattribute as in the following example:

<textLang mainLang="OCS" otherLangs="RUS HEL">Mostly Old Church
Slavonic, with some Russian and Greek material</textLang>

Since Old Church Slavonic may be written in eitherCyrillic or Glagolitic scripts, and even occasionally in both within thesame manuscript, it might be preferable to use a more explicitidentifier:

<textLang mainLang="OCS-cyrs">Old Church Slavonic in Cyrillic script</textLang>

The form and scope of language identifiers recommended by theseGuidelines is based on the IANA standard described at vi.i Language identification and should be followed throughout. Where additional detail is needed correctly to describe a language, or to discuss itsdeployment in a given text, this should be done using thelangUsage element in the TEI Header, within whichindividual language elements document the languagesused: see 2.4.2 言語.

Note that the language element defines a particularcombination of human language and writing system. Only onelanguage element may be supplied for each suchcombination. Standard TEI practice also allows this element to bereferenced by any element using the global xml:langattribute in order to specify the language applicable to the contentof that element. For example, assuming that languageelements have been defined with the identifiers fr (forFrench), la (for Latin), and de (forGerman), a manuscript description written in French which specifiesthat a particular manuscript contains predominantly German but alsosome Latin material, mighthave a textLang element like the following:

<textLang xml:lang="fr" mainLang="de" otherLangs="la">allemand et latin</textLang>

« 10.6 Intellectual Content
Home | 目次

10.7 Physical DescriptionTEI: Physical Description¶

Under the general heading ‘physical description’we subsume a large number of different aspects generally regarded asuseful in the description of a given manuscript. These include aspectsof the form, support, extent, and quire structure of the manuscriptobject and of the way in which the text is laid out on the page (10.7.1 Object Description); the styles of writing, such as theway it is laid out on the page, the styles of writing, decorativefeatures, any musicalnotation employed and any annotations or marginalia (10.7.2 Writing, Decoration, and Other Notations); and discussion of its binding, seals, and anyaccompanying material (10.7.3 Bindings, Seals, and Additional Material).

Most manuscript descriptions touch on several of these categoriesof information though few include them all, and not all distinguishthem as clearly as we propose here. In particular, it is often thecase that an existing description will include information for whichwe propose distinct elements within a single paragraph, or evensentence. The encoder must then decide whether to rewrite thedescription using the structure proposed here, or to retain theexisting prose, marked up simply as a series of p elements,directly within the physDesc element.

The physDesc element may thus be used in either of twodistinct ways: it may contain a series of paragraphs addressing topicslisted above and similar ones; or it may act as a container for anychoice of the more specialized elements described in the remainder ofthis section, each of which itself contains a series of paragraphs,and may also have more specific attributes. Note that the two waysshould, and indeed may, not be combined within the samedescription.

10.7.1 Object DescriptionTEI: Object Description¶

The objectDesc element is used to group together thoseparts of the physical description which relate specifically to thetext-bearing object, its format, constitution, layout, etc. Theform attribute is used to indicate the specific type ofwriting vehicle being described, for example, as a codex, roll,tablet, etc. It has two parts: a description of thesupport, i.e. the physical carrier on which the text isinscribed; and a description of the layout, i.e. the waytext is organized on the carrier.

Taking these in turn, the description of the support is taggedusing the following elements, each of which is discussed in moredetail below:

supportDesc (support description) groups elements describing the physical support for the written part of a manuscript.
support contains a description of the materialsetc. which make up the physical support for the written part of a manuscript.
extent describes the approximate size of a text as stored onsome carrier medium, whether digital or non-digital, specified in any convenient units.
collation contains a description of how the leaves or bifolia are physicallyarranged.
foliation describes the numbering system or systems used to count the leaves or pages in a codex.
condition contains a description of the physicalcondition of the manuscript.

Each of these elements contains paragraphs relating to the topicconcerned. Within these paragraphs, phrase-level elements (inparticular those discussed above at 10.3 Phrase-level Elements),may be used to tag specific terms of interest if sodesired.

<objectDesc form="codex">
<supportDesc>
 Mostly <material>paper</material>, with watermarks
 <watermark>unicorn</watermark> (<ref>Briquet 9993</ref>) and
 <watermark>ox</watermark> (close to <ref>Briquet 2785</ref>).
 The first and last leaf of each quire, with the exception of
 quires xvi and xviii, are constituted by bifolia of parchment,
 and all seven miniatures have been painted on inserted
 singletons of parchment.
</supportDesc>
</objectDesc>

This example combines information which might alternatively be moreprecisely tagged using the more specific elements described in thefollowing subsections.

» 10.7.1.2 Extent
Home | 目次

10.7.1.1 SupportTEI: Support¶

The support element groups together information about thephysical carrier. Typically, for western manuscripts, this will entaildiscussion of the material (parchment, paper, or a combination of thetwo) written on. For paper, a discussion of any watermarks present mayalso be useful. If this discussion makes reference to standardcatalogues of such items, these may be tagged using the standardref element as in the following example:

<support>

 <material>Paper</material> with watermark: <watermark>anchor in a circle
 with star on top</watermark>, <watermark>countermark B-B with
 trefoil</watermark> similar to <ref>Moschin, Anchor N 1680</ref>
 <date>1570-1585</date>.
</support>

10.7.1.2 ExtentTEI: Extent¶

The extent element, defined in the TEI header, may also beused in a manuscript description to specify the number ofleaves a manuscript contains, as in the following example:

Information regarding the size of the leaves may bespecifically marked using the phrase level dimensionselement, as in the following example, or left as plain prose.

<extent>ii + 321 leaves
<dimensions unit="cm">
<height>35</height>
<width>27</width>
</dimensions>
</extent>

Alternatively, the generic measure element might be used within extent, as in the following example:

10.7.1.3 CollationTEI: Collation¶

The collation element should be used to provide adescription of a book's current and original structure, that is, thearrangement of its leaves and quires. This information may be conveyedusing informal prose, or any appropriate notationalconvention. Although no specific notation is defined here, provisionis made for the tagging of such with the standard TEI formulaelement. Here are some examples of different ways of treating collation:

<collation>

 <formula>1-3:8, 4:6, 5-13:8</formula>

</collation>
<collation>
There are now four gatherings, the first, second and fourth originally consisting of
 eight leaves, the third of seven. A fifth gathering thought to have followed has left no trace.
<list>
 <item>Gathering I consists of 7 leaves, a first leaf, originally conjoint with <locus>fol. 7</locus>,
 having been cut away leaving only a narrow strip along the gutter; the others, <locus>fols 1</locus>
 and <locus>6</locus>, <locus>2</locus> and <locus>5</locus>, and <locus>3</locus> and <locus>4</locus>,
 are bifolia.</item>
 <item>Gathering II consists of 8 leaves, 4 bifolia.</item>
 <item>Gathering III consists of 7 leaves; <locus>fols 16</locus> and <locus>22</locus> are conjoint,
 the others singletons.</item>
 <item>Gathering IV consists of 2 leaves, a bifolium.</item>
 </list>

</collation>
<collation>
I (1, 2+9, 3+8, 4+7, 5+6, 10); II (11, 12+17, 13, 14, 15, 16, 18, 19).
</collation>
<collation>

 <formula>1-5.8 6.6 (catchword, f. 46, does not match following
 text) 7-8.8 9.10, 11.2 (through f. 82) 12-14.8 15.8(-7)</formula>

</collation>

10.7.1.4 FoliationTEI: Foliation¶

The foliation element may be used to indicate the scheme,medium or location of folio, page, column, or line numbers written inthe manuscript, frequently including a statement about when and, ifknown, by whom, the numbering was done.

<foliation>
Neuere Foliierung, die auch das Vorsatzblatt mitgezählt hat.
</foliation>
<foliation>
Folio numbers were added in brown ink by Árni Magnússon
ca. 1720-1730 in the upper right corner of all recto-pages.
</foliation>

Where a manuscript contains traces of more thanone foliation, each should be recorded as a distinctfoliation element and optionally given a distinct value forits xml:id attribute. The locus element discussed in10.3.5 References to Locations within a Manuscript can then indicate which foliation scheme is being citedby means of its source attribute, which points to thisidentifier:

<foliation xml:id="original">
Original foliation in red roman numerals in the middle of
the outer margin of each recto
</foliation>
<foliation xml:id="modern">
Foliated in pencil in the top right
corner of each recto page.
</foliation>

10.7.1.5 ConditionTEI: Condition¶

The condition element is used to summarize the overallphysical state of a manuscript, in particular where such informationis not recorded elsewhere in the description. It should not, however, beused to describe changes or repairs to a manuscript, as these are moreappropriately described as a part of its custodial history (see 10.7.5.1.2 Availability and Custodial History).

<condition>
The manuscript shows signs of damage from water and mould on its outermost leaves.
</condition>
<condition>
Despite tears on many of the leaves the codex is reasonably well preserved.
 The top and the bottom of f. 1 is damaged, and only a thin slip is left of the original second
 leaf (now foliated as 1bis). The lower margin of f. 92 has been cut away. There is a lacuna of
 one leaf between ff. 193 and 194. The manuscript ends defectively (there are approximately six
 leaves missing).
</condition>

« 10.7.1.5 Condition
Home | 目次

10.7.1.6 Layout DescriptionTEI: Layout Description¶

The second part of the objectDesc element is thelayoutDesc element, which is used to describe and document themise-en-page of the manuscript, that is the way in which text and illumination are arranged on the page, specifying for example the number of written, ruled, orpricked lines and columns per page, size of margins,distinct blocks such as glosses, commentaries, etc. This may be given as a simpleseries of paragraphs. Alternatively, one or more different layoutsmay be identified within a single manuscript, each described by itsown layout element.

layoutDesc (layout descrition) collects the set of layout descriptions applicable to a manuscript.
layout describes how text is laid out on the page, including information about any ruling, pricking, or other evidence of page-preparation techniques.

Where the layout element is used, the layout will often besufficiently regular for the attributes on this element to convey allthat is necessary; more usually however a more detailed treatment willbe required. The attributes are provided as a convenient shorthand forcommonly occurring cases, and should not be used except where thelayout is regular. The value NA (not-applicable) shouldbe used for cases where the layout is either very irregular, or whereit cannot be characterized simply in terms of lines and columns, forexample, where blocks of commentary and text are arranged in a regularbut complex pattern on each page

The following examples indicate the range of possibilities:

<layout ruledLines="25 32">
Most pages have between 25 and 32 long lines ruled in lead.
</layout>
<layout columns="1" writtenLines="24">
Written in one column throughout; 24 lines per page.
</layout>
<layout>
Written in 3 columns, with 8 lines of text and interlinear glosses in
 the centre, and up to 26 lines of gloss in the outer two columns. Double
 vertical bounding lines ruled in hard point on hair side. Text lines ruled
 faintly in lead. Remains of prickings in upper, lower, and outer (for 8 lines
 of text only) margins.
</layout>

Where multiple layout elements are supplied, the scope foreach specification can be indicated by means of locuselements within the content of the element, as in the followingexample:

<layoutDesc>
<layout ruledLines="25 32">
 On <locus from="1r" to="202v">fols 1r-200v</locus> and
 <locus from="210r" to="212v">fols 210r-212v</locus> there are
 between 25 and 32 ruled lines.
</layout>
<layout ruledLines="34 50">
 On <locus from="203r" to="209v">fols 203r-209v</locus> there are between 34
 and 50 ruled lines.
</layout>
</layoutDesc>

10.7.2 Writing, Decoration, and Other NotationsTEI: Writing, Decoration, and Other Notations¶

The second group of elements within a structured physical descriptionconcerns aspects of the writing, illumination, or other notation (notably, music) foundin a manuscript, including additions made in later hands — the ‘text’, as it were, as opposed to the carrier.

handDesc (description of hands) contains a description of all the different kinds of writing used in a manuscript.
handNote (note on hand) describes a particular styleor hand distinguished within a manuscript.
decoDesc (decoration description) contains a description of the decoration of a manuscript, either as a sequence of paragraphs, or as a sequence of topically organised decoNote elements.
decoNote (note on decoration) contains a note describing either adecorative component of a manuscript, or a fairly homogenous class ofsuch components.
musicNotation contains description of type of musical notation.
additions contains a description of any significant additions foundwithin a manuscript, such as marginalia or other annotations.

» 10.7.2.2 Decoration
Home | 目次

10.7.2.1 WritingTEI: Writing¶

The handDesc element can contain a short description ofthe general characteristics of the writing observed in a manuscript,as in the following example:

<handDesc>
Written in a <term>late Caroline minuscule</term>; versals in a
 form of <term>rustic capitals</term>; although the marginal and
 interlinear gloss is written in varying shades of ink that are
 not those of the main text, text and gloss appear to have been
 copied during approximately the same time span.
</handDesc>

Note the use of the term element to mark specific technicalterms within the context of the handDesc element.

Where several distinct hands have been identified, this fact can be registered by using the hands attribute, as inthe following example:

<handDesc hands="2">
The manuscript is written in two contemporary hands, otherwise
 unknown, but clearly those of practised scribes. Hand I writes
 ff. 1r-22v and hand II ff. 23 and 24. Some scholars, notably
 Verner Dahlerup and Hreinn Benediktsson, have argued for a third hand
 on f. 24, but the evidence for this is insubstantial.
</handDesc>

Alternatively, or in addition, where more specificinformation about one or more of the hands identified is to be recorded,the handNote element shouldbe used, as in the following example:

<handDesc hands="3">
<handNote xml:id="Eirsp-1" scope="minor">
 The first part of the manuscript,
 <locus from="1v" to="72v:4">fols 1v-72v:4</locus>, is written in a practised
 Icelandic Gothic bookhand. This hand is not found elsewhere.
</handNote>
<handNote xml:id="Eirsp-2" scope="major">
 The second part of the manuscript, <locus from="72v:4" to="194v">fols
 72v:4-194</locus>, is written in a hand contemporary with the first; it can
 also be found in a fragment of <title>Knýtlinga saga</title>,
 <ref>AM 20b II fol.</ref>.
</handNote>
<handNote xml:id="Eirsp-3" scope="minor">
 The third hand has written the majority of the chapter headings.
 This hand has been identified as the one also found in <ref>AM
 221 fol.</ref>.
</handNote>
</handDesc>

Note here the use of the locus element, discussed in section 10.3.5 References to Locations within a Manuscript, to specify exactly which parts of amanuscript are written by a given hand.

When a full or partial transcription of a manuscript is availablein addition to the manuscript description, the handShiftelement described in 11.4.1 Document Hands can be used to link therelevant parts of the transcription to the appropriatehandNote element in the description: for example, at thepoint in the transcript where the second hand listed above starts(i.e. at folio 72v:4), we might insert handShiftnew="#Eirsp-2"/

10.7.2.2 DecorationTEI: Decoration¶

It can be difficult to draw a clear distinction between aspects ofa manuscript which are purely physical and those which form part ofits intellectual content. This is particularly true of illuminationsand other forms of decoration in a manuscript. We propose thefollowing elements for the purpose of delimiting discussion of theseaspects within a manuscript description, and for convenience locatethem all within the physical description, despite the fact that theillustrative features of a manuscript will in many cases also be seenas constitutiing part of its intellectual content.

The decoDesc element may contain simply one or moreparagraphs summarizing the overall nature of the decorative featuresof the manuscript, as in the following example:

<decoDesc>
The decoration comprises two full page miniatures, perhaps added
 by the original owner, or slightly later; the original major decoration
 consists of twenty-three large miniatures, illustrating the divisions of
 the Passion narrative and the start of the major texts, and the major
 divisions of the Hours; seventeen smaller miniatures, illustrating the
 suffrages to saints; and seven historiated initials, illustrating
 the pericopes and major prayers.
</decoDesc>

Alternatively, it may contain a series of more specific typeddecoNote elements, each summarizing a particular aspect orindividual instance of the decoration present, for example the use ofminiatures, initials (historiated or otherwise), borders, diagrams,etc., as in the following example:

<decoDesc>
<decoNote type="miniature">
 One full-page miniature, facing the beginning of the first
 Penitential Psalm.
</decoNote>
<decoNote type="initial">
 One seven-line historiated initial, commencing the first
 Penitential Psalm.
</decoNote>
<decoNote type="initial">
 Six four-line decorated initials, commencing the second through the
 seventh Penitential Psalm.
</decoNote>
<decoNote type="initial">
 Some three hundred two-line versal initials with pen-flourishes,
 commencing the psalm verses.
</decoNote>
<decoNote type="border">
 Four-sided border decoration surrounding the miniatures and three-sided
 border decoration accompanying the historiated and decorated initials.
</decoNote>
</decoDesc>

Where more exact indexing of the decorative content of a manuscriptis required, the standard TEI elements term or indexmay be used within the prose description to supply or delimitappropriate iconographic terms, as in the following example:

<decoDesc>
<decoNote type="miniatures">
 Fourteen large miniatures with arched tops, above five lines of text:
 <list>
 <item>
 <locus>fol. 14r</locus>Pericopes. <term>St. John writing on
 Patmos</term>, with the Eagle holding his ink-pot and pen-case; some
 flaking of pigment, especially in the sky</item>
 <item>
 <locus>fol. 26r</locus>Hours of the Virgin, Matins.
 <term>Annunciation</term>; Gabriel and the Dove to the right</item>
 <item>
 <locus>fol. 60r</locus>Prime. <term>Nativity</term>; the
 <term>Virgin and Joseph adoring the Child</term>
 </item>
 <item>
 <locus>fol. 66r</locus>Terce. <term>Annunciation to the
 Shepherds</term>, one with <term>bagpipes</term>
 </item>

 </list>
 
</decoNote>
</decoDesc>

10.7.2.3 Musical NotationTEI: Musical Notation¶

Where a manuscript contains music, the musicNotationelement may be used to describe the form of notation employed, as inthe following example:

<musicNotation>
Square notation on 4-line red staves.
</musicNotation>
<musicNotation>
Neumes in campo aperto of the St. Gall type.
</musicNotation>

« 10.7.2.3 Musical Notation
Home | 目次

10.7.2.4 Additions and MarginaliaTEI: Additions and Marginalia¶

The additions element can be used to list or describe anyadditions to the manuscript, such as marginalia, scribblings, doodles,etc., which are considered to be of interest or importance. Suchtopics may also be discussed or referenced elsewhere in a description,for example in the history element, in cases where themarginalia provide evidence of ownership. Some examples follow:

<additions>
Doodles on most leaves, possibly by children, and often quite amusing.
</additions>
<additions>
Quelques annotations marginales des XVIe et XVIIe s.
</additions>
<additions>
The text of this manuscript is not interpolated with sentences from
 Royal decrees promulgated in 1294, 1305 and 1314. In the margins, however,
 another somewhat later scribe has added the relevant paragraphs of these
 decrees, see pp. 8, 24, 44, 47 etc.
As a humorous gesture the scribe in one opening of the manuscript, pp. 36
 and 37, has prolonged the lower stems of one letter f and five letters þ
 and has them drizzle down the margin.
</additions>
<additions>
Spaces for initials and chapter headings were left by the scribe but not filled in.
 A later, probably fifteenth-century, hand has added initials and chapter headings in
 greenish-coloured ink on fols <locus>8r</locus>, <locus>8v</locus>, <locus>9r</locus>,
<locus>10r</locus> and <locus>11r</locus>. Although a few of these chapter headings are
 now rather difficult to read, most can be made out, e.g. fol. <locus>8rb</locus>
 <quote xml:lang="is">floti ast<expan>ri</expan>d<expan>ar</expan>
 </quote>; fol. <locus>9rb</locus>
 <quote xml:lang="is">v<expan>m</expan> olaf conung</quote>, and fol. <locus>10ra</locus>
 <quote xml:lang="is">Gipti<expan>n</expan>g ol<expan>a</expan>fs k<expan>onun</expan>gs</quote>.
The manuscript contains the following marginalia:
<list>
 <item>Fol. <locus>4v</locus>, left margin: <quote xml:lang="is">hialmadr <expan>ok</expan>
 <lb/>brynjadr</quote>,
 in a fifteenth-cenury hand, imitating an addition made to the text by the scribe at this point.</item>
 <item>Fol. <locus>5r</locus>, lower margin: <quote xml:lang="is">þ<expan>e</expan>tta þiki
 m<expan>er</expan> v<expan>er</expan>a gott blek en<expan>n</expan>da kan<expan>n</expan> ek icki
 betr sia</quote>, in a fifteenth-century hand, probably the same as that on the previous page.</item>
 <item>Fol. <locus>9v</locus>, bottom margin: <quote xml:lang="is">þessa bok uilda eg <sic>gæt</sic>
 lært med <lb/>an Gud gefe myer Gott ad <lb/>læra</quote>; seventeenth-century hand.</item>
 </list>

There are in addition a number of illegible scribbles in a later hand (or hands) on fols
<locus>2r</locus>, <locus>3r</locus>, <locus>5v</locus> and <locus>19r</locus>.
</additions>

10.7.3 Bindings, Seals, and Additional MaterialTEI: Bindings, Seals, and Additional Material¶

The third major component of the physical description relates tosupporting but distinct physical components, such as bindings, seals and accompanying material. These may be described using the following specialist elements:

bindingDesc (binding description) describes the present and former bindings of a manuscript, eitheras a series of paragraphs or as a series of distinct binding elements,one for each binding of the manuscript.
binding contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript.
sealDesc (seal description) describes the seals or other external items attached to a manuscript, eitheras a series of paragraphs or as a series of distinct seal elements,possibly with additional decoNotes.
seal contains a description of one seal or similar attachment applied to a manuscript.
accMat (accompanying material) contains details of any significant additionalmaterial which may be closely associated with the manuscript beingdescribed, such as non-contemporaneous documents or fragments bound inwith the manuscript at some earlier historical period.

» 10.7.3.2 Seals
Home | 目次

10.7.3.1 Binding DescriptionsTEI: Binding Descriptions¶

The bindingDesc element contains a description of the state ofthe present and former bindings of a manuscript, including informationabout its material, any distinctive marks, and provenance information. This maybe given as a series of paragraphs, if only one binding is being described, oras a series of distinct binding elements, each describing a distinctbinding, where these are separately described. For example:

<bindingDesc>
Sewing not visible; tightly rebound over 19th-century pasteboards, reusing
 panels of 16th-century brown leather with gilt tooling à la fanfare, Paris
 c. 1580-90, the centre of each cover inlaid with a 17th-century oval medallion
 of red morocco tooled in gilt (perhaps replacing the identifying mark of a
 previous owner); the spine similarly tooled, without raised bands or title-piece;
 coloured endbands; the edges of the leaves and boards gilt. Boxed.
</bindingDesc>

Within a binding description, the element decoNote isavailable, as an alternative to p, for paragraphs dealingexclusively with information about decorative features of a binding,as in the following example:

<binding>
Bound, s. XVIII (?), in <material>diced russia leather</material>
 retaining most of the original 15th century metal ornaments (but with
 some replacements) as well as the heavy wooden boards.
<decoNote>
 On each cover: alternating circular stamps of the Holy Monogram,
 a sunburst, and a flower.
</decoNote>
<decoNote>
 On the cornerpieces, one of which is missing, a rectangular stamp
 of the Agnus Dei.
</decoNote>
Rebacked during the 19th century.
</binding>

10.7.3.2 SealsTEI: Seals¶

The sealDesc element supplies information about theseal(s) attached to documents to guarantee their integrity, or to showauthentication of the issuer or consent of the participants. It maycontain one or more paragraphs summarizing the overall nature of theseals, or may contain one or more seal elements.

<sealDesc>
<seal n="1" type="pendant" subtype="cauda_duplex">
 Round seal of <name>Anders Olufsen</name> in black wax:
 <bibl>
 <ref>DAS 930</ref>
 </bibl>. Parchment tag, on which is written:
 <quote>pertinere nos predictorum placiti nostri iusticarii precessorum dif</quote>.
</seal>
<seal n="2" type="pendant" subtype="cauda_duplex">
 The seal of <name>Jens Olufsen</name> in black wax:
 <bibl>
 <ref>DAS 1061</ref>
 </bibl>. Legend: <quote>S IOHANNES OLAVI</quote>.
 Parchment tag on which is written: <quote>Woldorp Iohanne G</quote>.
</seal>
</sealDesc>

« 10.7.3.2 Seals
Home | 目次

10.7.3.3 Accompanying MaterialTEI: Accompanying Material¶

The circumstance may arise where material not originally part of amanuscript is bound into or otherwise kept with a manuscript. In somecases this material would best be treated in a separatemsPart element (see 10.7.6 Manuscript Parts below). There are,however, cases where the additional matter is not self-evidently adistinct manuscript: it might, for example, be a set of notes by alater scholar, or a file of correspondence relating to themanuscript. The accMat element is provided as a holder forthis kind of information.

accMat (accompanying material) contains details of any significant additionalmaterial which may be closely associated with the manuscript beingdescribed, such as non-contemporaneous documents or fragments bound inwith the manuscript at some earlier historical period.

Here is an example of the use of this element, describing a note bythe Icelandic manuscript collector Árni Magnússon whichhas been bound with the manuscript:

<accMat>
A slip in Árni Magnússon's hand has been stuck to the
 pastedown on the inside front cover; the text reads:
<quote xml:lang="is">Þidreks Søgu þessa hefi eg
 feiged af Sekreterer Wielandt Anno 1715 i Kaupmanna høfn. Hun er,
 sem eg sie, Copia af Austfirda bókinni (Eidagás) en<expan>n</expan>
 ecki progenies Brædratungu bokarinnar. Og er þar fyrer eigi i
 allan<expan>n</expan> máta samhlioda þ<expan>eir</expan>re er
 Sr Jon Erlendz son hefer ritad fyrer Mag. Bryniolf. Þesse Þidreks
 Saga mun vera komin fra Sr Vigfuse á Helgafelle.</quote>

</accMat>

10.7.4 HistoryTEI: History¶

The following elements are used to record information about the history of a manuscript:

history groups elementsdescribing the full history of a manuscript or manuscript part.
origin contains any descriptive or other informationconcerning the origin of a manuscript or manuscript part.
provenance contains any descriptive or other informationconcerning a single identifiable episode during the history of a manuscriptor manuscript part, after its creation but before its acquisition.
acquisition contains any descriptive or other informationconcerning the process by which a manuscript or manuscript part entered the holdinginstitution.

The three components of the history element all have thesame substructure, consisting of one or more paragraphs marked asp elements. Each of these three elements is also a member ofthe att.datable attribute class, itself amember of the att.datable.w3c class, andthus also carries the following optional attributes:

att.datable.w3c provides attributes for normalization of elements that contain datable events using the W3C datatypes.
notBefore specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
notAfter specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.

Information about the origins of the manuscript, its place and dateof writing, should be given as one or more paragraphs contained by asingle origin element; following this, any availableinformation on distinct stages in the history of the manuscript beforeits acquisition by its current holding institution should be includedas paragraphs within one or more provenanceelements. Finally, any information specific to the means by which themanuscript was acquired by its present owners should be given asparagraphs within the acquisition element.

Here is a fairly simple example of the use of this element:

<history>
<origin>
 Written in <origPlace>Durham</origPlace> during <origDate notBefore="1125" notAfter="1175">the
 mid-twelfth century</origDate>.
</origin>
<provenance>
 Recorded in two medieval catalogues of the books belonging
 to <name type="org">Durham Priory</name>, made in <date>1391</date> and
 <date>1405</date>.
 Given to <name type="person">W. Olleyf</name> by <name type="person">William
 Ebchester, Prior (1446-56)</name> and later belonged to <name type="person">Henry
 Dalton</name>, Prior of Holy Island (<name type="place">Lindisfarne</name>)
 according to inscriptions on ff. 4v and 5.
</provenance>
<acquisition>
 Presented to <name type="org">Trinity College</name> in
 <date>1738</date> by <name type="person">Thomas Gale</name> and
 his son <name type="person">Roger</name>.
</acquisition>
</history>

Here is a fuller example:

<history>
<origin notBefore="1225" notAfter="1275">
 Written in Spain or Portugal in the middle of the 13th century
 (the date 1042, given in a marginal note on f. 97v, cannot be correct.)
</origin>
<provenance>
 The Spanish scholar <name type="person">Benito Arias
 Montano</name> (1527-1598) has written his name on f. 97r, and may be
 presumed to have owned the manuscript. It came somehow into the
 possession of <foreign xml:lang="da">etatsråd</foreign>
 <name type="person">Holger Parsberg</name> (1636-1692), who has written his
 name twice, once on the front pastedown and once on f. 1r, the former dated
 <date>1680</date> and the latter <date>1682</date>. Following Parsberg's
 death the manuscript was bought by <foreign>etatsråd</foreign>
 <name type="person">Jens Rosenkrantz</name> (1640-1695) when Parsberg's
 library was auctioned off (23 October 1693).
</provenance>
<acquisition notBefore="1696" notAfter="1697">
 The manuscript was acquired by Árni
 Magnússon from the estate of Jens Rosenkrantz, presumably at
 auction (the auction lot number 468 is written in red chalk on the
 flyleaf), either in 1696 or 97.
</acquisition>
</history>

10.7.5 Additional informationTEI: Additional information¶

Three categories of additional information are provided for by thescheme described here, grouped together within the additionalelement described in this section.

additional groups additional information, combiningbibliographic information about a manuscript, or surrogate copies ofit with curatorial or administrative information.
adminInfo (administrative information) contains information about the presentcustody and availability of the manuscript, and also about the recorddescription itself.
surrogates contains information about any digital orphotographic representations of the manuscript being described whichmay exist in the holding institution or elsewhere.
listBibl (citation list) contains a list of bibliographic citations of any kind.

None of the constituent elements of additional isrequired. If any is supplied, it may appear once only; furthermore,the order in which elements are supplied should be as specified above.

» 10.7.5.2 Surrogates
Home | 目次

10.7.5.1 Administrative informationTEI: Administrative information¶

A variety of information relating to the curation and management ofa manuscript may be recorded as simple prose narrative tagged usingthe standard p element. Alternatively, different aspects of thisinformation may be presented grouped within one or moreof the following specialized elements:

recordHist (recorded history) provides information about the source andrevision status of the parent manuscript description itself.
availability supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, etc.
custodialHist (custodial history) contains a description of a manuscript's custodial history, eitheras running prose or as a series of dated custodial events.

10.7.5.1.1 Record HistoryTEI: Record History¶

The recordHist element, if supplied, must contain asource element, followed by an optional series ofchange elements.

source describes the original source for the information contained with a manuscript description.
change summarizes a particular change or correction madeto a particular version of an electronic text which isshared between several researchers.

The source element is used to document the primary sourceof information for the record containing it, in a similarway to the standard TEI sourceDesc element within a TEIHeader. If the record is a new one, made without reference to anythingother than the manuscript itself, then it may simply contain a pelement, as in the following example:

<source>
Directly catalogued from the original manuscript.
</source>

Frequently, however, the record will be derived from somepreviously existing description, which may be specified using thestandard TEI bibl element, as in the following example:

<recordHist>
<source>
 Information transcribed from <bibl>
 <title>The index of Middle English verse</title>
 <biblScope>123</biblScope>
 </bibl>.
</source>
</recordHist>

If, as is likely, a full bibliographic description of the sourcefrom which cataloguing information was taken is included within thelistBibl element contained by the current additionalelement, or elsewhere in the current document, then it need not berepeated here. Instead, it should be referenced using the standard TEIref element, as in the following example:

<additional>
<adminInfo>
 <recordHist>
 <source>
 Information transcribed from
 <bibl>
 <ref target="#IMEV">IMEV</ref> 123</bibl>.
 </source>
 </recordHist>
</adminInfo>
<listBibl>
 <bibl xml:id="IMEV">
 <author>Carleton Brown</author> and <author>Rossell Hope Robbins</author>
 <title level="m">The index of Middle English verse</title>
 <pubPlace>New York</pubPlace>
 <date>1943</date>
 </bibl>

</listBibl>
</additional>

The change element is a standard TEI element, whichmay also appear within the revisionDesc element of thestandard TEI Header; its use here is intended to signal thesimilarity of function between the two container elements. Where theTEI Header should be used to document the revision history of thewhole electronic file to which it is prefixed, the recordHistelement may be used to document changes at a lower level, relating tothe individual description, as in the following example:

<change when="2005-03-10">On 10 March 2005
<name>MJD</name> converted to P5</change>

« 10.7.5.1.1 Record History
Home | 目次

10.7.5.1.2 Availability and Custodial HistoryTEI: Availability and Custodial History¶

The availability element is a standard TEI element,which should be used here to supply any information concerningaccess to the current manuscript, such as its physical location (where thisis not implicit in its identifier), any restrictions on access, informationabout copyright, etc.

<availability>
Viewed by appointment only, to be arranged with curator.
</availability>
<availability>
In conservation, Jan. - Mar., 2002. On loan to the
 Bayerische Staatsbibliothek, April - July, 2002.
</availability>
<availability>
The manuscript is in poor condition, due to many of the leaves being
 brittle and fragile and the poor quality of a number of earlier repairs;
 it should therefore not be used or lent out until it has been conserved.
</availability>

The custodialHist record is used to describe the custodialhistory of a manuscript, recording any significant events noted duringthe period that it has been located within its holding institution. Itmay contain either a series of paragraphs tagged with the standard TEIp element, or a series of custEvent elements, eachdescribing a distinct incident or event, further specified by atype attribute, and carrying dating information by virtueof its membership in the att.datable class, as noted above.

custEvent (custodial event) describes a single event during the custodial history of a manuscript.

Here is an example of the use of this element:

<custodialHist>
<custEvent type="conservation" notBefore="1961-03-01" notAfter="1963-02-28">
 Conserved between March 1961 and February 1963 at Birgitte Dalls
 Konserveringsværksted.
</custEvent>
<custEvent type="photography" notBefore="1988-05-01" notAfter="1988-05-30">
 Photographed in May 1988 by AMI/FA.
</custEvent>
<custEvent type="transfer" notBefore="1989-11-13" notAfter="1989-11-13">
 Dispatched to Iceland 13 November 1989.
</custEvent>
</custodialHist>

10.7.5.2 SurrogatesTEI: Surrogates¶

The surrogates element is usedto provide information about any digital or photographicrepresentations of the manuscript which may exist within the holdinginstitution or elsewhere.

surrogates contains information about any digital orphotographic representations of the manuscript being described whichmay exist in the holding institution or elsewhere.

The surrogates element should not be used to repeatinformation about representations of the manuscript available withinpublished works; this should normally be documented within thelistBibl element within the additionalelement. However, it is often also convenient to record informationsuch as negative numbers, digital identifiers etc. for unpublishedcollections of manuscript images maintained within the holdinginstitution, as well as to provide more detailed descriptiveinformation about the surrogate itself. Such information may be providedas prose paragraphs, within which identifying information about particularsurrogates may be presented using the standard TEI bibl element,as in the following example:

<surrogates>

 <bibl>
 <title type="gmd">microfilm (master)</title>
 <idno>G.neg. 160</idno> n.d.</bibl>
 <bibl>
 <title type="gmd">microfilm (archive)</title>
 <idno>G.pos. 186</idno> n.d.</bibl>
 <bibl>
 <title type="gmd">b/w prints</title>
 <idno>AM 795 4to</idno>
 <date when="1999-01-27">27 January 1999</date>
 <note>copy of G.pos. 186</note>
 </bibl>
 <bibl>
 <title type="gmd">b/w prints</title>
 <idno>reg.nr. 75</idno>
 <date when="1999-01-25">25 January 1999</date>
 <note>photographs of the spine, outside covers, stitching etc.</note>
 </bibl>

</surrogates>

Note the use of the specialized form of title (general material designation) to specify the kind of surrogate being documented.

At a later revision, the content of the surrogates elementis likely to be expanded to include elements more specificallyintended to provide detailed information such as technical details ofthe process by which a digital or photographic image was made. Forinformation about the inclusion of digital facsimile images within aTEI document, refer also to 11.1 Digital Facsimiles.

10.7.6 Manuscript PartsTEI: Manuscript Parts¶

The msPart element may be used in cases where what wereoriginally physically separate manuscripts or parts of manuscriptshave been bound together and/or share the same call number.

msPart (manuscript part) contains information about an originallydistinct manuscript or part of a manuscript, now forming part of a composite manuscript.

Since each component of such a composite manuscript will in alllikelihood have its own content, physical description, history, and soon, the structure of msPart is in the main identical to thatof msDesc, allowing one to retain the top level ofidentity (msIdentifier), but to branch out thereafter into asmany parts, or even subparts, as necessary. If the parts of acomposite manuscript have their own identifiers, they should be taggedusing the idno element, rather than the msIdentifierelement, as in the following example:

<msDesc>
<msIdentifier>
 <settlement>Amiens</settlement>
 <repository>Bibliothèque Municipale</repository>
 <idno>MS 3</idno>
 <msName>Maurdramnus Bible</msName>
</msIdentifier>

<msPart>
 <altIdentifier>
 <idno>MS 6</idno>
 </altIdentifier>

</msPart>
<msPart>
 <altIdentifier>
 <idno>MS 7</idno>
 </altIdentifier>

</msPart>
<msPart>
 <altIdentifier>
 <idno>MS 9</idno>
 </altIdentifier>

</msPart>

</msDesc>

« 10.7.6 Manuscript Parts
Home | 目次

10.7.7 手書きモジュールTEI: 手書きモジュール¶

The module described in this chapter makes available the followingcomponents:

Module msdescription: Manuscript Description

Elements defined: accMat acquisition additional additions adminInfo altIdentifier binding bindingDesc catchwords collation collection colophon condition custEvent custodialHist decoDesc decoNote depth dimensions explicit filiation finalRubric foliation handDesc height heraldry history incipit institution layout layoutDesc locus material msContents msDesc msIdentifier msItem msItemStruct msName msPart musicNotation objectDesc origDate origPlace origin physDesc provenance recordHist repository rubric seal sealDesc secFol signatures source stamp summary support supportDesc surrogates textLang watermark width
Classes defined: att.msExcerpt

The selection and combination of modules to form a TEI schema is described in1.2 TEIスキーマの定義.

↑ Contents « 9 Dictionaries » 11 Representation of Primary Sources

unit	names the unit used for the measurement
scope	specifies the applicability of this measurement, where more than one object is being measured.
quantity	specifies the length in the units specified

notBefore	specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
notAfter	specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.