TEI XML customisation for quantitative codicological manuscript description
Cataloguing guidelines for the project Stories for all time: The Icelandic fornaldarsögur
edited by Eric Andrew Haswell eah@faust.ab.ca and Matthew James Driscoll mjd@hum.ku.dk.
Copenhagen
2012

Table of contents

Introduction

This document describes a narrow subset of the Text Encoding Initiative's P5 Guidelines for Electronic Text Encoding and Interchange as used by the research project Stories for all time: The Icelandic fornaldarsögur (FASNL) based at Nordisk Forskningsinstitut (NFI), a research institute within the Faculty of Humanities at the University of Copenhagen.

Compared to other TEI customisations (e.g. The ENRICH Schema), this customisation is considerably more data-centric because of the FASNL project's focus on quantitative codicology. Therefore, many aspects of manuscripts which would otherwise be included in an XML description have been omitted here; in many cases, a fuller record may be available from other sources, e.g. the Handrit.is union catalogue.

The format is formally expressed by a schema which is generated from the XML source of this guide. The guide itself is a conformant subset of Release 2.0.2 of The Text Encoding Initiative's Guidelines for Electronic Text Encoding and Interchange (TEI P5). The schema defined by this document is available in RELAX NG at the following location: http://am-dk.net/fasnl/xml/fasnl_text.rnc.

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

  1. metadata describing the original source manuscript (1. Manuscript Description Metadata (<teiHeader>))
  2. metadata describing digitized images of the original source manuscript ([[undefined fa]])
  3. a transcription of the text contained by the original source manuscript (2. Transcription)
The overall structure of a FASNL-conformant XML document may be summarised as follows:
<TEI xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader> <!-- ... metadata describing the manuscript -->  </teiHeader>  <facsimile> <!-- ... metadata describing the digital images -->  </facsimile>  <text> <!-- (optional) transcription of the manuscript -->  </text> </TEI>

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

1. Manuscript Description Metadata (<teiHeader>)

Each distinct manuscript must be described using a distinct TEI-conformant <teiHeader> element, as specified in the TEI Guidelines, chapter 2. For FASNL project purposes, the following components of the TEI Header must be provided, and must conform to the constraints specified here.

The following example shows the minimal required structure:
<teiHeader>  <fileDesc>   <titleStmt>    <title>[Shelfmark]</title>   </titleStmt>   <publicationStmt>    <availability status="restricted">     <p>Not ready for publication.</p>    </availability>    <authority>Den Arnamagnæanske Samling, København</authority>   </publicationStmt>   <sourceDesc>    <msDesc xml:id="example" xml:lang="en"> <!-- [full manuscript description ]-->    </msDesc>   </sourceDesc>  </fileDesc>  <revisionDesc>   <change who="#MJD" when="2012-01-01"> <!-- [revision information] -->   </change>  </revisionDesc> </teiHeader>

Taking these in turn,

The <msDesc> element is used to provide detailed information about a single manuscript. For FASNL 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 must be derived from the shelfmark, so as to create a valid QName.

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. Note that xml:lang does not indicate the language of the manuscript itself; this information is encoded under <textLang>, as described below.

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

All of these components are mandatory, apart from <msPart> which should only be used for composite manuscripts, i.e. manuscripts comprising two or more originally distinct manuscript parts.

The first, <msIdentifier>, is described in more detail in 1.1. The Manuscript Identifier (<msIdentifier>) below. It is followed by the specialised elements <msContents> (1.2. Manuscript Contents (<msContents>)), <physDesc> (1.3. Physical Description (<physDesc>)), <history> (1.4. History), and <additional> (1.3.4. <additions>). These elements 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 ([[undefined mspt]]).

1.1. The Manuscript Identifier (<msIdentifier>)

The <msIdentifier> element provides an unambiguous means of uniquely identifying a particular manuscript. This must be done in a structured way, by providing information about the holding institution and call number, shelfmark or other identifier used to indicate its location within that institution.

The following elements are used within <msIdentifier> to identify a manuscript and its holding institution:

<repository> and <idno> are both mandatory within the <msIdentifier>. <altIdentifier> is optional.

This example shows the minimal required structure of <msIdentifier>:
<msIdentifier>  <repository ref="#LBS">Landsbókasafn</repository>  <idno>JS 8 fol.</idno> </msIdentifier>

<repository> is a member of the attribute class att.canonical, and thus can use the attribute ref to reference a single standardised source of information about the entity being named. <repository> may therefore be empty, since all details about the repository, including its name and location, can be recorded in the authority file designated for this purpose. This authority file is described in another section of this document (3.3. Repositories). The value of the key attribute points to a record in the authority file, and a formatting application is expected to retrieve the repository information from there.

This example points to a record having the xml:id #LBS in the repository authority file.
<repository ref="#LBS"/>
This example points to a record having the xml:id #AMIS in the repository authority file. Although it is not an error to supply a textual description of the repository as shown here, it should nonetheless be avoided to prevent redundancy. A correctly configured formatting application will ignore the content of <repository>.
<repository ref="#AMIS">Arnamagnæan Collection, Reykjavík</repository>

The <idno> element is mandatory, and must contain the shelfmark of the manuscript. Manuscript repositories will usually have a preferred form of citation for their manuscript shelfmarks, including rules about punctuation, spacing, abbreviations etc., which should ideally be adhered to.

It is possible to add the <altIdentifier> element in order to reference to a former shelfmark or a different form of identification, e.g. by nickname. The type of alternative Identifier is indicated using the type. Possible values are:
former_shelfmark
the alternative Identifier is a former shelfmark
nickname
the alternative Identifier is a nickname
<msIdentifier>  <repository ref="#AMIS">Arnamagnæan Collection, Reykjavík</repository>  <idno>GKS 1005 fol.</idno>  <altIdentifier type="nickname">   <idno>Flateyjarbók</idno>  </altIdentifier> </msIdentifier>

1.2. Manuscript Contents (<msContents>)

The <msContents> element is used to describe the intellectual content of a manuscript or manuscript part. It comprises a single <titlePage> element with an ana attribute, followed by a series of <msItem> elements, each of which provides a more detailed description of a single item contained within the manuscript.

This example shows the content model of <msContents>:
<msContents>  <titlePage ana="later"/>  <msItem n="1" class="fas"> <!-- [content of msItem] -->  </msItem>  <msItem n="2" class="ridd"> <!-- [content of msItem] -->  </msItem> <!-- [further msItem elements as necessary] --> </msContents>

1.2.1. <titlePage>

<titlePage> can be used to indicate the presence or absence of a title page in a manuscript; if a title page is present, it is required to indicate whether the title page is contemporaneous with the rest of the manuscript or was added later.

  • titlePage (title page) contains the title page of a text, appearing within the front or back matter.
    ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.

The ana attribute is required on <titlePage> and must take one of the following values:

no
The is no title page present in the manuscript.
contemporary
A title page is present and it is contemporaneous with the rest of the manuscript.
later
A title page is present and has been added at some time after the manuscript's creation.
Example of a manuscript without a title page:
<titlePage ana="no"/>
Example of a manuscript with a title page which is contemporary with the rest of the manuscript:
<titlePage ana="contemporary"/>

1.2.2. <msItem>

Each discrete item in a manuscript or manuscript part must be described within a distinct <msItem>, and must be classified using the class attribute and numbered using the n attribute. Another attribute, defective, is optional. A valid manuscript description must contain at least one <msItem>. Nesting of <msItem> elements is permitted where appropriate.

  • msItem (manuscript item) describes an individual work or item within the intellectual content of a manuscript or manuscript part.
    n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
    classidentifies the text types or classifications applicable to this item
    defectiveindicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.

The value of the class attribute should specify the identifier used for the appropriate text classification within a <taxonomy> element. This taxonomy comprises an authority file for text types, and is described in another section of this document (3.4. Text classes).

The defective attribute is optional and should be used only to indicate that a text is incomplete because of loss or damage. If defective is used, it must carry the value true. The absence of defective from an <msItem> element is understood to indicate that the item in question is not defective, i.e. complete.

This example shows the encoding of a manuscript item which belongs to the text class fornaldarsögur. The value of class points to a record in <classDecl> having the xml:id value fas. The example also shows a value of 1 on the attribute n, indicating that this is the first item in the manuscript. Further, the item in question is marked as being incomplete by the use of the defective attribute.
<msItem class="fas" n="1" defective="true">  <locus from="1r:1" to="8v:17"/>  <title type="uniform">Sögubrot af nokkrum fornkonungum í Dana ok Svía    veldi</title> </msItem>
This example demonstrates the method for nesting <msItem> elements. The value of the n attribute on nested <msItem> elements indicates the depth of nesting.
<msItem n="2" class="ridd">  <locus from="23r" to="80r"/>  <title type="uniform">Mágus saga</title>  <note>Rituð á Flankastöðum á Miðnesi af GGS, p. 80r</note>  <msItem n="2.1" class="ridd">   <title type="uniform">Hrólfs þáttur skuggafífls</title>  </msItem>  <msItem n="2.2" class="ridd">   <title type="uniform">Vilhjálms þáttur Laissonar</title>  </msItem>  <msItem n="2.3" class="ridd">   <title type="uniform">Geirarðs þáttur frækna</title>  </msItem> </msItem>
1.2.2.1. <locus>

A <locus> element must be included within <msItem> in order to specify the location (or locations) of that item within the manuscript being described.

  • locus defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references.
    fromspecifies the starting point of the location in a normalized form.
    tospecifies the end-point of the location in a normalized form.

Start and end points must be, at a minimum, specified as folios (e.g. 1r, 45r, 78v). If desired, it is possible to supplement this information with line numbers of one or both of the start and end points of the text. If provided, line numbers must be separated from the folio by a colon character, as shown in the example below.

The content of the <locus> element should be omitted; a formatting application is expected to be able to construct it automatically from the values of the from and to attributes.

This example shows the encoding of a manuscript item which begins on folio 3 verso and ends on folio 17 recto:
<locus from="3v" to="17r"/>
This example shows the encoding of a manuscript item which begins on line 1 of folio 1 recto and ends on line 17 of folio 8 verso.
<locus from="1r:1" to="8v:17"/>
1.2.2.2. <title>

The <title> element contains the title of the individual manuscript item and is required at least once (multiple titles are possible). This title should be provided in a uniform format – that is, the standardised title by which a work is generally known.

  • title contains a title for any kind of work.
    typeclassifies the title according to some convenient typology.

The indication of the type of title is given by the type attribute, which is required and must take one of the following values:

uniform
The title given is a uniform title, i.e. the standard title by which the work is known in e.g. Anonymous classics: a list of uniform headings for European literatures, published by the International Federation of Library Associations and Institutions.
supplied
The title is given in the form provided in a manuscript catalogue or some other source or supplied by the cataloguer. supplied should be used only if it is not possible to assign a uniform title, for example if there is no corresponding entry in the reference literature, and should describe the contents in a general way.
In this example, the manuscript catalogue gives the title of the item as Mágus saga jarls, which is shortened to Mágus saga based on the reference sources:
<title type="uniform">Mágus saga</title>
In this example, the reference sources do not provide a corresponding uniform title. The title is therefore given as written in the manuscript catalogue, and the value of type is supplied.
<title type="supplied">Prayer</title>
1.2.2.3. <textLang>
<textLang> is required to indicate the language of the text within <msItem>. The mainLang attribute is used to encode the predominant language of a text. In cases where a manuscript is written in more than one language, use otherLangs to encoding the additional languages. Abbreviations for each language are taken from the ISO 639-1 codes:
<textLang mainLang="non" otherLangs="la"/>
Note: the abbreviation 'non' is the standard code for Old Norse-Icelandic. It can be found in the expanded list of ISO 639-2 codes.
1.2.2.4. <rubric>, <incipit> and <explicit>

All three of these elements are optional. <rubric> is used to encode headings which indicate textual divisions. Usually these are titles of sagas or other works and are written in a larger, more ornate script within the Icelandic manuscripts. <incipit> and <explicit> encode the first and last words of a text respectively and are often used to identify a text when no title is given. Usually these are five to ten words long, but this length will vary depending on the text

<rubric>Sagann af Eireke Rauda</rubric> <incipit>Olafur heet <ex>kon</ex>ung<ex>ur</ex> er kallaþ<ex>ur</ex> var Oleyfur hvyte</incipit> <explicit>og end<ex>ar</ex> hier so sauguna af Eireke hinum rauda</explicit>
1.2.2.5. <filiation>

The <filiation> element is a container for listing one or more manuscripts which are related to the manuscript described by the current record. Each of these manuscript relations is expressed using <ref> children as necessary.

  • filiation contains information concerning the manuscript's filiation, i.e. its relationship to other surviving manuscripts of the same text, its protographs, antigraphs and apographs.
  • ref (reference) defines a reference to another location, possibly modified by additional text or comment.
    typecharacterizes the element in some sense, using any convenient classification scheme or typology.
    targetspecifies the destination of the reference by supplying one or more URI References
    ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.

Each <ref> child of <filiation> is required to carry the three attributes type, target and ana.

The value of type is can be either ms (manuscript) or book.

The value of target is a list of one or more URI pointers to the xml:id of a manuscript record or records. The value of ana is one of the three following values:

protograph
The manuscript described in the current record derives from or is of the same tradition as the manuscript referenced by target but is not a direct copy of it.
antigraph
The manuscript described in the current record is a direct copy of the manuscript referenced by target.
apograph
The manuscript referenced by target is a direct copy of the manuscript described in the current record.

In the following example, the manuscript being described is derived from, but is not a direct copy of, MS 9999, and is also the source from which the MS 1111 was copied:
<filiation>  <ref type="ms" target="#MS_1111" ana="apograph"/>  <ref type="ms" target="#MS_9999" ana="protograph"/> </filiation>
1.2.2.6. <note>
  • note contains a note or annotation.

In some cases, a cataloguer may wish to include information on a manuscript item which does not fit elsewhere. <note> should be used for this purpose. The <note> element is optional.

Example:
<note>A note concerning something of note.</note>

1.3. Physical Description (<physDesc>)

Under the general heading ‘physical description’ we subsume a large number of elements which are useful in the codicological description of a given manuscript. These include:

The <physDesc> element acts as a container for a specific structure comprised of the specialised elements described in the remainder of this section, each of which itself requires a very precise content model, and may also require certain specific attributes, as the following example demonstrates:
<physDesc>  <objectDesc form="codex">   <supportDesc material="chart">    <support>     <num type="front-flyleaf" value="2"/>     <num type="book-block" value="367"/>     <num type="back-flyleaf" value="1"/>     <dimensions type="leaf">      <height unit="mm" quantity="200"/>      <width unit="mm" quantity="160"/>     </dimensions>     <watermark ana="no"/>    </support>    <foliation ana="later pag"/>    <condition ana="good"/>   </supportDesc>   <layoutDesc>    <layout columns="1" writtenLines="4 30">     <num type="wpl" atLeast="6" atMost="20"/>     <dimensions type="written">      <height unit="mm" quantity="130"/>      <width unit="mm" quantity="175"/>     </dimensions>    </layout>   </layoutDesc>  </objectDesc>  <handDesc hands="3">   <handNote scope="major" script="cursiva"/>   <handNote scope="major" scribeRef="BryJon01" script="cursiva"/>   <handNote scope="major" scribeRef="ThoSig161" script="cursiva"/>  </handDesc>  <decoDesc ana="low">   <decoNote type="initial">Initiala slightly larger, but no ornaments or colour at      all.</decoNote>  </decoDesc>  <additions ana="high">   <p>Lots of marginalia throughout the manuscript, particularly on leaves originally left blank.</p>  </additions>  <bindingDesc>   <binding ana="plain" contemporary="true">    <p>The binding is not in particularly good condition; it is covered in a vellum leaf        containing texts in Latin, one of them a Psalm of David. </p>   </binding>  </bindingDesc> </physDesc>

1.3.1. Object Description (<objectDesc>)

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.

  • objectDesc contains a description of the physical components making up the object which is being described.

The form attribute is used to indicate the specific type of text-bearing object being described. It is required and its value must be one of the following:

codex
A bound codex
leaf
A loose leaf
scroll
A scroll
other
Any other format

The <objectDesc> element has two parts: a description of the support (1.3.1.1. Support Description (<supportDesc>)), i.e. the physical carrier on which the text is inscribed; and a description of the layout 1.3.1.2. Layout Description (<layoutDesc>), i.e. the way text is organised on the carrier.

1.3.1.1. Support Description (<supportDesc>)
  • supportDesc (support description) groups elements describing the physical support for the written part of a manuscript.
    materiala short project-defined name for the material composing the majority of the support

The form attribute on <supportDesc> is used briefly to summarise the materials used for the support. For FASNL project purposes, it must have one of the following values:

perg
Parchment
chart
Paper
mixed
A combination of materials
unknown
Support material unknown
1.3.1.1.1. <support>

The <support> element groups together information about the physical carrier.

  • support contains a description of the materials etc. which make up the physical support for the written part of a manuscript.
The following example shows the required structure of <objectDesc> and its child elements:
<objectDesc form="codex">  <supportDesc material="chart">   <support>    <num type="front-flyleaf" value="4"/>    <num type="book-block" value="206"/>    <num type="back-flyleaf" value="6"/>    <dimensions>     <height unit="mm" quantity="167"/>     <width unit="mm" quantity="132"/>    </dimensions>    <watermark ana="yes"/>   </support>  </supportDesc> </objectDesc>
1.3.1.1.1.1. <num>

The <num> element is used under <support> to indicate the number of leaves present in a manuscript.

  • num (number) contains a number, written in any form.
    typeindicates the type of numeric value.
    valuesupplies the value of the number in standard form.

The value of the type attribute must be one of the following:

back-flyleaf
Fly leaves which come after the main book block.
book-block
The assemblage of leaves making up the main part of the manuscript.
front-flyleaf
Fly leaves which come before the main book block.

At least one and no more than three <num> elements must be present. In the case of a single <num> element, the type attribute must carry the value book-block. If flyleaves are present either at the front or back of the manuscript, further <num> elements may be used as necessary.

1.3.1.1.1.2. <dimensions>

<dimensions> as a child of <support> records the physical size of a manuscript's support.

Leaf dimensions are encoded using two child elements, <height> and <width>, each of which must carry a unit attribute. The measured values for height and width of a manuscript's support should be encoded in one of two ways:

  • Where leaf size is consistent throughout the entire manuscript, the quantity attribute is used.
  • If leaf size varies, the attributes atLeast and atMost should be used to provide minimum and maximum values, respectively.
  • height contains a measurement measured along the axis at right angles to the bottom of the written surface, i.e. parallel to the spine for a codex or book.
    atLeastgives a minimum estimated value for the approximate measurement.
    atMostgives a maximum estimated value for the approximate measurement.
    quantityspecifies the length in the units specified
    unitnames the unit used for the measurement
  • width contains a measurement measured along the axis parallel to the bottom of the written surface, i.e. perpendicular to the spine of a book or codex.
    atLeastgives a minimum estimated value for the approximate measurement.
    atMostgives a maximum estimated value for the approximate measurement.
    quantityspecifies the length in the units specified
    unitnames the unit used for the measurement
1.3.1.1.1.3. <watermark>

<watermark> is required, and is used solely to record either the presence or absence of a watermark. No further information about a watermark is necessary.

  • watermark contains a word or phrase describing a watermark or similar device.
    ana(analysis) Indicates the presence or absence of a watermark.

The ana attribute is required and must take one of the following values:

no
No watermarks are visible in the manuscript.
yes
One or more watermarks are visible.

Note that the absence of the <watermark> element in this context should not be interpreted as equal to an ana value of no.

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

  • foliation describes the numbering system or systems used to count the leaves or pages in a codex.
    ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.

The ana attribute on <foliation> is used to encode two separate but related pieces of information: when the manuscript was foliated and how. The value of ana must be a whitespace-separated sequence of two of the following:

col
Foliation is by column.
contemporary
Foliation is contemporary with the manuscript.
fol
Foliation is by folio.
later
Foliation occurred some time after the manuscript was produced.
no
Manuscript is not foliated.
pag
Foliation is by page.

Note that in the case of a manuscript which was not foliated, a single value, no, is to be used.

The following example shows the encoding of <foliation> for a manuscript which was foliated by folio at the time of its creation:

<foliation ana="contemporary fol"/>

The following example shows the encoding of <foliation> for a manuscript which was foliated by page at the time of its creation:

<foliation ana="contemporary pag"/>

The following example shows the encoding of <foliation> for a manuscript is not foliated:

<foliation ana="no"/>
Note: What to do in cases where there is multiple foliations? e.g. one contemporary, and then another later on. (e.g. Papp 4to 38)?
1.3.1.1.3. <condition>
  • condition contains a description of the physical condition of the manuscript.
    ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.

The <condition> element is used to summarise the overall physical state of a manuscript. Physical state is given as a single value carried by the ana attribute. This must be one of the following three values:

poor
Manuscript condition is fairly bad: some damage to pages and binding.
average
Manuscript condition is average.
good
Manuscript condition is relatively good: structural integrity is sound, with only minor signs of deterioration.

Note that while it is possible to provide a prose description of a manuscript's condition using the <condition> elements descendent, it is not required.

1.3.1.2. Layout Description (<layoutDesc>)

The second part of <objectDesc> 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 is arranged on the page, specifying the number of written lines and columns per page, the number of words per line and the size of the written area.

  • layoutDesc (layout description) collects the set of layout descriptions applicable to a manuscript.

<layoutDesc> has a very specific content model, as illustrated by the following example:

<layoutDesc>  <layout ana="verse-prose" columns="1" writtenLines="24 30">   <num type="wpl" atLeast="6" atMost="20"/>   <dimensions type="written">    <height unit="mm" quantity="130"/>    <width unit="mm" quantity="175"/>   </dimensions>  </layout> </layoutDesc>
1.3.1.2.1. <layout>
  • layout describes how text is laid out on the page, including information about any ruling, pricking, or other evidence of page-preparation techniques.
    ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
    columnsspecifies the number of columns per page
    writtenLinesspecifies the number of written lines per column

The ana attribute on <layout> is optional. It should be used when a manuscript's text includes verses (as is frequently the case with the fornaldarsögur). The attribute's values distinguish between two methods of writing verses: distinct from the prose, i.e. in verse lines, or in-line, i.e. as if it were prose. As such, ana and may take one of the following values, where appropriate:

verse-separate
Verses are present and are written separately from the prose.
verse-prose
Verses are present and are written in-line with the flow of the prose.

Note that as ana is optional, its absence will be taken to imply that there are no verses anywhere in the manuscript.

Note: Explain ana usage better. What constitutes a verse?

The columns attribute is required, and takes a single integer as its value which indicates the number of columns per manuscript page. Note that even if there is only one column present, the columns attribute is still required nonetheless.

The writtenLines attribute is also required and is used for encoding the number of written lines per page of a manuscript. This information may expressed as either a single integer, in the case of a manuscript containing the same number of written lines on each page, or as a whitespace-separated sequence of two integers if the number of written lines varies. In the above example, the number of written lines in the manuscript ranges from 24 to 30.

Note: Explain writtenLines methodology.
1.3.1.2.1.1. <num>

In the context of <layout>, the <num> element is used to encode the number of words per line in the manuscript.

  • num (number) contains a number, written in any form.
    typeindicates the type of numeric value.
    atLeastgives a minimum estimated value for the approximate measurement.
    atMostgives a maximum estimated value for the approximate measurement.

All three of type, atLeast and atMost are required to be present on <num> in this context. The value of type must always be wpl (words per line). The atLeast and atMost attributes encode the lowest and highest number of words per line, respectively. Three pages are chosen at random in the manuscript, and word counts are made on those three pages, taking three or four lines from each. In the unlikely event that all lines sampled contain the same number of words, the atLeast and atMost attributes will both have the same value; otherwise the values will represent the highest and lowest number of those sampled.

1.3.1.2.1.2. <dimensions>
  • dimensions contains a dimensional specification.
    typeindicates which aspect of the object is being measured.

As a descendant of <layoutDesc>, <dimensions> is a container element used to encode the height and width of the written area of the page. To this end, the type attribute is required, and must always carry the value written.

The written area is measured from the ascenders of the first written line to the base line of the last written line, and from the stem of the first letter to the end of the bowl or bar of the last letter. Flourished squiggles, tails and elongated ascenders and descenders are not included. If the written area has been marked by pencil or pen, or is grooved, those marks can be used for measurements.

The height and width of the written area are encoded using the <height> and <width> elements as children of <dimensions>. The measured values for height and width of the written area should be encoded in one of two ways:

  • Where written area is consistent throughout the entire manuscript, the quantity attribute is used.
  • If the size of the written area varies, the attributes atLeast and atMost should be used to provide minimum and maximum values, respectively.
  • height contains a measurement measured along the axis at right angles to the bottom of the written surface, i.e. parallel to the spine for a codex or book.
    unitnames the unit used for the measurement
    quantityspecifies the length in the units specified
    atLeastgives a minimum estimated value for the approximate measurement.
    atMostgives a maximum estimated value for the approximate measurement.
  • width contains a measurement measured along the axis parallel to the bottom of the written surface, i.e. perpendicular to the spine of a book or codex.
    unitnames the unit used for the measurement
    quantityspecifies the length in the units specified
    atLeastgives a minimum estimated value for the approximate measurement.
    atMostgives a maximum estimated value for the approximate measurement.

On both the <height> and <width> elements, the unit and quantity attributes are required. Measurements are expressed in millimetres, and as such the value of unit will always be mm. The quantity attribute is an integer expressing the number of millimetres. Measurements should be rounded to the nearest millimetre.

Note: Explain that dimensions can be used twice in the case of an MS with two scribes with major scope and differing page dims (e.g. Papp 8vo 7).

1.3.2. Hand Description (<handDesc>)

  • handDesc (description of hands) contains a description of all the different kinds of writing used in a manuscript.
    handsspecifies the number of distinct hands identified within the manuscript
  • handNote (note on hand) describes a particular style or hand distinguished within a manuscript.
    scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
The <handDesc> element and its descendant element <handNote> (see below) are used to encode, in a highly structured manner, characteristics of the writing observed in a manuscript, as in the following example:
<handDesc hands="2">  <handNote scribeRef="#scribe1" scope="major" script="textualis"/>  <handNote scribeRef="#scribe2" scope="minor" script="textualis"/> </handDesc>

The hands attribute on <handDesc> carries an integer value which indicates the number of identifiable hands in the manuscript. If it apparent that more than one hand is present, but it is not possible to arrive at a definitive determination of the exact number of hands, then the value 999 should be used. This is interpreted as meaning 'several hands', with an implied uncertainly as to the precise number.

A <handNote> element is required for each of the identifiable hands in the manuscript. Each <handNote> element is required to have three attributes describing the hand in question: scribeRef, scope and script.

The scribeRef attribute carries a reference code which points to a full description of the scribe in an authority file for persons (described in a later section - 3.1. Persons). If the name of a scribe is known but he can nevertheless not be doubtlessly identified, the value "ambig" is used to indicate ambiguity. In that case it is mandatory to supply the name and whatever information available in prose.

The scope attribute indicates the extent to which the hand is used in the manuscript, and may take one of three values:

sole
only this hand is found throughout the manuscript
major
this hand writes most of the manuscript
minor
this hand appears only occasionally in the manuscript

The script attribute describes the type of script used by the hand. If a scribe uses more than one script, the dominant script type is chosen as value of script. Other script types can be specified in prose. The allowable values for script are as follows:

carolingian
protogothic
textualis
cursiva
hybrida
semihybrida
hum cursiva
fractura
chancery fractura
chancery
kurrent
unknown

If desired, it it even possible to distinguish between:

early kurrent
late kurrnet

1.3.3. Decoration Description (<decoDesc>)

  • decoDesc (decoration description) contains a description of the decoration of a manuscript, either as a sequence of paragraphs, or as a sequence of topically organized <decoNote> elements.
    ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
  • decoNote (note on decoration) contains a note describing either a decorative component of a manuscript, or a fairly homogenous class of such components.
    typecharacterizes the element in some sense, using any convenient classification scheme or typology.
The <decoDesc> element and its child element <decoNote> (see below) are used to encode, in a highly structured manner, characteristics of the decoration found in a manuscript, as in the following example:
<decoDesc ana="medium">  <decoNote type="initials">Some initials in red.</decoNote>  <decoNote type="vignette">A tailpiece.</decoNote> </decoDesc>

The ana attribute on <decoDesc> is required and carries a value which indicates the relative level of decoration in the manuscript. The value of ana must be one of the following:

no
the manuscript has no decoration
low
there is very little decoration in the manuscript
medium
the manuscript is moderately decorated
high
the manuscript is highly decorated
The following example demonstrates how to encode and manuscript having no decoration:
<decoDesc ana="no"/>

For each type of decoration in the manuscript, a <decoNote> element can be used. The type attribute on <decoNote> is required, and should describe the type of decoration present. The allowable values for type are as follows:

border
diagram
frieze
illustration
initial
map
marginal
miniature
mixed
other
paratext
printmark
publishmark
secondary
vignette
unspecified

If desired, a prose description of the decoration may also be provided as content of the <decoNote> element, but this is not required.

1.3.4. <additions>

  • additions contains a description of any significant additions found within a manuscript, such as marginalia or other annotations.
    ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.

The <additions> element is used to encode information about any additions to the text, in particular marginalia.

The ana attribute on <additions> is required and carries a value which indicates the relative level of additions in the manuscript. The value of ana must be one of the following:

no
the manuscript has no additions
low
there are very few additions in the manuscript
medium
the manuscript has a moderate number of additions
high
the manuscript has a high number of additions
If desired, a description of the additions may be provided using the standard phrase-level element <p>, as shown in the following example:
<additions ana="low">  <p>Text on leaves on the inner side of both front- and back-boards.</p> </additions>
It is also possible, although not required, to provide a much more detailed description of additions made to the manuscript, as shown in the following example:
<additions ana="medium">  <p>Writing exercises, scribbles and so have been added to    empty spaces or blank pages between items as well as in the margins. Some of these are of    importance as the names of owners<term key="later"/>  </p>  <p>Marteinn Jónsson 12/12 60<locus from="1r" to="1r"/>  </p>  <p>A scribble or exercise: <q>Virðuleglegre heiður kvinnu</q>  </p>  <p>An empty page <locus from="24r" to="24r"/> has been filled later with all sorts    of scribble. At the top: <q>Björn Sigurðsson: Með eigin hendi</q>; in the margin    sideways: <q>Kristborg virðugleg... heiðurs...</q>; Two verses: <q>Fimmtán vetur og fjóra      betur ..., Móðir mín á menntir fín ...</q> written twice with some more writing    exercises.</p>  <note>The same verses are repeated on page 121v <locus from="121v" to="121v"/> as well    as the name <q>Guðrún Björnsdóttir</q>. One hand on leaf 121v is the same as the more    primitive one on leaf 24v</note>  <p>At the end of Hrólfs saga Gautrekssonar <locus from="92vr" to="92v"/> written    in different hand: <q>G G Amen</q>.</p>  <p>At the end of Nikulás saga leikara<locus from="131v" to="131v"/> is written:  <q>Gudrun Bjorns dotter á bókina</q>, as well as some scribbles and writing exercises    repeating this and the verses from page 24r <locus from="24r" to="24r"/>.</p>  <p>At the end of Friðþjós saga frækna <locus from="131v" to="131v"/>some scribbles:  <q>Hafe sa þock er las en skömm skrifade. Virduleg og velforst</q>  </p>  <p>At the end of Adonías saga<locus from="187v" to="187v"/>some scribbles: <q>Hafe sa      þök er L aunga sa sem skrifade</q>.</p>  <p>Scribbles and writing exercises at the end of Sigurðar saga fóts: <locus from="207v" to="207v"/>GSigvaldason; SBJonsson; Gudrun Bjornsdotter; med egenn    hende; Søgubók, gudmundson; GSigvalldason; SMagnusson; MS Jon; GS; Christian;    MSveinsson</p>  <p>On right hand side og leaf 208 sidewise in the margin is written:<locus from="208v" to="208v"/>Gudmundur. Gudrun Biornsdotter a Hreimsstodum a bókena    med riettu þad vitnar sa</p>  <p>At the left hand side of leaf <locus from="209r" to="209r"/> there are is    sidewise written this text, names and verses: Ríchtínus Björnsson Blekið lekur    bókfell á /bytur lítið ... [á?] þesse penne þóknast mier /þó ad sie úr hrafne    /hann hefur skorið Geirager /Guðmundur ad nafne. Solfe ad heimann lagde leid    /liet uppá Baukenn [onidr?] Kómba . . . Vyrdulegur heidursqvinnu Gudrunu Biornsd    Magnusson hefur skrifad þettad Gudrun Bjornsdotter a Bokina og einginn annar </p>  <p>In the margin of leaf 210r <locus from="210r" to="210r"/>is written sidewise:    Þessa bók á eg underteiknud Gudrun ey veit eg hvurs dóttur hún er og hef lied    Jens Magnussini til yferlesningar sier til dægrastittingar: Olafur Jóhnson hefur    skrifad þettad</p>  <p>On a loose leaf <locus from="accMat01r" to="accMat01r">is this text: Arið 1857      lét eg hlaða 64 faðma af túngaråi, plægja í fyrsta sinni 1452 #(fer) faðma án      þess ad vinna meira að því, og taka upp svörð, í minnsta lagi 100 hestar      þurrir. - Ljótstöðum 23/4 58 August Jónsson</locus>  </p> </additions>

1.3.5. Binding Description (<bindingDesc>)

  • bindingDesc (binding description) describes the present and former bindings of a manuscript, either as a series of paragraphs or as a series of distinct <binding> elements, one for each binding of the manuscript.
  • binding contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript.
    ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
    contemporaryspecifies whether or not the binding is contemporary with the majority of its contents

The ana attribute on <binding> is required and is used to encode information about the manuscript binding and its level of decoration. It must take one of the following values:

plain
a plain binding with no decoration
moderate
the binding is moderately decorated
decorative
the binding is highly decorated; special attention has been invested in imparting pleasing aesthetic characteristics to the binding

The contemporary attribute is also required on <binding>, and carries a Boolean value, i.e. true or false, to indicate whether or not the binding is contemporaneous with the manuscript.

If desired, it is possible to supplement the required markup described above with a prose description of the binding, using standard phrase-level elements such as <p>.

The following example demonstrates encoding information about a plain binding contemporary with the manuscript's production:
<bindingDesc>  <binding ana="plain" contemporary="true">   <p>Plain leather cover without boards.</p>  </binding> </bindingDesc>
The following example encodes information about a moderately-decorated binding added as a replacement to the original binding at some later date:
<bindingDesc>  <binding ana="moderate" contemporary="false">   <p>Library binding, leather spine and corners.</p>  </binding> </bindingDesc>

1.4. History

1.4.1. <origin>

  • origin contains any descriptive or other information concerning the origin of a manuscript or manuscript part.

The child elements of <origin> (<origDate> and <origPlace>) are used to encode, in a highly structured manner, information about the place and date of origin of a manuscript.

The following example demonstrates the encoding method for a manuscript produced ca. 1810 in Iceland.
<origin>  <origDate notBefore="1790" notAfter="1810"/>  <origPlace key="IS"/> </origin>
1.4.1.1. <origDate>
  • origDate (origin date) contains any form of date, used to identify the date of origin for a manuscript or manuscript part.
    notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
    notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
    fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
    toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
    whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.

The <origDate> element is required, and should not contain any text or child elements. Depending on the circumstances of, and level of certainly about, a manuscript's date of origin, one of three possible methods may be used to encode the date of origin:

  • If the manuscript was produced in a single year, and this date is known, the when attribute is used.
  • If the manuscript was produced over a span of two or more years, and these dates are known, the from and to attributes are used.
  • If the manuscript's exact date of production is not known, the notBefore and notAfter attributes are used.

Only one of these three methods should be used for the attributes on <origDate>.

The following example demonstrates the encoding method for a manuscript known to have been produced in 1691:
<origDate when="1691"/>
The following example demonstrates the encoding method for a manuscript known to have been begun in 1815 and completed in 1827:
<origDate from="1815" to="1827"/>
The following example demonstrates the encoding method for a manuscript whose date of production is not precisely known, but is estimated to have occurred at some point in the first quarter of the 18th century:
<origDate from="1701" to="1725"/>
1.4.1.2. <origPlace>
  • origPlace (origin place) contains any form of place name, used to identify the place of origin for a manuscript or manuscript part.
    keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.

The <origPlace> element is also required, and, like <origDate>, should not contain any text or child elements. The key attribute carries a reference code which points to a full description of the place of origin in an authority file.

The following example demonstrates the encoding method for a manuscript produced in Iceland:
<origPlace key="IS"/>
1.4.1.3. <provenance>
  • provenance contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript or manuscript part, after its creation but before its acquisition.
  • name (name, proper noun) contains a proper noun or noun phrase.
    keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
    rolemay be used to specify further information about the entity referenced by this name, for example the occupation of a person, or the status of a place.
    typecharacterizes the element in some sense, using any convenient classification scheme or typology.

The <provenance> element is optional. If information on the history of the manuscript is available, particularly with respect to individuals known to have been involved with the manuscript in some way, e.g. as owners, then this information should be encoded using <name> elements as children of <provenance>. Such elements in this context are required to carry three attributes: type, key and role.

For personal names, the value of type is always person.

key carries a reference code which points to a full description of the person in an authority file (described in a later section - 3.1. Persons).

role identifies the nature of the relationship between the person and the manuscript. Some possible values include owner, signatory, commissioner.

The following example demonstrates the method of encoding various owners and signatories of a manuscript:
<provenance>  <name type="person" role="owner" key="Jonooo005">Jón úr Vör</name>  <name type="person" role="owner" key="SigEin005">Sigríður Einarsdóttir</name>  <name type="person" role="owner" key="JonSig045">Jón Sigurður Sigurðsson</name>  <name type="person" role="owner" key="SigJen001">Sigurður Jensson</name>  <name type="person" role="owner" key="SigBry002">Sigríður Brynjólfsdóttir</name>  <name type="person" role="owner" key="BryBen001">Brynjólfur Benedictsen</name>  <name type="person" role="signatory" key="BryBen001">Brynjólfur    Benedictsen</name>  <name type="person" role="owner" key="KarOla001">Kári Ólafsson</name>  <name type="person" role="signatory" key="KarOla001">Kári Ólafsson</name>  <name type="person" role="owner" key="">Þorbjörn Bjarnason</name>  <name type="person" role="signatory" key="ThoBja001">Þorbjörn Bjarnason</name> </provenance>

1.5. Manuscript Parts

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

Since each component of such a composite manuscript will in all likelihood have its own content, physical characterstics, 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 describe the individual parts 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 1</idno>   </altIdentifier> <!-- other information specific to this part here -->  </msPart>  <msPart>   <altIdentifier type="other">    <idno>MS 2</idno>   </altIdentifier> <!-- other information specific to this part here -->  </msPart>  <msPart>   <altIdentifier type="other">    <idno>MS 3</idno>   </altIdentifier> <!-- other information specific to this part here -->  </msPart> <!-- other msParts here --> </msDesc>

2. Transcription

Transcription is encoding which aims is to represent important features of a primary source without relatively little prejudice or editorial intervention. Hence the term diplomatic transcription.

Encodeable features include:

2.1. Text

Manuscript text should be transcribed as UTF8-encoded electronic text. No entities are to be used.

Each distinct word, and any markup associated with it, should be contained within a <w> element. The following example demonstrates this method, as well as several other aspects of text encoding discussed in this section:
<w>  <choice>   <reg>konungasynir</reg>   <orig>k<choice>     <am>̅</am>     <ex>on</ex>    </choice>ga<g ref="#slong"/>yner</orig>  </choice> </w>

2.1.1. Orthography and spacing

The text should be transcribed exactly as it is with respect to orthography and spacing. With the exception of small capitals, used to denote geminates (principally N and R, but potentially also D, G, M, S and T), variant forms of the same letter (allographs) need not be distinguished. It may, in some cases, be deemed necessary also to distinguish between:

  • high and round s
  • ordinary and round r (r-rotunda)
  • ordinary and insular forms of f and v
  • ordinary and uncial forms of d, e, m and t

The means of encoding these characters are discussed below (2.1.6. Variant letter forms).

Note that only ligatures with an independent phonemic value (a and e, double a etc.) are to be represented; ligatures which are the result of graphic economy should be treated as two separate characters (high s + t, for example).
If desired, a <hi> element may be used to indicate text which has been emphasized by the scribe (e.g. large initials):
<w>  <choice>   <orig>    <hi rend="2">Þ</hi>eir</orig>   <reg>Þeir</reg>  </choice> </w>
Note: Discuss gaiji usage

2.1.2. Abbreviations and expansions

Expand abbreviations in accordance with the normal spelling of the scribe in question. Use <am> to encode the abbreviation marker and <ex> to indicate supplied letters. Surround both of these with <choice>:
H<choice>  <am>:</am>  <ex>elgi</ex> </choice>
The <am> element is optional, and if it is not present, then <choice> may also be omitted. Encoding for abbreviation expansions is required:
<w>H<ex>elgi</ex> </w>

2.1.3. Corrections and emendations

Use the <supplied> element to indicate letters which have been added by the editor. The reason attribute is used to indicate the reason for the editorial intervention. Typical values for reason include:
illegible
letters or words which are now unreadable but assumed to have originally been in the manuscript (which in a printed edition would be placed in square brackets)
omitted
letters or words assumed to have been inadvertently omitted by the scribe (which in a printed edition would be placed in angle brackets)
damaged
letters or words assumed to have originally been in the manuscript but are now illegible due to damage
maklig<supplied reason="omitted">t</supplied>
lid<supplied reason="illegible">z</supplied>
If the supplied text has been taken from another authority, such as a printed edition, this information should be encoded within the source attribute. The value of this attribute should correspond to a valid xml:id from the project bibliography:
<w>  <choice>   <orig>h<supplied reason="omitted" source="#KaaGri2000">v</supplied>    <choice>     <am>͛</am>     <ex>er</ex>    </choice>iu</orig>   <reg>h<supplied reason="omitted" source="#KaaGri2000">v</supplied>erju</reg>  </choice> </w>
The <supplied> element should only be used when the missing text can be reconstructed with a very high degree of accuracy. When such is not the case <gap> should be used instead, with both an reason and an extent attribute. The extent should be given as the number of characters presumed missing, which can then be made to display as a series of small noughts, as is customary in a printed edition.

Editorial corrections may be encoded using <sic>, which contains the text from the manuscript, and <corr>, which contains the editor's correction. The <corr> element must always have either a source or resp (e.g. @resp="#BES") attribute:
<w>  <choice>   <sic>    <choice>     <orig>g<choice>       <am>͛</am>       <ex>ior</ex>      </choice>it</orig>     <reg>giorit</reg>    </choice>   </sic>   <corr source="#KaaGri2000">    <choice>     <orig>g<choice>       <am>͛</am>       <ex>ior</ex>      </choice>ir</orig>     <reg>gerir</reg>    </choice>   </corr>  </choice> </w>

2.1.4. Additions and deletions

Additions and deletions made in the manuscript by the scribe or in another hand should be indicated with the <add> and <del> elements; further information may (but need not) be given as attribute values. The placement of additions on the page is indicated with the place attribute:
<add place="margin">  <w>   <choice>    <reg>en</reg>    <orig>enn</orig>   </choice>  </w>  <w>   <choice>    <reg>mér</reg>    <orig>mier</orig>   </choice>  </w> </add>
For deletions, the type attribute might include:
overstrike
the text has been struck-through
overwrite
the text has been overwritten
erase
the text has been erased
subpunction
dots have been placed below the text so as to indicate deletion
superpunction
dots have been placed above the text so as to indicate deletion
<w>  <choice>   <reg>konungsdottir</reg>   <orig>    <del type="overstrike">kongz dottir</del>   </orig>  </choice> </w>
If a portion of text has been substituted by the scribe, then the deletions and additions should be placed within a <subst> element:
<w>  <choice>   <orig>    <subst>     <del type="cancellation" rend="overwrite">ſ</del>     <add place="inline" rend="overwrite">e</add>    </subst>r</orig>   <reg>er</reg>  </choice> </w>
The <surplus> element may be used to indicate text deemed superfluous by an editor. A reason attribute should indicate why the editor deems the material extraneous:
<surplus reason="repeated">  <w>   <choice>    <reg>at</reg>    <orig>ad</orig>   </choice>  </w>  <w>   <choice>    <reg>mér</reg>    <orig> mi<choice>      <am>͛</am>      <ex>er</ex>     </choice>    </orig>   </choice>  </w> </surplus>

2.1.5. Punctuation

The <pc> element is used to encode punctuation characters. Original punctuation from the manuscript is optional, but a level of normalized punctuation is required. When using normalized punctuation, modern standards for capitalization (e.g. at sentence beginnings) should be observed:
<pc>,</pc>
<pc>.</pc>

2.1.6. Variant letter forms

In virtually all cases, Unicode code points are available to encode the abstract characters found in a manuscript. However, in some cases it may be desirable to provide the option of different renderings of a given character. In such cases, the g element may be used, with a ref attribute pointing to a definition of the required character or glyph in the <encodingDesc> section of the document header. Variant letter forms are optional for semi-diplomatic transcriptions.

In the text:
<g ref="#slong"/>mijdi
In the document header:
<glyph xml:id="slong">  <glyphName>LATIN SMALL LETTER LONG S</glyphName>  <mapping type="dipl">ſ</mapping>  <mapping type="codepoint">U+017F</mapping>  <mapping type="norm">s</mapping> </glyph>

2.1.7. Quotations

Direct speech may be encoded by using <q>:
<q>  <w>   <choice>    <reg>Leitið</reg>    <orig>leitid</orig>   </choice>  </w>  <w>   <choice>    <reg>þangat</reg>    <orig>þangad</orig>   </choice>  </w>  <w>   <choice>    <reg>fyrst</reg>    <orig>     <g ref="#fins"/>yr<g ref="#slong"/>t</orig>   </choice>  </w>  <pc>,</pc> </q>

Note: This element is optional.

2.1.8. Proper names

Proper names (e.g. of people or places) should be encoded with the <name> element. The type of name (person, place, animal or object) should be indicated with the type attribute. In semi-diplomatic transcriptions, capitalisation may be normalised:
<name type="person">  <w>   <choice>    <orig>haughne</orig>    <reg>Högni</reg>   </choice>  </w> </name>

2.2. Structure

2.2.1. Boundaries

Indicate line-, column- and page-boundaries using the empty milestone tags <lb>, <cb> and <pb>, giving a number for each as the value of the n attribute.
<lb n="7"/>
<pb n="17v"/>
These elements should come at the beginning of the line/column/page to which they refer.

2.2.2. Divisions

Large structural divisions in the text, such as chapters, should be encoded using the <div> element and the type and n attributes:
<div type="chapter" n="4"> <!-- Content of chapter --> </div>
Each <div> will contain one or more <p> elements.

2.2.3. Headings

If desired, chapter headings may be tagged using <head>, which is placed immediately after <div> and before the first <p>. The nature of the <head>, i.e. whether it is found in the manuscript itself or supplied by an editor, should be indicated in the value of the type attribute, as in the following examples:
<head type="rubric">I. Cap<choice>   <am>.</am>   <ex>itulum</ex>  </choice> </head>
<head type="supplied">Chapter 3</head>

2.2.4. Framework, Catchwords

Use the <fw> element to indicate catchwords. The type attribute is used to indicate the type of catchword. Typical values for type include:

catch
the catchword is located at the bottom of a page and matches the first word of the next page as normal
pseudocatch
a word is positioned like a catchword, but the first word on the following page does not match
last-line-catch
the catchword is written as part of the last line of text and matches the first word of the next page

2.3. Normalisation

The original orthography from the manuscript must be encoded, but an additional level of normalisation may be added. The <reg> element is used to mark the normalised form of a word and the <orig> element to indicate the original spelling. These elements are grouped as alternatives using the <choice> element:
<choice>  <reg>hallardyra</reg>  <orig>hallardira</orig> </choice>
Where the two forms are the same there is obviously no need to use <orig> and <reg>.
More complex encoding is possible, using other elements discussed previously in this section, such as <am> and <ex>:
<choice>  <reg>konungr</reg>  <orig>k<choice>    <am>:</am>    <ex>ongur</ex>   </choice>  </orig> </choice>

3. Authority files

The FASNL project uses a system of authority files for persons, places, repositories and text classes referenced in manuscript descriptions. This prevents repetition of information and greatly reduces the possibility of error.

3.1. Persons

<person sex="1" role="scribe" xml:id="MagJon001">  <persName xml:lang="is">   <forename sort="1">Magnús</forename>   <surname sort="2">Jónsson </surname>  </persName>  <birth when="1835-10-19">19 October 1835</birth>  <death when="1922-05-17">17 May 1922</death>  <residence> From <date>1864</date> Magnús lived at <placeName>    <settlement type="farm">Tjaldanes</settlement>    <region type="county">Dalasýsla</region>    <region type="compass">Western</region>    <country key="IS">Iceland</country>   </placeName>  </residence>  <occupation xml:lang="is">Bóndi, Hreppstjóri</occupation>  <bibl>   <ref target="DM">Dalamenn</ref>   <biblScope type="volume">II</biblScope>   <biblScope type="pages">375</biblScope>  </bibl>  <bibl>   <ref target="IsAev">Íslenzkar æviskrár</ref>   <biblScope type="volume">III</biblScope>   <biblScope type="pages">435-436</biblScope>  </bibl>  <bibl>   <note>AM 957 4to.</note>  </bibl> </person>

3.2. Places

3.3. Repositories

3.4. Text classes

4. Elements<T…

4.1. Elements

4.1.1. <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, comprising a TEI header and a text, either in isolation or as part of a <teiCorpus> element. [4. 15.1. ]
Moduletextstructure — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
versionspecifies the major version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatype
data.version
NoteThe major version number is historically prefixed by a P (for Proposal), and is distinct from the version number used for individual releases of the Guidelines, as used by (for example) the source of the <schemaSpec> element. The current version is P5.
Member of
Contained by
Empty element
May contain
header: teiHeader
textstructure: text
Declaration
element TEI { att.global.attributes, attribute version { data.version }?, ( teiHeader, ( ( model.resourceLike+, text? ) | text ) ) }
Schematron
<s:ns prefix="tei" uri="http://www.tei-c.org/ns/1.0"/>
Schematron
<s:ns prefix="rng" uri="http://relaxng.org/ns/structure/1.0"/>
Example
<TEI version="5.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>The shortest TEI Document Imaginable</title>    </titleStmt>    <publicationStmt>     <p>First published as part of TEI P2, this is the P5          version using a name space.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <text>   <body>    <p>This is about the shortest TEI document imaginable.</p>   </body>  </text> </TEI>
NoteThis element is required.

4.1.2. <accMat>

<accMat> (accompanying material) contains details of any significant additional material which may be closely associated with the manuscript being described, such as non-contemporaneous documents or fragments bound in with the manuscript at some earlier historical period. [10.7.3.3. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.typed (@type, @subtype)
Member of
Contained by
msdescription: physDesc
May contain
Declaration
element accMat { att.global.attributes, att.typed.attributes, macro.specialPara }
Example
<accMat>A copy of a tax form from 1947 is included in the envelope with the letter. It is not catalogued separately.</accMat>

4.1.3. <acquisition>

<acquisition> contains any descriptive or other information concerning the process by which a manuscript or manuscript part entered the holding institution. [10.8. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Member of
Contained by
msdescription: history
May contain
Declaration
element acquisition { att.global.attributes, att.datable.attributes, macro.specialPara }
Example
<acquisition>Left to the <name type="place">Bodleian</name> by <name type="person">Richard Rawlinson</name> in 1755. </acquisition>

4.1.4. <add>

<add> (addition) contains letters, words, or phrases inserted in the text by an author, scribe, annotator, or corrector. [3.4.3. ]
Modulecore — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) ) att.placement (@place) att.typed (@type, @subtype)
Member of
Contained by
May contain
Declaration
element add { att.global.attributes, att.transcriptional.attributes, att.placement.attributes, att.typed.attributes, macro.paraContent }
Example
The story I am going to relate is true as to its main facts, and as to the consequences <add place="above">of these facts</add> from which this tale takes its title.
NoteThe <add> element should not be used for additions made by editors or encoders. In these cases, either the <corr> or <supplied> element should be used.

4.1.5. <addName>

<addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [13.2.1. ]
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
Member of
Contained by
May contain
Declaration
element addName { att.global.attributes, att.personal.attributes, att.typed.attributes, macro.phraseSeq }
Example
<persName>  <forename>Frederick</forename>  <addName type="epithet">the Great</addName>  <roleName>Emperor of Prussia</roleName> </persName>

4.1.6. <addSpan/>

<addSpan/> (added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also <add>). [11.3.1.4. ]
Moduletranscr — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) ) att.placement (@place) att.typed (@type, @subtype) att.spanning (@spanTo)
Member of
Contained by
May containEmpty element
Declaration
element addSpan { att.global.attributes, att.transcriptional.attributes, att.placement.attributes, att.typed.attributes, att.spanning.attributes, empty }
Schematron
<sch:assert test="@spanTo">The spanTo= attribute of <sch:name/> is required.</sch:assert>
Schematron
<sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert>
Example
<handNote xml:id="HEOL" scribe="HelgiÓlafsson"/> <body>  <div/>  <addSpan n="added gathering" hand="#HEOL" spanTo="#P025"/>  <div/>  <div/>  <div/>  <div/>  <anchor xml:id="P025"/>  <div/> </body>
NoteBoth the beginning and the end of the added material must be marked; the beginning by the <addSpan> element itself, the end by the spanTo attribute.

4.1.7. <additional>

<additional> groups additional information, combining bibliographic information about a manuscript, or surrogate copies of it with curatorial or administrative information. [10.9. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
msdescription: msDesc msPart
May contain
msdescription: adminInfo surrogates
Declaration
element additional { att.global.attributes, ( adminInfo?, surrogates?, listBibl? ) }
Example
<additional>  <adminInfo>   <recordHist>    <p/>   </recordHist>   <custodialHist>    <p/>   </custodialHist>  </adminInfo>  <surrogates>   <p/>  </surrogates>  <listBibl>   <bibl/>  </listBibl> </additional>

4.1.8. <additions>

<additions> contains a description of any significant additions found within a manuscript, such as marginalia or other annotations. [10.7.2. ]
Modulemsdescription — 4.
AttributesAttributesatt.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) att.global.facs (@facs) att.global.change (@change)
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived fromatt.global.analytic
StatusRequired
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Valuesone or more valid identifiers of one or more interpretive elements (usually <fs> or <interp>), separated by white space.
Legal values are:
no
low
medium
high
Member of
Contained by
msdescription: physDesc
May contain
Declaration
element additions { att.global.attribute.xmlid, att.global.attribute.n, att.global.attribute.xmllang, att.global.attribute.rend, att.global.attribute.style, att.global.attribute.rendition, att.global.attribute.xmlbase, att.global.attribute.xmlspace, att.global.facs.attribute.facs, att.global.change.attribute.change, attribute ana { list { ( "no" | "low" | "medium" | "high" )+ } }, macro.specialPara }
Example
<additions>  <p>There are several marginalia in this manuscript. Some consist of    single characters and others are figurative. On 8v is to be found a drawing of    a mans head wearing a hat. At times sentences occurs: On 5v:  <q xml:lang="is">Her er skrif andres isslendin</q>,    on 19r: <q xml:lang="is">þeim go</q>,    on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad      batar þad mælgi ok mal</q>,    On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p> </additions>

4.1.9. <adminInfo>

<adminInfo> (administrative information) contains information about the present custody and availability of the manuscript, and also about the record description itself. [10.9.1. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
msdescription: additional
May contain
core: note
header: availability
msdescription: custodialHist recordHist
Declaration
element adminInfo { att.global.attributes, ( recordHist?, availability?, custodialHist?, model.noteLike? ) }
Example
<adminInfo>  <recordHist>   <source>Record created <date>1 Aug 2004</date>   </source>  </recordHist>  <availability>   <p>Until 2015 permission to photocopy some materials from this      collection has been limited at the request of the donor. Please ask repository staff for details      if you are interested in obtaining photocopies from Series 1:      Correspondence.</p>  </availability>  <custodialHist>   <p>Collection donated to the Manuscript Library by the Estate of      Edgar Holden in 1993. Donor number: 1993-034.</p>  </custodialHist> </adminInfo>

4.1.10. <affiliation>

<affiliation> (affiliation) contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [15.2.2. ]
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
May contain
Declaration
element affiliation { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.naming.attributes, macro.phraseSeq }
Example
<affiliation>Junior project officer for the US <name type="org">National Endowment for    the Humanities</name> </affiliation> <affiliation notAfter="1960-01-01" notBefore="1957-02-28">Paid up member of the <orgName>Australian Journalists Association</orgName> </affiliation>
NoteIf included, the name of an organization may be tagged using either the <name> element as above, or the more specific <orgName> element.

4.1.11. <age>

<age> (age) specifies the age of a person.
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
valuesupplies a numeric code representing the age or age group
StatusOptional
Datatype
data.count
NoteThis attribute may be used to complement a more detailed discussion of a person's age in the content of the element
Member of
Contained by
namesdates: person personGrp
May contain
Declaration
element age { att.global.attributes, att.editLike.attributes, att.datable.attributes, attribute value { data.count }?, macro.phraseSeq.limited }
Example
<age value="2" notAfter="1986">under 20 in the early eighties</age>
NoteAs with other culturally-constructed traits such as sex, the way in which this concept is described in different cultural contexts may vary. The normalizing attributes are provided as a means of simplifying that variety to Western European norms and should not be used where that is inappropriate. The content of the element may be used to describe the intended concept in more detail, using plain text.

4.1.12. <altIdentifier>

<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript, such as a former catalogue number. [10.4. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.typed (@type, @subtype)
Member of
Contained by
msdescription: msIdentifier msPart
May contain
Declaration
element altIdentifier { att.global.attributes, att.typed.attributes, ( model.placeNamePart_sequenceOptional, institution?, repository?, collection?, idno, note? ) }
Example
<altIdentifier>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <idno>MS.El.26.C.9</idno> </altIdentifier>
NoteAn identifying number of some kind must be supplied if known; if it is not known, this should be stated.

4.1.13. <am>

<am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [11.3.1.2. ]
Moduletranscr — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp))
Member of
Contained by
May contain
Declaration
element am { att.global.attributes, att.editLike.attributes, ( text | model.gLike | model.pPart.transcriptional )* }
Example
do you <abbr>Mr<am>.</am> </abbr> Jones?
Example
<expan>  <abbr>Aug<am>g</am>  </abbr>  <ex>ustorum duo</ex> </expan>

4.1.14. <appInfo>

<appInfo> (application information) records information about an application which has edited the TEI file.
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
header: encodingDesc
May contain
header: application
Declaration
element appInfo { att.global.attributes, model.applicationLike+ }
Example
<appInfo>  <application version="1.24" ident="Xaira">   <label>XAIRA Indexer</label>   <ptr target="#P1"/>  </application> </appInfo>

4.1.15. <application>

<application> provides information about an application which has acted upon the document.
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
identSupplies an identifier for the application, independent of its version number or display name.
StatusRequired
Datatype
data.name
versionSupplies a version number for the application, independent of its identifier or display name.
StatusRequired
Datatype
token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }
Member of
Contained by
header: appInfo
May contain
core: p ref
Declaration
element application { att.global.attributes, att.typed.attributes, att.datable.attributes, attribute ident { data.name }, attribute version { token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" } }, ( model.labelLike+, ( model.ptrLike* | model.pLike* ) ) }
Example
<appInfo>  <application version="1.5" ident="ImageMarkupTool1" notAfter="2006-06-01">   <label>Image Markup Tool</label>   <ptr target="#P1"/>   <ptr target="#P2"/>  </application> </appInfo>
This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two <ptr> elements.

4.1.16. <author>

<author> in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.11.2.2. 2.2.1. ]
Modulecore — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
core: bibl
msdescription: msItem msItemStruct
May contain
Declaration
element author { att.global.attributes, att.naming.attributes, macro.phraseSeq }
Example
<author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author>  <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author>  <orgName key="BBC">British Broadcasting    Corporation</orgName>: Radio 3 Network </author>
NoteParticularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

4.1.17. <authority>

<authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
May contain
Declaration
element authority { att.global.attributes, macro.phraseSeq.limited }
Example
<authority>John Smith</authority>

4.1.18. <availability>

<availability> supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.declarable (@default)
statussupplies a code identifying the current availability of the text.
StatusOptional
Datatype
data.enumerated
Legal values are:
free
the text is freely available.
unknown
the status of the text is unknown. [Default]
restricted
the text is not freely available.
Member of
Contained by
msdescription: adminInfo
May contain
core: p
header: licence
Declaration
element availability { att.global.attributes, att.declarable.attributes, attribute status { "free" | "unknown" | "restricted" }?, ( model.availabilityPart | model.pLike )+ }
Example
<availability status="restricted">  <p>Available for academic research purposes only.</p> </availability> <availability status="free">  <p>In the public domain</p> </availability> <availability status="restricted">  <p>Available under licence from the publishers.</p> </availability>
Example
<availability>  <licence target="http://opensource.org/licenses/MIT">   <p>The MIT License      applies to this document.</p>   <p>Copyright (C) 2011 by The University of Victoria</p>   <p>Permission is hereby granted, free of charge, to any person obtaining a copy      of this software and associated documentation files (the "Software"), to deal      in the Software without restriction, including without limitation the rights      to use, copy, modify, merge, publish, distribute, sublicense, and/or sell      copies of the Software, and to permit persons to whom the Software is      furnished to do so, subject to the following conditions:</p>   <p>The above copyright notice and this permission notice shall be included in      all copies or substantial portions of the Software.</p>   <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR      IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,      FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE      AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER      LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,      OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN      THE SOFTWARE.</p>  </licence> </availability>
NoteA consistent format should be adopted

4.1.19. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. 4. ]
Moduletextstructure — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.declaring (@decls)
Member of
Contained by
textstructure: text
transcr: facsimile
May contain
Declaration
element back { att.global.attributes, att.declaring.attributes, ( ( model.frontPart | model.pLike.front | model.global )*, ( ( ( ( model.div1Like ), ( model.frontPart | model.div1Like | model.global )* ) | ( ( model.divLike ), ( model.frontPart | model.divLike | model.global )* ) )? ), ( ( ( model.divBottomPart ), ( model.divBottomPart | model.global )* )? ) ) }
Example
<back>  <div1 type="appendix">   <head>The Golden Dream or, the Ingenuous Confession</head>   <p>To shew the Depravity of human Nature </p>  </div1>  <div1 type="epistle">   <head>A letter from the Printer, which he desires may be inserted</head>   <salute>Sir.</salute>   <p>I have done with your Copy, so you may return it to the Vatican, if you please </p>  </div1>  <div1 type="advert">   <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr      Newbery's at the Bible and Sun in St Paul's Church-yard.</head>   <list>    <item n="1">The Christmas Box, Price 1d.</item>    <item n="2">The History of Giles Gingerbread, 1d.</item>    <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,        10 Vol, Pr. bound 1l.</item>   </list>  </div1>  <div1 type="advert">   <head>    <hi rend="center">By the KING's Royal Patent,</hi> Are sold by J. NEWBERY, at the      Bible and Sun in St. Paul's Church-Yard.</head>   <list>    <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c.        2s. 6d</item>    <item n="2">Dr. Hooper's Female Pills, 1s.</item>   </list>  </div1> </back>
NoteThe content model of back matter is identical to that of front matter, reflecting the facts of cultural history.

4.1.20. <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. 2.2.7. 15.3.2. ]
Modulecore — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Declaration
element bibl { att.global.attributes, att.declarable.attributes, att.typed.attributes, att.sortable.attributes, att.docStatus.attributes, ( text | model.gLike | model.highlightedmodel.pPart.datamodel.pPart.edit | model.segLike | model.ptrLikemodel.biblPartmodel.global )* }
Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
<bibl>  <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher>  <date>1968</date>. </bibl>
Example
<bibl type="article" subtype="book_chapter" xml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
NoteContains phrase-level elements, together with any combination of elements from the biblPart class

4.1.21. <biblFull>

<biblFull> (fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present. [3.11.1. 2.2. 2.2.7. 15.3.2. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.declarable (@default) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Declaration
element biblFull { att.global.attributes, att.declarable.attributes, att.sortable.attributes, att.docStatus.attributes, ( ( titleStmt, editionStmt?, extent?, publicationStmt, seriesStmt?, notesStmt? ), sourceDesc* ) }
Example
<biblFull>  <titleStmt>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>  </titleStmt>  <editionStmt>   <edition>UK edition</edition>  </editionStmt>  <extent>1231 pp</extent>  <publicationStmt>   <publisher>Yale University Press</publisher>   <pubPlace>New Haven and London</pubPlace>   <date>1990</date>  </publicationStmt>  <sourceDesc>   <p>No source: this is an original work</p>  </sourceDesc> </biblFull>

4.1.22. <binding>

<binding> contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript. [10.7.3.1. ]
Modulemsdescription — 4.
AttributesAttributes att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) att.global.facs (@facs) att.global.change (@change)
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived fromatt.global.analytic
StatusRequired
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Valuesone or more valid identifiers of one or more interpretive elements (usually <fs> or <interp>), separated by white space.
Legal values are:
none
plain
moderate
decorative
contemporaryspecifies whether or not the binding is contemporary with the majority of its contents
StatusOptional
Datatype
data.xTruthValue
NoteThe value true indicates that the binding is contemporaneous with its contents; the value false that it is not. The value unknown should be used when the date of either binding or manuscript is unknown
Member of
Contained by
msdescription: bindingDesc
May contain
core: p
msdescription: condition decoNote
Declaration
element binding { att.global.attribute.xmlid, att.global.attribute.n, att.global.attribute.xmllang, att.global.attribute.rend, att.global.attribute.style, att.global.attribute.rendition, att.global.attribute.xmlbase, att.global.attribute.xmlspace, att.global.facs.attribute.facs, att.global.change.attribute.change, att.datable.attributes, attribute ana { list { ( "none" | "plain" | "moderate" | "decorative" )+ } }, attribute contemporary { data.xTruthValue }?, ( model.pLike | condition | decoNote )+ }
Example
<binding contemporary="true">  <p>Contemporary blind stamped leather over wooden boards with evidence of a fore edge clasp    closing to the back cover.</p> </binding>
Example
<bindingDesc>  <binding contemporary="false">   <p>Quarter bound by the Phillipps' binder, Bretherton, with his sticker on the front      pastedown.</p>  </binding>  <binding contemporary="false">   <p>Rebound by an unknown 19th c. company; edges cropped and gilt.</p>  </binding> </bindingDesc>

4.1.23. <bindingDesc>

<bindingDesc> (binding description) describes the present and former bindings of a manuscript, either as a series of paragraphs or as a series of distinct <binding> elements, one for each binding of the manuscript. [10.7.3.1. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: binding condition decoNote
Declaration
element bindingDesc { att.global.attributes, ( ( model.pLike | decoNote | condition )+ | binding+ ) }
Example
<bindingDesc>  <p>Sewing not visible; tightly rebound over    19th-cent. pasteboards, reusing panels of 16th-cent. brown leather with    gilt tooling à la fanfare, Paris c. 1580-90, the centre of each    cover inlaid with a 17th-cent. oval medallion of red morocco tooled in    gilt (perhaps replacing the identifying mark of a previous owner); the    spine similarly tooled, without raised bands or title-piece; coloured    endbands; the edges of the leaves and boards gilt.Boxed.</p> </bindingDesc>

4.1.24. <birth>

<birth> (birth) contains information about a person's birth, such as its date and place. [15.2.2. ]
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
namesdates: person personGrp
May contain
Declaration
element birth { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.naming.attributes, macro.phraseSeq }
Example
<birth>Before 1920, Midlands region.</birth>
Example
<birth when="1960-12-10">In a small cottage near <name type="place">Aix-la-Chapelle</name>, early in the morning of <date>10 Dec 1960</date> </birth>

4.1.25. <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. ]
Moduletextstructure — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.declaring (@decls)
Member of
Contained by
textstructure: text
May contain
Declaration
element body { att.global.attributes, att.declaring.attributes, ( model.global*, ( ( model.divTop ), ( model.global | model.divTop )* )?, ( ( model.divGenLike ), ( model.global | model.divGenLike )* )?, ( ( ( model.divLike ), ( model.global | model.divGenLike )* )+ | ( ( model.div1Like ), ( model.global | model.divGenLike )* )+ | ( ( ( model.common ), model.global* )+, ( ( ( model.divLike ), ( model.global | model.divGenLike )* )+ | ( ( model.div1Like ), ( model.global | model.divGenLike )* )+ )? ) ), ( ( model.divBottom ), model.global* )* ) }
Example
<body>  <l>Nu scylun hergan hefaenricaes uard</l>  <l>metudæs maecti end his modgidanc</l>  <l>uerc uuldurfadur sue he uundra gihuaes</l>  <l>eci dryctin or astelidæ</l>  <l>he aerist scop aelda barnum</l>  <l>heben til hrofe haleg scepen.</l>  <l>tha middungeard moncynnæs uard</l>  <l>eci dryctin æfter tiadæ</l>  <l>firum foldu frea allmectig</l>  <trailer>primo cantauit Cædmon istud carmen.</trailer> </body>

4.1.26. <cRefPattern>

<cRefPattern> (canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI. [2.3.6.3. 2.3.6. 2.3.6.2. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.patternReplacement (@matchPattern, @replacementPattern)
Member of
Contained by
header: refsDecl
May contain
core: p
Declaration
element cRefPattern { att.global.attributes, att.patternReplacement.attributes, model.pLike* }
Example
<cRefPattern   matchPattern="([1-9A-Za-z]+)\s+([0-9]+):([0-9]+)"   replacementPattern="#xpath(//div[@type='book'][@n='$1']/div[@type='chap'][@n='$2']/div[@type='verse'][@n='$3'])"/>
NoteThe result of the substitution may be either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the cRef attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

4.1.27. <calendar>

<calendar> describes a calendar or dating system used in a dating formula in the text. [2.4.4. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.pointing (@targetLang, @target, @evaluate)
Member of
Contained by
header: calendarDesc
May contain
core: p
Declaration
element calendar { att.global.attributes, att.pointing.attributes, model.pLike+ }
Example
<calendarDesc>  <calendar xml:id="Julian">   <p>Julian Calendar (including proleptic)</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar    xml:id="Egyptian"    target="http://en.wikipedia.org/wiki/Egyptian_calendar">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>

4.1.28. <calendarDesc>

<calendarDesc> (calendar description) contains a description of the calendar system used in any dating expression found in the text. [2.4. 2.4.4. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
header: profileDesc
May contain
header: calendar
Declaration
element calendarDesc { att.global.attributes, calendar+ }
Example
<calendarDesc>  <calendar xml:id="cal_AD">   <p>Anno Domini (Christian Era)</p>  </calendar>  <calendar xml:id="cal_AH">   <p>Anno Hegirae (Muhammedan Era)</p>  </calendar>  <calendar xml:id="cal_AME">   <p>Mauludi Era (solar years since Mohammed's birth)</p>  </calendar>  <calendar xml:id="cal_AM">   <p>Anno Mundi (Jewish Calendar)</p>  </calendar>  <calendar xml:id="cal_AP">   <p>Anno Persici</p>  </calendar>  <calendar xml:id="cal_AS">   <p>Aji Saka Era (Java)</p>  </calendar>  <calendar xml:id="cal_BE">   <p>Buddhist Era</p>  </calendar>  <calendar xml:id="cal_CB">   <p>Cooch Behar Era</p>  </calendar>  <calendar xml:id="cal_CE">   <p>Common Era</p>  </calendar>  <calendar xml:id="cal_CL">   <p>Chinese Lunar Era</p>  </calendar>  <calendar xml:id="cal_CS">   <p>Chula Sakarat Era</p>  </calendar>  <calendar xml:id="cal_EE">   <p>Ethiopian Era</p>  </calendar>  <calendar xml:id="cal_FE">   <p>Fasli Era</p>  </calendar>  <calendar xml:id="cal_ISO">   <p>ISO 8601 calendar</p>  </calendar>  <calendar xml:id="cal_JE">   <p>Japanese Calendar</p>  </calendar>  <calendar xml:id="cal_KE">   <p>Khalsa Era (Sikh calendar)</p>  </calendar>  <calendar xml:id="cal_KY">   <p>Kali Yuga</p>  </calendar>  <calendar xml:id="cal_ME">   <p>Malabar Era</p>  </calendar>  <calendar xml:id="cal_MS">   <p>Monarchic Solar Era</p>  </calendar>  <calendar xml:id="cal_NS">   <p>Nepal Samwat Era</p>  </calendar>  <calendar xml:id="cal_OS">   <p>Old Style (Julian Calendar)</p>  </calendar>  <calendar xml:id="cal_RS">   <p>Rattanakosin (Bangkok) Era</p>  </calendar>  <calendar xml:id="cal_SE">   <p>Saka Era</p>  </calendar>  <calendar xml:id="cal_SH">   <p>Mohammedan Solar Era (Iran)</p>  </calendar>  <calendar xml:id="cal_SS">   <p>Saka Samvat</p>  </calendar>  <calendar xml:id="cal_TE">   <p>Tripurabda Era</p>  </calendar>  <calendar xml:id="cal_VE">   <p>Vikrama Era</p>  </calendar>  <calendar xml:id="cal_VS">   <p>Vikrama Samvat Era</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="cal_Gregorian">   <p>Gregorian calendar</p>  </calendar>  <calendar xml:id="cal_Julian">   <p>Julian calendar</p>  </calendar>  <calendar xml:id="cal_Islamic">   <p>Islamic or Muslim (hijri) lunar calendar</p>  </calendar>  <calendar xml:id="cal_Hebrew">   <p>Hebrew or Jewish lunisolar calendar</p>  </calendar>  <calendar xml:id="cal_Revolutionary">   <p>French Revolutionary calendar</p>  </calendar>  <calendar xml:id="cal_Iranian">   <p>Iranian or Persian (Jalaali) solar calendar</p>  </calendar>  <calendar xml:id="cal_Coptic">   <p>Coptic or Alexandrian calendar</p>  </calendar>  <calendar xml:id="cal_Chinese">   <p>Chinese lunisolar calendar</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar    xml:id="cal_Egyptian"    target="http://en.wikipedia.org/wiki/Egyptian_calendar">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
NoteIn the first example above, calendars and short codes for xml:ids are from W3 guidelines at

4.1.29. <catDesc>

<catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal textDesc. [2.3.7. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
header: category
May contain
Declaration
element catDesc { att.global.attributes, ( text | model.limitedPhrase | model.catDescPart )* }
Example
<catDesc>Prose reportage</catDesc>
Example
<catDesc>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertain" degree="high"/>   <purpose type="inform" degree="medium"/>  </textDesc> </catDesc>

4.1.30. <catRef/>

<catRef/> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.pointing (@targetLang, @target, @evaluate)
schemeidentifies the classification scheme within which the set of categories concerned is defined
StatusOptional
Datatype
data.pointer
ValuesMay supply the identifier of the associated <taxonomy> element.
Member of
Contained by
header: textClass
May containEmpty element
Declaration
element catRef { att.global.attributes, att.pointing.attributes, attribute scheme { data.pointer }?, empty }
Example
<catRef target="#news #prov #sales2"/> <taxonomy>  <category xml:id="news">   <catDesc>Newspapers</catDesc>  </category>  <category xml:id="prov">   <catDesc>Provincial</catDesc>  </category>  <category xml:id="sales2">   <catDesc>Low to average annual sales</catDesc>  </category> </taxonomy>
NoteThe scheme attribute need be supplied only if more than one taxonomy has been declared

4.1.31. <catchwords>

<catchwords> describes the system used to ensure correct ordering of the quires making up a codex or incunable, typically by means of annotations at the foot of the page. [10.3.7. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
May contain
Declaration
element catchwords { att.global.attributes, macro.phraseSeq }
Example
<catchwords>Vertical catchwords in the hand of the scribe placed along the inner bounding line, reading from top to bottom.</catchwords>

4.1.32. <category>

<category> contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
May contain
Declaration
element category { att.global.attributes, ( ( catDesc+ | ( model.descLike | model.glossLike )* ), category* ) }
Example
<category xml:id="b1">  <catDesc>Prose reportage</catDesc> </category>
Example
<category xml:id="b2">  <catDesc>Prose </catDesc>  <category xml:id="b11">   <catDesc>journalism</catDesc>  </category>  <category xml:id="b12">   <catDesc>fiction</catDesc>  </category> </category>
Example
<category xml:id="LIT">  <catDesc xml:lang="pl">literatura piękna</catDesc>  <catDesc xml:lang="en">fiction</catDesc>  <category xml:id="LPROSE">   <catDesc xml:lang="pl">proza</catDesc>   <catDesc xml:lang="en">prose</catDesc>  </category>  <category xml:id="LPOETRY">   <catDesc xml:lang="pl">poezja</catDesc>   <catDesc xml:lang="en">poetry</catDesc>  </category>  <category xml:id="LDRAMA">   <catDesc xml:lang="pl">dramat</catDesc>   <catDesc xml:lang="en">drama</catDesc>  </category> </category>

4.1.33. <change>

<change> documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.5. 2.4.1. ]
Moduleheader — 4.
AttributesAttributes att.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.docStatus (@status) att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.typed (@type, @subtype)
targetpoints to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Member of
Contained by
msdescription: recordHist
May contain
Declaration
element change { att.ascribed.attributes, att.datable.attributes, att.docStatus.attributes, att.global.attributes, att.typed.attributes, attribute target { list { data.pointer+ } }?, macro.specialPara }
Example
<titleStmt>  <title> ... </title>  <editor xml:id="LDB">Lou Burnard</editor>  <respStmt xml:id="BZ">   <resp>copy editing</resp>   <name>Brett Zamir</name>  </respStmt> </titleStmt> <revisionDesc status="published">  <change who="#BZ" when="2008-02-02" status="public">Finished chapter 23</change>  <change who="#BZ" when="2008-01-02" status="draft">Finished chapter 2</change>  <change n="P2.2" when="1991-12-21" who="#LDB">Added examples to section 3</change>  <change when="1991-11-11" who="#MSM">Deleted chapter 10</change> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange>    <change xml:id="DRAFT1">First draft in pencil</change>    <change xml:id="DRAFT2" notBefore="1880-12-09">First revision, mostly        using green ink</change>    <change xml:id="DRAFT3" notBefore="1881-02-13">Final corrections as        supplied to printer.</change>   </listChange>  </creation> </profileDesc>
NoteThe who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

4.1.34. <classCode>

<classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
schemeidentifies the classification system or taxonomy in use.
StatusRequired
Datatype
data.pointer
Valuesmay point to a local definition, for example in a <taxonomy> element, or more usually to some external location where the scheme is fully defined.
Member of
Contained by
header: textClass
May contain
Declaration
element classCode { att.global.attributes, attribute scheme { data.pointer }, macro.phraseSeq.limited }
Example
<classCode scheme="http://www.udc.org">410</classCode>

4.1.35. <classDecl>

<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. 2.3. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
header: encodingDesc
May contain
header: taxonomy
Declaration
element classDecl { att.global.attributes, taxonomy+ }
Example
<classDecl>  <taxonomy xml:id="LCSH">   <bibl>Library of Congress Subject Headings</bibl>  </taxonomy> </classDecl> <textClass>  <keywords scheme="#LCSH">   <term>Political science</term>   <term>United States -- Politics and government —      Revolution, 1775-1783</term>  </keywords> </textClass>

4.1.36. <collation>

<collation> contains a description of how the leaves or bifolia are physically arranged. [10.7.1. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
msdescription: supportDesc
May contain
Declaration
element collation { att.global.attributes, macro.specialPara }
Example
<collation>The written leaves preceded by an original flyleaf, conjoint with the pastedown.</collation>
Example
<collation>  <p>   <formula>1-5.8 6.6 (catchword, f. 46, does not match following text)      7-8.8 9.10, 11.2 (through f. 82) 12-14.8 15.8(-7)</formula>   <catchwords>Catchwords are written horizontally in center      or towards the right lower margin in various manners:      in red ink for quires 1-6 (which are also signed in red      ink with letters of the alphabet and arabic numerals);      quires 7-9 in ink of text within yellow decorated frames;      quire 10 in red decorated frame; quire 12 in ink of text;      quire 13 with red decorative slashes; quire 14 added in      cursive hand.</catchwords>  </p> </collation>

4.1.37. <collection>

<collection> contains the name of a collection of manuscripts, not necessarily located within a single repository. [10.4. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype)
Member of
Contained by
May containCharacter data only
Declaration
element collection { att.global.attributes, att.naming.attributes, att.typed.attributes, macro.xtext }
Example
<msIdentifier>  <country>USA</country>  <region>California</region>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <collection>Ellesmere</collection>  <idno>El 26 C 9</idno>  <msName>The Ellesmere Chaucer</msName> </msIdentifier>

4.1.38. <colophon>

<colophon> contains the colophon of a manuscript item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript. [10.6.1. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
msdescription: msItem msItemStruct
May contain
Declaration
element colophon { att.global.attributes, macro.phraseSeq }
Example
<colophon>Ricardus Franciscus Scripsit Anno Domini 1447.</colophon>
Example
<colophon>Explicit expliceat/scriptor ludere eat.</colophon>
Example
<colophon>Explicit venenum viciorum domini illius, qui comparavit Anno domini Millessimo Trecentesimo nonagesimo primo, Sabbato in festo sancte Marthe virginis gloriose. Laus tibi criste quia finitur libellus iste.</colophon>

4.1.39. <condition>

<condition> contains a description of the physical condition of the manuscript. [10.7.1.5. ]
Modulemsdescription — 4.
AttributesAttributesatt.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) att.global.facs (@facs) att.global.change (@change)
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived fromatt.global.analytic
StatusRequired
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Valuesone or more valid identifiers of one or more interpretive elements (usually <fs> or <interp>), separated by white space.
Legal values are:
poor
average
good
unknown
Member of
Contained by
May contain
Declaration
element condition { att.global.attribute.xmlid, att.global.attribute.n, att.global.attribute.xmllang, att.global.attribute.rend, att.global.attribute.style, att.global.attribute.rendition, att.global.attribute.xmlbase, att.global.attribute.xmlspace, att.global.facs.attribute.facs, att.global.change.attribute.change, attribute ana { list { ( "poor" | "average" | "good" | "unknown" )+ } }, macro.specialPara }
Example
<condition>  <p>There are lacunae in three places in this    manuscript. After 14v two    leaves has been cut out and narrow strips leaves remains in the spine. After    68v one gathering is missing and after 101v at least one gathering of 8 leaves    has been lost. </p>  <p>Several leaves are damaged with tears or holes or have a    irregular shape. Some of the damages do not allow the lines to be of full    length and they are apparently older than the script. There are tears on fol.    2r-v, 9r-v, 10r-v, 15r-18v, 19r-v, 20r-22v, 23r-v, 24r-28v, 30r-v, 32r-35v,    37r-v, 38r-v, 40r-43v, 45r-47v, 49r-v, 51r-v, 53r-60v, 67r-v, 68r-v, 70r-v,    74r-80v, 82r-v, 86r-v, 88r-v, 89r-v, 95r-v, 97r-98v 99r-v, 100r-v. On fol. 98    the corner has been torn off. Several leaves are in a bad condition due to    moist and wear, and have become dark, bleached or    wrinkled. </p>  <p>The script has been    touched up in the 17th century with black ink. The touching up on the following    fols. was done by  <name>Bishop Brynjólf Sveinsson</name>: 1v, 3r, 4r, 5r,    6v, 8v,9r, 10r, 14r, 14v, 22r,30v, 36r-52v, 72v, 77r,78r,103r, 104r,. An    AM-note says according to the lawman  <name>Sigurður Björnsson</name> that the rest of the    touching up was done by himself and another lawman  <name>Sigurður Jónsson</name>.  <name>Sigurður Björnsson</name> did the touching up    on the following fols.: 46v, 47r, 48r, 49r-v, 50r, 52r-v.  <name>Sigurður Jónsson</name> did the rest of the    touching up in the section 36r-59r containing  <title>Bretasögur</title>  </p> </condition>

4.1.40. <correction>

<correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. 15.3.2. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.declarable (@default)
statusindicates the degree of correction applied to the text.
StatusOptional
Datatype
data.enumerated
Legal values are:
high
the text has been thoroughly checked and proofread.
medium
the text has been checked at least once.
low
the text has not been checked.
unknown
the correction status of the text is unknown. [Default]
methodindicates the method adopted to indicate corrections within the text.
StatusOptional
Datatype
data.enumerated
Legal values are:
silent
corrections have been made silently [Default]
markup
corrections have been represented using markup
Member of
Contained by
May contain
core: p
Declaration
element correction { att.global.attributes, att.declarable.attributes, attribute status { "high" | "medium" | "low" | "unknown" }?, attribute method { "silent" | "markup" }?, model.pLike+ }
Example
<correction>  <p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user    defined dictionary of 500 extra words taken from Chambers Twentieth Century    Dictionary.</p> </correction>
NoteMay be used to note the results of proof reading the text against its original, indicating (for example) whether discrepancies have been silently rectified, or recorded using the editorial tags described in section 3.4..

4.1.41. <country>

<country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. ]
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Member of
Contained by
May contain
Declaration
element country { att.global.attributes, att.naming.attributes, att.typed.attributes, att.datable.attributes, macro.phraseSeq }
Example
<country key="DK">Denmark</country>
NoteThe recommended source for codes to represent coded country names is ISO 3166.

4.1.42. <creation>

<creation> contains information about the creation of a text. [2.4.1. 2.4. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Member of
Contained by
header: profileDesc
May contain
Declaration
element creation { att.global.attributes, att.datable.attributes, ( text | model.limitedPhrase | listChange )* }
Example
<creation>  <date>Before 1987</date> </creation>
Example
<creation>  <date when="1988-07-10">10 July 1988</date> </creation>
NoteThe <creation> element may be used to record details of a text's creation, e.g. the date and place it was composed, if these are of interest.It may also contain a more structured account of the various stages or revisions associated with the evolution of a text; this should be encoded using the <listChange> element. It should not be confused with the <publicationStmt> element, which records date and place of publication.

4.1.43. <custEvent>

<custEvent> (custodial event) describes a single event during the custodial history of a manuscript. [10.9.1.2. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type, @subtype)
Member of
Contained by
msdescription: custodialHist
May contain
Declaration
element custEvent { att.global.attributes, att.datable.attributes, att.typed.attributes, macro.specialPara }
Example
<custEvent type="photography">Photographed by David Cooper on <date>12 Dec 1964</date> </custEvent>

4.1.44. <custodialHist>

<custodialHist> (custodial history) contains a description of a manuscript's custodial history, either as running prose or as a series of dated custodial events. [10.9.1.2. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
msdescription: adminInfo
May contain
core: p
msdescription: custEvent
Declaration
element custodialHist { att.global.attributes, ( model.pLike+ | custEvent+ ) }
Example
<custodialHist>  <custEvent type="conservation" notBefore="1961-03" notAfter="1963-02">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="transfer-dispatch" notBefore="1989-11-13" notAfter="1989-11-13">Dispatched to Iceland    13 November 1989.</custEvent> </custodialHist>

4.1.45. <damage>

<damage> contains an area of damage to the text witness. [11.3.3.1. ]
Moduletranscr — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.typed (@type, @subtype) att.damaged (@hand, @agent, @degree, @group) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) )
Member of
Contained by
May contain
Declaration
element damage { att.global.attributes, att.typed.attributes, att.damaged.attributes, macro.paraContent }
Example
<l>The Moving Finger wri<damage agent="water" group="1">es; and</damage> having writ,</l> <l>Moves <damage agent="water" group="1">   <supplied>on: nor all your</supplied>  </damage> Piety nor Wit</l>
NoteSince damage to text witnesses frequently makes them harder to read, the <damage> element will often contain an <unclear> element. If the damaged area is not continuous (e.g. a stain affecting several strings of text), the group attribute may be used to group together several related <damage> elements; alternatively the <join> element may be used to indicate which <damage> and <unclear> elements are part of the same physical phenomenon.The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. for discussion of which element is appropriate for which circumstance.

4.1.46. <damageSpan/>

<damageSpan/> (damaged span of text) marks the beginning of a longer sequence of text which is damaged in some way but still legible. [11.3.3.1. ]
Moduletranscr — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.damaged (@hand, @agent, @degree, @group) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) att.typed (@type, @subtype) att.spanning (@spanTo)
Member of
Contained by
May containEmpty element
Declaration
element damageSpan { att.global.attributes, att.damaged.attributes, att.typed.attributes, att.spanning.attributes, empty }
Schematron
<s:assert test="@spanTo">The @spanTo attribute of <s:name/> is required.</s:assert>
Schematron
<s:assert test="@spanTo">L'attribut spanTo est requis.</s:assert>
Example
<p>Paragraph partially damaged. This is the undamaged portion <damageSpan spanTo="#a34"/>and this the damaged portion of the paragraph.</p> <p>This paragraph is entirely damaged.</p> <p>Paragraph partially damaged; in the middle of this paragraph the damage ends and the anchor point marks the start of the <anchor xml:id="a34"/> undamaged part of the text. ...</p>
NoteBoth the beginning and ending of the damaged sequence must be marked: the beginning by the <damageSpan> element, the ending by the target of the spanTo attribute: if no other element available, the <anchor> element may be used for this purpose.The damaged text must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <damageSpan> element should not be used. Rather, the <gap> or <unclear> element should be employed, with the value of the reason attribute giving the cause. See further sections 11.3.3.1. and 11.3.3.2..

4.1.47. <date>

<date> contains a date in any format. [3.5.4. 2.2.4. 2.5. 3.11.2.3. 15.2.3. 13.3.6. ]
Modulecore — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) att.typed (@type, @subtype)
Member of
Contained by
May contain
Declaration
element date { att.global.attributes, att.datable.attributes, att.editLike.attributes, att.typed.attributes, ( text | model.gLike | model.phrase | model.global )* }
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>

4.1.48. <death>

<death> (death) contains information about a person's death, such as its date and place. [15.2.2. ]
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
namesdates: person personGrp
May contain
Declaration
element death { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.naming.attributes, macro.phraseSeq }
Example
<death when="1902-10-01"/>
Example
<death when="1960-12-10">Passed away near <name type="place">Aix-la-Chapelle</name>, after suffering from cerebral palsy. </death>

4.1.49. <decoDesc>

<decoDesc> (decoration description) contains a description of the decoration of a manuscript, either as a sequence of paragraphs, or as a sequence of topically organized <decoNote> elements. [10.7.3. ]
Modulemsdescription — 4.
AttributesAttributesatt.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) att.global.facs (@facs) att.global.change (@change)
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived fromatt.global.analytic
StatusRequired
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Valuesone or more valid identifiers of one or more interpretive elements (usually <fs> or <interp>), separated by white space.
Legal values are:
no
low
medium
high
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: decoNote summary
Declaration
element decoDesc { att.global.attribute.xmlid, att.global.attribute.n, att.global.attribute.xmllang, att.global.attribute.rend, att.global.attribute.style, att.global.attribute.rendition, att.global.attribute.xmlbase, att.global.attribute.xmlspace, att.global.facs.attribute.facs, att.global.change.attribute.change, attribute ana { list { ( "no" | "low" | "medium" | "high" )+ } }, ( model.pLike+ | ( summary?, decoNote+ ) ) }
Example
<decoDesc>  <p>The start of each book of the Bible with a 10-line historiated    illuminated initial; prefaces decorated with 6-line blue initials with red    penwork flourishing; chapters marked by 3-line plain red initials; verses    with 1-line initials, alternately blue or red.</p> </decoDesc>

4.1.50. <decoNote>

<decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript, or a fairly homogenous class of such components. [10.7.3. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.typed (type, @subtype)
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatype
data.enumerated
Legal values are:
border
diagram
initial
marginal
miniature
mixed
paratext
secondary
other
illustration
printmark
publishmark
vignette
frieze
map
unspecified
Member of
Contained by
May contain
Declaration
element decoNote { att.global.attributes, att.typed.attribute.subtype, attribute type { "border" | "diagram" | "initial" | "marginal" | "miniature" | "mixed" | "paratext" | "secondary" | "other" | "illustration" | "printmark" | "publishmark" | "vignette" | "frieze" | "map" | "unspecified" }?, macro.specialPara }
Example
<decoDesc>  <decoNote type="initial">   <p>The start of each book of the Bible with      a 10-line historiated illuminated initial;      prefaces decorated with 6-line blue initials      with red penwork flourishing; chapters marked by      3-line plain red initials; verses with 1-line initials,      alternately blue or red.</p>  </decoNote> </decoDesc>

4.1.51. <del>

<del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, annotator, or corrector. [3.4.3. ]
Modulecore — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) ) att.typed (@type, @subtype)
Member of
Contained by
May contain
Declaration
element del { att.global.attributes, att.transcriptional.attributes, att.typed.attributes, macro.paraContent }
Example
<l>  <del rend="overtyped">Mein</del> Frisch <del rend="overstrike" type="primary">schwebt</del> weht der Wind </l>
Example
<del rend="overstrike">  <gap reason="illegible" quantity="5" unit="character"/> </del>
NoteDegrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 21.).This element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the <gap> tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the <gap> element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way.There is a clear distinction in the TEI between <del>, which is a statement of the the or a later scribe's intent to cancel or remove text, and elements such as <gap> or <unclear> which signal the editor's decision to omit or inability to read the text remaining. See further sections 11.3.1.7. and, for the close association of the <del> tag with the <gap>, <damage>, <unclear> and <supplied> elements (the latter three tags available when using the additional tagset for transcription of primary sources), 11.3.3.2..The <del> tag should not be used for deletions made by editors or encoders. In these cases, either <corr>, <surplus> or <gap> should be used.

4.1.52. <delSpan/>

<delSpan/> (deleted span of text) marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector. [11.3.1.4. ]
Moduletranscr — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) ) att.typed (@type, @subtype) att.spanning (@spanTo)
Member of
Contained by
May containEmpty element
Declaration
element delSpan { att.global.attributes, att.transcriptional.attributes, att.typed.attributes, att.spanning.attributes, empty }
Schematron
<s:assert test="@spanTo">The spanTo= attribute of <s:name/> is required.</s:assert>
Schematron
<s:assert test="@spanTo">L'attribut spanTo est requis.</s:assert>
Example
<p>Paragraph partially deleted. This is the undeleted portion <delSpan spanTo="#a23"/>and this the deleted portion of the paragraph.</p> <p>Paragraph deleted together with adjacent material.</p> <p>Second fully deleted paragraph.</p> <p>Paragraph partially deleted; in the middle of this paragraph the deletion ends and the anchor point marks the resumption <anchor xml:id="a23"/> of the text. ...</p>
NoteBoth the beginning and ending of the deleted sequence must be marked: the beginning by the <delSpan> element, the ending by the target of the spanTo attribute.The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <delSpan> tag should not be used. Rather, the <gap> tag should be employed to signal that text cannot be transcribed, with the value of the reason attribute giving the cause for the omission from the transcription as deletion. If it is not fully legible, the <unclear> element should be used to signal the areas of text which cannot be read with confidence. See further sections 11.3.1.7. and, for the close association of the <delSpan> tag with the <gap>, <damage>, <unclear> and <supplied> elements, 11.3.3.2..The <delSpan> tag should not be used for deletions made by editors or encoders. In these cases, either the <corr> tag or the <gap> tag should be used.

4.1.53. <depth>

<depth> contains a measurement measured across the spine of a book or codex, or (for other text-bearing objects) perpendicular to the measurement given by the ‘width’ element. [10.3.4. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May containCharacter data only
Declaration
element depth { att.global.attributes, att.dimensions.attributes, macro.xtext }
Example
<depth unit="in" quantity="4"/>
NoteIf used to specify the width of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘width’ axis.

4.1.54. <dim>

<dim> contains any single measurement forming part of a dimensional specification of some sort. [10.3.4. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.typed (@type, @subtype) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May containCharacter data only
Declaration
element dim { att.global.attributes, att.typed.attributes, att.dimensions.attributes, macro.xtext }
Example
<dim type="circumference" extent="4.67 in"/>
NoteThe specific elements <width>, <height>, and <depth> should be used in preference to this generic element wherever appropriate.

4.1.55. <dimensions>

<dimensions> contains a dimensional specification. [10.3.4. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
typeindicates which aspect of the object is being measured.
StatusRequired
Datatype
data.enumerated
Legal values are:
leaf
binding
slip
written
boxed
unknown
Member of
Contained by
May contain
msdescription: depth dim height width
Declaration
element dimensions { att.global.attributes, att.dimensions.attributes, attribute type { "leaf" | "binding" | "slip" | "written" | "boxed" | "unknown" }, ( ( dim | model.dimLike )* ) }
Schematron
<s:report test="count(tei:width)> 1">The element <s:name/> may appear once only </s:report> <s:report test="count(tei:height)> 1">The element <s:name/> may appear once only </s:report> <s:report test="count(tei:depth)> 1">The element <s:name/> may appear once only </s:report>
Example
<dimensions type="leaves">  <height scope="range">157-160</height>  <width>105</width> </dimensions> <dimensions type="ruled">  <height scope="most">90</height>  <width scope="most">48</width> </dimensions> <dimensions unit="in">  <height>12</height>  <width>10</width> </dimensions>
ExampleThis element may be used to record the dimensions of any text-bearing object, not necessarily a codex. For example:
<dimensions type="panels">  <height scope="all">7004</height>  <width scope="all">1803</width>  <dim type="relief" unit="mm">345</dim> </dimensions>
This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm.
ExampleWhen simple numeric quantities are involved, they may be expressed on the quantity attribute of any or all of the child elements, as in the following example:
<dimensions type="leaves">  <height scope="range">157-160</height>  <width quantity="105"/> </dimensions> <dimensions type="ruled">  <height unit="cm" scope="most" quantity="90"/>  <width unit="cm" scope="most" quantity="48"/> </dimensions> <dimensions unit="in">  <height quantity="12"/>  <width quantity="10"/> </dimensions>
NoteContains no more than one of each of the specialized elements used to express a three-dimensional object's height, width, and depth, combined with any number of other kinds of dimensional specification.

4.1.56. <distributor>

<distributor> supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
core: bibl
May contain
Declaration
element distributor { att.global.attributes, macro.phraseSeq }
Example
<distributor>Oxford Text Archive</distributor> <distributor>Redwood and Burn Ltd</distributor>

4.1.57. <district>

<district> contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. [13.2.3. ]
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Member of
Contained by
May contain
Declaration
element district { att.global.attributes, att.naming.attributes, att.typed.attributes, att.datable.attributes, macro.phraseSeq }
Example
<placeName>  <district type="ward">Jericho</district>  <settlement>Oxford</settlement> </placeName>
Example
<placeName>  <district type="area">South Side</district>  <settlement>Chicago</settlement> </placeName>

4.1.58. <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. ]
Moduletextstructure — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.divLike (@org, @sample) (att.fragmentable (@part)) att.typed (@type, @subtype) att.declaring (@decls)
Member of
Contained by
textstructure: back body div
May contain
Declaration
element div { att.global.attributes, att.divLike.attributes, att.typed.attributes, att.declaring.attributes, ( ( model.divTop | model.global )*, ( ( ( ( ( model.divLike | model.divGenLike ), model.global* )+ ) | ( ( ( model.common ), model.global* )+, ( ( model.divLike | model.divGenLike ), model.global* )* ) ), ( ( model.divBottom ), model.global* )* )? ) }
Example
<body>  <div type="part">   <head>Fallacies of Authority</head>   <p>The subject of which is Authority in various shapes, and the object, to repress all      exercise of the reasoning faculty.</p>   <div n="1" type="chapter">    <head>The Nature of Authority</head>    <p>With reference to any proposed measures having for their object the greatest        happiness of the greatest number....</p>    <div n="1.1" type="section">     <head>Analysis of Authority</head>     <p>What on any given occasion is the legitimate weight or influence to be attached to          authority ... </p>    </div>    <div n="1.2" type="section">     <head>Appeal to Authority, in What Cases Fallacious.</head>     <p>Reference to authority is open to the charge of fallacy when... </p>    </div>   </div>  </div> </body>

4.1.59. <edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
core: bibl
header: editionStmt
May contain
Declaration
element edition { att.global.attributes, macro.phraseSeq }
Example
<edition>First edition <date>Oct 1990</date> </edition> <edition n="S2">Students' edition</edition>

4.1.60. <editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. 2.2. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
May contain
Declaration
element editionStmt { att.global.attributes, ( model.pLike+ | ( edition, model.respLike* ) ) }
Example
<editionStmt>  <edition n="S2">Students' edition</edition>  <respStmt>   <resp>Adapted by </resp>   <name>Elizabeth Kirk</name>  </respStmt> </editionStmt>
Example
<editionStmt>  <p>First edition, <date>Michaelmas Term, 1991.</date>  </p> </editionStmt>

4.1.61. <editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.11.2.2. ]
Modulecore — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
core: bibl
msdescription: msItem
May contain
Declaration
element editor { att.global.attributes, att.naming.attributes, macro.phraseSeq }
Example
<editor>Eric Johnson</editor> <editor role="illustrator">John Tenniel</editor>
NoteA consistent format should be adopted.Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.

4.1.62. <editorialDecl>

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. 2.3. 15.3.2. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.declarable (@default)
Member of
Contained by
header: encodingDesc
May contain
Declaration
element editorialDecl { att.global.attributes, att.declarable.attributes, ( model.pLike | model.editorialDeclPart )+ }
Example
<editorialDecl>  <normalization>   <p>All words converted to Modern American spelling using      Websters 9th Collegiate dictionary   </p>  </normalization>  <quotation marks="all">   <p>All opening quotation marks converted to “ all closing      quotation marks converted to &amp;cdq;.</p>  </quotation> </editorialDecl>

4.1.63. <education>

<education> contains a description of the educational experience of a person. [15.2.2. ]
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
namesdates: person personGrp
May contain
Declaration
element education { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.naming.attributes, macro.phraseSeq }
Example
<education>Left school at age 16</education> <education notBefore="1986-01-01" notAfter="1990-06-30">Attended <name>Cherwell School</name> </education>

4.1.64. <encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. 2.1.1. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
header: teiHeader
May contain
Declaration
element encodingDesc { att.global.attributes, ( ( model.encodingDescPart | model.pLike )+ ) }
Example
<encodingDesc>  <p>Basic encoding, capturing lexical information only. All    hyphenation, punctuation, and variant spellings normalized. No    formatting or layout information preserved.</p> </encodingDesc>

4.1.65. <event>

<event> (event) contains data relating to any kind of significant event associated with a person, place, or organization.
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.sortable (@sortKey)
whereindicates the location of an event by pointing to a <place> element
StatusOptional
Datatype
data.pointer
Member of
Contained by
May contain
core: bibl note p
header: biblFull
msdescription: msDesc
namesdates: event relationGrp
Declaration
element event { att.global.attributes, att.datable.attributes, att.editLike.attributes, att.typed.attributes, att.naming.attributes, att.sortable.attributes, attribute where { data.pointer }?, ( model.headLike*, ( ( model.pLike+ ) | ( model.labelLike+ ) ), ( model.noteLike | model.biblLike | linkGrp | link )*, event* ) }
Example
<person>  <event type="mat" when="1972-10-12">   <label>matriculation</label>  </event>  <event type="grad" when="1975-06-23">   <label>graduation</label>  </event> </person>

4.1.66. <ex>

<ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. [11.3.1.2. ]
Moduletranscr — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp))
Member of
Contained by
May containCharacter data only
Declaration
element ex { att.global.attributes, att.editLike.attributes, macro.xtext }
Example
The address is Southmoor <choice>  <expan>R<ex>oa</ex>d</expan>  <abbr>Rd</abbr> </choice>

4.1.67. <explicit>

<explicit> contains the explicit of a manuscript item, that is, the closing words of the text proper, exclusive of any rubric or colophon which might follow it. [10.6.1. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.typed (@type, @subtype) att.msExcerpt (@defective)
Member of
Contained by
msdescription: msItem msItemStruct
May contain
Declaration
element explicit { att.global.attributes, att.typed.attributes, att.msExcerpt.attributes, macro.phraseSeq }
Example
<explicit>sed libera nos a malo.</explicit> <rubric>Hic explicit oratio qui dicitur dominica.</rubric> <explicit type="defective">ex materia quasi et forma sibi proporti<gap/> </explicit> <explicit type="reverse">saued be shulle that doome of day the at </explicit>

4.1.68. <extent>

<extent> describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. 2.2. 3.11.2.3. 10.7.1. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
core: bibl
msdescription: supportDesc
May contain
Declaration
element extent { att.global.attributes, macro.phraseSeq }
Example
<extent>3200 sentences</extent> <extent>between 10 and 20 Mb</extent> <extent>ten 3.5 inch high density diskettes</extent>

4.1.69. <facsimile>

<facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. ]
Moduletranscr — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.declaring (@decls)
Member of
Contained by
textstructure: TEI
May contain
textstructure: back
Declaration
element facsimile { att.global.attributes, att.declaring.attributes, ( front?, ( model.graphicLike | surface | surfaceGrp )+, back? ) }
Example
<facsimile>  <graphic url="page1.png"/>  <surface>   <graphic url="page2-highRes.png"/>   <graphic url="page2-lowRes.png"/>  </surface>  <graphic url="page3.png"/>  <graphic url="page4.png"/> </facsimile>
Example
<facsimile>  <surface    ulx="0"    uly="0"    lrx="200"    lry="300">   <graphic url="Bovelles-49r.png"/>  </surface> </facsimile>

4.1.70. <faith>

<faith> specifies the faith, religion, or belief set of a person.
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.canonical (@key, @ref)
Member of
Contained by
namesdates: person personGrp
May contain
Declaration
element faith { att.global.attributes, att.editLike.attributes, att.datable.attributes, att.canonical.attributes, macro.phraseSeq }
Example
<faith>protestant</faith>
Example
<faith ref="http://dbpedia.org/page/Manichaeism">Manichaeism</faith>

4.1.71. <fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. 2.1.1. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
header: teiHeader
May contain
Declaration
element fileDesc { att.global.attributes, ( ( titleStmt, editionStmt?, extent?, publicationStmt, seriesStmt?, notesStmt? ), sourceDesc+ ) }
Example
<fileDesc>  <titleStmt>   <title>The shortest possible TEI document</title>  </titleStmt>  <publicationStmt>   <p>Distributed as part of TEI P5</p>  </publicationStmt>  <sourceDesc>   <p>No print source exists: this is an original digital text</p>  </sourceDesc> </fileDesc>
NoteThe major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

4.1.72. <filiation>

<filiation> contains information concerning the manuscript's filiation, i.e. its relationship to other surviving manuscripts of the same text, its protographs, antigraphs and apographs. [10.6.1. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.typed (@type, @subtype)
Member of
Contained by
msdescription: msItem
May contain
Declaration
element filiation { att.global.attributes, att.typed.attributes, macro.specialPara }
Example
<msContents>  <msItem>   <title>Beljakovski sbornik</title>   <filiation type="protograph">Bulgarian</filiation>   <filiation type="antigraph">Middle Bulgarian</filiation>   <filiation type="apograph">    <ref target="#DN17">Dujchev N 17</ref>   </filiation>  </msItem> </msContents> <msDesc xml:id="DN17">  <msIdentifier>   <settlement>Faraway</settlement>  </msIdentifier> </msDesc>
In this example, the reference to ‘Dujchev N17’ includes a link to some other manuscript description which has the identifier DN17.
Example
<msItem>  <title>Guan-ben</title>  <filiation>   <p>The "Guan-ben" was widely current among mathematicians in the      Qing dynasty, and "Zhao Qimei version" was also read. It is      therefore difficult to know the correct filiation path to follow.      The study of this era is much indebted to Li Di. We explain the      outline of his conclusion here. Kong Guangsen      (1752-1786)(17) was from the same town as Dai Zhen, so he obtained      "Guan-ben" from him and studied it(18). Li Huang (d. 1811)      (19) took part in editing Si Ku Quan Shu, so he must have had      "Guan-ben". Then Zhang Dunren (1754-1834) obtained this version,      and studied "Da Yan Zong Shu Shu" (The General Dayan      Computation). He wrote Jiu Yi Suan Shu (Mathematics      Searching for One, 1803) based on this version of Shu Xue Jiu      Zhang (20).</p>   <p>One of the most important persons in restoring our knowledge      concerning the filiation of these books was Li Rui (1768(21)      -1817)(see his biography). ... only two volumes remain of this      manuscript, as far as chapter 6 (chapter 3 part 2) p.13, that is,      question 2 of "Huan Tian San Ji" (square of three loops),      which later has been lost.</p>  </filiation> </msItem>

4.1.73. <finalRubric>

<finalRubric> contains the string of words that denotes the end of a text division, often with an assertion as to its author and title, usually set off from the text itself by red ink, by a different size or type of script, or by some other such visual device. [10.6.1. ]
Modulemsdescription — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.typed (@type, @subtype)
Member of
Contained by
msdescription: msItem msItemStruct
May contain
Declaration
element finalRubric { att.global.attributes, att.typed.attributes, macro.phraseSeq }
Example
<finalRubric>Explicit le romans de la Rose ou l'art d'amours est toute enclose.</finalRubric> <finalRubric>ok lúkv ver þar Brennu-Nials savgv</finalRubric>

4.1.74. <floruit>

<floruit> contains information about a person's period of activity.
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp))
Member of
Contained by
namesdates: person personGrp
May contain
Declaration
element floruit { att.global.attributes, att.datable.attributes, att.editLike.attributes, macro.phraseSeq }
Example
<floruit notBefore="1066" notAfter="1100"/>

4.1.75. <foliation>

<foliation> describes the numbering system or systems used to count the leaves or pages in a codex. [10.7.1.4. ]
Modulemsdescription — 4.
AttributesAttributesatt.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) att.global.facs (@facs) att.global.change (@change)
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived fromatt.global.analytic
StatusRequired
Datatype1–∞ occurrences of 
data.pointer
separated by whitespace
Valuesone or more valid identifiers of one or more interpretive elements (usually <fs> or <interp>), separated by white space.
Legal values are:
no
contemporary
later
pag
col
fol
Member of
Contained by
msdescription: supportDesc
May contain
Declaration
element foliation { att.global.attribute.xmlid, att.global.attribute.n, att.global.attribute.xmllang, att.global.attribute.rend, att.global.attribute.style, att.global.attribute.rendition, att.global.attribute.xmlbase, att.global.attribute.xmlspace, att.global.facs.attribute.facs, att.global.change.attribute.change, attribute ana { list { ( "no" | "contemporary" | "later" | "pag" | "col" | "fol" )+ } }, macro.specialPara }
Example
<foliation>Contemporary foliation in red roman numerals in the centre of the outer margin.</foliation>

4.1.76. <forename>

<forename> contains a forename, given or baptismal name. [13.2.1. ]
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
Member of
Contained by
May contain
Declaration
element forename { att.global.attributes, att.personal.attributes, att.typed.attributes, macro.phraseSeq }
Example
<persName>  <roleName>Ex-President</roleName>  <forename>George</forename>  <surname>Bush</surname> </persName>

4.1.77. <funder>

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. ]
Moduleheader — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
Member of
Contained by
core: bibl
msdescription: msItem
May contain
Declaration
element funder { att.global.attributes, macro.phraseSeq.limited }
Example
<funder>The National Endowment for the Humanities, an independent federal agency</funder> <funder>Directorate General XIII of the Commission of the European Communities</funder> <funder>The Andrew W. Mellon Foundation</funder> <funder>The Social Sciences and Humanities Research Council of Canada</funder>
NoteFunders provide financial support for a project; they are distinct from sponsors, who provide intellectual support and authority.

4.1.78. <fw>

<fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [11.6. ]
Moduletranscr — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.placement (@place)
typeclassifies the material encoded according to some useful typology.
StatusRecommended
Datatype
data.enumerated
Sample values include:
header
a running title at the top of the page
footer
a running title at the bottom of the page
pageNum
(page number) a page number or foliation symbol
lineNum
(line number) a line number, either of prose or poetry
sig
(signature) a signature or gathering symbol
catch
(catchword) a catch-word
Member of
Contained by
May contain
Declaration
element fw { att.global.attributes, att.placement.attributes, attribute type { data.enumerated }?, macro.phraseSeq }
Example
<fw type="sig" place="bottom">C3</fw>
NoteWhere running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The <fw> element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance.

4.1.79. <gap>

<gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.4.3. ]
Modulecore — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.editLike (@evidence, @source, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.responsibility (@cert, @resp))
reasongives the reason for omission. Sample values include sampling, inaudible, irrelevant, cancelled.
StatusOptional
Datatype1–∞ occurrences of 
data.word
separated by whitespace
Valuesany short indication of the reason for the omission.
handin the case of text omitted from the transcription because of deliberate deletion by an identifiable hand, signifies the hand which made the deletion.
StatusOptional
Datatype
data.pointer
Valuesmust point to a hand identifier typically but not necessarily declared in the document header (see section 11.3.2.1.).
agentIn the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.
StatusOptional
Datatype
data.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
Member of
Contained by
May containEmpty element
Declaration
element gap { att.global.attributes, att.editLike.attributes, attribute reason { list { data.word+ } }?, attribute hand { data.pointer }?, attribute agent { data.enumerated }?, ( model.descLike | model.certLike )* }
Example
<gap quantity="4" unit="chars" reason="illegible"/>
Example
<gap quantity="1" unit="essay" reason="sampling"/>
Example
<del>  <gap    atLeast="4"    atMost="8"    unit="chars"    reason="illegible"/> </del>
Example
<gap extent="unknown" unit="lines" reason="lost"/>
NoteThe <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 11.3.3.2. for discussion of which element is appropriate for which circumstance.The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion.

4.1.80. <genName>

<genName> (generational name component) contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. [13.2.1. ]
Modulenamesdates — 4.
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
Member of
Contained by
core: add author bibl