The ENRICH Schema — A Reference Guide

1 Manuscript Description Metadata

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

fileDesc (Descripción del archivo.) contiene una descripción bibliográfica completa del archivo electrónico.
titleStmt (declaración del título) agrupa la información referente al título de una obra y a los responsables de su contenido intelectual.
publicationStmt (declaración de la publicación) agrupa la información concerniente a la publicación o distribución de un texto electrónico u otro texto.
sourceDesc (descripción de la fuente) proporciona una descripción del texto (o textos) fuente del que un texto electrónico deriva o ha sido generado.
revisionDesc (descripción de la revisión) resume el historial de la revisión de un archivo.

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

The following example shows the minimal required structure:

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

 </msDesc>
 </sourceDesc>
</fileDesc>
<revisionDesc>
 <change when="2008-01-01">

 </change>
</revisionDesc>
</teiHeader>

Taking these in turn,

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

msDesc (descripción del manuscrito) contiene la definición de un único manuscrito.

xml:id	(identificador) proporciona un identificador único para el elemento al cual se asocia el atributo.
xml:lang	(lengua) indica la lengua del contenido del elemento utilizando los códigos extraídos de RFC 3066

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

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

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

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

msIdentifier (identificador del manuscrito) contiene la información necesaria para identificar el manuscrito que se examina.
msContents (contenido del manuscrito) describe el contenido intelectual de un manuscrito o parte de un manuscrito, a través de párrafos o fragemtos del manuscrito.
physDesc (descripción física) contiene una descripción física completa de un manuscrito o de una de sus partes que puede ser ulteriormente subdividida utilizando elementos específicos de la clase model.physDescPart.
history agrupa elementos que describen la historia completa de un manuscrito o de una de sus partes.
additional agrupa información adicional, combinando informaciones bibliográficas relativas al manuscrito o a copias adicionales del mismo con informaciones de carácter conservacional o administrativo.
msPart (fragmento del manuscrito) contiene información relativas a un manuscrito o a parte de un manuscrito originariamente distintas pero actualmente parte de un manuscrito compuesto.

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

To demonstrate the variety of records which may be produced, consider the following sample manuscript description, chosen more or less at random from the Bodleian Library's Summary catalogue

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

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

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

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

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

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

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

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

1.1 Phrase-level Elements

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

catchwords describe el sistema utilizado para garantizar la ordenación correcta de los cuadernos que constituyen un códex o un incunable, obtenido normalmente por medio de anotaciones a pie de página.
dimensions contiene cualquier tipo de especificación referente a las dimensiones.
heraldry contiene una fórmula o frade heráldica, normalmente parte de un escudo de armas, blasón, etc.
locus define una posición al interno de un manuscrito o de una de sus partes, generalmente como secuencia (no necesariamete contínua) de referencias de folios.
locusGrp groups a number of locations which together form a distinct but discontinuous item within a manuscript or manuscript part, according to a specific foliation.
material contiene una palabra o sintagma que describe el material del que se compone un manuscrito (o parte del manuscrito).
watermark contiene una palabra o sintagma que describe una filigrana o una técnica similar.
origDate (fecha origen) contiene cualquier tipo de fecha utilizada para indicar la fecha de origen de un manuscrito o de una de sus partes.
origPlace (lugar de origen) contiene cualquier tipo de nombre de lugar utilizado para indicar el lugar de origen de un manuscrito o de una de sus partes.
secFol (segundo folio) la palabra o palabras extraídas de un punto preciso de un códex (normalmente el inicio del segundo folio) con el fin de identificar lo mismo en modo unívoco.
signatures contiene el registro de las signaturas del folio o del cuaderno pertenecientes al códex.

1.1.1 Origination

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

origDate (fecha origen) contiene cualquier tipo de fecha utilizada para indicar la fecha de origen de un manuscrito o de una de sus partes.
origPlace (lugar de origen) contiene cualquier tipo de nombre de lugar utilizado para indicar el lugar de origen de un manuscrito o de una de sus partes.

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

att.editLike proporciona atributos que describen la naturaleza de una intervención crítica codificada o una interpretación de cualquier tipo.

cert	(certeza) significa el grado de certeza asociado con la intervención o la interpretación.
resp	(parte responsable) indica el agente responsable de la intervención o la interpretación, p.ej. un editor o un transcriptor.
evidence	indica la naturaleza de las pruebas que sostienen la fiabilidad o precisión de la intervención o interpretación.

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

att.datable.w3c proporciona atributos para la normalización de elementos que contienen eventos datables.atributos para registrar expresiones temporales normalizadas.

notBefore	especifica la fecha más temprana posible para un evento en un formato estándard, p.ej. aaaa-mm-dd.
notAfter	especifica la fecha más tardana posible para un evento en un formato estándard, p.ej. aaaa-mm-dd.
when	proporciona el valor de una fecha o una hora en un formato estandard.
from	indica el punto de inicio del período en el formato estándard.
to	indica el punto final de un periodo en formato estándard.

1.1.2 Material

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

material contiene una palabra o sintagma que describe el material del que se compone un manuscrito (o parte del manuscrito).

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

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

1.1.3 Watermarks and Stamps

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

watermark contiene una palabra o sintagma que describe una filigrana o una técnica similar.
stamp contiene una palabra o sintagma que describe un sello o una técnica similar.

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

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

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

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

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

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

</binding>

1.1.4 Dimensions

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

dimensions contiene cualquier tipo de especificación referente a las dimensiones.

type	indica que aspecto del objeto se mide.

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

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

The following elements are available within the dimensions element:

dim contains any single measurement forming part of a dimensional specification of some sort.
height refiere la medida tomada del largo del eje paralelo del dorso.***
width contiene la medida tomada al largo del eje perpendicular del dorso.***
depth refiere la medida tomada del ancho del dorso.***

The dim element may be used to supply any kind of dimensional information, for example diameter or circumference, and may be repeated as often as needed. The other three have specific senses and each of them may only be given once.

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

att.dimensions proporciona atributos que califican una determinata medición.

unit	especifica las unidades usadas para la medición.
quantity	especifica la longitud en las unidades especificadas
scope	especifica la aplicabilidad de esta medición, en los casos en que se mida más de un objeto.

Through this class membership, these elements also inherit the following attributes from the att.ranging class:

att.ranging provides attributes for describing numerical ranges.

atLeast	gives a minimum estimated value for the measurement.
atMost	gives a maximum estimated value for the measurement.
min	where the measurement summarizes more than one observation, supplies the minimum value observed.
max	where the measurement summarizes more than one observation, supplies the maximum value observed.

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

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

In the simplest case, only the extent attribute may be supplied:

<width extent="6 cubit">six cubits</width>

More usually, the measurement will be normalised into a value and an appropriate SI unit:

<width quantity="270" unit="cm">six cubits</width>

Where the exact value is uncertain, the attributes atLeast and atMost may be used to indicate the upper and lower bounds of an estimated value:

<width atLeast="250" atMost="300" unit="cm">six cubits</width>

It is often convenient to supply a measurement which applies to a number of discrete observations: for example, the number of ruled lines on the pages of a manuscript (which may not all be the same), or the diameter of an object like a bell, which will differ depending where it is measured. In such cases, the scope attribute may be used to specify the observations for which this measurement is applicable:

This indicates that most pages have at least 20 lines. The attributes min and max can also be used to specify the possible range of values: for example, to show that all pages have between 12 and 30 lines:

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

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

1.1.5 References to Locations within a Manuscript

The locus element and its grouping element locusGrp are specialized forms of the ref element.

locus define una posición al interno de un manuscrito o de una de sus partes, generalmente como secuencia (no necesariamete contínua) de referencias de folios.

from	indica el punto de inicio de una localización en una forma estándard.
to	indica el punto final de una localización en una forma estándard.
scheme	identifica la foliación en base a la posición especificada.

locusGrp groups a number of locations which together form a distinct but discontinuous item within a manuscript or manuscript part, according to a specific foliation.

scheme

identifies the foliation scheme in terms of which all the locations contained by the group are specified.

The locus element is used to reference a single location within a manuscript, typically to specify the location occupied by the element within which it appears. If for example it is used as the first component of an msItem element, or of any of the more specific elements appearing within one (see further section 1.4 Intellectual Content below, then it is understood to specify the location (or locations) of that item within the manuscript being described.

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

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

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

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

When the item concerned occupies a discontinuous sequence of pages, this may simply be indicated in the body of the locus element:

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

Alternatively, if it is desired to indicate normalised values for each part of the sequence, a sequence of locus elements can be supplied, grouped within the locusGrp element:

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

Finally, the content of the locus element may be omitted if a formatting application can construct it automatically from the values of the from and to attributes:

<msItem n="1">
<locusGrp>
<locus from="1r" to="12v"/>
<locus from="18" to="24r"/>
</locusGrp>
<title>Apocalypsis beati Ioannis Apostoli</title>
</msItem>

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

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

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

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

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

<pb xml:id="f1r"/>

<pb xml:id="f1v"/>

<pb xml:id="f2r"/>

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

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

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

1.1.6 Names of Persons, Places, and Organizations

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

name (nombre, nombre propio) contiene un nombre propio o un sintagma nominal

As further discussed in http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONARS , this element is a member of the TEI class att.canonical, from which it inherits the following attributes:

att.canonical provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.

key	provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
ref	(reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.

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

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

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

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

</person>

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

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

All the person elements referenced by a particular document set should be collected together within a listPerson element, located in the TEI Header. This functions as a kind of prosopography for all the people referenced by the set of manuscripts being described, in much the same way as a listBibl element in the back matter may be used to hold bibliographic information for all the works referenced.

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

1.1.7 Catchwords, Signatures, Secundo Folio

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

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

Alternatively, it may contain more details:

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

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

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

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

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

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

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

1.1.8 Heraldry

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

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

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

1.2 The Manuscript Identifier

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

msIdentifier (identificador del manuscrito) contiene la información necesaria para identificar el manuscrito que se examina.

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

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

country (country) contiene el nombre de una unidad geopolítica, como una nación, país, colonia, etc. más grande o administrativamente superior que una región y más pequeño que un bloque.
region >contiene el nombre de una unidad administrativa, como un estado, una región o una província, que sea mayor que un pequeño asentamiento, pero menor a un país.
settlement contiene el nombre de un asentamiento, del tipo ciudad, pueblo, villa etc. identificado como una unidad geopolítica o administrativa.
institution contiene el nombre de una organización (una universidad o una biblioteca por ejemplo) donde se encuentra el manuscrito.***
repository contiene el nombre de un depósito, parte o no de una institución, en el que se conservan los manuscritos.

At least one of the elements listed above must be given within the msIdentifier and they must, if present, appear in the order given.

Like name, these elements are all also members of the attribute class att.canonical, and thus can use the attributes key or ref to reference a single standardized source of information about the entity being named.

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

collection contiene el nombre de una colección de manuscritos, no necesariamente colocados en un único depósito.
idno (número identificativo) proporciona un número, estándard o no, usado para la identificación de un elemento bibliográfico.

altIdentifier (identificador alternativo) contiene un identificador estructurado, alternativo o precedente, utilizado para un manuscrito, p.ej. un número antiguo de catalogación.

type	caracteriza el elemento utilizando una clasificación o tipología funcional.

msName (nombre alternativo.) contiene cualquier forma de nombre alternativo no estructurado usado para un manuscrito, como por ejemplo ‘ocellus nominum’, o sobranombre.

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

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

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

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

would clearly be inappropriate. Equally clearly,

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

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

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

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

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

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

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

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

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

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

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

Element altIdentifier

change

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

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

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

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

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

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

1.3 The Manuscript Heading

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

head (encabezamiento) contiene cualquier tipo de encabezamiento, por ejemplo el título de una sección o el encabezado de una lista, glosario, descripción de un manuscrito, etc.

In this way the cataloguer or scholar can supply in one place a minimum of essential information, such as might be displayed or printed as the heading of a full description.

Phrase-level elements, such as title, name, date, or the specialized elements origPlace and origDate, can also be used within a head element, but it should be remembered that the head element is intended principally to contain a heading. More structured information concerning the contents, physical form, or history of the manuscript should be given within the specialized elements described below, msContents, physDesc, history, etc. However, in simple cases, the p element may also be used to supply an unstructured collection of such information, as in the example given above ( 1 Manuscript Description Metadata.

A manuscript may often contain multiple works by multiple authors. The head element should only be used to provide summary information:

<head>
<author>Hildegard of Bingen</author> et alii, <title>Opera varia</title>; <origPlace>Heidelberg</origPlace>, <origDate>1455</origDate>.
</head>

which should be supported by a more detailed description using the msContents element described in the next section.

1.4 Intellectual Content

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

msContents (contenido del manuscrito) describe el contenido intelectual de un manuscrito o parte de un manuscrito, a través de párrafos o fragemtos del manuscrito.
msItem (elemento del manuscrito) describe una obra individual o un elemento al interno del contenido intelectual de un manuscrito o de una de sus partes.

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

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

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

<msContents>
<msItem n="1">
 <locus>fols. 5r -7v</locus>
 <title>An ABC</title>
 <bibl>
 <title>IMEV</title>
 <biblScope type="pages">239</biblScope>
 </bibl>
</msItem>
<msItem n="2">
 <locus>fols. 7v -8v</locus>
 <title xml:lang="fr">Lenvoy de Chaucer a Scogan</title>
 <bibl>
 <title>IMEV</title>
 <biblScope type="pages">3747</biblScope>
 </bibl>
</msItem>
<msItem n="3">
 <locus>fol. 8v</locus>
 <title>Truth</title>
 <bibl>
 <title>IMEV</title>
 <biblScope type="pages">809</biblScope>
 </bibl>
</msItem>
<msItem n="4">
 <locus>fols. 8v-10v</locus>
 <title>Birds Praise of Love</title>
 <bibl>
 <title>IMEV</title>
 <biblScope type="pages">1506</biblScope>
 </bibl>
</msItem>
<msItem n="5">
 <locus>fols. 10v -11v</locus>
 <title xml:lang="la">De amico ad amicam</title>
 <title xml:lang="la">Responcio</title>
 <bibl>
 <title>IMEV</title>
 <biblScope type="pages">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>

1.4.1 The <msItem> Element

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

These are the possible component elements of msItem

author en una referencia bibliográfica, contiene el nombre del autor/es, personal o empresa de una obra; la declaración esencial de responsabilidad para cualquier ítem bibliográfico.
respStmt (declaración de responsabilidad) proporciona la declaración de la responsabilidad para el contenido intelectual de un texto, edición, grabación o serie, donde no basten o no se apliquen los elementos especializados para autores, editores, etc.
title contiene el título completo de una obra de cualquier tipo.
rubric contiene el texto de eventuales rúbricas o títulos asignados a un determinado fragmento del manuscrito; se trata de series de palabras que señalan el inicio de una división textual, a menudo tales series contienen información sobre el autor o el título, y se evidencian del resto mediante tinta roja, un estilo distinto o una dimensión distinta del carácter, u otro rasgo gráfico visible.
incipit contiene el incipit de un manuscrito, es decir, las primeras palabras del texto propriamente dicho, a excepción de eventuales títulos en rojo que lo preceden; los incipit tienen una longitud a deteminar según de que obra se trate y, antiguamente, eran utilizados a menudo para referirse a las obras mismas en lugar de títulos eventuales.
quote (cita) contiene una frase o pasaje atribuido por el narrador o autor a un agente externo al texto.
explicit contiene el explicit de un manuscrito, es decir, las palabras de clausura del texto como tal, a excepción de las eventuales rúbricas o colofón sucesivos.
finalRubric contiene una serie de palabras que señala el fin de una división textual; a menudo declara el autor y el título, y dicha serie normalmente es evidenciada del resto mediante tinta roja, un estilo distinto o una dimensión distinta de los caracteres, u otro rasgo gráfico visible.
colophon contiene el colophon de un manuscrito, es decir, una declaración que contiene informaciones relativas a fecha, lugar, agente, o finalidad de la producción del manuscrito.
decoNote (observaciones de la decoración) contiene una nota que describe un componente decorativo de un manuscrito o una clase razonablemente homogénea de tales componentes.
listBibl (lista de cita) contiene una lista de citas bibliográficas de cualquier tipo.
bibl (cita bibliográfica.) contiene una cita bibliográfica estructurada libremente, los componentes de la cual pueden nohaber sido etiquetados explícitamente.
filiation contiene información referente a la filiación de un manuscrito, p.ej. su relación con otros manuscritos supervivientes del mismo texto, es decir, sus protógrafos, antígrafos y apógrafos.
note contiene una nota o aclaración
textLang (lengua del texto) describe las lenguas y los sistemas de escritura usados en un manuscrito (no se ha de confundir con la descripción contenida en el elemento langUsage. ****

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

docAuthor (autor del documento) contiene el nombre del autor del documento, como se indica en el frontispicio (a menudo, pero no siempre, contenido al interno del elemento byline (autoria).
docTitle (título del documento) contiene el título del documento incluyendo todos sus elementos constitutivos, como especificado en el frontispicio.
docImprint (declaración de imprenta) contiene la declaración de la publicación (lugar y fecha de publicación, casa editorial) tal y como consta al pie del frontispicio.

These elements are also available within the msItem element.

In addition, an msItem may contain nested msItem elements.

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

The elements msContents, msItem, incipit, and explicit are all members of the class att.msExcerpt from which they inherit the defective attribute.

att.msExcerpt (extracto de manuscrito) proporciona atributos usados para describir extractos de un manuscrito ******

defective

indica si el pasaje que se describe es completo o no, p.ej. si ha sufrido pérdidas o daños.

This attribute can be used for example with collections of fragments, where each fragment is given as a separate msItem and the first and last words of each fragment are transcribed as defective incipits and explicits.

1.4.2 Authors and Titles

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

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

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

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

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

The resp element is also a member of the att.canonical class, from which it inherits the key attribute. For ENRICH purposes, this may be used to supply a standard relationship code for the kind of responsibility concerned, as defined in the list maintained at http://www.loc.gov/marc/relators/relacode.html :

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

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

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

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

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

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

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

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

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

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

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

1.4.4 Filiation

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

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

1.4.5 Text Classification

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

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

The value of the class attribute should specify the identifier used for the appropriate classification within a taxonomy element, defined in the classDecl element of the TEI Header ( http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD55 ), as shown here:

1.4.6 Languages and Writing Systems

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

<textLang mainLang="chu">Old Church Slavonic, written in Cyrillic script.</textLang>

Element textLang

change

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

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

Since Old Church Slavonic may be written in either Cyrillic or Glagolitic scripts, and even occasionally in both within the same manuscript, it might be preferable to use a more explicit identifier:

<textLang mainLang="chu-Cyrs">Old Church Slavonic in Cyrillic script</textLang>

The form and scope of language identifiers recommended by these Guidelines is based on the IANA standard described at http://www.tei-c.org/release/doc/tei-p5-doc/html/CH.html#CHSH and should be followed throughout. Where additional detail is needed correctly to describe a language, or to discuss its deployment in a given text, this should be done using the langUsage element in the TEI Header, within which individual language elements document the languages used: see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD41 .

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

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

1.5 Physical Description

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

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

Most manuscript descriptions touch on several of these categories of information though few include them all, and not all distinguish them as clearly as we propose here. In particular, it is often the case that an existing description will include within a single paragraph, or even sentence, information for which we propose distinct elements. In this case, if rewriting is not an option, the existing prose must be marked up simply as a series of p elements, directly within the physDesc element.

The physDesc element may thus be used in either of two distinct ways. It may contain a series of paragraphs addressing topics listed above and similar ones. Alternatively, it may act as a container for any choice of the more specialized elements described in the remainder of this section, each of which itself contains a series of paragraphs, and may also have more specific attributes. If the two ways are combined in a single description, care should be taken to avoid duplication and all paragraphs of generic description must precede the first of the more specialised elements.

1.5.1 Object Description

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

Element objectDesc

change

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

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

supportDesc (descripción de ayuda) agrupa los elementos que describen el soporte físico de la parte escrita de un manuscrito.

material

un nombre breve definido en el ámbito de un proyecto y referente al material que costituye la mayor parte del suporte.

support contiene una descripción de los materiales, etc. que constituyen el soporte físico de la parte escrita de un manuscrito.
extent describe el tamaño aproximado de un texto almacenado en algún medio, digital o no, especificándolo en alguna unidad funcional.
collation contiene una descripción de cómo los folios o bifolios están físicamente dispuestos.
foliation describe el sistema o sistemas de numeración usados para contar los fólios o las páginas de un códex.
condition contiene una descripción de la condición física de un manuscrito.

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

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

Element supportDesc

change

Here is a simple example:

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

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

1.5.1.1 Support

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

<support>

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

1.5.1.2 Extent

The extent element, defined in the TEI header, may also be used in a manuscript description to specify the number of leaves a manuscript contains, as in the following example:

Information regarding the size of the leaves may be specifically marked using the phrase level dimensions element, as in the following example, or left as plain prose.

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

1.5.1.3 Collation

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

<collation>

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

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

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

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

</collation>

1.5.1.4 Foliation

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

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

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

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

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

1.5.1.5 Condition

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

<supportDesc>
<condition>
The manuscript shows signs of damage from water and mould on its outermost leaves.
</condition>
</supportDesc>

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

1.5.1.6 Layout Description

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

layoutDesc (descripción de la disposición) agrupa el conjunto de las descripciones de la distribución aplicable a un manuscrito.
layout describe la disposición del texto en la página, comprendiendo eventuales informaciones sobre la lineación***, indicaciones de agujereado***, u otras señales de técnicas de preparación de la página utilizadas.

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

The following examples indicate the range of possibilities:

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

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

Element layout

change

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

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

1.5.2 Writing, Decoration, and Other Notations

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

handDesc (descripción de las manos) contiene una descripción de todos los diferentes tipos de escritura usados en un manuscrito.

hands

especifica el número de manos distintas identificadas al interno de un manuscrito.

handNote (notas sobre la mano) describe un determinado estilo o una determinada mano al interno de un manuscrito.

script	caracteriza un determinado estilo de escritura utilizado por la mano en cuestión, p.ej. secretario, grabado sobre cobre, cancelleresco, italiano, etc.
scope	especifica en qué medida es utilizada la mano en el manuscrito.

typeDesc contains a description of the typefaces or other aspects of the printing of an incunable or other printed source.
typeNote describes a particular font or other significant typographic feature distinguished within the description of a printed resource.
decoDesc (descripción de la decoración) contiene una descripción de la decoración de un manuscrito en forma de secuencia de párrafos o de secuencia de elementos decoNote organizados por el argumento.
decoNote (observaciones de la decoración) contiene una nota que describe un componente decorativo de un manuscrito o una clase razonablemente homogénea de tales componentes.
musicNotation contiene la descripción de un tipo de anotación musical.
additions contiene una descripción de cualquier adición significativa encontrada al interno de un manuscrito como notas al márgen u otras anotaciones.

1.5.2.1 Writing

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

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

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

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

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

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

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

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

If early printed material or incunables are described using this schema, the typeDesc and typeNote elements may be used (in the same way as handDesc and handNote) to record information about the typefaces etc. of interest in the source.

<typeDesc>
<summary>Uses a mixture of Roman and Black Letter types.</summary>
<typeNote>Antiqua typeface, showing influence of Jenson's Venetian
fonts.</typeNote>
<typeNote>The black letter face is a variant of Schwabacher.</typeNote>
</typeDesc>

Both typeDesc and handDesc may be supplied, for example in the case where a printed work has been annotated by a number of hands.

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

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

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

1.5.2.2 Decoration

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

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

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

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

Element decoNote

change

Here is a simple example:

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

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

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

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

1.5.2.3 Musical Notation

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

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

1.5.2.4 Additions and Marginalia

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

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

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

1.5.3 Bindings, Seals, and Additional Material

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

bindingDesc (descripción obligatoria) describe la encuadernación actual y precedente de un manuscrito en forma de una serie de párrafos o de una serie de diversos elementos binding (encuadernación), uno para cada encuadernación del manuscrito.
binding contiene la descripción de una encuadernación, p.ej. tipo de cubiertas, tablas, etc. presentes en un manuscrito.
condition contiene una descripción de la condición física de un manuscrito.
sealDesc (descripción del sello) describe los sellos u otros objetos externos aplicados a un manuscrito mediante una serie de párrafos o una serie de diversos elementos seal (sellos), eventualmente con ulteriores elementos decoNote.
seal contiene la descripción de un sello o de un elemento externo aplicado a un manuscrito.
accMat (material adicional) contiene eventuales detalles que conciernen a materiales añadidos estrechamente relacionados con el manuscrito examinado, p.ej. documentos no actuales o fragmentos cosidos junto al manuscrito en un período histórico precedente al actual.

1.5.3.1 Binding Descriptions

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

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

Within a binding description, the elements decoNote and is condition are available as an alternatives 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>
<condition>Front and back leather inlaid panels very badly worn.</condition>
Rebacked during the 19th century.
</binding>

1.5.3.2 Seals

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

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

1.5.3.3 Accompanying Material

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

accMat (material adicional) contiene eventuales detalles que conciernen a materiales añadidos estrechamente relacionados con el manuscrito examinado, p.ej. documentos no actuales o fragmentos cosidos junto al manuscrito en un período histórico precedente al actual.

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

</accMat>

1.6 History

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

history agrupa elementos que describen la historia completa de un manuscrito o de una de sus partes.
origin contiene informaciones relativas al orígen de un manuscrito o de una de sus partes.
provenance contiene descripciones o informaciones relativas a un único episodio identificable en la historia de un manuscrito o de una de sus partes que sea posterior al momento de su creación pero anterior al momento de su adquisición.
acquisition contiene cualquier descripción u otra información concerniente al proceso de adquisición del manuscrito o de una de sus partes.

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

att.datable.w3c proporciona atributos para la normalización de elementos que contienen eventos datables.atributos para registrar expresiones temporales normalizadas.

notBefore	especifica la fecha más temprana posible para un evento en un formato estándard, p.ej. aaaa-mm-dd.
notAfter	especifica la fecha más tardana posible para un evento en un formato estándard, p.ej. aaaa-mm-dd.
from	indica el punto de inicio del período en el formato estándard.
to	indica el punto final de un periodo en formato estándard.
when	proporciona el valor de una fecha o una hora en un formato estandard.

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

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

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

Here is a fuller example:

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

1.7 Additional information

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

additional agrupa información adicional, combinando informaciones bibliográficas relativas al manuscrito o a copias adicionales del mismo con informaciones de carácter conservacional o administrativo.
adminInfo (información administrativa.) contiene información relativa a la gestión y a la disponibilidad del manuscrito y a la descripción misma de la documentación.
surrogates contains information about any non-digital representations of the manuscript being described which may exist in the holding institution or elsewhere.
listBibl (lista de cita) contiene una lista de citas bibliográficas de cualquier tipo.

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

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

1.7.1 Administrative information

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

recordHist (historia registrada) proporciona información relativa a la fuente y sobre el estatus de revisión de la descripción del manuscrito del que deriva.

availability proporciona información sobre la disponibilidad de un texto, por ejemplo cualquier restricción en cuanto a su uso o distribución, su copyright, etc.

status

proporciona un código identificativo de la disponibilidad actual del texto.

custodialHist (historial de la custodia) contiene una descripción de la historia de la conservación del manuscrito en forma de prosa o come serie de eventos fechados relativos a la gestión del manuscrito.

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

1.7.1.1 Record History

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

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

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

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

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

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

</listBibl>
</additional>

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

1.7.1.2 Availability and Custodial History

The availability element is another element also available in the TEI Header, which should be used here to supply any information concerning access to the current manuscript, such as its physical location (where this is not implicit in its identifier), any restrictions on access, information about copyright, etc.

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

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

custEvent (acontecimiento de la custodia) describe un único evento en la historia de la conservación de un manuscrito.

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

Element custEvent

change

Here is an example of the use of this element:

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

1.7.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 non-digital 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 or digital identifiers for unpublished collections of manuscript images maintained within the holding institution, as well as to provide more detailed descriptive information about the surrogate itself. Such information may be provided as prose paragraphs, within which identifying information about particular surrogates may be presented using the standard TEI bibl element, as in the following example:

<surrogates>

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

</surrogates>

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

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

1.8 Manuscript Parts

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

msPart (fragmento del manuscrito) contiene información relativas a un manuscrito o a parte de un manuscrito originariamente distintas pero actualmente parte de un manuscrito compuesto.

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

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

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

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

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

</msPart>

</msDesc>

3 Customization Section

We include in the schema the four basic key TEI modules header, core, tei, and textstructure. We also include five specialized modules: msdescription, linking, namesdates, figures, and transcr.

All the elements and attributes defined by these modules are included in the ENRICH schema, with the following modifications. Firstly, several unwanted elements are deleted. Secondly, some optional attributes have been made compulsory, and their range of possible values are constrained. Finally, the content model for a small number of elements has been simplified to remove unwanted alternatives.

The following elements are deleted: <ab>, <alt>, <altGrp>, <analytic>, <appInfo>, <application>, <biblFull>, <biblStruct>, <binaryObject>, <broadcast>, <cRefPattern>, <cell>, <cit>, <climate>, <correction>, <distinct>, <email>, <emph>, <equipment>, <equiv>, <fsdDecl>, <headItem>, <headLabel>, <hyphenation>, <imprint>, <interpretation>, <join>, <joinGrp>, <link>, <linkGrp>, <listNym>, <measure>, <measureGrp>, <meeting>, <mentioned>, <metDecl>, <metSym>, <monogr>, <msItemStruct>, <namespace>, <normalization>, <num>, <nym>, <postBox>, <postCode>, q, <quotation>, <recording>, <recordingStmt>, <refsDecl>, <rendition>, <row>, <rs>, <said>, <samplingDecl>, <scriptStmt>, <segmentation>, <series>, <soCalled>, <sp>, <speaker>, <stage>, <state>, <stdVals>, <street>, <table>, <tagUsage>, <tagsDecl>, <teiCorpus>, <terrain>, <time>, <timeline>, <variantEncoding>, <when>.

The att.global.linking class is also deleted, since we anticipate no need for complex pointing mechanisms.

On the altIdentifier element, the type attribute is compulsory, and must take one of the following values: former; partial; internal; system; other

On the availability element, the status attribute is compulsory, and must take one of the following values: free; unknown; restricted.

On the biblScope element, the type attribute is compulsory, and must take one of the following values: volume; pages.

On the custEvent element, the type attribute is compulsory, and must take one of the following values: check; conservation; description; exhibition; loan; photography; other.

On the decoNote element, the type attribute is compulsory, and must take one of the following values: border; diagram; initial; marginal; miniature; mixed; paratext; secondary; other; illustration; printmark; publishmark; vignette; frieze; map; unspecified.

On the dimensions element, the type attribute is compulsory, and must take one of the following values: leaf; binding; slip; written; boxed; unknown.

On the gap element, the reason attribute is compulsory, and must take one of the following values: damage; illegible; cancelled; irrelevant.

On all members of the att.dimensions class, the unit attribute is compulsory, and must take one of the following values: chars; leaves; lines; mm; pages; words. The precision attribute is removed.

On the handNote element, the script attribute is compulsory, and must take one of the following values: carolmin; textualis; cursiva; hybrida; humbook; humcursiva; kanzlei; kurrent; other.

On the handNote element, the scope attribute is compulsory, and must take one of the following values: sole; major; minor.

On the hi element, the rend attribute is compulsory, and must take one of the following values: hyphenated; underline; double-underline; bold; caps; italic; sup; rubric.

On the layout element, the columns attribute is compulsory, and must take a numeric value.

On the msDesc element, the xml:id attribute is compulsory, and must be a valid XML identifier.

On the msDesc element, the xml:lang attribute is compulsory, and must be a valid ISO 639 language code.

On the name element, the type attribute is compulsory, and must take one of the following values: person; place; org; unknown.

On the objectDesc element, the form attribute is compulsory, and must take one of the following values: codex; leaf; scroll; other.

On the person element, the sex attribute is compulsory, and must be one of 1 (male), 2 (female), 0 (inapplicable), or 9 (unknown).

On the region element, the type attribute is compulsory, and must take one of the following values: parish; county; compass; geog; state; unknown.

On the supplied element, the reason attribute is compulsory, and must take one of the following values: omitted; illegible; damage; unknown.

On the supportDesc element, the material attribute is compulsory, and must take one of the following values: perg; chart; mixed; unknown.

The following changes do not affect TEI conformance since either they affect only optional parts of TEI content models or they involve additional value constraints for TEI attributes:

On the textLang element, the mainLang attribute is compulsory, and must take a legal character identifier as value.
The optional elements xml:id and xml:lang are made mandatory for the msDesc element.
The content model of the date element is changed to include a schematron rule which enforces an appropriate selection of attributes (one of: when, to and from, or notAfter and notBefore)
The content model of the recordHist element is changed to remove the possibility of including the change element here.

Schema enrich: Model classes

model.addressLike

model.addressLike agrupa elementos sintagmáticos usados para representar una dirección postal o electrónica.
Módulo	tei
Usado por	location model.pPart.data
Miembros	affiliation

model.biblLike

model.biblLike agrupa elementos que contienen una descripción bibliográfica.
Módulo	tei
Usado por	event listBibl location org place population relatedItem sourceDesc taxonomy trait model.inter
Miembros	bibl msDesc

model.biblPart

model.biblPart agrupa los elementos que pueden aparecer al interno citas bibliográficas.
Módulo	tei
Usado por	bibl
Miembros	model.imprintPart [biblScope distributor pubPlace publisher] model.respLike [author editor funder principal respStmt sponsor] edition extent idno msIdentifier relatedItem

model.choicePart

model.choicePart agrupa los elementos (excluída el propio elemento "choice") que pueden ser usados en alternancia con choice.
Módulo	tei
Usado por	choice
Miembros	abbr am corr ex expan orig reg seg sic unclear

model.common

model.common agrupa elementos comunes a nivel de fragmentos de texto o internivel.
Módulo	tei
Usado por	body div
Miembros	model.divPart [model.lLike [l] model.pLike [p] lg] model.inter [model.biblLike [bibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list listBibl listEvent listOrg listPerson listPlace] model.qLike [model.quoteLike [quote] q] ]
Nota	Esta clase define el conjunto de los elementos de fragmento e inter-nivel; se utiliza en muchos modelos de contención, incluyendo aquellos para las divisiones textuales.

model.dateLike

model.dateLike agrupa elementos que contienen expresiones temporales.
Módulo	tei
Usado por	model.pPart.data
Miembros	date

model.dimLike

model.dimLike groups elements which describe a measurement forming part of the physical dimensions of some object.
Módulo	tei
Usado por	dimensions
Miembros	depth height width

model.divBottom

model.divBottom agrupa elementos que pueden aparecer sólo al final de una división textual, p.ej. un tráiler.
Módulo	tei
Usado por	body div group lg list
Miembros	model.divBottomPart model.divWrapper [docAuthor]

model.divGenLike

model.divGenLike agrupa elementos usados para representar divisiones estructurales que se generan explícitamente porque estan presentes en la fuente.
Módulo	tei
Usado por	body div
Miembros	divGen

model.divLike

model.divLike agrupa los elementos usados para representar divisiones estructurales recursivamente.
Módulo	tei
Usado por	back body div front
Miembros	div

model.divPart

model.divPart agrupa elementos que pueden aparecer entre párrafos u otras divisiones, pero no dentro de estos.
Módulo	tei
Usado por	macro.specialPara model.common
Miembros	model.lLike [l] model.pLike [p] lg
Nota	Observa que esta clase de elemento no incluye a los miembros de la clase model.inter, que puede aparecer dentro o entre los items del nivel-párrafo.

model.divTop

model.divTop agrupa los elementos que aparecen al principio de una división textual.
Módulo	tei
Usado por	body div group lg list
Miembros	model.divTopPart [model.headLike [head] ] model.divWrapper [docAuthor]

model.divTopPart

model.divTopPart agrupa los elementos que pueden aparecer solamente al principio de una división textual.
Módulo	tei
Usado por	model.divTop
Miembros	model.headLike [head]

model.divWrapper

model.divWrapper agrupa elementos que pueden aparecer al principio o al final de cualquier elemento de clase de división.
Módulo	tei
Usado por	model.divTop model.divBottom
Miembros	docAuthor

model.emphLike

model.emphLike agrupa elementos sintagmáticos semánticos.
Módulo	tei
Usado por	model.highlighted model.limitedPhrase
Miembros	foreign gloss term title

model.encodingPart

model.encodingPart agrupa elementos que pueden aparecer al interno de encodingDesc (Descripción de la codificación) y que aparecen en diversas ocasiones.
Módulo	header
Usado por	encodingDesc
Miembros	charDecl classDecl editorialDecl geoDecl projectDesc

model.frontPart

model.frontPart agrupa elementos que aparecen a nivel de particiones textuales al interno del paratexto inicial o final.
Módulo	tei
Usado por	back front
Miembros	divGen titlePage

model.gLike

model.gLike agrupa elementos que son
Módulo	tei
Usado por	am bibl date docImprint origDate macro.paraContent macro.phraseSeq macro.specialPara macro.xtext
Miembros	g

model.global

model.global agrupa elementos vacíos que pueden aparecer en cualquier punto de un texto TEI
Módulo	tei
Usado por	back bibl body change date div docImprint docTitle figure front group lg list msItem person text titlePage macro.paraContent macro.phraseSeq macro.phraseSeq.limited macro.specialPara
Miembros	model.global.edit [addSpan damageSpan delSpan gap space] model.global.meta [index] model.milestoneLike [anchor cb fw lb milestone pb] model.noteLike [note] figure

model.global.edit

model.global.edit agrupa elementos vacíos con funciones editoriales específicas, p.ej. la indicación del comienzo de un fragmento de texto añadido, omitido o perdido en el original.
Módulo	tei
Usado por	model.global
Miembros	addSpan damageSpan delSpan gap space

model.global.meta

model.global.meta agrupa elementos vacíos que describen el estatus de otros elementos, p.ej. estableciendo grupos de relaciones o interpretaciones abstractas, o bien proporcionando indicaciones de certeza, etc., y que pueden aparecer en cualquier punto de un documento.
Módulo	tei
Usado por	model.global
Miembros	index
Nota	Los elementos en esta clase se utilizan típicamente para llevar a cabo los grupos de conexiones o de interpretaciones abstractas, o bien para proporcionar indicaciones de la certeza etc. Puede ser conveniente localizar todos los elementos de los metadatos, por ejemplo para contenerlos dentro de la misma división que los elementos con los cuales se relacionan; o para localizarlos todos en la división que les es propia. Sin embargo pueden aparecer en cualquier momento en un texto de TEI.

model.glossLike

model.glossLike agrupa los elementos que proporcionan un nombre, descripción o explicación alternativa a elementos de codificación.
Módulo	tei
Usado por	category char gap glyph surface taxonomy zone
Miembros	desc gloss

model.graphicLike

model.graphicLike agrupa elementos que contienen imágenes, fórmulas u objetos similares.
Módulo	tei
Usado por	char facsimile figure formula glyph surface zone model.phrase
Miembros	formula graphic

model.headLike

model.headLike agrupa los elementos usados para proporcionar un título o un encabezadoa al principio de una división textual.
Módulo	tei
Usado por	divGen event figure listBibl listEvent listOrg listPerson listPlace msDesc msPart org place population trait model.divTopPart
Miembros	head

model.headerPart

model.headerPart agrupa elementos que pueden usarse al interno del teiHeader y aparecen en diversas ocasiones.
Módulo	header
Usado por	teiHeader
Miembros	encodingDesc profileDesc

model.hiLike

model.hiLike agrupa elementos de nivel sintagmático para subrayar que no tienen una semántica específica.
Módulo	tei
Usado por	origDate model.highlighted
Miembros	hi

model.highlighted

model.highlighted agrupa elementos de nivel sintagmático relativos al énfasis.
Módulo	tei
Usado por	bibl model.phrase
Miembros	model.emphLike [foreign gloss term title] model.hiLike [hi]

model.imprintPart

model.imprintPart agrupa los elementos bibliográficos que aparecen al interno de las siglas editoriales.
Módulo	tei
Usado por	model.biblPart
Miembros	biblScope distributor pubPlace publisher

model.inter

model.inter agrupa elementos de la clase intermedia (internivel): tales elementos pueden aparecer bien al interno bien entre párrafos u entre otros elementos de tipo división de texto.
Módulo	tei
Usado por	change macro.limitedContent macro.paraContent macro.specialPara model.common
Miembros	model.biblLike [bibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list listBibl listEvent listOrg listPerson listPlace] model.qLike [model.quoteLike [quote] q]

model.lLike

model.lLike agrupa elementos que representan componentes métricos como los versos.
Módulo	tei
Usado por	lg model.divPart
Miembros	l

model.labelLike

model.labelLike agrupa los elementos usados para glosar o para explicar otras partes de un documento.
Módulo	tei
Usado por	event location org place population trait model.inter
Miembros	desc label

model.limitedPhrase

model.limitedPhrase agrupa los elementos que pueden aparecer a nivel de palabras o sintagmas, excluyendo los elementos destinados a la transcripción.
Módulo	tei
Usado por	catDesc change macro.limitedContent macro.phraseSeq.limited
Miembros	model.emphLike [foreign gloss term title] model.pPart.data [model.addressLike [affiliation] model.dateLike [date] model.measureLike [depth dim geo height width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName nameLink roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] ] ] ] model.pPart.editorial [abbr am choice ex expan subst] model.pPart.msdesc [catchwords dimensions handShift heraldry locus locusGrp material origDate origPlace secFol signatures stamp watermark] model.ptrLike [ptr ref]

model.listLike

model.listLike agrupa todos los elementos del tipo de lista.
Módulo	tei
Usado por	sourceDesc model.inter
Miembros	list listBibl listEvent listOrg listPerson listPlace

model.measureLike

model.measureLike agrupa elementos que contienen un número, una cantidad, una medida, o un fragmento de texto similar que refleja algún significado numérico.
Módulo	tei
Usado por	location model.pPart.data
Miembros	depth dim geo height width

model.milestoneLike

model.milestoneLike agrupa elementos del tipo frontera (milestone) utilizados para representar sistemas de referencia.
Módulo	tei
Usado por	listBibl model.global
Miembros	anchor cb fw lb milestone pb

model.msItemPart

model.msItemPart la clase de elementos que pueden aparecer dentro de la descripción de un manuscrito.
Módulo	tei
Usado por	msItem
Miembros	model.msQuoteLike [colophon explicit finalRubric incipit rubric title] model.quoteLike [quote] model.respLike [author editor funder principal respStmt sponsor] bibl decoNote filiation listBibl msItem textLang

model.msQuoteLike

model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
Módulo	tei
Usado por	model.msItemPart
Miembros	colophon explicit finalRubric incipit rubric title

model.nameLike

model.nameLike agrupa los elementos que nombran o indican a una persona, un lugar (construido por el hombre o geográfico), o una organización.
Módulo	tei
Usado por	org model.pPart.data
Miembros	model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName nameLink roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] ]
Nota	Un superconjunto de elementos de nombramiento que pueden aparecer en las líneas de fecha, de dirección, de declaración de esponsabilidad,l etc.

model.nameLike.agent

model.nameLike.agent agrupa elementos que contienen nombres de individuos o de agrupaciones o sociedades.
Módulo	tei
Usado por	respStmt model.nameLike
Miembros	name orgName persName
Nota	Esta clase se utiliza en el modelo de elementos cuyos nombres se refieren a gente o a organizaciones.

model.noteLike

model.noteLike agrupa todos los elementos del tipo de nota.
Módulo	tei
Usado por	adminInfo char event glyph location notesStmt org place population trait model.global
Miembros	note

model.offsetLike

model.offsetLike agrupa los elementos que pueden aparecer solamente como parte de un topónimo.
Módulo	tei
Usado por	location model.nameLike
Miembros	geogFeat offset

model.pLike

model.pLike la clase de elementos de tipo párrafa con la finalidad de intercambio.
Módulo	tei
Usado por	availability binding bindingDesc custodialHist decoDesc editionStmt editorialDecl encodingDesc event figure handDesc history langKnowledge layoutDesc msContents msDesc msItem msPart objectDesc org person personGrp physDesc place population projectDesc publicationStmt recordHist relationGrp seal sealDesc seriesStmt sourceDesc supportDesc trait typeDesc model.divPart
Miembros	p

model.pLike.front

model.pLike.front agrupa los elementos que aparecen como componentes directos del paratexto inicial cuando no se da un encabezamiento electrónico.
Módulo	tei
Usado por	back front
Miembros	docAuthor docEdition docImprint docTitle head titlePart

model.pPart.data

model.pPart.data agrupa los elementos a nivel sintagmàtico que contienen nombres, fechas, medidas o datos similares.
Módulo	tei
Usado por	bibl model.phrase model.limitedPhrase
Miembros	model.addressLike [affiliation] model.dateLike [date] model.measureLike [depth dim geo height width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName nameLink roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] ] ]

model.pPart.edit

model.pPart.edit agrupa elementos de nivel sintagmático utilizados para simples correcciones o transcripciones editoriales.
Módulo	tei
Usado por	bibl model.phrase
Miembros	model.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del orig reg restore sic supplied unclear]

model.pPart.editorial

model.pPart.editorial agrupa elementos a nivel sintagmático utilizados para simples intervenciones editoriales que pueden ser útiles tanto en la transcripción como para autoría.
Módulo	tei
Usado por	model.pPart.edit model.limitedPhrase
Miembros	abbr am choice ex expan subst

model.pPart.msdesc

model.pPart.msdesc agrupa les elementos empleados en la descripción de manuscritos.
Módulo	tei
Usado por	model.phrase model.limitedPhrase
Miembros	catchwords dimensions handShift heraldry locus locusGrp material origDate origPlace secFol signatures stamp watermark

model.pPart.transcriptional

model.pPart.transcriptional agrupa solo elementos sintagmáticos utilizados para simples correcciones y transcripciones editoriales que no parecen ser útiles para la autoría.
Módulo	tei
Usado por	am subst model.pPart.edit
Miembros	add corr damage del orig reg restore sic supplied unclear

model.persEventLike

model.persEventLike clase de elementos que describen eventos específicos en la vida de una persona, p.ej., nacimiento, matrimonio, nómina, etc.; tales elementos no representan caraterísticas verdaderas y propias de un individuo, pero a menudo hacen que el individuo en cuestión adquiera determinadas características o un estatus determinado.
Módulo	tei
Usado por	model.personPart
Miembros	birth death event
Nota	Éstas no son características de un individuo, pero a menudo provocan que un individuo adquiera tales características, o que entre en un nuevo estado.

model.persNamePart

model.persNamePart agrupa los elementos que componen un nombre propio de persona.
Módulo	namesdates
Usado por	model.nameLike
Miembros	addName forename genName nameLink roleName surname

model.persStateLike

model.persStateLike clase de elementos que describen las características mutables o con una duración determinada en una persona, p.ej. ocupación, residencia, nombre, etc.; tales características de un individuo representan generalmente una consecuencia de sus acciones o de las de otros.
Módulo	tei
Usado por	model.personPart
Miembros	affiliation education floruit occupation persName residence
Nota	Estas características de un individuo son típicamente una consecuencia de su propia acción o de la de otros.

model.persTraitLike

model.persTraitLike clase de elementos que describe características físicas o de derivación social generalmente inmutables de una persona, p.ej. color de pelo, etnia, sexo, etc.; tales características de un undividuo son normalmente independientes de su voluntad o de sus acciones.
Módulo	tei
Usado por	model.personPart
Miembros	age faith langKnowledge nationality sex socecStatus trait
Nota	Estas características de un individuo son típicamente independientes de su voluntariedad o acción.

model.personLike

model.personLike clase de elementos utilizados para proporcionar informaciones relativas a personas y a las relaciones entre estas.
Módulo	tei
Usado por	listPerson org
Miembros	org person personGrp

model.personPart

model.personPart agrupa elementos que describen determinadas características de las personas a las cuales se hace referencia en el texto o que participan en una interacción verbal.
Módulo	tei
Usado por	person personGrp
Miembros	model.persEventLike [birth death event] model.persStateLike [affiliation education floruit occupation persName residence] model.persTraitLike [age faith langKnowledge nationality sex socecStatus trait] bibl

model.phrase

model.phrase agrupa los elementos que pueden aparecer en el nivel de palabras o sintagmas.
Módulo	tei
Usado por	date docImprint macro.paraContent macro.phraseSeq macro.specialPara
Miembros	model.graphicLike [formula graphic] model.highlighted [model.emphLike [foreign gloss term title] model.hiLike [hi] ] model.pPart.data [model.addressLike [affiliation] model.dateLike [date] model.measureLike [depth dim geo height width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat offset] model.persNamePart [addName forename genName nameLink roleName surname] model.placeStateLike [model.placeNamePart [bloc country district geogName placeName region settlement] ] ] ] model.pPart.edit [model.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del orig reg restore sic supplied unclear] ] model.pPart.msdesc [catchwords dimensions handShift heraldry locus locusGrp material origDate origPlace secFol signatures stamp watermark] model.ptrLike [ptr ref] model.segLike [seg]
Nota	Esta clase de elementos puede darse solamente dentro de elementos más grandes de la clase inter o fragmento. En prosa significa que estos elementos pueden aparecer dentro de párrafos, en los elementos de una lista, en las líneas de verso, etc.

model.physDescPart

model.physDescPart elementos descriptivos específicos que constituyen la descripción física de un manuscrito o de una fuente escrita similar.
Módulo	tei
Usado por
Miembros	accMat additions bindingDesc decoDesc handDesc musicNotation objectDesc sealDesc typeDesc

model.placeEventLike

model.placeEventLike agrupa elementos que describen acontecimientos que afectan a un lugar.
Módulo	tei
Usado por	place
Miembros	event

model.placeLike

model.placeLike elementos de los grupos usados para proporcionar a la información sobre los lugares y sus lazos.
Módulo	tei
Usado por	listPlace org place
Miembros	place

model.placeNamePart

model.placeNamePart agrupa los elementos que forman parte del nombre de un lugar
Módulo	tei
Usado por	location model.placeStateLike
Miembros	bloc country district geogName placeName region settlement

model.placeStateLike

model.placeStateLike agrupa los elementos que describen aspectos variables de un lugar.
Módulo	tei
Usado por	place model.nameLike
Miembros	model.placeNamePart [bloc country district geogName placeName region settlement]

model.placeTraitLike

model.placeTraitLike agrupa los elementos que describen los rasgos invariables de un lugar.
Módulo	tei
Usado por	place
Miembros	location population trait

model.profileDescPart

model.profileDescPart agrupa los elementos que pueden ser usados al interno de profileDesc y que aparecen en diversas ocasiones.
Módulo	header
Usado por	profileDesc
Miembros	handNotes langUsage textClass

model.ptrLike

model.ptrLike agrupa elementos usados para establecer localizaciones y referencias.
Módulo	tei
Usado por	bibl relatedItem model.phrase model.limitedPhrase
Miembros	ptr ref

model.publicationStmtPart

model.publicationStmtPart agrupa los hijos de publicationStmt.
Módulo	tei
Usado por	publicationStmt
Miembros	authority availability date distributor idno pubPlace publisher

model.qLike

model.qLike agrupa elementos relativos al evidenciado que aparece al interno de o entre elementos a nivel de fragmentos de texto.
Módulo	tei
Usado por	model.inter
Miembros	model.quoteLike [quote] q

model.quoteLike

model.quoteLike agrupa los elementos que contienen directamente las citas
Módulo	tei
Usado por	model.qLike model.msItemPart
Miembros	quote

model.resourceLike

model.resourceLike agrupa los elementos no-textuales que pueden aparecer junto al encabezado y un texto para constituir un documento de TEI.
Módulo	tei
Usado por	TEI
Miembros	facsimile

model.respLike

model.respLike aggrupa elementos utilizados para indicar responsabilidad intelectual, p.ej. dentro de un elemento bibliográfico.
Módulo	tei
Usado por	titleStmt model.biblPart model.msItemPart
Miembros	author editor funder principal respStmt sponsor

model.segLike

model.segLike agrupa elementos usados por una segmentación arbitraria.
Módulo	tei
Usado por	bibl model.phrase
Miembros	seg
Nota	Los principios en los cuales se realiza la segmentación, y cualesquiera sean los códigos o valores de atributo especiales usados, se deben definir explícitamente en el elemento <segmentación> del encodingDesc dentro del encabezado TEI asociado.

model.titlepagePart

model.titlepagePart agrupa los elementos que aparecen como componentes directos del frontispicio electrónico (docTitle, docAuthor, docImprint, <epigraph>, etc.)
Módulo	tei
Usado por	msItem titlePage
Miembros	docAuthor docEdition docImprint docTitle graphic titlePart

Schema enrich: Attribute classes

att.ascribed

att.ascribed proporciona atributos para los elementos que representan palabras o acciones atribuibles a individuos determinados.

Módulo tei

Miembros change q

Atributos

who

indica la persona o grupo de personas a las que se refiere el contenido del elemento.

Estado	Opcional
Tipo de datos	1–∞ apariciones de `xsd:anyURI` separado por espacio en blanco
Valores	For transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified person element.

att.canonical

att.canonical provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.

Módulo tei

Miembros att.naming [att.personal [addName forename genName orgName persName roleName surname] affiliation birth bloc collection country death district education event geogFeat geogName institution name nationality occupation origPlace placeName population pubPlace region relation repository residence settlement socecStatus trait] author docAuthor docTitle resp term title

Atributos

key

provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.

Estado	Opcional
Tipo de datos	`string`
Valores	any string of Unicode characters

ref

(reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.

Estado	Opcional
Tipo de datos	1–∞ apariciones de `xsd:anyURI` separado por espacio en blanco

att.coordinated

att.coordinated los elementos se pueden colocar dentro de un sistema de coordenadas bidimensional.

Módulo transcr

Miembros surface zone

Atributos

ulx

proporciona el valor de la coordinada X para el ángulo superior izquierdo de un espacio rectangular.

Estado	Opcional
Tipo de datos	`xsd:double \| token { pattern = "(\-?[\d]+/\-?[\d]+)" } \| xsd:decimal`

uly

proporciona el valor de la coordinada Y para el ángulo superior izquierdo de un espacio rectangular.

Estado	Opcional
Tipo de datos	`xsd:double \| token { pattern = "(\-?[\d]+/\-?[\d]+)" } \| xsd:decimal`

lrx

proporciona el valor de la coordinada X para el ángulo inferior derecho de un espacio rectangular

Estado	Opcional
Tipo de datos	`xsd:double \| token { pattern = "(\-?[\d]+/\-?[\d]+)" } \| xsd:decimal`

lry

proporciona el valor de la coordinada Y para el ángulo inferior izquierdo de un espacio rectangular

Estado	Opcional
Tipo de datos	`xsd:double \| token { pattern = "(\-?[\d]+/\-?[\d]+)" } \| xsd:decimal`

att.damaged

att.damaged proporciona los atributos que describen la naturaleza de cualquier daño físico que afecta a una lectura.

Módulo tei

Miembros damage damageSpan

Atributos

att.dimensions (@unit, @quantity, @extent, @scope) (att.ranging (@atLeast, @atMost, @min, @max))

hand

en el caso de daño (deliberado o no) adscribible a una mano identificable, indica la mano responsable del daño.

Estado	Opcional
Tipo de datos	`xsd:anyURI`
Valores	must be one of the hand identifiers declared in the document header (see section ??).

agent

categoriza la causa del daño, si esta puede ser identificada.

Estado	Opcional
Tipo de datos	`xsd:Name`
Posibles valores:	rubbing el daño se deriva por el roce de los márgenes de los folios mildew daño resultante de la presencia de moho en la superficie del folio smoke daños provocados por el humo

degree

>indica el grado del daño medido en base a una escala funcional; la etiqueta damage (daño) con el atributo degree (grado) deberán utilizarse sólo si el texto puede ser leído con una cierta certeza; los textos proporcionados por otras fuentes serán etiquetados como supplied (suplente)

Estado	Opcional
Tipo de datos
Valores	an alphanumeric categorization of the degree of damage, as 0.4.
Nota	La etiqueta <daño> con el atributo grado debe ser utilizado solamente donde el texto se puede leer con certeza a pesar del daño. Es apropiada donde se desee registrar el daño, aunque éste no haya afectado a la legibilidad del texto (como puede ser el caso de materiales desgastados). Donde el daño ha provocado que el texto sea más o menos ilegible conviene usar la etiqueta <ilegible> (para la ilegibilidad parcial) o la etiqueta <agujero> (para la ilegibilidad completa, carente del texto suministrado), con la información referente al daño en los valores de atributo de estas etiquetas. Ver la sección ?? para la discusión sobre el uso de estas etiquetas en circunstancias particulares.

group

asigna un número arbitrario a cada fragmento del daño considerado como parte del mismo fenómeno físico.

Estado	Obligatorios cuando se aplican
Tipo de datos	`xsd:nonNegativeInteger`

att.datable

att.datable proporciona atributos para la normalización de elementos que contienen eventos datables.atributos para registrar expresiones temporales normalizadas.
Módulo	tei
Miembros	acquisition affiliation age binding birth bloc country custEvent date death district education event faith floruit geogFeat langKnowledge langKnown location nationality occupation orgName origDate origPlace origin persName placeName population provenance region relation residence seal settlement sex socecStatus stamp trait
Atributos	att.datable.w3c (@period, @when, @notBefore, @notAfter, @from, @to)
Nota	Esta ‘superclase’ proporciona atributos que pueden ser utilizados para proporcionar valores normalizados de información temporal. Por defecto, los atributos de la clase att.datable.w3c son proporcionados. Si el módulo para los nombres y las fechas se acciona, esta clase también proporciona atributos de att.datable.iso. En general, los valores posibles de los atributos son los restringidos por la forma de los datatypes de W3C, un subconjunto de esos valores disponibles vía el estándar de ISO 8601. Sin embargo, la mayoría de expresiones de los datatypes de ISO pueden no ser necesarios, y existe software de soporte para los datatypes de W3C.

att.datable.w3c

att.datable.w3c proporciona atributos para la normalización de elementos que contienen eventos datables.atributos para registrar expresiones temporales normalizadas.

Módulo

tei

Miembros

att.datable [acquisition affiliation age binding birth bloc country custEvent date death district education event faith floruit geogFeat langKnowledge langKnown location nationality occupation orgName origDate origPlace origin persName placeName population provenance region relation residence seal settlement sex socecStatus stamp trait]

Atributos

period

suministra un indicador a una localización concreta que define un periodo de tiempo conocido dentro del cual el item datable se ha producido.

Introduction

1 Manuscript Description Metadata

1.1 Phrase-level Elements

1.1.1 Origination

1.1.2 Material

1.1.3 Watermarks and Stamps

1.1.4 Dimensions

1.1.5 References to Locations within a Manuscript

1.1.6 Names of Persons, Places, and Organizations

1.1.7 Catchwords, Signatures, Secundo Folio

1.1.8 Heraldry

1.2 The Manuscript Identifier

1.3 The Manuscript Heading

1.4 Intellectual Content

1.4.1 The <msItem> Element

1.4.2 Authors and Titles

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

1.4.4 Filiation

1.4.5 Text Classification

1.4.6 Languages and Writing Systems

1.5 Physical Description

1.5.1 Object Description

1.5.1.1 Support

1.5.1.2 Extent

1.5.1.3 Collation

1.5.1.4 Foliation

1.5.1.5 Condition

1.5.1.6 Layout Description

1.5.2 Writing, Decoration, and Other Notations

1.5.2.1 Writing

1.5.2.2 Decoration

1.5.2.3 Musical Notation

1.5.2.4 Additions and Marginalia

1.5.3 Bindings, Seals, and Additional Material

1.5.3.1 Binding Descriptions

1.5.3.2 Seals

1.5.3.3 Accompanying Material

1.6 History

1.7 Additional information

1.7.1 Administrative information

1.7.1.1 Record History

1.7.1.2 Availability and Custodial History

1.7.2 Surrogates

1.8 Manuscript Parts

2 Metadata about digital facsimiles

3 Customization Section

Schema enrich: Model classes

model.addressLike

model.biblLike

model.biblPart

model.choicePart

model.common

model.dateLike

model.dimLike

model.divBottom

model.divGenLike

model.divLike

model.divPart

model.divTop

model.divTopPart

model.divWrapper

model.emphLike

model.encodingPart

model.frontPart

model.gLike

model.global

model.global.edit

model.global.meta

model.glossLike

model.graphicLike

model.headLike

model.headerPart

model.hiLike

model.highlighted

model.imprintPart

model.inter

model.lLike

model.labelLike

model.limitedPhrase

model.listLike