Stories for all time: The Icelandic fornaldarsögur
Encoding guidelines for manuscript catalogue records
edited by M. J. Driscoll
mjd@hum.ku.dk
Copenhagen
2016
Version 1.1

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, largely owing to the project's focus on quantitative codicology. Many aspects of manuscripts which would otherwise be included in an XML description are 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 these guidelines. It is a conformant subset of Release 2.9.1 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://fasnl.ku.dk/fasnl/xml/FASNL_msDesc.rnc.

The overall structure of a TEI-conformant XML document can be summarised as follows:
<TEI xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
<!-- metadata describing the manuscript -->
 </teiHeader>
 <facsimile>
<!-- (optional) metadata describing, and links to, digital images of the manuscript -->
 </facsimile>
 <text>
<!-- (optional) transcription of the manuscript -->
 </text>
</TEI>
Note that although facsimile and text are both optional, one of them must be present.

The present document pertains only to the first of these aspects, manuscript description, in part using material derived from the P5 release of the TEI Guidelines.

1 Manuscript description metadata

Each manuscript must be described within the teiHeader element of a TEI-conformant document, 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="free">
    <licence target="http://creativecommons.org/licenses/by-sa/3.0/">Distributed by
         the University of Copenhagen under a Creative Commons Attribution-ShareAlike
         3.0 Unported License.</licence>
   </availability>
   <authority>Nordisk Forskningsinstitut, Københavns Universitet</authority>
  </publicationStmt>
  <sourceDesc>
   <msDesc xml:id="examplexml:lang="en">
<!-- [full manuscript description ]-->
   </msDesc>
  </sourceDesc>
 </fileDesc>
 <revisionDesc>
  <change when="2016-01-01who="#ABC">
<!-- [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. In the system we employ in the project, the description of a manuscript with the shelfmark AM 11 fol. would have as its id AM02-0011-en while GKS 2450 4to would be GKS04-2450-en.

The value for xml:lang, as elsewhere, must be supplied in the form of a valid language identifier (see below). Note that xml:lang does not indicate the language of the manuscript itself; this information is encoded under textLang, as described below (1.2.2.3 textLang).

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

The first four of these are mandatory; the fifth is optional. msPart should only be used for composite manuscripts, i.e. manuscripts comprising two or more originally distinct manuscript parts now kept together as a unit, and msFrag for scattered manuscripts, i.e. manuscripts one or more parts of which have become separated from the original codex and may now be kept in different repositories.

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.

  • msIdentifier (manuscript identifier) contains the information required to identify the manuscript being described.

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

  • repository contains the name of a repository within which manuscripts are stored, possibly forming part of an institution.
  • idno (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way.
  • altIdentifier (alternative identifier) contains an alternative or former structured identifier used for a manuscript, such as a former catalogue number.

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 (2.3 Repositories). The value of the ref attribute points to a record in the authority file.

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 and retrieve the repository information from the authority file.
<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"/>
 <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.

  • msContents (manuscript contents) describes the intellectual content of a manuscript or manuscript part, either as a series of paragraphs or as a series of structured manuscript items.
This example shows the content model of msContents:
<msContents>
 <titlePage ana="#later"/>
 <msItem class="fasn="1">
<!-- [content of msItem] -->
 </msItem>
 <msItem class="riddn="2">
<!-- [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, you should 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"/>
The text on the title page can be transcribed, using one or more titlePart elements, with type attributes as necessary.
<titlePage ana="#contemporary">
 <titlePart type="main">Historien om Rolf Krage, Konge i Danmark</titlePart>
 <titlePart type="sub">Af det Islandske sprog, udsat paa dansk.</titlePart>
</titlePage>

1.2.2 <msItem>

Each 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 by pointing to other elements or resources defining the classification concerned. Suggested values include: 1] fas; 2] ridd; 3] edd; 4] isl; 5] kvad; 6] kon; 7] islt; 8] rimur; 9] forns; 10] avint; 11] konth; 12] almb; 13] riddst
    defective [att.msExcerpt]indicates 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, which thus functions as an authority file for text types, and is described in another section of this document (2.4 Text classes).

The defective attribute is optional and should only be used 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="fasdefective="truen="1">
 <locus from="1r:1to="8v:17"/>
 <title ref="#snfdsvtype="uniform">Sögubrot af nokkrum fornkonungum í Dana og
   Svía veldi</title>
</msItem>
The ref attribute should be used when the item in question is a fornaldarsaga; see below 1.2.2.2 title.
This example demonstrates the method for nesting msItem elements, which is useful in cases such as this, where a saga comprises several individual þættir. The value of the n attribute on the nested msItem elements indicates the depth of nesting.
<msItem class="riddn="2">
 <locus from="23rto="80r"/>
 <title type="uniform">Mágus saga jarls</title>
 <msItem class="riddn="2.1">
  <title type="uniform">Hrólfs þáttur skuggafífls</title>
 </msItem>
 <msItem class="riddn="2.2">
  <title type="uniform">Vilhjálms þáttur Laissonar</title>
 </msItem>
 <msItem class="riddn="2.3">
  <title type="uniform">Geirarðs þáttur frækna</title>
 </msItem>
</msItem>

1.2.2.1 <locus>

A locus element should 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, typically a page number.
    tospecifies the end-point of the location in a normalized form, typically as a page number.

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.

Although not required to be empty, the content of the locus element should ideally 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="3vto="17r"/>
As mentioned, it is also possible, but generally not necessary, to write out the range of folios as the content of the element:
<locus from="3vto="17r">f. 3v-17r</locus>
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:1to="8v:17"/>

1.2.2.2 <title>

The title element contains the title of the individual manuscript item and is required to appear at least once (multiple titles are possible). This title should be provided in a uniform format, that is, the standardised title by which the work is generally known. The form of the title found in the manuscript itself can also be given using the rubric or finalRubric elements; see below 1.2.2.4 rubric, incipit, explicit and finalRubric.

  • title contains a title for any kind of work.
    typeclassifies the title according to some convenient typology.
    ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.

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 or canonical title by which an individual 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 is a general description of the work in question rather than a standard title. supplied should be used when it is not possible to assign a uniform title, for example if there is no corresponding entry in the reference literature or provided in a manuscript catalogue.
parallel
An alternative title by which the work is also known.
In this example, most catalogues give the title of the item as Þjalar Jóns saga but it is also known as Jóns saga Svipdagssonar.
<title type="uniform">Þjalar Jóns saga</title>
<title type="parallel">Jóns saga Svipdagssonar</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>

As mentioned above, the ref attribute on title must be used when the item in question is a fornaldarsaga. The abbreviations for the various sagas are as follows:

#asb
Áns saga bogsveigis
#ask
Ásmundar saga kappabana
#bsh
Bósa saga og Herrauðs
#eseab
Egils saga einhenda og Ásmundar berserkjabana
#esv
Eiríks saga víðförla
#ff
Frá Fornjóti og hans ættmönnum
#fsf
Friðþjófs saga frækna
#ghs
Göngu-Hrólfs saga
#gsgr
Gautreks saga og Gjafa-Refs
#gsl
Gríms saga loðinkinna
#hs
Heiðreks saga konungs og Hervarar (Hervarar saga)
#hsb
Hálfdanar saga Brönufóstra
#hse
Hálfdanar saga Eysteinssonar
#hsg
Hrólfs saga Gautrekssonar
#hsgr
Hrómundar saga Gripssonar
#hsh
Héðins saga og Högna (Sörla þáttur)
#hsk
Hrólfs saga kraka
#hskh
Hálfs saga konungs og Hálfsrekka
#hso
Hjálmþés saga og Ölvis
#hthth
Helga þáttur Þórissonar
#isg
Illuga saga Gríðarfóstra
#jss
Jóns saga Svipdagssonar (Þjalar-Jóns saga)
#ksh
Ketils saga hængs
#ngth
Norna-Gests þáttur
#oeos
Örvar-Odds saga
#rsl
Ragnars saga loðbrókar
#rth
Ragnarssona þáttur
#snfdsv
Sögubrot af nokkrum fornkonungum í Dana og Svíaveldi
#sss
Sörla saga sterka
#ssst
Sturlaugs saga starfsama
#thsv
Þorsteins saga Víkingssonar
#ththb
Þorsteins þáttur bæjarmagns
#ttht
Tóka þáttur Tókasonar
#upp
Af Upplendinga konungum
#vs
Völsunga saga
#ysv
Yngvars saga víðförla

1.2.2.3 <textLang>

  • textLang (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description.
    mainLang(main language) supplies a code which identifies the chief language used in the bibliographic work.
    otherLangs(other languages) one or more codes identifying any other languages used in the bibliographic work.

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. All those used have been hard-wired into the schema.

In the following example, the manuscript is principally in Icelandic but with some material in Latin and German:
<textLang mainLang="isotherLangs="la de"/>
Note: The standard code for Old Norse-Icelandic is non, which can be found in the expanded list of ISO 639-2 codes. For the purposes of this project, however, it is unnecessary to distinguish between Old and Modern Icelandic, so is should be used for both.

1.2.2.4 <rubric>, <incipit>, <explicit> and <finalRubric>

  • rubric contains the text of any rubric or heading attached to a particular manuscript item, that is, a string of words through which a manuscript signals the beginning of a text division, often with an assertion as to its author and title, which is in some way set off from the text itself, usually in red ink, or by use of different size or type of script, or some other such visual device.
  • incipit contains the incipit of a manuscript item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipits were, in former times, frequently used a means of reference to a work, in place of a title.
  • 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.
  • 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.
  • 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.

All of these elements are optional. rubric is used to encode headings in the text. Usually these are or contain some form of title and are frequently written in a larger, more ornate script than the rest of the text. There may be more than one rubric, in which case multiple rubric elements may be used. incipit and explicit encode the first and last words of a text respectively and are sometimes used to identify a text when no title is given. Usually these are five to ten words long, but this will vary depending on the text; ideally they should form a complete syntactic unit. finalRubric should be used when the last words of the text give its title, as in the example below. colophon is used where the scribe provides information on himself or the place, date or circumstaces under which the text was copied.

<rubric>Sagann af Eireke Rauda</rubric>
<incipit>Olafur heet k<ex>on</ex>ung<ex>ur</ex> er kallaþ<ex>ur</ex> var Oleyfur
hvyte</incipit>
<finalRubric>og end<ex>ar</ex> hier so sauguna af Eireke hinum rauda</finalRubric>
Note that transcriptions from the text should be given in semi-diplomatic form, i.e. preserving the orthography of the original as much as possible, but with expanded abbreviations, where the expansions are clearly marked using, as a minimum, the ex element.
<rubric>Hervarar þättur hin<ex>n</ex> gamle fin<ex>n</ex>st so skrifadur sem hier
epter fÿlger.</rubric>
The unexpanded forms can also be given, using am and ex within choice:
<rubric>Hervarar þättur hin<choice>
  <ex>n</ex>
  <am>̅</am>
 </choice> gamle
fin<choice>
  <ex>n</ex>
  <am>̅</am>
 </choice>st so skrifadur sem hier epter
fÿlger.</rubric>
The elements abbr and expan can also be used, although this results in markup which is unnecessarily heavy.
<rubric>Hervarar þättur
<choice>
  <expan>hin<ex>n</ex>
  </expan>
  <abbr>hin<am>̅</am>
  </abbr>
 </choice>
gamle
<choice>
  <expan>fin<ex>n</ex>st</expan>
  <abbr>fin<ab>̅</ab>st</abbr>
 </choice> so
skrifadur sem hier epter fÿlger.</rubric>

For more information on recommended transcription practice see the project's transcription guidelines.

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, as explained below.

  • 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.
    type [att.typed]characterizes the element in some sense, using any convenient classification scheme or typology.
    target [att.pointing]specifies 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 ana="#apographtarget="#MS_1111"
  type="ms"/>

 <ref ana="#protographtarget="#MS_9999"
  type="ms"/>

</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>This is the shorter version of the saga, comprising only 11 chapters rather
than the usual 14.</note>

1.3 Physical description (<physDesc>)

  • physDesc (physical description) contains a full physical description of a manuscript or manuscript part, optionally subdivided using more specialized elements from the model.physDescPart class.

Under the general heading ‘physical description’ we subsume a large number of elements which are useful for 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-flyleafvalue="2"/>
    <num type="book-blockvalue="367"/>
    <num type="back-flyleafvalue="1"/>
    <dimensions type="leaf">
     <height quantity="200unit="mm"/>
     <width quantity="160unit="mm"/>
    </dimensions>
    <watermark ana="#no"/>
   </support>
   <foliation ana="#later pag"/>
   <condition ana="#good"/>
  </supportDesc>
  <layoutDesc>
   <layout columns="1writtenLines="4 30">
    <num atLeast="6atMost="20type="wpl"/>
    <dimensions type="written">
     <height quantity="130unit="mm"/>
     <width quantity="175unit="mm"/>
    </dimensions>
   </layout>
  </layoutDesc>
 </objectDesc>
 <handDesc hands="3">
  <handNote scope="majorscript="cursiva"/>
  <handNote scope="major"
   scribeRef="BryJon01script="cursiva"/>

  <handNote scope="major"
   scribeRef="ThoSig161script="cursiva"/>

 </handDesc>
 <decoDesc ana="#low">
  <decoNote type="initial">Initials slightly larger, but without colour or
     ornamentation.</decoNote>
 </decoDesc>
 <additions ana="#high">
  <p>Lots of marginalia throughout the manuscript, particularly on leaves originally
     left blank.</p>
 </additions>
 <bindingDesc>
  <binding ana="#plaincontemporary="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.
    forma short project-specific name identifying the physical form of the carrier, for example as a codex, roll, fragment, partial leaf, cutting etc.

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 page (or other surface).

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 material 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-flyleafvalue="4"/>
   <num type="book-blockvalue="206"/>
   <num type="back-flyleafvalue="6"/>
   <dimensions>
    <height quantity="167unit="mm"/>
    <width quantity="132unit="mm"/>
   </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:

front-flyleaf
Flyleaves which come before the main book block.
book-block
The assemblage of leaves making up the main part of the manuscript.
back-flyleaf
Flyleaves which come after 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.
    atLeast [att.ranging]gives a minimum estimated value for the approximate measurement.
    atMost [att.ranging]gives a maximum estimated value for the approximate measurement.
    quantity [att.dimensions]specifies the length in the units specified
    unit [att.dimensions]names 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.
    atLeast [att.ranging]gives a minimum estimated value for the approximate measurement.
    atMost [att.ranging]gives a maximum estimated value for the approximate measurement.
    quantity [att.dimensions]specifies the length in the units specified
    unit [att.dimensions]names 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. For obvious reasons the watermark element will only be present in cases where the support is paper (or mixed).

1.3.1.1.2 <foliation>

The foliation element may be used to indicate the scheme, medium or location of folio, page or column 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
The manuscript is columnated, i.e. numbered by column.
contemporary
Foliation is contemporary with the manuscript.
fol
The manuscript is foliated, i.e. numbered by folio.
later
Foliation occurred some time after the manuscript was produced.
no
Manuscript is not foliated.
pag
The manuscript is paginated, i.e. numbered by page.

Note that in the case of a manuscript which has not been foliated, the single value no can 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 is not foliated:

<foliation ana="#no"/>

Where there is multiple foliation, e.g. original columnation and later foliation, more than one foliation element should be used.

<foliation ana="#contemporary col"/>
<foliation ana="#later fol"/>

As in other cases, more information can be provided within the element:

<foliation ana="#contemporary col">Original columnation.</foliation>
<foliation ana="#later fol">Foliated in red ink in the upper right-hand corner of
the recto side by Kr. Kålund.</foliation>
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 wear.

Here again, it is also possible to provide a prose description of a manuscript's condition using the condition element, but 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-prosecolumns="1"
  writtenLines="24 30">

  <num atLeast="16atMost="20type="wpl"/>
  <dimensions type="written">
   <height quantity="130unit="mm"/>
   <width quantity="175unit="mm"/>
  </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.
unknown
It has not been determined how verses are written.

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

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, as is the case with most manuscripts, the columns attribute is still required.

The writtenLines attribute is also required and is used for encoding the number of written lines per page. 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.

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.
    atLeast [att.ranging]gives a minimum estimated value for the approximate measurement.
    atMost [att.ranging]gives 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 child 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 should measured from the tops of 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, pen or drypoint these 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.
    unit [att.dimensions]names the unit used for the measurement
    quantity [att.dimensions]specifies the length in the units specified
    atLeast [att.ranging]gives a minimum estimated value for the approximate measurement.
    atMost [att.ranging]gives 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.
    unit [att.dimensions]names the unit used for the measurement
    quantity [att.dimensions]specifies the length in the units specified
    atLeast [att.ranging]gives a minimum estimated value for the approximate measurement.
    atMost [att.ranging]gives 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: dimensions can be used twice in the case of a manuscript with two (or more) scribes with major scope and differing page dimensions (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. Sample values include: 1] carolingian; 2] protogothic; 3] textualis; 4] cursiva; 5] hybrida; 6] semihybrida; 7] hum cursiva; 8] fractura; 9] chancery fractura; 10] chancery; 11] kurrent; 12] early kurrent; 13] late kurrent; 14] unknown
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 scope="major"
  scribeRef="#scribe1script="textualis"/>

 <handNote scope="minor"
  scribeRef="#scribe2script="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 should have the three attributes 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 - 2.1 Persons). If the name of a scribe is known but he can nevertheless not be identified with certainty, 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. For the purposes of this project 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 kurrent

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.

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, as in the following example, but this is not required.

<decoDesc ana="#medium">
 <decoNote type="initials">Some initials in red.</decoNote>
 <decoNote type="vignette">A tailpiece.</decoNote>
</decoDesc>

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>Pen trials, scribbles, words and sentences have been added to empty spaces or
   blank pages between items as well as in the margins. Some of these are of
   importance as they contain the names of previous owners, e.g. <q>Marteinn
     Jónsson 12/12 60</q> (<locus from="1rto="1r"/>) and <q>Björn Sigurðsson: Með
     eigin hendi</q> (<locus from="24rto="24r"/>).</p>
 <p>At the end of Hrólfs saga Gautrekssonar <locus from="92vrto="92v"/> written
   in different hand: <q>G G Amen</q>.</p>
 <p>At the end of Nikulás saga leikara (<locus from="131vto="131v"/>) is written:
 <q>Gudrun Bjorns dotter á bókina</q>.</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="#plaincontemporary="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 notAfter="1820notBefore="1800">ca. 1810</origDate>
 <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.
    notBefore [att.datable.w3c]specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
    notAfter [att.datable.w3c]specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
    from [att.datable.w3c]indicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
    to [att.datable.w3c]indicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
    when [att.datable.w3c]supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.

The origDate element is required. 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 but can be approximately determined via other means, such as palaeography and orthography, the notBefore and notAfter attributes are used.

Only one of these three methods should be used for the attributes on origDate. The element need not contain any text or child elements.

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="1815to="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 notAfter="1725notBefore="1701"/>

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, need not contain any text or child elements. The value of the key attribute should be the standard reference code for the country in which the manuscript was produced.

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.
    ref [att.canonical](reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
    role [att.naming]may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, 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.

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

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

The following example demonstrates the method of encoding various owners of a manuscript:
<provenance>
 <name ref="#SigEin005role="owner"
  type="person">
Sigríður Einarsdóttir</name>
 <name ref="#JonSig045role="owner"
  type="person">
Jón Sigurður Sigurðsson</name>
 <name ref="#SigJen001role="owner"
  type="person">
Sigurður Jensson</name>
</provenance>

1.5 Manuscript parts

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

  • msPart (manuscript part) contains information about an originally distinct manuscript or part of a manuscript, which is now part of a composite manuscript.

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

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

Each person, place, repository or text class is assigned a unique identifier using xml:id. These can them be pointed to, using key or ref, from within the manuscript record.

Examples are given below.

2.1 Persons

Persons are defined using the element person.
  • person provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source.
<person role="scribesex="1"
 xml:id="JonErl001">

 <persName xml:lang="is">
  <forename sort="1">Jón</forename>
  <surname sort="2">Erlendsson</surname>
 </persName>
 <birth notAfter="1610notBefore="1600">ca. 1605</birth>
 <death when="1672-08">August 1672</death>
 <residence>
  <placeName>
   <settlement ref="#VilVil01type="farm">Villingaholt</settlement>
  </placeName>
 </residence>
 <occupation xml:lang="en">Priest</occupation>
 <bibl>
  <ref target="#IsAev">Íslenzkar æviskrár</ref>
  <biblScope unit="volume">III</biblScope>
  <biblScope from="195to="196unit="page"/>
 </bibl>
</person>
This is then referenced in the manuscript record like this:
<name ref="#JonErl001type="person">Jón Erlendsson</name>
or
<handNote scope="major"
 scribeRef="#JonErl001script="textualis">
Written, apart from
fol. 12, by Jón Erlendsson from Villingaholt in a clear, seventeenth-century Gothic
book hand.</handNote>

Note that the placeName element within residence contains a pointer to the corresponding place element, shown in the next section.

2.2 Places

Places are defined using the element place.
  • place contains data about a geographic location
<place xml:id="VilVil01">
 <placeName xml:lang="is">
  <settlement type="farm">Villingaholt</settlement>
  <region ref="#Villin01type="parish"/>
  <region ref="#Árnes01type="county"/>
  <region ref="#Sunnle01type="geog"/>
  <country ref="#IS"/>
 </placeName>
 <location>
  <geo>63.883997 -20.750909</geo>
 </location>
</place>

2.3 Repositories

Repositories are defined using the element org (organisation).
  • org (organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people.
<org xml:id="AMDK">
 <orgName xml:lang="en">Arnamagnæan Collection, Copenhagen</orgName>
 <orgName xml:lang="da">Nordisk Forskningsinstitut, Københavns Universitet</orgName>
 <place>
  <settlement key="Copen01"/>
  <country key="DK"/>
 </place>
</org>

2.4 Text classes

In order to establish the compilation patterns of manuscripts containing fornaldarsögur, the class attribute is required on every msItem within a manuscript description.
  • msItem (manuscript item) describes an individual work or item within the intellectual content of a manuscript or manuscript part.
    classidentifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned. Suggested values include: 1] fas; 2] ridd; 3] edd; 4] isl; 5] kvad; 6] kon; 7] islt; 8] rimur; 9] forns; 10] avint; 11] konth; 12] almb; 13] riddst
The possible values of the attribute are defined in a classification declaration in the teiHeader.
  • classDecl (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text.
  • taxonomy defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy.
  • category contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy.
  • 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.
The class declarations are based on the indices to Páll Eggert Ólason's Skrá um handritasöfn Landsbókasafnsins and are the same as those used by handrit.is.
<category xml:id="fas">
 <catDesc>
  <term xml:lang="is">Fornaldarsögur</term>
  <term xml:lang="da">Oldtidssagaer</term>
  <term xml:lang="en">Legendary sagas</term>
 </catDesc>
</category>
The most common classes found in fornaldarsaga manuscripts, in addition to fornaldarsögur, are:
ridd
Riddarasögur (Indigenous chivalric romances)
edd
Eddukvæði (Eddic poetry)
isl
Íslendingasögur (Icelandic family sagas)
kvad
Kveðskapur (Poetry of various kinds, other than Eddic)
kon
Konungasögur (Kings' sagas)
islt
Íslendingaþættir (Short tales of Icelanders)
rimur
Rímur (Metrical romances)
forns
Fornaldarsögur síðari tíma (Post-mediaeval legendary sagas)
avint
Ævintýri (Exempla)
konth
Konungasagnaþættir (Short tales of Norwegian kings)
almb
Almúgabækur (Chapbooks)
riddst
Riddarasögur síðari tíma (Post-mediaeval chivalric romances)

3 Customisation section

In the following section a brief survey of the modifications made vis-à-vis the TEI schema is presented. In general, the idea has been to put as much information into the encoding as possible, avoiding wherever possible the use of natural language. This is done both to make data-input easier for the cataloguers and reduce the risk of error, and also to make the data more easily searchable.

Included in the FASNL schema are the four basic key TEI modules <header>, <core>, <tei> and <textstructure>. Also included are the five specialised modules <namesdates>, <msdescription>, <analysis>, <figures> and <transcr>. A good many unwanted elements have been deleted, however, and several optional attributes have been made compulsory and their range of possible values constrained. Finally, the content model for a small number of elements has been simplified. Formal definitions for all the elements can be found in section 4 below (4 Formal definitions.

On the msDesc (manuscript description) element the attributes xml:id, which provides a unique identifier for the element, and xml:lang, which indicates the language of the element content, have been made madatory.

The sub-elements of msDesc, msIdentifier, msContents, physDesc, history and additional, have all been made mandatory, apart from additional; also optional are msPart, which is only used for composite manuscripts, and msFrag, which is used for scattered manuscripts.

The msContents element must contain at least one msItem element, on which the attributes class and n must be present. Each msItem, in turn, must contain the elements locus, title and textLang, each with their required attributes.

The attributes from and to are required on the locus element.

On the title element the type attribute is required; possible values are uniform | supplied | parallel.

The textLang element has been made empty and requires the mainLang attribute.

The attribute ana (analysis) is used on a number of elements in order to provide basic information on the presence or absence of a feature or its relative level or extent. All are required (if the element is used).

The elements are:

4 Formal definitions

Schema FASNL_msDesc: Elements

<abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.5.5. Abbreviations and Their Expansions]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.source (@source) att.typed (type, @subtype)
typeallows the encoder to classify the abbreviation according to some convenient typology. Sample values include: 1] suspension; 2] contraction; 3] brevigraph; 4] superscription; 5] acronym; 6] title; 7] organization; 8] geographic
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Sample values include:
suspension
the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
contraction
the abbreviation omits some letter(s) in the middle.
brevigraph
the abbreviation comprises a special symbol or mark.
superscription
the abbreviation includes writing above the line.
acronym
the abbreviation comprises the initial letters of the words of a phrase.
title
the abbreviation is for a title of address (Dr, Ms, Mr, …)
organization
the abbreviation is for the name of an organization.
geographic
the abbreviation is for a geographic name.
Note

The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see [ID PETTY in TEI Guidelines]

Member of
Contained by
May contain
Note

The abbr tag is not required; if appropriate, the encoder may transcribe abbreviations in the source text silently, without tagging them. If abbreviations are not transcribed directly but expanded silently, then the TEI header should so indicate.

Example
<choice>
 <expan>North Atlantic Treaty Organization</expan>
 <abbr cert="low">NorATO</abbr>
 <abbr cert="high">NATO</abbr>
 <abbr cert="highxml:lang="fr">OTAN</abbr>
</choice>
Example
<choice>
 <abbr>SPQR</abbr>
 <expan>senatus populusque romanorum</expan>
</choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element abbr
{
   att.global.attributes,
   att.source.attributes,
   att.typed.attribute.subtype,
   attribute type { teidata.enumerated }?,
   macro.phraseSeq
}

<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. Accompanying Material]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype)
Member of
Contained by
msdescription: physDesc
May contain
Example
<accMat>A copy of a tax form from 1947 is included in the envelope
with the letter. It is not catalogued separately.</accMat>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element accMat
{
   att.global.attributes,
   att.typed.attributes,
   macro.specialPara
}

<acquisition>

<acquisition> contains any descriptive or other information concerning the process by which a manuscript or manuscript part entered the holding institution. [10.8. History]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.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))
Contained by
msdescription: history
May contain
Example
<acquisition>Left to the <name type="place">Bodleian</name> by
<name type="person">Richard Rawlinson</name> in 1755.
</acquisition>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element acquisition
{
   att.global.attributes,
   att.datable.attributes,
   macro.specialPara
}

<add>

<add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) (att.written (@hand)) att.placement (@place) att.typed (@type, @subtype)
Member of
Contained by
May contain
Note

In a diplomatic edition attempting to represent an original source, the add element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the corr or supplied element are recommended.

In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of add may be appropriate, dependent on the editorial philosophy of the project.

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.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element add
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.placement.attributes,
   att.typed.attributes,
   macro.paraContent
}

<additional>

<additional> groups additional information, combining bibliographic information about a manuscript, or surrogate copies of it with curatorial or administrative information. [10.9. Additional Information]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: msDesc msFrag msPart
May contain
core: listBibl
msdescription: adminInfo surrogates
Example
<additional>
 <adminInfo>
  <recordHist>
   <p>
<!-- record history here -->
   </p>
  </recordHist>
  <custodialHist>
   <p>
<!-- custodial history here -->
   </p>
  </custodialHist>
 </adminInfo>
 <surrogates>
  <p>
<!-- information about surrogates here -->
  </p>
 </surrogates>
 <listBibl>
  <bibl>
<!-- ... -->
  </bibl>
<!-- full bibliography here -->
 </listBibl>
</additional>
Content model
<content>
 <sequence>
  <elementRef key="adminInfominOccurs="0"/>
  <elementRef key="surrogates"
   minOccurs="0"/>

  <elementRef key="listBiblminOccurs="0"/>
 </sequence>
</content>
Schema Declaration
element additional
{
   att.global.attributes,
   ( adminInfo?, surrogates?, listBibl? )
}

<additions>

<additions> contains a description of any significant additions found within a manuscript, such as marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription — Formal definitions
AttributesAttributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp)
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived fromatt.global.analytic
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
#no
#low
#medium
#high
#unknown
Member of
Contained by
msdescription: physDesc
May contain
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>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element additions
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute ana
   {
      list { ( "#no" | "#low" | "#medium" | "#high" | "#unknown" )+ }
   },
   macro.specialPara
}

<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. Personal Names]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
Member of
Contained by
May contain
Example
<persName>
 <forename>Frederick</forename>
 <addName type="epithet">the Great</addName>
 <roleName>Emperor of Prussia</roleName>
</persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element addName
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

<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. Administrative Information]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: additional
May contain
core: note
header: availability
msdescription: custodialHist recordHist
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>
Content model
<content>
 <sequence>
  <elementRef key="recordHist"
   minOccurs="0"/>

  <elementRef key="availability"
   minOccurs="0"/>

  <elementRef key="custodialHist"
   minOccurs="0"/>

  <classRef key="model.noteLike"
   minOccurs="0"/>

 </sequence>
</content>
Schema Declaration
element adminInfo
{
   att.global.attributes,
   ( recordHist?, availability?, custodialHist?, model.noteLike? )
}

<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. The Participant Description]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) 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
Note

If included, the name of an organization may be tagged using either the name element as above, or the more specific orgName element.

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>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element affiliation
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.naming.attributes,
   macro.phraseSeq
}

<age>

<age> specifies the age of a person. [13.3.2.1. Personal Characteristics]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) 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
Status Optional
Datatype teidata.count
Note

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

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

Example
<age notAfter="1986value="2">under 20 in the early eighties</age>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
element age
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   attribute value { teidata.count }?,
   macro.phraseSeq.limited
}

<altIdentifier>

<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript, such as a former catalogue number. [10.4. The Manuscript Identifier]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype)
Contained by
msdescription: msFrag msIdentifier msPart
May contain
Note

An identifying number of some kind must be supplied if known; if it is not known, this should be stated.

Example
<altIdentifier>
 <settlement>San Marino</settlement>
 <repository>Huntington Library</repository>
 <idno>MS.El.26.C.9</idno>
</altIdentifier>
Content model
<content>
 <sequence>
  <classRef expand="sequenceOptional"
   key="model.placeNamePart"/>

  <elementRef key="institution"
   minOccurs="0"/>

  <elementRef key="repository"
   minOccurs="0"/>

  <elementRef key="collection"
   minOccurs="0"/>

  <elementRef key="idno"/>
  <elementRef key="noteminOccurs="0"/>
 </sequence>
</content>
Schema Declaration
element altIdentifier
{
   att.global.attributes,
   att.typed.attributes,
   (
      placeName?,
      country?,
      region?,
      district?,
      settlement?,
      institution?,
      repository?,
      collection?,
      idno,
      note?
   )
}

<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. Abbreviation and Expansion]
Moduletranscr — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
Member of
Contained by
May contain
Example
do you <abbr>Mr<am>.</am>
</abbr> Jones?
Example
<expan>
 <abbr>Aug<am>g</am>
 </abbr>
 <ex>ustorum duo</ex>
</expan>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.pPart.transcriptional"/>
 </alternate>
</content>
Schema Declaration
element am
{
   att.global.attributes,
   att.typed.attributes,
   att.editLike.attributes,
   ( text | model.gLike | model.pPart.transcriptional )*
}

<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. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
core: bibl
header: titleStmt
msdescription: msItem
May contain
Note

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

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>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element author
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq
}

<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. Publication, Distribution, Licensing, etc.]
Moduleheader — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Example
<authority>John Smith</authority>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
element authority { att.global.attributes, macro.phraseSeq.limited }

<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. Publication, Distribution, Licensing, etc.]
Moduleheader — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declarable (@default)
statussupplies a code identifying the current availability of the text.
Status Optional
Datatype teidata.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
core: bibl
msdescription: adminInfo
May contain
core: p
header: licence
Note

A consistent format should be adopted

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>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">

  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
Schema Declaration
element availability
{
   att.global.attributes,
   att.declarable.attributes,
   attribute status { "free" | "unknown" | "restricted" }?,
   ( model.availabilityPart | model.pLike )+
}

<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. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Note

Contains phrase-level elements, together with any combination of elements from the biblPart class

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 subtype="book_chaptertype="article"
 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>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration
element bibl
{
   att.global.attributes,
   att.declarable.attributes,
   att.typed.attributes,
   att.sortable.attributes,
   att.docStatus.attributes,
   (
      text
    | model.gLikemodel.highlightedmodel.pPart.datamodel.pPart.editmodel.segLikemodel.ptrLikemodel.biblPartmodel.global
   )*
}

<biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.citing (@unit, @from, @to)
Member of
Contained by
core: bibl
May contain
Note

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute should be used without to. For example, if the citation has ‘p. 3ff’ as a page reference.

Example
<biblScope>pp 12–34</biblScope>
<biblScope from="12to="34unit="page"/>
<biblScope unit="volume">II</biblScope>
<biblScope unit="page">12</biblScope>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element biblScope
{
   att.global.attributes,
   att.citing.attributes,
   macro.phraseSeq
}

<binding>

<binding> contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript. [10.7.3.1. Binding Descriptions]
Modulemsdescription — Formal definitions
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, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp)
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived fromatt.global.analytic
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
#none
#plain
#moderate
#decorative
#unknown
contemporaryspecifies whether or not the binding is contemporary with the majority of its contents
Status Optional
Datatype teidata.xTruthValue
Note

The 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

Contained by
msdescription: bindingDesc
May contain
core: p
msdescription: 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>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">

  <classRef key="model.pLike"/>
  <elementRef key="condition"/>
  <elementRef key="decoNote"/>
 </alternate>
</content>
Schema Declaration
element binding
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.datable.attributes,
   attribute ana
   {
      list
      {
         ( "#none" | "#plain" | "#moderate" | "#decorative" | "#unknown" )+
      }
   },
   attribute contemporary { teidata.xTruthValue }?,
   ( model.pLike | condition | decoNote )+
}

<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. Binding Descriptions]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: binding condition decoNote
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>
Content model
<content>
 <alternate>
  <alternate maxOccurs="unbounded"
   minOccurs="1">

   <classRef key="model.pLike"/>
   <elementRef key="decoNote"/>
   <elementRef key="condition"/>
  </alternate>
  <elementRef key="binding"
   maxOccurs="unboundedminOccurs="1"/>

 </alternate>
</content>
Schema Declaration
element bindingDesc
{
   att.global.attributes,
   ( ( model.pLike | decoNote | condition )+ | binding+ )
}

<birth>

<birth> contains information about a person's birth, such as its date and place. [15.2.2. The Participant Description]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) 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
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>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element birth
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.naming.attributes,
   macro.phraseSeq
}

<body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls)
Contained by
textstructure: text
May contain
msdescription: msDesc
textstructure: div
Content model
<content>
 <sequence>
  <classRef key="model.global"
   maxOccurs="unboundedminOccurs="0"/>

  <sequence minOccurs="0">
   <classRef key="model.divTop"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">

    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0">
   <classRef key="model.divGenLike"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">

    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="1">

    <classRef key="model.divLike"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">

     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="unbounded"
    minOccurs="1">

    <classRef key="model.div1Like"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">

     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence>
    <sequence maxOccurs="unbounded"
     minOccurs="1">

     <classRef key="model.common"/>
     <classRef key="model.global"
      maxOccurs="unboundedminOccurs="0"/>

    </sequence>
    <alternate minOccurs="0">
     <sequence maxOccurs="unbounded"
      minOccurs="1">

      <classRef key="model.divLike"/>
      <alternate maxOccurs="unbounded"
       minOccurs="0">

       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="1">

      <classRef key="model.div1Like"/>
      <alternate maxOccurs="unbounded"
       minOccurs="0">

       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">

   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unboundedminOccurs="0"/>

  </sequence>
 </sequence>
</content>
Schema 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* )*
   )
}

<c>

<c> (character) represents a character. [17.1. Linguistic Segment Categories]
Moduleanalysis — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.segLike (@function) (att.datcat (@datcat, @valueDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype)
Member of
Contained by
May containEmpty element
Note

Contains a single character, a <g> element, or a sequence of graphemes to be treated as a single character. The type attribute is used to indicate the function of this segmentation, taking values such as letter, punctuation, or digit etc.

Example
<phr>
 <c>M</c>
 <c>O</c>
 <c>A</c>
 <c>I</c>
 <w>doth</w>
 <w>sway</w>
 <w>my</w>
 <w>life</w>
</phr>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
Schema Declaration
element c
{
   att.global.attributes,
   att.segLike.attributes,
   att.typed.attributes,
   macro.xtext
}

<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. Catchwords, Signatures, Secundo Folio]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Example
<catchwords>Vertical catchwords in the hand of the scribe placed along
the inner bounding line, reading from top to bottom.</catchwords>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element catchwords { att.global.attributes, macro.phraseSeq }

<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. The Classification Declaration]
Moduleheader — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
header: category
May contain
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 degree="hightype="entertain"/>
  <purpose degree="mediumtype="inform"/>
 </textDesc>
</catDesc>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.catDescPart"/>
 </alternate>
</content>
Schema Declaration
element catDesc
{
   att.global.attributes,
   ( text | model.limitedPhrase | model.catDescPart )*
}

<category>

<category> contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Moduleheader — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
May contain
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>
Content model
<content>
 <sequence>
  <alternate>
   <elementRef key="catDesc"
    maxOccurs="unboundedminOccurs="1"/>

   <alternate maxOccurs="unbounded"
    minOccurs="0">

    <classRef key="model.descLike"/>
    <classRef key="model.glossLike"/>
   </alternate>
  </alternate>
  <elementRef key="category"
   maxOccurs="unboundedminOccurs="0"/>

 </sequence>
</content>
Schema Declaration
element category
{
   att.global.attributes,
   ( ( catDesc+ | ( model.descLike | model.glossLike )* ), category* )
}

<cb>

<cb> (column break) marks the beginning of a new column of a text on a multi-column page. [3.10.3. Milestone Elements]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break)
Member of
Contained by
May containEmpty element
Note

On this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this cb element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column breaks relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The cb element is placed at the head of the column to which it refers.

Example

Markup of an early English dictionary printed in two columns:

<pb/>
<cb n="1"/>
<entryFree>
 <form>Well</form>, <sense>a Pit to hold Spring-Water</sense>:
<sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner
   sinks into the Ground, to find out and disappoint the Enemies Mines,
   or to prepare one</sense>.
</entryFree>
<entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or
<sense>lie groveling</sense>.</entryFree>
<!-- remainder of column -->
<cb n="2"/>
<entryFree>
 <form>Wey</form>, <sense>the greatest Measure for dry Things,
   containing five Chaldron</sense>.
</entryFree>
<entryFree>
 <form>Whale</form>, <sense>the greatest of
   Sea-Fishes</sense>.
</entryFree>
Content model
<content>
</content>
Schema Declaration
element cb
{
   att.global.attributes,
   att.typed.attributes,
   att.edition.attributes,
   att.spanning.attributes,
   att.breaking.attributes,
   empty
}

<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.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]
Moduleheader — Formal definitions
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, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype)
targetpoints to one or more elements that belong to this change.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
msdescription: recordHist
May contain
Note

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

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 status="publicwhen="2008-02-02"
  who="#BZ">
Finished chapter 23</change>
 <change status="draftwhen="2008-01-02"
  who="#BZ">
Finished chapter 2</change>
 <change n="P2.2when="1991-12-21"
  who="#LDB">
Added examples to section 3</change>
 <change when="1991-11-11who="#MSM">Deleted chapter 10</change>
</revisionDesc>
Example
<profileDesc>
 <creation>
  <listChange>
   <change xml:id="DRAFT1">First draft in pencil</change>
   <change notBefore="1880-12-09"
    xml:id="DRAFT2">
First revision, mostly
       using green ink</change>
   <change notBefore="1881-02-13"
    xml:id="DRAFT3">
Final corrections as
       supplied to printer.</change>
  </listChange>
 </creation>
</profileDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element change
{
   att.ascribed.attributes,
   att.datable.attributes,
   att.docStatus.attributes,
   att.global.attributes,
   att.typed.attributes,
   attribute target { list { teidata.pointer+ } }?,
   macro.specialPara
}

<choice>

<choice> groups a number of alternative encodings for the same point in a text. [3.4. Simple Editorial Changes]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
May contain
Note

Because the children of a choice element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

Note also that choice elements may self-nest.

Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

Example

An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.

<p>Lastly, That, upon his solemn oath to observe all the above
articles, the said man-mountain shall have a daily allowance of
meat and drink sufficient for the support of <choice>
  <sic>1724</sic>
  <corr>1728</corr>
 </choice> of our subjects,
with free access to our royal person, and other marks of our
<choice>
  <orig>favour</orig>
  <reg>favor</reg>
 </choice>.</p>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <classRef key="model.choicePart"/>
  <elementRef key="choice"/>
 </alternate>
</content>
Schema Declaration
element choice { att.global.attributes, ( model.choicePart | choice )* }

<classDecl>

<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
Moduleheader — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
header: encodingDesc
May contain
header: 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>
Content model
<content>
 <elementRef key="taxonomy"
  maxOccurs="unboundedminOccurs="1"/>

</content>
Schema Declaration
element classDecl { att.global.attributes, taxonomy+ }

<collation>

<collation> contains a description of how the leaves or bifolia are physically arranged. [10.7.1. Object Description]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: supportDesc
May contain
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>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element collation { att.global.attributes, macro.specialPara }

<collection>

<collection> contains the name of a collection of manuscripts, not necessarily located within a single repository. [10.4. The Manuscript Identifier]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype)
Contained by
May containEmpty element
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>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
Schema Declaration
element collection
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   macro.xtext
}

<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. The msItem and msItemStruct Elements]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
msdescription: msItem
May contain
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>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element colophon { att.global.attributes, macro.phraseSeq }

<condition>

<condition> contains a description of the physical condition of the manuscript. [10.7.1.5. Condition]
Modulemsdescription — Formal definitions
AttributesAttributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp)
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived fromatt.global.analytic
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
#poor
#average
#good
#unknown
Contained by
May contain
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>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element condition
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute ana { list { ( "#poor" | "#average" | "#good" | "#unknown" )+ } },
   macro.specialPara
}

<corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.4.1. Apparent Errors]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type, @subtype)
Member of
Contained by
May contain
Example

If all that is desired is to call attention to the fact that the copy text has been corrected, corr may be used alone:

I don't know,
Juan. It's so far in the past now — how <corr>can we</corr> prove
or disprove anyone's theories?
Example

It is also possible, using the choice and sic elements, to provide an uncorrected reading:

I don't know, Juan. It's so far in the past now —
how <choice>
 <sic>we can</sic>
 <corr>can we</corr>
</choice> prove or
disprove anyone's theories?
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element corr
{
   att.global.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   macro.paraContent
}

<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. Place Names]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) 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
Note

The recommended source for codes to represent coded country names is ISO 3166.

Example
<country key="DK">Denmark</country>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element country
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   macro.phraseSeq
}

<custEvent>

<custEvent> (custodial event) describes a single event during the custodial history of a manuscript. [10.9.1.2. Availability and Custodial History]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.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.typed (@type, @subtype)
Contained by
msdescription: custodialHist
May contain
Example
<custEvent type="photography">Photographed by David Cooper on <date>12 Dec 1964</date>
</custEvent>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element custEvent
{
   att.global.attributes,
   att.datable.attributes,
   att.typed.attributes,
   macro.specialPara
}

<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. Availability and Custodial History]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: adminInfo
May contain
core: p
msdescription: custEvent
Example
<custodialHist>
 <custEvent notAfter="1963-02"
  notBefore="1961-03type="conservation">
Conserved between March 1961 and February 1963 at
   Birgitte Dalls Konserveringsværksted.</custEvent>
 <custEvent notAfter="1988-05-30"
  notBefore="1988-05-01type="photography">
Photographed in
   May 1988 by AMI/FA.</custEvent>
 <custEvent notAfter="1989-11-13"
  notBefore="1989-11-13type="transfer-dispatch">
Dispatched to Iceland
   13 November 1989.</custEvent>
</custodialHist>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

  <elementRef key="custEvent"
   maxOccurs="unboundedminOccurs="1"/>

 </alternate>
</content>
Schema Declaration
element custodialHist { att.global.attributes, ( model.pLike+ | custEvent+ ) }

<damage>

<damage> contains an area of damage to the text witness. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.damaged (@agent, @degree, @group) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.written (@hand))
Member of
Contained by
May contain
Note

Since 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. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

Example
<l>The Moving Finger wri<damage agent="watergroup="1">es; and</damage> having writ,</l>
<l>Moves <damage agent="watergroup="1">
  <supplied>on: nor all your</supplied>
 </damage> Piety nor Wit</l>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element damage
{
   att.global.attributes,
   att.typed.attributes,
   att.damaged.attributes,
   macro.paraContent
}

<date>

<date> contains a date in any format. [3.5.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.3.6. Dates and Times]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.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.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type, @subtype)
Member of
Contained by
May contain
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>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration
element date
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   ( text | model.gLike | model.phrase | model.global )*
}

<death>

<death> contains information about a person's death, such as its date and place. [15.2.2. The Participant Description]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) 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
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>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element death
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.naming.attributes,
   macro.phraseSeq
}

<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. Bindings, Seals, and Additional Material]
Modulemsdescription — Formal definitions
AttributesAttributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp)
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived fromatt.global.analytic
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
#no
#low
#medium
#high
#unknown
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: decoNote summary
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>
Content model
<content>
 <alternate maxOccurs="1minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

  <sequence maxOccurs="1minOccurs="1">
   <elementRef key="summaryminOccurs="0"/>
   <elementRef key="decoNote"
    maxOccurs="unboundedminOccurs="1"/>

  </sequence>
 </alternate>
</content>
Schema Declaration
element decoDesc
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute ana
   {
      list { ( "#no" | "#low" | "#medium" | "#high" | "#unknown" )+ }
   },
   ( model.pLike+ | ( summary?, decoNote+ ) )
}

<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. Bindings, Seals, and Additional Material]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (type, @subtype)
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
Status Optional
Datatype teidata.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
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>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema 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
}

<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, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) (att.written (@hand)) att.typed (@type, @subtype)
Member of
Contained by
May contain
Note

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.

Degrees 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. Certainty, Precision, and Responsibility).

There is a clear distinction in the TEI between del and surplus on the one hand and gap or unclear on the other. del indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. surplus indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. gap or unclear, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription.

Example
<l>
 <del rend="overtyped">Mein</del> Frisch <del rend="overstriketype="primary">schwebt</del>
weht der Wind
</l>
Example
<del rend="overstrike">
 <gap quantity="5reason="illegible"
  unit="character"/>

</del>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element del
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.typed.attributes,
   macro.paraContent
}

<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. Dimensions]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May containEmpty element
Note

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

Example
<depth quantity="4unit="in"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
Schema Declaration
element depth { att.global.attributes, att.dimensions.attributes, macro.xtext }

<dim>

<dim> contains any single measurement forming part of a dimensional specification of some sort. [10.3.4. Dimensions]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May containEmpty element
Note

The specific elements width, height, and depth should be used in preference to this generic element wherever appropriate.

Example
<dim extent="4.67 intype="circumference"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
Schema Declaration
element dim
{
   att.global.attributes,
   att.typed.attributes,
   att.dimensions.attributes,
   macro.xtext
}

<dimensions>

<dimensions> contains a dimensional specification. [10.3.4. Dimensions]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
typeindicates which aspect of the object is being measured.
Status Required
Datatype teidata.enumerated
Legal values are:
leaf
binding
slip
written
boxed
Member of
Contained by
May contain
msdescription: depth dim height width
Note

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

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

This 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="reliefunit="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.

Example

When 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 quantity="90scope="most"
  unit="cm"/>

 <width quantity="48scope="mostunit="cm"/>
</dimensions>
<dimensions unit="in">
 <height quantity="12"/>
 <width quantity="10"/>
</dimensions>
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>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <elementRef key="dim"/>
  <classRef key="model.dimLike"/>
 </alternate>
</content>
Schema Declaration
element dimensions
{
   att.global.attributes,
   att.dimensions.attributes,
   attribute type { "leaf" | "binding" | "slip" | "written" | "boxed" },
   ( dim | model.dimLike )*
}

<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. Place Names]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) 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
Example
<placeName>
 <district type="ward">Jericho</district>
 <settlement>Oxford</settlement>
</placeName>
Example
<placeName>
 <district type="area">South Side</district>
 <settlement>Chicago</settlement>
</placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element district
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   macro.phraseSeq
}

<div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.divLike (@org, @sample) (att.fragmentable (@part)) att.typed (@type, @subtype) att.declaring (@decls) att.written (@hand)
Member of
Contained by
textstructure: body div
May contain
msdescription: msDesc
textstructure: div
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="1type="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.1type="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.2type="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>
Schematron

<s:report test="ancestor::tei:l"> Abstract model violation: Lines may not contain higher-level structural elements such as div.
</s:report>
Schematron

<s:report test="ancestor::tei:p or ancestor::tei:ab and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div.
</s:report>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">

   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence maxOccurs="unbounded"
     minOccurs="1">

     <alternate>
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      maxOccurs="unboundedminOccurs="0"/>

    </sequence>
    <sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="1">

      <classRef key="model.common"/>
      <classRef key="model.global"
       maxOccurs="unboundedminOccurs="0"/>

     </sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="0">

      <alternate>
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       maxOccurs="unboundedminOccurs="0"/>

     </sequence>
    </sequence>
   </alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="0">

    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     maxOccurs="unboundedminOccurs="0"/>

   </sequence>
  </sequence>
 </sequence>
</content>
Schema Declaration
element div
{
   att.global.attributes,
   att.divLike.attributes,
   att.typed.attributes,
   att.declaring.attributes,
   att.written.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* )*
      )?
   )
}

<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. Titles, Authors, and Editors]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
core: bibl
header: titleStmt
msdescription: msItem
May contain
Note

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

Example
<editor>Eric Johnson</editor>
<editor role="illustrator">John Tenniel</editor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element editor
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq
}

<education>

<education> contains a description of the educational experience of a person. [15.2.2. The Participant Description]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) 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
Example
<education>Left school at age 16</education>
Example
<education from="1986-01-01"
 to="1990-06-30">
Attended <name>Cherwell School</name>
</education>
Example
<education notAfter="1690-06"
 notBefore="1685-07">
Anthony Hammond
smuggled her into the University of Cambridge, where she was
disguised as his male cousin, Jack. She remained there for some
months learning grammar, logic, rhetoric, and ethics</education>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element education
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.naming.attributes,
   macro.phraseSeq
}

<encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
header: teiHeader
May contain
core: p
header: classDecl
Example
<encodingDesc>
 <p>Basic encoding, capturing lexical information only. All
   hyphenation, punctuation, and variant spellings normalized. No
   formatting or layout information preserved.</p>
</encodingDesc>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">

  <classRef key="model.encodingDescPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
Schema Declaration
element encodingDesc
{
   att.global.attributes,
   ( model.encodingDescPart | model.pLike )+
}

<event>

<event> contains data relating to any kind of significant event associated with a person, place, or organization. [13.3.1. Basic Principles]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.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.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) 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
Status Optional
Datatype teidata.pointer
Member of
Contained by
May contain
msdescription: msDesc
namesdates: event
Example
<person>
 <event type="matwhen="1972-10-12">
  <label>matriculation</label>
 </event>
 <event type="gradwhen="1975-06-23">
  <label>graduation</label>
 </event>
</person>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   maxOccurs="unboundedminOccurs="0"/>

  <alternate>
   <classRef key="model.pLike"
    maxOccurs="unboundedminOccurs="1"/>

   <classRef key="model.labelLike"
    maxOccurs="unboundedminOccurs="1"/>

  </alternate>
  <alternate maxOccurs="unbounded"
   minOccurs="0">

   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
  </alternate>
  <elementRef key="event"
   maxOccurs="unboundedminOccurs="0"/>

 </sequence>
</content>
Schema Declaration
element event
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   att.naming.attributes,
   att.sortable.attributes,
   attribute where { teidata.pointer }?,
   (
      model.headLike*,
      ( model.pLike+ | model.labelLike+ ),
      ( model.noteLike | model.biblLike | linkGrp | link )*,
      event*
   )
}

<ex>

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

<expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.5.5. Abbreviations and Their Expansions]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
Member of
Contained by
May contain
Note

The content of this element should usually be a complete word or phrase. The ex element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.

Example
The address is Southmoor <choice>
 <expan>Road</expan>
 <abbr>Rd</abbr>
</choice>
Example
<expan xml:lang="la">
 <abbr>Imp</abbr>
 <ex>erator</ex>
</expan>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element expan
{
   att.global.attributes,
   att.editLike.attributes,
   macro.phraseSeq
}

<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. The msItem and msItemStruct Elements]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.msExcerpt (@defective)
Member of
Contained by
msdescription: msItem
May contain
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>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element explicit
{
   att.global.attributes,
   att.typed.attributes,
   att.msExcerpt.attributes,
   macro.phraseSeq
}

<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. Type and Extent of File 2.2. The File Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]
Moduleheader — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Member of
Contained by
core: bibl
header: fileDesc
msdescription: supportDesc
May contain
Example
<extent>3200 sentences</extent>
<extent>between 10 and 20 Mb</extent>
<extent>ten 3.5 inch high density diskettes</extent>
Example

The <measure> element may be used to supplied normalised or machine tractable versions of the size or sizes concerned.

<extent>
 <measure quantity="4.2unit="MiB">About four megabytes</measure>
 <measure quantity="245unit="pages">245 pages of source
   material</measure>
</extent>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element extent { att.global.attributes, macro.phraseSeq }

<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. Digital Facsimiles]
Moduletranscr — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls)
Member of
Contained by
textstructure: TEI
May contain
figures: formula
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 lrx="200lry="300ulx="0uly="0">
  <graphic url="Bovelles-49r.png"/>
 </surface>
</facsimile>
Content model
<content>
 <sequence>
  <elementRef key="frontminOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">

   <classRef key="model.graphicLike"/>
   <elementRef key="surface"/>
   <elementRef key="surfaceGrp"/>
  </alternate>
  <elementRef key="backminOccurs="0"/>
 </sequence>
</content>
Schema Declaration
element facsimile
{
   att.global.attributes,
   att.declaring.attributes,
   ( front?, ( model.graphicLike | surface | surfaceGrp )+, back? )
}

<faith>

<faith> specifies the faith, religion, or belief set of a person. [13.3.2.1. Personal Characteristics]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) 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
Example
<faith>protestant</faith>
Example
<faith ref="http://dbpedia.org/page/Manichaeism">Manichaeism</faith>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element faith
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   att.canonical.attributes,
   macro.phraseSeq
}

<fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
header: teiHeader
May contain
Note

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

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>
Content model
<content>
 <sequence>
  <sequence>
   <elementRef key="titleStmt"/>
   <elementRef key="editionStmt"
    minOccurs="0"/>

   <elementRef key="extentminOccurs="0"/>
   <elementRef key="publicationStmt"/>
   <elementRef key="seriesStmt"
    minOccurs="0"/>

   <elementRef key="notesStmt"
    minOccurs="0"/>

  </sequence>
  <elementRef key="sourceDesc"
   maxOccurs="unboundedminOccurs="1"/>

 </sequence>
</content>
Schema Declaration
element fileDesc
{
   att.global.attributes,
   (
      (
         titleStmt,
         editionStmt?,
         extent?,
         publicationStmt,
         seriesStmt?,
         notesStmt?
      ),
      sourceDesc+
   )
}

<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. The msItem and msItemStruct Elements]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype)
Member of
Contained by
msdescription: msItem
May contain
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>
<!--http://www2.nkfust.edu.tw/~jochi/ed1.htm-->
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element filiation
{
   att.global.attributes,
   att.typed.attributes,
   macro.specialPara
}

<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. The msItem and msItemStruct Elements]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype)
Member of
Contained by
msdescription: msItem
May contain
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>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element finalRubric
{
   att.global.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

<floruit>

<floruit> contains information about a person's period of activity. [13.3.2.1. Personal Characteristics]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.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.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
Member of
Contained by
namesdates: person personGrp
May contain
Example
<floruit notAfter="1100notBefore="1066"/>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element floruit
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   macro.phraseSeq
}

<foliation>

<foliation> describes the numbering system or systems used to count the leaves or pages in a codex. [10.7.1.4. Foliation]
Modulemsdescription — Formal definitions
AttributesAttributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rend, @style, @rendition) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp)
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived fromatt.global.analytic
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
#no
#contemporary
#later
#pag
#col
#fol
#unknown
Contained by
msdescription: supportDesc
May contain
Example
<foliation>Contemporary foliation in red
roman numerals in the centre
of the outer margin.</foliation>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element foliation
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute ana
   {
      list
      {
         (
            "#no"
          | "#contemporary"
          | "#later"
          | "#pag"
          | "#col"
          | "#fol"
          | "#unknown"
         )+
      }
   },
   macro.specialPara
}

<forename>

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

<formula>

<formula> contains a mathematical or other formula. [14.2. Formulæ and Mathematical Expressions]
Modulefigures — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.notated (@notation)
Member of
Contained by
May contain
core: hi
figures: formula
Example
<formula notation="tex">$E=mc^2$</formula>
Example
<formula notation="none">E=mc<hi rend="sup">2</hi>
</formula>
Example
<formula notation="mathml">
 <m:math>
  <m:mi>E</m:mi>
  <m:mo>=</m:mo>
  <m:mi>m</m:mi>
  <m:msup>
   <m:mrow>
    <m:mi>c</m:mi>
   </m:mrow>
   <m:mrow>
    <m:mn>2</m:mn>
   </m:mrow>
  </m:msup>
 </m:math>
</formula>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.hiLike"/>
 </alternate>
</content>
Schema Declaration
element formula
{
   att.global.attributes,
   att.notated.attributes,
   ( text | model.graphicLike | model.hiLike )*
}

<fw>

<fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [11.6. Headers, Footers, and Similar Matter]
Moduletranscr — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.placement (@place) att.written (@hand)
typeclassifies the material encoded according to some useful typology. Sample values include: 1] header; 2] footer; 3] pageNum(page number) ; 4] lineNum(line number) ; 5] sig(signature) ; 6] catch(catchword)
Status Recommended
Datatype teidata.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
Note

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

Example
<fw place="bottomtype="sig">C3</fw>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element fw
{
   att.global.attributes,
   att.placement.attributes,
   att.written.attributes,
   attribute type { teidata.enumerated }?,
   macro.phraseSeq
}

<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. Additions, Deletions, and Omissions]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.timed (@start, @end) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
reasongives the reason for omission. Sample values include sampling, inaudible, irrelevant, cancelled.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
handin the case of text omitted from the transcription because of deliberate deletion by an identifiable hand, indicates the hand which made the deletion.
Deprecatedwill be removed on 2017-08-01
Status Optional
Datatype teidata.pointer
agentin the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified. Sample values include: 1] rubbing; 2] mildew; 3] smoke
Status Optional
Datatype teidata.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
Note

The 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. Use of the gap, del, damage, unclear, and supplied Elements in Combination 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.

Example
<gap quantity="4reason="illegible"
 unit="chars"/>
Example
<gap quantity="1reason="sampling"
 unit="essay"/>
Example
<del>
 <gap atLeast="4atMost="8"
  reason="illegibleunit="chars"/>

</del>
Example
<gap extent="unknownreason="lost"
 unit="lines"/>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
Schema Declaration
element gap
{
   att.global.attributes,
   att.timed.attributes,
   att.editLike.attributes,
   attribute reason { list { teidata.word+ } }?,
   attribute hand { teidata.pointer }?,
   attribute agent { teidata.enumerated }?,
   ( model.descLike | model.certLike )*
}

<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. Personal Names]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
Member of
Contained by
May contain
Example
<persName>
 <forename>Charles</forename>
 <genName>II</genName>
</persName>
Example
<persName>
 <surname>Pitt</surname>
 <genName>the Younger</genName>
</persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element genName
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

<geo>

<geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [13.3.4.1. Varieties of Location]
Modulenamesdates — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls)
Member of
Contained by
May containCharacter data only
Note

Uses of geo can be associated with a coordinate system, defined by a <geoDecl> element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each geo element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System.

Example
<geoDecl datum="WGS84xml:id="WGS">World Geodetic System</geoDecl>
<geoDecl datum="OSGB36xml:id="OS">Ordnance Survey</geoDecl>
<!-- ... -->
<location>
 <desc>A tombstone plus six lines of
   Anglo-Saxon text, built into the west tower (on the south side
   of the archway, at 8 ft. above the ground) of the
   Church of St. Mary-le-Wigford in Lincoln.</desc>
 <geo decls="#WGS">53.226658 -0.541254</geo>
 <geo decls="#OS">SK 97481 70947</geo>
</location>
Example
<geo>41.687142 -74.870109</geo>
Content model
<content>
 <textNode/>
</content>
Schema Declaration
element geo { att.global.attributes, att.declaring.attributes, text }

<handDesc>

<handDesc> (description of hands) contains a description of all the different kinds of writing used in a manuscript. [10.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
handsspecifies the number of distinct hands identified within the manuscript
Status Optional
Datatype teidata.count
Member of
Contained by
msdescription: physDesc
May contain
core: p
header: handNote
msdescription: summary
Example
<handDesc>
 <handNote scope="major">Written throughout in <term>angelicana formata</term>.</handNote>
</handDesc>
Example
<handDesc hands="2">
 <p>The manuscript is written in two contemporary hands, otherwise
   unknown, but clearly those of practised scribes. Hand I writes
   ff. 1r-22v and hand II ff. 23 and 24. Some scholars, notably
   Verner Dahlerup and Hreinn Benediktsson, have argued for a third hand
   on f. 24, but the evidence for this is insubstantial.</p>
</handDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

  <sequence>
   <elementRef key="summaryminOccurs="0"/>
   <elementRef key="handNote"
    maxOccurs="unboundedminOccurs="1"/>

  </sequence>
 </alternate>
</content>
Schema Declaration
element handDesc
{
   att.global.attributes,
   attribute hands { teidata.count }?,
   ( model.pLike+ | ( summary?, handNote+ ) )
}

<handNote>

<handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [10.7.2. Writing, Decoration, and Other Notations]
Moduleheader — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.handFeatures (script, @scribe, @scribeRef, @scriptRef, @medium, @scope)
scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc. Sample values include: 1] carolingian; 2] protogothic; 3] textualis; 4] cursiva; 5] hybrida; 6] semihybrida; 7] hum cursiva; 8] fractura; 9] chancery fractura; 10] chancery; 11] kurrent; 12] early kurrent; 13] late kurrent; 14] unknown
Derived fromatt.handFeatures
Status Required
Datatype 1–∞ occurrences of teidata.name separated by whitespace
Sample values include:
carolingian
protogothic
textualis
cursiva
hybrida
semihybrida
hum cursiva
fractura
chancery fractura
chancery
kurrent
early kurrent
late kurrent
unknown
Contained by
msdescription: handDesc
May contain
Example
<handNote scope="sole">
 <p>Written in insular
   phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed
   minuscule.</p>
</handNote>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element handNote
{
   att.global.attributes,
   att.handFeatures.attribute.scribe,
   att.handFeatures.attribute.scribeRef,
   att.handFeatures.attribute.scriptRef,
   att.handFeatures.attribute.medium,
   att.handFeatures.attribute.scope,
   attribute script { list { teidata.name+ } },
   macro.specialPara
}

<handShift>

<handShift> marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [11.3.2.1. Document Hands]
Moduletranscr — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope) att.source (@source)
newindicates a handNote element describing the hand concerned.
Status Recommended
Datatype teidata.pointer
Note

This attribute serves the same function as the hand attribute provided for those elements which are members of the att.transcriptional class. It may be renamed at a subsequent major release.

Member of
Contained by
May containEmpty element
Note

The handShift element may be used either to denote a shift in the document hand (as from one scribe to another, on one writing style to another). Or, it may indicate a shift within a document hand, as a change of writing style, character or ink. Like other milestone elements, it should appear at the point of transition from some other state to the state which it describes.

Example
<l>When wolde the cat dwelle in his ynne</l>
<handShift medium="greenish-ink"/>
<l>And if the cattes skynne be slyk <handShift medium="black-ink"/> and gaye</l>
Content model
<content>
</content>
Schema Declaration
element handShift
{
   att.global.attributes,
   att.handFeatures.attributes,
   att.source.attributes,
   attribute new { teidata.pointer }?,
   empty
}

<height>

<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. [10.3.4. Dimensions]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May containEmpty element
Note

If used to specify the height of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis perpendicular to the surface of the earth.

Example
<height quantity="7unit="in"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
Schema Declaration
element height
{
   att.global.attributes,
   att.dimensions.attributes,
   macro.xtext
}

<hi>

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.written (@hand)
Member of
Contained by
May contain
Example
<hi rend="gothic">And this Indenture further witnesseth</hi>
that the said <hi rend="italic">Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element hi { att.global.attributes, att.written.attributes, macro.paraContent }

<history>

<history> groups elements describing the full history of a manuscript or manuscript part. [10.8. History]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
Contained by
msdescription: msDesc msFrag msPart
May contain
core: p
Example
<history>
 <origin>
  <p>Written in Durham during the mid twelfth
     century.</p>
 </origin>
 <provenance>
  <p>Recorded in two medieval
     catalogues of the books belonging to Durham Priory, made in 1391 and
     1405.</p>
 </provenance>
 <provenance>
  <p>Given to W. Olleyf by William Ebchester, Prior (1446-56)
     and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)
     according to inscriptions on ff. 4v and 5.</p>
 </provenance>
 <acquisition>
  <p>Presented to Trinity College in 1738 by
     Thomas Gale and his son Roger.</p>
 </acquisition>
</history>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

  <sequence>
   <elementRef key="summaryminOccurs="0"/>
   <elementRef key="originminOccurs="0"/>
   <elementRef key="provenance"
    maxOccurs="unboundedminOccurs="0"/>

   <elementRef key="acquisition"
    minOccurs="0"/>

  </sequence>
 </alternate>
</content>
Schema Declaration
element history
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, origin?, provenance*, acquisition? ) )
}

<idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Moduleheader — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey)
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
Status Optional
Datatype teidata.enumerated
Member of
Contained by
May contain
header: idno
Note

idno should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on idno are ISBN, ISSN, DOI, and URI.

Example
<idno type="ISBN">978-1-906964-22-1</idno>
<idno type="ISSN">0143-3385</idno>
<idno type="DOI">10.1000/123</idno>
<idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
<idno type="URI">http://authority.nzetc.org/463/</idno>
<idno type="LT">Thomason Tract E.537(17)</idno>
<idno type="Wing">C695</idno>
<idno type="oldCat">
 <g ref="#sym"/>345
</idno>

In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.

Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>
Schema Declaration
element idno
{
   att.global.attributes,
   att.sortable.attributes,
   attribute type { teidata.enumerated }?,
   ( text | model.gLike | idno )*
}

<incipit>

<incipit> contains the incipit of a manuscript item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipits were, in former times, frequently used a means of reference to a work, in place of a title. [10.6.1. The msItem and msItemStruct Elements]
Modulemsdescription — Formal definitions
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.msExcerpt (@defective)
Member of
Contained by
msdescription: msItem
May contain