P5 Fascicule - idhmcmain.tamu.eduidhmcmain.tamu.edu/poetess/about/FASC-ms.pdf · P5 Fascicule Lou...

P5 Fascicule

Lou Burnard, Sebastian Rahtz Date:

÷ODDSUBSET ÷ TheManuscriptDescriptionElement÷Overview

This module defines a special purpose element which may be used to provide detailed descriptive informationabout handwritten primary sources. Although originally developed with the needs of cataloguers and scholarsworking with medieval manuscripts in the European tradition, the scheme presented here is general enough that itcan also be extended to other traditions and materials, and is potentially useful for any kind of inscribed artefact.The scheme described here is also intended to accomodate the needs of many different classes of encoders. On theone hand, encoders may be engaged in retrospective conversion of existing detailed descriptions and cataloguesinto machine tractable form; on the other, they may be engaged in cataloguing ex nihilo, that is, creating newdetailed descriptions for materials never before catalogued. Some may be primarily concerned to representaccurately the description itself, as opposed to the ideas and interpretations the description represents; othersmay have entirely opposite priorities. At one extreme, a project may simply wish to capture an existing cataloguein a form that can be displayed on the web, and which can be searched for literal strings, or for such featuressuch as titles, authors and dates; at the other, a project may wish to create in highly structured and encoded forma detailed database of information about the physical characteristics, history, interpretation, etc. of the material,able to support practitioners of quantitative codicology as well as librarians.To cater for this diversity, here as elsewhere, these Guidelines propose a flexible approach, in which encodersmust choose for themselves the degree of prescription appropriate to their needs, and are provided with a choiceof encoding mechanisms to support those differing degrees.The <msDescription> element will normally appear within the <sourceDescription> element of the headerof a TEI conformant document, where the document being encoded is a digital representation of some manuscriptoriginal, whether as a transcription, as a collection of digital images, or as some combination of the two.However, in cases where the document being encoded is essentially a collection of manuscript descriptions,the <msDescription> element may be used in the same way as the bibliographic elements (for example,<bibl><biblStruct>) making up the TEI element class tei.bibl. These typically appear within the <listBibl>element.The <msDescription> element carries some special purpose attributes, listed below, which categorise the itemdescribed in various ways.

• <msDescription> contains a description of a single identifiable manuscript or manuscript part

type specifies the type of manuscript being described, for example as ’diploma’, ’codex’ etc.

status specifies the compositional status of a manuscript or manuscript part. Values are:

uni unitary: the manuscript is a complete entity which exists as a single unit.compo composite: the manuscript is a complete entity comprising multiple units of different origin.frag fragmentary: a leaf, a part of a leaf, or a manuscript from which the majority of leaves are

missing.def defective: a ms from which a minority of the leaves are missing.unknown unknown or unstated.

The <msDescription> element has the following components, which provide more detailed information under anumber of headings. Each of these component elements is further described in the remainder of this chapter.

• <msIdentifier> contains the information required to identify a given manuscript or manuscript part uniquelywithin its holding institution.

– No attributes other than those globally available (see definition for tei.global.attributes)

• <head> contains any heading, for example, the title of a section, or the heading of a list or glossary.

type categorizes the heading in some way meaningful to the encoder.

• <msContents> describes the intellectual content of a manuscript or manuscript part either as a series ofparagraphs or as a series of structured manuscript items.

class identifies the text types or classifications applicable to this item

defective indicates whether the work contained is defective, i.e. incomplete.

1 Date:

P5 Fascicule

• <physDesc> contains a full physical description of a manuscript, either as a sequence of paragraphs, or asa series of more specialised elements.


• <history> groups elements describing the full history of a manuscript or manuscript part.


• <additional> groups additional information relating to the modern bibliography for a manuscript, its currentcuratorial status, and and other associated materials.


• <msPart> contains information about an originally distinct manuscript or manuscript fragment nowforming part of a composite manuscript.


The first of these components, <msIdentifier>, is the only mandatory one; it is described in more detail in1.1.3. The Manuscript Identifier below. This is followed optionally by one or more <head> elements, eachholding a brief heading (see 1.1.4. The Manuscript Heading), and then either one or more paragraphs, markedup as a series of elements, or one or more of the specialised elements <msContents> (1.1.5. IntellectualContent), <physDesc> (1.1.6. Physical Description), <history> (1.1.7. History), and <additional> (1.1.8.Additional information), each of which is optional. Finally a full manuscript description may also contain one ormore optional <msPart> elements, (1.1.9. Manuscript Parts).Here is a very simple example of a complete manuscript description, using no additional elements, apart from themandatory <msIdentifier> element:

Example 1.11 <msDescription status="uni">2 <msIdentifier>3 <settlement>Oxford</settlement>4 <repository>Bodleian Library</repository>5 <idno>MS. Rawlinson poet. 149</idno>6 </msIdentifier>7 Geoffrey Chaucer, The Canterbury Tales. 1450-1475 Pembrokeshire (Wales).8 </msDescription>

Here is the same description, using some of the manuscript-specific phrase-level elements described below, butstill fairly simple:

Example 1.21 <msDescription status="uni">2 <msIdentifier>3 <settlement>Oxford</settlement>4 <repository>Bodleian Library</repository>5 <idno>MS. Rawlinson poet. 149</idno>6 </msIdentifier>7 Geoffrey Chaucer, <title>The Canterbury Tales</title>.8 <origDate notBefore="1450" notAfter="1475">1450-1475</origDate>9 <origPlace>Pembrokeshire (Wales)</origPlace>

10 11 </msDescription>

And finally, a more ambitious description for the same manuscript, using the full range of elements described inthe following sections.

Example 1.31 <msDescription status="uni">2 <msIdentifier>3 <settlement>Oxford</settlement>4 <repository>Bodleian Library</repository>5 <idno>MS. Rawlinson poet. 149</idno>6 </msIdentifier>7 <msContents>8 <msItem>9 <author>Geoffrey Chaucer</author>

Date: 2

Lou Burnard, Sebastian Rahtz

10 <title>The Canterbury Tales</title>11 <rubric>The Tales of Canterbury</rubric>12 <note>Mutilated at beginning and end: contains A431-I109213 in the Riverside edition numbering</note>14 <textLang>Middle English</textLang>15 </msItem>16 </msContents>17 <physDesc>18 <objectDesc form="codex">19 <supportDesc>20 <support>21 Parchment codex22 </support>23 <extent>136 folios:24 <dimensions>25 <height>28</height>26 <width>19</width>27 </dimensions>28 </extent>29 <collation>30 Twenty-three quires of eight, of which only nine are not defective,31 and a final (defective) quire of six.32 </collation>33 </supportDesc>34 <layoutDesc>35 <layout ruledLines="38-74">36 Margined and ruled with crayon through fol. 51v , then in drypoint.37 Single columns of 38-74 lines per page.38 </layout>39 </layoutDesc>40 </objectDesc>41 <handDesc hands="4">42 Four hands, varying between cursive anglicana (the first hand) and mixed43 secretary (the fourth hand). The fourth hand is responsible for around44 two-thirds of the manuscript, from fol. 45 to the end; the third hand wrote45 only three lines and a few words on fol. 38r; the other two hands divide the46 remainder of the manuscript up to fol. 45 between them.47 </handDesc>48 <additions>49 A fifteenth-century note in the margin of fol. 114v.50 </additions>51 </physDesc>52 <history>53 <origin>54 55 <origDate notBefore="1450" notAfter="1475">1450-1475</origDate>56 <origPlace>Pembrokeshire (Wales)</origPlace>57 58 </origin>59 <provenance>60 On fol. 91r is a smudged copy of a bill or document61 with names of people and places in Wales (Pembrokeshire, Bangor)62 and the date 160763 </provenance>64 <acquisition>65 Left to the Bodleian by Richard Rawlinson in 1755.66 </acquisition>67 </history>68 <additional>69 <adminInfo>70 <recordHist>71 <source>72 This description is derived from that made by Daniel W. Mosser73 for the Canterbury Tales Project.

3 Date:

P5 Fascicule

74 </source>75 </recordHist>76 </adminInfo>77 <surrogates>78 A rotograph copy of the manuscript was made for John Manly in the 1920s,79 and a copy of this rotograph is available in microfilm as part of the80 Manly/Rickert collection from the University of Chicago library. The81 manuscript has been microfilmed more recently by the Bodleian. Digital82 images derived from this microfilm have been published on the CDROMs83 prepared by the Canterbury Tales Project.84 </surrogates>85 </additional>86 </msDescription>

The formal definition for the <msDescription> element is as follows:

Element: msDescriptionmsDescription =## contains a description of a single identifiable## manuscript or manuscript partelement msDescription msDescription.content, msDescription.attributesmsDescription.content =msIdentifier,head*,( p+ | ( msContents?, physDesc?, history?, additional?, msPart* ) )msDescription.attributes =tei.global.attributes,msDescription.attributes.type,msDescription.attributes.status,[ a:defaultValue = "msDescription" ] attribute TEIform text ?,emptymsDescription.attributes.type =## specifies the type of manuscript being described, for example as’diploma’, ’codex’ etc.attribute type msDescription.attributes.type.content ?msDescription.attributes.type.content = textmsDescription.attributes.status =## specifies the compositional status of a manuscript or manuscript part.attribute status msDescription.attributes.status.content ?msDescription.attributes.status.content = texttei.sourcedesc |= msDescription

÷Phrase− levelelements

When this module is in use, a number of extra elements are added to the phrase level class, and thus becomeavailable within paragraphs and elsewhere in a document. These elements are listed below in alphabetical order:

• <dimensions> contains any kind of dimensional specification.

type indicates which aspect of the object is being measured. Sample values include:

leaves dimensions relate to one or more leaves (e.g. a single leaf, a gathering, or a separately boundpart)

ruled dimensions relate to the area of a leaf which has been ruled in preparation for writing.pricked dimensions relate to the area of a leaf which has been pricked out in preparation for ruling

(used where this differs significantly from the ruled area, or where the ruling is not measurable).written dimensions relate to the area of a leaf which has been written, with the height measured from

the top of the minims on the top line of writing, to the bottom of the minims on the bottom lineof writing.

miniatures dimensions relate to the miniatures within the manuscriptbinding dimensions relate to the binding in which the codex or manuscript is contained

Date: 4

msDescription.content

msIdentifier

head

p

msContents

physDesc

history

additional

msPart

msDescription

box dimensions relate to the box or other container in which the manuscript is stored.

• <heraldry> contains a heraldic formula or phrase, typically found as part of a blazon, coat of arms, etc.within a manuscript .


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

scheme identifies the foliation scheme in terms of which the location is being specified

from specifies the starting point of the location in a normalised form

to specifies the end-point of the location in a normalized form

targets supplies a link to one or more page images or transcriptions of the specified range of folios

• <material> contains a phrase describing the material of which any part of a manuscript or binding iscomposed.


• <origDate> contains any form of date, used to identify the date of origin for a manuscript or manuscriptpart.


• <origPlace> contains any form of place name, used to identify the place of origin for a manuscript ormanuscript part.


• <secFol> The word or words that a cataloguer, typically medieval but possibly modern as well, might takefrom a fixed point in all the codices he is describing (the beginning of the second leaf, the beginning of thesecond column, the beginning of the penultimate leaf, the end of the penultimate leaf, and so on) in order toprovide a unique identifier to the particular codex.


• <signatures> contains discussion of the leaf or quire signatures found within a codex.


• <watermark> contains a word or phrase describing a watermark or similar device.


Within a manuscript description, many other standard TEI phrase level elements are available, notably thosedescribed in the Core module («CO». Additional elements of particular relevance to manuscript description suchas those for names and dates may also be made available by including the relevant module in your schema.÷Originationandmaterial

The <origDate> and <origPlace> elements are specialised forms of the existing <date> and <name> elements,used to indicate specifically date and place of origin respectively. The <origDate> element is a member of thedatable class, and may thus also carry the following attributes:

• <tei.datable> defines the set of attributes common to all elements that contain datable events.

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.

certainty specifies the general opinion as to the reliability or accuracy of the dating. Sample values include:

high the dating is generally considered to be correct.medium the dating is generally considered approximately correct.low the dating is generally considered doubtful but possible.

evidence indicates the nature of the evidence supporting the reliability or accuracy of the dating. Samplevalues include:

internal there is internal evidence to support the dating.external there is external evidence to support the dating.conjecture no specific evidence is available to support the dating.

5 Date:

P5 Fascicule

As a specialisation of the <name> element, the <origPlace> element has a reg attribute which may be used tosupply a regularized form of the place name. Alternatively, the key attribute can be used to provide an identifyingcode or key for the name.Detailed information about the history of a manuscript should be encoded within the <history> elementdiscussed in section 1.1.7. History.The <material> element may be used to tag any specific term used for the material of which a manuscript (orbinding, seal etc.) is composed, wherever the term occurs. ÷Dimensions

The <dimensions> element is used to specify measurements, and is thus a specialised form of the existing TEI<measure> element.

• <dimensions> contains any kind of dimensional specification. Selected attributes:

type indicates which aspect of the object is being measured.

The <extent> (1.1.6.1. Object descriptionmay be used to contain a simple description of the size of a manuscript:

Example 1.51 <extent>2 Most leaves are 140 x 100 mm. but the outer gatherings are about3 5 mm. taller.</extent>

For portability, however, and where conventions differ, it may be preferable to specify the units used, and it mayalso be useful to specify exactly the dimension along which a measurement has been made. For these reasons, thefollowing 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> contains a measurement measured across the spine.


These elements are all members of the measured class, and thus all carry the following attributes:

• <tei.measured> defines the set of attributes common to all elements that contain measurements. Selectedattributes:

units names the units used for the measurement.

scope specifies the applicability of this measurement, where more than one object is being measured.

These elements must be given in the order specified, but groups of them may be repeated as often as necessary,with appropriate values for their attributes to indicate the nature and scope of the measurement concerned. Forexample, in the following case the leaf size and ruled space of the leaves of the manuscript are specified:

Example 1.61 <dimensions type="leaves">2 <height scope="range">157-160</height>3 <width>105</width>4 </dimensions>5 <dimensions type="ruled">6 <height scope="most">90</height>7 <width scope="most">48</width>8 </dimensions>

This indicates that for most leaves of the manuscript being described the ruled space is 90 mm high and 48 mmwide; the leaf size throughout however is between 157 and 160 mm wide, and 105 mm high.Dimensions of the manuscript being described should normally be specified within the <extent> element (part ofthe <physDesc> element discussed in 1.1.6.1. Object description) rather than elsewhere. Dimensions of specificparts of a manuscript, such as accompanying materials, binding, etc. may however be given in other parts of thedescription, as appropriate. ÷Referencestomanuscriptlocations

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

Date: 6

• <locus> defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous)sequence of folio references. Selected attributes:





The <locus> element is used to specify the location in the manuscript occupied by the element within which itappears. If, for example, it is used as the first component of a <msItem> element, or of any of the more specificelements appearing within one (see further section 1.1.5. Intellectual Content below) then it is understood tospecify the location of that item within the manuscript being catalogued.A <locus> element may be used to identify any reference to one or more folios within a manuscript, whereversuch a reference is appropriate. Locations are conventionally specified as a sequence of folio or page numbers, butmay also be a discontinuous list, or a combination of the two. This specification should be given as the contentof the <locus> element, using the conventions appropriate to the cataloguing institution, as in the followingexample:

Example 1.71 <msItem n="1">2 <locus>ff. 1r-24r</locus>3 <title>Apocalypsis beati Ioannis Apostoli</title>4 </msItem>

A normalised form of the location may also be supplied, using special purpose attributes on the <locus> element,as in the following revision of the above example:

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

The targets attribute may be used to associate a <locus> element with one or more other elements in the currentdocument, which should contain either a transcription of the location indicated, or page images of it, as in thefollowing example:

Example 1.91 <decoDesc>2 Most of the main body of the book (up to <locus targets="#txt182">fol. 182v</locus>)3 was painted and decorated in one4 style, having links in style and iconography with the school of5 Maître François, although several of the6 miniatures in this section have been damaged and overpainted at a7 later date (e.g. the figure of Christ on <locus targets="http://www.images.fr#F33R">8 fol. 33r</locus>; the face of the Shepherdess on <locus targets="http://www.images.fr#F59V">fol. 59v</locus>, etc.).9 </decoDesc>

The identifier txt182 in this example is assumed to reference the section of the manuscript ‘up to the fol.182v’which has been transcribed elsewhere in the current document; the references http://www.images.fr#F33R andhttp://www.images.fr#F59V link to images of the indicated pages, presumably held in an image archive.Where more than one foliation has been applied to a manuscript, the <locus> element may specify the folionumber/s applicable in each foliation used, as in the following example:

Example 1.101 

÷Namesofpersons, places, andorganizations

The standard TEI <name> element has attributes type, reg and key, which are used to indicate the type of name(e.g. personal name, placename etc.), to provide a regularised form of the name, and to provide an identifyingcode or key for it respectively.

• <name> contains a proper noun or noun phrase.

7 Date:

P5 Fascicule

type indicates the type of the object which is being named by the phrase.

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

Example 1.111 <name type="place">Villingaholt</name>2 <name type="person">Hoccleve</name>3 <name type="person" key="HOC001">Hoccleve</name>4 <name type="org" reg="Koninklijke Biblioteek">Royal Library</name>

Note that the <name> element is defined as providing information about a name, not a person (or place). In thelast example above, the key attribute is used to associate the name with a more detailed description of the personnamed, provided elsewhere. This more detailed information about a person is provided using the standard TEIelement <person>.

• <person> describes a single participant in a language interaction.

role specifies the role of this participant in the group.

sex specifies the sex of the participant. Legal values are:

m malef femaleu unknown or inapplicable

age specifies the age group to which the participant belongs.

For the Hoccleve example given above to be valid, a <person> element must be provided elsewhere which hasthe value HOCCL1 for its xml:id attribute; the same value will be used as the key attribute of every reference toHoccleve in the manuscript descriptions (however spelled), but there will only be one <person> element with thisidentifier.All the <person> elements referenced by a particular document set should be collected together within a<listPerson> element, located in the TEI Header. This functions as a kind of prosopography for all the peoplereferenced by the set of manuscripts being described, in much the same way as a <listBibl> element in the backmatter may be used to hold bibliographic information for all the works referenced.Similar mechanisms are provided for referencing the names of places and organizations.÷Catchwords, signatures, secundofolio

The <secFol> element is used to discuss any ‘secundo folio’ information recorded for a manuscript as in thefollowing example:

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

÷Heraldry

Heraldic descriptions may appear at various points in the description of Western European early modern andmedieval manuscripts, usually in the context of ownership information, binding descriptions, or detailed accountsof illustrations. If a description contains a detailed account of the heraldic components of a manuscriptindependently considered, this should appear as a distinct paragraph within the appropriate section of the physicaldescription. More usually, however, heraldic descriptions will be cited as short phrases within other parts of therecord. The phrase level element <heraldry> is provided to enable the cataloguer to mark such phrases forfurther subsequent analysis, as in the following example:

Example 1.131 Ownership stamp2 (xvii cent.) on i recto with the arms <heraldry>A bull passant3 within a bordure bezanty, in chief a crescent for difference</heraldry> [Cole],4 crest, and the legend <q>Cole Deum</q>.

÷Formaldefinitions

The additional phrase level elements are formally defined as follows:

Element: dimensionsdimensions =## contains any kind of dimensional specification.element dimensions dimensions.content, dimensions.attributes

Date: 8

dimensions.content


dimensions.content = ( height?, width?, depth? )+dimensions.attributes =tei.global.attributes,tei.measured.attributes,dimensions.attributes.type,[ a:defaultValue = "dimensions" ] attribute TEIform text ?,emptydimensions.attributes.type =## indicates which aspect of the object is being measured.attribute type dimensions.attributes.type.content ?dimensions.attributes.type.content = datatype.Keytei.measured |= dimensionstei.data |= dimensions

Element: heightheight =## contains a measurement measured along the axis parallel to the spine.element height height.content, height.attributesheight.content = textheight.attributes =tei.global.attributes,tei.measured.attributes,[ a:defaultValue = "height" ] attribute TEIform text ?,emptytei.measured |= height

Element: depthdepth =## contains a measurement measured across the spine.element depth depth.content, depth.attributesdepth.content = textdepth.attributes =tei.global.attributes,tei.measured.attributes,[ a:defaultValue = "depth" ] attribute TEIform text ?,emptytei.measured |= depth

Element: widthwidth =## contains a measurement measured along the axis perpendicular to thespine.element width width.content, width.attributeswidth.content = textwidth.attributes =tei.global.attributes,tei.measured.attributes,[ a:defaultValue = "width" ] attribute TEIform text ?,emptytei.measured |= width

Element: locuslocus =## defines a location within a manuscript or manuscript part, usually asa (possibly discontinuous) sequence of folio references.element locus locus.content, locus.attributeslocus.content = textlocus.attributes =

9 Date:

height

width

depth

datatype.Key

dimensions

dimensions

height.content

height

depth.content

depth

width.content

width

locus.content

P5 Fascicule

tei.global.attributes,locus.attributes.scheme,locus.attributes.from,locus.attributes.to,locus.attributes.targets,[ a:defaultValue = "locus" ] attribute TEIform text ?,emptylocus.attributes.scheme =## identifies the foliation scheme in terms of which the location is beingspecifiedattribute scheme locus.attributes.scheme.content ?locus.attributes.scheme.content = datatype.Keylocus.attributes.from =## specifies the starting point of the location in a normalised formattribute from locus.attributes.from.content ?locus.attributes.from.content = datatype.Keylocus.attributes.to =## specifies the end-point of the location in a normalized formattribute to locus.attributes.to.content ?locus.attributes.to.content = datatype.Keylocus.attributes.targets =## supplies a link to one or more page images or## transcriptions of the specified range of foliosattribute targets locus.attributes.targets.content ?locus.attributes.targets.content = datatype.uriListtei.phrase |= locus

Element: origDateorigDate =## contains any form of date, used to identify the## date of origin for a manuscript or manuscript part.element origDate origDate.content, origDate.attributesorigDate.content = textorigDate.attributes =tei.global.attributes,tei.datable.attributes,[ a:defaultValue = "origDate" ] attribute TEIform text ?,emptytei.datable |= origDatetei.phrase |= origDate

Element: origPlaceorigPlace =## contains any form of place name, used to identify the## place of origin for a manuscript or manuscript part.element origPlace origPlace.content, origPlace.attributesorigPlace.content = textorigPlace.attributes =tei.global.attributes,[ a:defaultValue = "origPlace" ] attribute TEIform text ?,emptytei.phrase |= origPlace

Element: materialmaterial =## contains a phrase describing the material of which any part of amanuscript or binding is composed.element material material.content, material.attributes

Date: 10

datatype.Key

datatype.Key

datatype.Key

datatype.uriList

locus

origDate.content

origDate

origDate

origPlace.content

origPlace

material.content


material.content = macro.phraseSeqmaterial.attributes =tei.global.attributes,[ a:defaultValue = "material" ] attribute TEIform text ?,emptytei.phrase |= material

Element: heraldryheraldry =## contains a heraldic formula## or phrase, typically found as part of a blazon, coat of arms, etc.## within a manuscript .element heraldry heraldry.content, heraldry.attributesheraldry.content = macro.phraseSeqheraldry.attributes =tei.global.attributes,[ a:defaultValue = "heraldry" ] attribute TEIform text ?,emptytei.phrase |= heraldry

Element: signaturessignatures =## contains discussion of the leaf or quire signatures found within acodex.element signatures signatures.content, signatures.attributessignatures.content = macro.phraseSeqsignatures.attributes =tei.global.attributes,[ a:defaultValue = "signatures" ] attribute TEIform text ?,emptytei.phrase |= signatures

Element: secFolsecFol =## The word or words that a cataloguer, typically medieval but possiblymodern as well, might take from a fixed point in all the codices he isdescribing (the beginning of the second leaf, the beginning of the secondcolumn, the beginning of the penultimate leaf, the end of the penultimateleaf, and so on) in order to provide a unique identifier to the particularcodex.element secFol secFol.content, secFol.attributessecFol.content = macro.phraseSeqsecFol.attributes =tei.global.attributes,[ a:defaultValue = "secFol" ] attribute TEIform text ?,emptytei.phrase |= secFol

Element: watermarkwatermark =## contains a word or phrase describing a## watermark or similar device.element watermark watermark.content, watermark.attributeswatermark.content = macro.phraseSeqwatermark.attributes =tei.global.attributes,[ a:defaultValue = "watermark" ] attribute TEIform text ?,emptytei.phrase |= watermark

11 Date:

macro.phraseSeq

material

heraldry.content

macro.phraseSeq

heraldry

signatures.content

macro.phraseSeq

signatures

secFol.content

macro.phraseSeq

secFol

watermark.content

macro.phraseSeq

watermark

P5 Fascicule

÷TheManuscriptIdentifier

The <msIdentifier> element is intended to provide an unambiguous means of identification for particularmanuscript items within a collection.

• <msIdentifier> contains the information required to identify a given manuscript or manuscript part uniquelywithin its holding institution.


A manuscript identifier typically has two parts, the first being its catalogued location, and the second the nameused for it within that location. The location may be specified as a collection, located within a repository, formingpart of an institution whose primary geographic location is within a city, itself located within a region or country,or both. A manuscript may have alternative identifiers additional to the one currently used, including informalnames or old shelfmarks which are retained even after they have been officially superceded. All this informationneeds to be included.The ‘catalogued location’ of a manuscript is the place of ownership. A manuscript’s exact physical location mayoccasionally be different: for example, at Cambridge University, manuscripts owned by different colleges may bephysically located within the Cambridge University Library. In such cases, the college location should be specifiedin the manuscript identifier. Similarly, a holding institution may wish to specify additional and more precisephysical location information within the <adminInfo> element discussed in section 1.1.8.1. AdministrativeInformation below.The following elements are available within <msIdentifier> to identify the physical location of a manuscript:

• <country> in an address, gives the name of the nation, country, colony, or commonwealth; in a place namegiven as a hierarchy of geo-political units, the country is larger or administratively superior to the regionand smaller than the bloc.


• <region> in an address, contains the state, province, county or region name; in a place name given asa hierarchy of geo-political units, the region is larger or administratively superior to the settlement andsmaller or administratively less important than the country.


• <settlement> contains the name of the smallest component of a place name expressed as a hierarchy ofgeo-political or administrative units as in Rochester, New York; Glasgow, Scotland.


• <institution> contains the name of an organization, such as a University or Library, within which amanuscript repository is located.


• <repository> contains the name of a repository (usually a distinct physical building) within whichmanuscripts are stored, forming part of an institution.


• <collection> contains the name of a collection of manuscripts, not necessarily located within a singlerepository.


These elements are all structurally equivalent to the standard TEI <name> element with an appropriate value for itstype attribute; however the use of this ‘syntactic sugar’ enables the model for <msIdentifier> to be constrainedrather more tightly than would otherwise be possible. Specifically, only one of each of the elements listed abovemay appear within the <msIdentifier> and if present, they must appear in the order given.These elements are all also members of the standard TEI attribute class names, which means that they can allbear attributes such as reg to supply a regularized form of a name, or key to specify a database or similar uniquekey for it, as further documented in the description of this class.The distinction between <institution> and <repository> may not always exist, nor is it possible here topropose use of one element over the other; presumably local decisions will apply as to which element seems moreappropriate.The following elements are used within <msIdentifier> to provide different ways of identifying the manuscript:

Date: 12

• <idno> supplies any standard or non-standard number used to identify a bibliographic item.

type categorizes the number, for example as an ISBN or other standard series.

• <altIdentifier> contains an alternative or former structured identifier used for a manuscript, such as a formercatalogue number.


• <altName> contains any form of unstructured alternative name used for a manuscript, such as an ocellusnominum, or nickname.

type further characterizes the alternative name, for example as former shelfmark, nickname, etc.

Major manuscript repositories will usually have a preferred form of citation for manuscript shelfmarks, includingstrict rules about punctuation, spacing, abbreviation, etc., which should be adhered to. Where such a format alsocontains information which might additionally be supplied as a distinct subcomponent of the <msIdentifier>,for example a collection or repository name, the cataloguer must decide whether or not to include this informationin both locations. For example,

Example 1.261 <collection>fr.</collection>2 <idno>2810</idno>

may be considered as gratuitous, extraneous markup by cataloguers at the Bibliothèque nationale de France, wherethe concept of

Example 1.271 <idno>fr. 2810</idno>

as a unit may be felt to better determine the identity of the manuscript in question. Other examples are theRawlinson collection in the Bodleian Library, or the Ellesmere collection in the Huntington Library, whereseparate tagging of "Rawlinson" and "Ellesmere" as collections would lead users to incorrect forms of citation; inthe latter case correct markup would be:

Example 1.281 <msIdentifier>2 <country>USA</country>3 <region>California</region>4 <settlement>San Marino</settlement>5 <repository>Huntington Library</repository>6 <idno>MS.El.26.C.9</idno>7 <altName>The Ellesmere Chaucer</altName>8 </msIdentifier>

Here the name of the collection is not explicitly tagged, since it is implicit in the standard form of the manuscriptshelf mark. In many cases, however, such as the following example, a collection name is useful:

Example 1.291 <msIdentifier>2 <country>USA</country>3 <region>New Jersey</region>4 <settlement>Princeton</settlement>5 <institution>Princeton University</institution>6 <repository>Princeton University Library</repository>7 <collection>Scheide Library</collection>8 <idno>MS 71</idno>9 <altName>Blickling Homiliary</altName>

10 </msIdentifier>

In the previous two examples, <altName> was used to provide a common name, other than the shelfmark, bywhich a manuscript is known. Any number of these elements may also be used to supply alternative names usedfor the manuscript, as in the following example, where the repository in question only has one manuscript (or onlyone of any significance), which has no call number as such but is known under multiple names:

13 Date:

P5 Fascicule

Example 1.301 <msIdentifier>2 <settlement>Rossano</settlement>3 <repository lang="it">Biblioteca arcivescovile</repository>4 <idno/>5 <altName lang="la" type="nick">Codex Rossanensis</altName>6 <altName lang="la" type="nick">Codex aureus</altName>7 <altName lang="la" type="nick">Codex purpureus</altName>8 <altName lang="en" type="gloss">The Rossano Gospels</altName>9 </msIdentifier>

Note the use of the globally available xml:lang attribute above to specify the language in which the content of anelement is supplied. This is a standard TEI facility, which the cataloguer may find useful in certain environments(for example, when compiling a single catalogue from a variety of originally different sources), and which maysafely be ignored in others.Where manuscripts have moved from one institution to another, or within the same institution, it may often beuseful to supply a former identifier, with a detailed structure similar to that of the <msIdentifier> itself. Forexample, the following example shows a manuscript which had shelfmark II-M-5 in the collection of the Duquede Osuna, but which now has the shelfmark MS 10237 in the National Library in Madrid:

Example 1.311 <msIdentifier>2 <settlement>Madrid</settlement>3 <repository>Biblioteca Nacional</repository>4 <idno>MS 10237</idno>5 <altIdentifier>6 <region>Andalucia</region>7 <settlement>Osuna</settlement>8 <repository>Duque de Osuna</repository>9 <idno>II-M-5</idno>

10 </altIdentifier>11 </msIdentifier>

<altIdentifier> can also be used to supply information on former shelfmarks, holding institutions etc. Suchinformation would, however, normally be dealt with under <history>, except in cases where a manuscript islikely still to be referred to or known by its former identifier. An institution may, for example, have changed itscall number system but wishes to retain a record of the earlier call number, especially where the manuscript hasbeen cited in print with its previous number:

Example 1.321 <msIdentifier>2 <settlement>Berkeley</settlement>3 <institution>University of California</institution>4 <repository>Bancroft Library</repository>5 <idno>UCB 16</idno>6 <altIdentifier>7 <idno>2MS BS1145 I8</idno>8 </altIdentifier>9 </msIdentifier>

Where (as in this example) no repository is specified for the <altIdentifier>, it is assumed to be thesame as that of the parent <msIdentifier>. Where the holding institution has only one preferred form ofcitation but wishes to retain the other for internal administrative purposes, the secondary could be given within<altIdentifier> with an appropriate value on the type attribute:

Example 1.331 <msIdentifier>2 <settlement>Oxford</settlement>3 <repository>Bodleian Library</repository>4 <idno>MS. Bodley 406</idno>5 <altIdentifier type="internal">6 <idno>S.C. 2297</idno>7 </altIdentifier>8 </msIdentifier>

Date: 14

It might, however, be preferable to include such information within the <adminInfo> element discussed in section1.1.8.1. Administrative Information below.The <msIdentifier> element and its constituents are formally defined as follows:

Element: msIdentifiermsIdentifier =## contains the information required to identify## a given manuscript or manuscript part uniquely within its holdinginstitution.element msIdentifier msIdentifier.content, msIdentifier.attributesmsIdentifier.content =country?,region?,settlement,institution?,repository,collection?,idno,( altIdentifier | altName )*msIdentifier.attributes =tei.global.attributes,[ a:defaultValue = "msIdentifier" ] attribute TEIform text ?,emptytei.biblPart |= msIdentifier

Element: institutioninstitution =## contains the name of an## organization, such as a University or Library, within which a## manuscript repository is located.element institution institution.content, institution.attributesinstitution.content = textinstitution.attributes =tei.global.attributes,tei.names.attributes,[ a:defaultValue = "institution" ] attribute TEIform text ?,emptytei.names |= institution

Element: repositoryrepository =## contains the name of a repository (usually## a distinct physical building) within which manuscripts are stored,forming part## of an institution.element repository repository.content, repository.attributesrepository.content = textrepository.attributes =tei.global.attributes,tei.names.attributes,[ a:defaultValue = "repository" ] attribute TEIform text ?,emptytei.names |= repository

Element: collectioncollection =## contains the name of a collection of## manuscripts, not necessarily located within a single repository.

15 Date:

msIdentifier.content

country

region

settlement

institution

repository

collection

idno

altIdentifier

altName

msIdentifier

institution.content

institution

repository.content

repository

P5 Fascicule

element collection collection.content, collection.attributescollection.content = textcollection.attributes =tei.global.attributes,tei.names.attributes,[ a:defaultValue = "collection" ] attribute TEIform text ?,emptytei.names |= collection

Element: altIdentifieraltIdentifier =## contains an alternative or former structured identifier used for## a manuscript, such as a former catalogue number.element altIdentifier altIdentifier.content, altIdentifier.attributesaltIdentifier.content =country?, region?, settlement?, institution?, repository?, collection?,idnoaltIdentifier.attributes =tei.global.attributes,tei.typed.attributes,[ a:defaultValue = "altIdentifier" ] attribute TEIform text ?,emptytei.typed |= altIdentifier

Element: altNamealtName =## contains any form of unstructured alternative## name used for## a manuscript, such as an ocellus## nominum, or nickname.element altName altName.content, altName.attributesaltName.content = textaltName.attributes =tei.global.attributes,altName.attributes.type,[ a:defaultValue = "altName" ] attribute TEIform text ?,emptyaltName.attributes.type =## further characterizes the alternative name, for example as## former shelfmark, nickname, etc.attribute type altName.attributes.type.content ?altName.attributes.type.content = datatype.Key

÷TheManuscriptHeading

Historically, the briefest possible meaningful description of a manuscript consists of no more than a title, e.g.‘Polychronicon’. This will often have been enough to identify a manuscript in a small collection because theidentity of the author is implicit. Where a title does not imply the author, and thus is insufficient to identify the maintext of a manuscript, the author has to be stated explicitly (e.g. ‘Augustinus, Sermones’, ‘Cicero, Letters’). Manyinventories of manuscripts consist of no more than the author and title, with some form of copy-specific identifier,such as a shelfmark or secundo folio reference (e.g. ‘Arch. B. 3. 2: Evangelium Matthei cum glossa’, ‘126.Isidori Originum libri octo’, ‘Biblia Hieronimi, 2o fo. opus est’). Information on date and place of writing willsometimes also be included. The standard TEI element <head> element can be used to supply a brief descriptionof this kind, supplying in one place a minimum of essential information, such as might be displayed or printed asthe heading of a full catalogue description, such as the following:

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

Date: 16

collection.content

collection

altIdentifier.content

country

region

settlement

institution

repository

collection

idno

altIdentifier

altName.content

datatype.Key

Any phrase-level elements, such as <name>, <title> and <date>, can also be used within a <head> element,but for more structured markup the specialised elements described here, <msContents>, <history> etc., shouldbe used instead.It is permissible to include multiple <head> elements in the case of a composite manuscript, as in the followingexample:

Example 1.411 <msDescription>2 <msIdentifier>3 <settlement>Sankt Gallen</settlement>4 <repository>Stiftsbibliothek</repository>5 <idno>Codex 658</idno>6 </msIdentifier>7 <head n="1">Robertus Monachus: Geschichte des 1.8 Kreuzzugs (bebildert)</head>9 <head n="2">Ottokar von Steiermark:

10 Österreichische Reimchronik: Fall Akkons.</head>11 

13 </msDescription>

÷IntellectualContent

The <msContents> element is used to describe the intellectual content of a manuscript or manuscript part. Itcomprises either a series of informal prose paragraphs or a series of more structured <msItem> elements, each ofwhich provides a more detailed description of a single item contained within the manuscript.

• <msContents> describes the intellectual content of a manuscript or manuscript part either as a series ofparagraphs or as a series of structured manuscript items.



• <msItem> describes an individual work or item within the intellectual content of a manuscript or manuscriptpart.


defective indicates whether the item being described is defective, i.e. incomplete.

In the simplest case, only a brief description may be provided, as in the following example:

Example 1.421 <msContents>2 A collection of Lollard sermons3 </msContents>

This description may of course be expanded to include any of the TEI elements generally available within a element, such as <bibl> to mark bibliographic descriptions, or <list> for a list. More usually however, eachindividual work within a manuscript will be given its own description, using the <msItem> element described inthe next section, as in the following example:

Example 1.431 <msContents>2 <msItem n="1">3 <locus>fols. 5r -7v</locus>4 <title>An ABC</title>5 <bibl>6 <title>IMEV</title>7 <biblScope>239</biblScope>8 </bibl>9 </msItem>

10 <msItem n="2">11 <locus>fols. 7v -8v</locus>12 <title lang="fr">Lenvoy de Chaucer a Scogan</title>13 <bibl>14 <title>IMEV</title>

17 Date:

P5 Fascicule

15 <biblScope>3747</biblScope>16 </bibl>17 </msItem>18 <msItem n="3">19 <locus>fol. 8v</locus>20 <title>Truth</title>21 <bibl>22 <title>IMEV</title>23 <biblScope>809</biblScope>24 </bibl>25 </msItem>26 <msItem n="4">27 <locus>fols. 8v-10v</locus>28 <title>Birds Praise of Love</title>29 <bibl>30 <title>IMEV</title>31 <biblScope>1506</biblScope>32 </bibl>33 </msItem>34 <msItem n="5">35 <locus>fols. 10v -11v</locus>36 <title lang="la">De amico ad amicam</title>37 <title lang="la">Responcio</title>38 <bibl>39 <title>IMEV</title>40 <biblScope>16 & 19</biblScope>41 </bibl>42 </msItem>43 <msItem n="6">44 <locus>fols. 14r-126v</locus>45 <title>Troilus and Criseyde</title>46 <note>Bk. 1:71-Bk. 5:1701, with additional losses due to47 mutilation throughout</note>48 </msItem>49 </msContents>

÷The<msItem>element

Any combination of the elements described in this section may be used to record information about individualitems within the intellectual content of a manuscript or manuscript part. Each discrete item should be encodedwithin a distinct <msItem> element, and may be classified using the class attribute.The <msItem> element may not contain any untagged running text. Instead, it contains the following elements,which must be supplied in the following order:

• <author> in a bibliographic reference, contains the name of the author(s), personal or corporate, of a work;the primary statement of responsibility for any bibliographic item.


• <respStmt> supplies a statement of responsibility for someone responsible for the intellectual content of atext, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice ordo not apply.


• <title> contains the title of a work, whether article, book, journal, or series, including any alternative titlesor subtitles.

level indicates whether this is the title of an article, book, journal, series, or unpublished material. Legalvalues are:

a analytic title (article, poem, or other item published as part of a larger item)m monographic title (book, collection, or other item published as a distinct item, including single

volumes of multi-volume works)j journal titles series title

Date: 18

u title of unpublished material (including theses and dissertations unless published by a commercialpress)

type classifies the title according to some convenient typology. Sample values include:

main main titlesubordinate subtitle, title of partparallel alternate title, often in another language, by which the work is also knownabbreviated abbreviated form of title

• <rubric> contains the text of any rubric or heading attached to a particular manuscript item, that is, a stringof words whereby a manuscript signals a text division (e.g. beginning, book, chapter, end) which is in someway set off from the text itself, usually in red ink,or by use of different size or type of script, lining, or othersuch visual device. . Selected attributes:

type specifies the type of rubric, e.g. whether it is at the start or end of the item.

• <incipit> contains the text of any incipit attached to a particular manuscript item, that is the opening wordsof a text, frequently used as a form of identifier for it; it may be preceded by one or more rubrics, and maybe defective.

Selected attributes:

defective indicates whether the incipit as given is defective, i.e. incomplete.

type specifies the type of incipit, e.g. whether it introduces a work, is biblical, legal, etc.

• <explicit> contains the text of any explicit attached to a particular manuscript item, that is, the closingwords of a text or a section of a text, sometimes used as a kind of title, possibly followed by one or morerubrics or colophons.

Selected attributes:

defective indicates whether the explicit as given is defective, i.e. incomplete.

type specifies the type of explicit, e.g. whether it is a formal closing for the work.

• <colophon> contains the text of any colophon attached to a particular manuscript item: that is, aninscription, usually found at a break point such as the end of a text or codex, usually containing informationabout the production of the manuscript, such as the name of the scribe, the date and place of the copying,the person who commissioned the copying, etc.


• <decoNote> contains a note describing either a decorative component of a manuscript, or a fairlyhomogenous class of such components.

type specifies the kind of decorative feature being described

subtype supplies a further sub-categorization of the value specified by the type attribute.

• <listBibl> contains a list of bibliographic citations of any kind.


• <q> contains a quotation or apparent quotation — a representation of speech or thought marked as beingquoted from someone else (whether in fact quoted or not); in narrative, the words are usually those of of acharacter or speaker; in dictionaries, q may be used to mark real or contrived examples of usage.

type may be used to indicate whether the quoted matter is spoken or thought, or to characterize it morefinely. Sample values include:

spoken representation of direct speech, usually marked by quotation marks.thought representation of thought, e.g. internal monologue.

direct may be used to indicate whether the quoted matter is regarded as direct or indirect speech. Legalvalues are:

y speech or thought is represented directly.n speech or thought is represented indirectly, e.g. by use of a marked verbal aspect.unknown no claim is made.

who identifies the speaker of a piece of direct speech.

• <bibl> contains a loosely-structured bibliographic citation of which the sub-components may or may notbe explicitly tagged.

19 Date:

P5 Fascicule


• <filiation> contains information concerning the manuscript’s filiation, i.e. its relationship to other survivingmanuscripts of the same text, its protographs, antigraphs and apographs.


• <note> contains a note or annotation.

type describes the type of note.

resp indicates who is responsible for the annotation: author, editor, translator, etc. Sample values include:

auth note originated with the author of the text.ed note added by the editor of the text.comp note added by the compiler of a collection.tr note added by the translator of a text.transcr note added by the transcriber of a text into electronic form.

place indicates where the note appears in the source text. Sample values include:

foot note appears at foot of page.end note appears at end of chapter or volume.inline note appears as a marked paragraph in the body of the text.left note appears in left margin.right note appears in right margin.interlinear note appears between lines of the text.app note appears in the apparatus at the foot of the page.

anchored indicates whether the copy text shows the exact place of reference for the note. Legal values are:

true copy text indicates the place of attachment for the note.false copy text indicates no place of attachment for the note.

target indicates the point of attachment of a note, or the beginning of the span to which the note is attached.

targetEnd points to the end of the span to which the note is attached, if the note is not embedded in thetext at that point.

• <textLang> describes the languages and writing systems used by a manuscript (as opposed to itsdescription, which is described in the langUsage element)

langKey supplies a code which identifies the chief language used in the manuscript.

otherLangs one or more codes identifying any other languages used in the manuscript.

• <msItem> describes an individual work or item within the intellectual content of a manuscript or manuscriptpart.



All the above elements may be repeated as often as appropriate within a single <msItem>, with the exception of<rubric>, <incipit>, and <explicit>, each of which can appear only once.The <title> element should be used to supply a regularized form of the item’s title, quite distinct from any rubricor incipit quoted from the manuscript. If the item concerned has a standardized or ‘uniform’ title, then this shouldalways be the form preferred as content of the <title> element. If no uniform title exists, or none has been yetidentified, then the type attribute on the <title> should be given the value supplied. Abbreviated ‘titles’ suchas ‘IMEV 3747’ may be tagged using the standard TEI <ref> element, optionally including a pointer to a fullerbibliographic description in a bibliography elsewhere, as further discussed in section 1.1.8.1.1. Record History.If supplied, the <author> element should generally contain the normalised form of an author’s name, irrespectiveof how (or whether) this form of the name is cited in the manuscript. If it is desired to retain the form of theauthor’s name as given in the manuscript, this may be tagged as a distinct <name> element, nested within the<author> element with the normalized form of the name on its reg attribute. Alternatively, the normalized formof the name may be supplied as the value of a reg attribute on the <author> element. If value is supplied for eitherreg or key attributes, then the content of the <author> element is assumed to be a standardized form of name.Note that the key attribute should be used, as on names in general, to specify the identifier of a <person> elementcarrying full details of the person concerned (see further 1.1.2.4. Names of persons, places, and organizations).Each element within <msItem> has the same substructure, containing any mixture of phrase-level elements andplain text. If a <locus> element is included, in order to specify the location of the component, then it should begiven at the start of that element, as in the following example:

Date: 20

Example 1.441 <msContents>2 <msItem>3 <locus>f. 1-223</locus>4 <author>Radulphus Flaviacensis</author>5 <title>Expositio super Leviticum </title>6 <incipit>7 <locus>f. 1</locus>8 Forte Hervei monachi</incipit>9 <explicit>

10 <locus>f. 223v</locus>11 Benedictio salis et aquae</explicit>12 <note>cf. <bibl>Stegmüller, RB 7093</bibl>13 </note>14 </msItem>15 </msContents>

In the following example, standard TEI editorial elements have been used to mark the transcription of abbrevia-tions etc. present in the original:

Example 1.451 <msItem defective="true">2 <locus>ff. 1r-24v</locus>3 <title type="uniform">ágrip af Noregs konunga s&oogon;gum</title>4 <incipit defective="true">regi oc h<expan>ann</expan> seti ho<gap reason="illegible" extent="7"/>5 <lb/>sc heim se<expan>m</expan> þio</incipit>6 <explicit defective="true">h<expan>on</expan> hev<expan>er</expan>7 <expan>oc</expan> þa buit hesta .ij. <lb/>annan viþ fé en8 h<expan>on</expan>o<expan>m</expan> annan til reiþ<expan>ar</expan>9 </explicit>

10 <listBibl>11 <bibl>12 <ref target="#Agr1834">Brudstykke af en gammel norsk Kongesaga, 1834</ref>13 </bibl>14 <bibl>15 <ref target="#FMS10">Fornmanna Sögur X</ref>, pp. 377-421</bibl>16 <bibl>17 <ref target="#STUAGNL2">Ágrip 1880</ref>18 </bibl>19 <bibl>20 <ref target="#ASB18">Ágrip 1929</ref>21 </bibl>22 <bibl>23 <ref target="#IF29">Ágrip, ÍF XXIX</ref>24 </bibl>25 <bibl>26 <ref target="#Agr1995">Ágrip 1995</ref>27 </bibl>28 </listBibl>29 </msItem>

As indicated above, a manuscript item may itself contain further nested items, for example where a title ordescription is supplied for a group of works each of which also has its own rubric, as in the following example:

Example 1.461 <msItem>2 <locus>ff. 17v, 21v, 34</locus>3 <title>Charms numbered 1-3, consisting of4 variously formed crosses with inscribed circles</title>5 <msItem>6 <locus>f. 17v</locus>7 <rubric>Contra inimicos, 1</rubric>8 <q>Si quis hoc signum super se portat nequid capi ab9 inimico;</q>

10 </msItem>

21 Date:

P5 Fascicule

11 <msItem>12 <locus>f. 21v</locus>13 <rubric>Contra mortem subitam, 2</rubric>14 <q>Qui hoc signum super se portat sine confessione non15 morietur;</q>16 </msItem>17 <msItem>18 <locus>f. 34</locus>19 <rubric>Pro victoria, 3</rubric>20 <q>Hoc signum misit deus Regi Tedeon; qui cum isto pugnat21 victoriam habebit;</q>22 </msItem>23 </msItem>

One or more text classification or text-type codes may be specified, either for the whole of a <msContents>element, or for one or more of its constituent <msItem> elements, using the class attribute as specified above:

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

The value of the class attribute should specify the identifier used for the appropriate classification within a<taxonomy> element, defined in the <classDecl> element of the TEI Header («HD55»), as shown here:

Example 1.481 <classDecl>2 <taxonomy>3 4 <category id="law">5 <catDesc>Law</catDesc>6 </category>7 

9 </taxonomy>10 </classDecl>

÷Languagesandscripts

The <textLang> element should be used to provide information about the languages used within a manuscriptitem. It may take the form of a simple note, as in the following example:

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

Where, for validation and indexing purposes, it is thought convenient to add keywords identifying the particularlanguages used, the langKey attribute may be used, as in the following example:

Example 1.501 <textLang langKey="#OCS">Old Church Slavonic, written in Cyrillic script.</textLang>

For this example to be valid, the identifier OCS must also be predefined as the value of the xml:id attribute on a<language> element in the TEI header associated with this description.

Example 1.511 <langUsage>2 <language ident="OCS">Old Church Slavonic, written in Cyrillic script.</language>3 

5 </langUsage>

Date: 22

A manuscript item will often contain material in more than one language. The langKey attribute should be usedonly for the chief language. Other languages used may be specified using the otherLangs attribute as in thefollowing example:

Example 1.521 <textLang langKey="#OCS" otherLangs="#RUS #HEL">2 Mostly Old Church Slavonic, with some Russian and Greek material</textLang>

Since Old Church Slavonic may be written in either Cyrillic or Glagolitic scripts, and even occasionally in bothwithin the same manuscript, it might be preferable to define identifiers which make the distinction explicit. Insuch a case, the following <textLang> element might be preferred:

Example 1.531 <textLang otherLangs="#OCS-CYR #OCS-GLA">Old Church Slavonic, written in2 Cyrillic and Glagolitic scripts.</textLang>

and the following declarations might then be supplied in the <langUsage> element of the associated TEI Header:

Example 1.541 <langUsage>2 <language ident="OCS-CYR">3 Old Church Slavonic, written in Cyrillic script.</language>4 <language ident="OCS-GLA">5 Old Church Slavonic, written in Glagolitic script.</language>6 

8 </langUsage>

Note that the <language> element defines a particular combination of human language and writing system. Onlyone <language> element may be supplied for each such combination. Standard TEI practice also allows thiselement to be referenced by any element using the global xml:lang attribute in order to specify the languageapplicable to the content of that element. For example, assuming that <language> elements have been definedwith the identifiers FRA (for French), LAT (for Latin), and DEU (for German), a manuscript description written inFrench which specifies that a particular manuscript contains predominantly German but also some Latin material,might have a <textLang> element like the following:

Example 1.551 <textLang lang="fr" langKey="#de" otherLangs="#la">2 allemand et latin</textLang>

÷Formaldefinition

The <msContents> element and its constituents are formally defined as follows:

Element: colophoncolophon =## contains the text of any colophon## attached to a particular manuscript item: that is, an inscription,## usually found at a break point such as the end of a text or codex,## usually containing information about the production of the manuscript,## such as the name of the scribe, the date and place of the copying, the## person who commissioned the copying, etc.element colophon colophon.content, colophon.attributescolophon.content = macro.phraseSeqcolophon.attributes =tei.global.attributes,[ a:defaultValue = "colophon" ] attribute TEIform text ?,empty

Element: explicitexplicit =## contains the text of any explicit attached## to a particular manuscript item, that is, the closing words of a textor a section of

23 Date:

colophon.content

macro.phraseSeq

P5 Fascicule

## a text, sometimes used as a kind of title, possibly followed by one ormore rubrics or colophons.##element explicit explicit.content, explicit.attributesexplicit.content = macro.phraseSeqexplicit.attributes =tei.global.attributes,explicit.attributes.defective,explicit.attributes.type,[ a:defaultValue = "explicit" ] attribute TEIform text ?,emptyexplicit.attributes.defective =## indicates whether the explicit as given is defective, i.e. incomplete.attribute defective explicit.attributes.defective.content ?explicit.attributes.defective.content = datatype.UBooleanexplicit.attributes.type =## specifies the type of explicit, e.g. whether it is a formal closingfor the## work.attribute type explicit.attributes.type.content ?explicit.attributes.type.content = datatype.Key

Element: incipitincipit =## contains the text of any incipit## attached to a particular manuscript item, that is the opening words of## a text, frequently used as a form of identifier for it; it may be## preceded by one or more rubrics, and may be defective.element incipit incipit.content, incipit.attributesincipit.content = macro.phraseSeqincipit.attributes =tei.global.attributes,incipit.attributes.defective,incipit.attributes.type,[ a:defaultValue = "incipit" ] attribute TEIform text ?,emptyincipit.attributes.defective =## indicates whether the incipit as given is defective, i.e. incomplete.attribute defective incipit.attributes.defective.content ?incipit.attributes.defective.content = datatype.UBooleanincipit.attributes.type =## specifies the type of incipit, e.g. whether it introduces a work,## is biblical, legal, etc.attribute type incipit.attributes.type.content ?incipit.attributes.type.content = datatype.Key

Element: msContentsmsContents =## describes the intellectual content of a## manuscript or manuscript part either as a series of paragraphs or as a## series of structured manuscript items.element msContents msContents.content, msContents.attributesmsContents.content = tei.paragraph+ | ( summary?, msItem+ )msContents.attributes =tei.global.attributes,msContents.attributes.class,msContents.attributes.defective,

Date: 24

explicit.content

macro.phraseSeq

datatype.UBoolean

datatype.Key

incipit.content

macro.phraseSeq

datatype.UBoolean

datatype.Key

msContents.content

tei.paragraph

summary

msItem


[ a:defaultValue = "msContents" ] attribute TEIform text ?,emptymsContents.attributes.class =## identifies the text types or classifications applicable to this## itemattribute class msContents.attributes.class.content ?msContents.attributes.class.content = datatype.uriListmsContents.attributes.defective =## indicates whether the work contained is defective, i.e. incomplete.attribute defective msContents.attributes.defective.content ?msContents.attributes.defective.content = datatype.UBoolean

Element: msItemmsItem =## describes an individual work or item within the intellectual## content of a manuscript or manuscript part.element msItem msItem.content, msItem.attributesmsItem.content =locus?,(tei.paragraph+| (author*,respStmt*,title*,rubric?,incipit?,explicit?,colophon*,decoNote*,langUsage*,listBibl*,q*,bibl*,filiation*,note*,textLang?,msItem*))msItem.attributes =tei.global.attributes,msItem.attributes.class,msItem.attributes.defective,[ a:defaultValue = "msItem" ] attribute TEIform text ?,emptymsItem.attributes.class =## identifies the text types or classifications applicable to this## itemattribute class msItem.attributes.class.content ?msItem.attributes.class.content = datatype.uriListmsItem.attributes.defective =## indicates whether the item being described## is defective, i.e. incomplete.attribute defective msItem.attributes.defective.content ?msItem.attributes.defective.content = datatype.UBoolean

25 Date:

datatype.uriList

datatype.UBoolean

msItem.content

locus

tei.paragraph

author

respStmt

title

rubric

incipit

explicit

colophon

decoNote

langUsage

listBibl

q

bibl

filiation

note

textLang

msItem

datatype.uriList

datatype.UBoolean

P5 Fascicule

Element: rubricrubric =## contains the text of any rubric or heading attached to a particularmanuscript item, that is, a string of words whereby a## manuscript signals a text division (e.g. beginning, book, chapter,end)## which is in some way set off from the text itself, usually in red ink,orby use of different size or type of script, lining, or other such visualdevice.## .element rubric rubric.content, rubric.attributesrubric.content = macro.phraseSeqrubric.attributes =tei.global.attributes,rubric.attributes.type,[ a:defaultValue = "rubric" ] attribute TEIform text ?,emptyrubric.attributes.type =## specifies the type of rubric, e.g. whether it is at the start or endof## the item.attribute type rubric.attributes.type.content ?rubric.attributes.type.content = datatype.Key

Element: summarysummary =## contains a brief summary of the## intellectual content of an item, provided by the cataloguerelement summary summary.content, summary.attributessummary.content = macro.phraseSeqsummary.attributes =tei.global.attributes,[ a:defaultValue = "summary" ] attribute TEIform text ?,empty

Element: filiationfiliation =## contains information concerning the manuscript’s filiation, i.e.its relationship to other surviving manuscripts of the same text, itsprotographs, antigraphs and apographs.element filiation filiation.content, filiation.attributesfiliation.content = macro.specialParafiliation.attributes =tei.global.attributes,tei.typed.attributes,[ a:defaultValue = "filiation" ] attribute TEIform text ?,emptytei.typed |= filiation

Element: textLangtextLang =## describes the languages and writing systems used by a## manuscript (as opposed to its description, which is described in thelangUsage element)element textLang textLang.content, textLang.attributestextLang.content = macro.phraseSeqtextLang.attributes =tei.global.attributes,

Date: 26

rubric.content

macro.phraseSeq

datatype.Key

summary.content

macro.phraseSeq

filiation.content

macro.specialPara

filiation

textLang.content

macro.phraseSeq

textLang.attributes.langKey,textLang.attributes.otherLangs,[ a:defaultValue = "textLang" ] attribute TEIform text ?,emptytextLang.attributes.langKey =## supplies a code which identifies the chief language used in themanuscript.attribute langKey textLang.attributes.langKey.content ?textLang.attributes.langKey.content = datatype.uritextLang.attributes.otherLangs =## one or more codes identifying any other languages used in themanuscript.attribute otherLangs textLang.attributes.otherLangs.content ?textLang.attributes.otherLangs.content = datatype.uriList

÷PhysicalDescription

Under the general heading of ‘physical description’ we subsume a large number of different aspects generallyregarded as useful in the description of a given manuscript. These include aspects of the form, support, extent,and quire structure of the manuscript object (1.1.6.1. Object description); aspects of the writing, such as the wayit is laid out on the page, the styles of writing and any musical notation employed (1.1.6.2. Writing, Decorationand other Notations); discussion of decorative features of the manuscript, of any paratextual features such aspagination, and of any annotations (1.1.6.2.2. Decoration); discussion of its binding and state of repair (1.1.6.2.4.Additions and marginalia).Most manuscript descriptions touch on several of these categories of information though few include them all, andnot all distinguish them as clearly as we propose here. In particular, it is often the case that an existing descriptionwill include information for which we propose distinct elements within a single paragraph, or even sentence. Theencoder must then decide whether to rewrite the description using the structure proposed here, or to retain theexisting prose, marked up simply as a series of elements, directly within the <physDesc> element.The <physDesc> element may thus be used in either of two distinct ways: it may contain a series of paragraphsaddressing topics listed above and similar ones; or it may act as a container for any choice of the more specialisedelements described in the remainder of this section, each of which itself contains a series of paragraphs, and mayalso have more specific attributes. Note that the two ways should, indeed may, not be combined within the samedescription. ÷Objectdescription

The <objectDesc> element is used to group together those parts of the physical description which relatespecifically to the inscribed material (typically, pages of a manuscript), their format, constitution, layout, etc.Its form attribute is used to indicate the specific type of object being described, for example, as a codex, fragment,roll, etc. It has two parts: a description of the support, i.e. the physical carrier on which the writing of themanuscript is inscribed; and a description of one or more layouts, i.e. the way that the writing is organized on thephysical carrier.Taking these in turn, the description of the support is tagged using the following elements, each of which isdiscussed in more detail below:

• <supportDesc> groups elements describing the physical support for the written part of a manuscript.

material a short project-defined name for the material composing the majority of the support Values are:

paper Paperparch Parchmentmixed mixed

• <support> contains a description of the materials etc. which make up the physical support for the writtenpart of a manuscript.


• <extent> describes the approximate size of the electronic text as stored on some carrier medium, specifiedin any convenient units.


• <collation> contains a description of how the leaves or bifolia are physically arranged.


• <foliation> describes the numbering system or systems used to count the leaves or pages in a codex.

27 Date:

datatype.uri

datatype.uriList

P5 Fascicule


• <condition> contains a description of the physical condition of the manuscript.


Each of these elements contains paragraphs relating to the topic concerned. Within the paragraphs, phrase-levelelements (in particular those discussed above at 1.1.2. Phrase-level elements), may be used to tag specific termsof interest if so desired.

Example 1.671 <objectDesc form="codex">2 <supportDesc>3 Mostly <material>paper</material>, with watermarks4 <watermark>unicorn</watermark> (<ref>Briquet 9993</ref>) and5 <watermark>ox</watermark> (close to <ref>Briquet 2785</ref>).6 The first and last leaf of each quire, with the7 exception of quires xvi and xviii, are constituted by8 bifolia of parchment, and all seven miniatures have been9 painted on inserted singletons of parchment

10 </supportDesc>11 </objectDesc>

This example combines information which might alternatively be more precisely tagged using the more specificelements described in the following subsections. ÷Support

The <support> element groups together information about the physical carrier. Typically, for manuscripts, thiswill entail discussion of the materials (paper, parchment...) written on. For paper, a discussion of any watermarkspresent may also be useful. If this makes reference to standard catalogues of such items, these may be taggedusing the standard <ref> element as in the following example:

Example 1.681 <support>2 3 <material>Paper</material> with watermark: <watermark>anchor in a4 circle with star on top</watermark>,5 <watermark>countermark B-B with trefoil</watermark>6 similar to <ref>Moschin, Anchor N 1680</ref>7 <date>1570-1585</date>.8 </support>

÷Extent

The <extent> element, defined in the TEI header, may also be used in a manuscript description, for example tospecify the number of leaves or bifolia a manuscript contains. Such measurements may be specifically markedusing the phrase level <dimensions> element, as in the following example, or left as plain prose.

Example 1.691 <extent>2 leaves, taken from the binding of a printed book</extent>2 <extent>ii + 321 leaves3 <dimensions units="cm">4 <height>5</height>5 <width>3</width>6 </dimensions>7 </extent>

Since the <dimensions> element is available for use anywhere in a description, the cataloguer may choose todiscuss (for example) dimensions of miniatures at the same time as describing the miniatures, rather than specifythat information within the <extent> element. ÷Collation

The <collation> element should be used to specify exactly how the leaves or bifolia of a manuscript arecombined into quires etc. This may be described using informal prose, or any appropriate notational convention.No specific notation is defined here as yet, but provision is made for the tagging of such formulae with the standardTEI <formula> element as in the following example:

Example 1.701 <collation>2 3 <formula>1-5.8 6.6 (catchword, f. 46, does not match following text)

Date: 28

4 7-8.8 9.10, 11.2 (through f. 82) 12-14.8 15.8(-7)</formula>5 Catchwords are written horizontally in center6 or towards the right lower margin in various manners:7 in red ink for quires 1-6 (which are also signed in red8 ink with letters of the alphabet and arabic numerals);9 quires 7-9 in ink of text within yellow decorated frames;

10 quire 10 in red decorated frame; quire 12 in ink of text;11 quire 13 with red decorative slashes; quire 14 added in12 cursive hand.13 </collation>

÷Foliation

The <foliation> element describes one or more pagination schemes applied to the manuscript. It should beused to indicate the scheme of page numbers, folio numbers or column numbers provided in the manuscript, as inthe following examples:

Example 1.711 <foliation>2 Folio numbers were added by Árni Magnússon3 ca. <date>1720-1730</date> with brown ink in the upper right corner4 of all recto-pages.5 </foliation>6 <foliation>7 Page numbers have been written with pen in the late8 19th century on top of every ten recto-pages, to the right: 11,9 21, 31, etc. Later, folio numbers have been written between

10 columns on top of every recto-page, in pencil.11 </foliation>

It may also include discussion of such features as original signatures or catchwords, where relevant, as in thefollowing example:

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

÷Condition

The <condition> element may be used to summarize the overall physical state of a manuscript, in particularwhere such information is not recorded elsewhere in the description. It should not however be used to describechanges or repairs to a manuscript; these are more appropriately described as a part of its custodial history.

Example 1.731 <condition>2 The text begins and ends defective, and there are two lacunae toward3 the end. What was originally the first leaf of the first quire,4 numbered 1a, has been cut away, leaving a strip approximately 15 mm5 wide; one to two letters, in some places on the verso up to four,6 remain of each line. The manuscript contains a large number of7 erasures, possibly by the scribe, possibly by a later hand, but in any8 case for the most part unfilled in; for example on f. 3ra, lines 15-69 there are two erasures, the first of perhaps 16 the second of six

10 characters, and four lines of text have been erased on f. 5vb11 following l. 21. In addition, there are several spaces that appear12 never to have been filled in, e.g. f. 13vb, l. 24, where enough space13 for about eight letters has been left blank by the scribe.14 15 </condition>

29 Date:

P5 Fascicule

÷LayoutDescription

The second part of the <objectDesc> element is a <layoutDesc> element, which is used to describe anddocument the way in which text and illustration are displayed on the written surface, specifying for examplethe number of written, ruled, or pricked lines and columns per page, presence or absence of margins, distinctblocks such as glossaria etc. This may be given as a simple series of paragraphs. Alternatively, one or moredifferent layouts may be identified within a single manuscript, each described by its own <layout> element.

• <layoutDesc> 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, orother evidence of page-preparation techniques.

columns specifies the number of columns per page

ruledLines specifies the number of ruled lines per column

writtenLines specifies the number of written lines per colum

Where the <layout> element is used, the layout will often be sufficiently regular for the attributes on this elementto convey all that is necessary; more usually however a more detailed treatment will be required. The attributesare provided as a convenient short hand for commonly occurring cases, and should not be used except where thelayout is regular. The value NA (not-applicable) should be used for cases where the layout is either very irregular, orwhere it cannot be characterised simply in terms of lines and columns, for example, where blocks of commentaryand text are arranged in a regular but complex pattern on each pageThe following examples indicate the range of possibilities:

Example 1.741 <layout ruledLines="25-32">2 Most pages have between 25 and 32 long lines ruled in lead.3 </layout>

Where multiple <layout> elements are supplied, the scope for each specification should be indicated by meansof <locus> elements within the content of the element, as in the following example:

Example 1.751 <layoutDesc>2 <layout ruledLines="25-32">3 4 <locus from="1r-202v"/>5 <locus from="210r-212v"/>6 Between 25 and 32 ruled lines.7 </layout>8 <layout ruledLines="34-50">9 

10 <locus from="203r-209v"/>Between 34 and 50 ruled lines.11 </layout>12 </layoutDesc>

÷Writing, DecorationandotherNotations

The second group of elements within a structured physical description concerns aspects of the writing or othernotation (notably, music) found within a manuscript, including additions made in later hands.

• <handDesc> contains a description of all the different kinds of writing used in a manuscript.

hands specifies the number of distinct hands identified within the manuscript

• <handNote> describes a particular style or hand distinguished within a manuscript.

scribe gives a standard name or other identifier for the scribe believed to be responsible for this hand.

script characterizes the particular script or writing style used by this hand, for example ‘secretary’,‘copperplate’, ‘Chancery’, ‘Italian’, etc..

medium describes the tint or type of ink, e.g. ‘brown’, or other writing medium, e.g. ‘pencil’,

scope specifies how widely this hand is used in the manuscript. Legal values are:

sole only this hand is used throughout the manuscript

Date: 30

major this hand is used through most of the manuscriptminor this hand is used occasionally in the manuscript

• <decoDesc> contains a description of the decoration of a manuscript, either as a sequence of paragraphs, oras a sequence of topically organised decoNote elements.


• <decoNote> contains a note describing either a decorative component of a manuscript, or a fairlyhomogenous class of such components.



• <musicNotation> contains description of type of musical notation.


• <additions> contains a description of any significant additions found within a manuscript, such asmarginalia or other annotations.


÷Writing

The <handDesc> element may contain a short description of the general characteristics of the writing observed ina manuscript as in the following example:

Example 1.761 <handDesc>2 Written in a <term>late caroline minuscule</term>; versals in a3 form of <term>rustic capitals</term>; although the marginal and4 interlinear gloss is written in varying shades of ink that are5 not those of the main text, text and gloss appear to have been6 copied during approximately the same time span.7 </handDesc>

Note the use of the <term> element to mark specific technical terms within the context of the <handDesc>element. Where several distinct hands have been identified, the cataloguer may simply specify the fact using thehands attribute, as in the following example:

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

Alternatively, or in addition, where more specific information about one or more of the hands identified is to berecorded, the <handNote> element should be used. Such hand descriptions may contain prose and may also bearparticular attributes to facilitate retrieval as in the following example:

Example 1.781 EXAMPLE NEEDED

3 

The <locus> element discussed in section 1.1.2.3. References to manuscript locations may be used to specifyexactly which parts of a manuscript are written by a given hand where this information is included within the handdescription.When a full or partial transcription of a manuscript is available as well as the manuscript description, the<handShift> element described in «PHDH» may be used to link the relevant parts of the transcription to theappropriate <handDesc> element in the description.

31 Date:

P5 Fascicule

Example 1.791 EXAMPLE NEEDED

3 

÷Decoration

In describing a manuscript, it is often difficult or impossible to draw a clear distinction between aspects which arepurely physical and aspects which contribute to the intellectual content. This is particularly true of ‘decorative’aspects such as illustrations and decorations within the manuscript or binding. We propose the following elementsfor the purpose of delimiting discussion of these aspects within a manuscript description, amd for conveniencelocate them all within the physical description, despite the fact that illustrative features in many cases may bebetter thought of as part of the intellectual content, and thus better described under the <msContents> elementdiscussed in section 1.1.5. Intellectual Content.The <decoDesc> element may contain simply one or more paragraphs summarizing the overall nature of thedescriptive features of the manuscript, as in the following example:

Example 1.801 <decoDesc>2 The decoration comprises two3 full page miniatures, perhaps added by the original4 owner, or slightly later; the original major decoration5 consists of twenty-three large miniatures, illustrating6 the divisions of the Passion narrative and the start of7 the major texts, and the major divisions of the Hours;8 seventeen smaller miniatures, illustrating the suffrages9 to saints; and seven historiated initials, illustrating

10 the pericopes and major prayers.11 </decoDesc>

Alternatively, it may contain a series of more specific typed <decoNote> elements, each summarizing a particularaspect of the decoration present, for example the use of miniatures, initials (historiated or otherwise), borders,diagrams, etc., as in the following example:

Example 1.811 <decoDesc>2 <decoNote type="miniature">3 One full-page miniature, facing the beginning of the first Penitential Psalm.4 </decoNote>5 <decoNote type="initial">6 One seven-line historiated initial, commencing the first Penitential Psalm.7 </decoNote>8 <decoNote type="initial">9 Six four-line decorated initials, commencing the second through the

10 seventh Penitential Psalm.11 </decoNote>12 <decoNote type="initial">13 Some three hundred two-line versal initials with pen-flourishes,14 commencing the psalm verses.15 </decoNote>16 <decoNote type="border">17 Four-sided border decoration surrounding the miniatures and18 three-sided border decoration accompanying the historiated and19 decorated initals.20 </decoNote>21 </decoDesc>

Where more exact indexing of the decorative content of a manuscript is required, the standard TEI elements<term> or <index> may be used within the prose description to supply or delimit appropriate iconographicterms, as in the following example:

Example 1.821 <decoDesc>2 <decoNote type="miniatures">

Date: 32

3 Fourteen large miniatures with arched4 tops, above five lines of text:5 <list>6 <item>7 <locus>fol. 14r</locus>Pericopes. <term>St. John writing on8 Patmos</term>, with the Eagle holding his ink-pot and pen-case;9 some flaking of pigment, especially in the sky</item>

10 <item>11 <locus>fol. 26r</locus>Hours of the Virgin, Matins.12 <term>Annunciation</term>; Gabriel and the Dove to the13 right</item>14 <item>15 <locus>fol. 60r</locus>Prime. <term>Nativity</term>; the16 <term>Virgin and Joseph adoring the Child</term>17 </item>18 <item>19 <locus>fol. 66r</locus>Terce. <term>Annunciation to the20 Shepherds</term>, one with <term>bagpipes</term>21 </item>22 

24 </list>25 26 </decoNote>27 </decoDesc>

÷Musicalnotation

Where a manuscript contains music or similar non-verbal notation, the <musicNotation> element may be usedto describe the notation employed, as in the following example:

Example 1.831 <musicNotation>2 Square notation of 4-line red staves.3 </musicNotation>4 <musicNotation>5 Neumes in campo aperto of the St. Gall type.6 </musicNotation>

÷Additionsandmarginalia

The <additions> element is used to record and discuss any written or drawn additional text found in amanuscript, such as marginalia, scribblings, etc. which the cataloguer considers of interest or importance. Suchtopics may also be discussed or referenced elsewhere in a description, for example in the <history> elementwhere the marginalia provide evidence of ownership, but the <additions> element is particularly useful for thispurpose.Here are some examples of the use of this element

Example 1.841 <additions>2 In most parts of the codex the text has been quite3 extensively corrected in a contemporary hand from the manuscript GKS4 3270 4to.5 </additions>6 <additions>7 The text of this manuscript is not interpolated with8 sentences from Royal decrees promulgated in 1294, 1305 and 1314. In9 the margins, however, another somewhat later scribe has added the

10 relevant paragraphs of these decrees, see pp. 8, 24, 44, 4711 etc.12 As a humorous gesture the scribe in one opening of the13 manuscript, pp. 36 and 37, has prolonged the lower stems of one letter14 f and five letters þ and has them drizzle down the15 margin.16 </additions>

33 Date:

P5 Fascicule

÷Bindingsandseals

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

• <bindingDesc> describes the present and former bindings of a manuscript, either as a series of paragraphsor 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

contemporary specifies whether or not the binding is contemporary with the majority of its contents Valuesare:yes the binding is contemporaneous with its contentsno the binding is not contemporaneous with its contentsunknown the date of either binding or manuscript is unknown

• <sealDesc> describes the seals or other external items attached to a manuscript, either as a series ofparagraphs 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

contemporary specifies whether or not the seal is contemporary with the item to which it is affixed

• <accMat> contains details of any significant additional material which may be closely associated withthe manuscript being described, such as non-contemporaneous documents or fragments bound in with themanuscript at some earlier historical period.

type further characterizes the accompanying material, for example as letter, note, paste-in, etc.

÷BindingDescriptions

The <bindingDesc> element contains a description of the state of the present and former bindings of amanuscript, including information about its material, any distinctive marks, and provenance information. Thismay be given as a series of paragraphs, if only one binding is being described, or as a series of distinct <binding>elements, each describing a distinct binding, where these are separately described. For example:

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

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

Example 1.861 <binding>2 Bound, s. XVIII (?), in3 <material>diced russia leather</material>4 retaining most of the original 15th century5 metal ornaments (but with some replacements)6 as well as the heavy wooden boards; 7 <decoNote>8 on each cover: alternating circular stamps of the9 Holy Monogram, a sunburst, and a flower;

10 </decoNote>11 <decoNote>12 on the cornerpieces, one of which is missing,13 a rectangular stamp of the Agnus Dei;14 </decoNote>15 rebacked during the 19th (?) century.16 </binding>

Date: 34

÷Sealsandotheradditionalcomponents

The <sealDesc> element supplies information about the seal(s) attached to documents to guarantee their integrity,or to show authentication of the issuer or consent of the participants. It may contain one or more paragraphsummarizing the the overall nature of the seals, or may contain one or more <seal> elements.

Example 1.871 <sealDesc>2 <seal n="1" type="pendant" subtype="cauda duplex">3 Round seal of <name>Anders Olufsen</name> in black wax:4 <bibl>5 <ref>DAS 930</ref>6 </bibl>. Parchment tag, on which is written: <q>pertinere nos predictorum placiti nostri iusticarii precessorum dif</q>.7 </seal>8 <seal n="2" type="pendant" subtype="cauda duplex">9 The seal of <name>Jens Olufsen</name> in black wax. <bibl>

10 <ref>DAS 1061</ref>11 </bibl>. Legend: <q>S IOHANNES OLAVI</q>.12 Parchment tag on which is written: <q>Woldorp Iohanne G</q>.13 </seal>14 </sealDesc>

÷Accompanyingmaterial

The circumstance commonly arises where a manuscript has additional material, not originally part of themanuscript, which is bound with it or otherwise accompanying the manuscript. In cases where this is clearlya distinct manuscript, the whole manuscript should be treated as a composite manuscript and the additional matterdescribed in a separate <msPart> (see 1.1.9. Manuscript Parts below). However, there are cases where theadditional matter is not self-evidently a distinct manuscript: it might be an important set of notes by a later scholaror owner, or it might be a file of correspondence relating to the manuscript. The <accMat> element is provided asa holder for this kind of information:

• <accMat> contains details of any significant additional material which may be closely associated withthe manuscript being described, such as non-contemporaneous documents or fragments bound in with themanuscript at some earlier historical period. Selected attributes:


Here is an example of the use of this element, describing a note by the Icelandic manuscript collector ÁrniMagnússon which has been bound with the manuscript:

Example 1.881 <accMat>2 A slip in Árni Magnússon’s hand has been stuck to the3 pastedown on the inside front cover; the text reads:4 <q lang="is">Þidreks Søgu þessa hefi eg5 feiged af Sekreterer Wielandt Anno 17156 i Kaupmanna høfn. Hun er, sem eg sie, Copia af Austfirda7 bókinni (Eidagás) en<expan>n</expan> ecki progenies8 Brædratungu bokarinnar. Og er þar fyrer eigi i9 allan<expan>n</expan> máta samhlioda

10 þ<expan>eir</expan>re er Sr Jon Erlendz son hefer ritad fyrer11 Mag. Bryniolf. Þesse Þidreks Saga mun vera komin fra Sr12 Vigfuse á Helgafelle.</q>13 14 </accMat>

÷Formaldefinitions

The formal definition for the <physDesc> element and its constituents is as follows:

Element: physDescphysDesc =## contains a full physical description of a## manuscript, either as a sequence of paragraphs, or as a series of more## specialised elements.

35 Date:

P5 Fascicule

element physDesc physDesc.content, physDesc.attributesphysDesc.content =tei.paragraph+| (objectDesc?,handDesc?,musicNotation?,decoDesc?,additions?,bindingDesc?,sealDesc?,accMat?)physDesc.attributes =tei.global.attributes,[ a:defaultValue = "physDesc" ] attribute TEIform text ?,empty

Element: objectDescobjectDesc =## contains a description of the physical## components making up the object which is being described.element objectDesc objectDesc.content, objectDesc.attributesobjectDesc.content = tei.paragraph+ | ( supportDesc?, layoutDesc? )objectDesc.attributes =tei.global.attributes,objectDesc.attributes.form,[ a:defaultValue = "objectDesc" ] attribute TEIform text ?,emptyobjectDesc.attributes.form =## a short project-specific name identifying the physical form of## the carrier, for example as a codex, roll, fragment, partial leaf,## cutting etc.attribute form objectDesc.attributes.form.content ?objectDesc.attributes.form.content = datatype.Key

Element: supportDescsupportDesc =## groups elements describing the physical support for the written part ofa manuscript.element supportDesc supportDesc.content, supportDesc.attributessupportDesc.content =tei.paragraph+ | ( support?, extent?, foliation?, collation?, condition?)supportDesc.attributes =tei.global.attributes,supportDesc.attributes.material,[ a:defaultValue = "supportDesc" ] attribute TEIform text ?,emptysupportDesc.attributes.material =## a short project-defined name for the material composing## the majority of the supportattribute material supportDesc.attributes.material.content ?supportDesc.attributes.material.content = datatype.Key

Date: 36

physDesc.content

tei.paragraph

objectDesc

handDesc

musicNotation

decoDesc

additions

bindingDesc

sealDesc

accMat

objectDesc.content

tei.paragraph

supportDesc

layoutDesc

datatype.Key

supportDesc.content

tei.paragraph

support

extent

foliation

collation

condition

datatype.Key


Element: supportsupport =## contains a description of the materials## etc. which make up the physical support for the written part of amanuscript.element support support.content, support.attributessupport.content = tei.paragraph+support.attributes =tei.global.attributes,[ a:defaultValue = "support" ] attribute TEIform text ?,empty

Element: collationcollation =## contains a description of how the leaves or bifolia are physically## arranged.element collation collation.content, collation.attributescollation.content = tei.paragraph+collation.attributes =tei.global.attributes,[ a:defaultValue = "collation" ] attribute TEIform text ?,empty

Element: foliationfoliation =## describes the numbering system or systems used to## count the leaves or pages in a codex.element foliation foliation.content, foliation.attributesfoliation.content = tei.paragraph+foliation.attributes =tei.global.attributes,[ a:defaultValue = "foliation" ] attribute TEIform text ?,empty

Element: conditioncondition =## contains a description of the physical## condition of the manuscript.element condition condition.content, condition.attributescondition.content = tei.paragraph+condition.attributes =tei.global.attributes,[ a:defaultValue = "condition" ] attribute TEIform text ?,empty

Element: layoutDesclayoutDesc =## collects the set of layout descriptions applicable to a manuscript.element layoutDesc layoutDesc.content, layoutDesc.attributeslayoutDesc.content = tei.paragraph+ | layout+layoutDesc.attributes =tei.global.attributes,[ a:defaultValue = "layoutDesc" ] attribute TEIform text ?,empty

Element: layoutlayout =## describes how text is laid out on the page,## including information about any ruling, pricking, or other evidence of

37 Date:

support.content

tei.paragraph

collation.content

tei.paragraph

foliation.content

tei.paragraph

condition.content

tei.paragraph

layoutDesc.content

tei.paragraph

layout

P5 Fascicule

## page-preparation techniques.element layout layout.content, layout.attributeslayout.content = tei.paragraph+layout.attributes =tei.global.attributes,layout.attributes.columns,layout.attributes.ruledLines,layout.attributes.writtenLines,[ a:defaultValue = "layout" ] attribute TEIform text ?,emptylayout.attributes.columns =## specifies the number of columns per pageattribute columns layout.attributes.columns.content ?layout.attributes.columns.content = datatype.Keylayout.attributes.ruledLines =## specifies the number of ruled lines per columnattribute ruledLines layout.attributes.ruledLines.content ?layout.attributes.ruledLines.content = datatype.Keylayout.attributes.writtenLines =## specifies the number of written lines per columattribute writtenLines layout.attributes.writtenLines.content ?layout.attributes.writtenLines.content = datatype.Key

Element: handDeschandDesc =## contains a description of all the different kinds of writing used in amanuscript.element handDesc handDesc.content, handDesc.attributeshandDesc.content = ( handNote | tei.paragraph )+handDesc.attributes =tei.global.attributes,handDesc.attributes.hands,[ a:defaultValue = "handDesc" ] attribute TEIform text ?,emptyhandDesc.attributes.hands =## specifies the number of distinct hands identified within the manuscriptattribute hands handDesc.attributes.hands.content ?handDesc.attributes.hands.content = datatype.Key

Element: handNotehandNote =## describes a particular style## or hand distinguished within a manuscript.element handNote handNote.content, handNote.attributeshandNote.content = tei.paragraph+handNote.attributes =tei.global.attributes,handNote.attributes.scribe,handNote.attributes.script,handNote.attributes.medium,handNote.attributes.scope,[ a:defaultValue = "handNote" ] attribute TEIform text ?,emptyhandNote.attributes.scribe =## gives a standard name or other identifier for the scribe## believed to be responsible for this hand.attribute scribe handNote.attributes.scribe.content ?

Date: 38

layout.content

tei.paragraph

datatype.Key

datatype.Key

datatype.Key

handDesc.content

handNote

tei.paragraph

datatype.Key

handNote.content

tei.paragraph


handNote.attributes.scribe.content = datatype.KeyhandNote.attributes.script =## characterizes the particular script or writing style used by## this hand, for example secretary, copperplate, Chancery, Italian, etc..attribute script handNote.attributes.script.content ?handNote.attributes.script.content = datatype.KeyhandNote.attributes.medium =## describes the tint or type of ink, e.g. brown, or other## writing medium, e.g. pencil,attribute medium handNote.attributes.medium.content ?handNote.attributes.medium.content = datatype.KeyhandNote.attributes.scope =## specifies how widely this hand is used in the manuscript.attribute scope handNote.attributes.scope.content ?handNote.attributes.scope.content = datatype.Key

Element: musicNotationmusicNotation =## contains description of type of musical notation.element musicNotation musicNotation.content, musicNotation.attributesmusicNotation.content = tei.paragraph+musicNotation.attributes =tei.global.attributes,[ a:defaultValue = "musicNotation" ] attribute TEIform text ?,empty

Element: decoDescdecoDesc =## contains a description of the decoration of a manuscript, either as asequence of paragraphs, or as a sequence of topically organised decoNoteelements.element decoDesc decoDesc.content, decoDesc.attributesdecoDesc.content = tei.paragraph+ | decoNote+decoDesc.attributes =tei.global.attributes,[ a:defaultValue = "decoDesc" ] attribute TEIform text ?,empty

Element: decoNotedecoNote =## contains a note describing either a## decorative component of a manuscript, or a fairly homogenous class of## such components.element decoNote decoNote.content, decoNote.attributesdecoNote.content = tei.paragraph+decoNote.attributes =tei.global.attributes,decoNote.attributes.type,decoNote.attributes.subtype,[ a:defaultValue = "decoNote" ] attribute TEIform text ?,emptydecoNote.attributes.type =## specifies the kind of decorative feature being describedattribute type decoNote.attributes.type.content ?decoNote.attributes.type.content = datatype.KeydecoNote.attributes.subtype =## supplies a further sub-categorization of the value specified by the## type

39 Date:

datatype.Key

datatype.Key

datatype.Key

datatype.Key

musicNotation.content

tei.paragraph

decoDesc.content

tei.paragraph

decoNote

decoNote.content

tei.paragraph

datatype.Key

P5 Fascicule

## attribute.attribute subtype decoNote.attributes.subtype.content ?decoNote.attributes.subtype.content = datatype.Key

Element: bindingDescbindingDesc =## describes the present and former bindings of a manuscript, either## as a series of paragraphs or as a series of distinct binding elements,## one for each binding of the manuscript.element bindingDesc bindingDesc.content, bindingDesc.attributesbindingDesc.content = ( p | decoNote )+ | binding+bindingDesc.attributes =tei.global.attributes,[ a:defaultValue = "bindingDesc" ] attribute TEIform text ?,empty

Element: bindingbinding =## contains a description of one binding, i.e. type of covering, boards,etc. applied to a manuscriptelement binding binding.content, binding.attributesbinding.content = ( tei.paragraph | decoNote )+binding.attributes =tei.global.attributes,tei.datable.attributes,binding.attributes.contemporary,[ a:defaultValue = "binding" ] attribute TEIform text ?,emptybinding.attributes.contemporary =## specifies whether or not the binding is contemporary with the majorityof its contentsattribute contemporary binding.attributes.contemporary.content ?binding.attributes.contemporary.content = datatype.UBooleantei.datable |= binding

Element: sealDescsealDesc =## describes the seals or other external items attached to a manuscript,either## as a series of paragraphs or as a series of distinct seal elements,## possibly with additional decoNotes.element sealDesc sealDesc.content, sealDesc.attributessealDesc.content = p+ | ( decoNote | seal )+sealDesc.attributes =tei.global.attributes,[ a:defaultValue = "sealDesc" ] attribute TEIform text ?,empty

Element: sealseal =## contains a description of one seal or similar## attachment applied to a manuscriptelement seal seal.content, seal.attributesseal.content = ( tei.paragraph | decoNote )+seal.attributes =tei.global.attributes,tei.typed.attributes,tei.datable.attributes,

Date: 40

datatype.Key

bindingDesc.content

p

decoNote

binding

binding.content

tei.paragraph

decoNote

datatype.UBoolean

binding

sealDesc.content

p

decoNote

seal

seal.content

tei.paragraph

decoNote

seal.attributes.contemporary,[ a:defaultValue = "seal" ] attribute TEIform text ?,emptyseal.attributes.contemporary =## specifies whether or not the seal is contemporary with the## item to which it is affixedattribute contemporary seal.attributes.contemporary.content ?seal.attributes.contemporary.content = datatype.UBooleantei.typed |= sealtei.datable |= seal

Element: additionsadditions =## contains a description of any significant additions found## within a manuscript, such as marginalia or other annotations.element additions additions.content, additions.attributesadditions.content = tei.paragraph+additions.attributes =tei.global.attributes,[ a:defaultValue = "additions" ] attribute TEIform text ?,empty

Element: accMataccMat =## contains details of any significant additional## material which may be closely associated with the manuscript being## described, such as non-contemporaneous documents or fragments bound in## with the manuscript at some earlier historical period.element accMat accMat.content, accMat.attributesaccMat.content = tei.paragraph+accMat.attributes =tei.global.attributes,accMat.attributes.type,[ a:defaultValue = "accMat" ] attribute TEIform text ?,emptyaccMat.attributes.type =## further characterizes the accompanying material, for example as letter,note, paste-in, etc.attribute type accMat.attributes.type.content ?accMat.attributes.type.content = datatype.Key

÷History

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

• <history> groups elements describing the full history of a manuscript or manuscript part.


• <origin> contains any descriptive or other information concerning the origin of a manuscript or manuscriptpart.


• <provenance> contains any descriptive or other information concerning a single identifiable episode duringthe history of a manuscript or manuscript part, after its creation but before its acquisition.


• <acquisition> contains any descriptive or other information concerning the process by which a manuscriptor manuscript part entered the holding institution.


41 Date:

datatype.UBoolean

seal

seal

additions.content

tei.paragraph

accMat.content

tei.paragraph

datatype.Key

P5 Fascicule

The three components of the <history> element all have the same substructure, consisting of one or moreparagraphs marked as elements. Each of these three elements is also a member of the datable attributeclass, and thus also carries the following optional attributes:

• <tei.datable> defines the set of attributes common to all elements that contain datable events. Selectedattributes:



evidence indicates the nature of the evidence supporting the reliability or accuracy of the dating.

The history of a manuscript should normally be presented in the order implied by the above description.Information about the origins of the element (including any discussion of its sources) should be given asone or more paragraphs contained by a single <origin> element; any available information or discussion ofdistinct stages in the history of the manuscript before its arrival in its current location should be included asparagraphs within one or more <provenance> elements following this. Finally, any information specific to themeans by which the manuscript was acquired by its present owners should be given as paragraphs within the<acquisition> element.Here is a simple example of the use of this element:

Example 1.1151 <history>2 <origin>3 Written in Durham during the mid twelfth4 century.5 </origin>6 <provenance>7 Recorded in two medieval8 catalogues of the books belonging to Durham Priory, made in 1391 and9 1405.

10 Given to W. Olleyf by William Ebchester, Prior (1446-56)11 and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)12 according to inscriptions on ff. 4v and 5.13 </provenance>14 <acquisition>15 Presented to Trinity College in 1738 by16 Thomas Gale and his son Roger.17 </acquisition>18 </history>

Here is a more realistic example:

Example 1.1161 <history>2 <origin notBefore="1225" notAfter="1275" evidence="attributed">3 Written in Spain or Portugal in the middle of the 13th4 century (that date 1042 given in a marginal note on f. 97v cannot be correct.)5 </origin>6 <provenance>7 The Spanish scholar <name type="person">Benito Arias8 Montano</name> (1527-1598) has written his name on f. 97r, and may be9 presumed to have owned the manuscript. It came somehow into the

10 possession of <foreign lang="da">etatsråd</foreign>11 <name type="person">Holger12 Parsberg</name> (1636-1692), who has written his name twice, once on13 the front pastedown and once on f. 1r, the former dated14 <date>1680</date> and the latter <date>1682</date>. Following15 Parsberg’s death the manuscript was bought by <foreign>etatsråd</foreign>16 <name type="person">Jens Rosenkrantz</name> (1640-1695) when Parsberg’s17 library was auctioned off (23.10.1693).18 </provenance>19 <acquisition>20 The manuscript was acquired by Árni21 Magnússon from the estate of Jens Rosenkrantz, presumably at22 auction (the auction lot number 468 is written in red chalk on the

Date: 42

23 flyleaf), either in 1696 or 97.24 </acquisition>25 </history>

The <history> element and its immediate component elements are formally defined as follows:

Element: historyhistory =## groups elements## describing the full history of a manuscript or manuscript part.element history history.content, history.attributeshistory.content = tei.paragraph+ | ( origin?, provenance*, acquisition? )history.attributes =tei.global.attributes,[ a:defaultValue = "history" ] attribute TEIform text ?,empty

Element: originorigin =## contains any descriptive or other information## concerning the origin of a manuscript or manuscript part.element origin origin.content, origin.attributesorigin.content = tei.paragraph+origin.attributes =tei.global.attributes,tei.datable.attributes,[ a:defaultValue = "origin" ] attribute TEIform text ?,emptytei.datable |= origin

Element: provenanceprovenance =## contains any descriptive or other information## concerning a single identifiable episode during the history of amanuscript## or manuscript part, after its creation but before its acquisition.element provenance provenance.content, provenance.attributesprovenance.content = tei.paragraph+provenance.attributes =tei.global.attributes,tei.datable.attributes,[ a:defaultValue = "provenance" ] attribute TEIform text ?,emptytei.datable |= provenance

Element: acquisitionacquisition =## contains any descriptive or other information## concerning the process by which a manuscript or manuscript part enteredthe holding## institution.element acquisition acquisition.content, acquisition.attributesacquisition.content = tei.paragraph+acquisition.attributes =tei.global.attributes,tei.datable.attributes,[ a:defaultValue = "acquisition" ] attribute TEIform text ?,emptytei.datable |= acquisition

43 Date:

history.content

tei.paragraph

origin

provenance

acquisition

origin.content

tei.paragraph

origin

provenance.content

tei.paragraph

provenance

acquisition.content

tei.paragraph

acquisition

P5 Fascicule

÷Additionalinformation

Four categories of additional information are provided for by the scheme described here, grouped together withinthe <additional> element described in this section.

• <additional> groups additional information relating to the modern bibliography for a manuscript, its currentcuratorial status, and and other associated materials.


• <adminInfo> contains information about the present custody and availability of the manuscript, and alsoabout the record description itself.


• <surrogates> contains information about any digital or photographic representations of the manuscriptbeing described which may exist in the holding institution or elsewhere.


• <listBibl> contains a list of bibliographic citations of any kind.


None of the constituent elements of <additional> is required. If any is supplied, it may appear once only;furthermore, the order in which elements are supplied should be as specified above.The <additional> element is formally defined as follows:

Element: additionaladditional =## groups additional information relating to the## modern bibliography for a manuscript, its current curatorial status,and## and other associated materials.element additional additional.content, additional.attributesadditional.content = adminInfo?, surrogates?, listBibl?additional.attributes =tei.global.attributes,[ a:defaultValue = "additional" ] attribute TEIform text ?,empty

÷AdministrativeInformation

A variety of information relating to the curation and management of a manuscript may be recorded as simpleprose narrative tagged using the standard element. Alternatively, different aspects of this information may bepresented grouped within one or more of the following specialized elements:

• <recordHist> provides information about the source and revision status of the parent manuscript descriptionitself.


• <custodialHist> contains a description of a manuscript’s custodial history, either as running prose or as aseries of dated custodial events.


• <availability> supplies information about the availability of a text, for example any restrictions on its useor distribution, its copyright status, etc.

status supplies a code identifying the current availability of the text. Legal values are:

free the text is freely available.unknown the status of the text is unknown.restricted the text is not freely available.

• <remarks> contains any commentary or discussion about the usage of an element, attribute, class, or entitynot otherwise documented within the containing element.

Date: 44

additional.content

adminInfo

surrogates

listBibl

÷RecordHistory

The <recordHist> element, if supplied, must contain a <source> element, followed by an optional series of<change> elements.

• <source> describes the original source for the information contained with a manuscript description.


• <change> summarizes a particular change or correction made to a particular version of an electronic textwhich is shared between several researchers.


The <source> element is used to document the primary source of information for the catalogue record containingit, in a similar way to the standard TEI <sourceDesc> element within a TEI Header. If the record is a newone, catalogued without reference to anything other than the manuscript itself, then it may simply contain a element as in the following example:

Example 1.1221 <source>2 Directly catalogued from the original manuscript.3 </source>

More usually however the record will be derived from some previously existing catalogue, which may be specifiedusing the standard TEI <bibl> element, as in the following example:

Example 1.1231 <recordHist>2 <source>3 Information transcribed from4 <bibl>5 <title>IMEV</title>6 <biblScope>1234</biblScope>7 </bibl>8 9 </source>

10 </recordHist>

If, as is likely, a full bibliographic description of the source from which cataloguing information was taken isincluded within the <listBibl> element contained by the current <additional> element, or elsewhere in thecurrent document, then it need not be repeated here. Instead, it should be referenced using the standard TEI <ref>element, as in the following example:

Example 1.1241 <additional>2 <adminInfo>3 <recordHist>4 <source>5 Information transcribed from6 <ref target="#IMEV123">IMEV 123</ref>7 8 </source>9 </recordHist>

10 </adminInfo>11 <listBibl>12 <bibl id="IMEV123">13 <title>Index of Medieval Verse</title>14 15 <biblScope>123</biblScope>16 </bibl>17 

19 </listBibl>20 </additional>

45 Date:

P5 Fascicule

The <change> element is a standard TEI element, which may also appear within the <revisionDesc> elementof the standard TEI Header; its use here is intended to signal the similarity of function between the two containerelements. Where the TEI Header should be used to document the revision history of the whole electronic file towhich it is prefixed, the <recordHist> element may be used to document changes at a lower level, relating to theindividual description, as in the following example:

Example 1.1251 EXAMPLE NEEDED2 

÷Availabilityandcustodialhistory

The <availability> element is a standard TEI element, which should be used here to supply any informationconcerning access to the current manuscript, such as its physical location where this is not implicit in its identifier,any restrictions on access, information about copyright, etc.

Example 1.1261 <availability>2 The manuscript is in poor condition, due to many of3 the leaves being brittle and fragile and the poor quality of a number4 of earlier repairs; it should therefore not be used or lent out until5 it has been conserved.6 </availability>

The <custodialHist> record is used to describe the custodial history of a manuscript, recording any significantevents noted during the period that it has been located within the cataloguing institution. It may contain eithera series of paragraphs tagged with the standard TEI element, or a series of <custEvent> elements, eachdescribing a distinct incident or event, further specified by a type attribute, and carrying dating information byvirtue of its membership in the datable class, as noted above.

• <custEvent> describes a single event during the custodial history of a manuscript. Selected attributes:

type specifies the type of event, for example conservation, photography, exhibition, etc.

Here is an example of the use of this element:Example 1.127

1 <custodialHist>2 <custEvent type="conservation" notBefore="1961-03" notAfter="1963-02">3 Conserved between March 1961 and February 1963 at Birgitte Dalls4 Konserveringsværksted.5 </custEvent>6 <custEvent type="photography" notBefore="1988-05-01" notAfter="1988-05-30">7 Photographed in May 1988 by AMI/FA.8 </custEvent>9 <custEvent type="transfer/dispatch" notBefore="1989-11-13" notAfter="1989-11-13">

10 Dispatched to Iceland 13 November 1989.11 </custEvent>12 </custodialHist>

÷Formaldefinitions

The <adminInfo> element and its immediate component elements are formally defined as follows:

Element: adminInfoadminInfo =## contains information about the present## custody and availability of the manuscript, and also about the record## description itself.element adminInfo adminInfo.content, adminInfo.attributesadminInfo.content =tei.paragraph+ | ( recordHist?, availability?, custodialHist?, note? )adminInfo.attributes =tei.global.attributes,[ a:defaultValue = "adminInfo" ] attribute TEIform text ?,empty

Date: 46

adminInfo.content

tei.paragraph

recordHist

availability

custodialHist

note

Element: recordHistrecordHist =## provides information about the source and## revision status of the parent manuscript description itself.element recordHist recordHist.content, recordHist.attributesrecordHist.content = tei.paragraph+ | ( source, change* )recordHist.attributes =tei.global.attributes,[ a:defaultValue = "recordHist" ] attribute TEIform text ?,empty

Element: sourcesource =## describes the original source for the information contained with amanuscript description.element source source.content, source.attributessource.content = tei.paragraph+source.attributes =tei.global.attributes,[ a:defaultValue = "source" ] attribute TEIform text ?,empty

Element: custodialHistcustodialHist =## contains a description of a manuscript’s custodial history, either## as running prose or as a series of dated custodial events.element custodialHist custodialHist.content, custodialHist.attributescustodialHist.content = tei.paragraph+ | custEvent+custodialHist.attributes =tei.global.attributes,[ a:defaultValue = "custodialHist" ] attribute TEIform text ?,empty

Element: custEventcustEvent =## describes a single event during the custodial history of a manuscript.element custEvent custEvent.content, custEvent.attributescustEvent.content = tei.paragraph+custEvent.attributes =tei.global.attributes,tei.datable.attributes,custEvent.attributes.type,[ a:defaultValue = "custEvent" ] attribute TEIform text ?,emptycustEvent.attributes.type =## specifies the type of event, for example conservation, photography,exhibition, etc.attribute type custEvent.attributes.type.content ?custEvent.attributes.type.content = datatype.Keytei.datable |= custEvent

÷Surrogates

The <surrogates> element is used to provide information about any digital or photographic representations ofthe manuscript which may exist within the holding institution or elsewhere.

• <surrogates> contains information about any digital or photographic representations of the manuscriptbeing described which may exist in the holding institution or elsewhere.


47 Date:

recordHist.content

tei.paragraph

source

change

source.content

tei.paragraph

custodialHist.content

tei.paragraph

custEvent

custEvent.content

tei.paragraph

datatype.Key

custEvent

P5 Fascicule

The <surrogates> element should not be used to repeat information about representations of the manuscriptavailable within published works; this should normally be documented within the <listBibl> element withinthe <additional> element. However, it is often also convenient to record information such as negative numbers,digital identifiers etc. for unpublished collections of manuscript images maintained within the holding institution,as well as to provide more detailed descriptive information about the surrogate itself. Such information may beprovided as prose paragraphs, within which identifying information about particular surrogates may be presentedusing the standard TEI <bibl> element, as in the following example:

Example 1.1331 <surrogates>2 3 <bibl>4 <title type="gmd">diapositive</title>5 <idno>AM 74 a, fol.</idno>6 <date>May 1984</date>7 </bibl>8 <bibl>9 <title type="gmd">b/w prints</title>

10 <idno>AM 75 a, fol.</idno>11 <date>1972</date>12 </bibl>13 14 </surrogates>

Note the use of the specialised form of GMD (general material designation) title to specify the kind of surrogatebeing documented.At a later revision, the content of the <surrogates> element is likely to be expanded to include elements morespecifically intended to provide detailed information such as technical details of the process by which a digital orphotographic image was made.If the whole of a manuscript is being digitized, it should be contained in a separate document which lists all theimages using <div> etc. to structure them. In such a case, the <msDescription> placed within the teiHeader.The <surrogates> element is formally defined as follows:

Element: surrogatessurrogates =## contains information about any digital or## photographic representations of the manuscript being described which## may exist in the holding institution or elsewhere.element surrogates surrogates.content, surrogates.attributessurrogates.content = tei.paragraph+surrogates.attributes =tei.global.attributes,[ a:defaultValue = "surrogates" ] attribute TEIform text ?,empty

÷ManuscriptParts

It is frequently the case that an item catalogued as if it were a single object is in fact a composite made up ofseveral different and originally distinct manuscripts or manuscript fragments. Each such component should berecorded using a distinct <msPart> element, embedded within the <msDescription> element for the composite:

• <msPart> contains information about an originally distinct manuscript or manuscript fragment nowforming part of a composite manuscript.


Each component of a composite manuscript may have its own content, physical description, history, etc. It mayhave been given a distinct identifier which it would be desirable to maintain. And finally, it is not impossible thata composite be made from previously-existing composites. For all these reasons, the <msPart> element used torecord information about an individual constituent of a composite manuscript has an almost identical structure tothat of a <msdescription> proper. The main difference is that an identifier must be supplied for a full manuscriptdescription (using the <msIdentifier> element), but is only optional in the case of a manuscript part.Here is a simple example of a composite manuscript, in which there are two discrete components:

Date: 48

surrogates.content

tei.paragraph

Example 1.1351 <msDescription>2 <msIdentifier>3 4 </msIdentifier>5 6 7 8 <msPart>9 <physDesc>

10 11 </physDesc>12 <msContent>13 14 </msContent>15 </msPart>16 <msPart>17 <physDesc>18 19 </physDesc>20 <msContent>21 22 </msContent>23 </msPart>24 </msDescription>

If the parts of a composite manuscript have their own identifiers, they should be tagged using the <idno> element,rather than the <msIdentifier> element. Whatever value is specified should be appended to the <idno>specified in the parent <msIdentifier> in order to obtain a full identification for the part, as in the followingexample:

Example 1.1361 <msDescription>2 <msIdentifier>3 <settlement>Amiens</settlement>4 <repository>Bibliothèque Municipale</repository>5 <idno>MS 3</idno>6 <altName>Maurdramnus Bible</altName>7 </msIdentifier>8 9 <msPart>

10 <altIdentifier>11 <idno>MS 6</idno>12 </altIdentifier>13 

15 </msPart>16 <msPart>17 <altIdentifier>18 <idno>MS 7</idno>19 </altIdentifier>20 

22 </msPart>23 <msPart>24 <altIdentifier>25 <idno>MS 9</idno>26 </altIdentifier>27 

29 </msPart>30 

32 </msDescription>

49 Date:

P5 Fascicule

The <msPart> element is formally defined as follows:

Element: msPartmsPart =## contains information about an originally distinct manuscript ormanuscript fragment now forming part of a composite manuscript.element msPart msPart.content, msPart.attributesmsPart.content =altIdentifier,head*,( p+ | ( msContents?, physDesc?, history?, additional?, msPart* ) )msPart.attributes =tei.global.attributes,[ a:defaultValue = "msPart" ] attribute TEIform text ?,empty

÷ReferenceSection

This chapter documents the following two modules:Module msdescription-decl: Populates the classes used by the Manuscript Description module

• Elements defined:

• Classes defined: tei.measured: tei.datable:

• Macros defined:

Module msdescription: Manuscript Description

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

• Classes defined:

• Macros defined:

Here is an overview of the declarations documented by this chapter:

Class: tei.measuredtei.measured |= notAllowed

tei.measured.attributes |=tei.measured.attributes.units,tei.measured.attributes.scopetei.measured.attributes.units =## names the units used for the measurement.attribute units tei.measured.attributes.units.content ?tei.measured.attributes.units.content = texttei.measured.attributes.scope =## specifies the applicability of this measurement, where## more than one object is being measured.attribute scope tei.measured.attributes.scope.content ?tei.measured.attributes.scope.content = text

Class: tei.databletei.datable |= notAllowed

Date: 50

msPart.content

altIdentifier

head

p

msContents

physDesc

history

additional

msPart

tei.measured

tei.datable

msDescription

dimensions

height

depth

width

locus

origDate

origPlace

material

heraldry

signatures

secFol

watermark

msIdentifier

institution

repository

collection

altIdentifier

altName

colophon

explicit

incipit

msContents

msItem

rubric

summary

filiation

textLang

physDesc

objectDesc

supportDesc

support

collation

foliation

condition

layoutDesc

layout

handDesc

handNote

musicNotation

decoDesc

decoNote

bindingDesc

binding

sealDesc

seal

additions

accMat

history

origin

provenance

acquisition

additional

adminInfo

recordHist

source

custodialHist

custEvent

surrogates

msPart


tei.datable.attributes |=tei.datable.attributes.notBefore,tei.datable.attributes.notAfter,tei.datable.attributes.certainty,tei.datable.attributes.evidencetei.datable.attributes.notBefore =## specifies the earliest possible date for the event in## standard form, e.g. yyyy-mm-dd.attribute notBefore tei.datable.attributes.notBefore.content ?tei.datable.attributes.notBefore.content =xsd:date| xsd:gYear| xsd:gMonth| xsd:gDay| xsd:gYearMonth| xsd:gMonthDay| xsd:time| xsd:dateTimetei.datable.attributes.notAfter =## specifies the latest possible date for the event in## standard form, e.g. yyyy-mm-dd.attribute notAfter tei.datable.attributes.notAfter.content ?tei.datable.attributes.notAfter.content =xsd:date| xsd:gYear| xsd:gMonth| xsd:gDay| xsd:gYearMonth| xsd:gMonthDay| xsd:time| xsd:dateTimetei.datable.attributes.certainty =## specifies the general opinion as to the reliability or## accuracy of the dating.attribute certainty tei.datable.attributes.certainty.content ?tei.datable.attributes.certainty.content = texttei.datable.attributes.evidence =## indicates the nature of the evidence supporting the reliability or## accuracy of the dating.attribute evidence tei.datable.attributes.evidence.content ?tei.datable.attributes.evidence.content = text

« include 1 »

« include 2 »

« include 3 »

« include 4 »

« include 5 »

« include 6 »

« include 7 »

« include 8 »

« include 9 »

51 Date:

P5 Fascicule

« include 10 »

÷Classcatalogue÷ tei.datable[class]Description: defines the set of attributes common to all elements that contain datable events.Attributes: (In addition to global attributes)



certainty specifies the general opinion as to the reliability or accuracy of the dating. Sample values include:

high the dating is generally considered to be correct.

medium the dating is generally considered approximately correct.

low the dating is generally considered doubtful but possible.

evidence indicates the nature of the evidence supporting the reliability or accuracy of the dating. Sample valuesinclude:

internal there is internal evidence to support the dating.

external there is external evidence to support the dating.

conjecture no specific evidence is available to support the dating.

Member of classes (none)Members: origDate: binding: seal: origin: provenance: acquisition: custEventModule: msdescription-decl ÷tei.measured[class]Description: defines the set of attributes common to all elements that contain measurements.Attributes: (In addition to global attributes)

units names the units used for the measurement.

scope specifies the applicability of this measurement, where more than one object is being measured. Samplevalues include:

all measurement applies to all instances.

most measurement applies to most of the instances inspected.

range measurement applies to only the specified range of instances.

Member of classes (none)Members: dimensions: height: depth: widthModule: msdescription-decl ÷Patterncatalogue÷ Elementcatalogue÷ accMat[element]Description: (accompanying material) contains details of any significant additional material which may be closelyassociated with the manuscript being described, such as non-contemporaneous documents or fragments bound inwith the manuscript at some earlier historical period.Declaration:

element accMat

tei.global.attributes,

accMat.attributes.type,

tei.paragraph+

Attributes: (In addition to global attributes)


Example:

<accMat>A copy of a tax form from 1947 is included in the envelopewith the letter. It is not catalogued separately.

</accMat>

Date: 52

origDate

binding

seal

origin

provenance

acquisition

custEvent

dimensions

height

depth

width

tei.paragraph

Module: msdescription ÷acquisition[element]Description: contains any descriptive or other information concerning the process by which a manuscript ormanuscript part entered the holding institution.Classes: tei.datableDeclaration:

element acquisition


tei.datable.attributes,

tei.paragraph+

Attributes: Global attributes and those inherited from : tei.datableExample:

<acquisition>Left to the <name type="place">Bodleian</name> by<name type="person">Richard Rawlinson</name> in 1755.

</acquisition>

Module: msdescription ÷additional[element]Description: groups additional information relating to the modern bibliography for a manuscript, its currentcuratorial status, and and other associated materials.Declaration:

element additional


( adminInfo?, surrogates?, listBibl? )

Attributes: Global attributes onlyExample:

<additional><adminInfo><recordHist>



</recordHist><custodialHist>



</custodialHist></adminInfo><surrogates>



</surrogates><listBibl>



</listBibl></additional>

Module: msdescription ÷additions[element]Description: contains a description of any significant additions found within a manuscript, such as marginalia orother annotations.Declaration:

53 Date:

tei.datable

tei.paragraph

tei.datable

adminInfo

surrogates

listBibl

P5 Fascicule

element additions tei.global.attributes, tei.paragraph+


Module: msdescription ÷adminInfo[element]Description: (administrative information) contains information about the present custody and availability of themanuscript, and also about the record description itself.Declaration:

element adminInfo


( tei.paragraph+ | ( recordHist?, availability?, custodialHist?, note? ) )


<adminInfo><recordHist><source>Record created <date>1 Aug 2004</date>

</source></recordHist><availability>Until 2015 permission to photocopy some materials from thiscollection has been limited at the request of the donor. Please ask repository staff for detailsif you are interested in obtaining photocopies from Series 1:Correspondence.

</availability><custodialHist>Collection donated to the Manuscript Library by the Estate ofEdgar Holden in 1993. Donor number: 1993-034.

</custodialHist></adminInfo>

Module: msdescription ÷altIdentifier[element]Description: (alternative identifier) contains an alternative or former structured identifier used for a manuscript,such as a former catalogue number.Classes: tei.typedDeclaration:

element altIdentifier


(

country?,

region?,

settlement?,

institution?,

repository?,

collection?,

idno

)

Date: 54

tei.paragraph

tei.paragraph

recordHist

availability

custodialHist

note

country

region

settlement

institution

repository

collection

idno

Attributes: Global attributes and those inherited from : tei.typedExample:

<altIdentifier><settlement>San Marino</settlement><repository>Huntington Library</repository><idno>MS.El.26.C.9</idno>

</altIdentifier>

An identifying number of some kind must be supplied if known; if it is not known, this should be stated.Module: msdescription ÷altName[element]Description: (alternative name) contains any form of unstructured alternative name used for a manuscript, suchas an ‘ocellus nominum’, or nickname.Declaration:

element altName tei.global.attributes, altName.attributes.type, text


type further characterizes the alternative name, for example as former shelfmark, nickname, etc.

Example:

<altName type="nick">The Vercelli Book</altName>

Module: msdescription ÷binding[element]Description: contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscriptClasses: tei.datableDeclaration:

element binding



binding.attributes.contemporary,

( tei.paragraph | decoNote )+

Attributes: (In addition to global attributes and those inherited from : tei.datable)

contemporary specifies whether or not the binding is contemporary with the majority of its contents Values are:

yes the binding is contemporaneous with its contents

no the binding is not contemporaneous with its contents

unknown the date of either binding or manuscript is unknown

Example:

<binding contemporary="yes">Contemporary blind stamped leather over woodenboards with evidence of a fore edge clasp closingto the back cover.</binding>

Example:

<bindingDesc><binding contemporary="no">Quarter bound by the Phillipps’ binder, Bretherton,with his sticker on the front pastedown.

55 Date:

tei.datable

tei.paragraph

decoNote

tei.datable

P5 Fascicule

</binding><binding contemporary="no">Rebound by an unknown 19th c. company; edges cropped andgilt.</binding></bindingDesc>

Module: msdescription ÷bindingDesc[element]Description: describes the present and former bindings of a manuscript, either as a series of paragraphs or as aseries of distinct <binding> elements, one for each binding of the manuscript.Declaration:

element bindingDesc tei.global.attributes, ( ( p | decoNote )+ | binding+ )


<bindingDesc>Sewing not visible; tightly rebound over19th-cent. pasteboards, reusing panels of 16th-cent. brown leather withgilt tooling à la fanfare, Paris c. 1580-90, the centre of eachcover inlaid with a 17th-cent. oval medallion of red morocco tooled ingilt (perhaps replacing the identifying mark of a previous owner); thespine similarly tooled, without raised bands or title-piece; colouredendbands; the edges of the leaves and boards gilt.Boxed.</bindingDesc>

Module: msdescription ÷collation[element]Description: contains a description of how the leaves or bifolia are physically arranged.Declaration:

element collation tei.global.attributes, tei.paragraph+


<collation>The written leaves preceded by an original flyleaf,conjoint with the pastedown.</collation>

Example:

<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><catchwords>Catchwords are written horizontally in centeror towards the right lower margin in various manners:in red ink for quires 1-6 (which are also signed in redink with letters of the alphabet and arabic numerals);quires 7-9 in ink of text within yellow decorated frames;quire 10 in red decorated frame; quire 12 in ink of text;quire 13 with red decorative slashes; quire 14 added incursive hand.</catchwords></collation>

Module: msdescription ÷collection[element]Description: contains the name of a collection of manuscripts, not necessarily located within a single repository.

Date: 56

p

decoNote

binding

tei.paragraph

Classes: tei.namesDeclaration:

element collection tei.global.attributes, text

Attributes: Global attributes and those inherited from : tei.namesExample:

Module: msdescription ÷colophon[element]Description: contains the text of any colophon attached to a particular manuscript item: that is, an inscription,usually found at a break point such as the end of a text or codex, usually containing information about theproduction of the manuscript, such as the name of the scribe, the date and place of the copying, the personwho commissioned the copying, etc.Declaration:

element colophon tei.global.attributes, macro.phraseSeq


<colophon>Ricardus Franciscus Scripsit Anno Domini 1447.</colophon><colophon>Explicit expliceat/scriptor ludere eat.</colophon>

Module: msdescription ÷condition[element]Description: contains a description of the physical condition of the manuscript.Declaration:

element condition tei.global.attributes, tei.paragraph+


Module: msdescription ÷custEvent[element]Description: describes a single event during the custodial history of a manuscript.Classes: tei.datableDeclaration:

element custEvent



custEvent.attributes.type,

tei.paragraph+

Attributes: (In addition to global attributes and those inherited from : tei.datable)

type specifies the type of event, for example conservation, photography, exhibition, etc.

Example:

57 Date:

macro.phraseSeq

tei.paragraph

tei.datable

tei.paragraph

tei.datable

P5 Fascicule

<custEvent type="photography"><date>12 Dec 1964</date>Photographed by David Cooper</custEvent>

Module: msdescription ÷custodialHist[element]Description: contains a description of a manuscript’s custodial history, either as running prose or as a series ofdated custodial events.Declaration:

element custodialHist


( tei.paragraph+ | custEvent+ )


<custodialHist><custEvent type="conservation" notBefore="1961-03" notAfter="1963-02">Conserved between March 1961 and February 1963 at Birgitte DallsKonserveringsværksted.

</custEvent><custEvent type="photography" notBefore="1988-05-01" notAfter="1988-05-30">Photographed in May 1988 by AMI/FA.

</custEvent><custEvent type="transfer/dispatch" notBefore="1989-11-13" notAfter="1989-11-13">Dispatched to Iceland 13 November 1989.

</custEvent></custodialHist>

Module: msdescription ÷decoDesc[element]Description: contains a description of the decoration of a manuscript, either as a sequence of paragraphs, or as asequence of topically organised <decoNote> elements.Declaration:

element decoDesc tei.global.attributes, ( tei.paragraph+ | decoNote+ )


<decoDesc>The start of each book of the Bible with a 10-line historiatedilluminated initial; prefaces decorated with 6-line blue initials with redpenwork flourishing; chapters marked by 3-line plain red initials; verseswith 1-line initials, alternately blue or red.</decoDesc>

Module: msdescription ÷decoNote[element]Description: contains a note describing either a decorative component of a manuscript, or a fairly homogenousclass of such components.Declaration:

element decoNote


decoNote.attributes.type,

decoNote.attributes.subtype,

tei.paragraph+

Date: 58

tei.paragraph

custEvent

tei.paragraph

decoNote

tei.paragraph

Example:

<decoDesc><decoNote type="initial">The start of each book of the Bible witha 10-line historiated illuminated initial;prefaces decorated with 6-line blue initialswith red penwork flourishing; chapters marked by3-line plain red initials; verses with 1-line initials,alternately blue or red.

</decoNote></decoDesc>

Module: msdescription ÷depth[element]Description: contains a measurement measured across the spine.Classes: tei.measuredDeclaration:

element depth tei.global.attributes, tei.measured.attributes, text

Attributes: Global attributes and those inherited from : tei.measuredExample:

<depth units="in">4</depth>

Module: msdescription ÷dimensions[element]Description: contains any kind of dimensional specification.Classes: tei.measured: tei.dataDeclaration:

element dimensions


tei.measured.attributes,

dimensions.attributes.type,

( height?, width?, depth? )+

Attributes: (In addition to global attributes and those inherited from : tei.measured: tei.data)

type indicates which aspect of the object is being measured. Sample values include:

leaves dimensions relate to one or more leaves (e.g. a single leaf, a gathering, or a separately bound part)

ruled dimensions relate to the area of a leaf which has been ruled in preparation for writing.

pricked dimensions relate to the area of a leaf which has been pricked out in preparation for ruling (usedwhere this differs significantly from the ruled area, or where the ruling is not measurable).

written dimensions relate to the area of a leaf which has been written, with the height measured from thetop of the minims on the top line of writing, to the bottom of the minims on the bottom line of writing.

miniatures dimensions relate to the miniatures within the manuscript

binding dimensions relate to the binding in which the codex or manuscript is contained

box dimensions relate to the box or other container in which the manuscript is stored.

Example:

59 Date:

tei.measured

tei.measured

tei.measured

height

width

depth

tei.measured

P5 Fascicule

<dimensions type="leaves"><height scope="range">157-160</height><width>105</width>

</dimensions><dimensions type="ruled"><height scope="most">90</height><width scope="most">48</width>

</dimensions><dimensions units="in"><height>12</height><width>10</width>

</dimensions>

Module: msdescription ÷explicit[element]Description: contains the text of any explicit attached to a particular manuscript item, that is, the closing wordsof a text or a section of a text, sometimes used as a kind of title, possibly followed by one or more rubrics orcolophons.Declaration:

element explicit


explicit.attributes.defective,

explicit.attributes.type,

macro.phraseSeq


defective indicates whether the explicit as given is defective, i.e. incomplete.

type specifies the type of explicit, e.g. whether it is a formal closing for the work.

Example:

<explicit>sed libera nos a malo.</explicit><rubric>Hic explicit oratio quidicitur dominica.</rubric>

<explicit type="defective">ex materia quasi et forma sibiproporti<gap></explicit>

<explicit type="reverse">saued be shulle that doome of day the at</explicit>

Module: msdescription ÷filiation[element]Description: contains information concerning the manuscript’s filiation, i.e. its relationship to other survivingmanuscripts of the same text, its protographs, antigraphs and apographs.Classes: tei.typedDeclaration:

element filiation tei.global.attributes, macro.specialPara

Attributes: Global attributes and those inherited from : tei.typedExample:

<msItem><title>Beljakovski sbornik</title>

Date: 60

macro.phraseSeq

macro.specialPara

<filiation type="protograph">Bulgarian</filiation><filiation type="antigraph">Middle Bulgarian</filiation><filiation type="apograph"><ref target="#DN17">Dujchev N 17</ref>

</filiation></msItem>

In this example, the reference to ‘Dujchev N17’ includes a link to some other manuscript description which hasthe identifier DN17.Example:

<msItem><title>Guan-ben</title><filiation>The "Guan-ben" was widely current among mathematicians in the

Qing dynasty, and "Zhao Qimei version" was also read. It istherefore difficult to know the correct filiation path to follow.The study of this era is much indebted to Li Di. We explain theoutline of his conclusion here. Kong Guangsen(1752-1786)(17) was from the same town as Dai Zhen, so he obtained"Guan-ben" from him and studied it(18). Li Huang (d. 1811)(19) took part in editing Si Ku Quan Shu, so he must have had"Guan-ben". Then Zhang Dunren (1754-1834) obtained this version,and studied "Da Yan Zong Shu Shu" (The General DayanComputation). He wrote Jiu Yi Suan Shu (MathematicsSearching for One, 1803) based on this version of Shu Xue JiuZhang (20).

One of the most important persons in restoring our knowledgeconcerning the filiation of these books was Li Rui (1768(21)-1817)(see his biography). ... only two volumes remain of thismanuscript, as far as chapter 6 (chapter 3 part 2) p.13, that is,question 2 of "Huan Tian San Ji" (square of three loops),which later has been lost.

</filiation></msItem>



Module: msdescription ÷foliation[element]Description: describes the numbering system or systems used to count the leaves or pages in a codex.Declaration:

element foliation tei.global.attributes, tei.paragraph+


<foliation>Contemporary foliation in redroman numerals in the centreof the outer margin.</foliation>

Module: msdescription ÷handDesc[element]Description: contains a description of all the different kinds of writing used in a manuscript.Declaration:

element handDesc


handDesc.attributes.hands,

( handNote | tei.paragraph )+

61 Date:

tei.paragraph

handNote

tei.paragraph

P5 Fascicule


hands specifies the number of distinct hands identified within the manuscript

Example:

<handDesc>Written in <term>angelicana formata</term>.

</handDesc>

Example:

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

</handDesc>

Module: msdescription ÷handNote[element]Description: (note on hand) describes a particular style or hand distinguished within a manuscript.Declaration:

element handNote


handNote.attributes.scribe,

handNote.attributes.script,

handNote.attributes.medium,

handNote.attributes.scope,

tei.paragraph+


scribe gives a standard name or other identifier for the scribe believed to be responsible for this hand.

script characterizes the particular script or writing style used by this hand, for example ‘secretary’, ‘copperplate’,‘Chancery’, ‘Italian’, etc..

medium describes the tint or type of ink, e.g. ‘brown’, or other writing medium, e.g. ‘pencil’,

scope specifies how widely this hand is used in the manuscript. Legal values are:

sole only this hand is used throughout the manuscript

major this hand is used through most of the manuscript

minor this hand is used occasionally in the manuscript

Example:

<handNote scope="sole">Written in insular phase II half-uncialwith interlinear Old English gloss in an Anglo-Saxonpointed minuscule.

</handNote>

Module: msdescription ÷height[element]Description: contains a measurement measured along the axis parallel to the spine.Classes: tei.measuredDeclaration:

Date: 62

tei.paragraph

tei.measured

element height tei.global.attributes, tei.measured.attributes, text


<height units="in">4</height>

Module: msdescription ÷heraldry[element]Description: contains a heraldic formula or phrase, typically found as part of a blazon, coat of arms, etc. within amanuscript .Classes: tei.phraseDeclaration:

element heraldry tei.global.attributes, macro.phraseSeq

Attributes: Global attributes and those inherited from : tei.phraseExample:

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 <q>Cole Deum</q>.

Module: msdescription ÷history[element]Description: groups elements describing the full history of a manuscript or manuscript part.Declaration:

element history


( tei.paragraph+ | ( origin?, provenance*, acquisition? ) )


<history><origin>Written in Durham during the mid twelfthcentury.</origin><provenance>Recorded in two medievalcatalogues of the books belonging to Durham Priory, made in 1391 and1405.Given to W. Olleyf by William Ebchester, Prior (1446-56)and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)according to inscriptions on ff. 4v and 5.</provenance><acquisition>Presented to Trinity College in 1738 byThomas Gale and his son Roger.</acquisition></history>

Module: msdescription ÷incipit[element]Description: contains the text of any incipit attached to a particular manuscript item, that is the opening wordsof a text, frequently used as a form of identifier for it; it may be preceded by one or more rubrics, and may bedefective.Declaration:

63 Date:

tei.measured

macro.phraseSeq

tei.paragraph

origin

provenance

acquisition

P5 Fascicule

element incipit


incipit.attributes.defective,

incipit.attributes.type,

macro.phraseSeq


defective indicates whether the incipit as given is defective, i.e. incomplete.

type specifies the type of incipit, e.g. whether it introduces a work, is biblical, legal, etc.

Example:

<incipit>Pater noster qui es in celis</incipit>

<incipit defective ="yes"><gap/>tatem dedit hominibus alleluia.<rubric>Capitulum,</rubric> Primum quidemsermonem feci de omnibus</incipit>

<incipit type="biblical">Ghif ons huden onse dagelixbroet</incipit>

<incipit>O ongehoerde gewerdighe christi</incipit>

<incipit type="lemma">Firmiter</incipit>

<incipit>Ideo dicit firmiter quiaordo fidei nostre probari non potest</incipit>

Module: msdescription ÷institution[element]Description: contains the name of an organization, such as a University or Library, within which a manuscriptrepository is located.Classes: tei.namesDeclaration:

element institution tei.global.attributes, text


Module: msdescription ÷layout[element]Description: describes how text is laid out on the page, including information about any ruling, pricking, or otherevidence of page-preparation techniques.Declaration:

element layout


layout.attributes.columns,

layout.attributes.ruledLines,

layout.attributes.writtenLines,

tei.paragraph+

Date: 64

macro.phraseSeq

tei.paragraph

columns specifies the number of columns per page

ruledLines specifies the number of ruled lines per column

writtenLines specifies the number of written lines per colum

Example:

<layout ruledLines="25-32">Most pages have between 25 and 32 long lines ruled in lead.

</layout>

Example:

<layout columns="2" ruledLines="42">2 columns of 42 lines ruled in ink, with central rulebetween the columns.

</layout>

Module: msdescription ÷layoutDesc[element]Description: collects the set of layout descriptions applicable to a manuscript.Declaration:

element layoutDesc tei.global.attributes, ( tei.paragraph+ | layout+ )


<layoutDesc>Most pages have between 25 and 32 long lines ruled in lead.

</layoutDesc>

Example:

<layoutDesc><layout columns="2" ruledLines="42"><locus from="f12r" to="f15v"/>

2 columns of 42 lines pricked and ruled in ink, withcentral rule between the columns.

</layout><layout columns="3"><locus from="f16"/>Prickings for three columns are visible.

</layout></layoutDesc>

Module: msdescription ÷locus[element]Description: defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous)sequence of folio references.Classes: tei.phraseDeclaration:

element locus


locus.attributes.scheme,

65 Date:

tei.paragraph

layout

P5 Fascicule

locus.attributes.from,

locus.attributes.to,

locus.attributes.targets,

text

Attributes: (In addition to global attributes and those inherited from : tei.phrase)





Example:

<locus targets="#P12 img01#P13 #P14 #P16">fols 12-14, 16r</locus>

Module: msdescription ÷material[element]Description: contains a phrase describing the material of which any part of a manuscript or binding is composed.Classes: tei.phraseDeclaration:

element material tei.global.attributes, macro.phraseSeq




Module: msdescription ÷msContents[element]Description: describes the intellectual content of a manuscript or manuscript part either as a series of paragraphsor as a series of structured manuscript items.Declaration:

element msContents


msContents.attributes.class,

msContents.attributes.defective,

( tei.paragraph+ | ( summary?, msItem+ ) )




Example:

<msContents>A collection of Lollard sermons</msContents>

Example:

Date: 66

macro.phraseSeq

tei.paragraph

summary

msItem

<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 tomutilation throughout</note></msItem></msContents>

Module: msdescription ÷msDescription[element]Description: contains a description of a single identifiable manuscript or manuscript partClasses: tei.sourcedescDeclaration:

element msDescription


msDescription.attributes.type,

msDescription.attributes.status,

(

msIdentifier,

head*,

( p+ | ( msContents?, physDesc?, history?, additional?, msPart* ) )

)

Attributes: (In addition to global attributes and those inherited from : tei.sourcedesc)

type specifies the type of manuscript being described, for example as ’diploma’, ’codex’ etc.

status specifies the compositional status of a manuscript or manuscript part. Values are:

uni unitary: the manuscript is a complete entity which exists as a single unit.

compo composite: the manuscript is a complete entity comprising multiple units of different origin.

frag fragmentary: a leaf, a part of a leaf, or a manuscript from which the majority of leaves are missing.

def defective: a ms from which a minority of the leaves are missing.

unknown unknown or unstated.

Example:

<msDescription><msIdentifier><settlement>Oxford</settlement><repository>Bodleian Library</repository><idno type="Bod">MS Poet. Rawl. D. 169.</idno>

67 Date:

msIdentifier

head

p

msContents

physDesc

history

additional

msPart

P5 Fascicule

</msIdentifier><msContents><msItem><author>Geoffrey Chaucer</author><title>The Canterbury Tales</title>

</msItem></msContents><physDesc><objectDesc>A parchment codex of 136 folios, measuring approx28 by 19 inches, and containing 24 quires.

The pages are margined and ruled throughout.Four hands have been identied in the manuscript: the first 44folios being written in two cursive anglicana scripts, while theremainder is for the most part in a mixed secretary hand.

</objectDesc></physDesc>

</msDescription>

Module: msdescription ÷msIdentifier[element]Description: contains the information required to identify a given manuscript or manuscript part uniquely withinits holding institution.Classes: tei.biblPartDeclaration:

element msIdentifier


(

country?,

region?,

settlement,

institution?,

repository,

collection?,

idno,

( altIdentifier | altName )*

)

Attributes: Global attributes and those inherited from : tei.biblPartExample:

<msIdentifier><settlement>San Marino</settlement><repository>Huntington Library</repository><idno>MS.El.26.C.9</idno>

</msIdentifier>

Module: msdescription ÷msItem[element]Description: describes an individual work or item within the intellectual content of a manuscript or manuscriptpart.Declaration:

element msItem


msItem.attributes.class,

Date: 68

country

region

settlement

institution

repository

collection

idno

altIdentifier

altName

msItem.attributes.defective,

(

locus?,

(

tei.paragraph+

| (

author*,

respStmt*,

title*,

rubric?,

incipit?,

explicit?,

colophon*,

decoNote*,

langUsage*,

listBibl*,

q*,

bibl*,

filiation*,

note*,

textLang?,

msItem*

)

)

)




Example:

<msItem><locus>ff. 1r-24v</locus><title>Agrip af Noregs konunga sögum</title><incipit>regi oc h<expan>ann</expan> setiho<gap reason="illegible" extent="7"/>scheim se<expan>m</expan> þio</incipit>

<explicit>h<expan>on</expan> hev<expan>er</expan><expan>oc</expan>þa buit hesta .ij. aNan viþfé enh<expan>on</expan>o<expan>m</expan> aNan tilreiþ<expan>ar</expan>

</explicit><textLang langKey="#ONI">Old Norse/Icelandic</textLang>

</msItem>

Module: msdescription ÷msPart[element]Description: contains information about an originally distinct manuscript or manuscript fragment now formingpart of a composite manuscript.Declaration:

69 Date:

locus

tei.paragraph

author

respStmt

title

rubric

incipit

explicit

colophon

decoNote

langUsage

listBibl

q

bibl

filiation

note

textLang

msItem

P5 Fascicule

element msPart


(

altIdentifier,

head*,

( p+ | ( msContents?, physDesc?, history?, additional?, msPart* ) )

)


Module: msdescription ÷musicNotation[element]Description: contains description of type of musical notation.Declaration:

element musicNotation tei.global.attributes, tei.paragraph+


<musicNotation>Square notation of 4-line red staves.</musicNotation>

Example:

<musicNotation>Neumes in campo aperto of the St. Gall type.</musicNotation>

Module: msdescription ÷objectDesc[element]Description: contains a description of the physical components making up the object which is being described.Declaration:

element objectDesc


objectDesc.attributes.form,

( tei.paragraph+ | ( supportDesc?, layoutDesc? ) )


form a short project-specific name identifying the physical form of the carrier, for example as a codex, roll,fragment, partial leaf, cutting etc.

Example:

<objectDesc form="codex"><supportDesc material="mixed">Early modern<material>parchment</material> and<material>paper</material>.

</supportDesc><layoutDesc><layout ruledLines="25-32"/>

</layoutDesc></objectDesc>

Date: 70

altIdentifier

head

p

msContents

physDesc

history

additional

msPart

tei.paragraph

tei.paragraph

supportDesc

layoutDesc

Module: msdescription ÷origDate[element]Description: contains any form of date, used to identify the date of origin for a manuscript or manuscript part.Classes: tei.datable: tei.phraseDeclaration:

element origDate tei.global.attributes, tei.datable.attributes, text

Attributes: Global attributes and those inherited from : tei.datable: tei.phraseExample:

<origDate>3rd century BCE</origDate>

Module: msdescription ÷origP lace[element]Description: contains any form of place name, used to identify the place of origin for a manuscript or manuscriptpart.Classes: tei.phraseDeclaration:

element origPlace tei.global.attributes, text


<origPlace>Birmingham</origPlace>

Module: msdescription ÷origin[element]Description: contains any descriptive or other information concerning the origin of a manuscript or manuscriptpart.Classes: tei.datableDeclaration:

element origin



tei.paragraph+


<origin notBefore="1802" notAfter="1845" evidence="internal">Copied in <name type=origPlace>Derby</name>, probably from anold Flemish original, between 1802 and 1845..</origin>

Module: msdescription ÷physDesc[element]Description: contains a full physical description of a manuscript, either as a sequence of paragraphs, or as a seriesof more specialised elements.Declaration:

element physDesc


(

tei.paragraph+

71 Date:

tei.datable

tei.datable

tei.datable

tei.paragraph

tei.datable

tei.paragraph

P5 Fascicule

| (

objectDesc?,

handDesc?,

musicNotation?,

decoDesc?,

additions?,

bindingDesc?,

sealDesc?,

accMat?

)

)


Module: msdescription ÷provenance[element]Description: contains any descriptive or other information concerning a single identifiable episode during thehistory of a manuscript or manuscript part, after its creation but before its acquisition.Classes: tei.datableDeclaration:

element provenance



tei.paragraph+


<provenance>Listed as the property of Lawrence Sterne in 1788.</provenance><provenance>Sold at Sothebys in 1899.</provenance>

Module: msdescription ÷recordHist[element]Description: provides information about the source and revision status of the parent manuscript description itself.Declaration:

element recordHist


( tei.paragraph+ | ( source, change* ) )


<recordHist><source>Derived from <ref target="#IMEV123">IMEV 123</ref> with additional researchby P.M.W.Robinson

</source>

Date: 72

objectDesc

handDesc

musicNotation

decoDesc

additions

bindingDesc

sealDesc

accMat

tei.datable

tei.paragraph

tei.datable

tei.paragraph

source

change

<change><date>23 June 1999</date><respStmt><name>LDB</name><resp>editor</resp>

</respStmt><item>checked examples against DTD version 3.6</item>

</change></recordHist>

Module: msdescription ÷repository[element]Description: contains the name of a repository (usually a distinct physical building) within which manuscripts arestored, forming part of an institution.Classes: tei.namesDeclaration:

element repository tei.global.attributes, text


Module: msdescription ÷rubric[element]Description: contains the text of any rubric or heading attached to a particular manuscript item, that is, a string ofwords whereby a manuscript signals a text division (e.g. beginning, book, chapter, end) which is in some way setoff from the text itself, usually in red ink,or by use of different size or type of script, lining, or other such visualdevice. .Declaration:

element rubric


rubric.attributes.type,

macro.phraseSeq


type specifies the type of rubric, e.g. whether it is at the start or end of the item.

Example:

<rubric>Explicit le romans de la Rose ou l’art d’amours est touteenclose.</rubric><rubric>Nu koma Skyckiu Rym<expan>ur</expan>.</rubric><rubric><locus>16. f. 28v in margin: </locus>Dicta Cassiodori</rubric>

Module: msdescription ÷seal[element]Description: contains a description of one seal or similar attachment applied to a manuscriptClasses: tei.typed: tei.datableDeclaration:

element seal



seal.attributes.contemporary,

( tei.paragraph | decoNote )+

73 Date:

macro.phraseSeq

tei.datable

tei.paragraph

decoNote

P5 Fascicule

Attributes: (In addition to global attributes and those inherited from : tei.typed: tei.datable)

contemporary specifies whether or not the seal is contemporary with the item to which it is affixed

Example:

<seal n="2" type="pendant" subtype="cauda duplex">The seal of <name>Jens Olufsen</name> in black wax.(<ref>DAS 1061</ref>). Legend: <q>S IOHANNES OLAVI</q>.Parchment tag on which is written: <q>Woldorp Iohanne G</q>.

</seal>

Module: msdescription ÷sealDesc[element]Description: describes the seals or other external items attached to a manuscript, either as a series of paragraphsor as a series of distinct <seal> elements, possibly with additional <decoNote>s.Declaration:

element sealDesc tei.global.attributes, ( p+ | ( decoNote | seal )+ )




Module: msdescription ÷secFol[element]Description: The word or words that a cataloguer, typically medieval but possibly modern as well, might takefrom a fixed point in all the codices he is describing (the beginning of the second leaf, the beginning of the secondcolumn, the beginning of the penultimate leaf, the end of the penultimate leaf, and so on) in order to provide aunique identifier to the particular codex.Classes: tei.phraseDeclaration:

element secFol tei.global.attributes, macro.phraseSeq


<secFol>(con-)versio morum</secFol>

Module: msdescription ÷signatures[element]Description: contains discussion of the leaf or quire signatures found within a codex.Classes: tei.phraseDeclaration:

element signatures tei.global.attributes, macro.phraseSeq


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

Date: 74

tei.datable

p

decoNote

seal

macro.phraseSeq

macro.phraseSeq

Module: msdescription ÷source[element]Description: describes the original source for the information contained with a manuscript description.Declaration:

element source tei.global.attributes, tei.paragraph+


<source>Derived from <ref target="#STAN60">Stanley (1960)</ref></source>

Module: msdescription ÷summary[element]Description: contains a brief summary of the intellectual content of an item, provided by the cataloguerDeclaration:

element summary tei.global.attributes, macro.phraseSeq


<summary>This item consists of three books with a prologue and an epilogue.</summary>

Module: msdescription ÷support[element]Description: contains a description of the materials etc. which make up the physical support for the written partof a manuscript.Declaration:

element support tei.global.attributes, tei.paragraph+


<objectDesc form="roll"><supportDesc><support>Parchment roll with <material>silk</material> ribbons.

</support></supportDesc>

</objectDesc>

Module: msdescription ÷supportDesc[element]Description: groups elements describing the physical support for the written part of a manuscript.Declaration:

element supportDesc


supportDesc.attributes.material,

(

tei.paragraph+

| ( support?, extent?, foliation?, collation?, condition? )

)

75 Date:

tei.paragraph

macro.phraseSeq

tei.paragraph

tei.paragraph

support

extent

foliation

collation

condition

P5 Fascicule


material a short project-defined name for the material composing the majority of the support Values are:

paper Paper

parch Parchment

mixed mixed

Example:

Module: msdescription ÷surrogates[element]Description: contains information about any digital or photographic representations of the manuscript beingdescribed which may exist in the holding institution or elsewhere.Declaration:

element surrogates tei.global.attributes, tei.paragraph+


<surrogates><bibl>

<title type="gmd">diapositive</title><idno>AM 74 a, fol.</idno><date>May 1984</date>

</bibl><bibl>

<title type="gmd">b/w prints</title><idno>AM 75 a, fol.</idno><date>1972</date>

</bibl></surrogates>

Module: msdescription ÷textLang[element]Description: describes the languages and writing systems used by a manuscript (as opposed to its description,which is described in the <langUsage> element)Declaration:

element textLang


textLang.attributes.langKey,

textLang.attributes.otherLangs,

macro.phraseSeq


langKey supplies a code which identifies the chief language used in the manuscript.

otherLangs one or more codes identifying any other languages used in the manuscript.

Example:

<textLang langKey="#EN" otherLangs="#LA">Predominantly in English with Latin glosses</textLang>

Date: 76

tei.paragraph

macro.phraseSeq

Module: msdescription ÷watermark[element]Description: contains a word or phrase describing a watermark or similar device.Classes: tei.phraseDeclaration:

element watermark tei.global.attributes, macro.phraseSeq


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

</support>

Module: msdescription ÷width[element]Description: contains a measurement measured along the axis perpendicular to the spine.Classes: tei.measuredDeclaration:

element width tei.global.attributes, tei.measured.attributes, text


<width units="in">4</width>

Module: msdescription

77 Date:

macro.phraseSeq

tei.measured

tei.measured

P5 Fascicule - idhmcmain.tamu.eduidhmcmain.tamu.edu/poetess/about/FASC-ms.pdf · P5 Fascicule Lou...

Documents

Transcript of P5 Fascicule - idhmcmain.tamu.eduidhmcmain.tamu.edu/poetess/about/FASC-ms.pdf · P5 Fascicule Lou...