Whenever the <bibl> element is used, each
sub-component should be marked up explictly using a legal
sub-element. For example, instead of
<bibl>Grech
G. M. , 'The Manuscript Tradition of Peter of Auvergne's Unedited
Commentary on Aristotle's Politics', Angelicum 41 (1964),
pp. 444-445</bibl>
use
<bibl><author>Grech,
G.M</author><title level="a">The Manuscript Tradition of
Peter of Auvergne's Unedited Commentary on Aristotle's
Politics</title> <title level="m">Angelicum</title>
<biblScope type="volume">41</biblscope>
<date>1964</date><biblScope
type="pages">444-445</biblScope></bibl>
Appendix B2.1.1. biblScope
The following
values should be used for the
attribute within <biblScope>:-
volume
issue
pages
chapter
part
For
example:-
<biblScope
type="pages">444-445</biblScope>
Appendix B2.1.2. title
The attribute should be assigned a value
when the <title> element is used within a <bibl>. One of
the following values should be used:-
aanalytic title (article, poem, or
other items published as part of a larger
item)
mmonograph
j
journal title
s series
title
u unpublished
material
For example:-
<title
level="m">Angelicum</title>
Appendix B2.2. name
The names of the following classes of individuals
should be marked with the <name> element:
scribes
binders
owners
artists
scholars
The attribute of the <name>
element should be used to designate into which category the name
falls, (ie, "scribe", "binder", "owner", "artist", or "scholar"). The
attribute of <name> should
be used to record the authoritative form of the name. For
example:-
Use the attribute
for <country>, <region> and <settlement >within
<msIdentifier> to express the regularised form of the names of
these elements. Within the element itself, use your preferred form of
the name.For example:-
Within <msIdentifier> provide an <idNo>
element for the current shelfmark only, not for previous
shelfmarks. Do not use the
attribute
Appendix B3.3. collection
Do not use
the collection element within the <mdIdentifier> if the name of
the collection is incorporated into the <idNo> for the
item.For example, an entry for
<idNo>MS Rawlinson
poet. 223</idNo>
should not include a separate entry for
collection.
In general, use
the regularised form of an author's name within the <author>
element. throughout a manuscript description. Where the author is
known more widely by an alternative form of his/her name, use a
<name> element within <author>, and use the
<name> element's attribute
to hold the regularised form of the name. For example:-
<author><name reg="Christine, de Pisan,
ca. 1364-ca. 1431">Christine de Pizan,
ca. 1364-ca. 1431</name></author>
Appendix B4.1.2. title
Within the
<msItem>, give the uniform title for an item within the
<title> element. Do not use the attribute for the <title>
element.
When
referring to a surrogate using a <bibl> element, the
<title> sub-element, with the attribute set to "gmd", should be used to indicate the
form of surrogate being described. For example:-
If the elements <acquisition>,
<binding>, <custEvent>, <origDate>,
<origin>, or <provenance> refer to a datable event or
feature, the attributes and
should be used to mark the
beginning and end of the date range referred to: their values should
contain a date in the ANSI (yyyy-mm-dd) format. For
example:-
The following cataloguing rules have been proposed for use within the Master Project. This document is maintained at the Bodleian Master site, which should be checked for up to date information.
MASTER, by default,
will use the authority form for names, places and uniform titles given
in the Library of Congress authority list. This will be supplemented,
where there is no such name or place, by our own authority list.
This document is undergoing constant revision, as a consequence of
ongoing work within the MASTER Project and in response to public
comment and criticism. Please do not use or reference this document
without first checking that you have the most recent version. Versions
of this document are identified by date and version number, given at
the end of the table of contents.
This document is maintained in XML, using a partial
implementation of the TEI ODD2 system designed by Michael
Sperberg-McQueen and Lou Burnard. The XML source of the whole manual
is available from
http://www.hcu.ox.ac.uk/TEI/Master/Reference/Source/.
The HTML and PDF versions are generated from the XML source, as are the DTD
fragments which make up the DTD itself (see further section 3 Building the TEI DTD for Manuscript Description).
The manuscript descriptions DTD file contains formal definitions for any
standard TEI elements which have been changed, together with the
formal definitions of the additional elements documented here.
The file begins with a redefinition of the standard TEI
<sourceDesc> element, needed to make it possible for manuscript
descriptions to be included within the TEI Header as well as within
the body of a TEI document (the latter is achieved by virtue of making
the <msDescription> element a member of the
chunk). This is followed by the definitions given
elsewhere in this document.
(revised 21 Jun 01)
Edited by Lou Burnard for the MASTER Work Group.
Copyright TEI Consortium 2001
HTML/ms.html 0100644 0001750 0001750 00000005641 07416434621 011325 0 ustar lou lou
The Manuscript Description Element
Master Project
The MASTER Document Type Definition: reference manual
Four categories of additional information are provided for by the
scheme described here, grouped together within the <additional>
element described in this section.
<additional>
groups additional information relating to the
modern bibliography for a manuscript, its current curatorial status, and
and other associated materials.
<adminInfo>
contains information about the present
custody and availability of the manuscript, and also about the record description itself. 2.8.1 Administrative Information
<surrogates>
contains information about any digital or
photographic representations of the manuscript being described which
may exist in the holding institution or elsewhere. 2.8.2 Surrogates
<accMat>
contains details of any significant additional
material which may be closely associated with the manuscript being
described, such as non-contemporaneous documents or fragments bound in
with the manuscript at some earlier historical period.2.8.2 Surrogates
<listBibl>
lists bibliographic descriptions of publications relating to
the manuscript (standard TEI element)
None of the constituent elements of <additional> is
required. If any is supplied, it may appear once only; furthermore,
the order in which elements are supplied should be as specified above.
The <additional> element is formally defined as follows:
2.8.1 Administrative Information
A variety of information relating to the curation and management of
a manuscript may be recorded as simple prose narrative tagged using
the standard <p> element. Alternatively, different aspects of this
information may be presented grouped within one or more
of the following specialized elements:
<recordHist>
provides information about the source and
revision status of the parent manuscript description itself.
<custodialHist>
contains a description of a manuscript's custodial history, either
as running prose or as a series of dated custodial events.
<availability>
supplies information about the availability of a manuscript, for example any restrictions on its use or access, its copyright status, etc. (standard TEI element)
<remarks>
contains any comments or remarks not forming
part of the description proper, for use by the cataloguer.
<!-- to be supplied-->
2.8.1.1 Record History
The <recordHist> element, if supplied, must contain a
<source> element, followed by an optional series of
<change> elements.
<source>
describes the original source for the information contained with a manuscript description.
<change>
summarizes any change in the record history, specifying a date, a responsibility statement, and a description of the change (standard TEI element)
The <source> element is used to document the primary source
of information for the catalogue record containing it, in a similar
way to the standard TEI <sourceDesc> element within a TEI
Header. If the record is a new one, catalogued without reference to anything
other than the manuscript itself, then it may simply contain a <p>
element as in the following example:
<source><p>Directly catalogued from the original manuscript</p></source>
More usually however the record will be derived from some
previously existing catalogue, which may be specified using the
standard TEI <bibl> element, as in the following example:
<source><p>Information transcribed from
<bibl><title>IMEV</title><biblScope>1234</biblScope></bibl>
</p></source>
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>
<recordHist>
<source><p>Information transcribed from
<ref target="IMEV123">IMEV 123</ref>
</p></source>
</recordHist>
<!-- ... -->
<listBibl>
<bibl id="IMEV123">
<title>Index of Medieval Verse</title>
<!-- other bibliographic details for IMEV here -->
<biblScope>123</biblScope>
</bibl>
<!-- other bibliographic records relating to this manuscript here -->
</listBibl>
</additional>
The <change> element is a standard TEI element, which
may also appear within the <revisionDesc> element of the
standard TEI Header; its use here is intended to signal the
similarity of function between the two container elements. Where the
TEI Header should be used to document the revision history of the
whole electronic file to which it is prefixed, the <recordHist>
element may be used to document changes at a lower level, relating to
the individual description, as in the following example:
<!-- to be supplied -->
2.8.1.2 Availability and custodial history
The <availability> element is a standard TEI element,
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><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 the cataloguing
institution. It may contain either a series of paragraphs tagged with
the standard TEI <p> element, 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 datable class, as noted above.
<custEvent>
describes a single event during the custodial history of a manuscript or manuscript.
Attributes include
type
specifies the type of event, for example conservation, photography, exhibition, etc.
Datatype: CDATA
any convenient typology may be used
Default: #IMPLIED
Here is an example of the use of this element:
<custodialHist>
<custEvent type="conservation" notBefore="1961-03" notAfter="1963-02">
<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="transfer/dispatch" notBefore="1989-11-13" notAfter="1989-11-13" >
<p>Dispatched to Iceland 13 November 1989.</p></custEvent>
</custodialHist>
2.8.1.3 Cataloguer's notes
It may occasionally be convenient to include detailed comments or
notes which are not properly part of the manuscript description. The
<remarks> element is provided for this purpose.
<remarks>
contains any comments or remarks not forming
part of the description proper, for use by the cataloguer.
<remarks>
<p>Re ff. 33-36v: According to Leroquais, the feast of Corpus
Christi with its octave was instituted for Franciscans in 1319;
the hymn here is the standard Tantum ergo.</p>
<p> Re a photo: Yes, do one, since the manuscript is signed and dated!
How about f. 7v (nice cadelled initials, and f. 18 with Clare
has already been reproduced elsewhere).</p>
</remarks>
2.8.1.4 Formal definitions
The <adminInfo> element and its immediate component elements
are formally defined as follows:
2.8.2 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.
<surrogates>
contains information about any digital or
photographic representations of the manuscript being described which
may exist in 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, digital identifiers etc. for unpublished
collections of manuscript images maintained within the holding
institution, as well as to provide more detailed descriptive
information about the surrogate itself. Such information may 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:
Note the use of the specialised form of GMD (general material designation)
title to specify the kind of surrogate being documented.
At a later revision, the content of the <surrogates> element
is likely to be expanded to include elements more specifically
intended to provide detailed information such as technical details of
the process by which a digital or photographic image was made.
If the whole of a manuscript is being digitized, it should be contained
in a separate document which lists all the images using <div> etc. to
structure them. In such a case, the <msDescription> placed within
the teiHeader.
The <surrogates> element is formally defined as follows:
2.8.3 Accompanying material
The circumstance commonly arises where a manuscript has additional
material, not originally part of the manuscript, which is bound with
it or otherwise accompanying the manuscript. In cases where this
is clearly a distinct manuscript, the whole manuscript should be
treated as a composite manuscript and the additional matter described
in a separate <msPart> (see 2.9 Manuscript Parts below).
However, there are cases where the additional matter is not
self-evidently a distinct manuscript: it might be an important set of
notes by a later scholar or owner, or it might be a file of
correspondence relating to the manuscript. The <accMat>
element is provided as a holder for this kind of information:
<accMat>
contains details of any significant additional
material which may be closely associated with the manuscript being
described, such as non-contemporaneous documents or fragments bound in
with the manuscript at some earlier historical period.
Attributes include
type
further characterizes the accompanying material, for example as letter, note, paste-in, etc.
Datatype: CDATA
any convenient typology may be used
Default: #IMPLIED
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 &Aacute;rni Magn&uacute;sson's hand has been stuck to the
pastedown on the inside front cover; the text reads:
<q lang="IS">&THORN;idreks S&oslash;gu &thorn;essa hefi eg
feiged af Sekreterer Wielandt Anno 1715
i Kaupmanna h&oslash;fn. Hun er, sem eg sie, Copia af Austfirda
b&oacute;kinni (Eidag&aacute;s) en<expan>n</expan> ecki progenies
Br&aelig;dratungu bokarinnar. Og er &thorn;ar fyrer eigi i
allan<expan>n</expan> m&aacute;ta samhlioda
&thorn;<expan>eir</expan>re er Sr Jon Erlendz son hefer ritad fyrer
Mag. Bryniolf. &THORN;esse &THORN;idreks Saga mun vera komin fra Sr
Vigfuse &aacute; Helgafelle.</q></p>
</accMat>
The formal definition for the <accMat> element is as
follows:
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 more
structured <msItem> elements, each of which provides a more
detailed description of a single item contained within the manuscript.
<mscontents>
describes the intellectual content of a
manuscript or manuscript part either as a series of paragraphs or as a
series of structured manuscript items.
<msItem>
describes an individual work or item within the intellectual
content of a manuscript or manuscript part.
Attributes include
class
identifies the text types or classifications applicable to this
item
Datatype: IDREFS
One or more codes, each of which is used as the identifier for
a text classification element supplied in the TEI Header <textClass>
element.
Default: #IMPLIED
defective
indicates whether the item being described
is defective, i.e. incomplete.
Datatype: (yes|no|unk)
Yes, No, or Unknown
Default: no
In the simplest case, only a brief description may be provided, as
in the following example:
<msContents>
<p>A collection of Lollard sermons</p>
</msContents>
This description may of course be expanded to include any of the
TEI elements generally available within a <p> element, such as
<bibl> to mark bibliographic descriptions, or <list> for
a 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>239</biblScope></bibl></msItem>
<msItem n="2"><locus>fols. 7v -8v</locus>
<title lang="FRA">Lenvoy de Chaucer a Scogan</title>
<bibl><title>IMEV</title>
<biblScope>3747</biblScope></bibl></msItem>
<msItem n="3"><locus>fol. 8v</locus><title>Truth</title>
<bibl><title>IMEV</title> <biblScope>809</biblScope></bibl></msItem>
<msItem n="4"><locus>fols. 8v-10v</locus>
<title>Birds Praise of Love</title>
<bibl><title>IMEV</title> <biblScope>1506</biblScope></bibl></msItem>
<msItem n="5"><locus>fols. 10v -11v</locus>
<title lang="LAT">De amico ad amicam</title>
<title lang="LAT">Responcio</title>
<bibl><title>IMEV</title> <biblScope>16 & 19</biblScope></bibl></msItem>
<msItem n="6"><locus>fols. 14r-126v</locus>
<title>Troilus and Criseyde</title>
<note>Bk. 1:71-Bk. 5:1701, with additional losses due to
mutilation throughout</note>
</msItem>
</msContents>
Where the cataloguer wishes to describe only some of the manuscript
items in detail, the sequence of <msItem> elements should be
prefixed by an <overview> element (see section 2.6 Physical Description below) , giving a brief description of the whole content,
as in the following example:
<!-- to be supplied -->
2.5.1 ThemsItemelement
Any combination of the elements described in this section may be
used to record information about individual items within the
intellectual content of a manuscript or manuscript part. Each
discrete item should be encoded within a distinct <msItem>
element, and may be classified using the class
attribute.
The <msItem> element may not contain any untagged running
text. Instead, it may contain any number of any of the following elements,
given in any order:
<author>
identifies the primary author of the work or works contained in a manuscript.
Attributes include
attested
indicates whether the attribution is explicitly attested in the manuscript.
Datatype: yes|no|unk
Sample values include:
yes
the attribution is made on the basis of a claim in the ms.
added
the attribution is made on the basis of a claim added by a subsequent hand in the ms.
no
the attribution is made on the basis of other evidence.
unk
the attribution may or may not be attested in the ms.
Default: unk
accepted
indicates whether or not the authorship attribution is generally accepted.
Datatype: a|y|n|u
Sample values include:
a
the attribution is generally accepted as an attribution.
y
the attribution is generally accepted to be true.
n
the attribution is generally accepted to be false.
u
no claim is made concerning truth of the attribution.
Default: a
<bibl>
contains a conventional bibliographic description, for example of a modern edition of the item (standard TEI element)
<colophon>
contains the text of any colophon
attached to a particular manuscript item: that is, an inscription,
usually found at a break point such as the end of a text or codex,
usually containing information about the production of the manuscript,
such as the name of the scribe, the date and place of the copying, the
person who commissioned the copying, etc.
<decoNote>
contains a note describing either a
decorative component of a manuscript, or a fairly homogenous class of
such components.; see further 2.6.3 Decoration and binding
<explicit>
contains the text of any explicit attached
to a particular manuscript item, that is, the closing words of a text or a section of
a text, sometimes used as a kind of title, possibly followed by one or more rubrics or colophons.
Attributes include
type
specifies the type of explicit, e.g. whether it is a formal closing for the
work.
Datatype: CDATA
A typology has yet to be defined
Default: #IMPLIED
defective
indicates whether the explicit as given is defective, i.e. incomplete.
Datatype: (yes|no|unk)
Yes, No, or Unknown
Default: no
<incipit>
contains the text of any incipit
attached to a particular manuscript item, that is the opening words of
a text, frequently used as a form of identifier for it; it may be
preceded by one or more rubrics, and may be defective.
Attributes include
type
specifies the type of incipit, e.g. whether it introduces a work,
is biblical, legal, etc.
Datatype: CDATA
A typology has yet to be defined
Default: #IMPLIED
defective
indicates whether the incipit as given is defective, i.e. incomplete.
supplies a name and description for anyone other than an author credited with intellectual responsibility for some aspect of the item (e.g. an illustrator) (standard TEI element)
<rubric>
contains the text of any rubric or heading attached to a particular manuscript item, that is, a string of words whereby a
manuscript signals a text division (e.g. beginning, book, chapter, end)
which is in some way set off from the text itself, usually in red ink,or by use of different size or type of script, lining, or other such visual device.
.
Attributes include
type
specifies the type of rubric, e.g. whether it is at the start or end of
the item.
Datatype: CDATA
A typology has yet to be defined
Default: #IMPLIED
<summary>
contains a brief summary of the
contents of an item provided by the cataloguer
<textLang>
describes the languages and writing systems used by a
manuscript (as opposed to its description, which is described in the langUsage element)
The <title> element should be used to supply a regularized
form of the item's title, quite distinct from any rubric or incipit
quoted from the manuscript. If the item concerned has a standardized
or `uniform' title, then this should always be the
form preferred as content of the <title> element. If no uniform
title exists, or none has been yet identified, then the
type attribute on the <title> should be given
the value supplied. It is conventional to enclose such
supplied titles within square braces, but this will normally be done
by a stylesheet. Abbreviated `titles' such as
`IMEV 3747' may be tagged using the standard TEI
<ref> element, optionally including a pointer to a fuller
bibliographic description in a bibliography elsewhere, as further
discussed in section 2.8.1.1 Record History.
If supplied, the <author> element should generally
contain the normalised 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 may be tagged as a distinct <name> element,
nested within the <author> element with the
normalized form of the name on its reg
attribute. Alternatively, the normalized form of the name may be
supplied as the value of a reg attribute on the
<author> element. If value is supplied for either reg
or key attributes, then the content of the <author>
element is assumed to be a standardized form of name.
Note that the key attribute should be used, as on
names in general, to specify the identifier of a <person>
element carrying full details of the person concerned (see further
2.2.4 Names of persons, places, and organizations).
Each element within <msItem> has the same substructure,
containing any mixture of phrase-level elements and plain text. If a
<locus> element is included, in order to specify the location
of the component, then it should be given at the start of that
element, as in the following example:
<msContents>
<msItem><locus>f. 1-223</locus>
<author>Radulphus Flaviacensis</author>
<title>Expositio super Leviticum </title>
<note>cf. <bibl>Stegmüller, RB 7093</bibl></note>
<incipit><locus>f. 1</locus>
Forte Hervei monachi</incipit>
<explicit><locus>f. 223v</locus>
Benedictio salis et aquae</explicit>
</msItem>
</msContents>
In the following example, standard TEI editorial elements have been used to mark
the transcription of abbreviations etc. present in the original:
As indicated above, a manuscript item may itself contain further
nested items, for example where a title or description is supplied for
a group of works each of which also has its own rubric, as in the
following example:
<msItem>
<locus>ff. 17v, 21v, 34</locus>
<title>Charms numbered 1-3, consisting of
variously formed crosses with inscribed circles</title>
<msItem><locus>f. 17v</locus>
<rubric>Contra inimicos, 1</rubric>
<q>Si quis hoc signum super se portat nequid capi ab
inimico;<./q>
</msItem>
<msItem><locus>f. 21v</locus>
<rubric>Contra mortem subitam, 2</rubric>
<q>Qui hoc signum super se portat sine confessione non
morietur;</q></msItem>
<msItem><locus>f. 34</locus>
<rubric>Pro victoria, 3</rubric>
<q>Hoc signum misit deus Regi Tedeon; qui cum isto pugnat
victoriam habebit;</q></msItem>
</msItem>
One or more text classification or text-type codes may be
specified, either for the whole of a <msContents> element, or
for one or more of its constituent <msItem> elements, using the
class attribute as specified above. This attribute
should specify the identifier used for the appropriate classification
within the standard <classCode> element in the TEI Header, as
in the following example:
<!-- to be supplied -->
2.5.2 Formal definition
The <msContents> element and its constituents are formally defined as follows:
It is common practice to prefix a full manuscript description with
a brief prose characterization, title, or description, summarizing the
whole of the manuscript, which may be used as a kind of
`supplied title' or heading. A special purpose
<msHeading> element is provided for this purpose.
The <msHeading> element may simply hold
a short summary title, `heading', or
`tombstone' specifying a supplied title or heading
applicable to the whole of a manuscript, or
this
may be complemented with other elements.
The <msHeading> element and its constituents provide for the
inclusion of the following information in a structured form:
<msHeading>
contains a brief structured description of a manuscript.
<author>
identifies the primary author of the work or works contained in a manuscript.
<title>
supplies a title for the work or works contained in a manuscript,or a brief description of a
manuscript (standard TEI element)
<respStmt>
supplies a name and description for someone other than an author credited with intellectual responsibility for some aspect of the work or works within a manuscript (e.g. an illustrator) (standard TEI element).
<origPlace>
contains any form of place name, used to identify the
place of origin for a manuscript or manuscript part.
<origDate>
contains any form of date, used to identify the
date of origin for a manuscript or manuscript part.
<textLang>
describes the languages and writing systems used by a
manuscript (as opposed to its description, which is described in the langUsage element)
<note>
contains any additional descriptive information
about a manuscript (standard TEI element)
The constituents of a <msHeading> element may be repeated as
often as desired, in any order, and with embedded character data
between them, for example to supply any descriptive or interpretive
information about a manuscript which cannot be accomodated using more
specific elements because it covers more than one topic, or is not
otherwise catered for.
Here is a simple example:
<msHeading>
<author>Domenico Cavalca</author>
<title>Vite dei santi padri</title>
<origPlace>Naples</origPlace>
<origDate>1474</origDate>
</msHeading>
Here is a more complex example, showing how the <note>
and <respStmt> can be used to provide more detailed information
about the intellectual content of a manuscript:
<msHeading>
<author attested="no">Galterus de Castellione</author>
<title lang="LAT">Alexandreis</title>
<title lang="ENG">Alexander's saga</title>
<respStmt><resp>translated into Old Icelandic by</resp>
<name key="BRAJO1">Brandr J&oacute;nsson</name></respStmt>
<origPlace>Iceland</origPlace>
<origDate>s. XII ex</origDate>
<textLang>Old Norse/Icelandic</textLang>
<note>This is the principal manuscript of the saga and the basis
for all printed editions.</note>
</msHeading>
2.4.1 Languages and scripts
The <textLang> element should be used to provide
information about the languages used within a manuscript. It may take
the form of a simple note, as in the following example:
<textLang>Old Bulgarian, written in Cyrillic script.</textLang>
Where, for validation and indexing purposes, it is thought
convenient to add keywords identifying the particular languages used,
the langKey attribute may be used, as in the following
example:
<textLang langKey="OBG">Old Bulgarian, written in Cyrillic script.</textLang>
For this example to be valid, the identifier OBG
must also be predefined as the value of the ident attribute
on a <language> element in the TEI header associated with this
description.
<langUsage>
<language id="OBG">Old Bulgarian, written in Cyrillic script.</language>
<!-- other languages used or referenced in the manuscript description -->
</langUsage>
A manuscript will often contain material in more than one language. The
langKey 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 langKey="OBG" otherlangs="RUS HEL">
Mostly Old Bulgarian, with some Russian and Greek material</textLang>
Since Old Bulgarian may be written in either
Cyrillic or Glagolitic scripts, and even occasionally in both within the
same manuscript, it might be preferable to define identifiers which make
the distinction explicit. In such a case, the following <textLang>
element might be preferred:
<textLang otherLangs="OBG-CYR OBG-GLA">Old Bulgarian, written in
Cyrillic and Glagolitic scripts.</textLang>
and the following declarations might then be supplied in the <langUsage>
element of the associated TEI Header:
<langUsage>
<language id="OBG-CYR">Old Bulgarian, written in Cyrillic script.</language>
<language id="OBG-GLA">Old Bulgarian, written in Glagolitic script.</language>
<!-- other languages used or referenced in the manuscript description -->
</langUsage>
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 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 FRA (for
French), LAT (for Latin), and DEU (for
German), a manuscript description written in French which specifies
that a particular manuscript contains German material, might
have a <textLang> element like the following:
Until the elements described in this document, or similar ones,
have been formally integrated wih the rest of the TEI structure, their
use requires the definition of a TEI extension set, as defined in TEI
P3 (reference). This extension set comprises two files, called here
msDesc.ent and msDesc.dtd, the former
containing definitions of parameter entities needed for this set of
extensions, and the latter containing the actual SGML element and
attribute definitions which make up the required modifications.
The definitions here assume the availability of a number of elements
from other TEI tagsets, in particular the additional tagsets for
figures, names and dates, and manuscript transcription. With all
these in place, a complete TEI conformant document making use of the
manuscript description tagset will begin as follows:
This file, and others making up the DTD, are available from the URL
http://www.hcu.ox.ac.uk/TEI/Master/Reference/DTD/.
Both XML and SGML versions of a one-file DTD are available from the
same location.
The list of tag sets above makes available a large number of
standard TEI elements, not all of which are required for manuscript
description purposes, and which are therefore excluded from the Master
DTD. This exclusion is achieved by including in the extension entity
file the following set of parameter entity declarations:
The following elements are used to record information about the
history of a manuscript:
<history>
groups elements
describing the full history of a manuscript or manuscript part.
<origin>
contains any descriptive or other information
concerning the origin of a manuscript or manuscript part.
<provenance>
contains any descriptive or other information
concerning a single identifiable episode during the history of a manuscript
or manuscript part, after its creation but before its acquisition.
<acquisition>
contains any descriptive or other information
concerning the process by which a ms or ms part entered the holding
institution.
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 datable attribute class, and thus also carries the
following optional attributes:
notBefore
specifies the earliest possible date for the information in the
associated element.
Datatype: CDATA
Normalised dates should be specified in whatever standardised
form is defined by the TEI Header
Default: #IMPLIED
notAfter
specifies the latest possible date for the information in the
associated element
Datatype: CDATA
Normalised dates should be specified in whatever standardised
form is defined by the TEI Header
Default: #IMPLIED
evidence
specifies the kind of evidence for the dating
supplied by the other attributes.
Datatype: CDATA
Sample values include:
internal
the dating is based on evidence internal to the ms
(e.g. an inscription).
external
the dating is based on evidence external to the ms (e.g. a reference to the ms in some other datable context).
conjecture
the dating is based on conjecture, which may be further
discussed within the associated element.
Default: #IMPLIED
The history of a manuscript should normally be presented in the
order implied by the above description. Information about the origins
of the element (including any discussion of its sources) should be
given as one or more paragraphs contained by a single <origin>
element; any available information or discussion of distinct stages in
the history of the manuscript before its arrival in its current
location should be included as paragraphs within one or more
<provenance> elements following this. 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 simple example of the use of this element:
<history>
<origin><p>Written in Durham during the mid twelfth
century.</p></origin>
<provenance><p>Recorded in two medieval
catalogues of the books belonging to Durham Priory, made in 1391 and
1405.</p>
<p>Given to W. Olleyf by William Ebchester, Prior (1446-56)
and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)
according to inscriptions on ff. 4v and 5.</p>
</provenance>
<acquisition><p>Presented to Trinity College in 1738 by
Thomas Gale and his son Roger.</p></acquisition>
</history>
Here is a more realistic example:
<history>
<origin notBefore="1025" notAfter="1075" certainty="medium"
evidence="internal"><p>Written in Spain in the middle of the 11th
century (1042 according to the marginal note on f. 97v.)</p></origin>
<provenance><p>The Spanish scholar <name type="owner">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 lang="DAN">etatsr&aring;d</foreign> <name type="owner">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&aring;d</foreign>
<name type="owner">Jens Rosenkrantz</name> (1640-1695) when Parsberg's
library was auctioned off (23.10.1693).</p></provenance>
<acquisition><p>The manuscript was acquired by &Aacute;rni
Magn&uacute;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>
The <history> element and its immediate component elements
are formally defined as follows:
The primary purpose of manuscript description is to provide an
unambiguous means of identification for particular manuscript items
within a collection. The <msIdentifier> element is provided for
this purpose.
<msIdentifier>
contains the information required to identify
a given manuscript or manuscript part uniquely within its holding institution.
A full manuscript description may well contain many
<msidentifier> elements, since the discussion of one manuscript
may well involve the need to refer to others. For that reason, the
Master DTD permits the <msidentifier> element to appear
anywhere within any paragraph of the description. There is however
one place where this element is mandatory, and has a special
significance: it must be given as the very first component of a
<msDescription>, in which place it identifies the manuscript
being described.
A manuscript identifier typically has two parts, the first being
its catalogued location, and the second the name used for it within that
location. The location may be specified as a collection, located
within a repository, forming part of an institution whose primary
geographic location is within a city, itself located within a region
or country, or both. A manuscript may have alternative identifiers
additional to the one currently used, including informal names or old
shelfmarks which are retained even after they have been officially
superceded.
The `catalogued location' of a manuscript is the
place of ownership. A manuscript's exact physical location may
occasionally be different: for example, at Cambridge University,
manuscripts owned by different colleges may be physically located
within the Cambridge University Library. In such cases, the college
location should be specified in the manuscript identifier. Similarly,
a holding institution may wish to specify additional and more precise
physical location information within the <adminInfo> element
discussed in section 2.8.1 Administrative Information below.
The following elements are available within <msIdentifier>
to identify the physical location of a manuscript:
<country>
contains the name of a geo-political unit larger than or administratively
superior to a <region> (standard TEI element)
<region>
contains the name of a smaller geo-political unit, intermediate
between <country> and <settlement> (standard TEI
element)
<settlement>
contains the name of the smallest component of a
placename expressed as a hierarchy of geo-political or administrative
units (standard TEI element)
<institution>
contains the name of an
organization, such as a University or Library, within which a
manuscript repository is located.
<repository>
contains the name of a repository (usually
a distinct physical building) within which manuscripts are stored, forming part
of an institution.
<collection>
contains the name of a collection of
manuscripts, not necessarily located within a single repository.
These elements are all structurally equivalent to the standard TEI
<name> element with an appropriate value for its
type attribute; however the use of this `syntactic
sugar' enables the model for <msIdentifier> to be
constrained rather more tightly than would otherwise be
possible. Specifically, only one of each of the elements listed above
may appear within the <msIdentifier>; if present, they must
appear in the order given; and all of them except for the
<settlement> and <repository> element may be
omitted.
These elements are all also members of the standard TEI attribute class
names, which means that they can all bear attributes such
as reg to supply a regularized form of a name, or key
to specify a database or similar unique key for it, as further documented
in the TEI description of this class..
The following elements are used within <msIdentifier> to
provide the identification used for the manuscript:
<idno>
supplies the string of abbreviations and numbers, usually
referred to as the `call number', `shelfmark', `accession number', etc., that is
used to identify the item (standard TEI element)
Attributes include
type
<altName>
contains any form of alternative identifier used for
a manuscript, such as a former catalogue number, ocellus
nominum, or nickname.
Attributes include
type
further characterizes the alternative name, for example as
former catalogue number, nickname, etc.
Datatype: CDATA
any convenient typology may be used
Default: #REQUIRED
Major manuscript repositories will usually have a preferred
form of citation for manuscript shelfmarks, including strict 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 or repository name,
the cataloguer must decide whether or not to include this information
in both locations; it is required within <idno>. The
type attribute on the <idno> element may be used
to indicate when the format of the <idno> element is of some
kind other than that implied by the repository name
Note, in the preceding example, that the name of the collection
(Rawlinson) is not explicitly tagged, since it is implicit in the
standard form of the manuscript shelf mark. In the following example,
however, a collection name is useful:
<!-- to be supplied -->
Any number of <altName>
elements may also be used to supply alternative names used for the
manuscript, as in the following example:
Note the use of the globally available lang attribute
above to specify the language in which the content of an element is
supplied. This is a standard TEI facility, which the cataloguer may
find useful in certain environments (for example, when compiling a
single catalogue from a variety of originally different sources), and
which may safely be ignored in others.
The <msIdentifier> element and its constituents are formally
defined as follows:
An <msDescription> element may reasonably appear either
within the body or the header of a TEI conformant document. In the
former case, where the document being encoded is essentially a
collection of manuscript descriptions, the <msDescription>
element may be placed anywhere that a paragraph might appear. In the
latter case, where the description forms part of the metadata to be
associated with a digital representation of some manuscript original,
whether as a transcription, as a collection of digital images, or as
some combination of the two, then the <msDescription> should
appear within the <sourceDesc> element of the header.
The <msDescription> element has the following components, of
which only the first is mandatory. They are listed here, and discussed
in the associated section below.
an itemised list of the intellectual contents
of a manuscript or manuscript part, with bibliographic descriptions etc. as
appropriate; 2.5 Intellectual Content
<physDesc>
groups information providing a detailed
descriptions of all physical aspects of the manuscript or manuscript part (e.g. its
material, script, component parts, illustration, binding); 2.6 Physical Description
<history>
summarizes the known history of a manuscript or manuscript part:
its origin and provenance; 2.7 History
<additional>
groups other related information about a
manuscript, in particular, administrative information relating to
its current location, additional materials associated with it,
etc.; 2.8 Additional information
<msPart>
contains a nested description for a manuscript
fragment which is now regarded as forming part of the manuscript being
described, although physically distinct; 2.9 Manuscript Parts
In addition to the global attributes rend,
id, lang etc. available to all TEI elements, the
<msDescription> element carries a special purpose
attributes status and type:
<msDescription>
contains a description of a single identifiable
manuscript or manuscript part
Attributes include
status
specifies the compositional status of a manuscript or manuscript part.
Datatype: (uni|compo|frag|def|unknown)
Sample values include:
uni
unitary: the manuscript is a complete entity which
exists as a single unit.
compo
composite: the manuscript is a complete entity comprising multiple units of different origin.
frag
fragmentary: a leaf, a part of a leaf, or a manuscript from which the majority of leaves are missing.
def
defective: a ms from which a minority of the leaves are missing.
unknown
unknown or unstated.
Default: 'uni'
type
specifies the type of manuscript being described, for example as 'diploma', 'codex' etc.
Datatype: CDATA
Typology to be defined
Default: #IMPLIED
Here is a very simple example of a complete manuscript description:
Here is a slightly more ambitious
description for the same manuscript, using elements described in more
detail in the following sections.
<msDescription status="uni">
<msIdentifier>
<settlement>Oxford</settlement>
<repository>Bodleian Library</repository>
<idno>MS. Rawlinson poet. 149</idno>
</msIdentifier>
<msHeading>
<author>Geoffrey Chaucer</author>
<title>The Canterbury Tales</title>
<origDate notBefore="1450" notAfter="1475">1450-1475</origDate>
<origPlace reg="Wales: Pembroke">?Pembrokeshire (Wales)</origPlace>
<textLang langKey="ENG">Middle English</textLang>
</msHeading>
<msContents>
<msItem>
<title>The Canterbury Tales</title>
<rubric>The Tales of Canterbury</rubric>
<author>Geoffrey Chaucer</author>
<note>Mutilated at beginning and end: contains A431-I1092 in the Riverside
edition numbering</note>
</msItem>
</msContents>
<physDesc>
<form>
<p>Codex. </p>
</form>
<support>
<p>Parchment.</p>
</support>
<extent>136 folios
<dimensions><height>28</height><width>19</width></dimensions>
</extent>
<collation>
<p>Twenty-three quires of eight, of which only nine are not defective, and a
final (defective) quire of six.</ps></collation>
<layout ruledLines="38-74">
<p>Margined and ruled with crayon through fol. 51v , then in drypoint.
Single columns of 38-74 lines per page. </p></layout>
<msWriting hands="4">
<p>Four hands, varying between cursive anglicana (the first hand) and mixed
secretary (the fourth hand). The fourth hand is responsible for around
two-thirds of the manuscript, from fol. 45 to the end; the third hand wrote
only three lines and a few words on fol. 38r; the other two hands divide the
remainder of the manuscript up to fol. 45 between them.
</p></msWriting>
<additions><p>
A fifteenth-century note in the margin of fol. 114v.
</p>
</additions>
</physDesc>
<history>
<origin>
<p>On fol. 91r is a smudged copy of a bill or document with names of people
and places in Wales (Pembrokeshire, Bangor) and the date 1607</p>
</origin>
<acquisition>
<p>Left to the Bodleian by Richard Rawlinson in 1755.</p>
</acquisition>
</history>
<additional>
<adminInfo>
<recordHist>
<source><p>This description is derived from that made by Daniel W. Mosser
for the Canterbury Tales Project.</p></source>
</recordHist>
</adminInfo>
<surrogates>
<p>A rotograph copy of the manuscript was made for John Manly in the 1920s,
and a copy of this rotograph is available in microfilm as part of the
Manly/Rickert collection from the University of Chicago library. The
manuscript has been microfilmed more recently by the Bodleian. Digital
images derived from this microfilm have been published on the CDROMs
prepared by the Canterbury Tales Project.</p>
</surrogates>
</additional>
</msDescription>
The formal definition for the <msDescription> element is as
follows:
Under the general heading of `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 (2.6.1 Physical form of the whole ms); aspects of the writing,
such as the way it is laid out on the page, the styles of writing and
any musical notation employed (2.6.2 Writing and Notations); discussion of
decorative features of the manuscript, of any paratextual features
such as pagination, and of any annotations (2.6.3 Decoration and binding);
discussion of its binding and state of repair (2.6.4 Foliation, additions, and condition).
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 information for which
we propose distinct elements within a single paragraph, or even
sentence. The encoder must then decide whether to rewrite the
description using the structure proposed here, or to retain the
existing prose, marked up simply as a series of <p> elements,
directly within the <physDesc> element.
The <physDesc> element may thus be used in either of two
distinct ways: it may contain a series of paragraphs addressing topics
listed above and similar ones; or it may act as a container for any
choice of the more specialised elements described in the remainder of
this section, each of which itself contains a series of paragraphs,
and may also have more specific attributes. Note that the two ways should
not be combined within the same description.
<!-- example to be supplied -->
2.6.1 Physical form of the whole ms
The following elements should appear at the start of a structured
physical description in the order specified. They describe various
aspects relating to the format of the manuscript object, the material
of which it is composed, its size, and physical organization as a
sequence of leaves:
<form>
contains a description of the physical format of the manuscript.
<support>
contains a description of the written materials making up the manuscript item.
<extent>
describes the approximate size of the manuscript, specified in any convenient units.(standard TEI element)
<collation>
contains a description of how the leaves or bifolia are physically
arranged.
The <form> element may often contain only a single word or
phrase: at a later revision of this standard, it is possible that it
will be supplied as an attribute value. The <support> element,
by contrast, may contain a detailed prose description of the material
on which a manuscript is written. Phrase-level elements
may be used to tag specific terms of interest if so
desired: as in the following example the <material>, <ref>,
and <term> elements have been used for this purpose:
<form><p>codex</p></form>
<support>
<p>Mostly <material>paper</material>, with watermarks
<term>unicorn</term> (<ref>Briquet 9993</ref>) and
<term>ox</term> (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 <material>parchment</material>, and all
seven miniatures have been painted on inserted
singletons of <material>parchment</material>.</p>
</support>
If so desired, more specific paragraph-level elements may be used
to divide the components of the <support> element. Two such
elements are provided:
<overview>
contains the introductory section of any specialised component of a manuscript description.
<watermarks>
contains a detailed description of the watermarks identified in the paper of which a manuscript is composed.
The <overview> element may be used to enclose a general
discussion of the support, typically preceding a more detailed discussion,
as in the following example:
<!-- to be supplied -->
The <watermarks> element may be used to enclose discussion of
one or more watermarks; if this makes reference to standard catalogues of
such items, these may be tagged using the standard <ref> element
as in the following example:
<support><material>Paper</material>
<watermarks>Watermark: <term>anchor in a
circle with star on top</term>,
<term>countermark B-B with trefoil</term>
similar to <ref>Moschin, Anchor N 1680</ref>
<date>1570-1585</date>.</watermarks></support>
The <extent> element is principally a specification of the
number of leaves or bifolia a manuscript contains, but may also
contain any number of other measurements carried out on the
manuscript. Such measurements may be specifically marked using the
phrase level <dimensions> element, as in the following example,
or left as plain prose.
<extent>2 leaves, taken from the binding of a printed book</extent>
<extent>ii+321 leaves</extent>
<extent>37+212 leaves</extent>
Since the <dimensions> element is
available for use anywhere in a description, the cataloguer may choose
to discuss (for example) dimensions of miniatures at the
same time as describing the miniatures, rather than specify that information
within the <extent> element.
The <collation> element should be used to specify exactly
how the leaves or bifolia of a manuscript are combined into quires
etc. This may be described using informal prose, or any appropriate
notational convention. No specific notation is defined here as yet,
but provision is made for the tagging of such formul with the
standard TEI <formula> element as in the following example:
<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>
<catchwords>Catchwords are written horizontally in center
or towards the right lower margin in various manners:
in red ink for quires 1-6 (which are also signed in red
ink with letters of the alphabet and arabic numerals);
quires 7-9 in ink of text within yellow decorated frames;
quire 10 in red decorated frame; quire 12 in ink of text;
quire 13 with red decorative slashes; quire 14 added in
cursive hand.</catchwords>
</p></collation>
2.6.2 Writing and Notations
The second group of elements within a structured physical description
concerns aspects of the writing or other notation (notably, music) found
within a manuscript.
<layout>
contains a description of ruling technique and layout.
Attributes include
columns
specifies the number of columns per page
Datatype: CDATA
either a whole number or the string "NA" (not applicable)
Default: '1'
ruledLines
specifies the number of ruled lines per column
Datatype: CDATA
may be given as a pair of numbers (a range), as a whole number, or as
the string "NA" (not applicable)
Default: #IMPLIED
writtenLines
specifies the number of written lines per colum
Datatype: CDATA
may be given as a pair of numbers (a range), as a whole number, or as the string "NA" (not applicable)
Default: #IMPLIED
<msWriting>
contains a description of all the different kinds of writing used in a manuscript.
Attributes include
hands
specifies the number of distinct hands identified within the manuscript
Datatype: CDATA
A whole number, or the string "many"
Default: #IMPLIED
<handDesc>
describes a particular style
or hand distinguished within a manuscript.
Attributes include
scribe
gives a standard name or other identifier for the scribe
believed to be responsible for this hand.
Datatype: CDATA
'tremulous hand', 'Hoccleve', etc.
Default: #IMPLIED
script
characterizes the particular script or writing style used by
this hand.
Datatype: CDATA
'secretary', 'copperplate', 'Chancery', 'Italian', etc.
Default: #IMPLIED
medium
describes the tint or type of ink, e.g. 'brown', or other
writing medium, e.g. 'pencil',
Datatype: CDATA
Default: #IMPLIED
scope
specifies how widely this hand is used in the manuscript.
Datatype: (sole|major|minor)
Sample values include:
sole
only this hand is used throughout the manuscript
major
this hand is used through most of the manuscript
minor
this hand is used occasionally in the manuscript
Default: #IMPLIED
<musicNotation>
contains description of type of musical notation.
2.6.2.1 Layout
The <layout> element is used to describe and document the
way in which text and illustration are displayed on the written
surface, specifying for example the number of written, ruled, or
pricked lines and columns per page, presence or absence of margins,
distinct blocks such as glossaria etc. In some cases, the layout will
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 short
hand 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 characterised 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">
<p>Most pages have between 25 and 32 long lines ruled in lead.</p>
</layout>
2.6.2.2 Writing
The <msWriting> element may contain a short description of
the general characteristics of the writing observed in a manuscript
as in the following example:
<msWriting>
<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>
</msWriting>
Note the use of the <term> element to mark specific technical
terms within the context of the <msWriting> element.
Where several distinct hands have been identified, the cataloguer
may simply specify the fact using the hands attribute, as in
the following example:
<msWriting 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>
</msWriting>
Alternatively, or in addition, where more specific
information about one or more of the hands identified is to be recorded,
the <handDesc> element should
be used. Such hand descriptions may contain
prose and may also bear particular attributes to facilitate retrieval
as in the following example:
<handDesc><p>Written in insular phase II half-uncial
with interlinear Old English gloss in an Anglo-Saxon
pointed minuscule.</p></handDesc>
The <locus> element discussed in section 2.2.3 References to manuscript locations may be used to specify exactly which parts of a
manuscript are written by a given hand where this information is
included within the hand description. Alternatively, the standard TEI
<handShift> element may be used within the body of a
transcription to point to a <handDesc> element. Note that this
element replaces the existing TEI <hand> element, which has a
more restricted scope of application.
2.6.2.3 Musical notation
Finally, where a manuscript contains music or similar non-verbal
notation, the <musicNotation> element may be used to describe the
notation employed, as in the following example:
<musicNotation>
<p>Neumes in campo aperto of the St. Gall type.</p>
</musicNotation>
2.6.3 Decoration and binding
In describing a manuscript, it is often difficult or impossible to
draw a clear distinction between aspects which are purely physical and
aspects which contribute to the intellectual content. This is
particularly true of `decorative' aspects such as
illustrations and decorations within the manuscript or binding. We
propose the following elements for the purpose of delimiting
discussion of these aspects within a manuscript description, amd for
convenience locate them all within the physical description, despite
the fact that illustrative features in many cases may be better
thought of as part of the intellectual content, and thus better
described under the <msContents> element discussed in section
2.5 Intellectual Content.
<decoration>
contains a description of the decoration of a manuscript, either as a sequence of
paragraphs, or as a sequence of topically organised decoNote elements.
<decoNote>
contains a note describing either a
decorative component of a manuscript, or a fairly homogenous class of
such components.
Attributes include
type
specifies the kind of decorative feature being described
Datatype: CDATA
Any convenient typology may be used
Default: #IMPLIED
subtype
supplies a further sub-categorization of the value specified by the
type
attribute.
Datatype: CDATA
Any convenient typology may be used
Default: #IMPLIED
figurative
indicates whether the note concerns purely figurative aspects
of the decoration
Datatype: (yes|no|na)
Sample values include:
yes
figurative features are discussed
no
figurative features are not discussed
na
not applicable
Default: 'na'
technique
the note primarily concerns the technique or style
of the decorative features
Datatype: CDATA
Any convenient typology may be used
Default: #IMPLIED
quality
the note contains an assessment of the aesthetic quality
of the decorative feature
Datatype: CDATA
Any convenient typology may be used
Default: #IMPLIED
figurative
indicates whether the note concerns purely figurative aspects
of the decoration
Datatype: (yes|no|na)
Sample values include:
yes
figurative features are discussed
no
figurative features are not discussed
na
not applicable
Default: 'na'
illustrative
indicates whether the note concerns purely illustrative aspects of
the decoration
Datatype: (y|n|u)
Sample values include:
y
illustrative features are discussed
n
illustrative features are not discussed
u
unknown or inapplicable
Default: 'u'
<bindingDesc>
describes the present and former bindings of a manuscript, either
as a series of paragraphs or as a series of distinct binding elements,
one for each binding of the manuscript.
<binding>
contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript
Attributes include
contemporary
specifies whether or not the binding is contemporary with the majority of its contents
Datatype: (yes|no|unk)
Sample values include:
yes
the binding is contemporaneous with its contents
no
the binding is not contemporaneous with its contents
unk
the date of either binding or manuscript is unknown
Default: 'unk'
2.6.3.1 Decoration
The <decoration> element may contain simply one or more
paragraphs summarizing the overall nature of the descriptive features
of the manuscript, as in the following example:
<decoration>
<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>
</decoration>
Alternatively, it may contain a series of more specific typed
<decoNote> elements, each summarizing a particular aspect of
the decoration present, for example the use of miniatures, initials
(historiated or otherwise), borders, diagrams, etc., as in the
following example:
<decoration>
<decoNote type="miniature" technique="painted" figurative="yes">
<p>One full-page miniature, facing the beginning of the first Penitential Psalm.</p></decoNote>
<decoNote type="initial" technique="painted" figurative="yes">
<p>One seven-line historiated initial, commencing the first Penitential Psalm.</p>
</decoNote>
<decoNote type="initial" technique="painted" figurative="no">
<p>Six four-line decorated initials, commencing the second through the
seventh Penitential Psalm.</p></decoNote>
<decoNote type="initial" technique="pen-flourished" figurative="no">
<p>Some three hundred two-line versal initials with pen-flourishes,
commencing the psalm verses.</p></decoNote>
<decoNote type="border" technique="painted" figurative="no">
<p>Four-sided border decoration surrounding the miniatures and
three-sided border decoration accompanying the historiated and
decorated initals.</p></decoNote></decoration>
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:
<decoration>
<decoNote type="miniatures">
<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>
</decoration>
2.6.3.2 Binding
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-cent. pasteboards, reusing panels of 16th-cent. brown leather with
gilt tooling à la fanfare, Paris c. 1580-90, the centre of each
cover inlaid with a 17th-cent. 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>Bound, s. XVIII (?), in
<material>diced russia leather</material>
retaining most of the original 15th century
metal ornaments (but with some replacements)
as well as the heavy wooden boards;
<decoNote>on each cover: alternating circular stamps of the
Holy Monogram, a sunburst, and a flower;</decoNote>
<decoNote>on the cornerpieces, one of which is missing,
a rectangular stamp of the Agnus Dei;</decoNote>
rebacked during the 19th (?) century.
</binding>
2.6.4 Foliation, additions, and condition
The following elements are used to describe the remaining subdivisions
of the physical description:
<foliation>
describes the numbering system or systems used to
count the leaves or pages in a codex.
<condition>
contains a description of the physical
condition of the manuscript.
<additions>
contains a description of any significant additions found
within a manuscript, such as marginalia or other annotations.
2.6.4.1 Foliation
The <foliation> element describes one or more pagination schemes
applied to the manuscript. It should be used to indicate
the scheme of page numbers, folio numbers or column numbers provided
in the manuscript, as in the following examples:
<foliation>
<p>Folio numbers were added by &Aacute;rni Magn&uacurte;sson
ca. <date>1720-1730</date> with brown ink in the upper right corner
of all recto-pages.</p></foliation>
<foliation><p>Page numbers have been written with pen in the late
19th century on top of every ten recto-pages, to the right: 11,
21, 31, etc. Later, folio numbers have been written between
columns on top of every recto-page, in pencil.</p></foliation>
It may also include discussion of such
features as original signatures or catchwords, where relevant, as in the
following example:
<foliation>
<p>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 center 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).</p>
</foliation>
2.6.4.2 Additions and marginalia
The <additions> element is used to record and discuss any
written or drawn additional text found in a manuscript, such as
marginalia, scribblings, etc. which the cataloguer considers of
interest or importance. Such topics may also be discussed or
referenced elsewhere in a description, for example in the
<history> element where the marginalia provide evidence of
ownership, but the <additions> element is particularly useful
for this purpose.
<additions>
contains a description of any significant additions found
within a manuscript, such as marginalia or other annotations.
Here are some examples of the use of this element
<additions><p>In most parts of the codex the text has been quite
extensively corrected in a contemporary hand from the manuscript GKS
3270 4to.</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 &thorn; and has them drizzle down the
margin.</p>
</addition>
2.6.4.3 Condition
The <condition> element may be 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; these are more
appropriately described as a part of its custodial history.
<condition>
<p>The text begins and ends defective, and there are two lacunae toward
the end. What was originally the first leaf of the first quire,
numbered 1a, has been cut away, leaving a strip approximately 15 mm
wide; one to two letters, in some places on the verso up to four,
remain of each line. The manuscript contains a large number of
erasures, possibly by the scribe, possibly by a later hand, but in any
case for the most part unfilled in; for example on f. 3ra, lines 15-6
there are two erasures, the first of perhaps 16 the second of six
characters, and four lines of text have been erased on f. 5vb
following l. 21. In addition, there are several spaces that appear
never to have been filled in, e.g. f. 13vb, l. 24, where enough space
for about eight letters has been left blank by the scribe.
</p></condition>
2.6.5 Formal definitions
The formal definition for the <physDesc> element and its
constituents is as follows:
As noted above, the present DTD is constructed as an application of
the general TEI dtd. This implies the availability of a large number
of standard TEI elements, the majority of which are not documented
specifically here.
In particular, the following standard TEI elements may be included
within the body of any paragraph (<p>) element in a manuscript
description. (Note that this list includes some TEI elements specific
to manuscript transcription, which are not available in all
TEI-derived document type definitions).
<abbr>
(abbreviation) contains an abbreviation of any sort (specification)
<add>
(addition) contains letters, words, or phrases inserted in the text by an author, scribe, annotator or corrector. (specification)
<addSpan>
(added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector. (specification)
<bibl>
(bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. (specification)
<corr>
(correction) contains the correct form of a passage apparently erroneous in the copy text (specification)
<damage>
contains an area of damage to the text witness. (specification)
contains two dates or another phrase delimiting a time period. (specification)
<del>
(deletion) contains a letter, word or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, annotator or corrector (specification)
<delSpan>
(deleted span of text) marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector. (specification)
<expan>
(expansion) contains the expansion of an abbreviation. (specification)
<figure>
indicates the location of a graphic, illustration, or figure. (specification)
<foreign>
identifies a word or phrase as belonging to some language other than that of the surrounding text. (specification)
<formula>
contains a mathematical or other formula. (specification)
<fw>
(forme work) contains a running head (e.g. a `header', `footer'), catchword, or similar material appearing on the current page. (specification)
<gap>
(omitted material) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible or inaudible. (specification)
<gloss>
identifies a phrase or word used to provide a gloss or definition for some other word or phrase. (specification)
<handShift>
marks the beginning of a sequence of text written in a new hand, or of a change in the scribe, writing style, ink or character of the document hand. (specification)
<hi>
(highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. (specification)
<label>
contains the label associated with an item in a list; in glossaries, marks the term being defined. (specification)
<list>
contains any sequence of items organized as a list. (specification)
<listBibl>
(citation list) contains a list of bibliographic citations of any kind. (specification)
(number) contains a number, written in any form. (specification)
<orig>
(original form) contains the original form of a reading, for which a regularized form is given in an attribute value. (specification)
<ptr>
defines a pointer to another location in the current document in terms of one or more identifiable elements. (specification)
<q>
(quoted speech or thought) contains a quotation or apparent quotation. (specification)
<ref>
defines a reference to another location in the current document, in terms of one or more identifiable elements, possibly modified by additional text or comment (specification)
<reg>
(regularization) contains a reading which has been regularized or normalized in some sense. (specification)
<restore>
indicates restoration of text to an earlier state by cancellation of an editorial or authorial marking or instruction. (specification)
<sic>
contains text reproduced although apparently incorrect or inaccurate. (specification)
<space>
indicates the location of a significant space in the copy text. (specification)
<supplied>
contains text supplied by the transcriber or editor in place of text which cannot be read, either because of physical damage or loss in the original or because it is illegible for any reason. (specification)
<table>
contains text displayed in tabular form, in rows and columns. (specification)
<term>
contains a single-word, multi-word or symbolic designation which is regarded as a technical term. (specification)
<text>
contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample (specification)
<title>
contains the title of a work, whether article, book, journal, or series, including any alternative titles or subtitles. (specification)
<unclear>
contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. (specification)
Definitions, attribute specifications, and usage examples for all
the above elements are provided in the full TEI documentation and may
be found by following the links from the above list; they are not
discussed further within the present document.
In addition to these standard TEI elements, the Master DTD defines
a number of additional manuscript-specific elements which are
available within the content of any paragraph, wherever it appears
within a manuscript description. These elements are listed below in
alphabetical order:
contains any kind of dimensional specification. (2.2.2 Dimensions)
<heraldry>
contains a heraldic formula
or phrase occurring within such components as blazons, coats of arms, etc. found
within a manuscript . (2.2.6 Heraldry)
<locus>
defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references. (2.2.3 References to manuscript locations)
<material>
contains a phrase describing the material of which any part of a manuscript or binding is composed. (2.2.1 Origination and material)
<msIdentifier>
contains the information required to identify
a given manuscript or manuscript part uniquely within its holding institution. (2.3 The Manuscript Identifier)
contains any form of date, used to identify the
date of origin for a manuscript or manuscript part. (2.2.1 Origination and material)
<origPlace>
contains any form of place name, used to identify the
place of origin for a manuscript or manuscript part. (2.2.1 Origination and material)
<secFol>
The word or words that a cataloguer, typically medieval but possibly modern as well, might take from a fixed point in all the codices he is describing (the beginning of the second leaf, the beginning of the second column, the beginning of the penultimate leaf, the end of the penultimate leaf, and so on) in order to provide a unique identifier to the particular codex.
(2.2.5 Catchwords, signatures, secundo folio)
The <origDate> and <origPlace> elements are
specialised forms of the existing <date> and <name>
elements, used to indicate specifically date and place of origin
respectively. The <origDate> element is a member of the
datable class, and may thus also carry the following
attributes:
notBefore
specifies the earliest possible date for the information in the
associated element.
Datatype: CDATA
Normalised dates should be specified in whatever standardised
form is defined by the TEI Header
Default: #IMPLIED
notAfter
specifies the latest possible date for the information in the
associated element
Datatype: CDATA
Normalised dates should be specified in whatever standardised
form is defined by the TEI Header
Default: #IMPLIED
evidence
specifies the kind of evidence for the dating
supplied by the other attributes.
Datatype: CDATA
Sample values include:
internal
the dating is based on evidence internal to the ms
(e.g. an inscription).
external
the dating is based on evidence external to the ms (e.g. a reference to the ms in some other datable context).
conjecture
the dating is based on conjecture, which may be further
discussed within the associated element.
Default: #IMPLIED
Omission of the attributes notBefore and
notAfter, though permitted by the DTD, is deprecated within
the Master project.
As a specialisation of the <name> elemenmt, the <origPlace>
element has a reg attribute which may be used to supply
a regularized form of the place name.
Detailed information about the history of a manuscript should be
encoded within the <history> element discussed in section 2.7 History.
The <material> element may be used to tag any specific term used
for the material of which a manuscript is composed, wherever the term occurs.
2.2.2 Dimensions
The <dimensions> element is used to specify measurements,
and is thus a specialised form of the existing TEI <measure>
element.
<dimensions>
contains any kind of dimensional specification.
Attributes include
type
indicates which aspect of the object is being measured.
For manuscripts, example
values might include:
Datatype: CDATA
Sample values include:
leaves
dimensions relate to one or more leaves (e.g. a single leaf, a
gathering, or a separately bound part)
ruled
dimensions relate to the area of a leaf which has been ruled in
preparation for writing.
pricked
dimensions relate to the area of a leaf which has been pricked
out in preparation for ruling (used where this differs significantly
from the ruled area, or where the ruling is not measurable).
written
dimensions relate to the area of a leaf which has been written,
with the height measured from the top of the minims on the top line of
writing, to the bottom of the minims on the bottom line of writing.
miniatures
dimensions relate to the miniatures within the manuscript
binding
dimensions relate to the binding in which the codex or manuscript is contained
box
dimensions relate to the box or other container in which the
manuscript is stored.
Default: #IMPLIED
The <dimensions> may contain a simple description of the
measurements which have been made:
<dimensions type="leaves">
Most leaves are 140 x 100 mm. but the outer gatherings are about
5 mm. taller.</dimensions>
Where an institution-wide convention has been established
regarding the order in which measurements are to be supplied, their
units, etc. this element may contain a simple formula like the
following:
<dimensions>12 x 10 x 3</dimensions>
For portability, however, and where conventions differ, it may be
preferable to specify the units used, and it may also be useful to
specify exactly the dimension along which a measurement has been
made. For these reasons, the following three elements are available
within the <dimensions> element as an alternative to character
data:
<height>
contains a measurement measured along the axis parallel to the spine.
<width>
contains a measurement measured along the axis perpendicular to the spine.
<depth>
contains a measurement measured across the spine.
These elements are all members of the measured class,
and thus all carry the following attributes:
units
specifies the units used for this measurement.
Datatype: CDATA
The default, and
recommended, value is mm, i.e. millimetres.
Default: #IMPLIED
scope
specifies the applicability of this measurement to the containing
manuscript or manuscript part.
Datatype: (all|most|range)
Sample values include:
all
measurement applies to all instances in this manuscript or
manuscript part.
most
measurement applies to most instances in this manuscript or
manuscript part.
range
all the instances measured in this manuscript or manuscript part
are within the range specified.
Default: #IMPLIED
These elements may be given in any order, and may be repeated as
often as necessary, with appropriate values for their attributes 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:
This indicates that for most leaves of the manuscript being described
the ruled space is 90 mm high and 48 mm wide; the leaf size throughout
however is between 157 and 160 mm wide, and 105 mm high.
Dimensions of the manuscript being described should normally be
specified within the <extent> element (part of the
<physDesc> element discussed in 2.6.1 Physical form of the whole ms) rather
than elsewhere. Dimensions of specific parts of a manuscript, such as
accompanying materials, binding, etc. may however be given in other
parts of the description, as appropriate.
2.2.3 References to manuscript locations
The <locus> element is a specialized form of the <ref> element.
<locus>
defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references.
Attributes include
from
specifies the starting point of the location in a normalised form
Datatype: CDATA
typically this will be a page number
Default: #IMPLIED
to
specifies the end-point of the location in a normalized form
Datatype: CDATA
typically this will be a page number
Default: #IMPLIED
scheme
identifies the foliation scheme in terms of which the location is being specified
Datatype: CDATA
Identifies a foliation scheme, as further defined in the <foliation> element
Default: #IMPLIED
targets
supplies identifiers of associated page images
Datatype: IDREFS
a list of SGML identifiers, either of <figure> elements within a
transcript containing digitized page images, or of
<xptr> elements linked to such images
Default: #IMPLIED
The <locus> element is used to specify the location in the
manuscript occupied by the element within which it appears. If, for
example, it is used as the first component of a <msItem>
element, or of any of the more specific elements appearing within one
(see further section 2.5 Intellectual Content below) then it is understood
to specify the location of that item within the manuscript being
catalogued.
A <locus> element may be used to identify any reference to one or more
folios within a manuscript, 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 cataloguing
institution, as in the following example:
<msItem n="1"><locus>ff. 1r-24r</locus>
<title>Apocalypsis beati Ioannis Apostoli</title>
</msItem>
A normalised form of the location may also be
supplied, using special purpose attributes on the <locus>
element, as in the following revision of the above example:
<msItem n="1"><locus from="1r" to="24r">ff. 1r-24r</locus>
<title>Apocalypsis beati Ioannis Apostoli</title>
</msItem>
The targets attribute may be used to associate a
<locus> element with one or more other SGML elements in the
current document, which should contain either a transcription of the
location indicated, or page images of it, as in the following example:
<decoration>
<p>Most of the main body of the book (<locus targets="S1">up to
fol.182v</locus>) was painted and decorated in one style, having links
in style and iconography with the school of Ma&icirc;tre Francois,
although several of the miniatures in this section have been damaged
and overpainted at a later date (e.g. the figure of Christ on <locus
targets="F33R">fol. 33r</locus>; the face of the Shepherdess on <locus
targets="F59V">fol. 59v</locus>, etc.).</p>
</decoration>
The identifier S1 in this example is assumed to reference the section
of the manuscript ‘up to the fol.182v’ which has been transcribed elsewhere in
the current document; the identifiers F33R and F33R
will reference <figure> elements containing images of the indicated pages.
Where more than one foliation has been applied to a manuscript, the <locus> element may specify the folio number/s applicable in each foliation used, as in the following example:
<!-- to be supplied -->
2.2.4 Names of persons, places, and organizations
The standard TEI <name> element has attributes
type, reg and key, which
are used to indicate the type of name (e.g. personal name, placename
etc.), to provide a regularised form of the name, and to provide an
identifying code or key for it respectively. In addition to these
standard TEI facilities, the MASTER DTD also defines an additional
role attribute which may be used to specify more
exactly the role of a person named in a ms description.
<name>
contains a proper noun or noun
phrase.
Attributes include
type
indicates the type of thing being named.
Datatype: (person|female|place|org|other)
Sample values include:
person
names a person, gender unknown or unmarked
female
names a person, gender female
place
names a place
org
names an organization
other
names some other entity
Default: "person"
role
indicates the role of the
thing being named.
Datatype: CDATA
Typical values for the Master project include scribe,
binder,artist,owner,
scholar,translator,annotator,
compiler,adapter,dedicatee,
patron,commissioner
Default: #IMPLIED
reg
provides a regularized form of the name.
Datatype: CDATA
The form supplied should conform to local norms and should be taken
from an authority file
Default: #IMPLIED
key
supplies a reference to the
unique identifier used for some other
element, typically a <person>, which contains more detailed
information about the thing being named.
Datatype: IDREF
An element must exist elsewhere in the document with an id attribute
taking the value specified
Default: #IMPLIED
Here are some examples of the use of the <name> element:
Note that the <name> element is defined as providing
information about a name, not a person (or place). In
the last example above, the key attribute is used to
associate the name with a more detailed description of the person
named, provided elsewhere. This more detailed information about a
person is provided using the standard TEI element <person>.
<person>
provides structured biographical and other information
about any person referenced in a manuscript description.
Attributes include
role
specifies the chief role of the person (e.g. as author, scribe, owner etc.)
Datatype: CDATA
a set of keywords to be defined
Default: #IMPLIED
sex
specifies the sex of the person.
Datatype: (m | f | u )
Sample values include:
m
male
f
female
u
unknown or inapplicable
Default: "m"
age
specifies the age group to which the participant belongs.
Datatype: CDATA
suggested values are to be supplied
Default: #IMPLIED
For the Hoccleve example given above to be valid, a <person>
element must be provided elsewhere which has the value
HOCCL1 for its id attribute; the same
value will be used as the key attribute of every
reference to Hoccleve in the manuscript descriptions (however
spelled), but there will only be one <person> element with this
identifier.
All the <person> elements referenced by a particular
document set should be collected together within a <listPerson>
element, located elsewhere 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. (This element
is the same as the standard <particDesc> or participant
description element, but has been renamed within the Master DTD).
As used in the Master DTD, the <person> element may contain simply
one or more paragraphs of running prose, as in the following example:-
<person id="HOCC01" sex="m" role="scribe">
<p>Robert Hoccleve, born c.1368 in London, died in
Southwick c. 1450. Poet and tragedian, he lived in
Chester, and was for many years a Clerk, in the
office of the Privy Seal</p>
</person>
More usually however, individual parts of the information about a person
will be tagged using the following more specific elements:
<persName>
contains a proper noun or proper-noun phrase
referring to a person, possibly including any or all of the person's
forename, surname, honorific, added names, etc. (specification)
<birth>
contains information about a person's birth, in particular its date and place.
<death>
contains information about a person's death, notably its date and place.
<residence>
describes a
person's present or past places of residence (specification).
<occupation>
contains an informal description of a
person's trade, profession or occupation (specification).
The names used for the person should be given first, tagged with
the <persName> element, followed by a single <birth> and
<death> element, and then any number of <residence> or
<occupation> elements, one for each residence, or occupation
recorded for the person being described. Each element should use the
additional attributes provided by its membership in the
datable class, as discussed above (2.2.1 Origination and material); this is the preferred method of dating events
such as birth and death of a person. If an exact date is known for a
birth or death, it should be supplied on the date
attribute. In this case, the notBefore and
notAfter attributes need not be supplied, since all
attributes are then assumed to have the same value. Dates may also
be tagged within the body of these elements, as may names of places
(using the <placeName> element).
Here is more structured version of the previous example:
Note that the <persName> and <placeName> elements are
used only within a <person> element. Elsewhere, Master
recommended practice is to use the more general <name> element.
If a person has several distinct names (for example, a nickname), each
different name may be tagged, as in the following example:
<!-- to be supplied -->
2.2.5 Catchwords, signatures, secundo folio
The <secFol> element is used to discuss any
`secundo folio' information recorded for a manuscript as in
the following example:
<secFol>(ando-)ssene in una villa</secFol>
2.2.6 Heraldry
Heraldic descriptions may appear at various points in the description
of Western European early modern and medieval manuscripts, usually in the context
of ownership information, binding descriptions, or detailed accounts of
illustrations. If a description contains a detailed account of the heraldic
components of a manuscript independently considered, this should appear as
a distinct paragraph within the appropriate section of the
physical description. More usually, however, heraldic descriptions will
be cited as short phrases within other parts of the record. The phrase level
element <heraldry> is provided to enable the cataloguer to mark
such phrases for further subsequent analysis, as in the following examples:
Ownership stamp (xvii cent.) on i recto with the arms
<heraldry>A bull passant within a bordure bezanty,
in chief a crescent for difference</heraldry> [Cole],
crest, and the legend <q>Cole Deum</q>.'
<p>... partie sup. armoriée, de gauche à droite: armes de
France <heraldry>d'azur à 3 fleurs de lys d'or</heraldry>;
de Saint-Étienne de Dijon <heraldry>de gueules à 1
palme d'or, 2 caillous d'or en chef et 1 en pointe</heraldry>;
de Clément VII, antipape <heraldry>équipollé
d'or et d'azur</heraldry>, surmontées des clefs du
Saint-Siège; de Philippe le Hardi ou de Bourgogne-Valois
<heraldry>écartelé au 1er et 4e d'azur
à la fleur de lys d'or à la bordure componée d'argent
et de gueules, aux 2e et 3e, bandé d'or et d'azur de six
pièces à la bordure de gueules<heraldry>; non
identifiées <heraldry>de gueules à la bande d'or</heraldry>
</p>
2.2.7 Formal definitions
The additional phrase level elements are formally defined as follows:
The additional elements used within the <listPerson> element in
the TEI Header are defined as follows:
It is frequently the case that an item catalogued as if it were a
single object is in fact a composite made up of several different and
originally distinct manuscripts or manuscript fragments. Each such
component should be recorded using a distinct <msPart> element,
embedded within the <msDescription> element for the composite:
<msPart>
contains information about an originally distinct manuscript or manuscript fragment now forming part of a composite manuscript.
Each component of a composite manuscript may have its own content,
physical description, history, etc. It may have been given a distinct
identifier which it would be desirable to maintain. And finally, it is
not impossible that a composite be made from previously-existing
composites. For all these reasons, the <msPart> element used to
record information about an individual constituent of a composite
manuscript has an almost identical structure to that of a
<msdescription> proper. The main difference is that an
identifier must be supplied for a full manuscript description (using
the <msIdentifier> element), but is only optional in the case
of a manuscript part.
Here is a simple example of a composite manuscript, in which there
are two discrete components:
<msDescription>
<msIdentifier>
<!-- identifying information for the whole manuscript -->
</msIdentifier>
<msHeading>
<!-- short description of the whole manuscript -->
</msHeading>
<msPart>
<physDesc>
<!-- physical description of the first component part -->
</physDesc>
<msContent>
<!-- intellectual content of first component part -->
</msContent>
</mspart>
<msPart>
<physDesc>
<!-- physical description of the second component part -->
</physDesc>
<msContent>
<!-- intellectual content of second component part -->
</msContent>
</mspart>
</msDescription>
If the parts of a composite manuscript have
their own identifiers, they should be tagged using the <idno>
element, rather than the <msIdentifier> element. Whatever value
is specified should be appended to the <idno> specified in the
parent <msIdentifier> in order to obtain a full
identification for the part, as in the following example:
<msDescription>
<msIdentifier>
<settlement>Amiens</settlement>
<repository>Biblioth&egrave;que Municipale</repository>
<altName>Maurdramnus Bible</altName>
</msIdentifier>
<!-- other elements here -->
<msPart>
<idno>MS 6</idno>
<!-- other information specific to this part here -->
</msPart>
<msPart>
<idno>MS 7</idno>
<!-- other information specific to this part here -->
</msPart>
<msPart>
<idno>MS 9</idno>
<!-- other information specific to this part here -->
</msPart>
<!-- other msParts here -->
</msDescription>
The <msPart> element is formally defined as follows:
The MASTER Document Type Definition: reference manual
<accMat>
<accMat>
contains details of any significant additional
material which may be closely associated with the manuscript being
described, such as non-contemporaneous documents or fragments bound in
with the manuscript at some earlier historical period.
Attributes
type
further characterizes the accompanying material, for example as letter, note, paste-in, etc.
Datatype: CDATA
any convenient typology may be used
Default: #IMPLIED
Example
Class
Declaration
<!ELEMENT accMat- - (p+)>
<!ATTLIST accMat
%a.global;
type CDATA #IMPLIED>
The MASTER Document Type Definition: reference manual
<additional>
<additional>
groups additional information relating to the
modern bibliography for a manuscript, its current curatorial status, and
and other associated materials.
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
<additional>
<adminInfo>
<recordHist>
<!-- record history here -->
</recordHist>
<custodialHist>
<!-- custodial history here -->
</custodialHist>
</admininfo>
<surrogates>
<!-- information about surrogates here -->
</surrogates>
<accMat>
<!-- description of any accompanying materials here -->
</accMat>
<listBibl>
<!-- full bibliography here -->
</listBibl>
</additional>
The MASTER Document Type Definition: reference manual
<binding>
<binding>
contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript
Attributes
contemporary
specifies whether or not the binding is contemporary with the majority of its contents
Datatype: (yes|no|unk)
Sample values include:
yes
the binding is contemporaneous with its contents
no
the binding is not contemporaneous with its contents
unk
the date of either binding or manuscript is unknown
Default: 'unk'
Example
<binding contemporary="yes">
<p>Contemporary blind stamped leather over wooden
boards with evidence of a fore edge clasp closing
to the back cover.</p>
</binding>
Example
<bindingDesc>
<binding contemporary="no">
<p>Quarter bound by the Phillipps' binder, Bretherton,
with his sticker on the front pastedown.</p>
</binding>
<binding contemporary="no">
<p>Rebound by an unknown 19th c. company; edges cropped and
gilt.
</binding>
</bindingDesc>
The MASTER Document Type Definition: reference manual
<bindingDesc>
<bindingDesc>
describes the present and former bindings of a manuscript, either
as a series of paragraphs or as a series of distinct <binding> elements,
one for each binding of the manuscript.
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
<bindingDesc>
<p>Sewing not visible; tightly rebound over
19th-cent. pasteboards, reusing panels of 16th-cent. brown leather with
gilt tooling à la fanfare, Paris c. 1580-90, the centre of each
cover inlaid with a 17th-cent. 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>
The MASTER Document Type Definition: reference manual
<collation>
<collation>
contains a description of how the leaves or bifolia are physically
arranged.
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
<collation>
<p>The written leaves preceded by an original flyleaf,
conjoint with the pastedown.</p>
</collation>
Example
<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>
<catchwords>Catchwords are written horizontally in center
or towards the right lower margin in various manners:
in red ink for quires 1-6 (which are also signed in red
ink with letters of the alphabet and arabic numerals);
quires 7-9 in ink of text within yellow decorated frames;
quire 10 in red decorated frame; quire 12 in ink of text;
quire 13 with red decorative slashes; quire 14 added in
cursive hand.</catchwords>
</p></collation>
The MASTER Document Type Definition: reference manual
<colophon>
<colophon>
contains the text of any colophon
attached to a particular manuscript item: that is, an inscription,
usually found at a break point such as the end of a text or codex,
usually containing information about the production of the manuscript,
such as the name of the scribe, the date and place of the copying, the
person who commissioned the copying, etc.
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
<colophon>Ricardus Franciscus Scripsit Anno Domini 1447.</colophon>
<colophon>Explicit expliceat/scriptor ludere eat.</colophon>
The MASTER Document Type Definition: reference manual
<custodialHist>
<custodialHist>
contains a description of a manuscript's custodial history, either
as running prose or as a series of dated custodial events.
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
<custodialHist>
<custEvent type="conservation" notBefore="1961-03" notAfter="1963-02">
<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="transfer/dispatch" notBefore="1989-11-13" notAfter="1989-11-13" >
<p>Dispatched to Iceland 13 November 1989.</p></custEvent>
</custodialHist>
The MASTER Document Type Definition: reference manual
<decoNote>
<decoNote>
contains a note describing either a
decorative component of a manuscript, or a fairly homogenous class of
such components.
Attributes
type
specifies the kind of decorative feature being described
Datatype: CDATA
Any convenient typology may be used
Default: #IMPLIED
subtype
supplies a further sub-categorization of the value specified by the
type
attribute.
Datatype: CDATA
Any convenient typology may be used
Default: #IMPLIED
technique
the note primarily concerns the technique or style
of the decorative features
Datatype: CDATA
Any convenient typology may be used
Default: #IMPLIED
quality
the note contains an assessment of the aesthetic quality
of the decorative feature
Datatype: CDATA
Any convenient typology may be used
Default: #IMPLIED
figurative
indicates whether the note concerns purely figurative aspects
of the decoration
Datatype: (yes|no|na)
Sample values include:
yes
figurative features are discussed
no
figurative features are not discussed
na
not applicable
Default: 'na'
illustrative
indicates whether the note concerns purely illustrative aspects of
the decoration
Datatype: (y|n|u)
Sample values include:
y
illustrative features are discussed
n
illustrative features are not discussed
u
unknown or inapplicable
Default: 'u'
Example
<decoration>
<decoNote type="initial">
<p>The start of each book of the Bible with
a 10-line historiated illuminated initial;
prefaces decorated with 6-line blue initials
with red penwork flourishing; chapters marked by
3-line plain red initials; verses with 1-line initials,
alternately blue or red.</p>
</decoNote></decoration>
The MASTER Document Type Definition: reference manual
<decoration>
<decoration>
contains a description of the decoration of a manuscript, either as a sequence of
paragraphs, or as a sequence of topically organised <decoNote> elements.
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
<decoration>
<p>The start of each book of the Bible with a 10-line historiated
illuminated initial; prefaces decorated with 6-line blue initials with red
penwork flourishing; chapters marked by 3-line plain red initials; verses
with 1-line initials, alternately blue or red.</p>
</decoration>
The MASTER Document Type Definition: reference manual
<dimensions>
<dimensions>
contains any kind of dimensional specification.
Attributes
type
indicates which aspect of the object is being measured.
For manuscripts, example
values might include:
Datatype: CDATA
Sample values include:
leaves
dimensions relate to one or more leaves (e.g. a single leaf, a
gathering, or a separately bound part)
ruled
dimensions relate to the area of a leaf which has been ruled in
preparation for writing.
pricked
dimensions relate to the area of a leaf which has been pricked
out in preparation for ruling (used where this differs significantly
from the ruled area, or where the ruling is not measurable).
written
dimensions relate to the area of a leaf which has been written,
with the height measured from the top of the minims on the top line of
writing, to the bottom of the minims on the bottom line of writing.
miniatures
dimensions relate to the miniatures within the manuscript
binding
dimensions relate to the binding in which the codex or manuscript is contained
box
dimensions relate to the box or other container in which the
manuscript is stored.
Default: #IMPLIED
Example
<dimensions type="leaves">
<height scope="range">157-160</height>
<width>105</width>
</dimensions>
<dimensions type="ruled">
<height scope="most">90</height>
<width scope="most">48</width>
</dimensions>
<dimensions type="leaves">
Most leaves are 140 x 100 mm. but the outer gatherings are about
5 mm. taller.</dim>
<dimensions units="in">12 x 10 x 3</dimensions>
The MASTER Document Type Definition: reference manual
<explicit>
<explicit>
contains the text of any explicit attached
to a particular manuscript item, that is, the closing words of a text or a section of
a text, sometimes used as a kind of title, possibly followed by one or more rubrics or colophons.
Attributes
defective
indicates whether the explicit as given is defective, i.e. incomplete.
Datatype: (yes|no|unk)
Yes, No, or Unknown
Default: no
type
specifies the type of explicit, e.g. whether it is a formal closing for the
work.
Datatype: CDATA
A typology has yet to be defined
Default: #IMPLIED
Example
<explicit>sed libera nos a malo.</explicit>
<rubric>Hic explicit oratio qui
dicitur dominica.</rubric>
<explicit type="defective">ex materia quasi et forma sibi
proporti<gap></explicit>
<explicit type="reverse">saued be shulle that doome of day the at
</explicit>
The MASTER Document Type Definition: reference manual
<heraldry>
<heraldry>
contains a heraldic formula
or phrase occurring within such components as blazons, coats of arms, etc. found
within a manuscript .
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
Ownership stamp (xvii cent.) on i recto with the arms
<heraldry>A bull passant within a bordure bezanty,
in chief a crescent for difference</heraldry> [Cole],
crest, and the legend <q>Cole Deum</q>.'
The MASTER Document Type Definition: reference manual
<history>
<history>
groups elements
describing the full history of a manuscript or manuscript part.
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
<history>
<origin><p>Written in Durham during the mid twelfth
century.</p></origin>
<provenance><p>Recorded in two medieval
catalogues of the books belonging to Durham Priory, made in 1391 and
1405.</p>
<p>Given to W. Olleyf by William Ebchester, Prior (1446-56)
and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)
according to inscriptions on ff. 4v and 5.</p>
</provenance>
<acquisition><p>Presented to Trinity College in 1738 by
Thomas Gale and his son Roger.</p></acquisition>
</history>
Declaration
<!ELEMENT history - - (p+ | (origin?, provenance*, acquisition?))>
<!ATTLIST history
%a.global;>
The MASTER Document Type Definition: reference manual
<incipit>
<incipit>
contains the text of any incipit
attached to a particular manuscript item, that is the opening words of
a text, frequently used as a form of identifier for it; it may be
preceded by one or more rubrics, and may be defective.
Attributes
defective
indicates whether the incipit as given is defective, i.e. incomplete.
Datatype: (yes|no|unk)
Yes, No, or Unknown
Default: no
type
specifies the type of incipit, e.g. whether it introduces a work,
is biblical, legal, etc.
Datatype: CDATA
A typology has yet to be defined
Default: #IMPLIED
Example
<incipit>Pater noster qui es in celis</incipit>
<incipit defective ="yes">
<gap/>tatem dedit hominibus alleluia.
<rubric>Capitulum,</rubric> Primum quidem
sermonem feci de omnibus</incipit>
<incipit type="biblical">Ghif ons huden onse dagelix
broet</incipit>
<incipit>O ongehoerde gewerdighe christi</incipit>
<incipit type="lemma">Firmiter</incipit>
<incipit>Ideo dicit firmiter quia
ordo fidei nostre probari non potest</incipit>
The MASTER Document Type Definition: reference manual
<locus>
<locus>
defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references.
Attributes
scheme
identifies the foliation scheme in terms of which the location is being specified
Datatype: CDATA
Identifies a foliation scheme, as further defined in the <foliation> element
Default: #IMPLIED
from
specifies the starting point of the location in a normalised form
Datatype: CDATA
typically this will be a page number
Default: #IMPLIED
to
specifies the end-point of the location in a normalized form
Datatype: CDATA
typically this will be a page number
Default: #IMPLIED
targets
supplies identifiers of associated page images
Datatype: IDREFS
a list of SGML identifiers, either of <figure> elements within a
transcript containing digitized page images, or of
<xptr> elements linked to such images
The MASTER Document Type Definition: reference manual
<name>
<name>
contains a proper noun or noun
phrase.
Attributes
type
indicates the type of thing being named.
Datatype: (person|female|place|org|other)
Sample values include:
person
names a person, gender unknown or unmarked
female
names a person, gender female
place
names a place
org
names an organization
other
names some other entity
Default: "person"
role
indicates the role of the
thing being named.
Datatype: CDATA
Typical values for the Master project include scribe,
binder,artist,owner,
scholar,translator,annotator,
compiler,adapter,dedicatee,
patron,commissioner
Default: #IMPLIED
reg
provides a regularized form of the name.
Datatype: CDATA
The form supplied should conform to local norms and should be taken
from an authority file
Default: #IMPLIED
key
supplies a reference to the
unique identifier used for some other
element, typically a <person>, which contains more detailed
information about the thing being named.
Datatype: IDREF
An element must exist elsewhere in the document with an id attribute
taking the value specified
The MASTER Document Type Definition: reference manual
<origin>
<origin>
contains any descriptive or other information
concerning the origin of a manuscript or manuscript part.
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
<origin notBefore="1802" notAfter="1845" evidence="internal">
<p>Copied in <name type=origPlace>Derby</name>, probably from an
old Flemish original, between 1802 and 1845..</p>
</origin>
The MASTER Document Type Definition: reference manual
<person>
<person>
provides structured biographical and other information
about any person referenced in a manuscript description.
Attributes
role
specifies the chief role of the person (e.g. as author, scribe, owner etc.)
Datatype: CDATA
a set of keywords to be defined
Default: #IMPLIED
sex
specifies the sex of the person.
Datatype: (m | f | u )
Sample values include:
m
male
f
female
u
unknown or inapplicable
Default: "m"
age
specifies the age group to which the participant belongs.
Datatype: CDATA
suggested values are to be supplied
Default: #IMPLIED
Example
<person id="HOCC01" sex="m" role="scribe">
<p>Robert Hoccleve, born c.1368 in London, died in
Southwick c. 1450. Poet and tragedian, he lived in
Chester, and was for many years a Clerk, in the
office of the Privy Seal</p>
</person>
Content
May contain a prose description organized as paragraphs, or
any sequence of demographic elements in any combination.
Declaration
<!ELEMENT person %mm; (p+ | (persName*, birth?, death?,
(occupation|residence)* ))>
<!ATTLIST person
%a.global;
role CDATA #IMPLIED
sex (m | f | u ) ""m""
age CDATA #IMPLIED>
The MASTER Document Type Definition: reference manual
<provenance>
<provenance>
contains any descriptive or other information
concerning a single identifiable episode during the history of a manuscript
or manuscript part, after its creation but before its acquisition.
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
<provenance>
<p>Listed as the property of Lawrence Sterne in 1788.
</provenance>
<provenance>
<p>Sold at Sothebys in 1899.
</provenance>
The MASTER Document Type Definition: reference manual
<recordHist>
<recordHist>
provides information about the source and
revision status of the parent manuscript description itself.
Attributes
No attributes other than those globally
available (see definition for a.global)
Example
<recordHist>
<source><p>Derived from <ref target="IMEV123">IMEV 123</ref> with additional research
by P.M.W.Robinson</p></source>
<change><date>23 June 1999</date>
<respStmt><name>LDB</name><resp>editor</resp></respStmt>
<item>checked examples against DTD version 3.6</item>
</change>
The MASTER Document Type Definition: reference manual
<rubric>
<rubric>
contains the text of any rubric or heading attached to a particular manuscript item, that is, a string of words whereby a
manuscript signals a text division (e.g. beginning, book, chapter, end)
which is in some way set off from the text itself, usually in red ink,or by use of different size or type of script, lining, or other such visual device.
.
Attributes
type
specifies the type of rubric, e.g. whether it is at the start or end of
the item.
Datatype: CDATA
A typology has yet to be defined
Default: #IMPLIED
Example
<rubric>Explicit le romans de la Rose ou l'art d'amours est toute
enclose.</rubric>
<rubric>Nu koma Skyckiu Rym<expan>ur</expan>.</rubric>
<rubric><locus>16. f. 28v in margin: </locus>Dicta Cassiodori</rubric>
The MASTER Document Type Definition: reference manual
<msWriting>
<msWriting>
contains a description of all the different kinds of writing used in a manuscript.
Attributes
hands
specifies the number of distinct hands identified within the manuscript
Datatype: CDATA
A whole number, or the string "many"
Default: #IMPLIED
Example
<msWriting>
<p>Written in <term>angelicana formata</term>.</p>
</msWriting>
Example
<msWriting 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>
</msWriting>
The MASTER Document Type Definition: reference manual
<secfol>
<secfol>
The word or words that a cataloguer, typically medieval but possibly modern as well, might take from a fixed point in all the codices he is describing (the beginning of the second leaf, the beginning of the second column, the beginning of the penultimate leaf, the end of the penultimate leaf, and so on) in order to provide a unique identifier to the particular codex.
Attributes
No attributes other than those globally
available (see definition for a.global)
The MASTER Document Type Definition: reference manual
<signatures>
<signatures>
contains discussion of the leaf or quire signatures found within a codex.
Attributes
No attributes other than those globally
available (see definition for a.global)
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 center 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).</p></signatures>
The MASTER Document Type Definition: reference manual
<surrogates>
<surrogates>
contains information about any digital or
photographic representations of the manuscript being described which
may exist in the holding institution or elsewhere.
Attributes
No attributes other than those globally
available (see definition for a.global)
