2.2 Phrase-level elements

2.2.1 Origination and material

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:

Normalised dates should be specified in whatever standardised form is defined by the TEI Header Normalised dates should be specified in whatever standardised form is defined by the TEI Header

notBefore	specifies the earliest possible date for the information in the associated element.
	Datatype: CDATA
	Default: #IMPLIED
notAfter	specifies the latest possible date for the information in the associated element
	Datatype: CDATA
	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:

The default, and recommended, value is mm, i.e. millimetres.

units	specifies the units used for this measurement.
	Datatype: CDATA
	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:

<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>

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

typically this will be a page number typically this will be a page number Identifies a foliation scheme, as further defined in the <foliation> element a list of SGML identifiers, either of <figure> elements within a transcript containing digitized page images, or of <xptr> elements linked to such images from specifies the starting point of the location in a normalised form Datatype: CDATA Default: #IMPLIED to specifies the end-point of the location in a normalized form Datatype: CDATA Default: #IMPLIED scheme identifies the foliation scheme in terms of which the location is being specified Datatype: CDATA Default: #IMPLIED targets supplies identifiers of associated page images Datatype: IDREFS 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&amp;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

Typical values for the Master project include scribe, binder,artist,owner, scholar,translator,annotator, compiler,adapter,dedicatee, patron,commissioner The form supplied should conform to local norms and should be taken from an authority file An element must exist elsewhere in the document with an id attribute taking the value specified 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 Default: #IMPLIED reg provides a regularized form of the name. Datatype: CDATA 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 Default: #IMPLIED

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

<name type="place">Villingaholt</name>
<name type="person" role="scribe">Hoccleve</name>
<name type="person" role="scribe" key="HOC001">Hoccleve</name>
<name type="org" role="owner" reg="Koninklijke Biblioteek">Royal Library</name>

Note that the <name> element is defined as providing information about a name, not a person (or place). In 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

a set of keywords to be definedsuggested values are to be supplied role specifies the chief role of the person (e.g. as author, scribe, owner etc.) Datatype: CDATA 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 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:

  <person id="HOCC01" sex="m">
  <persName>Hoccleve, Robert</persName>
  <birth notBefore="1365" notAfter="1370">
     <date>c.1368</date>
     <name type="place">London</name>
  </birth>
  <occupation>Clerk, office of Privy Seal</occupation>
  <death notBefore="1440" notAfter="1460">
     <date>c.1450</date>
     <name type="place">Southwick, England</name>
  </death>
  <residence notBefore="1370" notAfter="1460">
     <name type="place">Chester</name>
  </residence>
  </person>

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&eacute;e, de gauche &agrave; droite:  armes de
France <heraldry>d'azur &agrave; 3 fleurs de lys d'or</heraldry>; 
de Saint-&Eacute;tienne de Dijon <heraldry>de gueules &agrave; 1 
palme d'or, 2 caillous d'or en chef et 1 en pointe</heraldry>; 
de Cl&eacute;ment VII, antipape <heraldry>&eacute;quipoll&eacute; 
d'or et d'azur</heraldry>, surmont&eacute;es des clefs du 
Saint-Si&egrave;ge; de Philippe le Hardi ou de Bourgogne-Valois 
<heraldry>&eacute;cartel&eacute; au 1er et 4e d'azur
&agrave; la fleur de lys d'or &agrave; la bordure compon&eacute;e d'argent
et de gueules, aux 2e et 3e, band&eacute; d'or et d'azur de six
pi&egrave;ces &agrave; la bordure de gueules<heraldry>; non 
identifi&eacute;es <heraldry>de gueules &agrave; 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: