TEI P5 schema for ENRICH
language: en
availability: Distributed under a Creative Commons Attribution-ShareAlike 3.0 Unported License Copyright 2013 TEI Consortium. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditio (http://creativecommons.org/licenses/by-sa/3.0/)

Introduction

This document defines an XML format for the structure of the data which all ENRICH partners will contribute to the Manuscriptorium, either directly or indirectly by means of a harvester or transformation process. The schema is a conformant subset of Release 1.1.0 of TEI P5.

The schema defined by this document addresses three distinct aspects of a digitized manuscript:

- metadata describing the original source manuscript (Manuscript Description Metadata)
- metadata describing digitized images of the original source manuscript (Metadata about digital facsimiles)
- a transcription of the text contained by the original source manuscript

Within Manuscriptorium, only the first two are required. However, the schema documented here also provides for the third, in the interest of completeness and for the assistance of ENRICH partners wishing to provide richer access facilities to their holdings.

The schema defined by this document is available in DTD, RELAX NG, and W3C Schema languages, downloadable from the address . A PDF version of the present document (300 pages) is also available from ; this forms one of the key deliverables for Work Package 3 of the ENRICH project.

The MASTER and MASTER-X specifications both defined comparatively unconstrained XML formats, which permitted a very wide range of possibilities and did not attempt to constrain (for example) values to any predefined set of values. While appropriate for an interchange format, this approach has some drawbacks.

- there may be wide variation in approaches taken to represent essentially the same phenomenon (e.g.)
- the format appears over complex to novice users, who will only ever want to use a very small subset of the possible tags
- developing software (e.g. stylesheets) for the format becomes unnecessarily complex, since every possibility must be allowed for even though it is unlikely to appear
- accurate searching of the data may be needlessly complicated by the large number of ways of representing e.g. attribute values such as dates

In the ENRICH schema the number of choices and the possible values of several attributes to have been considerably constrained. Nevertheless,

- the resulting schema remains fully TEI Conformant: we are only defining a subset
- all constraints introduced have the full consent of all partners in the project

The overall structure of an ENRICH-conformant XML document may be summarized as follows:

<TEI>
<teiHeader/>
<facsimile/>
<text/>
</TEI>

The remainder of this document describes each of these aspects in more detail, using material derived from the P5 release of the TEI Guidelines.

Manuscript Description Metadata

Each distinct manuscript must be described using a distinct TEI-conformant <teiHeader> element, as specified in the TEI Guidelines, chapter 2. This element may contain many components, depending on the needs of the creator, which may be provided in either structured or (relatively) unstructured form. For Manuscriptorium purposes, the following components of the TEI Header must be provided, and must conform to the constraints specified here.

Other header components, if present, will be ignored by Manuscriptorium; they will be retained for storage in the system and returned on request, but their content is not processed for any purpose, including access.

The following example shows the minimal required structure:

<teiHeader>
<fileDesc>
<titleStmt>
<title>[Title of manuscript]</title>
</titleStmt>
<publicationStmt>
<distributor>[name of data provider]</distributor>
<idno>[project-specific identifier]</idno>
</publicationStmt>
<sourceDesc>
<msDesc xml:id="ex5" xml:lang="en"/>
</sourceDesc>
</fileDesc>
<revisionDesc>
<change when="2008-01-01"/>
</revisionDesc>
</teiHeader>

Taking these in turn,

- the title of the manuscript is used to identify it in short summary displays; it should correspond with the information used for the same purpose in the <head> element within the <msDesc> element below.
- the name of the data provider may be given in any conventional form but should be consistent across all data provided.
- the project-specific identifier has two parts: it consists of the short alphabetic code used to identify the partner (e.g. OCS for OUCS), followed by a four digit sequence number. For example, OCS0002 would be the second digital record contributed to the Manuscriptorium project by partner OCS. Note that this identifier has nothing to do with the manuscript shelfmark or other identifier. When ingesting records, Manuscriptorium will assume that if a record with this identifier already exists, the intention is to replace it.
- the manuscript description provided must follow the specification given in the remainder of this section.
- at least one <change> element must be provided, providing the date that this record was last revised before being submitted. As elsewhere, dates must be provided in the ISO format yyyy-mm-dd. The content of the <change> element is free text, which may be used to indicate the scope of any revision and the person/s responsible for it.

The <msDesc> element is used to provide detailed information about a single manuscript. For ENRICH purposes, this must carry the attributes mentioned above, to supply a unique internal identifier for the manuscript, and to specify the language of its description respectively.

The value for @xml:id may be the same as the value supplied for the <idno> element in the <teiHeader>, or it may be some other project-specific identifier used for cross-reference. It should however be prefixed by an identifier for the partner concerned, so as to avoid possible identifier collisions.

The value for @xml:lang, as elsewhere, must be supplied in the form of a valid language identifier (see below). If no value is supplied, the assumption is that the language of the description is English.

The <msDesc> element has the following component elements, each of which is further described in the remainder of this section.

The first of these components, <msIdentifier>, is mandatory; it is described in more detail in The Manuscript Identifier below. It is followed by either one or more paragraphs, marked up as a series of <p> elements, or one or more of the specialized elements <msContents> (Intellectual Content), <physDesc> (Physical Description), <history> (History), and <additional> (Additional information). These elements are all optional, but if used they must appear in the order given here. Finally, in the case of a composite manuscript, a full description may also contain one or more <msPart> elements (Manuscript Parts).

To demonstrate the variety of records which may be produced, consider the following sample manuscript description, chosen more or less at random from the Bodleian Library's Summary catalogue [Entry for Bodleian MS. Add. A. 61 in Madan et al. 1895-1953]

The simplest way of digitizing this catalogue entry would simply be to key in the text, tagging the relevant parts of it which make up the mandatory <msIdentifier> element, as follows:

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

With a suitable stylesheet, this encoding would be as readable as the original; it would not, however, be very useful for search purposes since only shelfmarks and other identifiers are distinguished by the markup. To improve on this, one might wrap the paragraphs in the appropriate special-purpose first-child-level elements of <msDesc> and use some additional phrase-level elements:

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

Such an encoding allows the user to search for such features as title, material, and date and place of origin; it is also possible to distinguish quoted material and Latin material from descriptive passages and to search within distinct parts of the description, for example, the manuscript history as distinct from its materials.

This process could be continued further, restructuring the whole entry so as to take full advantage of many more encoding possibilities:

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

Phrase-level Elements

Phrase-level elements are XML elements that can appear at the same hierarchic level as text in many parts of the digital record. Some of these are specialized, in that they may be used only within particular contexts; others may be used in any context (see ). Within the components of the <msDesc> element, the following specialized phrase level elements are available:

Origination

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

The <origDate> and <origPlace> elements are used to indicate the date and place of origin of a manuscript or manuscript part. Such information will usually appear within the <history> element, discussed in section History, but can also appear within other parts of the manuscript description, such as its decoration or binding, when these are not of the same date as the manuscript itself. Both these elements are members of the att.editLike class, from which they inherit the following attributes:

The <origDate> element is a member of the att.datable class, and may thus also carry the following attributes:

Material

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

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

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

Watermarks and Stamps

Two further elements are provided to mark up other decorative features characteristic of manuscript leaves and bindings:

These elements may appear wherever a term regarded as significant by the encoder occurs. The <watermark> element is most likely to be of use within the <support> element discussed in Support below. We give a simple example here:

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

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

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

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

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

Dimensions

The <dimensions> element can be used to specify the size of some aspect of the manuscript.

The <dimensions> element will normally occur within the element describing the particular feature or aspect of a manuscript whose dimensions are being given; thus the size of the leaves would be specified within the <support> or <extent> element (part of the <physDesc> element discussed in Object Description), while the dimensions of other specific parts of a manuscript, such as accompanying materials, binding, etc., would be given in other parts of the description, as appropriate.

The @type attribute on the <dimensions> element is used to specify more exactly the item being measured. For ENRICH purposes, this attribute must take one of the following values: "leaf", "binding", "slip", "written", "boxed".

The following three elements are available within the <dimensions> element: Each of these elements, if present, must be given in the order specified.

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

Attributes @min, @max, and @scope are used only when the measurement applies to several items, for example the size of many or all the leaves in a manuscript; attributes @atLeast and @atMost are used when the measurement applies to a single item, for example the size of a specific codex, but has had to be estimated. Attribute <quantity> is used when the measurement can be given exactly, and applies to a single item; this is the usual situation. The units in which dimensions are measured should always be specified using the @unit attribute, which will normally be taken from a closed set of values appropriate to the project, using standard units of measurement wherever possible. In the ENRICH project the following values are permitted: "cm", "mm", "in", "line", "char". If the only data available for the measurement uses some other unit, or it is preferred to normalize it in some other way, then it may be supplied as a string value using the @extent attribute.

The content of these elements, if present, simply copies the way that the measurement is presented in some source text; it may be omitted.

In the simplest case, only the @extent attribute may be supplied: <width extent="6 cubit">six cubits</width> More usually, the measurement will be normalised into a value and an appropriate SI unit: <width quantity="270" unit="cm">six cubits</width> Where the exact value is uncertain, the attributes @atLeast and @atMost may be used to indicate the upper and lower bounds of an estimated value: <width atLeast="250" atMost="300" unit="cm">six cubits</width>

It is often convenient to supply a measurement which applies to a number of discrete observations: for example, the number of ruled lines on the pages of a manuscript (which may not all be the same), or the diameter of an object like a bell, which will differ depending where it is measured. In such cases, the @scope attribute may be used to specify the observations for which this measurement is applicable: <height unit="lines" scope="most" atLeast="20"/> This indicates that most pages have at least 20 lines. The attributes @min and @max can also be used to specify the possible range of values: for example, to show that all pages have between 12 and 30 lines: <height unit="lines" scope="all" min="12" max="30"/>

The <dimensions> element may be repeated as often as necessary, with appropriate attribute values to indicate the nature and scope of the measurement concerned. For example, in the following case the leaf size and ruled space of the leaves of the manuscript are specified:

<dimensions type="written" unit="mm">
 <height scope="most" quantity="90" unit="mm"/>
 <width scope="most" quantity="48" unit="mm"/>
</dimensions>
<dimensions type="leaf">
 <height min="157" max="160" unit="mm"/>
 <width quantity="105" unit="mm"/>
</dimensions>

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

References to Locations within a Manuscript

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

The <locus> element is used to specify the location in the manuscript occupied by the element within which it appears. It should be supplied as the first component of an <msItem> element, or of any of the more specific elements appearing within one (see further section Intellectual Content below, in order to specify the location of that item within the manuscript being described.

A <locus> element can be used to identify any reference to one or more folios within a manuscript, wherever such a reference is appropriate. Locations are conventionally specified as a sequence of folio or page numbers, but may also be a discontinuous list, or a combination of the two. This specification should be given as the content of the <locus> element, using the conventions appropriate to the individual scholar or holding institution, as in the following example:

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

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

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

If a digital image is available for the locus described by the <locus> element, then the @facs attribute should be used to associate it with that image, as in the following example:

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

Usually, the @facs attribute points directly to a <surface> element within the <facsimile> element associated with the manuscript description, as further discussed in section Metadata about digital facsimiles below. It is also possible, but not recommended, to use this attribute to point to images of the relevant pages held in some other external image archive.

Where a transcription of the relevant pages is also available, this may be pointed to using the @target attribute, as in the following example:

    <msItem n="1">
      <locus target="#f1r #f1v #f2r">ff. 1r-2r</locus>
      <author>Ben Jonson</author>
      <title>Ode to himself</title>
      <rubric rend="italics">
       An Ode<lb/> to him selfe.</rubric>
      <incipit>Com leaue the loathed stage</incipit>
      <explicit>And see his chariot triumph ore his wayne.</explicit>
      <bibl><name type="person">Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl>
    </msItem>

<pb xml:id="f1r"/>

<pb xml:id="f1v"/>

<pb xml:id="f2r"/>

Where a manuscript contains more than one foliation, the @scheme attribute may be used to distinguish them. For example, MS 65 Corpus Christi College, Cambridge contains two fly leaves bearing music. These leaves have modern foliation 135 and 136 respectively, but are also marked with an older foliation. This may be preserved in an encoding such as the following:

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

Here the @scheme attribute points to a <foliation> element providing more details about the scheme used, as further discussed in Foliation below.

Names of Persons, Places, and Organizations

The standard TEI element <name> may be used to identify names of any kind occurring within a description: As further discussed in , this element is a member of the TEI class att.canonical, from which it inherits the following attributes:

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

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

Note that the <name> element is defined as providing information about a name, not the person, place, or organization to which that name refers. In the last example above, the @ref attribute is used to associate the name with a more detailed description of the person named. This is provided by means of the <person> element, which is also available in the ENRICH schema. An element such as the following might then be used to provide detailed information about the person indicated by the name:

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

</person>

Note that an instance of the <person> element must be provided for each distinct @ref value specified. In the example above, the value "HOC001" must be found as the @xml:id attribute of some <person>; the same value will be used as the @ref attribute of every reference to Hoccleve in the document (however spelled), but there will only be one <person> element with this identifier.

Alternatively, the @key attribute may be used to supply an identifying code for the person referenced by the name independently of both the existence of a <person> element and the use of the standard URI reference mechanism. If, for example, a project maintains as its authority file some non-digital resource, or uses a database which cannot readily be integrated with other digital resources for this purpose, the unique codes used by such offline resources may be used as values for the @key attribute. Although such practices clearly reduce the interchangeability of the resulting encoded texts, they may be judged more convenient or practical in certain situations.

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 people referenced by the set of manuscripts being described, in much the same way as a <listBibl> element in the back matter may be used to hold bibliographic information for all the works referenced.

Similar mechanisms are used to maintain and reference canonical lists of places or organizations.

Catchwords, Signatures, Secundo Folio

The <catchwords> element is used to describe one method by which correct ordering of the quires of a codex is ensured. Typically, this takes the form of a word or phrase written in the lower margin of the last leaf verso of a gathering, which provides a preview of the first recto leaf of the successive gathering. This may be a simple phrase such as the following: <catchwords>Quires signed on the last leaf verso in roman numerals.</catchwords> Alternatively, it may contain more details:

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

The Signatures element is used, in a similar way, to describe a similar system in which quires or leaves are marked progressively in order to facilitate arrangement during binding. For example:

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

The <signatures> element can be used for either leaf signatures, or a combination of quire and leaf signatures, whether the marking is alphabetic, alphanumeric, or some ad hoc system, as in the following more complex example:

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

The <secFol> element (for secundo folio) is used to record an identifying phrase (also called dictio probatoria) taken from a specific known point in a codex (for example the first few words on the second leaf). Since these words will differ from one copy of a text to another, the practice originated in the middle ages of using them when cataloguing a manuscript in order to distinguish individual copies of a work in a way which its opening words could not. <secFol>(ando-)ssene in una villa</secFol>

Heraldry

Descriptions of heraldic arms, supporters, devices, and mottos may appear at various points in the description of a manuscript, usually in the context of ownership information, binding descriptions, or detailed accounts of illustrations. A full description may also contain a detailed account of the heraldic components of a manuscript independently considered. Frequently, however, heraldic descriptions will be cited as short phrases within other parts of the record. The phrase level element <heraldry> is provided to allow such phrases to be marked for further analysis, as in the following examples:

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

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

The Manuscript Identifier

The <msIdentifier> element is intended to provide an unambiguous means of uniquely identifying a particular manuscript. This may be done in a structured way, by providing information about the holding institution and the call number, shelfmark, or other identifier used to indicate its location within that institution. Alternatively, or in addition, a manuscript may be identified simply by a commonly used name.

A manuscript's actual physical location may occasionally be different from its place of ownership; at Cambridge University, for example, manuscripts owned by various colleges are kept in the central University Library. Normally, it is the ownership of the manuscript which should be specified in the manuscript identifier, while additional or more precise information on the physical location of the manuscript can be given within the <adminInfo> element, discussed in section Administrative information below.

The following elements are available within <msIdentifier> to identify the holding institution:

Only one of each of the elements listed above may appear within the <msIdentifier> and they must, if present, appear in the order given.

[Should we make country mandatory?]

These elements are all also members of the attribute class att.naming, from which they inherit the following attribute:

The following elements are used within <msIdentifier> to provide different ways of identifying the manuscript within its holding institution:

Major manuscript repositories will usually have a preferred form of citation for manuscript shelfmarks, including rules about punctuation, spacing, abbreviation, etc., which should be adhered to. Where such a format also contains information which might additionally be supplied as a distinct subcomponent of the <msIdentifier>, for example a collection name, a decision must be taken as to whether to use the more specific element, or to include such information within the <idno> element. For example, the manuscript formally identified as “El 26 C 0” forms a part of the Ellesmere (“El”) collection. Either of the following encodings is therefore feasible:

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

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

In the former example, the preferred form of the identifier can be retrieved by prefixing the content of the <idno> element with that of the <collection> element, while in the latter it is given explicitly. The advantage of the former is that it it simplifies accurate retrieval of all manuscripts from a given collection; the disadvantage is that encoded abbreviations of this kind may not be as immediately comprehensible. Care should be taken to avoid redundancy: for example

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

would clearly be inappropriate. Equally clearly,

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

might be considered helpful in some circumstances (if, for example, some of the items in the Ellsemere collection had shelfmarks which did not begin “El”)

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

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

In these examples, <msName> has been used to provide a common name other than the shelfmark by which a manuscript is known. Where a manuscript has several such names, more than one of these elements may be used, as in the following example:

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

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

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

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

Where manuscripts have moved from one institution to another, or even within the same institution, they may have identifiers additional to the ones currently used, such as former shelfmarks, which are sometimes retained even after they have been officially superseded. In such cases it may be useful to supply an alternative identifier using the <altIdentifier> element, which has a detailed structure similar to that of the <msIdentifier> element, and an additional attribute @type to indicate what kind of alternative identifier this is. Only the following possibilities are envisaged:

former
- former catalogue or shelf number
partial
- identifier of a previously distinct item
internal
- internal project identifier
other
- other unspecified identifier

<altIdentifier>
@type
"former"
former catalogue or shelf number
"partial"
identifier of a previously distinct item
"internal"
internal project identifier
"other"
unspecified

The following example shows a manuscript which had shelfmark II-M-5 in the collection of the Duque de Osuna, but which now has the shelfmark MS 10237 in the National Library in Madrid:

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

Alternatively, such information may be dealt with under <history> or <adminInfo>, except in cases where a manuscript is likely still to be referred to or known by its former identifier.

Cases of such changed or alternative identifiers should be clearly distinguished from cases of scattered manuscripts, that is to say manuscripts which although physically disjoint are nevertheless generally treated as single units. One well-known example is the Old Church Slavonic manuscript known as Codex Suprasliensis, substantial parts of which are to be found in three separate repositories, in Ljubljana, Warsaw, and St. Petersburg. This should be represented using three distinct <altIdentifier> elements, using the value "partial" on the type attribute to indicate that these three identifiers are not alternate ways of referring to the same physical object, but three parts of the same entity.

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

As mentioned above, the smallest possible description is one that contains only the element <msIdentifier>; good practice in all but exceptional circumstances requires the presence within it of the three sub-elements <settlement>, <repository>, and <idno>, since they provide what is, by common consent, the minimum amount of information necessary to identify a manuscript.

Intellectual Content

The <msContents> element is used to describe the intellectual content of a manuscript or manuscript part. It comprises either a series of informal prose paragraphs or a series of <msItem> elements, each of which provides a more detailed description of a single item contained within the manuscript. These may be prefaced, if desired, by a <summary> element, which is especially useful where one wishes to provide an overview of a manuscript's contents and describe only some of the items in detail.

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

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

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

<msContents>
<msItem n="1"><locus>fols. 5r -7v</locus>
<title>An ABC</title>
<bibl><title>IMEV</title> <biblScope unit="pages">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 unit="pages">3747</biblScope></bibl></msItem>
<msItem n="3"><locus>fol. 8v</locus><title>Truth</title>
<bibl><title>IMEV</title> <biblScope unit="pages">809</biblScope></bibl></msItem>
<msItem n="4"><locus>fols. 8v-10v</locus>
<title>Birds Praise of Love</title>
<bibl><title>IMEV</title> <biblScope unit="pages">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 unit="pages">16 &amp; 19</biblScope></bibl></msItem>
<msItem n="6"><locus>fols. 14r-126v</locus>
<title>Troilus and Criseyde</title>
<note>Bk. 1:71-Bk. 5:1701, with additional losses due to
mutilation throughout</note>
</msItem>
</msContents>

The <msItem> Element

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

These are the possible component elements of <msItem> .

If early printed material or incunables are described using this schema, the <msItem> should be used to record details of each distinct work contained by the incunable. In this situation, the following extra elements may be found useful to transcribe relevant details from the original titlepage: These elements are also available within the <msItem> element.

In addition, an <msItem> may contain nested <msItem> elements.

Untagged running text is not permitted directly within an <msItem>, unless it is given within a <p> element, in which case none of the other component elements listed above is permitted.

The elements <msContents>, <msItem>, <incipit>, and <explicit> are all members of the class att.msExcerpt from which they inherit the @defective attribute. This attribute can be used for example with collections of fragments, where each fragment is given as a separate <msItem> and the first and last words of each fragment are transcribed as defective incipits and explicits .

Authors and Titles

When used within a manuscript description, the <title> element should be used to supply a regularized form of the item's title, as distinct from any rubric quoted from the manuscript. If the item concerned has a standardized distinctive title, e.g. Roman de la Rose, then this should be the form given as content of the <title> element, with the value of the @type attribute given as uniform. If no uniform title exists for an item, or none has been yet identified, or if one wishes to provide a general designation of the contents, then a supplied title can be given, e.g. missal, in which case the @type attribute on the <title> should be given the value supplied.

Similarly, if used within a manuscript description, the <author> element should always contain the normalized form of an author's name, irrespective of how (or whether) this form of the name is cited in the manuscript. If it is desired to retain the form of the author's name as given in the manuscript, this should be given in the <docAuthor> element, or as a distinct <name> element, within the text at the point where it occurs.

Note that the @key or @ref attributes can be used, on titles and on author names as on names in general, to link the name to a more detailed description of the person or work concerned (see further Names of Persons, Places, and Organizations).

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

<author>Diogenes Laertius</author>
<respStmt>
<resp>in the translation of</resp>
<name type="person">Ambrogio Traversari</name>
</respStmt>

The <resp> element is also a member of the att.canonical class, from which it inherits the @key attribute. For ENRICH purposes, this may be used to supply a standard relationship code for the kind of responsibility concerned, as defined in the list maintained at :

<respStmt>
 <resp key="trl">přeložil</resp>
 <name type="person">John Enrich</name>
</respStmt>

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

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

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

Rubrics, Incipits, Explicits, and Other Quotations from the Text

It is customary in a manuscript description to record the opening and closing words of a text as well as any headings or colophons it might have, and the specialised elements <rubric>, <incipit>, <explicit>, <finalRubric>, and <colophon> are available within <msItem> for doing so, along with the more general <quote>, for recording other bits of the text not covered by these elements. Each of these elements has the same substructure, containing a mixture of phrase-level elements and plain text. A <locus> element can be included within each, in order to specify the location of the component, as in the following example:

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

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

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

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

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

Filiation

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

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

Text Classification

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

<msContents>
<msItem n="1" defective="false" class="#law">
<locus from="1v" to="71v">1v-71v</locus>
<title type="uniform">Jónsbók</title>
<incipit>Magnus m<ex>ed</ex> guds miskun Noregs
k<ex>onungu</ex>r</incipit>
<explicit>en<ex>n</ex> u<ex>ir</ex>da
þo t<ex>il</ex> fullra aura</explicit>
</msItem>
</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 (), as shown here:

<classDecl><taxonomy>

<category xml:id="law">
<catDesc>Laws</catDesc>
</category>

</taxonomy></classDecl>

[^1]

[^1: Should ENRICH define its own taxonomy for this purpose, or re-use an existing one?]

Languages and Writing Systems

The <textLang> element should be used to provide information about the languages used within a manuscript item. It may take the form of a simple note, as in the following example: <textLang mainLang="chu">Old Church Slavonic, written in Cyrillic script.</textLang>

<textLang>
@mainLang

For validation and indexing purposes, the @mainLang attribute muse be supplied: it takes the same range of values as the global @xml:lang attribute, on which see further . When a manuscript item contains material in more than one language, the @mainLang attribute should be used only for the chief language. Other languages used may be specified using the @otherLangs attribute as in the following example:

<textLang mainLang="chu" otherLangs="RUS HEL">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 both within the same manuscript, it might be preferable to use a more explicit identifier: <textLang mainLang="chu-Cyrs">Old Church Slavonic in Cyrillic script</textLang>

The form and scope of language identifiers recommended by these Guidelines is based on the IANA standard described at and should be followed throughout. Where additional detail is needed correctly to describe a language, or to discuss its deployment in a given text, this should be done using the <langUsage> element in the TEI Header, within which individual <language> elements document the languages used: see .

Note that the <language> element defines a particular combination of human language and writing system. Only one <language> element may be supplied for each such combination. Standard TEI practice also allows this element to be referenced by any element using the global @xml:lang attribute in order to specify the language applicable to the content of that element. For example, assuming that <language> elements have been defined with the identifiers fr (for French), la (for Latin), and de (for German), a manuscript description written in French which specifies that a particular manuscript contains predominantly German but also some Latin material, might have a <textLang> element like the following: <textLang xml:lang="fr" mainLang="de" otherLangs="la">allemand et latin</textLang>

Physical Description

Under the general heading physical description we subsume a large number of different aspects generally regarded as useful in the description of a given manuscript. These include:

- aspects of the form, support, extent, and quire structure of the manuscript object and of the way in which the text is laid out on the page (Object Description);
- the styles of writing, such as the way it is laid out on the page, the styles of writing, decorative features, any musical notation employed and any annotations or marginalia (Writing, Decoration, and Other Notations);
- and discussion of its binding, seals, and any accompanying material (Bindings, Seals, and Additional Material).

Most manuscript descriptions touch on several of these categories of information though few include them all, and not all distinguish them as clearly as we propose here. In particular, it is often the case that an existing description will include within a single paragraph, or even sentence, information for which we propose distinct elements. In this case, if rewriting is not an option, the existing prose must be marked up simply as a series of <p> 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 paragraphs addressing topics listed above and similar ones. Alternatively, it may act as a container for any choice of the more specialized elements described in the remainder of this section, each of which itself contains a series of paragraphs, and may also have more specific attributes. If the two ways are combined in a single description, care should be taken to avoid duplication and all paragraphs of generic description must precede the first of the more specialised elements.

Object Description

The <objectDesc> element is used to group together those parts of the physical description which relate specifically to the text-bearing object, its format, constitution, layout, etc. The @form attribute is used to indicate the specific type of writing vehicle being described: it must be supplied, and its value must be one of "codex", "scroll", "leaf", or "other". If no value is supplied, the value "codex" will be assumed.

<objectDesc>
@form
"codex"
a bound codex
"leaf"
a loose leaf
"scroll"
a scroll
"other"
any other format

The <objectDesc> element has two parts: a description of the support, i.e. the physical carrier on which the text is inscribed; and a description of the layout, i.e. the way text is organized on the carrier.

Taking these in turn, the description of the support is tagged using the following elements, each of which is discussed in more detail below:

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

The @form attribute on <supportDesc> is used to summarize briefly the materials used for the support. For ENRICH purposes, it must have one of the following values: "perg" (parchment), "chart" (paper), "mixed", "unknown".

<supportDesc>
@material
"perg"
parchment
"chart"
paper
"mixed"
mixture of paper and parchment, or other materials
"unknown"

Here is a simple example:

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

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

Support

The <support> element groups together information about the physical carrier. Typically, for western manuscripts, this will entail discussion of the material (parchment, paper, or a combination of the two) written on. For paper, a discussion of any watermarks present may also be useful. If this discussion makes reference to standard catalogues of such items, these may be tagged using the standard <ref> element as in the following example:

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

Extent

The <extent> element, defined in the TEI header, may also be used in a manuscript description to specify the number of leaves a manuscript contains, as in the following example: <extent>ii + 97 + ii</extent> Information regarding the size of the leaves may be specifically marked using the phrase level <dimensions> element, as in the following example, or left as plain prose.

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

Collation

The <collation> element should be used to provide a description of a book's current and original structure, that is, the arrangement of its leaves and quires. This information may be conveyed using informal prose, or any appropriate notational convention. Although no specific notation is defined here, an appropriate element to enclose such an expression would be the <formula> element, which is provided when the figures module is included in a schema. Here are some examples of different ways of treating collation:

<collation><p><formula>1-3:8, 4:6, 5-13:8</formula></p></collation>
<collation>
<p>There are now four gatherings, the first, second and fourth originally consisting of
eight leaves, the third of seven. A fifth gathering thought to have followed has left no trace.
<list>
<item>Gathering I consists of 7 leaves, a first leaf, originally conjoint with <locus>fol. 7</locus>,
having been cut away leaving only a narrow strip along the gutter; the others, <locus>fols 1</locus>
and <locus>6</locus>, <locus>2</locus> and <locus>5</locus>, and <locus>3</locus> and <locus>4</locus>,
are bifolia.</item>
<item>Gathering II consists of 8 leaves, 4 bifolia.</item>
<item>Gathering III consists of 7 leaves; <locus>fols 16</locus> and <locus>22</locus> are conjoint,
the others singletons.</item>
<item>Gathering IV consists of 2 leaves, a bifolium.</item>
</list></p>
</collation>
<collation><p>I (1, 2+9, 3+8, 4+7, 5+6, 10); II (11, 12+17, 13, 14, 15, 16, 18, 19).</p></collation>
<collation>
<p><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>
</p>
</collation>

Foliation

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

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

Where a manuscript contains traces of more than one foliation, each should be recorded as a distinct <foliation> element and optionally given a distinct value for its @xml:id attribute. The <locus> element discussed in References to Locations within a Manuscript can then indicate which foliation scheme is being cited by means of its @scheme attribute, which points to this identifier:

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

<locus scheme="#modern">ff 1-20</locus>

Condition

The <condition> element is used to summarize the overall physical state of a manuscript, in particular where such information is not recorded elsewhere in the description. It should not, however, be used to describe changes or repairs to a manuscript, as these are more appropriately described as a part of its custodial history (see Availability and Custodial History). When used solely to describe the condition of the binding, it should appear within the <bindingDesc> element (Binding Descriptions).

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

Layout Description

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

Where the <layout> element is used, the layout will often be sufficiently regular for the attributes on this element to convey all that is necessary; more usually however a more detailed treatment will be required. The attributes are provided as a convenient shorthand for commonly occurring cases, and should not be used except where the layout is regular. The value NA (not-applicable) should be used for cases where the layout is either very irregular, or where it cannot be characterized simply in terms of lines and columns, for example, where blocks of commentary and text are arranged in a regular but complex pattern on each page

The following examples indicate the range of possibilities:

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

Note that if (as in the last example above) no value is given for the @columns attribute, the assumption is that there is a single column of writing on each page.

<layout>
@columns

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

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

Writing, Decoration, and Other Notations

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

Writing

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

<handDesc>
<p>Written in a <term>late Caroline minuscule</term>; versals in a
form of <term>rustic capitals</term>; although the marginal and
interlinear gloss is written in varying shades of ink that are
not those of the main text, text and gloss appear to have been
copied during approximately the same time span.</p>
</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, this fact can be registered by using the @hands attribute, as in the following example:

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

Where more specific information about one or more of the hands identified is to be recorded, the <handNote> element should be used, as in the following example:

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

As the above example shows, the attributes @script and @scope are both required on <handNote>. For ENRICH purposes, the @script attribute must take one of the following values: "carolmin", "textualis", "cursiva", "hybrida", "humbook", "humcursiva", or "other", and the @scope attribute must take one of the following values: "sole", "major", "minor".

If early printed material or incunables are described using this schema, the <typeDesc> and <typeNote> elements may be used (in the same way as <handDesc> and <handNote>) to record information about the typefaces etc. of interest in the source. Both <typeDesc> and <handDesc> may be supplied, for example in the case where a printed work has been annotated by a number of hands.

The <locus> element, discussed in section References to Locations within a Manuscript, may be used to specify which parts of a manuscript are written by a given hand.

In addition, when a full or partial transcription of a manuscript is available in addition to the manuscript description, the <handShift> element described in can be used to link the relevant parts of the transcription to the appropriate <handNote> or <typeNote> element in the description: for example, at the point in the transcript where the second hand listed above starts (i.e. at folio 72v:4), we might insert <handShift new="#Eirsp-2"/>.

No <typeShift> element is proposed; if it is felt inappropriate to use <handShift> for this purpose, the generic <mileStone> may be used.

Decoration

It can be difficult to draw a clear distinction between aspects of a manuscript which are purely physical and those which form part of its intellectual content. This is particularly true of illuminations and other forms of decoration in a manuscript. We propose the following elements for the purpose of delimiting discussion of these aspects within a manuscript description, and for convenience locate them all within the physical description, despite the fact that the illustrative features of a manuscript will in many cases also be seen as constitutiing part of its intellectual content.

The <decoDesc> element may contain simply one or more paragraphs summarizing the overall nature of the decorative features of the manuscript, as in the following example:

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

Alternatively, it may contain a series of more specific typed <decoNote> elements, each summarizing a particular aspect or individual instance of the decoration present, for example the use of miniatures, initials (historiated or otherwise), borders, diagrams, etc. The scope of the description is indicated by the @type attribute which, for ENRICH purposes, must take one of the following values: "border", "diagram", "initial", "marginal", "miniature", "mixed", "paratext", "secondary", "other".

<decoNote>
@type
other
"border"
"diagram"
"initial"
"marginal"
"miniature"
"mixed"
"paratext"
"secondary"
"other"

Here is a simple example:

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

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

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

Musical Notation

Where a manuscript contains music, the <musicNotation> element may be used to describe the form of notation employed, as in the following example:

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

Additions and Marginalia

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

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

Bindings, Seals, and Additional Material

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

Binding Descriptions

The <bindingDesc> element contains a description of the state of the present and former bindings of a manuscript, including information about its material, any distinctive marks, and provenance information. This may 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:

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

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

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

Seals

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 paragraphs summarizing the overall nature of the seals, or may contain one or more <seal> elements.

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

Accompanying Material

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

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

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

History

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

The three components of the <history> element all have the same substructure, consisting of one or more paragraphs marked as <p> elements. Each of these three elements is also a member of the att.datable attribute class, itself a member of the att.datable.w3c class, and thus also carries the following optional attributes:

Information about the origins of the manuscript, its place and date of writing, should be given as one or more paragraphs contained by a single <origin> element; following this, any available information on distinct stages in the history of the manuscript before its acquisition by its current holding institution should be included as paragraphs within one or more <provenance> elements. Finally, any information specific to the means by which the manuscript was acquired by its present owners should be given as paragraphs within the <acquisition> element.

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

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

Here is a fuller example:

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

Additional information

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

The <surrogates> element should not be used to describe digital images of the manuscript since the <facsimile> element described in Metadata about digital facsimiles is provided for this purpose.

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.

Administrative information

The <adminInfo> element is used to hold information relating to the curation and management of a manuscript. This may be supplied using <note> element. Alternatively, different aspects of this information may be presented grouped within one of the following specialized elements:

The @status attribute of <availability> must take one of the following values: "free", "restricted", "unknown".

Record History

The <recordHist> element may contain either a series of paragraphs or a single <source> element. It is used to document the primary source of information for the record containing it, in a similar way to the standard TEI <sourceDesc> element within a TEI Header. If the record is a new one, made without reference to anything other than the manuscript itself, then it may be omitted, or simply contain a <p> element, as in the following example: <source><p>Directly catalogued from the original manuscript.</p></source>

Frequently, however, the record will be derived from some previously existing description, which may be specified using the <bibl> element, as in the following example:

<recordHist>
<source><p>Information transcribed from <bibl><title>The index of
Middle English verse</title><biblScope unit="pages">123</biblScope></bibl>.</p></source>
</recordHist>

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

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

  </listBibl>
</additional>

The <change> element within the <revisionDesc> element of the TEI Header should be used to document the revision history of the record. It should not be given within the <recordHist> element.

Availability and Custodial History

The <availability> element is another element also available in the TEI Header, which should be used here to supply any information concerning 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.

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

The <custodialHist> record is used to describe the custodial history of a manuscript, recording any significant events noted during the period that it has been located within its holding institution. It may contain either a series of <p> elements, or a series of <custEvent> elements, each describing a distinct incident or event, further specified by a @type attribute, and carrying dating information by virtue of its membership in the att.datable class, as noted above.

For ENRICH purposes, the values of this attribute must be one of the following: "check", "conservation", "description", "exhibition", "loan", "photography", "other".

<custEvent>
@type
"check"
"conservation"
"description"
"exhibition"
"loan"
"photography"
"other"

Here is an example of the use of this element:

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

Surrogates

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

The <surrogates> element should not be used to repeat information about representations of the manuscript available within published works; this should normally be documented within the <listBibl> element within the <additional> element. However, it is often also convenient to record information such as negative numbers or digital identifiers 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 be provided as prose paragraphs, within which identifying information about particular surrogates may be presented using the standard TEI <bibl> element, as in the following example:

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

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

For ENRICH purposes, information about digital images of the manuscript being described should be provided within the <facsimile> element discussed in section Metadata about digital facsimiles below rather than within the <surrogates> element.

Manuscript Parts

The <msPart> element may be used in cases where what were originally physically separate manuscripts or parts of manuscripts have been bound together and/or share the same call number.

Since each component of such a composite manuscript will in all likelihood have its own content, physical description, history, and so on, the structure of <msPart> is in the main identical to that of <msDesc>, allowing one to retain the top level of identity (<msIdentifier>), but to branch out thereafter into as many parts, or even subparts, as necessary. If the parts of a composite manuscript have their own identifiers, they should be tagged using the <idno> element, rather than the <msIdentifier> element, as in the following example:

<msDesc xml:id="ex3" xml:lang="en">
  <msIdentifier>
    <settlement>Amiens</settlement>
    <repository>Bibliothèque Municipale</repository>
    <idno>MS 3</idno>
    <msName>Maurdramnus Bible</msName>
  </msIdentifier>

  <msPart>
    <msIdentifier>
  <altIdentifier type="other">
    <idno>MS 6</idno>
  </altIdentifier>

    </msIdentifier>
  </msPart>
  <msPart>
    <msIdentifier>
  <altIdentifier type="other">
    <idno>MS 7</idno>
  </altIdentifier>

    </msIdentifier>
  </msPart>
  <msPart>
    <msIdentifier>
  <altIdentifier type="other">
    <idno>MS 9</idno>
  </altIdentifier>

    </msIdentifier>
  </msPart>

</msDesc>

Metadata about digital facsimiles

The <facsimile> element is used to describe the digital images of the manuscript being made available to the ENRICH project. It contains, as a minimum, one <surface> element for each distinct page image, which in turn specifies one or more <graphic> element. These elements are used as described in the TEI Guidelines, section11.1.

Here is a simple example:

<facsimile xml:base="http://www.handrit.org/AM/fol/">
        <surface xml:id="LSB-1r" ulx="0" uly="0" lrx="200" lry="300">
            <graphic mimeType="jpeg" xml:id="AM02-5000-1r" url="AM02-5000-1r.jpg"/>
            <graphic mimeType="jpeg" url="AM02-5000-1r-thumb.jpg" width="1in" decls="#thumb"/>
            <zone ulx="20" uly="20" lrx="70" lry="70">
            <graphic mimeType="jpeg" xml:id="AM02-5000-1r-det" url="AM02-5000-1r-det.jpg"/>
            </zone>
        </surface>
        <surface start="#LSB-1v" ulx="0" uly="0" lrx="200" lry="300">
            <graphic mimeType="jpeg" xml:id="AM02-5000-1v" url="AM02-5000-1v.jgp"/>
            <graphic mimeType="jpeg" url="AM02-5000-1v-thumb.jpg" decls="http://www.enrich.org/imageDescs#thumb"/>
        </surface>
    </facsimile>

The @xml:base attribute specifies the root URL, which will be prefixed to all URL values within the child elements of this <facsimile>.

This example defines only two pages. There are three images associated with the first page, which is represented by the <surface> element with unique identifier "LSB-1r", and two with the second, which has no identifier. Each image is represented by means of a TEI <graphic> element.

As well as acting as a container for the various images associated with a page, the <surface> element defines an abstract co-ordinate system which may be used when defining additional zones of interest on the page. In this example, the location of an initial letter on the page is defined, since we have a graphic representing this detail. The zone within which the initial letter falls is in the box defined by the co-ordinates (20,20,70,70) within a grid defined by the co-ordinates (0,0,200,300). Thus, if the surface depicted actually measured 200 by 300 mm, the initial letter would occupy a 50 X 50 mm square, with its upper left corner located 20 mm from the left and 20 mm from the top edges of the surface. Note however that the numbers used to express co-ordinates are not measurements in any specific units and should not be used to determine the actual image size, since these may in any case vary greatly: in our example, the first image is a full page scan, while the second is a thumbnail.

The @mimeType attribute is used to indicate the format of the graphic file itself, and may be any valid MIME type, as defined by the IANA, for example "jpeg", "png", "bmp", "tiff" etc.

The @decls attribute is used to indicate an external URI from which further metadata applicable to this image may be found. In this case we are assuming that there is a definition which can be used to indicate characteristics of a thumbnail image at the address indicated. Note that this must be given in full, since it would otherwise be interpreted as an address relative to the value of the @xml:base attribute on the parent <facsimile>.

[Alternatively, should we invent a type-like attribute which could be validated in the schema?]

The <desc> element within a <zone> may be used to supply additional information about that zone, in this example to describe what it contains. In the TEI scheme, full documentation of a facsimile and its contents is carried in other parts of the digital document, linked to it in either or both of the following ways:

- the @start attribute may be used on a <zone> or <surface>; it points to an element in the transcription the start of which coincides with the zone or surface concerned.
- the @facs attribute may be used, for example on the <msContents> or <msItem> element in a manuscript description, or on any element in the transcription, to point to the <surface> bearing the start of the matter in question.

To complete the above example, we might thus expect that the <msDesc> for this manuscript will contain something like the following:

<msItem>
    <locus facs="#LSB-1r">ff. 1r-1v</locus>
    <title>Ludovícuss saga Bernharðssonar</title>
</msItem>

Here, the value of the @facs attribute is a pointer to the <surface> element corresponding with the part of the manuscript in which the <msItem> specified begins. If a transcription of this (regrettably nonexistent) manuscript exists, then it might begin as follows:

<div facs="#LSB-1r">
   <pb n="1r"/>
   <p>Maðr hét Ludovícus, sonr Bernharðs greifa, er kallaðr var loðinbjörn.

   <pb n="1v" xml:id="LSB-1v"/>

   </p>
</div>

pointer to the <surface> element corresponding with the part of the manuscript at which the transcribed text begins.

Schema

att.global.linking

att.datable.iso

model.addrPart

<address>

<analytic>

<biblFull>

<biblStruct>

<binaryObject>

<cit>

<distinct>

<email>

<emph>

<equiv>

<headItem>

<headLabel>

<imprint>

<measure>

<measureGrp>

<meeting>

<mentioned>

<monogr>

<num>

<postBox>

<postCode>

<refsDecl>

<rs>

<said>

<series>

<soCalled>

<sp>

<speaker>

<stage>

<street>

<teiCorpus>

<time>

<table>

<cell>

<row>

<appInfo>

<application>

<broadcast>

<correction>

<cRefPattern>

<equipment>

<fsdDecl>

<hyphenation>

<interpretation>

<metDecl>

<metSym>

<namespace>

<normalization>

<quotation>

<recording>

<recordingStmt>

<rendition>

<samplingDecl>

<scriptStmt>

<segmentation>

<state>

<stdVals>

<tagUsage>

<tagsDecl>

<variantEncoding>

<ab>

<alt>

<altGrp>

<join>

<joinGrp>

<link>

<linkGrp>

<timeline>

<when>

<msItemStruct>

<climate>

<listNym>

<nym>

<terrain>

<argument>

<byline>

<closer>

<dateline>

<div1>

<div2>

<div3>

<div4>

<div5>

<div6>

<div7>

<docDate>

<epigraph>

<floatingText>

<imprimatur>

<opener>

<postscript>

<salute>

<signed>

<trailer>

<biblScope>
@unit
"volume"
"pages"

<gap>
@reason
gives the reason for omission of this material from the transcription.
"damage"
medium is damaged
"illegible"
material cannot be reliably read
"cancelled"
material can be read but has been cancelled by scribe
"irrelevant"
material is not regarded as relevant by the transcriber
"omitted"
material omitted by transcriber
"lacuna"
material missing from the source
@unit
names the unit used for describing the extent of the gap
"chars"
written characters
"leaves"
leaves
"lines"
lines
"mm"
millimetres
"pages"
pages
"words"
words

<hi>
@rend
"hyphenated"
"underline"
"double-underline"
"bold"
"caps"
"italic"
"sup"
"rubric"

<name>
@type
"person"
"place"
"org"
"unknown"

<handNote>
@script
"carolmin"
"textualis"
"cursiva"
"hybrida"
"humbook"
"humcursiva"
"other"
script other than one of these
"unknown"
script information not available
@scope
"sole"
"major"
"minor"

<altIdentifier>
@type
"former"
former catalogue or shelf number
"system"
former system identifier (Manuscriptorium specific)
"partial"
identifier of a previously distinct item
"internal"
internal project identifier
"other"
unspecified

<availability>
@status
"free"
"unknown"
"restricted"

<textLang>
@mainLang

<objectDesc>
@form
"codex"
a bound codex
"leaf"
a loose leaf
"scroll"
a scroll
"other"
any other format

<supportDesc>
@material
"perg"
parchment
"chart"
paper
"mixed"
mixture of paper and parchment, or other materials
"unknown"

<layout>
@columns

<msDesc>
@xml:id
@xml:lang

<decoNote>
@type
other
"border"
"diagram"
"initial"
"marginal"
"miniature"
"mixed"
"paratext"
"secondary"
"other"
"illustration"
"printmark"
"publishmark"
"vignette"
"frieze"
"map"
"unspecified"

<custEvent>
@type
"check"
"conservation"
"description"
"exhibition"
"loan"
"photography"
"other"

<person>
@sex

att.dimensions
@precision
@unit
mm
"cm"
"mm"
"in"
"lines"
"chars"

<dimensions>
@type
"leaf"
"binding"
"slip"
"written"
"boxed"
"unknown"

<region>
@type
"parish"
"county"
"compass"
"geog"
"state"
"unknown"

<supplied>
@reason
"omitted"
"illegible"
"damage"
"unknown"

<date>
You must provide either @when or @to/@from, or @notAfter/@notBefore.

att.global.rendition
@rendition

<recordHist>

<origPlace>

<msContents>

<surrogates>
contains information about any non-digital representations of the manuscript being described which may exist in the holding institution or elsewhere.