TEI P5 Customization and Encoding Guidelines for Manuscript Description

These guidelines represent a community effort to develop uniform good practice in the cataloguing manuscripts using TEI. They are currently used by cataloguers at a number of institutions including the British Library, the Bodleian Libraries, Cambridge University Library, the John Rylands Library, and the Wellcome Trust. They remain under development and contributions are welcome via pull requests or issues submitted to the GitHub repository.

1 Encoding guidelines

1.1 Introduction

TEI P5 ODD Customization for Manuscripts in Oxford Libaries and the Fihrist and Senmai union catalogues

1.2 Acknowledgements

These draft guidelines are currently based on two main sources - the encoding guidelines for the Fihrist project [pdf], and encoding guidelines for medieval manuscripts jointly created by Cambridge University Library (James Freeman, with Suzanne Paul) and the Bodleian Library (Matthew Holford) with contributions by Andrew Dunning (formerly British Library). The medieval guidelines in turn draw in places on the guidelines created by Patrick Granholm and Eva Nyström for manuscripta.se.

1.3 General principles

1.3.1 Foreign Phrases and Words

Phrases or words in other languages than English may be tagged by adding the xml:lang attribute to the element enclosing the text, or where no other element is available with a foreign element and a xml:lang attribute. By default this text displays in italic when rendered in the online catalogue.

1.3.2 References to Locations within a Manuscript

References to a specific location or range within a manuscripts should be given in a locus element. The from and to attributes are optional but recommended, as they enable links to images to be generated and allow calculation of the length of manuscript items.

If from and to attributes are used to refer to a specific folio or page they should be used with identical values. The foliation scheme should be specified in the scheme attribute with the value folios or pages (the default is assumed to be folios. Lines and/or columns may be specified, e.g. fol. 1r, col. a, line 10 to fol. 2v, column b, line 5.

If reference to columns of text is necessary, use lower-case letters: a, b, c, etc. The lettering should begin with the first column on the left, and move across to the right. The sequence should begin afresh on each page (i.e. the letters do not run concurrently from recto to verso, or across an opening).

To identify columns / lines in the from or to attributes, use (for example):
<locus from="1ra10to="2vb5">(fols. 1ra, line 10 - 2vb, line
5)</locus>
Text in margins:
<locus from="1rto="10r">(fols. 1r-10r, margins)</locus>
For texts scattered over more than one location in the manuscript the locusGrp element should be used.
<locusGrp>
 <locus from="356rbto="356vb">Fols 356<hi rend="superscript">rb-vb</hi>,</locus>
 <locus from="374rato="374rb">374<hi rend="superscript">rab</hi>
 </locus>
</locusGrp>

1.3.3 Personal Names

Persons, if not in an author or editor element, should be tagged using the persName element. For indexing to function correctly this MUST be linked to the persons authority file using the key attribute. The role of the person referred to should be indicated using the role attribute. Values should correspond to the Library of Congress relator term list (http://www.loc.gov/marc//relators/relaterm.html). The most commonly occurring roles are: "aut" (author), "bnd" (binder), "scr" (scribe), "art" (artist; NB this is preferred to illustrator), "fmo" (former owner),"sgn" (signer), "pat" (patron). If necessary, multiple roles can be separated with whitespace.
Common-place book of
<persName key="person_697role="scr fmo">John
Curteys</persName> of Winchester College and New College, Oxford
To record alternative names for a person in such contexts, use nested persName elements, for example:
<persName key="person_f6124role="scr">
 <persName xml:lang="fa-Latn-x-lc">ʿAbd al-Raḥmān</persName>
(<persName xml:lang="fa">عبد الرحمان</persName>)

</persName>

Use "fmo" where there is evidence that a person owned an item. Use "sgn" where the person is only associated with the item by a signature or an inscription which does not necessarily imply ownership. "dnr" (donor) may be used where the person gave the manuscript to an institution but evidence of ownership before the gift is lacking; i.e. to describe manuscripts apparently bought or made with the intention of being directly presented, or manuscripts may have been purchased with money given by a donor rather than directly presented.

1.3.4 Corporate / Organization Names

Corporate entities should be tagged using the orgName element. For indexing to function correctly this MUST be linked to the persons authority file using the key attribute. The role of the organization referred to should be indicated using the role attribute. Values should correspond to the Library of Congress relator term list (http://www.loc.gov/marc//relators/relaterm.html). Separate multiple roles with whitespace.
<orgName key="org_148998848role="fmo">Würzburg, Domstift St Kilian</orgName>,
12th-century ex libris, fol. 1r, and 15th-century shelfmark, fol.
2r.

1.3.5 Placenames

In sections relating to manuscript contents, physical description and provenance, placenames should be tagged using the placeName. For indexing to function correctly this MUST be linked to the places authority file using the key attribute.
<placeName key="place_1234">Bologna</placeName>
  • placeName (place name) contains an absolute or relative place name.
    key [att.canonical]provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.

In the origPlace element, placenames should be tagged using (as appropriate) country, region and settlement. Again, for indexing to function correctly these MUST be linked to the places authority file using the key attribute. See under origPlace.

To accommodate geodata in legacy data, or for use by other systems, geo elements are permitted. But they are not displayed in catalogue web sites. For example, from the International Dunhuang Project:

<origPlace>DHMG.(Dunhuang Mogao) DHMG.17. <geo n="min">94.80388888888889198 40.03638888888888658</geo>
 <geo n="max">95.9375 40.04833333333333201</geo>
</origPlace>

In other cataloguing projects geodata should be given in the places authority file.

1.3.7 Formatting

In general, where possible, formatting should be carried out using semantic markup rather than using the hi element.

However, where use of the hi element is unavoidable, it should be used with the following values on rend:

  • superscript
  • subscript
  • underline

Multiple values may be separated by whitespace.

If correct formatting is not possible using these values, raise an issue on GitHub to add further values.

1.3.8 Attribute values

Attribute values forming more than one word in natural language should be given in camelCase.

1.3.9 Transcription

Transcriptions from the manuscript in the rubric, incipit, explicit, etc. elements, or in the provenance section, should be made diplomatically. Expand standard abbreviations silently. If the abbreviation can be expanded with some but not complete confidence, enclose the expansion in the ex element. Denote uncertain or ambiguous abbreviations with the character ’ [U0146], e.g. Westm’

Use capital letters only when they appear in the manuscript.

Transcription of special characters: e-caudata should be transcribed using U+0119: Latin Small Letter E With Ogonek

The relevant elements from the TEI transcription module should be used (see especially 11.3.3.2, http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PHCOMB)

For retroconversion, reproduce the text as given in the printed catalogue. Where abbreviation is indicated typographically, e.g. with italic font or between parentheses, indicate this using the ex element. Typographic indications of insertion, deletion, omission, supplied text, etc., using symbols such as [], \/, should be replaced with the relevant elements from the TEI transcription module.

Manuscript punctuation may be simplified by replacing the punctus versus and punctus elevatus with a point (.).

Indicate damage using the damage element.

Errors in the manuscript may be indicated using the sic and corr and choice elements. sic by itself simply signals the presence of an error, corr provides the correction.

<!-- MS. Add. C. 145 --> Explicit <sic>loica</sic> magistri pauli de
Venetijs

<!-- MS. Add. C. 145 --> Explicit
<choice>
 <sic>loica</sic>
 <corr>logica</corr>
</choice>
magistri pauli de Venetijs

The supplied element should be used for editorial additions, with the reason attribute (sample values: omitted, illegible, damage, or unknown).

  • supplied (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe.
    reasonone or more words indicating why the text has had to be supplied, e.g. overbinding, faded-ink, lost-folio, omitted-in-original.
  • ex (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation.
  • sic (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate.

Deletions by the scribe or later annotators should be recorded using the del element. The rend attribute may be used to indicate the manner of erasure: suggested values include strikethrough (the text has a line through it), erasure (the text has been scraped off), expunction.

  • 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.
    rend [att.global.rendition](rendition) indicates how the element in question was rendered or presented in the source text.

Additions by the scribe or later annotators should be recorded using the add element, with the place attribute. The values of the place attribute should be one of the values specified in the EpiDoc guidelines, e.g:

  • above: written above the line
  • below: written below the line
  • top: written in the top margin
  • bottom: written in the top margin
  • margin: written in an unspecified margin
  • unspecified: written in an unspecified location

  • add (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector.
    place [att.placement]specifies where this item is placed. Suggested values include: 1] top; 2] bottom; 3] margin; 4] opposite; 5] overleaf; 6] above; 7] right; 8] below; 9] left; 10] end; 11] inline; 12] inspace
Corrections by the scribe or later annotators should be recorded using a combination of the add and del elements with the subst or <mod> element.
<incipit>Theodocius dicit De coniugationibus apud grecos iii sunt
coniugationes uerborum
qu<subst>
  <del>a</del>
  <add>o</add>
 </subst>rum prima
positione</incipit>
Gaps should be marked with gap element, using the reason attribute to described the nature of the gap, and the unit attribute, in combination with quantity, and if necessary precision, to specify its extent. This extent should be indicated in characters if possible with the value char on the unit attribute. The atMost, atLeast may be used instead of quantity but these will be rendered as an ellipsis rather than a specific number of dots.
Suggested values for reason
  • damage: text has been omitted due to damage to the manuscript
  • illegible: text has been omitted because it is illegible (but the manuscript is not otherwise damaged)
  • editorial: text (e.g. the formulaic ending of an explicit) has been omitted for brevity
  • space: the gap in the transcription represents space that has been left in the manuscript itself, usually with the intention of text being supplied at a later stage. (Note: do not use this to transcribe initial letters which have been omitted: these should be transcribed using the supplied element.
  • lacuna: there is no gap in the text being transcribed, but the text is not complete (e.g. words or lines have been omitted from an exemplar).
<gap quantity="5reason="damage"
 unit="char"/>
<gap atLeast="4atMost="6"
 reason="illegibleunit="char"/>

Questionable or partly legible readings should be marked with unclear (generates a ‘(?)’ after the text in html)

Line beginnings should be indicated with empty lb elements, column beginnings with empty <cb> elements

1.3.10 Quotations from the manuscript

Quotations from the manuscript, outside of elements such as incipit, explicit and so on, should be enclosed in the q element. This may have attribute type with sample values:

  • pressmark: the quotation is a pressmark, shelfmark or similar
  • exLibris: the quotation is an ex libris inscription
  • inscription: the quotation is the inscription of a signer or reader

1.3.11 References to other manuscripts

References in the description to other manuscripts should be enclosed in bibl tags with type of value MS. The subtype may be used to indicate if the manuscript is held by the same institution that holds the manuscript being catalogued (value interal) or by another institution (value external). In the former case, the shelfmark should not include the location or institution name; in the latter case, location and institution should be included.

The ref element may be used to provide a link to an online catalogue or digital fascimile.
Eberbach, Cistercian abbey
(?): ‘modern’ chapter numbers added in boxes in the margin, as in
<bibl subtype="internaltype="MS">MS. Laud Lat. 107</bibl>.
This scribe was also
responsible for most of the Simeon manuscript (<bibl subtype="externaltype="MS">
 <ref target="http://www.bl.uk/manuscripts/FullDisplay.aspx?ref=Add_MS_22283">London, British Library, Add. MS. 22283</ref>
</bibl>) but
has not yet been identified in any other manuscripts or documents.

1.5 Subject Classifications

In some catalogues, the fourth button in the header is "Subjects" rather than "Places". This is an index of subject classifications, using the Library of Congress subject heading and name authorities.

<encodingDesc>
 <classDecl>
  <taxonomy xml:id="LCSH">
   <bibl>
    <ref target="http://id.loc.gov/authorities/about.html#lcsh">Library of Congress Subject Headings</ref>
   </bibl>
  </taxonomy>
 </classDecl>
</encodingDesc>
<profileDesc>
 <textClass>
  <keywords scheme="#LCSH">
   <list>
    <item>
     <term key="subject_sh2008111606">Shafiites--Early works
           to 1800</term>
    </item>
    <item>
     <term key="subject_sh85072984">Koran--Recitation</term>
    </item>
   </list>
  </keywords>
 </textClass>
</profileDesc>

Keywords apply to the manuscript as a whole. You can associate each with one or more specific works by enclosing the term in a ref whose target attribute is a space-separated list of pointers to the xml:id values of msItem elements, prefixed with #.

Each term must have a key attribute containing the LoC authority entry identifier prefixed with "subject_". The text within the term element is also required, as this is what is displayed on the manuscript's page on the web site. It can be a variant of LoC's preferred term, if you think that more appropriate. If the term hasn't been used before, it will be automatically added to the web site the next time it is re-indexed.

1.6 Manuscript Description

The sourceDesc element contains a single child element, the msDesc. Within that is all the information about the manuscript as a physical object, its constituent parts, and intellectual works represented within.

All manuscript descriptions must be informed by attention to codicological units. In other words, whether the manuscript was created in one place, over one period of time, or is a composite of parts from multiple sources, assembled at a later date.

If the manuscript forms a single codicological unit, its intellectual content, physical description, and history should be described directly under the msDesc element. Individual works can vary in date or hands while still being of a single source. In such cases, add note elements to the msItem for each work, and an overview for the whole manuscript in physDesc, history, etc. Do not simply enter information (dates, dimensions, etc) as lists of ref elements.

If the manuscript comprises multiple codicological units, each should be described in its own msPart element, and only information common to the whole manuscript should be described directly under the msDesc element. This will typically include aspects of the physical description (e.g. extent, foliation, binding), aspects of history (notably provenance and acquisition), but possibly also some intellectual content (for example, if a table of contents for the whole volume was added by a later owner, or if the manuscript has replacement leaves). Conversely information relevant to each unit should be described in separate msPart elements.

In each case the following elements are used:
<msDesc>
<!-- Common information -->
 <msPart>
<!-- Codicological unit 1 -->
 </msPart>
 <msPart>
<!-- Codicological unit 2 -->
 </msPart>
</msDesc>

1.6.1 The Manuscript Identifier

Information about the current location and shelfmark of the manuscript should be given in the msIdentifier element using the following elements in the following order: country, settlement, institution, repository, and idno which must have type with value shelfmark.

If the manuscript is well-known by a another name this should be recorded in a msName element. Former shelfmarks may be given inside an altIdentifier element in an idno element (type attribute with value former). If the manuscript has a reference number in another catalogue or reference work, this should be given inside an altIdentifier element in an idno element. The following values are currently used in the medieval catalogue:
  • SCN - Summary catalogue number
  • TM - identifier in Trismegistos
  • PR - papyrological reference
  • diktyon - Dikyton number
<msIdentifier>
 <country>United Kingdom</country>
 <region type="county">Oxfordshire</region>
 <settlement>Oxford</settlement>
 <institution>University of Oxford</institution>
 <repository>Bodleian Library</repository>
 <idno type="shelfmark">MS. Gr. class. b. 7 (P)</idno>
 <altIdentifier type="internal">
  <idno type="SCN">36946</idno>
 </altIdentifier>
 <altIdentifier type="external">
  <idno type="PR">P. Oxy. VII 1032</idno>
 </altIdentifier>
 <altIdentifier type="external">
  <idno type="PR">P. Oxy. VII 1049</idno>
 </altIdentifier>
 <altIdentifier type="external">
  <idno type="TM">20328</idno>
 </altIdentifier>
 <altIdentifier type="external">
  <idno type="TM">28329</idno>
 </altIdentifier>
</msIdentifier>

1.6.2 The Heading

For manuscripts described in detail, and/or containing more than one item, the head element should provide (1) a brief descriptive title (2) place of origin if known (3) date of origin. If the latter two are unknown, use the summary element within msContents instead.
<head>Ovid; England, 12th century</head>

1.6.3 Intellectual Content

The intellectual content of the manuscript or codicological unit should be listed in the msContents element.

1.6.3.1 Summary (optional)

The summary element can be used to provide a brief prose account of a manuscript's contents and significance, unless this has already been covered by the head.

1.6.3.2 Language(s) of the manuscript as a whole (optional)

Give the text language for the codicological unit in the textLangelement , as a child of msContents, immediately after summary (if used), with the mainLang attribute.
<textLang mainLang="grc">Greek</textLang>
For bilingual or multilingual units give the other languages in the otherLangs attribute, as a space-separated list.
<textLang mainLang="grc"
 otherLangs="la enm">
Greek with some
Latin and Middle English</textLang>

In some cases the decision of which language is ‘main’ and which is/are ‘other’ may be rather arbitrary.

The attributes values used should conform to the BCP 47 standard (http://www.rfc-editor.org/rfc/bcp/bcp47.txt) which start with two-or-three-letter ISO 639 codes for languages, then an ISO 15924 code for the script, and finally IANA language subtags (https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry) for other information, such as methods of transliteration.

If the unit contains multiple works, in different languages or scripts, the textLang element should be used in the msItem instead, q.v.

According to the conventions of the catalogue, languages may be encoded at a high or low level of granularity - for example, Middle English may be encoded as "enm" or as "en", Anglo-Norman French may be encoded as "fr" or "xno".

Current recommendations (July 2023) for cataloguers at Oxford and Cambridge are to encode languages to as granular a level as possible using the following codes:

Latin la
Ancient Greek grc
Modern Greek el
Old English ang
Middle English enm
English (after c. 1500); do not encode "Early Modern English" en
Old French fro
Middle French frm
Anglo-Norman xno
French fr

Guidance for other vernacular languages is under development.

1.6.3.3 Manuscript Item

The msItem element may be used:

  • To describe an item of intellectual content (including blank leaves if necessary)
  • To provide various notes about the manuscript's contents (e.g. to compare items and their order with the contents of other manuscripts, or to provide a note of content now missing that was formerly present.)

As a general rule, each distinct item in the manuscript should be descibed in a distinct msItem tag.

The items should be numbered with the n attribute. (This is particularly useful when the msItem element is nested, say to describe sections within works, or works in collections of works.) For retroconversion, follow the numbering system used in the original catalogue. For new cataloguing, use arabic numbers, using a decimal point when msItem is nested. For example, for the second section of the first work:
<msItem n="1.2">
<!-- ... -->
</msItem>
Just as the n attribute provides a way for readers to reference and locate items, xml:id attributes do the same for computers. So these ideally should be added too:
<msItem n="1.2"
 xml:id="Add_1056-item1-item2">

<!-- ... -->
</msItem>
Blank pages may be recorded as part of the item they follow, in a separate note element. The locus element may be used to encode the folio(s).
<note>
 <locus from="187vto="187v">Fol. 187v</locus>
blank.
</note>
More extensive streches of blank pages can be placed in a separate msItem.
<msItem>
 <locus from="187vto="189v">(fols. 187v-189v)</locus>
 <note>Blank.</note>
</msItem>

Pages containing short notes or scribbles by later hands should be recorded in the additions element, see 1.6.4.7 Additions.

1.6.3.3.1 What is a manuscript item?

The Guidelines offer the following definitions: ‘each discrete item in a manuscript’; ‘an individual work or item within the intellectual content of a manuscript’. Often the identification of these works or items does not pose difficulties, but many more complex cases do occur.

A more helpful definition of a manuscript item may be ‘a complete work or item, or a self-contained part of a larger work with (potentially) independent circulation’. A ‘self-contained part of a larger work’ could be a letter in a letter-collection, or a sermon in a homiliary; it could also represent the biblical text or the commentary in a glossed biblical manuscript.

As a guiding principle, where possible and practicable the msItem element should be used to markup up the work as a whole, and its self-contained parts, and the nesting of the different msItem elements should express the relationship between part and whole.

However, it is recognised that it may not be practical (for example) to markup every letter in a letter-collection as an msItem, and that the contents and order of a collection may simply be recorded in a note element.
<author key="person_95147024">Jerome</author>
<title key="work_2426">112 letters</title>
<note>
 <title>Epist.</title> 57 (38), 73 (44), 129 (57), 35
(1), 36 (2; as 3 items, dividing in sects. 10-15), 62
(3), 19 (4), 20 (5), 15 (6), 16 (7), 18B (8), 18A (9),
21 (10), 14 (37), 52 (33), 58 (34), 55 (?), 83-4
(39-40),
<!-- etc. -->
</note>

Difficulties are posed by:

  • texts which circulate with shorter related texts, for example Augustine’s De Trinitate, preceded in Merton College MS. 32 by the relevant extract from Retractationes and by Ep. 74.
  • texts followed or preceded by indexes (e.g. Merton College MS. 34, Augustine on the Psalms followed (fols. 385-412v) by a subject index.
  • brief items not catalogued in detail or not considered worth cataloguing in full, e.g. Merton College MS. 13 art. 6, Prouerbia Wiponis ‘followed by brief theological notes’. Merton College MS. 13, art. 22, Prosper, Responsiones, ‘Followed by ‘Quot secte Iudeorum. Quot fuerunt secte Iudeorum qui fuerunt separati a communi uita ...’, and extracts from Augustine, Jerome and Ambrose ff. 116v-17v.’

Recommended best practice is to catalogue and encode so that each item mentioned is discoverable. This can be achieved in different ways according to the information available. Suggested encodings for the above examples are:

<msItem>
 <author key="person_66806872">AUGUSTINE</author>
 <title key="work_784">De Trinitate</title>
 <note>Preceded by the relevant extract from <title key="work_804">Retract.</title> and the <title key="work_801">Epistola ad Aurelium (Epist.
     74).</title>
 </note>
</msItem>
<msItem>
 <locus>(fols. 1-384v)</locus>
 <author key="person_66806872">AUGUSTINE</author>
 <title key="work_790">Enarrationes in Psalmos
   77-148</title>
 <rubric>Incipit tractatus de psalmo septuagesimo
   septimo</rubric>
 <incipit>Psalmus iste ea continet quem ueteri populo
   diuinitus acta narrantur</incipit>
 <explicit>(<note>ends impf. in Ps. 148: 17;
     catchwords)</note> Cantus est cum laude
   Dei</explicit>
 <note>
  <title>CPL</title> 283; <title>CCSL</title> 39-40
   (2<hi rend="superscript">nd</hi> edn., 1990), p.
   1066 – 40, p. 2176 line 39.</note>
</msItem>
<msItem>
 <locus>(fols. 385-412v)</locus>
 <msItem n="a">
  <title type="desc">An index in 4 cols of first
     verses of each Psalm</title>
 </msItem>
 <msItem n="b">
  <title type="desc">Subject-index, ‘<hi rend="italic">Abissus</hi><hi rend="italic">Zelus</hi></title>
  <incipit>Abissus dicuntur in profundo
     peccati</incipit>
  <note>f. 413rv blank</note>
 </msItem>
</msItem>
1.6.3.3.2

For sample encodings of liturgical books (a Book of Hours) and a Bible, see the Appendix.

1.6.3.3.3 Texts with gloss and commentary

Treatment of these texts will vary according to the arrangement of text, gloss, and commentary; whether gloss and commentary are continuous; whether gloss and commentary are contemporary or later, and whether they form an integral part of the mise-en-page; whether there are multiple layers of gloss / commentary. Examples:


<!-- MS. Junius 27 --><msItem>
 <note>Psalter with Old English gloss</note>
 <msItem>
  <title>Psalms (Roman version)</title>
  <note>Beginning imperfectly at 2.4 and ending at
     144.6</note>
  <incipit defective="true">Qui habitat in
     caelis</incipit>
  <explicit defective="true">terribiliorum tuorum
     dicent</explicit>
 </msItem>
 <msItem>
  <title type="desc">Continuous interlinear gloss in
     Old English</title>
  <incipit>se eardað in heofonum</incipit>
  <explicit>þinra eyes fulnessa cweoðað</explicit>
 </msItem>
</msItem>

<!-- Christ Church MS. 95 --><msItem>
 <locus> Fols 1-161<hi rend="superscript">v</hi>
 </locus>
 <title key="work_13747type="desc">Pauline Epistles,
   with gloss </title>
 <msItem>
  <incipit type="text">Pavlvs seruus ihesu cristi
     uocatus apostolus segregatus</incipit>
 </msItem>
 <msItem>
  <note>Interlinear gloss:</note>
  <incipit>Saluatoris Regis sacerdotis cui merito
     omnes serui predicandum</incipit>
 </msItem>
 <msItem>
  <note>Marginal gloss:</note>
  <incipit>Pro altercatione scribit apostolus Romanis
     confutans modo gentiles</incipit>
 </msItem>
<!-- ... -->
</msItem>
1.6.3.3.4 Relating manuscript items to quires
Some catalogues/cataloguers indicate the relationship between each item and the quires of the codex. This may be encoded as follows:
<msItem>
 <note>Items 2-3 occupy quires 3-4.</note>
</msItem>
1.6.3.3.5 Extracts and parts of works
If only an extract of a work is present this should be encoded using the bibl element. Within this, the citedRange element may be used to provide a machine-reading encoding of which parts of the work are given.
<author key="person_59077661">Thomas à Kempis</author>
<title key="work_4859">Imitatio Christi</title>
<bibl>(book <citedRange from="1to="1unit="book">i</citedRange>)</bibl>
1.6.3.3.6 General notes on the content
These may be placed at the beginning or end of the msContents section in a separate msItem element.
<msItem>
 <note>Items (a)-(i), (j), (k) are in Vienna,
   Nationalbibl. MS. 415 in the same order.</note>
</msItem>
1.6.3.3.7 Added texts

Significant added texts should be described in msContents, NOT in additions. Decision as to what is ‘significant’ will be a matter of judgement, but in general if the text is to be discoverable - if it is important for the text to be identified or described, or to have its rubrics / incipits recorded, etc. - it should be encoded using msItem. This may involve some reorganization of the description during retroconversion.

Two possible approaches are described here. Each may be appropriate in different circumstances, dependent for example on the nature of the manuscript and/or the nature of the description being converted:

  • describe every msItem in sequence, using note to indicate if it is a later addition
  • Group added texts together in a separate section at the end of msContents, preceded by
    <msItem>
     <note>Added texts:</note>
    <!-- added texts here -->
    </msItem>

<!-- Christ Church MS. 105 --><msItem>
 <note>Added texts:</note>
 <msItem n="a">
  <locus>Fol. 164<hi rend="superscript">v</hi>
  </locus>
  <title key="work_10687type="desc">Calendar</title>
<!-- ... -->
 </msItem>
 <msItem n="b">
  <locusGrp>
   <locus from="356rbto="356vb">Fols 356<hi rend="superscript">rb-vb</hi>,</locus>
   <locus from="374rato="374rb">374<hi rend="superscript">rab</hi>
   </locus>
  </locusGrp>
  <incipit>heremita yu semest a fela <gap quantity="6unit="chars"/>
   <lb/>
   <gap quantity="18unit="chars"/> was he<gap quantity="2unit="chars"/>
   <lb/> but yu wit me al ny3t</incipit>
  <incipit>
   <locus>[fol. 374<hi rend="superscript">ra</hi>]</locus> And you seeme welle...</incipit>
  <incipit>
   <locus>[fol. 374<hi rend="superscript">rb</hi>]</locus> So help me lorde Jesu</incipit>
  <explicit>
   <gap quantity="13unit="chars"/>d ye <gap quantity="2unit="chars"/>y<gap quantity="1unit="chars"/> prince <lb/> For yis work as tu
     worth</explicit>
  <title key="work_12461">The King and the
     Hermit</title>
  <note> A version of ‘The king and the hermit’ (IMEV
     1764; DIMEV 2918), ed. W. Carew Hazlitt,
  <title>Remains of the Early Popular Poetry of
       England</title>, 4 vols (London, 1864-66), 1:12-34
     and, most recently, George Shuffleton,
  <title>Ashmole 61: A Compilation of Popular Middle
       English Verse</title> (Kalamazoo, MI, 2008),
     401-13, 590-6, 627-8 (with our copy opening with a
     version of l. 285). Here presented as if a
     dramatic dialogue, apparently extending beyond the
     fragmentary conclusion of the sole previously
     available witness, BodL, MS Ashmole 61, from which
     it also widely diverges. Written in on blank
     leaves in plummet, partially washed and much
     faded, in anglicana, s. xiv<hi rend="superscript">ex</hi>. The incipit above corresponds to line
     291 of the printed text (24); the text may begin
     on the virtually illegible fol. 374.</note>
 </msItem>
 <msItem n="c">
  <locus>Fols 372<hi rend="superscript">ra</hi>-73<hi rend="superscript">vb</hi>
  </locus>
  <incipit defective="true"> an sit agend’ indic’
     officio ut notatur Capitulo de edis
     do<ex>m</ex>ini</incipit>
  <explicit defective="true">clericus non intellegitur
     quod ad hoc potenter laico nec cedens euattura
     racione afficitur</explicit>
  <title key="work_14189type="desc">Questions in
     canon law (?)</title>
  <note>Apparently questions in canon law, incomplete
     at both ends. In double columns, each column 255
     mm x 80-85 mm, with 12 mm between columns, in
     about 64 lines to the column. Written in academic
     gothic textura quadrata, s. xiv med.</note>
 </msItem>
 <msItem n="d">
  <locus>Fol. 374</locus>
  <note>The opening of a list of the readings
     (epistle, lesson, gospel) for Sundays and
     feastdays; in gothic textura quadrata, s.
     xiii/xiv.</note>
 </msItem>
</msItem>
1.6.3.3.8 Locus
Give the start and end folio of each item according to the guidelines specified in 1.3.2 References to Locations within a Manuscript. If there are several items on a single folio, you may specify on which line the text starts and ends. For texts scattered over more than one location in the manuscript the locusGrp element should be used.
<locusGrp>
 <locus from="356rbto="356vb">Fols 356<hi rend="superscript">rb-vb</hi>,</locus>
 <locus from="374rato="374rb">374<hi rend="superscript">rab</hi>
 </locus>
</locusGrp>
1.6.3.3.9 Author
The author of a manuscript item, if known, should be recorded inside the author element. This MUST have a reference, using the key attribute, to the persons authority file, see 1.3.3 Personal Names. The author element should be omitted for anonymous works.
<author key="person_66806872">Augustine</author>

The author name should be given in a standardized form. For retroconversion, use the form of the name given in the source text; for new cataloguing, use a standard form from the usual reference works.

If you are not responsible for maintaining the authority files, go to the web site, click the People button, and search to see if the same person already exists in another manuscript in the same catalogue, with the same or similar (or translated) name. If they have, set the key attribute to the identifier of the existing record, which is the part of the URL after the last slash, starting with "person_". If you can find the person by searching in VIAF (http://viaf.org/) set the value to "person_" followed by their VIAF number. Otherwise, leave the key attribute blank and an identifier will be assigned to it at a later date.

Where an author has multiple names (e.g. translations or transliterations) add these as child persName elements (with xml:lang attributes). Do not use foreign in this context. But the key attribute remains on the author element. Multiple author elements should be used for works with multiple authors (not other contributors, such as scribes, these should be added as editor elements with role attributes.)

(Optional) Either author or persName elements can contain surname, forename and addName child elements to divide up the full name as appropriate to naming customs (addName has a type attribute in which you can specify "laqab", "kunyah", "khitab", "nisbah”", etc.)

(Optional) To indicate that an author's name is not present in the MS., use supplied.
<author key="person_66806872">
 <supplied>Augustine</supplied>
</author>
1.6.3.3.9.1 Pseudonymous, multiple, uncertain, disputed and attributed authorship
Texts which circulated consistently but incorrectly under the name of an author, but whose true author is not known, are by convention attributed to Pseudo-Augustine, Pseudo-Ambrose, etc., and these conventional attributions should be followed.
<author key="person_7386286">Ps.-Augustine</author>
<title key="work_3881">De Vera et Falsa
Poenitentia</title>
Texts which circulated consistently but incorrectly under the name of an author, but whose true author IS now known or suspected, should be catalogued under the author which modern scholarship prefers. In some cases, where the association with other authors is strong, it will be useful to give these in addition.
<author key="person_79148266">Haimo of Auxerre
(Ps.-Haimo of Halberstadt, Ps.-Cassiodorus)</author>
<title key="work_1946">Commentary on the Song of
Songs</title>
Note that the pseudonymous authors do not have their own author element (these may be given in the authority file: q.v.).
Where the attribution of a text in the manuscript differs from the attribution of modern scholarship, this can be recorded either in a note element or by relevant markup in the rubric element. Use the persName element with attribute role of value att (= ‘attributed name’)
<author key="person_84971682">Ivo of Chartres</author>
<title>Epistola ad Seuerinum</title>
<rubric>Incipit liber <persName key="person_100187025"
  role="att">
Anselmi</persName> de caritate</rubric>
<author key="person_209749583">
 <supplied>Ps.-Bede</supplied>
</author>
<title key="work_6131">
 <supplied>Commentary on
   John</supplied>
</title>
<note>Cap. 3. Here ascribed to <persName key="person_66806872role="att">Augustine</persName>.</note>
Multiple authors can be indicated using repeated author elements.
<msItem n="1xml:id="MS_Douce_332-item1">
 <author key="person_95220054">Guillaume de
   Lorris</author>
 <author key="person_304922354">Jean de
   Meung</author>
 <title key="work_1919">Le Roman de la Rose</title>
 <textLang mainLang="frm">Middle French</textLang>
</msItem>
Uncertainly regarding authorship can be indicated using the cert attribute. Following the usage of Richard Sharpe, ‘attrib.’ can be used for modern scholarly attributions of authorship; ‘ascr.’ denotes ascriptions in manuscripts; and ‘(?)’ denotes broader uncertainty.
<author cert="mediumkey="person_2205">Roger of Caen
(attrib.) (Ps.-Alexander Nequam)</author>
<title key="work_4455">De professione monachorum</title>
1.6.3.3.10 Editor / translator / etc.

For secondary statements of responsibility, use the editor element, distinguished with a role attribute containing a three-letter code (or multiple codes separated by spaces) selected from the MARC relators list (https://www.loc.gov/marc/relators/relaterm.html). Do not add a label for their role, as this will be added when displayed on the web site. For example, for a translator:

<editor key="person_5150639role="trl">
 <persName>Abū al-Faz̤l ibn Mubārak, 1551-1602</persName>
 <persName xml:lang="fa">ابو الفضل بن مبارك علامی</persName>
</editor>

In all other respects, editor elements can contain the same child elements as author (eg. multiple persName elements) and attributes (e.g. a key linking them to an entry in the persons authority file, so that they are indexed on the web site.) Further details about their role in the creation of the work can be explained in a separate note.

Alternatively (this is current practice in the medieval catalogue) information about translators, etc., may be provided in the note element as follows:
<author key="person_95155322"> Origen </author>
<title key="work_3395">Homilies on Joshua</title>
<note>(Latin tr. by <persName key="person_77679446role="trl">Rufinus</persName>)</note>
1.6.3.3.11 Title

The title element provides a standarized uniform title or a descriptive title for a manuscript item.

For retroconversion, use the form of the title given in the source catalogue (if one is given); for new cataloguing (or if the converted catalogue does not supply a title), use a standard form from the usual reference works; if a standard form cannot be found, one should be supplied by the cataloguer. By default titles are displayed in italic font.

If the title is descriptive, the type attribute should then be set with the value desc. This will display the title in normal font. Alternative titles should be give a type of alt, and main and sub can be used if there is a subtitle.

When providing translations of the title, or multiple versions in different scripts or forms of transliteration, add them as sibling title elements, each with an xml:lang attribute. Do not use foreign except to mark up a word or phrase within a title as being in a different language to the rest of the title.

Works which are to be indexed (i.e. you consider significant enough to be listed under the Works button on the web site) MUST have a reference using the key attribute to the works authority file
<title key="work_15602type="desc">Commentary on
Apocalypse</title>

If you are not responsible for maintaining the authority files, go to the web site, click the Works button, and search to see if the same work already exists in another manuscript in the same catalogue, with the same or similar (or translated) title. If it has, set the key attribute in the title element(s) to the identifier of the existing record, which is the part of the URL after the last slash, starting with "work_". Otherwise, leave the key attribute blank and an identifier will be assigned to it at a later date.

(optional) to indicate the title is not given in the manuscript, use the supplied element.
<author key="person_89657091">
 <supplied>Bonaventure</supplied>
</author>
<title key="work_1144">
 <supplied>Legenda
   maior</supplied>
</title>
1.6.3.3.12 Rubrics, incipits, explicits, final rubrics, and colophons.

Retroconversion: include these items if they are given. New cataloguing: include these items for all texts. The absence of a rubric need not be noted, although it can be included in a note if it is significant (e.g. all other texts do have rubrics).

Follow the principles of transcription outlined above 1.3.9 Transcription to transcribe the MS. or to encode the text given in an existing catalogue.

It is assumed that the language of incipits, etc., is the same as the language specified in textLang. It is not necessary to use xml:lang to specify the language of the incipit (etc.), unless multiple languages are involved (e.g. msItem with rubric in French but incipit in Latin).
<msItem xml:id="MS_Buchanan_e_13-item1-item5-item1">
 <locus>(fols.18r-21v)</locus>
 <rubric xml:lang="frm">Oraison tres deuote de nostre
   dame</rubric>
 <incipit xml:lang="la">Obsecro te</incipit>
 <note>[masculine forms] (cf. MS. Buchanan e. 2)</note>
</msItem>

For mutilated items the attribute defective should be used with value true.

The formatting of the rubric can be recorded in the rend attribute (see 1.3.7 Formatting). Comments on the rubric (e.g. if it is a later addition) can be recorded using a note tag inside the rubric tag.
<msItem n="6xml:id="MS_Ashmole_304-item6">
 <locus from="64rto="70v">(fols. 64r-70v)</locus>
 <title key="work_16047">Divinacio
   ciceronalis</title>
 <note>(incomplete)</note>
 <note>See A. A. Guardo, 'La <foreign rend="italic">Divinacio Ciceronalis</foreign>: un libro de
   suertes medieval. Estudio introductorio', in
 <title>De lo humano y lo divino en la literatura
     medieval: santos, ángeles y demonios</title>, ed.
   Juan Paredes Núñez (2012), 17-34.</note>
 <note>The surviving section in this MS. comprises the
   responses, fourteen (of originally 20) sections of
   21 lines, the first line of each in red, each
   section attributed to sun, moon, a planet or a sign
   of the zodiac (Guardo's section 4). The text in MS.
   Digby 46 has in addition a miniature of Cicero,
   twenty prognostical questions, and directions for
   use (see Guardo).</note>
 <rubric>Sol iudex primus</rubric>
 <incipit defective="true">
  <note>(first line in
     red)</note> Mittam te ad amicum meum et dicet tibi
   uerum Certe tibi dico prope est ut gaudeas et mutes
   fortunam</incipit>
</msItem>
Note that TEI distinguishes between the finalRubric, which contains a statement relating to the end of a particular work (e.g. ‘explicit liber’), and the colophon, which contains a statement about the scribe and/or date and/or place of writing (‘scriptum apud Oxon.’). If the final rubric and colophon form a single sentence, put both inside finalRubric with type attribute of value colophon. (The colophon element cannot have the type attribute.)
<finalRubric type="colophon">Expliciunt omelie Iohannis
Crisostomi patriarche Constantinopolitanis super Matheum
operis imperfecti scripte anno Domini 1382</finalRubric>
Multiple incipits, rubrics, etc., e.g. for prologues, dedications, text, should be distinguished using type (and if necessary by location, by including a child locus element at the start of each one). Suggested values of the type attribute are prologue (use for preface, prohemium, etc), dedication, text
<msItem>
 <locus from="12vto="12v">(fol. 12v)</locus>
 <author key="person_11566602">Garland</author>
 <title key="work_1724type="desc">Compotus</title>
 <incipit type="prologue">Sepe uolumina domni
   Bede</incipit>
 <incipit type="text">Superioris igitur pagine</incipit>
</msItem>
Use of the type attribute will not always be possible in retroversion if the catalogue does not provide the information. In this case a series of the relevant elements without type should be used.

<!-- Merton College MS. 20 --><msItem n="1">
 <locus from="1rto="14v">(fols. 1-14v)</locus>
 <author key="person_100187025">Anselm</author>
 <title key="work_537">Monologion</title>
 <rubric>Incipit epistola Anselmi archiepiscopi ad
   Lanfrancum primatem Anglie</rubric>
 <incipit>Reuerendo et amando suo domino</incipit>
 <rubric>Incipit prohemium beati Anselmi archiepiscopi in
   monologion R.</rubric>
 <incipit>Quidam fratres sepe me studioseque</incipit>
 <note>(<foreign rend="italic">capitula</foreign>)</note>
 <incipit>Si quis unam naturam summam omnique que
   sunt</incipit>
 <explicit>Deus ineffabilis trinus et unus</explicit>
 <finalRubric>Finitur monologion Anselmi.
   Explicit.</finalRubric>
 <bibl>
  <title>SAO</title> 1. 13-87.</bibl>
</msItem>

The rubric, incipit, etc. elements should not have final punctuation, unless they contain more than one sentence, in which case there should be a closing period.

1.6.3.3.12.1 Complex incipits

The incipit elements in a catalogue may be processed to generate an alphabetical list of incipits similar to those in a print catalogue.

For long and complex incipits, care should be taken to mark up the content in a way that enables multiple index entries to be generated to aid discovery.

Incipits containing an initial address should be divided into two incipit elements, the first containing the address and the second the incipit itself.
<author key="person_47155211">PETER OF WALTHAM</author>
<title key="work_3545">Remediarium Conuersorum</title>
<incipit>Reuerendo patri Ricardo ecclesie Londoniensi
episcopo tercio suus Petrus Blesensis archidiaconus
eiusdem ecclesie sic currere per temporalia ut
brauium apprehendat eternum</incipit>
<incipit>De beata mentis solitudine necnon et euangelice
paupertatis beatitudine </incipit>
Incipits of sermons often begin with a biblical lemma, and in a printed catalogue would be indexed both under the lemma and under the incipit. These should be marked up using the cit, quote, and bibl elements as follows.
<incipit>
 <cit>
  <quote rend="italic">Qui mihi ministrat me
     sequitur.</quote>
  <bibl>Io. 15.</bibl>
 </cit> In his uerbis notantur
duo; primum est Christo debita
administracio
</incipit>
If the source is not given, the quote element only may be used.
<incipit>
 <quote rend="italic">
  <supplied>V</supplied>erbo
   Domini celi firmati sunt</quote> &amp;c. Tria in
hiis uerbis sunt notari primum omnium sacre
scripture dignitas
</incipit>
Where a brief lemma would not typically be indexed separately (e.g. in a glossary or commentary), but would be considered an integral part of the incipit, the lemma may only be distinguished typographically.
<incipit>
 <hi rend="italic">Abba</hi> secundum Papiam
Syrum nomen est
</incipit>
1.6.3.3.13 Note, bibliography and additional information
Additional information about the text - for example whether or not the text is complete; whether or not the text is glossed or annotated; other copies of the text; references to repertories and editions - can be presented in various ways. It may be convenient in retroconversion to include this information in a single note element. Equally some of this information may be encoded more appropriately using other elements, such as bibl or filiation. Compare:
<msItem n="3">
 <locus>(fols 54r-73r)</locus>
 <author key="person_196789494">
  <supplied>Ps.</supplied>
   Athanasios</author>
 <title key="work_5884">Disputatio contra Arium</title>
 <note>CPG 2250, PG 28.440-501.</note>
</msItem>
<msItem n="3">
 <locus>(fols 54r-73r)</locus>
 <author key="person_196789494">
  <supplied>Ps.</supplied>
   Athanasios</author>
 <title key="work_5884">Disputatio contra Arium</title>
 <listBibl>
  <bibl>CPG 2250</bibl>
  <bibl>PG 28, 440-501</bibl>
 </listBibl>
</msItem>
The filiation element provides information about the relationship of the manuscript with other surviving manuscripts in terms of their content. For example:
<msItem n="2">
 <title xml:lang="ara-Latn-x-lc">Khulāṣat al-ikhtiṣāṣ fī
   maʻrifat al-quwá wa-al-khawāṣṣ</title>
 <filiation>There is another manuscript of this work at
   the Birmingham University, Mingana Collection,
   Islamic Arabic Ms. no. 933 (1485)</filiation>
</msItem>
A bibl containing a ref element can be used to link to external resources related to a work, such as printed catalogue pages.
<listBibl>
 <bibl>
  <ref target="http://www.lib.cam.ac.uk/arabic_catalogues/browne/view.php? id=76">no. 673</ref>
 </bibl>
</listBibl>
Do not use this method to link to digitized copies, use <surrogates> instead.

1.6.4 Physical description

The physical description includes serveral different aspects of the manuscript (or part of a manuscript) including:

  • aspects of the form, support, extent, and quire structure of the manuscript object and of the way in which the text is laid out on the page.
  • the style of writing used and discussion of any decorative features, any musical notation employed, and of any annotations or marginalia.
  • discussion of binding, seals, and any accompanying material.

1.6.4.1 secundo folio

Provide a transcription of the words found at the beginning of the recto side of the second leaf of the manuscript. These were often used in medieval book-lists or inventories and may sometimes be useful for identification of provenance – or simply for modern-day identification.

This information is placed inside the secFol element, inside a p element, directly after physDesc

If the manuscript begins imperfectly – for instance, if the first leaf of text is missing – provide both the original and the present-day secundo folio, in order to avoid any ambiguity.

If the manuscript begins with prefatory paratextual matter, such as an index, you should record the secundo folio in both this and the main text. Use locus to record the location of each.

If the secundo folio begins mid-word, the missing portion may be provided inside a supplied element


<!-- MS. Buchanan e. 10 --><physDesc>
 <p>
  <secFol>
   <locus from="3rto="3r">(Calendar, fol. 3)</locus>
     KL Feurier a</secFol>
  <secFol>
   <locus from="15rto="15r">(text, fol. 15)</locus>
     venientem in</secFol>
 </p>
</physDesc>

1.6.4.2 Object Description

The physical form of the carrier should be set in the form attribute of the objectDesc element. This should refer to the form of the object in its original state, before any mutilation, rebinding etc. The following values are recommended:
  • codex: multiple gatherings of leaves, held within a binding of some kind, and used by turning the leaves.
  • roll: a parchment membrane, or two or more such membranes, either sewn together edge-to-edge to form a continuous surface for writing, or laid together in a pile and sewn together at the head, and used by unrolling the membranes.
  • sheet: a single sheet of parchment or paper, not intended to form part of a codex, either kept flat or folded (rather than rolled) for storage.
  • faltbuch
  • roll-codex
  • other
  • unknown
The following may also be used:
  • booklet: a gathering of two or more bifolia, with a binding/covering, that appears to be complete in terms of its original textual content
  • quire: a complete gathering of two or more bifolia, without a binding/covering.
<physDesc>
 <objectDesc form="codex">
<!-- -->
 </objectDesc>
</physDesc>
1.6.4.2.1 Support Description

The supportDesc element may contain the following elements:

  • support (support) contains a description of the materials etc. which make up the physical support for the written part of a manuscript or other object.
  • 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.
  • foliation (foliation) describes the numbering system or systems used to count the leaves or pages in a codex or similar object.
  • collation (collation) contains a description of how the leaves, bifolia, or similar objects are physically arranged.
  • condition (condition) contains a description of the physical condition of the manuscript or object.

The support material for the codicological unit(s) should be recorded in the material attribute of supportDesc. Allowed values are: chart (for all kinds of paper), perg (for parchment and vellum), papyrus, palm (palm leaf), mixed, unknown, or other. The name of the material for display purposes, and further description of the support, should be added in the support element. For example:

<supportDesc material="chart">
 <support>Paper</support>
</supportDesc>
<supportDesc material="perg">
 <support>Exceptionally thick, stiff parchment</support>
</supportDesc>
1.6.4.2.1.1 Support
Provides a prose description of the material. For parchment, this may include comment on the quality of the parchment and its disposition. For mixed material, the nature of the combination should be described.
<support>Paper,
with parchment bifolia for the outer and inner
leaves of the quire.</support>
If the disposition of hair and flesh sides of parchment is recorded, this should be done consistently using the letters H (for hair) and F (for flesh) inside a term element with attribute type of value disposition. If the disposition is consistent throughout the manuscript, the formula need only refer to each side of the first two leaves in a quire. For example, HFFH indicates that the hair side is on the outside of the quire, with flesh sides facing flesh sides and hair sides facing hair sides in the rest of the quire (and vice versa). By contrast, FHFH indicates that the flesh side is on the outside of the quire, with hair sides facing flesh sides and flesh sides facing hair sides in the rest of the quire (and vice versa). For irregularly arranged quires, we recommend the provision of a full formula. If the disposition varies between portions of a composite manuscript, use msPart to provide separate formulae. Formulae such as 'HSOS' (hair side outside) should be altered in retroconversion. If the disposition of parchment varies between quires or otherwise between sections of the manuscript, it should be described in the layout element, rather than in support.
<support>Parchment (<term type="disposition">FHHF</term>)</support>
<support>Parchment (<term type="disposition">HFHF</term>)</support>

Note that this convention regarding H and F differs from the usage attributed to Julian Brown, in which our HFFH would be rendered HHHH, the H in the latter case describing the recto of each leaf in the first half of the quire. If retroconverting, ensure that you have understood the original intention of the cataloguer.

If different materials are used (paper and parchment, different kinds of parchment, or different paper stocks, for example), these may be described in separate material elements.

1.6.4.2.1.1.1 Description of paper

The level of detail in which paper is described will vary: in retroconversion, according to the detail of existing descriptions; in cataloguing afresh, according to the resources available

The paper should be described inside the support element. If there are multiple paper stocks, each should be described in its own material element.

The folding of the paper should be recorded using a measure element with the type attribute (value: folding) and quantity attribute whose values will be folio, quarto, etc.

The original size of the sheet may be given using dimensions with attribute type of value paperSheet

The number of chainlines per leaf should be recorded using a measure element with type of value chainlinesLeaf and an appropriate value of quantity.

The distance between chainlines may be recorded using dimensions with type of chainLines, containing a width element with quantity.

1.6.4.2.1.1.1.1 Watermarks

Describe each watermark in the watermark element.

The key term for the motif should be encoded using the term element with attribute type of value watermarkMotif and attribute key with the relevant value from the IPH standard. Additional descriptive terms may be placed inside a note element with type of watermarkVariation

The position of the watermark should be recorded in a note element with type of watermarkPosition

The dimensions of the watermark may be given in a dimensions element with type of watermark.

References to printed repertories may be given in the format specified above at Repertories. References to online repertories may be given using the ref element.

Countermarks should be described using the countermark element. Note that this customization is not currently part of the TEI P5 standard.

1.6.4.2.1.1.1.2 Examples:
<watermark>
 <term key="J3/3type="watermarkMotif">Monts/Dreiberg</term>
</watermark>
<support>
 <material>
  <locus from="1rto="48v">Fols. 1-48</locus>,
   paper, folded in <measure>quarto</measure>; <num type="chainlinesLeaf">8</num> chainlines per leaf.
 <watermark>Watermark: <term type="watermarkMotif">Hand</term>, <note type="variation">surmounted by
       a fleuron</note>, <note type="position">on a
       chainline</note>. </watermark>
 </material>
</support>
<support>
 <material>
  <locus from="1rto="48v">1-48</locus>, paper,
   folded in <measure>quarto</measure>, <note type="paperType">chancery</note>; original size of
   the sheet <dimensions type="sheetunit="mm">
   <height>315</height>
   <width>425</width>
  </dimensions> Chainlines: <num type="chainlinesLeaf">8</num> chainlines per leaf,
 <num type="chainlinesSheet">23</num> chainlines
   per sheet. <dimensions type="chainlinesunit="mm">
   <width>19</width>
  </dimensions> mm. between
   chainlines. <watermark>Watermark: <term type="watermarkMotif">Hand</term>, <note type="watermarkVariation">surmounted by a
       fleuron</note>, <note type="watermarkPosition">on
       a chainline</note> (<ref target="http://www.ksbm.oeaw.ac.at/_scripts/php/loadRepWmark.php?rep=briquet&amp;refnr=10713&amp;lang=fr">Briquet 10713</ref>)</watermark>
 </material>
 <material>
  <locus from="49rto="72v">49-72</locus>, paper,
   folded in <measure>folio</measure>, <note type="paperType">chancery</note>; original size of
   the sheet <dimensions type="paperSheetunit="mm">
   <height>290</height>
   <width>420</width>
  </dimensions>. Chainlines: <num type="chainlinesLeaf">6</num> chainlines per leaf,
 <num type="chainlinesSheet">12</num> chainlines
   per sheet. <dimensions type="chainlinesunit="mm">
   <width>33</width>
  </dimensions> mm. between
   chainlines. <watermark>Watermark: <term type="watermarkMotif">Bird</term>, <note type="watermarkVariation">with a cross surmounted
       with trefoils</note>, <note type="watermarkPosition">between chainlines</note>
     (<ref target="http://www.ksbm.oeaw.ac.at/_scripts/php/loadRepWmark.php?amp;rep=briquet&amp;refnr=12170&amp;lang=fr">Briquet 12170</ref>) <dimensions type="watermarkunit="mm">
    <height>41</height>
    <width>19</width>
   </dimensions>
  </watermark>
 </material>
</support>
1.6.4.2.1.2 Extent

This should contain:

seg and type may be used to separate these sections within extent, as shown below.

If the present state of the item is different from its original state, record this information within objectType, using the following terms:

  • roll-codex = a codex in which formerly joined membranes have been separated and rebound to resemble a codex, perhaps in concertina form
  • fragment = one or more remnants from a manuscript, whose survival in a form different to their original state has been accidental or an unintended consequence of their use for some other purpose not directly concerned with their original content or history (e.g. as pastedowns or sewing guards).
  • cutting = a single portion of a leaf, whose removal was guided by aesthetic or other criteria of selection, with the intention of preserving it separately from the rest of the manuscript.

Where necessary (particularly in the case of fragments), further brief description may be provided after the closing objectType tag, using the following terms:

  • quire = a complete gathering of two or more bifolia, without a binding/covering.
  • bifolium = two conjoint (but not necessarily contiguous) leaves, originally or still folded vertically down the middle, perhaps removed or otherwise detached from a codex.
  • leaf = a single leaf
<extent>
 <seg type="object">
  <objectType>Fragment</objectType>, comprising two
   originally contiguous strips of parchment, removed
   from a binding. </seg> [...]
</extent>
1.6.4.2.1.2.1 Number of leaves

The number of leaves within a manuscript has generally been expressed using a formula that separates endleaves from the leaves at the ‘core’ of the volume (formed by gatherings of leaves whose structure can be determined in collation). E.g. ii + 320 + ii (i.e. a medieval manuscript opening with two post-medieval endleaves, then 320 medieval leaves, and closing with two post-medieval endleaves).

Sometimes, a formula might distinguish between different kinds of endleaf. Example: ii + 1 + 320 + ii (i.e. a medieval manuscript opening with two post-medieval endleaves, a single medieval leaf, then 320 medieval leaves, and closing with two post-medieval endleaves).

It can sometimes be difficult to distinguish whether such leaves as that denoted by ‘+ 1’ in the above formula are original (i.e. were included in the manuscript when it was first made), contemporary (i.e. included around that time), or were added at some later juncture as part of a rebinding during the medieval period. In any case, they are not part of the quire structure.

Since this kind of endleaf may contain (for example) annotations, added texts, or information of relevance to the manuscript’s medieval provenance, or may comprise leaves recycled from another medieval manuscript (and therefore bearing text in need of identification), the current guide recommends that these endleaves be distinguished both from others that were clearly added later and from the ‘core’ leaves in a volume.

Use measure to encode each group of leaves separately, with the attribute value to provide the number of leaves within that group.

Use the following conventions:

  • lower-case Roman numerals to refer to endleaves that were not part of the original manuscript and are demonstrably not medieval, type=laterEndleaf
  • Arabic numerals to refer to endleaves that are either original / contemporary / medieval, encoded as type=endleaf
  • Arabic numerals to refer to leaves that are the ‘core’ of the volume, encoded as: type=leaf. (If the volume is paginated, use type=page.)
  • for rolls: Arabic numerals to refer to the number of membranes, encoded as: type=membrane

The terms ‘medieval’ and ‘post-medieval’ have been avoided in order that it might be possible to apply the same vocabulary and encoding practice to the task of cataloguing early modern manuscripts.

<extent> [...] <seg type="leaf">
  <measure quantity="2type="laterEndleaf">ii</measure> + <measure quantity="1type="endleaf">1</measure> + <measure quantity="320type="leaf">320</measure> + <measure quantity="2type="laterEndleaf">ii</measure>
 </seg>
</extent>
N.B. Note for retroconversion: catalogues do not always make it possible to distinguish endleaves from leaves. In particular, the Bodleian’s Summary Catalogue uses formulae such as “ii + 73”, where the front endleaves are enumerated (but modern / original leaves are not distinguished), but any rear endleaves are included in with the main block. In such cases mark up as follows:
<extent>
 <num type="endleafvalue="2">ii</num> + <num type="leafvalue="73">73</num>
</extent>
1.6.4.2.1.3 Leaf dimensions

Use the tag dimensions to encode measurements of the leaves and the attribute type to indicate what is being measured. The following values of type may be used:

  • leaf = one or more leaves
  • roll = the total dimensions of a series of sheets stitched together
  • membrane = a single sheet within a roll
  • fragment = a remnant of a manuscript (potentially of various kinds and not necessarily in its original form)
  • cutting = a single portion of a leaf, removed from a manuscript

Round measurements to the nearest 5mm - except for single-sheet documents or fragments.

Use the attribute unit to specify the measurement system. Dimensions should be measured in mm. when cataloguing afresh. For retroconversion, follow whichever system the catalogue has used. Suggested values of unit:

  • mm
  • cm
  • inch

The quantity attribute should be used to provide a machine-readable form of the measurement.

For a range of measurement (typically greater variation than 10mm between the leaves), use min and max:
<dimensions type="fragmentunit="mm">
 <height quantity="176">176</height>
 <width quantity="125">125</width>
</dimensions>
<dimensions type="leafunit="mm">
 <height max="315min="290">290-315</height>
 <width max="180min="160">160-180</width>
</dimensions>

The unit of measurement (mm., etc.) should not be expressed in prose but will be generated by the XSLT transformation.

In retroconversion, if the source catalogue uses "c.", the precision attribute should be used. (The default value of precision is assumed to be high.)
<dimensions type="leafunit="mm">
 <height max="315min="290"
  precision="medium">
c.
   290</height>
 <width max="180min="160"
  precision="medium">
c.
   160</width>
</dimensions>
If there is evidence of cropping (e.g. loss of text in the margins), record this using the attribute cert with the value low
<dimensions type="leafunit="mm">
 <height cert="lowquantity="290">290</height>
 <width quantity="160">160</width>
</dimensions>
<note>Severely cropped in the upper
margin.</note>

extent will not presently accommodate locus. For manuscripts that are not composite, but which nonetheless contain sections (perhaps, but not necessarily a whole quire or quires) with dimensions different to others of the volume, it is not currently possible to provide separate measurements that are distinguished by folio range. These details may be recorded in a note.

For rolls, provide both the dimensions of the roll as a whole, followed by those of the membranes.
<dimensions type="rollunit="mm">
 <height quantity="4425">4425</height>
 <width quantity="290">290</width>
</dimensions>
<dimensions type="membraneunit="mm">
 <height max="255min="220">220-255</height>
 <width quantity="290">290</width>
</dimensions>
Since the dimensions of fragments or cuttings could interfere with quantitative analyses of leaf dimensions, it is necessary to define them separately using the values fragment or cutting(see objectType for definitions of these terms). Regardless of what the fragment comprises, measurements of its total dimensions should be given, to the millimetre.
<dimensions type="fragmentunit="mm">
 <height quantity="172">172</height>
 <width quantity="93">93</width>
</dimensions>
It may be possible, in some instances, to provide or infer the original dimensions of a leaf from what survives in fragmentary form. e.g. a bifolium may have been flattened to form an endleaf but was not trimmed in the process; e.g. a fragment of papyrus may contain text on the recto and verso sufficient to calculate an approximate number of lines and original size of the leaf. Use cert to indicate where such inferences have been made, adding within note an explanation of the evidence.
<dimensions type="fragmentunit="mm">
 <height quantity="183">183</height>
 <width quantity="179">179</width>
</dimensions>
<dimensions type="leafunit="mm">
 <height cert="highquantity="179">179</height>
 <width cert="highquantity="106">106</width>
</dimensions>
<note>The fragment comprises a flattened bifolium,
trimmed along its original left-hand edge and
rotated 45 degrees anti-clockwise and inserted into
the volume as a pastedown. The right-hand edge
appears to have been left untrimmed. </note>
<dimensions type="fragmentunit="mm">
 <height quantity="81">81</height>
 <width quantity="48">48</width>
</dimensions>
<dimensions type="leafunit="mm">
 <height cert="lowquantity="240">240</height>
 <width cert="lowquantity="140">140</width>
</dimensions>
<note>The dimensions of the original leaf have been
inferred from the amount of text remaining on the
recto and verso and the likely space required to
copy the intervening text between the end of the
recto and the beginning of the verso. </note>

Measurements of the ruled and/or written spaces is often best given under layout. However, it is recognised that in printed catalogues, these measurements usually follow immediately on from measurements of leaf size (usually in brackets). In order to accommodate the continuation of this practice, and assist in retroconversion, the present guide accepts that it may be desirable to give measurements of ruled and/or written spaces under extent. Follow the practices as outlined above, using the attribute type with the values ruled or written as appropriate.

Concluding examples:
<extent>
 <seg type="leaf">
  <num type="later_endleafvalue="4">iv</num> +
 <num type="leafvalue="288">288</num> + <num type="later_endleafvalue="2">ii</num>
 </seg>
 <seg type="dimensions">
  <dimensions type="leafunit="mm">
   <height quantity="350">350</height>
   <width quantity="245">245</width>
  </dimensions>
 </seg>
</extent>
<extent>
 <seg type="object">
  <objectType>Cutting</objectType>, of a large
   historiated initial. </seg>
 <seg type="leaf">
  <num type="leaf">1</num>
 </seg>
 <seg type="dimensions">
  <dimensions type="fragmentunit="mm">
   <height quantity="334">334</height>
   <width quantity="291">291</width>
  </dimensions>
  <dimensions type="leafunit="mm">
   <height cert="highquantity="680">680</height>
   <width cert="highquantity="450">450</width>
  </dimensions>
  <note>The cutting was removed from Florence,
     Bibliotheca Laurenziana, Cod. Corale 2, from which
     total leaf dimensions have been taken.</note>
 </seg>
</extent>
1.6.4.2.2 Foliation

The foliation element is used to provide information about the systems used to number the folios or pages in the manuscript. It should record where and in what medium the numbers are written, and when this was done, and the sequence of those numbers. Where multiple systems have been used these can be referred to elsewhere if xml:id attributes are used. For example:

<foliation xml:id="original">
 <p>Original foliation in red Arab numerals in the outer
   margin of each recto</p>
</foliation>
<foliation xml:id="modern">
 <p>Additional pagination in pencil in <locus from="1bto="67a">ff. 1b-67a</locus>
 </p>
</foliation>
The dating attributes notBefore, notAfter and (less probably) when may be used if desired to (note: this is a customization and not currently part of the TEI P5 standard).
<foliation notAfter="1500notBefore="1400">Fifteenth-century foliation in roman
numerals.</foliation>

The fw element can be used to describe running heads. For example:

<foliation>
 <p>
  <fw place="lefttype="pagxml:lang="bo">Has pagination
     in Tibetan</fw>
  <fw place="lefttype="sigxml:lang="bo">ཁི</fw>
 </p>
</foliation>
1.6.4.2.3 Collation

The collation formula should be given inside the formula element.

The mainStructures attribute (a customization not currently part of the TEI P5 standard) may be used to record the most frequently occuring quire structure(s). The value of the attribute should be the number of leaves in the most frequently-occuring structure(s). A single value indicates that the given quire structure occurs in approximately 80% or more of quires. Multiple values indicate that the given structures in combination account for approximately 80% or more of quires; the most frequently-occuring structure should be placed first.
<collation mainStructures="8">
 <formula>I-XXII(8),
   XXIII(3)</formula>
</collation>
<collation mainStructures="12 16">
 <formula>I(14),
   II-III(12), IV(16), V-VI(12), VII(16), VIII-XI(12),
   XII(16), XIII(12), XIV(16), XV(10), XVI(16),
   XVII(13)</formula>
</collation>
The formula element should be used for brief collation formulae. For more detailed formulae, use the list element with attribute type of value collationFormula.
<collation>
 <list>
  <item>2 modern paper endleaves</item>
  <item>1 medieval endleaf</item>
  <item>Quire 1<hi rend="superscript">6</hi> (fols
     1-6)</item>
  <item>Quire 2<hi rend="superscript">8</hi> (fols
     7-14)</item>
  <item>Quire 3<hi rend="superscript">10</hi> (fols
     15-24)</item>
  <item>Quire 4<hi rend="superscript">12</hi> (fols
     25-36)</item>
  <item>2 modern paper endleaves</item>
 </list>
</collation>
<!-- todo: this should be regarded as a temporary solution? toDO: visColl? -->

The following terminology is recommended:

Not present when a leaf has been removed or lost, without affecting the contents of the volume, but for reasons that cannot presently be established.
Excised when a leaf has clearly been cut out deliberately (esp. if blank).
Missing when a leaf has been lost, perhaps but not necessarily accidentally, causing the text or decorative scheme to become imperfect.
Cancelled when a leaf has been removed but there is no evident interruption to the text or decorative scheme (e.g. leaf with an error, removed during copying).
Inserted when an extra leaf is contemporary with the production of the manuscript (e.g. a miniature on a single leaf in a Book of Hours).
Added when an extra leaf is a later insertion.
Record quire or leaf signatures in the signatures element. Use the attribute type to distinguish leaf and quire signatures. (NB this is a customization and not currently part of the TEI standard.)
  • leaf: the description refers to leaf or bifolium signatures (usually located in the lower right-hand corner of the recto side of the leaves in the first half of a quire, usually in alphanumerical sequence).
  • quire: the descripion refers to quire signatures or numbers, usually on the verso of the last leaf of the quire, or sometimes the recto of the first leaf, which assign a sequence of numbers, letters or a combination thereof to the sequence of quires.
<signatures type="leaf">Bifolium signatures, a-k,
accompanied by Roman numerals, on Quires 1-10; none
thereafter.</signatures>
<signatures type="quire">Quires numbered 1-12 in a
sixteenth-century hand.</signatures>

Record the catchwords in the catchwords element.

For multi-part manuscripts, the collation of each part should be recorded at the level of the msPart; it may also be recorded at the level of the manuscript as a whole if this aids clarity. In retroconversion this is likely to involve reorganization of the formula.

1.6.4.2.4 Condition
This element is used to provide a brief description of the overall condition of the manuscript: detached, loose, torn, mutilated or otherwise damaged leaves; flaking ink or pigments or ‘bleed-through’; deliberate damage inflicted upon decorative elements; post-medieval ‘touching up’ of the text or decoration; damp, creasing or anything else that affects the colouration of the parchment or paper or affects the legibility of the text; weak joints, detached boards, loose headbands and other damage to bindings. It is not necessary to repeat information about excised / missing / cancelled leaves or gatherings that has already been provided under collation. If there is a large quantity of information to record, use p to separate it into paragraphs.
<condition>
 <p>Several of the miniatures have been rubbed and the
   pigments smudged (<locus from="10vto="10v">10v</locus>, <locus from="26vto="26v">26v</locus>, <locus from="30vto="30v">30v</locus>, <locus from="33vto="33v">33v</locus>, <locus from="44vto="44v">44v</locus>, <locus from="51vto="51v">51v</locus>).</p>
 <p>Pigments have also flaked away in places (<locus from="10vto="10v">10v</locus>, <locus from="59vto="51v">59v</locus>) and transferred to facing
   leaves (<locus from="44vto="45r">44v-45r</locus>).</p>
</condition>

1.6.4.3 Layout Description

The layout section (which might more fully be called ‘layout and preparation of the page’) should be used to record: written and/or ruled space (but see also under Extent); number of columns and number of written and/or ruled lines; how and according to what pattern ruling was executed; whether the writing is ‘above’ or ‘below’ top line; and evidence for pricking of the page. This section comprises one or more layout elements inside the layoutDesc element.

If desired, the seg element may be used to divide the content of a layout element, using attribute type to label the sections, suggested values ruling, pricking.

Give the number of columns and ruled lines in the layout element using the columns and ruledLines or writtenLines attribute. If the number of columns and/or written or ruled lines varies give the minimum and maximum values with whitespace in-between.

In retroconversion: if a varying number of lines and/or columns is given, but a typical number is specified, encode the typical number in the attributes.
<layout columns="2">1-10 cols. (typically 2)</layout>
Give the height and width of the writing area in mm (with 5 mm precision) in the dimensions element (type attribute with value written, preceding this with the explanatory text 'written space').
<layout columns="1writtenLines="30">30 long lines; written
space <dimensions type="writtenunit="mm">
  <height quantity="290">290</height>
  <width quantity="160">160</width>
 </dimensions>
</layout>
<layoutDesc>
 <layout columns="1ruledLines="28">28 lines ruled in pale
   brown ink, with single vertical bounding lines,
   extending the full height of the page, ruled on the
   flesh side of the leaves with an instrument which
   produced a scored line, but also often left a brown
   'crayon' trace. <seg type="pricking">
   <hi rend="smallcaps">PRICKINGS</hi> are often visible
     in the upper and lower margins, and in the outer
     margin c.7 mm. below the bottom ruled
     line.</seg>
 </layout>
</layoutDesc>

In most descriptions, you need only provide a count of the number of written lines. If there is a discernible difference between the number of lines ruled and the number of lines written, use both ruledLines and writtenLines in order to differentiate.

There is as yet no straightforward means of recording the varying dimensions of columns and intercolumnar margins for the more complex, multi-column layouts such as those found in glossed books. Give a prose description instead.

Record the written (and/or ruled) space in the dimensions element with type of written/ruled as appropriate.

The description of the ruling type may be according to: a printed repertory (use the standard markup for repertoria); a verbal description; the formula established by D. Muzerelle, De re rigatoria [http://www.palaeographia.org/muzerelle/index.htm]. In the latter case the formula should be enclosed in a formula element with attribute notation of value Muzerelle

<layoutDesc>
 <layout columns="2writtenLines="24 52">
  <locus from="29rscheme="foliosto="30v">Fols.
     29r-30v</locus>: written space <dimensions type="written">
   <height quantity="165unit="mm">165</height>
   <width quantity="115unit="mm">115</width>
  </dimensions>
  <note>Main text always 24 lines per page. In the
     commentary surrounding the main text there around
     twice as many lines per page.</note>
 </layout>
</layoutDesc>
<layout columns="1"
 rulingMedium="leadpointtopLine="abovewrittenLines="25">
25 long lines. <seg type="pricking">Pricked in the outer margins.</seg> Ruled in leadpoint;
ruling often very faint, with double vertical bounding lines
extending the full height of the page, and the first, third,
twenty-third and twenty-fifth horizontal lines extending the
full width of the page (Muzerelle, <ref target="http://www.palaeographia.org/muzerelle/mastara.htm">Mastara</ref>, formula <formula notation="Muzerelle">2-2/0/101-101/J</formula>). Written above top line.
Written space <dimensions type="writtenunit="mm">
  <height max="125min="115">c. 115-125</height>
  <width max="85min="75">75-85</width>
 </dimensions>
</layout>

If the layout varies between different sections of the manuscript, use separate layout elements to record this.

1.6.4.3.1 Complex or unusual layouts

Complex or unusual layouts may be encoded using the type and subtype attributes on layout. (Note that this customization is not currently part of the TEI P5 standard.) For example:

To encode the layout of glossed manuscripts in textus inclusus format.
<layout columns="2type="text"
 writtenLines="34 35">
Text in 2 cols. of c. 34/35 lines, main text block <dimensions type="writtenunit="mm">
  <height>162</height>
  <width>96</width>
 </dimensions>
</layout>
<layout columns="2type="gloss"
 writtenLines="66 76">
Gloss in 2 cols. of c. 66-76 lines, text block including gloss <dimensions type="writtenunit="mm">
  <height>265</height>
  <width>166</width>
 </dimensions>
</layout>
1.6.4.3.2 Layout of fragments

The type and subtype attributes should be used to encode the layout of fragments if the written area of a page is not fully preserved.

To encode the existing form of a fragment, use type with fragment

If neither the full height or width of the written space is preserved:
<layout columns="1type="fragment"
 writtenLines="12">
Lower outer quarter of the leaf: 1 col., 12 lines.</layout>
If the full height of the written area is preserved:
<layout columns="1subtype="fullHeight"
 type="fragmentwrittenLines="55">
(at least) 1 col., 55 lines</layout>
If the full width of the written area is preserved:
<layout columns="2subtype="fullWidth"
 type="fragmentwrittenLines="46">
2 cols., at least 46 lines</layout>

For processing purposes this encoding should be interpreted as, respectively: at least one column, at least 12 lines; at least one column, 55 lines; two columns, at least 46 lines.

If the original layout can be reconstructed with some confidence, use type with reconstruction and a relevant value for the cert attribute.
<layout cert="highcolumns="2"
 type="reconstructionwrittenLines="44">
2 cols., originally 44 lines (42 lines extant at fullest extent, one fragmentary line at the bottom, one line missing at the top), written space <dimensions type="writtenunit="mm">
  <height precision="lowquantity="240">c. 240</height>
  <width precision="lowquantity="150">c. 150</width>
 </dimensions>
</layout>

1.6.4.4 Description of Hands

Each distinct hand and/or script in the codicological unit should be described in a separate handNote element in the handDesc element. The handDesc element itself has an attribute hands which can be used to record the number of hands identified. This is optional but recommended. The value of the attribute should be the number of hands involved in the original production of the manuscripts and should not include later additions or annotations.

The handNote element may have an xml:id attribute with the values hand-1, hand-2 etc, numbered in the order of appearance in the manuscript. If the same hand occurs in another unit the attribute sameAs may be used with a reference to the xml:id of that handNote.

The folios where the hand occurs should be specified and may be encoded using the locus or locusGrp element. Where the scribe is identifiable, either from the writing or a subscription, give the name in a persName element using the key attribute pointing to the persons authority file, and the role attribute with value scr.

The scope attribute can be used to indicate the extent of the hand's appearance in the manuscript. Its values can be one of:

  • sole
  • major
  • minor

The script attribute may be used to provide a high-level classification of the script. Suggested values in Western manuscripts are:

  • capitalsSquare
  • capitalsRustic
  • uncial
  • halfUncial
  • minusculeInsular
  • minusculeVernacular (use for English vernacular minuscule / Anglo-Saxon minuscule)
  • minusculeCaroline (use for both English and continental variants of the script)
  • minuscule (other forms of minuscule: Beneventan, Luxeuil, etc.)
  • protogothic (‘praegothica’)
  • textualisNorthern
  • textualisSouthern
  • semitextualis
  • cursivaAntiquior (‘anglicana’, ‘anglicana formata‘, etc.)
  • cursiva (‘cancelleresca’, ‘bastarda’, ‘lettre batarde’, ‘secretary’)
  • hybrida (‘semihybrida’, ‘loopless bastarda’, ‘fractura’, ‘mercantesca’)
  • gothicoAntiqua (‘fere-humanistica’, ‘gothico-humanistica’)
  • humanisticaTextualis
  • humanisticaSemitextualis
  • humanisticaCursiva

The classification for early scripts is based on Brown (1990) with modifications, for Gothic scripts on Derolez (2003), for humanistic scripts on Derolez (2011).

The attribute execution can be used to describe the formality of the script's execution, according to the classifications developed by Lieftinck, Gumbert, and Derolez. Note that this customization is not currently part of the TEI P5 standard.

  • formata: execution is calligraphic
  • libraria: a normal level of execution
  • currens: execution is informal

In Islamicate manuscripts suggested script values are:

  • muhaqqaq
  • rayhani
  • naskh
  • maghribi
  • bihari
  • nasta_liq
  • thuluth
  • tawqi_
  • riqa_
  • ghubar
  • ta_liq
  • diwani
  • ruq_ah
  • siyaqah
  • unknown
For further levels of classification the term element with type of script may be used.
<handDesc hands="1">
 <handNote script="cursivaAntiquior">Written in <term type="script">anglicana</term> by a single
   scribe.</handNote>
</handDesc>
Punctuation should be described in the handNote element. Use the term element with attribute type of value punctuation to mark up particular types of punctuation, if desired.
<handNote>Written in gothic <term type="script">textura
   quadrata</term>. Punctuation by <term type="punctuation">point</term> and <term type="punctuation">double
   point</term>.</handNote>

1.6.4.5 Musical Notation

Musical notation should be described in a pelement in the musicNotation element with a locus element. Multiple types of notation should appear in separate p elements.
<musicNotation>
 <p>8 long staves with square notation</p>
</musicNotation>

1.6.4.6 Description of the Decoration

The decoDesc element contains a description of the decoration in the manuscript or codicological unit, together with other ‘decorative’ aspects of the presentation of the text such as rubrication, It can only contain the elements p, summary, and decoNote.

Within the tag decoDesc, use decoNote to provide a hierarchical breakdown of the decoration in the manuscript, in the order given in the following table, with the appropriate values of type attribute.

Miniatures (or coloured drawings), listed in the following order: full-page, half-page, small, column; use for painted or tinted images, whether part of an original decorative scheme or added. miniature
Uncoloured drawings or sketches, whether part of an original decorative scheme or added. drawing
Bas-de-page scenes bas-de-page
Borders, in the following order: historiated, other; use for painted borders of any type (including for example historiated, inhabited, foliate) border
Diagram diagram
Map map
Headpiece headpiece
Canon table canonTable
Carpet page carpetPage
Historiated initials (i.e., containing an identifiable narrative scene) (Brown: historiated initial); initials, usually painted, containing identifiable persons or narrative scenes usually related to the text. histInit
decorated initials (Brown: decorated initial, anthropomorphic initial, zoomorphoric initial, gymnastic initial, inhabited initial). Other initials with significant decorative features, usually painted; includes 'arabesque' and 'silhouette' initials. decInit
coloured initials (i.e. of a single colour with no or minimal decorative features) colInit
initials with penwork flourishing (Reallexikon zur Deutschen Kunstgeschichte: fleuronné) (Brown: pen-flourished initial, littera florissa). Initials with "fine linear embellishment" (Brown) often in a contrasting colour (includes 'puzzle' initials); borders of similar embellishment. flourInit
chrysography (i.e. writing in gold) chrysography
plain initials (i.e. in the ink of the text and with no or minimal decorative features) plainInit
Line fillers lineFill
cadels cadel
instructions instructions
Spaces left for decoration unfilled
None (if an existing decoration being retro-converted specifies this) none
rubrication rubrication

In Fihrist, the following values for the type attribute should be used:

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

Artists should be identified using the persName element with role = art and key referring to the persons authority file.

<decoDesc>
 <decoNote type="miniature">
  <p>Two full-page miniatures, framed by green, blue,
     orange, ochre or pink panels linked by gold
     quadrilobes and surrounded by short black sprays
     terminating in gold disks and ivy leaves.</p>
  <p>The second miniature is signed ‘Willelmus de monte
     acuto me fecit’ by the artist <persName key="person_1234role="art">William Montague (fl.
       1390s?) (<locus from="37rto="37r">37r</locus>).</persName>
  </p>
 </decoNote>
</decoDesc>

To provide a more structured entry in the case of detailed descriptions of decoration, use the list, head, and item elements.


<!-- abbreviated from MS. Buchanan e. 10 --><decoNote type="histInit">
 <list>
  <head>Two five-line historiated initials:</head>
  <item>
   <locus from="19vto="19v">(fol. 19v)</locus>
     Obsecro te. Virgin and Child enthroned; the Virgin
     holding a red fruit(?).</item>
  <item>
   <locus from="23rto="23r">(fol. 23r)</locus> O
     intemerata. Pietà. </item>
 </list>
</decoNote>
<decoNote type="decInit">Four- or three-line initials in blue
and red, enclosing foliage, on a gold ground, at the start
of each text with a large miniature; two-line initals in
gold, on a blue and red ground with white tracery, to
psalms, capitula, lessons, etc. and the KL monograms in the
calendar; similar one-line initials to verses and other
minor divisions; similar line-fillers throughout.</decoNote>
The subjects of miniatures can be classified using the term element with attribute type of value iconography. The ref attribute can be used to point to a thesaurus, such as Iconclass.
<decoNote type="histInit">
 <list>
  <head>One six-line historiated initial: </head>
  <item>
   <locus from="49rto="49r">(fol. 49r)</locus>
     Hours of the Virgin, Lauds. <term ref="http://www.iconclass.org/rkd/73A6"
    type="iconography">
Visitation</term>. </item>
 </list>
</decoNote>

Aspects of the manuscript relating to the presentation of the text - notably rubrication - should also be included in the decoDesc element (rather than in the layout element, using decoNote with attribute type of value rubrication.

1.6.4.7 Additions

Marginalia, notes, and other additions of interest should usually be recorded in the additions element, inside one or more p or note elements. The note element can have the type and subtype attributes. Use locus to specify the location of these features.

If the language of the marginalia is significant (e.g., Latin marginalia in a Greek manuscript), the marginalia will need to be recorded as an additional text using msItem in msContents.

<msItem xml:id="MS_Auct_T_2_6-item2">
 <note subtype="glosstype="additions">Marginal and interlinear
   Latin glosses.</note>
 <textLang mainLang="la">Latin</textLang>
</msItem>

1.6.4.8 Binding Description

The binding should be described in one or more paragraphs (p) in a binding element inside the bindingDesc element. The standard dating attributes should be used on the binding element if information about the date of the binding is available.

The following order may be followed in the description:

  • covering material and coverage (full, half, quarter; textile; limp vellum; treasure)
  • chemise (alum-tawed, textile)
  • board material (wooden boards, pasteboard)
  • tooling patterns (blind, gold)
  • spine covering and tooling, incl. labels
  • metalwork fittings (plates, plaques, enamels, bosses, cornerpieces, strap and pin, clasps, chain staples).
  • inlaid/inset plaques
  • labels (esp. horn-plaques)

Key elements of the description may be marked with the term with relevant type attribute and with attribute ref referring to the appropriate URI in the Ligatus thesaurus.

Give the height, width and depth of the binding may be given in mm (with 5 mm precision) in the dimensions element (type attribute with value binding).

A description of decorative features on the binding can be recorded in one or more decoNote elements (note that this needs to be outside the p element as a child of binding)

Use the condition element to record repairs to the binding, such as rebacking.

Fore-edge painting or decoration should be described inside a decoDesc element, in a decoNote element with attribute type of value foreedge.

Bookmarks and other page markers should be described in a separate paragraph in the binding section, using where possible the vocabulary of the Ligatus thesaurus, and linking to that vocabulary using the term element with attribute type of value bookmark and relevant ref attribute.

<bindingDesc>
 <binding notAfter="1700notBefore="1600">
  <p>Light brown <term ref="http://w3id.org/lob/concept/1238"
    type="material">
calfskin</term> over paste-laminate boards,
     leather label on spine with title and shelfmark
     tooled in gold, gauffered fore-edges. 17th
     century.</p>
  <condition>Rebacked.</condition>
  <p>
   <term ref="http://www.ligatus.org.uk/lob/concept/2945"
    type="bookmark">
Leaf tab markers</term>.</p>
 </binding>
</bindingDesc>

Evidence of former bindings, or the reuse of earlier binding material in a modern binding, should be recorded in a separate binding element.

Note that all the above may require restructuring of an original description during retroconversion.

<bindingDesc>
 <binding notAfter="1900notBefore="1600">
  <p>Sewing not visible; tightly rebound between
     19th-century pasteboards, reusing earlier panels
     (see below); the centre of each cover inlaid with a
     17th-century oval medallion of red leather tooled in
     gilt (perhaps replacing the identifying mark of a
     previous owner); the spine similarly tooled, without
     raised bands or title-piece (similar in design to
  <hi rend="italic">ibid</hi>. pl. XIXa); coloured
     endbands; the edges of the leaves and boards gilt.
     Boxed.</p>
 </binding>
 <binding notAfter="1590notBefore="1580">
  <p>The binding re-uses panels of 16th-century brown
     leather with gilt tooling <foreign rend="italic">à
       la fanfare</foreign>, Paris c. 1580-90, in the
     style associated with Clovis Eve (of the bindings
     ill. in Hobson, <title>Les reliures à la
       fanfare</title>, the boards are closest in general
     design to pl. XXI b).</p>
 </binding>
</bindingDesc>

1.6.4.9 Seals

The sealDesc element supplies information about the seals attached to documents. It can either contain a text description in p tags, or any number of seal elements. These can be numbered using n attributes.

The seal impression of stamps of ownership may be described in decoDesc, in stylistic and decorative terms, or in provenance as regards its textual content.

1.6.4.10 Accompanying material

The accMat element may be used for brief descpritions of endleaves, waste leaves and similar material that are not part of the ‘original’ codex but were supplied during a binding process. If a detailed codicological description is required, use msPart

Use p to split up descriptions of multiple materials, and locus to identifying their locations.

1.6.5 History

The history element should include information about the origin, provenance and acquisition of the manuscript.

1.6.5.1 Origin

In the origin element specify date (origDate) and place (origPlace) (if known) of the manuscript's production. If not known, state this in a p element. Do not enclose a statement such as "No date" or "n.d." with origDate tags.

1.6.5.1.1 origDate

Dating attributes from the set notBefore, notAfter, from, to and when MUST be used for origDate

from and to denote a known period of writing, presumed to be more or less continuous, beginning at one date and ending at another. notBefore and notAfter denote the terminus a quo and terminus ad quem within which the writing is believed to have occured.

The values of those attributes are a date, starting with the year, then the month, then the day, separated by hyphens (but most often just a year, always expressed using four-digits) must be in the Gregorian calendar. the calendar attribute records the calendar system used by the expression of the date in the text enclosed by the origDate tags. The text is for display, the attributes are the machine-readable interpretation. For example:

<origDate calendar="#Hijri-qamari"
 when="1684">
1096
AH</origDate>

In retroconversion, the values given to the element and its attributes should reflect the conventions of the particular catalogue as expressed in the catalogue or, if necessary, as inferred by the encoder. (If inferred, a note to this effect may be added in encodingDesc.)

<origDate notAfter="1025notBefore="1000">s. xi<hi rend="superscript">in</hi>
</origDate>

Values used in the Bodleian medieval catalogue (intended to capture the usage of the Summary Catalogue and Paecht and Alexander) are as follows:

Early 14th century 1300-1310
Mid 14th century 1340-1360
Late 14th century 1390-1400
14th century, first quarter 1300-1325

Etc.

Values of dating attributes should be inclusive, i.e. 1000-1050, not 1001-1050 or 1000-1049.

The attribute evidence MAY be used to indicate the evidence for dating and localization. It is assumed that this will usually be equivalent to conjecture. If there is reasonable certainty about the dating or localization (the manuscript is 'dated or datable') this SHOULD be indicated using the attribute cert with value high, and the nature of the evidence may be specified with the evidence attribute.

In retroconversion, authoritative sources may differ regarding the date (or origin) of a manuscript. This can also be recorded using multiple origDate elements. (The resp attribute may be used on the element to indicate responsibility in a machine-readable way).
<origDate calendar="Gregorian"
 notAfter="1300notBefore="1290">
13th century, end (Hutter)</origDate>
or
<origDate calendar="Gregorian"
 notAfter="1325notBefore="1300">
14th century, first quarter
(Palau)</origDate>

For manuscripts with significant later additions, textual or decorative, use additional origDate elements with type of additions

<origDate calendar="Gregorian"
 notAfter="1225notBefore="1200">
13th century, first quarter</origDate>;

<origDate calendar="Gregorian"
 notAfter="1500notBefore="1400type="additions">
additions, 15th
century</origDate>
<origDate calendar="Gregoriancert="high"
 when="1488">
1488
(fols. 126-208)</origDate>;
<origDate calendar="Gregoriancert="high"
 notAfter="1488notBefore="1464">
1464 × 1488 (fols. 1-125v)</origDate>
1.6.5.1.2 origPlace

The content of origPlace should where possible be structured in the order (where relevant), country, settlement, institution. These should be marked up using the country, settlement, and <org> elements, which MUST have attributes key linking to the places authority file. Or, in catalogues such as Fihrist which have a subjects authority file instead of a places one, the key attribute should be "subject_" followed by the Library of Congress Name Authority identifier (e.g. "subject_n12345678").

There MUST be a country or country-like entity (see below), inside a country tag, if the origPlace element is used.

In Western manuscripts, countries of origin are typically expressed with reference to modern countries with some exceptions. Examples: England, France, Spain, Italy, Germany, Austria, Switzerland, but Bohemia, Dalmatia, Serbia, Flanders.

For manuscripts with significant later additions, textual or decorative, use additional origPlace elements with type of additions
<origPlace>
 <country key="place_1000070">French</country>, <region key="place_7024267">Brittany</region>
</origPlace>
<origPlace type="additions">additions, <country key="place_7002445">England</country>
</origPlace>
For manuscripts produced in more than one place (or, where there is more than one potential place of origin), use multiple origPlace elements, with the cert attribute if necessary.
<origPlace cert="low">
 <country key="place_1000080">Italian (?)</country>
</origPlace> or
<origPlace cert="low">
 <country key="place_1000070">French</country>,
<region>South</region> (?)
</origPlace>

1.6.5.2 Provenance

Record the different stages in the provenance in one or more provenance elements.

There are different conventions for the presentation of provenance evidence. Recommended best practice in these guidelines (which may involve some restructuring of material in the case of retroconversion) is that where possible each provenance event should occur in its own provenance element, which should have relevant dating attributes (when, notBefore, etc.). (They may alternatively contain date elements with those attributes.) As elsewhere, from and to denote a known period, presumed to be more or less continuous, beginning at one date and ending at another. notBefore and notAfter denote the terminus a quo and terminus ad quem within which the writing is believed to have occured. when denotes a single event (such as a dated signature or the donation of an item to a library). People involved in the transfer of ownership should be marked up with persName tags, with a role attribute (a Library of Congress relator code, usually "fmo" for former owner).

Pressmarks and shelfmarks should be recorded in a q element with attribute type, value pressmark; see 1.3.10 Quotations from the manuscript. It is not necesary to mark up pressmarks and shelfmarks which are already recorded as manuscript identifiers.
<acquisition notAfter="1468">At the head of f. iii<hi rend="superscript">v</hi> is ‘Liber domus scolarium de
Merton ex dono magistro <persName key="person_2899role="fmo dnr">Hamondi Haydok</persName>
incathenandus in libraria anno Domini m<hi rend="superscript">mo</hi>cccc<hi rend="superscript">o</hi>lxviii<hi rend="superscript">o</hi>’, in the same
hand as Wyght’s <foreign>ex dono</foreign> in MS 38. For
Hammond Haydok, see MS 16. On the front pastedown is a brief
table of contents, s. xvii, and <q type="pressmark">N. 3.
   13. Art:</q>, canc. and replaced with ‘A. 1. 10 (XXXIX)’
in red. The College bookplate. At the head of f. i is <q>M.
   A. 2. 5</q>, s. xvii. ‘13’ is inked on the
foredge.</acquisition>

1.6.5.3 Acquisition

The acquisition element should describe the last stage of the manuscript's history, i.e. how it was acquired by its present owners. It SHOULD have relevant dating attributes. Because the present owner, locaton etc. of the manuscript are recorded elsewhere in the manuscript description, it is NOT necessary to encode them using orgName or persName elements.

Note the usage of the different dating attributes in the following example.

<provenance notAfter="1833">
 <persName key="person_2854role="fmo">William Wilson</persName>, F.S.A.
(-1832?), of the Minories, his sale, Christie's, 31 Jan.-1
Feb. 1833, lot 56 on 1 Feb.; bought by Thorpe for £53.
11s.
</provenance>
<provenance from="1833to="1834">Purchased from Thorpe by
<persName key="person_69848690role="fmo">Douce</persName>, Feb. 1833.</provenance>
<acquisition when="1834">Bequeathed by Douce to the Bodleian in
1834.</acquisition>

The acquisition element is also the place to record any funding bodies which contributed to the cost of purchasing the manuscript. Each should be tagged as orgName elements with a role attribute of either "spn" or "fnd". The websites of sponsors, and their logos, can be included. For example:

<acquisition> Purchased with the support of
<orgName role="spn">
  <ref target="https://visit.bodleian.ox.ac.uk/friends-of-the-bodleian">Friends of the Bodleian</ref>
 </orgName>,
and the
<orgName role="spn">
  <ref target="https://www.vam.ac.uk/purchasegrantfund">V&amp;A Purchase Grant Fund</ref>
  <graphic url="https://www.fihrist.org.uk/images/logos/vampgf250.png"/>
 </orgName>, and a private donor.
</acquisition>

Ideally the @url attribute of the graphic element should point to an image hosted by the funding organization. The graphic element cannot be a child of the funder element, but must be enclosed in a persName or orgName element.

Contributions to the cost of cataloguing the manuscript should be recorded in the Title Statement.

1.6.6 Additional

The additional element is used to provide: information about the source of the description; information about the availability and custodial history of the manuscript; information about surrogates; bibliography; and links to online resources.

1.6.6.1 Record source and history

The source element, contained in recordHist, provides a prose description of the source(s) from which the description has been derived; this information will overlap with the information in respStmt. It may contain listBibl and bibl elements.

<adminInfo>
 <recordHist>
  <source>Description adapted (2018) from the
     following sources: <listBibl>
    <bibl>
     <title>The Douce Legacy</title> (1984), no.
         244</bibl>
    <bibl>Pächt and Alexander</bibl>
    <bibl>S. J. P. Van Dijk, <title>Handlist of the
           Latin Liturgical Manuscripts in the Bodleian
           Library Oxford : Vol. 2: Office Books</title>
         (typescript, 1957)</bibl>
   </listBibl> Additional description of content and
     decoration by Matthew Holford, March 2018.
     Previously described in the Summary Catalogue. <listBibl>
    <bibl facs="aaz0626.giftype="SC">Summary
         Catalogue, vol. 4, p. 607</bibl>
    <bibl facs="aaz0627.giftype="SC">Summary
         Catalogue, vol. 4, p. 608</bibl>
   </listBibl>
  </source>
 </recordHist>
</adminInfo>

1.6.6.2 Availability

The availability element can be used to supply information about the availability of a manuscript, using the status attribute. Valid values for status are free, unknown, restricted, offsite, exhibition, printcat, none. It may also contain information about the images or text, such as any restrictions on their use or distribution, their copyright status, etc.

1.6.6.3 Custodial History

The custodialHist element can be used to describe a manuscript's custodial history (e.g. conservation, exhibitions) either as prose tagged with p elements, or as a series of custodial events, using the custEvent element with attributes type, when, etc.

The custEvent element is currently used at the Bodleian to record barcoding of manuscripts:

<custodialHist>
 <custEvent type="barcode">Barcode: <idno type="barcode">603303329</idno>
 </custEvent>
</custodialHist>

1.6.6.4 Surrogates

The surrogates element, which follows recordHist, is used to link to digital or other facsimiles where these are hosted independently from the catalogue. The structure of a typical entry is shown below. The subtype attribute on the bibl element has the values full, where a manuscript has been digitized in full, or partial, where only selected items are available.

<surrogates>
 <listBibl>
  <bibl subtype="full"
   type="digital-facsimile">

   <ref target="https://digital.bodleian.ox.ac.uk/objects/34a6037b-12e8-4b12-8920-26c33914fe0e">
    <title>Digital Bodleian</title>
   </ref>
   <note>(full digital facsimile)</note>
  </bibl>
 </listBibl>
</surrogates>

This section should also be used to record the availability of microfilms.

<surrogates>
 <bibl subtype="partial"
  type="digital-facsimile">

  <ref target="https://digital.bodleian.ox.ac.uk/objects/4e3e7d80-c49a-40bd-9aff-a6452f196fa1/">
   <title>Digital Bodleian</title>
  </ref>
  <note>(3 images from 35mm slides)</note>
 </bibl>
 <bibl subtype="fulltype="microfilm">Microfilm available in the open shelf collections in the Weston Library (R. Films 101)</bibl>
</surrogates>

1.6.6.5 Bibliography

The bibliography of works referring to the manuscript should be recorded in the additional element in a listBibl element. In the Bodleian medieval catalogue only major printed descriptions or reproductions of the manuscript are listed here; other items should be recorded in the Zotero bibliography. The works should be listed in a chronological order, with the most recent item first.

This section is also used to provide links to online resources such as Pinakes, Trismegistos, JONAS etc. Online resources are placed in a separate listBibl element with the heading head 'Online resources:'.

<additional>
 <listBibl type="WRAPPER">
  <listBibl type="PRINT">
   <head>Printed descriptions:</head>
   <bibl>
    <title>The Douce Legacy</title> (1984), no.
       65</bibl>
   <bibl>A. G. Watson, <title>Catalogue of Dated and
         Datable Manuscripts c.435-1600 in Oxford
         Libraries</title> (Oxford, 1984), no. 464</bibl>
   <bibl>Otto Pächt and J. J. G. Alexander,
   <title>Illuminated Manuscripts in the Bodleian
         Library Oxford</title>, III (1973), no. 469</bibl>
  </listBibl>
  <listBibl type="INTERNET">
   <head>Online resources:</head>
   <bibl>
    <ref target="http://jonas.irht.cnrs.fr/manuscrit/40258">
     <title>JONAS: Répertoire des textes et des
           manuscrits médiévaux d'oc et
           d'oïl</title>
    </ref>
   </bibl>
  </listBibl>
 </listBibl>
</additional>
  • additional (additional) groups additional information, combining bibliographic information about a manuscript or other object, or surrogate copies of it, with curatorial or administrative information.
  • recordHist (recorded history) provides information about the source and revision status of the parent manuscript or object description itself.
  • source (source) describes the original source for the information contained with a manuscript or object description.
  • 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.
  • custodialHist (custodial history) contains a description of a manuscript or other object's custodial history, either as running prose or as a series of dated custodial events.
  • surrogates (surrogates) contains information about any representations of the manuscript or other object being described which may exist in the holding institution or elsewhere.
  • listBibl (citation list) contains a list of bibliographic citations of any kind.
  • bibl (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.

1.6.7 Multi-part, composite and similar units.

For multi-part manuscripts or in other cases where a ‘syntactical’ description (Andrist et al., 2013) is required, the msPart element should be used. These guidelines recommend the use of msPart for:

  • manuscripts originally separate, bound together at later dates
  • manuscripts with added codicological units
  • palimpsest manuscripts
  • re-used papyrus
  • manuscripts with replacement leaves
  • description of endleaves, in cases where a detailed description is required (for short descriptions of endleaves, use accMat)

The definition and understanding of composite manuscripts varies between different codicological traditions. The Western tradition has typically understood a composite manuscript to be composed of more than one combined production/usage unit. (For this terminology see Kwakkel 2002). Manuscripts with separate-but-contemporaneous production units, that were not also at some point separate usage units, are not typically catalogued as composite, although the different production units are usually noted in the description. (For a recent example, see Hanna and Rundle, Cat. Christ Church MSS., MS. 92.)

The use of msPart is not recommended for describing added text or decoration where this has been added on the original codicological unit as a supplement to existing text (rather than, as with a palimpsest, as a replacement for that text). In those cases, use of multiple origDate and/or origPlace elements is recommended; see above.

For composite manuscripts, each codicological unit should be described in a separate msPart element using the following elements:

  • msIdentifier (manuscript identifier) contains the information required to identify the manuscript or similar object being described.
  • msContents (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items.
  • physDesc (physical description) contains a full physical description of a manuscript, manuscript part, or other object optionally subdivided using more specialized elements from the model.physDescPart class.
  • history (history) groups elements describing the full history of a manuscript, manuscript part, or other object.

Endleaves should be described using one or more msPart elements following the msDesc element which contains the description of the main manuscript.

The element msFrag should not be used for this purpose. This element is used for describing manuscripts that have been 'virtually reconstructed' and is not currently used in this project.

Each codicological unit should be labelled using arabic numerals (or according to the convention of the existing catalogue in the case of retroconversion) inside the idno in the altIdentifier element inside the msIdentifier element. The folios comprising the unit should be given.
<msPart>
 <msIdentifier>
  <altIdentifier>
   <idno type="part">Manuscript I = fols 1-134</idno>
  </altIdentifier>
 </msIdentifier>
</msPart>
The data structure of the msPart element assumes that codicological units follow one another sequentially in the manuscript, which (in the case of Western manuscripts) is often but not universally true. In cases where one unit is inserted in the middle of another, the description should be organized to deal with each part in sequential order.
<msPart>
 <msIdentifier>
  <altIdentifier>
   <idno>Merton College MS. 13 - Part I (fols. 3-13,
       198-243)</idno>
  </altIdentifier>
 </msIdentifier>
 <msContents>
  <textLang mainLang="la">Latin</textLang>
  <msItem n="1">
   <locus>(fols. 3-13v)</locus>
   <title type="desc">Draft sermons</title>
<!-- ... -->
  </msItem>
  <msItem>
   <note>For items 2, 51-4 see Part II.</note>
   <note>For items 3-50 see Part III.</note>
  </msItem>
  <msItem n="55">
   <locus>(fols. 198-208v)</locus>
   <title type="desc">Eight sermons on Ioh. 17: 1-26,
       extracted from <persName key="person_66806872"
     role="aut">
Augustine</persName>, <title key="work_822">Tractatus in Iohannis
         Euang.</title>, 104. 2 – 111. 6</title>
  </msItem>
<!-- ... -->
 </msContents>
</msPart>

1.6.7.1 Endleaf

Example: MS. Auct. D. 2. 14 (abbreviated)

<msDesc xml:id="MS_Auct_D_2_14"
 xml:lang="en">

 <msIdentifier>
<!-- ... -->
 </msIdentifier>
 <head>Gospels; Italy, 7th century</head>
<!-- ... -->
 <msContents>
<!-- ... -->
 </msContents>
 <physDesc>
<!-- ... -->
 </physDesc>
 <history>
<!-- ... -->
 </history>
 <additional>
<!-- ... -->
 </additional>
 <msPart type="endleaf">
  <msIdentifier>
   <altIdentifier>
    <idno type="part">MS. Auct. D. 2. 14 - endleaf,
         fol. 173</idno>
   </altIdentifier>
  </msIdentifier>
  <msContents>
   <msItem>
    <locus>(fol. 173r)</locus>
    <title type="desc">Booklist and list of
         names</title>
    <note>N. R. Ker, <title>Catalogue of Manuscripts
           Containing Anglo-Saxon</title> (1957), p. 350 (no.
         290).</note>
    <textLang mainLang="ang">Old English</textLang>
   </msItem>
   <msItem>
    <locus>(fol. 173v)</locus>
    <title>Ad introitum porte</title>
    <textLang mainLang="la">Latin</textLang>
   </msItem>
  </msContents>
  <history>
   <origin>
    <origPlace>
     <country key="place_7002445">England</country>, <orgName key="org_150107857">Bury St Edmunds</orgName>
         (?)</origPlace>
    <origDate calendar="Gregorian"
     notAfter="1200notBefore="1150">
11th century,
         second half</origDate>
   </origin>
   <provenance>'Bealdewuine abb.', fol. 173r, probably
       Baldwin, abbot of Bury St Edmunds (d.
       1098).</provenance>
  </history>
 </msPart>
</msDesc>

1.6.7.2 Manuscripts with replacement leaves

Example: MS. Holkham Gr. 15 (simplified)

<msDesc>
<!-- ... -->
 <msContents>
  <textLang mainLang="grc">Greek</textLang>
  <msItem xml:id="MS_Holkham_Gr_15-item1">
   <locus>(fols. 1r-202v)</locus>
   <title key="work_13296type="desc">Menologion for
       September</title>
<!-- ... -->
  </msItem>
 </msContents>
 <physDesc>
  <p>11th century core with 14th or 15th century
     replacement leaves.</p>
  <objectDesc form="codex">
   <supportDesc>
    <extent> ii + 204<dimensions type="leafunit="mm">
      <height>350</height>
      <width>250</width>
     </dimensions>
    </extent>
   </supportDesc>
   <layoutDesc>
    <layout columns="2ruledLines="33">Lake II, 34c;
         written in two columns, 33 lines per
         column.</layout>
   </layoutDesc>
  </objectDesc>
  <decoDesc>
   <decoNote>fol. 1, Sketch with an image of St
       Theodora. Various decorated headpieces preceding
       each Vita. See Hutter III.1, pp. 59-60.</decoNote>
  </decoDesc>
  <additions>fol. 55r: ζήτει εἰς τὰς ὀκτὼ τοῦ μηνὸς εἰς
     τὴν ἀρχὴν τοῦ βιβλήου ἀναγνώσματα δ<ex>ύ</ex>ο/ εἰς
     τὸ σωσίκοσμ<ex>ον</ex> γενέθλον τῆς
     ὑπερ<ex>αγίας</ex> ἀμώμου δεσποίνης/ ἡμῶν
     Θεοτόκου· Ἀνδρέου κρίτης τοῦ ἱεροσολυμίτου :
     -</additions>
  <bindingDesc>
   <binding>
    <p>Holkham binding of black leather, with Coke
         family ostrich crest in gilt in the centre of the
         upper cover; Date: early nineteenth century.
         Rebound by <persName key="person_707role="bnd">John Jones of Liverpool</persName> (worked for
         Holkham 1816-1823). SPINE: lettered in gilt:
         SYMEONIS| METAPHRASTAE|VITAE| S.S. MARTYRUM| G.R.|
         M.S.| SAEC. XII|–| SEP.| </p>
   </binding>
  </bindingDesc>
 </physDesc>
<!-- ... -->
 <msPart>
  <msIdentifier>
   <altIdentifier>
    <idno>Codicological Unit 1 (fols. 8r-180v)</idno>
   </altIdentifier>
  </msIdentifier>
  <physDesc>
   <objectDesc form="codex">
    <supportDesc material="perg">
     <support> Parchment</support>
    </supportDesc>
   </objectDesc>
  </physDesc>
  <history>
   <origin>
    <origDate notAfter="1100"
     notBefore="1050">
11th
         century, second half</origDate>
   </origin>
  </history>
 </msPart>
 <msPart>
  <msIdentifier>
   <altIdentifier>
    <idno>Codicological Unit 2 (fols. 1r-7r,
         181r-202v)</idno>
   </altIdentifier>
  </msIdentifier>
  <physDesc>
   <objectDesc form="codex">
    <supportDesc material="chart">
     <support> Paper; replacement leaves</support>
    </supportDesc>
   </objectDesc>
  </physDesc>
  <history>
   <origin>
    <origDate notAfter="1500"
     notBefore="1300">
14th-15th century</origDate>
   </origin>
  </history>
 </msPart>
</msDesc>

1.6.8 Appendix of examples

1.6.8.1 Book of Hours

Divide the contents: Calendar; Suffrages (each saint listed as a separate msItem); Hours of the Virgin; Hours of the Passion; and so on – and then, using decimal point numbering for msItem, subdivide each of the Hours into the canonical hours, where present (Matins, Lauds, Prime, and so on).

<msItem n="12">
 <locus from="34rto="58v">34r-58v</locus>
 <title xml:lang="en">Hours of the Virgin</title>
 <textLang mainLang="lat">Latin</textLang>
 <msItem n="12.1">
  <locus from="34rto="37r">34r-37r</locus>
  <title xml:lang="en">Matins</title>
 </msItem>
</msItem>
<!-- etc. -->

1.6.8.2 Bible

Divide the contents: Prologue to the Vulgate; Old Testament; New Testament; ‘Interpretationes nominum hebraicorum’; and so on - and then, using decimal point numbering for msItem, subdivide each one where appropriate, distinguishing between the biblical text and their prologues.

<msItem n="1">
 <locus from="2rto="4v">2r-4v</locus>
 <title xml:lang="en">Prologue to the Vulgate</title>
 <author> [...] </author>
 <msItem n="1.1">
  <locus from="2rto="4r">2r-4r</locus>
  <title xml:lang="la">Epistula ad Paulinum
     presbyterum</title>
  <rubric>
   <locus from="1rto="1r">1r</locus>Incipit prologus
     Ieromini super totam bibliam </rubric>
  <incipit xml:lang="la">
   <locus from="1rto="1r">1r</locus>Frater Ambrosius
     tua mihi munuscula preferens </incipit>
  <explicit xml:lang="la">
   <locus from="4rto="4r">4r</locus>facile contempnit
     omnia qui se semper cogitat esse moriturum </explicit>
  <note>PL 23, 540-549; Stegmüller 284, 3306; CPL
     620</note>
  <note>CSEL 54 (1910), 442-65.</note>
 </msItem>
 <msItem n="1.2">
  <locus from="4rto="4v">4r-4v</locus>
  <title xml:lang="en">Prologue to the Old
     Testament</title>
  <rubric xml:lang="la">
   <locus from="4rto="4r">4r</locus>Incipit prologus
     beati Ieromini in pentachum </rubric>
  <incipit xml:lang="la">
   <locus from="4rto="4r">4r</locus> Desiderii meii
     desideratus accepi epistulas </incipit>
  <explicit xml:lang="la">
   <locus from="4vto="4v">4v</locus> possim eodem
     spiritu quo scripti sunt libri in latinum eos
     transferre sermonem </explicit>
  <note>PL 28, 177-184; Stegmüller 285.</note>
 </msItem>
</msItem>
<msItem n="2">
 <locus from="5rto="321v">5r-321v</locus>
 <title xml:lang="en">Vulgate, Old Testament</title>
 <incipit xml:lang="la">
  <locus from="5rto="5r">5r</locus>In principio creavit
   deus celum et terram </incipit>
 <explicit xml:lang="la">
  <locus from="321vto="321v">321v</locus>non erit ut
   ingratus hic ergo erit consummatus. </explicit>
 <msItem n="2.1">
  <locus from="5rto="21v">5r-21v</locus>
  <title xml:lang="en">Genesis</title>
 </msItem>
<!-- [...] -->
</msItem>

2 Schema

Schema msdesc: Elements

<abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
type(type) allows the encoder to classify the abbreviation according to some convenient typology.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Sample values include:
suspension
(suspension) the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
contraction
(contraction) the abbreviation omits some letter(s) in the middle.
brevigraph
the abbreviation comprises a special symbol or mark.
superscription
(superscription) the abbreviation includes writing above the line.
acronym
(acronym) the abbreviation comprises the initial letters of the words of a phrase.
title
(title) the abbreviation is for a title of address (Dr, Ms, Mr, …)
organization
(organization) the abbreviation is for the name of an organization.
geographic
(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 6.2.

Member of
Contained by
May contain
Note

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a p.

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.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 or object being described, such as non-contemporaneous documents or fragments bound in with it at some earlier historical period. [10.7.3.3. Accompanying Material]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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> (acquisition) contains any descriptive or other information concerning the process by which a manuscript or manuscript part or other object entered the holding institution. [10.8. History]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.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))
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.5.3. Additions, Deletions, and Omissions]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.placement (@place) att.typed (@type, @subtype) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
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,
   att.dimensions.attributes,
   macro.paraContent
}

<additional>

<additional> (additional) groups additional information, combining bibliographic information about a manuscript or other object, or surrogate copies of it, with curatorial or administrative information. [10.9. Additional Information]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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> (additions) contains a description of any significant additions found within a manuscript or other object, such as marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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.attributes, 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]
Module namesdates — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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
}

<address>

<address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Note

This element should be used for postal addresses only. Within it, the generic element addrLine may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as street, postCode etc.

Example

Using just the elements defined by the core module, an address could be represented as follows:

<address>
 <street>via Marsala 24</street>
 <postCode>40126</postCode>
 <name>Bologna</name>
 <name>Italy</name>
</address>
Example

When a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic name:

<address>
 <street>via Marsala 24</street>
 <postCode>40126</postCode>
 <settlement>Bologna</settlement>
 <country>Italy</country>
</address>
Example
<address>
 <addrLine>Computing Center, MC 135</addrLine>
 <addrLine>P.O. Box 6998</addrLine>
 <addrLine>Chicago, IL 60680</addrLine>
 <addrLine>USA</addrLine>
</address>
Example
<address>
 <country key="FR"/>
 <settlement type="city">Lyon</settlement>
 <postCode>69002</postCode>
 <district type="arrondissement">IIème</district>
 <district type="quartier">Perrache</district>
 <street>
  <num>30</num>, Cours de Verdun</street>
</address>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   maxOccurs="unboundedminOccurs="0"/>

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

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

  </sequence>
 </sequence>
</content>
Schema Declaration
element address
{
   att.global.attributes,
   ( model.global*, ( model.addrPart, model.global* )+ )
}

<addrLine>

<addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: address
May contain
Note

Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an address element directly but may be wrapped within an addrLine if they form part of the printed address in some source text.

Example
<address>
 <addrLine>Computing Center, MC 135</addrLine>
 <addrLine>P.O. Box 6998</addrLine>
 <addrLine>Chicago, IL</addrLine>
 <addrLine>60680 USA</addrLine>
</address>
Example
<addrLine>
 <ref target="tel:+1-201-555-0123">(201) 555 0123</ref>
</addrLine>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element addrLine { att.global.attributes, macro.phraseSeq }

<adminInfo>

<adminInfo> (administrative information) contains information about the present custody and availability of the manuscript or other object, and also about the record description itself. [10.9.1. Administrative Information]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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? )
}

<altIdentifier>

<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript or other object, such as a former catalogue number. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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))
Contained by
msdescription: msFrag msIdentifier
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,
   att.datable.attributes,
   (
      placeName?,
      country?,
      region?,
      settlement?,
      district?,
      geogName?,
      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]
Module transcr — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.editLike (@evidence, @instant)
Member of
Contained by
May contain
transcr: damage supplied
character data
Example
do you <abbr>Mr<am>.</am>
</abbr> Jones?
Example
<choice>
 <abbr>Aug<am>g</am>
 </abbr>
 <expan>Aug<ex>ustorum duo</ex>
 </expan>
</choice>
Example
<abbr>eu<am>
  <g ref="#b-er"/>
 </am>y</abbr>
<abbr>
 <am>
  <g ref="#b-per"/>
 </am>sone

</abbr> ...
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 )*
}

<analytic>

<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
core: biblStruct
May contain
Note

May contain titles and statements of responsibility (author, editor, or other), in any order.

The analytic element may only occur within a biblStruct, where its use is mandatory for the description of an analytic level bibliographic item.

Example
<biblStruct>
 <analytic>
  <author>Chesnutt, David</author>
  <title>Historical Editions in the States</title>
 </analytic>
 <monogr>
  <title level="j">Computers and the Humanities</title>
  <imprint>
   <date when="1991-12">(December, 1991):</date>
  </imprint>
  <biblScope>25.6</biblScope>
  <biblScope>377–380</biblScope>
 </monogr>
</biblStruct>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <elementRef key="author"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="date"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <elementRef key="availability"/>
 </alternate>
</content>
Schema Declaration
element analytic
{
   att.global.attributes,
   (
      authoreditorrespStmttitlemodel.ptrLikedatetextLangidnoavailability
   )*
}

<author>

<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.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) 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

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

<sch:rule context="//tei:msItem//tei:author[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'person_\d+')]">In the
medieval catalogue, the author element, when a child of
msItem, must have a key matching the pattern
'person_\d+'.</sch:assert>
</sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element author
{
   att.global.attributes,
   att.naming.attributes,
   att.datable.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.]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
Member of
Contained by
core: monogr
header: publicationStmt
May contain
Example
<authority>John Smith</authority>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
element authority
{
   att.global.attributes,
   att.canonical.attributes,
   macro.phraseSeq.limited
}

<availability>

<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.]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
statusSpecifies the availability of a manuscript. This attribute should not be used to specify the availability of manuscript metadata: use the licence element for that purpose.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
free
The item is available.
restricted
Access to the item is restricted for conservation or other reasons.
exhibition
The item is on exhibition at the owning library or another institution, and is likely to be temporarily unavailable.
offsite
The item is stored offsite, and will take at least twenty-four hours to produce.
printcat
The item is orderable through a catalogue of printed materials, typically because it is a fragment in a printed book or because it is part of a collection of mostly printed material.
none
The item cannot be ordered, typically either because it is a stub record or because it is not held by the library which is responsible for the catalogue.
unknown
Availability of the item is unknown.
Member of
Contained by
header: publicationStmt
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
   {
      list
      {
         (
            "free"
          | "restricted"
          | "exhibition"
          | "offsite"
          | "printcat"
          | "none"
          | "unknown"
         )+
      }
   }?,
   ( 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.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.sortable (@sortKey) att.docStatus (@status) 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
Suggested values include:
MS
The reference is to a manuscript
QUARTO
The reference is to the Bodleian Quarto Catalogues
SC
The reference is to the Bodleian Summary Catalogue
OC
The reference is to the Bodleian Old Catalogue
bible
The reference is to the bible
commentary
The reference is to a commentary
edition
The reference is to an edition
extract
The reference is to an extract
related
The reference is to a related item
text-relations
The reference is to a textually-related item
translation
The reference is to a translation
Member of
Contained by
May contain
Note

Contains phrase-level elements, together with any combination of elements from the model.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.attribute.subtype,
   att.sortable.attributes,
   att.docStatus.attributes,
   attribute type
   {
      "MS"
    | "QUARTO"
    | "SC"
    | "OC"
    | "bible"
    | "commentary"
    | "edition"
    | "extract"
    | "related"
    | "text-relations"
    | "translation"
    | teidata.enumerated
   }?,
   (
      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.12.2.5. Scopes and Ranges in Bibliographic Citations]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citing (@unit, @from, @to)
Member of
Contained by
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 may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff</biblScope>.

It is now considered good practice to supply this element as a sibling (rather than a child) of imprint, since it supplies information which does not constitute part of the imprint.

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
}

<biblStruct>

<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Example
<biblStruct>
 <monogr>
  <author>Blain, Virginia</author>
  <author>Clements, Patricia</author>
  <author>Grundy, Isobel</author>
  <title>The Feminist Companion to Literature in English: women writers from the middle ages
     to the present</title>
  <edition>first edition</edition>
  <imprint>
   <publisher>Yale University Press</publisher>
   <pubPlace>New Haven and London</pubPlace>
   <date>1990</date>
  </imprint>
 </monogr>
</biblStruct>
Example
<biblStruct type="newspaper">
 <analytic>
  <author>
   <forename>David</forename>
   <surname>Barstow</surname>
  </author>
  <author>
   <forename>Susanne</forename>
   <surname>Craig</surname>
  </author>
  <author>
   <forename>Russ</forename>
   <surname>Buettner</surname>
  </author>
  <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>
  <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>
 </analytic>
 <monogr>
  <title level="j">The New York Times</title>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>A. G. Sulzberger</publisher>
   <date when="2018-10-03">Wednesday, October 3, 2018</date>
  </imprint>
  <biblScope unit="volume">CLXVIII</biblScope>
  <biblScope unit="issue">58,104</biblScope>
  <biblScope unit="page">1</biblScope>
 </monogr>
</biblStruct>
Content model
<content>
 <sequence>
  <elementRef key="analytic"
   maxOccurs="unboundedminOccurs="0"/>

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

   <elementRef key="monogr"/>
   <elementRef key="series"
    maxOccurs="unboundedminOccurs="0"/>

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

   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
  </alternate>
 </sequence>
</content>
Schema Declaration
element biblStruct
{
   att.global.attributes,
   att.declarable.attributes,
   att.typed.attributes,
   att.sortable.attributes,
   att.docStatus.attributes,
   (
      analytic*,
      ( monogr, series* )+,
      ( model.noteLike | model.ptrLike | relatedItem | citedRange )*
   )
}

<binding>

<binding> (binding) contains a description of one binding, i.e. type of covering, boards, etc. applied to a manuscript or other object. [10.7.3.1. Binding Descriptions]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.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))
contemporary(contemporary) specifies 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>
Schematron

<sch:rule context="//tei:binding">
<sch:assert role="warn"
 test="@when or @notBefore or @notAfter or @contemporary='true'">
The binding element should have dating attributes (when or notBefore/notAfter)
or a contemporary attribute (with the value 'true').
</sch:assert>
</sch:rule>
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.attributes,
   att.datable.attributes,
   attribute contemporary { teidata.xTruthValue }?,
   ( model.pLike | condition | decoNote )+
}

<bindingDesc>

<bindingDesc> (binding description) describes the present and former bindings of a manuscript or other object, 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]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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+ )
}

<body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Module textstructure — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
Contained by
textstructure: text
May contain
derived-module-msdesc: include
figures: figure
msdescription: msDesc
textstructure: div
transcr: fw
Example
<body>
 <l>Nu scylun hergan hefaenricaes uard</l>
 <l>metudæs maecti end his modgidanc</l>
 <l>uerc uuldurfadur sue he uundra gihuaes</l>
 <l>eci dryctin or astelidæ</l>
 <l>he aerist scop aelda barnum</l>
 <l>heben til hrofe haleg scepen.</l>
 <l>tha middungeard moncynnæs uard</l>
 <l>eci dryctin æfter tiadæ</l>
 <l>firum foldu frea allmectig</l>
 <trailer>primo cantauit Cædmon istud carmen.</trailer>
</body>
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">

     <alternate maxOccurs="1minOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <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 )* )+
       | (
            ( ( schemaSpec | model.common ), model.global* )+,
            (
               ( model.divLike, ( model.global | model.divGenLike )* )+
             | ( model.div1Like, ( model.global | model.divGenLike )* )+
            )?
         )
      ),
      ( model.divBottom, model.global* )*
   )
}

<catchwords>

<catchwords> (catchwords) describes the system used to ensure correct ordering of the quires or similar making up a codex, incunable, or other object typically by means of annotations at the foot of the page. [10.3.7. Catchwords, Signatures, Secundo Folio]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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>
Schematron

<sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert>
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]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
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,
   att.canonical.attributes,
   ( text | model.limitedPhrase | model.catDescPart )*
}

<category>

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: category taxonomy
May contain
core: desc
header: catDesc category
Example
<category xml:id="b1">
 <catDesc>Prose reportage</catDesc>
</category>
Example
<category xml:id="b2">
 <catDesc>Prose </catDesc>
 <category xml:id="b11">
  <catDesc>journalism</catDesc>
 </category>
 <category xml:id="b12">
  <catDesc>fiction</catDesc>
 </category>
</category>
Example
<category xml:id="LIT">
 <catDesc xml:lang="pl">literatura piękna</catDesc>
 <catDesc xml:lang="en">fiction</catDesc>
 <category xml:id="LPROSE">
  <catDesc xml:lang="pl">proza</catDesc>
  <catDesc xml:lang="en">prose</catDesc>
 </category>
 <category xml:id="LPOETRY">
  <catDesc xml:lang="pl">poezja</catDesc>
  <catDesc xml:lang="en">poetry</catDesc>
 </category>
 <category xml:id="LDRAMA">
  <catDesc xml:lang="pl">dramat</catDesc>
  <catDesc xml:lang="en">drama</catDesc>
 </category>
</category>
Content model
<content>
 <sequence>
  <alternate>
   <elementRef key="catDesc"
    maxOccurs="unboundedminOccurs="1"/>

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

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

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

<change>

<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]
Module header — Schema
Attributes 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.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
target(target) points to one or more elements that belong to this change.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
header: revisionDesc
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> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
linking: seg
transcr: am ex supplied
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="2">

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

<cit>

<cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 9.3.5.1. Examples]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
Member of
Contained by
May contain
figures: figure formula
msdescription: msDesc
transcr: fw
Example
<cit>
 <quote>and the breath of the whale is frequently attended with such an insupportable smell,
   as to bring on disorder of the brain.</quote>
 <bibl>Ulloa's South America</bibl>
</cit>
Example
<entry>
 <form>
  <orth>horrifier</orth>
 </form>
 <cit type="translationxml:lang="en">
  <quote>to horrify</quote>
 </cit>
 <cit type="example">
  <quote>elle était horrifiée par la dépense</quote>
  <cit type="translationxml:lang="en">
   <quote>she was horrified at the expense.</quote>
  </cit>
 </cit>
</entry>
Example
<cit type="example">
 <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>
 <media mimeType="audio/wav"
  url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"/>

 <cit type="translation">
  <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>
 </cit>
 <cit type="translation">
  <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>
 </cit>
</cit>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">

  <classRef key="model.biblLike"/>
  <classRef key="model.egLike"/>
  <classRef key="model.entryPart"/>
  <classRef key="model.global"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.attributable"/>
  <elementRef key="pc"/>
  <elementRef key="q"/>
 </alternate>
</content>
Schema Declaration
element cit
{
   att.global.attributes,
   att.typed.attributes,
   (
      model.biblLikemodel.egLikemodel.entryPartmodel.globalmodel.graphicLikemodel.ptrLikemodel.attributable
    | pc
    | q
   )+
}

<citedRange>

<citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.citing (@unit, @from, @to)
Member of
Contained by
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 may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <citedRange from="3">p. 3ff</citedRange>.

Example
<citedRange>pp 12–13</citedRange>
<citedRange from="12to="13unit="page"/>
<citedRange unit="volume">II</citedRange>
<citedRange unit="page">12</citedRange>
Example
<bibl>
 <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.
   4-5</citedRange>
</bibl>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element citedRange
{
   att.global.attributes,
   att.pointing.attributes,
   att.citing.attributes,
   macro.phraseSeq
}

<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]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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> (collation) contains a description of how the leaves, bifolia, or similar objects are physically arranged. [10.7.1. Object Description]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
mainStructuresSpecifies the typical quire structure(s) of the book, according to English notation (i.e. the number of folios in the original quire), e.g. 8, 6 8. Note: This is a customization which is not currently part of the TEI P5 standard.
Status Optional
Datatype 1–∞ occurrences of teidata.count separated by whitespace
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,
   attribute mainStructures { list { teidata.count+ } }?,
   macro.specialPara
}

<collection>

<collection> (collection) contains the name of a collection of manuscripts or other objects, not necessarily located within a single repository. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype)
Contained by
msdescription: altIdentifier msIdentifier
May contain
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.phraseSeq.limited"/>
</content>
Schema Declaration
element collection
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   macro.phraseSeq.limited
}

<colophon>

<colophon> (colophon) contains the colophon of an item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript or other object. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective)
Member of
Contained by
msdescription: msItem msItemStruct
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,
   att.msExcerpt.attributes,
   macro.phraseSeq
}

<condition>

<condition> (condition) contains a description of the physical condition of the manuscript or object. [10.7.1.5. Condition]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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.attributes, macro.specialPara }

<corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) 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
}

<countermark> [https://github.com/msdesc/consolidated-tei-schema]

<countermark> Contains a description of a countermark. Note: This is a customization which is not currently part of the TEI P5 standard.
Namespace https://github.com/msdesc/consolidated-tei-schema
Module derived-module-msdesc
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
Contained by
May contain
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element countermark
{
   att.global.attributes,
   att.global.rendition.attributes,
   att.global.linking.attributes,
   att.global.change.attributes,
   att.global.responsibility.attributes,
   att.global.source.attributes,
   macro.phraseSeq
}

<country>

<country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. Place Names]
Module namesdates — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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>
Schematron

<sch:rule context="//tei:origin//tei:country[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'place_\d+')]">In the medieval
catalogue, the country element, when a descendant of origin,
must have a key matching the pattern
'place_\d+'.</sch:assert>
</sch:rule>
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 or other object. [10.9.1.2. Availability and Custodial History]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.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.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 or other object's custodial history, either as running prose or as a series of dated custodial events. [10.9.1.2. Availability and Custodial History]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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> (damage) contains an area of damage to the text witness. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Module transcr — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.4. Dates]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) 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.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.canonical.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.dimensions.attributes,
   att.typed.attributes,
   ( text | model.gLike | model.phrase | model.global )*
}

<decoDesc>

<decoDesc> (decoration description) contains a description of the decoration of a manuscript or other object, either as in paragraphs, or as one or more decoNote elements. [10.7.3. Bindings, Seals, and Additional Material]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

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

  </sequence>
 </alternate>
</content>
Schema Declaration
element decoDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, decoNote+ ) )
}

<decoNote>

<decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript or other object, or a fairly homogenous class of such components. [10.7.3. Bindings, Seals, and Additional Material]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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
Suggested values include:
border
The decoration note concerns the border(s)
diagram
The decoration note concerns the diagram(s)
illustration
The decoration note concerns the illustration(s)
initial
The decoration note concerns the initial(s)
marginal
The decoration note concerns the marginal decoration
micrography
The decoration note concerns the micrography
miniature
The decoration note concerns miniature(s) or coloured drawings
drawing
The decoration note concerns (uncoloured) drawings or sketches
rubrication
The decoration note concerns the rubrication or other highlighting
bas-de-page
The decoration note concerns bas-de-page scenes
map
The decoration note concerns a map or maps
headpiece
The decoration note concerns a headpiece
canonTable
The decoration note concerns canon table(s)
carpetPage
The decoration note concerns so-called carpet page(s)
histInit
The decoration note concerns historiated initials
decInit
The decoration note concerns decorated (but not historiated) initials
flourInit
The decoration note concerns pen-work flourishing of letters and/or borders
colInit
The decoration note concerns coloured (but not decorated or flourished) initials
plainInit
The decoration note concerns plain initials (in the ink of the text)
chrysography
The decoration note concerns chrysography (writing in gold)
lineFill
The decoration note concerns line fillers
cadel
The decoration note concerns cadels
instructions
The decoration note concerns intructions for decoration
unfilled
The decoration note concerns space for decoration left unfilled
none
The decoration note records the absence of any decoration
other
The decoration note concerns other/unspecified aspects (you may also provide a custom value)
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"
    | "illustration"
    | "initial"
    | "marginal"
    | "micrography"
    | "miniature"
    | "drawing"
    | "rubrication"
    | "bas-de-page"
    | "map"
    | "headpiece"
    | "canonTable"
    | "carpetPage"
    | "histInit"
    | "decInit"
    | "flourInit"
    | "colInit"
    | "plainInit"
    | "chrysography"
    | "lineFill"
    | "cadel"
    | "instructions"
    | "unfilled"
    | "none"
    | "other"
    | teidata.enumerated
   }?,
   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.5.3. Additions, Deletions, and Omissions]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.typed (@type, @subtype) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
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,
   att.dimensions.attributes,
   macro.paraContent
}

<depth>

<depth> (depth) contains a measurement from the front to the back of an object, perpendicular to the measurement given by the width element. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May contain Character data only
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 }

<desc>

<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [22.4.1. Description of Components]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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
Suggested values include:
deprecationInfo
(deprecation information) This element describes why or how its parent element is being deprecated, typically including recommendations for alternate encoding.
<dataSpec ident="teidata.point"
 module="teivalidUntil="2050-02-25">

 <desc type="deprecationInfo"
  versionDate="2018-09-14xml:lang="en">
Several standards bodies, including NIST in the USA,
   strongly recommend against ending the representation of a number
   with a decimal point. So instead of <q>3.</q> use either <q>3</q>
   or <q>3.0</q>.</desc>
<!-- ... -->
</dataSpec>
Member of
Contained by
May contain
Note

When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb.

Example

Example of a desc element inside a documentation element.

<dataSpec ident="teidata.point"
 module="tei">

 <desc versionDate="2010-10-17"
  xml:lang="en">
defines the data type used to express a point in cartesian space.</desc>
 <content>
  <dataRef name="token"
   restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>

 </content>
<!-- ... -->
</dataSpec>
Example

Example of a desc element in a non-documentation element.

<place xml:id="KERG2">
 <placeName>Kerguelen Islands</placeName>
<!-- ... -->
 <terrain>
  <desc>antarctic tundra</desc>
 </terrain>
<!-- ... -->
</place>
Schematron A desc with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when desc is a valid child of that element.

<sch:rule context="tei:desc[ @type eq 'deprecationInfo']">
<sch:assert test="../@validUntil">Information about a
deprecation should only be present in a specification element
that is being deprecated: that is, only an element that has a
@validUntil attribute should have a child <desc
type="deprecationInfo">.</sch:assert>
</sch:rule>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
Schema Declaration
element desc
{
   att.global.attributes,
   att.typed.attribute.subtype,
   attribute type { "deprecationInfo" | teidata.enumerated }?,
   macro.limitedContent
}

<dim>

<dim> contains any single measurement forming part of a dimensional specification of some sort. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May contain Character data only
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> (dimensions) contains a dimensional specification. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (type, @subtype)
typeindicates which aspect of the object is being measured.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
binding
The dimensions concerns the binding(s)
folia
The dimensions concerns the folia as a whole
leaf
The dimensions concerns the leaf
line-height
The dimensions concerns the line-height
ruled
The dimensions concerns the ruling
written
The dimensions concerns the written area
other
The dimensions concerns other/unspecified aspects (you may also provide a custom value)
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

<sch:rule context="//tei:dimensions">
<sch:assert role="errortest="@unit"> The unit of measurement
must be specified in the unit attribute on the dimensions
element </sch:assert>
</sch:rule>
Schematron

<sch:report test="count(tei:width)> 1">The element <sch:name/> may appear once only
</sch:report>
<sch:report test="count(tei:height)> 1">The element <sch:name/> may appear once only
</sch:report>
<sch:report test="count(tei:depth)> 1">The element <sch:name/> may appear once only
</sch: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,
   att.typed.attribute.subtype,
   attribute type
   {
      "binding"
    | "folia"
    | "leaf"
    | "line-height"
    | "ruled"
    | "written"
    | "other"
    | teidata.enumerated
   }?,
   ( dim | model.dimLike )*
}

<distributor>

<distributor> (distributor) supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
Member of
Contained by
core: bibl imprint
header: publicationStmt
May contain
Example
<distributor>Oxford Text Archive</distributor>
<distributor>Redwood and Burn Ltd</distributor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element distributor
{
   att.global.attributes,
   att.canonical.attributes,
   macro.phraseSeq
}

<district>

<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]
Module namesdates — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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]
Module textstructure — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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
derived-module-msdesc: include
figures: figure
msdescription: msDesc
textstructure: div
transcr: fw
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

<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:report>
Schematron

<sch: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, unless div is a descendant of floatingText.
</sch: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">

      <alternate maxOccurs="1"
       minOccurs="1">

       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <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* )+
          | (
               ( ( schemaSpec | model.common ), model.global* )+,
               ( ( model.divLike | model.divGenLike ), model.global* )*
            )
         ),
         ( model.divBottom, model.global* )*
      )?
   )
}

<edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: bibl monogr
header: editionStmt
May contain
Example
<edition>First edition <date>Oct 1990</date>
</edition>
<edition n="S2">Students' edition</edition>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element edition { att.global.attributes, macro.phraseSeq }

<editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: fileDesc
May contain
Example
<editionStmt>
 <edition n="S2">Students' edition</edition>
 <respStmt>
  <resp>Adapted by </resp>
  <name>Elizabeth Kirk</name>
 </respStmt>
</editionStmt>
Example
<editionStmt>
 <p>First edition, <date>Michaelmas Term, 1991.</date>
 </p>
</editionStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

  <sequence>
   <elementRef key="edition"/>
   <classRef key="model.respLike"
    maxOccurs="unboundedminOccurs="0"/>

  </sequence>
 </alternate>
</content>
Schema Declaration
element editionStmt
{
   att.global.attributes,
   ( model.pLike+ | ( edition, model.respLike* ) )
}

<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.12.2.2. Titles, Authors, and Editors]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Member of
Contained by
msdescription: 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 role="Technical_Editor">Ron Van den Branden</editor>
<editor role="Editor-in-Chief">John Walsh</editor>
<editor role="Managing_Editor">Anne Baillot</editor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element editor
{
   att.global.attributes,
   att.naming.attributes,
   att.datable.attributes,
   macro.phraseSeq
}

<email>

<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Note

The format of a modern Internet email address is defined in RFC 2822

Example
<email>membership@tei-c.org</email>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element email { att.global.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]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
header: teiHeader
May contain
core: p
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 )+
}

<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]
Module transcr — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May contain Character data only
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,
   att.dimensions.attributes,
   macro.xtext
}

<expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant)
Member of
Contained by
May contain
Note

The content of this element should be the expanded abbreviation, usually (but not always) 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.

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a p.

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

<explicit>

<explicit> (explicit) contains the explicit of a 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]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
Member of
Contained by
core: bibl
msdescription: msItem msItemStruct
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> (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.12.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: bibl monogr
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 supply normalized 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]
Module transcr — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
Member of
Contained by
textstructure: TEI
May contain
core: graphic
figures: formula
transcr: surface surfaceGrp
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>
Schematron

<sch:rule context="tei:facsimile//tei:line | tei:facsimile//tei:zone">
<sch:report test="child::text()[ normalize-space(.) ne '']"> A facsimile element represents a text with images, thus
transcribed text should not be present within it.
</sch:report>
</sch:rule>
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? )
}

<fallback> [http://www.w3.org/2001/XInclude]

<fallback> Wrapper for fallback elements if an XInclude fails
Namespace http://www.w3.org/2001/XInclude
Module derived-module-msdesc
Contained by
derived-module-msdesc: include
May contain ANY
Content model
<content>
 <alternate maxOccurs="1minOccurs="1">
  <textNode/>
  <anyElement/>
 </alternate>
</content>
Schema Declaration
element fallback { text | anyElement-fallback }

<figDesc>

<figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images]
Module figures — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
figures: figure
May contain
Note

This element is intended for use as an alternative to the content of its parent figure element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes.

Example
<figure>
 <graphic url="emblem1.png"/>
 <head>Emblemi d'Amore</head>
 <figDesc>A pair of naked winged cupids, each holding a
   flaming torch, in a rural setting.</figDesc>
</figure>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
Schema Declaration
element figDesc { att.global.attributes, macro.limitedContent }

<figure>

<figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [14.4. Specific Elements for Graphic Images]
Module figures — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.typed (@type, @subtype) att.written (@hand)
Member of
Contained by
May contain
derived-module-msdesc: include
msdescription: msDesc
transcr: fw
Example
<figure>
 <head>The View from the Bridge</head>
 <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
   series of buoys strung out between them.</figDesc>
 <graphic scale="0.5"
  url="http://www.example.org/fig1.png"/>

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

  <classRef key="model.headLike"/>
  <classRef key="model.common"/>
  <elementRef key="figDesc"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.global"/>
  <classRef key="model.divBottom"/>
 </alternate>
</content>
Schema Declaration
element figure
{
   att.global.attributes,
   att.placement.attributes,
   att.typed.attributes,
   att.written.attributes,
   (
      model.headLikemodel.commonfigDescmodel.graphicLikemodel.globalmodel.divBottom
   )*
}

<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]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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"
    maxOccurs="unboundedminOccurs="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> (filiation) contains information concerning the manuscript or other object's filiation, i.e. its relationship to other surviving manuscripts or other objects of the same text or contents, its protographs, antigraphs and apographs. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
Member of
Contained by
msdescription: msItem msItemStruct
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> (final rubric) 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]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
Member of
Contained by
msdescription: msItem msItemStruct
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,
   att.msExcerpt.attributes,
   macro.phraseSeq
}

<foliation>

<foliation> (foliation) describes the numbering system or systems used to count the leaves or pages in a codex or similar object. [10.7.1.4. Foliation]
Module msdescription — Schema
Attributes 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.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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.datable.attributes,
   att.global.attributes,
   macro.specialPara
}

<foreign>

<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Note

The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.

This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element.

The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.

Example
This is
heathen Greek to you still? Your <foreign xml:lang="la">lapis
philosophicus</foreign>?
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element foreign { att.global.attributes, macro.phraseSeq }

<forename>

<forename> (forename) contains a forename, given or baptismal name. [13.2.1. Personal Names]
Module namesdates — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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> (formula) contains a mathematical or other formula. [14.2. Formulæ and Mathematical Expressions]
Module figures — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.notated (@notation)
Member of
Contained by
May contain
core: graphic hi q
figures: formula
character data
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 )*
}

<funder>

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) 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
core: bibl monogr
msdescription: msItem
May contain
Note

Funders provide financial support for a project; they are distinct from sponsors (see element sponsor), who provide intellectual support and authority.

Example
<funder>The National Endowment for the Humanities, an independent federal agency</funder>
<funder>Directorate General XIII of the Commission of the European Communities</funder>
<funder>The Andrew W. Mellon Foundation</funder>
<funder>The Social Sciences and Humanities Research Council of Canada</funder>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
element funder
{
   att.global.attributes,
   att.canonical.attributes,
   att.datable.attributes,
   macro.phraseSeq.limited
}

<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]
Module transcr — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.written (@hand) att.typed (type, @subtype)
typeclassifies the material encoded according to some useful typology.
Derived fromatt.typed
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.typed.attribute.subtype,
   att.placement.attributes,
   att.written.attributes,
   attribute type { teidata.enumerated }?,
   macro.phraseSeq
}

<gap>

<gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.timed (@start, @end) att.editLike (@evidence, @instant) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
reason(reason) gives the reason for omission
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
cancelled
(cancelled)
deleted
(deleted)
editorial
(editorial) for features omitted from transcription due to editorial policy
illegible
(illegible)
inaudible
(inaudible)
irrelevant
(irrelevant)
sampling
(sampling)
agent(agent) in the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.
Status Optional
Datatype teidata.enumerated
Sample values include:
rubbing
(rubbing) damage results from rubbing of the leaf edges
mildew
(mildew) damage results from mildew on the leaf surface
smoke
(smoke) damage results from smoke
Member of
Contained by
May contain
core: desc
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="several linesreason="lost"/>
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,
   att.dimensions.attributes,
   attribute reason
   {
      list
      {
         (
            "cancelled"
          | "deleted"
          | "editorial"
          | "illegible"
          | "inaudible"
          | "irrelevant"
          | "sampling"
          | teidata.enumerated
         )+
      }
   }?,
   attribute agent { teidata.enumerated }?,
   ( model.descLike | model.certLike )*
}

<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]
Module namesdates — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls)
Member of
Contained by
May contain Character 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 }

<geogFeat>

<geogFeat> (geographical feature name) contains a common noun identifying some geographical feature contained within a geographic name, such as valley, mount, etc. [13.2.3. Place Names]
Module namesdates — Schema
Attributes 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.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May contain
Example
<geogName> The <geogFeat>vale</geogFeat> of White Horse</geogName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element geogFeat
{
   att.datable.attributes,
   att.editLike.attributes,
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.dimensions.attributes,
   macro.phraseSeq
}

<geogName>

<geogName> (geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai. [13.2.3. Place Names]
Module namesdates — Schema
Attributes 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.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype)
Member of
Contained by
May contain
Example
<geogName>
 <geogFeat>Mount</geogFeat>
 <name>Sinai</name>
</geogName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element geogName
{
   att.datable.attributes,
   att.editLike.attributes,
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

<graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 11.1. Digital Facsimiles]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.resourced (@url) att.declaring (@decls) att.typed (@type, @subtype)
Member of
Contained by
May contain
core: desc
Note

The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute.

Within the body of a text, a graphic element indicates the presence of a graphic component in the source itself. Within the context of a facsimile or <sourceDoc> element, however, a graphic element provides an additional digital representation of some part of the source being encoded.

Example
<figure>
 <graphic url="fig1.png"/>
 <head>Figure One: The View from the Bridge</head>
 <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
   series of buoys strung out between them.</figDesc>
</figure>
Example
<facsimile>
 <surfaceGrp n="leaf1">
  <surface>
   <graphic url="page1.png"/>
  </surface>
  <surface>
   <graphic url="page2-highRes.png"/>
   <graphic url="page2-lowRes.png"/>
  </surface>
 </surfaceGrp>
</facsimile>
Example
<facsimile>
 <surfaceGrp n="leaf1xml:id="spi001">
  <surface xml:id="spi001r">
   <graphic subtype="thumbnail"
    type="normalurl="spi/thumb/001r.jpg"/>

   <graphic subtype="low-restype="normal"
    url="spi/normal/lowRes/001r.jpg"/>

   <graphic subtype="high-res"
    type="normalurl="spi/normal/highRes/001r.jpg"/>

   <graphic subtype="low-res"
    type="high-contrasturl="spi/contrast/lowRes/001r.jpg"/>

   <graphic subtype="high-res"
    type="high-contrasturl="spi/contrast/highRes/001r.jpg"/>

  </surface>
  <surface xml:id="spi001v">
   <graphic subtype="thumbnail"
    type="normalurl="spi/thumb/001v.jpg"/>

   <graphic subtype="low-restype="normal"
    url="spi/normal/lowRes/001v.jpg"/>

   <graphic subtype="high-res"
    type="normalurl="spi/normal/highRes/001v.jpg"/>

   <graphic subtype="low-res"
    type="high-contrasturl="spi/contrast/lowRes/001v.jpg"/>

   <graphic subtype="high-res"
    type="high-contrasturl="spi/contrast/highRes/001v.jpg"/>

   <zone xml:id="spi001v_detail01">
    <graphic subtype="thumbnail"
     type="normalurl="spi/thumb/001v-detail01.jpg"/>

    <graphic subtype="low-res"
     type="normal"
     url="spi/normal/lowRes/001v-detail01.jpg"/>

    <graphic subtype="high-res"
     type="normal"
     url="spi/normal/highRes/001v-detail01.jpg"/>

    <graphic subtype="low-res"
     type="high-contrast"
     url="spi/contrast/lowRes/001v-detail01.jpg"/>

    <graphic subtype="high-res"
     type="high-contrast"
     url="spi/contrast/highRes/001v-detail01.jpg"/>

   </zone>
  </surface>
 </surfaceGrp>
</facsimile>
Content model
<content>
 <classRef key="model.descLike"
  maxOccurs="unboundedminOccurs="0"/>

</content>
Schema Declaration
element graphic
{
   att.global.attributes,
   att.media.attributes,
   att.resourced.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   model.descLike*
}

<handDesc>

<handDesc> (description of hands) contains a description of all the different hands used in a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
hands(hands) specifies 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]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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.
Derived fromatt.handFeatures
Status Optional
Datatype 1–∞ occurrences of teidata.name separated by whitespace
Suggested values include:
capitalsSquare
The script of the hand is square capitals
capitalsRustic
The script of the hand is rustic capitals
uncial
The script of the hand is uncial
halfUncial
The script of the hand is half uncial
minusculeInsular
The script of the hand is insular minuscule
minusculeVernacular
The script of the hand is English vernacular minuscule ('Anglo-Saxon minuscule')
minusculeCaroline
The script of the hand is Caroline minuscule (English and continental variants of the script)
minuscule
The script of the hand is an unspecifiec minuscule (not Caroline, insular, or English vernacular)
protogothic
The script of the hand is protogothic (Romanesque, praegothica)
textualisNorthern
The script of the hand is Northern textualis
textualisSouthern
The script of the hand is Southern textualis
semitextualis
The script of the hand is semi textualis
cursivaAntiquior
The script of the hand is cursiva antiquior (anglicana, 'Ältere gotische Kursive')
cursiva
The script of the hand is cursiva (‘cancelleresca’, ‘bastarda’, ‘lettre batarde’, ‘secretary’, etc.)
hybrida
The script of the hand is cursiva (‘semihybrida’, ‘loopless bastarda’, ‘fractura’, ‘mercantesca’, etc.)
gothicoAntiqua
The script of the hand is gothico-antiqua (‘fere-humanistica’, ‘gothico-humanistica’)
humanistica
The script of the hand is humanistic (unspecified)
humanisticaTextualis
The script of the hand is humanistic textualis (unspecified)
humanisticaSemitextualis
The script of the hand is humanistic semitextualis
humanisticaCursiva
The script of the hand is humanistic cursive
executionSpecifies the execution of the script according to a widely-used schema, where applicable. The default value is assumed to be libraria. Note: This is a customization which is not currently part of the TEI P5 standard.
Status Optional
Datatype teidata.word
Suggested values include:
formata
Execution is calligraphic.
libraria
A normal level of execution.
currens
Execution is informal.
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
      {
         (
            "capitalsSquare"
          | "capitalsRustic"
          | "uncial"
          | "halfUncial"
          | "minusculeInsular"
          | "minusculeVernacular"
          | "minusculeCaroline"
          | "minuscule"
          | "protogothic"
          | "textualisNorthern"
          | "textualisSouthern"
          | "semitextualis"
          | "cursivaAntiquior"
          | "cursiva"
          | "hybrida"
          | "gothicoAntiqua"
          | "humanistica"
          | "humanisticaTextualis"
          | "humanisticaSemitextualis"
          | "humanisticaCursiva"
          | teidata.name
         )+
      }
   }?,
   attribute execution { "formata" | "libraria" | "currens" | teidata.word }?,
   macro.specialPara
}
<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.placement (@place) att.written (@hand)
Member of
Contained by
core: lg list listBibl
figures: figure
msdescription: msDesc msFrag msPart
textstructure: body div
May contain
Note

The head element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a head element based on its structural position. A head occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section.

Example

The most common use for the head element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:

<div1 n="Itype="book">
 <head>In the name of Christ here begins the first book of the ecclesiastical history of
   Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
 <div2 type="section">
  <head>In the name of Christ here begins Book I of the history.</head>
  <p>Proposing as I do ...</p>
  <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve
     years passed.</p>
  <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six
     years from the beginning of the world down to the death of Saint Martin.</trailer>
 </div2>
</div1>
Example

When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.

<div type="subsection">
 <head place="margin">Secunda conclusio</head>
 <p>
  <lb n="1251"/>
  <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>
  </hi>
  <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium
   [...]
 </p>
</div>
Example

The head element is also used to mark headings of other units, such as lists:

With a few exceptions, connectives are equally
useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">
 <head>Connectives</head>
 <item>above</item>
 <item>accordingly</item>
 <item>across from</item>
 <item>adjacent to</item>
 <item>again</item>
 <item>
<!-- ... -->
 </item>
</list>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration
element head
{
   att.global.attributes,
   att.typed.attributes,
   att.placement.attributes,
   att.written.attributes,
   (
      text
    | lgmodel.gLikemodel.phrasemodel.intermodel.lLikemodel.global
   )*
}

<height>

<height> (height) contains a measurement measured along the axis at a right angle to the bottom of the object. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May contain Character data only
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
}

<heraldry>

<heraldry> (heraldry) contains a heraldic formula or phrase, typically found as part of a blazon, coat of arms, etc. [10.3.8. Heraldry]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Example
<p>Ownership stamp (xvii cent.) on i recto with the arms
<heraldry>A bull passant within a bordure bezanty,
   in chief a crescent for difference</heraldry> [Cole],
crest, and the legend <q>Cole Deum</q>.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element heraldry { att.global.attributes, macro.phraseSeq }

<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]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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> (history) groups elements describing the full history of a manuscript, manuscript part, or other object. [10.8. History]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
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. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) 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)
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
ISBN
International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.
ISSN
International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.
DOI
Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.
URI
Uniform Resource Identifier: a string of characters to uniquely identify a resource, following the syntax of RFC 3986.
VIAF
A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.
ESTC
English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.
OCLC
OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.
Member of
Contained by
May contain
header: idno
character data
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,
   att.datable.attributes,
   att.typed.attribute.subtype,
   attribute type
   {
      "ISBN"
    | "ISSN"
    | "DOI"
    | "URI"
    | "VIAF"
    | "ESTC"
    | "OCLC"
    | teidata.enumerated
   }?,
   ( text | model.gLike | idno )*
}

<imprint>

<imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
core: monogr
May contain
Example
<imprint>
 <pubPlace>Oxford</pubPlace>
 <publisher>Clarendon Press</publisher>
 <date>1987</date>
</imprint>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">

   <elementRef key="classCode"/>
   <elementRef key="catRef"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="1">

   <alternate>
    <classRef key="model.imprintPart"/>
    <classRef key="model.dateLike"/>
   </alternate>
   <elementRef key="respStmt"
    maxOccurs="unboundedminOccurs="0"/>

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

  </sequence>
 </sequence>
</content>
Schema Declaration
element imprint
{
   att.global.attributes,
   (
      ( classCode | catRef )*,
      ( ( model.imprintPart | model.dateLike ), respStmt*, model.global* )+
   )
}

<incipit>

<incipit> contains the incipit of a manuscript or similar object 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]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
Member of
Contained by
core: bibl
msdescription: msItem msItemStruct
May contain
Example
<incipit>Pater noster qui es in celis</incipit>
<incipit defective="true">tatem dedit hominibus alleluia.</incipit>
<incipit type="biblical">Ghif ons huden onse dagelix broet</incipit>
<incipit>O ongehoerde gewerdighe christi</incipit>
<incipit type="lemma">Firmiter</incipit>
<incipit>Ideo dicit firmiter quia ordo fidei nostre probari non potest</incipit>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element incipit
{
   att.global.attributes,
   att.typed.attributes,
   att.msExcerpt.attributes,
   macro.phraseSeq
}

<include> [http://www.w3.org/2001/XInclude]

<include> The W3C XInclude element
Namespace http://www.w3.org/2001/XInclude
Module derived-module-msdesc
Attributes
href pointer to the resource being included
Status Optional
Datatype teidata.pointer
parse
Status Optional
Legal values are:
xml
[Default]
text
xpointer
Status Optional
Datatype teidata.text
encoding
Status Optional
Datatype teidata.text
accept
Status Optional
Datatype teidata.text
accept-charset
Status Optional
Datatype teidata.text
accept-language
Status Optional
Datatype teidata.text
Member of
Contained by
figures: figure
header: teiHeader
textstructure: body div
May contain
derived-module-msdesc: fallback
Content model
<content>
 <elementRef key="fallbackmaxOccurs="1"
  minOccurs="0"/>

</content>
Schema Declaration
element include
{
   attribute href { teidata.pointer }?,
   attribute parse { "xml" | "text" }?,
   attribute xpointer { teidata.text }?,
   attribute encoding { teidata.text }?,
   attribute accept { teidata.text }?,
   attribute accept-charset { teidata.text }?,
   attribute accept-language { teidata.text }?,
   fallback?
}

<institution>

<institution> (institution) contains the name of an organization such as a university or library, with which a manuscript or other object is identified, generally its holding institution. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Contained by
msdescription: altIdentifier msIdentifier
May contain
Example
<msIdentifier>
 <settlement>Oxford</settlement>
 <institution>University of Oxford</institution>
 <repository>Bodleian Library</repository>
 <idno>MS. Bodley 406</idno>
</msIdentifier>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
element institution
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq.limited
}

<item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey)
Contained by
core: list
May contain
Note

May contain simple prose or a sequence of chunks.

Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the item element is by definition synonymous with the use of the label element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the label element, not n.

Example
<list rend="numbered">
 <head>Here begin the chapter headings of Book IV</head>
 <item n="4.1">The death of Queen Clotild.</item>
 <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
 <item n="4.3">The wives and children of Lothar.</item>
 <item n="4.4">The Counts of the Bretons.</item>
 <item n="4.5">Saint Gall the Bishop.</item>
 <item n="4.6">The priest Cato.</item>
 <item> ...</item>
</list>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element item
{
   att.global.attributes,
   att.sortable.attributes,
   macro.specialPara
}

<keywords>

<keywords> (keywords) contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
schemeidentifies the controlled vocabulary within which the set of keywords concerned is defined, for example by a taxonomy element, or by some other resource.
Status Optional
Datatype teidata.pointer
Contained by
header: textClass
May contain
core: list term
Note

Each individual keyword (including compound subject headings) should be supplied as a term element directly within the keywords element. An alternative usage, in which each term appears within an item inside a list is permitted for backwards compatibility, but is deprecated.

If no control list exists for the keywords used, then no value should be supplied for the scheme attribute.

Example
<keywords scheme="http://classificationweb.net">
 <term>Babbage, Charles</term>
 <term>Mathematicians - Great Britain - Biography</term>
</keywords>
Example
<keywords>
 <term>Fermented beverages</term>
 <term>Central Andes</term>
 <term>Schinus molle</term>
 <term>Molle beer</term>
 <term>Indigenous peoples</term>
 <term>Ethnography</term>
 <term>Archaeology</term>
</keywords>
Content model
<content>
 <alternate>
  <elementRef key="term"
   maxOccurs="unboundedminOccurs="1"/>

  <elementRef key="list"/>
 </alternate>
</content>
Schema Declaration
element keywords
{
   att.global.attributes,
   attribute scheme { teidata.pointer }?,
   ( term+ | list )
}

<l>

<l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.fragmentable (@part)
Member of
Contained by
May contain
Example
<l met="x/x/x/x/x/real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l>
Schematron

<sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]"> Abstract model violation: Lines may not contain lines or lg elements.
</sch:report>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

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

<label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.placement (@place) att.written (@hand)
Member of
Contained by
May contain
Example

Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:

<list type="glossxml:lang="enm">
 <head xml:lang="en">Vocabulary</head>
 <headLabel xml:lang="en">Middle English</headLabel>
 <headItem xml:lang="en">New English</headItem>
 <label>nu</label>
 <item xml:lang="en">now</item>
 <label>lhude</label>
 <item xml:lang="en">loudly</item>
 <label>bloweth</label>
 <item xml:lang="en">blooms</item>
 <label>med</label>
 <item xml:lang="en">meadow</item>
 <label>wude</label>
 <item xml:lang="en">wood</item>
 <label>awe</label>
 <item xml:lang="en">ewe</item>
 <label>lhouth</label>
 <item xml:lang="en">lows</item>
 <label>sterteth</label>
 <item xml:lang="en">bounds, frisks (cf. <cit>
   <ref>Chaucer, K.T.644</ref>
   <quote>a courser, <term>sterting</term>as the fyr</quote>
  </cit>
 </item>
 <label>verteth</label>
 <item xml:lang="la">pedit</item>
 <label>murie</label>
 <item xml:lang="en">merrily</item>
 <label>swik</label>
 <item xml:lang="en">cease</item>
 <label>naver</label>
 <item xml:lang="en">never</item>
</list>
Example

Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the label element is synonymous with the n attribute on the item element:

I will add two facts, which have seldom occurred
in the composition of six, or at least of five quartos. <list rend="runontype="ordered">
 <label>(1)</label>
 <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>
 <label>(2) </label>
 <item>Not a sheet has been seen by any human eyes, excepting those of the author and the
   printer: the faults and the merits are exclusively my own.</item>
</list>
Example

Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:

<list type="gloss">
 <label>March 1757.</label>
 <item>I wrote some critical observations upon Plautus.</item>
 <label>March 8th.</label>
 <item>I wrote a long dissertation upon some lines of Virgil.</item>
 <label>June.</label>
 <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus
     amori.</quote>
 </item>
 <label>August.</label>
 <item>I went to Crassy, and staid two days.</item>
</list>

Note that the label might also appear within the item rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.

Example

Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the label element appears within the p or lg element, rather than as a preceding sibling of it.

<p>[...]
<lb/>&amp; n’entrer en mauuais &amp; mal-heu-
<lb/>ré meſnage. Or des que le conſente-
<lb/>ment des parties y eſt le mariage eſt
<lb/> arreſté, quoy que de faict il ne ſoit
<label place="margin">Puiſſance maritale
   entre les Romains.</label>
 <lb/> conſommé. Depuis la conſomma-
<lb/>tion du mariage la femme eſt ſoubs
<lb/> la puiſſance du mary, s’il n’eſt eſcla-
<lb/>ue ou enfant de famille : car en ce
<lb/> cas, la femme, qui a eſpouſé vn en-
<lb/>fant de famille, eſt ſous la puiſſance
[...]</p>

In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it.

If so desired the type attribute may be used to distinguish different categories of label.

Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element label
{
   att.global.attributes,
   att.typed.attributes,
   att.placement.attributes,
   att.written.attributes,
   macro.phraseSeq
}

<layout>

<layout> (layout) describes how text is laid out on the page or surface of the object, including information about any ruling, pricking, or other evidence of page-preparation techniques. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Attributes att.typed (@type, @subtype) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
topLineSpecifies the whether the writing is above top line, below top line, or mixed. Note: This is a customization which is not currently part of the TEI P5 standard.
Status Optional
Legal values are:
above
The writing is above top line.
below
The writing is below top line.
mixed
The writing is variously above and below top line with no clear pattern.
rulingMediumSpecifies the medium used to carry out the ruling. Note: This is a customization which is not currently part of the TEI P5 standard.
Status Optional
Datatype teidata.enumerated
Suggested values include:
ink
The ruling is carried out using ink.
leadpoint
The ruling is carried out using leadpoint or plummet.
hardpoint
The ruling is carried out using hardpoint or drypoint.
crayon
The ruling is carried out using ‘crayon’.
mixed
The ruling is carried out using several methods.
board
The ruling is carried out using a board.
columns(columns) specifies the number of columns per page
Status Optional
Datatype 1–2 occurrences of teidata.count separated by whitespace
Note

If a single number is given, all pages referenced have this number of columns. If two numbers are given, the number of columns per page varies between the values supplied. Where columns is omitted the number is assumed to be 1.

Columns may be independent of page orientation or reading direction, and a single textual stream may have one or more columns.

streams(textual streams) indicates the number of streams per page, each of which contains an independent textual stream
Status Optional
Datatype 1–2 occurrences of teidata.count separated by whitespace
Note

If a single number is given, all pages referenced have this number of textual streams. If two numbers are given, the number of textual streams per page varies between the values supplied. Where streams is omitted the number is assumed to be 1 and unless specified elsewhere the script orientation of the source is identical to that used in the TEI document.

ruledLines(ruled lines) specifies the number of ruled lines per column
Status Optional
Datatype 1–2 occurrences of teidata.count separated by whitespace
Note

If a single number is given, all columns have this number of ruled lines. If two numbers are given, the number of ruled lines per column varies between the values supplied.

writtenLines(written lines) specifies the number of written lines per column
Status Optional
Datatype 1–2 occurrences of teidata.count separated by whitespace
Note

If a single number is given, all columns have this number of written lines. If two numbers are given, the number of written lines per column varies between the values supplied.

Contained by
msdescription: layoutDesc
May contain
Example
<layout columns="1ruledLines="25 32">Most pages have between 25 and 32 long lines ruled in lead.</layout>
Example
<layout columns="2ruledLines="42">
 <p>2 columns of 42 lines ruled in ink, with central rule
   between the columns.</p>
</layout>
Example
<layout columns="1 2writtenLines="40 50">
 <p>Some pages have 2 columns, with central rule
   between the columns; each column with between 40 and 50 lines of writing.</p>
</layout>
Example
<layout columns="3streams="3"/>
<!-- Further down in document body -->
<div type="page">
 <ab>
  <pb/>
   一二三<cb type="top-stream"/>
   一二三<cb type="mid-stream"/>
   一二三<cb type="bottom-stream"/>
<!-- cb here for demo purposes -->
 </ab>
</div>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element layout
{
   att.typed.attributes,
   att.global.attributes,
   attribute topLine { "above" | "below" | "mixed" }?,
   attribute rulingMedium
   {
      "ink"
    | "leadpoint"
    | "hardpoint"
    | "crayon"
    | "mixed"
    | "board"
    | teidata.enumerated
   }?,
   attribute columns { list { teidata.count, teidata.count? } }?,
   attribute streams { list { teidata.count, teidata.count? } }?,
   attribute ruledLines { list { teidata.count, teidata.count? } }?,
   attribute writtenLines { list { teidata.count, teidata.count? } }?,
   macro.specialPara
}

<layoutDesc>

<layoutDesc> (layout description) collects the set of layout descriptions applicable to a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
msdescription: objectDesc
May contain
core: p
msdescription: layout summary
Example
<layoutDesc>
 <p>Most pages have between 25 and 32 long lines ruled in lead.</p>
</layoutDesc>
Example
<layoutDesc>
 <layout columns="2ruledLines="42">
  <p>
   <locus from="f12rto="f15v"/>
     2 columns of 42 lines pricked and ruled in ink, with
     central rule between the columns.</p>
 </layout>
 <layout columns="3">
  <p>
   <locus from="f16"/>Prickings for three columns are visible.</p>
 </layout>
</layoutDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

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

  </sequence>
 </alternate>
</content>
Schema Declaration
element layoutDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, layout+ ) )
}

<lb>

<lb> (line beginning) marks the beginning of a new (typographic) line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.5. Speech Contents]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break)
Member of
Contained by
May contain Empty element
Note

By convention, lb elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next lb element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the l element is available) except in circumstances where structural units cannot otherwise be marked.

The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives.

Example

This example shows typographical line breaks within metrical lines, where they occur at different places in different editions:

<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example

This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word.

<titlePart>
 <lb/>With Additions, ne-<lb break="no"/>ver before Printed.
</titlePart>
Content model
<content>
 <empty/>
</content>
Schema Declaration
element lb
{
   att.global.attributes,
   att.typed.attributes,
   att.edition.attributes,
   att.spanning.attributes,
   att.breaking.attributes,
   empty
}

<lg>

<lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.divLike (@org, @sample) (att.fragmentable (@part)) att.typed (@type, @subtype) att.declaring (@decls)
Member of
Contained by
May contain
Note

contains verse lines or nested line groups only, possibly prefixed by a heading.

Example
<lg type="free">
 <l>Let me be my own fool</l>
 <l>of my own making, the sum of it</l>
</lg>
<lg type="free">
 <l>is equivocal.</l>
 <l>One says of the drunken farmer:</l>
</lg>
<lg type="free">
 <l>leave him lay off it. And this is</l>
 <l>the explanation.</l>
</lg>
Schematron

<sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element
must contain at least one child l, lg, or gap element.</sch:assert>
Schematron

<sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]"> Abstract model violation: Lines may not contain line groups.
</sch:report>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">

   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate>
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <elementRef key="lg"/>
  </alternate>
  <alternate maxOccurs="unbounded"
   minOccurs="0">

   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <classRef key="model.global"/>
   <elementRef key="lg"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">

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

  </sequence>
 </sequence>
</content>
Schema Declaration
element lg
{
   att.global.attributes,
   att.divLike.attributes,
   att.typed.attributes,
   att.declaring.attributes,
   (
      ( model.divTop | model.global )*,
      (
         model.lLikemodel.stageLikemodel.labelLikemodel.pPart.transcriptionallg
      ),
      (
         model.lLikemodel.stageLikemodel.labelLikemodel.pPart.transcriptionalmodel.globallg
      )*,
      ( model.divBottom, model.global* )*
   )
}

<licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.iso (@when-iso, @notBefore-iso, @notAfter-iso, @from-iso, @to-iso)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Member of
Contained by
header: availability
May contain
Note

A licence element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence.

Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
</licence>
Example
<availability>
 <licence notBefore="2013-01-01"
  target="http://creativecommons.org/licenses/by/3.0/">

  <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence
     applies to this document.</p>
  <p>The licence was added on January 1, 2013.</p>
 </licence>
</availability>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element licence
{
   att.global.attributes,
   att.pointing.attributes,
   att.datable.attributes,
   macro.specialPara
}

<list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (type, @subtype)
type(type) describes the nature of the items in the list.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
gloss
(gloss) each list item glosses some term or concept, which is given by a label element preceding the list item.
index
(index) each list item is an entry in an index such as the alphabetical topical index at the back of a print volume.
instructions
(instructions) each list item is a step in a sequence of instructions, as in a recipe.
litany
(litany) each list item is one of a sequence of petitions, supplications or invocations, typically in a religious ritual.
syllogism
(syllogism) each list item is part of an argument consisting of two or more propositions and a final conclusion derived from them.
Note

Previous versions of these Guidelines recommended the use of type on list to encode the rendering or appearance of a list (whether it was bulleted, numbered, etc.). The current recommendation is to use the rend or style attributes for these aspects of a list, while using type for the more appropriate task of characterizing the nature of the content of a list.

The formal syntax of the element declarations allows label tags to be omitted from lists tagged <list type="gloss">; this is however a semantic error.

Member of
Contained by
May contain
figures: figure
transcr: fw
Note

May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

Example
<list rend="numbered">
 <item>a butcher</item>
 <item>a baker</item>
 <item>a candlestick maker, with
 <list rend="bulleted">
   <item>rings on his fingers</item>
   <item>bells on his toes</item>
  </list>
 </item>
</list>
Example
<list rend="bulletedtype="syllogism">
 <item>All Cretans are liars.</item>
 <item>Epimenides is a Cretan.</item>
 <item>ERGO Epimenides is a liar.</item>
</list>
Example
<list rend="simpletype="litany">
 <item>God save us from drought.</item>
 <item>God save us from pestilence.</item>
 <item>God save us from wickedness in high places.</item>
 <item>Praise be to God.</item>
</list>
Example

The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):

<div1 type="section">
 <head>Athelstan's Ordinance</head>
 <list rend="numbered">
  <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with
     the stolen goods, [if he is] over twelve years and [if the value of the goods is] over
     eightpence.
  <list rend="numbered">
    <item n="1.1">And if anyone does spare one, he is to pay for the thief with his
         wergild — and the thief is to be no nearer a settlement on that account — or to
         clear himself by an oath of that amount.</item>
    <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is
         not to be spared [whether younger or older than twelve].</item>
    <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may
         then be redeemed with 120 shillings; and the kindred are to stand surety for him
         that he will desist for ever.</item>
    <item n="1.4">And if he steals after that, they are to pay for him with his wergild,
         or to bring him back there.</item>
    <item n="1.5">And if he steals after that, they are to pay for him with his wergild,
         whether to the king or to him to whom it rightly belongs; and everyone of those who
         supported him is to pay 120 shillings to the king as a fine.</item>
   </list>
  </item>
  <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom
     no justice can be obtained, that one should order their kindred to fetch back such a
     person to justice and to find him a lord in public meeting.
  <list rend="numbered">
    <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,
         he is then to be a fugitive afterwards, and he who encounters him is to strike him
         down as a thief.</item>
    <item n="2.2">And he who harbours him after that, is to pay for him with his wergild
         or to clear himself by an oath of that amount.</item>
   </list>
  </item>
  <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds
     his guilty man, so that the king is appealed to, is to repay the value of the goods and
     120 shillings to the king; and he who appeals to the king before he demands justice as
     often as he ought, is to pay the same fine as the other would have done, if he had
     refused him justice.
  <list rend="numbered">
    <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes
         known about him, is to forfeit the slave and be liable to his wergild on the first
         occasionp if he does it more often, he is to be liable to pay all that he owns.</item>
    <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been
         an accessory of thieves who have committed theft, is to liable to the same.</item>
   </list>
  </item>
  <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to
     a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is
     afterwards convicted at the three-fold ordeal.</item>
 </list>
</div1>

Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.

Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they
confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards
inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy
Cross.
<list rend="simple">
  <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have
     subscribed to the pious and catholic validity of this document with the sign of the Holy
     Cross.</item>
  <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with
     the sign of the Holy Cross.</item>
  <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the
     sign of the Holy Cross.</item>
  <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the
     sign of the Holy Cross.</item>
  <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of
     the Holy Cross.</item>
  <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>
  <item>I, Æthelwine, bishop, have subscribed through delegates.</item>
  <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy
     Cross.</item>
 </list>
</p>
Schematron

<sch:rule context="tei:list[@type='gloss']">
<sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert>
</sch:rule>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">

   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc"
    maxOccurs="unboundedminOccurs="0"/>

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

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

   </sequence>
   <sequence>
    <elementRef key="headLabel"
     minOccurs="0"/>

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

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

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

     <elementRef key="item"/>
     <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>
</content>
Schema Declaration
element list
{
   att.global.attributes,
   att.sortable.attributes,
   att.typed.attribute.subtype,
   attribute type
   {
      "gloss"
    | "index"
    | "instructions"
    | "litany"
    | "syllogism"
    | teidata.enumerated
   }?,
   (
      ( model.divTop | model.global | desc* )*,
      (
         ( item, model.global* )+
       | (
            headLabel?,
            headItem?,
            ( label, model.global*, item, model.global* )+
         )
      ),
      ( model.divBottom, model.global* )*
   )
}

<listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.declarable (@default) att.typed (@type, @subtype)
Member of
Contained by
May contain
msdescription: msDesc
transcr: fw
Example
<listBibl>
 <head>Works consulted</head>
 <bibl>Blain, Clements and Grundy: Feminist Companion to
   Literature in English (Yale, 1990)
 </bibl>
 <biblStruct>
  <analytic>
   <title>The Interesting story of the Children in the Wood</title>
  </analytic>
  <monogr>
   <title>The Penny Histories</title>
   <author>Victor E Neuberg</author>
   <imprint>
    <publisher>OUP</publisher>
    <date>1968</date>
   </imprint>
  </monogr>
 </biblStruct>
</listBibl>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   maxOccurs="unboundedminOccurs="0"/>

  <elementRef key="desc"
   maxOccurs="unboundedminOccurs="0"/>

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

   <classRef key="model.milestoneLike"
    maxOccurs="1minOccurs="1"/>

   <elementRef key="relationmaxOccurs="1"
    minOccurs="1"/>

   <elementRef key="listRelation"
    maxOccurs="1minOccurs="1"/>

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

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

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

    <classRef key="model.milestoneLike"
     maxOccurs="1minOccurs="1"/>

    <elementRef key="relation"
     maxOccurs="1minOccurs="1"/>

    <elementRef key="listRelation"
     maxOccurs="1minOccurs="1"/>

   </alternate>
  </sequence>
 </sequence>
</content>
Schema Declaration
element listBibl
{
   att.global.attributes,
   att.sortable.attributes,
   att.declarable.attributes,
   att.typed.attributes,
   (
      model.headLike*,
      desc*,
      ( model.milestoneLike | relation | listRelation )*,
      ( model.biblLike+, ( model.milestoneLike | relation | listRelation )* )+
   )
}

<locus>

<locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
scheme(scheme) identifies the foliation scheme in terms of which the location is being specified by pointing to some foliation element defining it, or to some other equivalent resource.
Status Optional
Datatype teidata.pointer
from(from) specifies the starting point of the location in a normalized form, typically a page number.
Status Optional
Datatype teidata.word
to(to) specifies the end-point of the location in a normalized form, typically as a page number.
Status Optional
Datatype teidata.word
Member of
Contained by
May contain
core: hi q
character data
Note

The target attribute should only be used to point to elements that contain or indicate a transcription of the locus being described, as in the ‘Ben Jonson’ example.

To associate a locus element with a page image or other comparable representation, the global facs attribute should be used, as shown in the ‘Birds Praise of Love’ example. The facs attribute may be used to indicate one or more image files, as in that example, or alternatively it may point to one or more appropriate XML elements, such as the surface, zone, graphic, or <binaryObject> elements.

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 may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <locus from="3">p. 3ff</locus>.

Example

<!-- within ms description --><msItem n="1">
 <locus from="1rtarget="#F1r #F1v #F2r"
  to="2r">
ff. 1r-2r</locus>
 <author>Ben Jonson</author>
 <title>Ode to himself</title>
 <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric>
 <incipit>Com leaue the loathed stage</incipit>
 <explicit>And see his chariot triumph ore his wayne.</explicit>
 <bibl>
  <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl>
</msItem>
<!-- within transcription ... -->
<pb xml:id="F1r"/>
<!-- ... -->
<pb xml:id="F1v"/>
<!-- ... -->
<pb xml:id="F2r"/>
<!-- ... -->
Example

The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example:

<msItem>
 <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus>
 <title>Birds Praise of Love</title>
 <bibl>
  <title>IMEV</title>
  <biblScope>1506</biblScope>
 </bibl>
</msItem>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.hiLike"/>
 </alternate>
</content>
Schema Declaration
element locus
{
   att.global.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   attribute scheme { teidata.pointer }?,
   attribute from { teidata.word }?,
   attribute to { teidata.word }?,
   ( text | model.gLike | model.hiLike )*
}

<locusGrp>

<locusGrp> (locus group) groups a number of locations which together form a distinct but discontinuous item within a manuscript, manuscript part, or other object. [10.3.5. References to Locations within a Manuscript]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
scheme(scheme) identifies the foliation scheme in terms of which all the locations contained by the group are specified by pointing to some foliation element defining it, or to some other equivalent resource.
Status Optional
Datatype teidata.pointer
Member of
Contained by
May contain
msdescription: locus
Example
<msItem>
 <locusGrp>
  <locus from="13to="26">Bl. 13--26</locus>
  <locus from="37to="58">37--58</locus>
  <locus from="82to="96">82--96</locus>
 </locusGrp>
 <note>Stücke von Daniel Ecklin’s Reise ins h. Land</note>
</msItem>
Content model
<content>
 <elementRef key="locus"
  maxOccurs="unboundedminOccurs="1"/>

</content>
Schema Declaration
element locusGrp
{
   att.global.attributes,
   attribute scheme { teidata.pointer }?,
   locus+
}

<material>

<material> (material) contains a word or phrase describing the material of which the object being described is composed. [10.3.2. Material and Object Type]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.typed (@type, @subtype)
functiondescribes the function or use of the material in relation to the object as a whole.
Status Optional
Datatype teidata.enumerated
Sample values include:
binding
covering material of a codex
endband
sewing at the head or tail of the codex spine to strengthen the binding, often decorative
slipcase
removable protective cover for a set of one or more codices
support
the surface for writing
tie
a ribbon or string used to bind or close a codex or rolled scroll
Note

The sample values here are for descriptive bibliography. Other sets of sample values might include armrests, legs, tabletop, pan, and back for furniture; or wall, floor, window, column, ceiling, roof, stairs, chimney for architecture.

targetidentifies one or more elements to which the metamark applies.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
May contain
Note

The ref attribute may be used to point to one or more items within a taxonomy of types of material, defined either internally or externally.

Example
<physDesc>
 <p>
  <material>Parchment</material> leaves with a
 <material>sharkskin</material> binding.</p>
</physDesc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element material
{
   att.global.attributes,
   att.canonical.attributes,
   att.typed.attributes,
   attribute function { teidata.enumerated }?,
   attribute target { list { teidata.pointer+ } }?,
   macro.phraseSeq
}

<measure>

<measure> (measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.6.3. Numbers and Measures]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.measurement (@unit, @unitRef, @quantity, @commodity) att.ranging (@atLeast, @atMost, @min, @max, @confidence) att.typed (type, @subtype)
typespecifies the type of measurement in any convenient typology.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Member of
Contained by
May contain
Example

This example references a definition of a measurement unit declared in the TEI header:

<measure type="weight">
 <num>2</num> pounds of flesh
</measure>
<measure type="currency">£10-11-6d</measure>
<measure type="areaunitRef="#merk">2 <unit>merks</unit> of old extent</measure>
<!-- In the TEI Header: -->
<encodingDesc>
 <unitDecl>
  <unitDef type="areaxml:id="merk">
   <label>merk</label>
   <placeName ref="#Scotland"/>
   <desc>A merk was an area of land determined variably by its agricultural
       productivity.</desc>
  </unitDef>
 </unitDecl>
</encodingDesc>
Example
<measure commodity="rumquantity="40"
 unit="hogshead">
2 score hh rum</measure>
<measure commodity="rosesquantity="12"
 unit="count">
1 doz. roses</measure>
<measure commodity="tulipsquantity="1"
 unit="count">
a yellow tulip</measure>
Example
<head>Long papers.</head>
<p>Speakers will be given 30 minutes each: 20 minutes for
presentation, 10 minutes for discussion. Proposals should not
exceed <measure commodity="wordsmax="500"
  unit="count">
500
   words</measure>. This presentation type is suitable for
substantial research, theoretical or critical discussions.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element measure
{
   att.global.attributes,
   att.typed.attribute.subtype,
   att.measurement.attributes,
   att.ranging.attributes,
   attribute type { teidata.enumerated }?,
   macro.phraseSeq
}

<monogr>

<monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
core: biblStruct
May contain
Note

May contain specialized bibliographic elements, in a prescribed order.

The monogr element may only occur only within a biblStruct, where its use is mandatory for the description of a monographic-level bibliographic item.

Example
<biblStruct>
 <analytic>
  <author>Chesnutt, David</author>
  <title>Historical Editions in the States</title>
 </analytic>
 <monogr>
  <title level="j">Computers and the Humanities</title>
  <imprint>
   <date when="1991-12">(December, 1991):</date>
  </imprint>
  <biblScope>25.6</biblScope>
  <biblScope from="377to="380unit="page">377–380</biblScope>
 </monogr>
</biblStruct>
Example
<biblStruct type="book">
 <monogr>
  <author>
   <persName>
    <forename>Leo Joachim</forename>
    <surname>Frachtenberg</surname>
   </persName>
  </author>
  <title level="mtype="main">Lower Umpqua Texts</title>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>Columbia University Press</publisher>
   <date>1914</date>
  </imprint>
 </monogr>
 <series>
  <title level="stype="main">Columbia University Contributions to
     Anthropology</title>
  <biblScope unit="volume">4</biblScope>
 </series>
</biblStruct>
Content model
<content>
 <sequence>
  <alternate minOccurs="0">
   <sequence>
    <alternate>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <alternate maxOccurs="unbounded"
     minOccurs="0">

     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <elementRef key="title"
     maxOccurs="unboundedminOccurs="1"/>

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

     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
     <elementRef key="textLang"/>
     <elementRef key="editor"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <alternate maxOccurs="unbounded"
     minOccurs="1">

     <elementRef key="title"/>
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
    </alternate>
    <alternate maxOccurs="unbounded"
     minOccurs="0">

     <elementRef key="textLang"/>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <elementRef key="authority"/>
    <elementRef key="idno"/>
   </sequence>
  </alternate>
  <elementRef key="availability"
   maxOccurs="unboundedminOccurs="0"/>

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

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

   <elementRef key="edition"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">

    <elementRef key="idno"/>
    <classRef key="model.ptrLike"/>
    <elementRef key="editor"/>
    <elementRef key="sponsor"/>
    <elementRef key="funder"/>
    <elementRef key="respStmt"/>
   </alternate>
  </sequence>
  <elementRef key="imprint"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">

   <elementRef key="imprint"/>
   <elementRef key="extent"/>
   <elementRef key="biblScope"/>
  </alternate>
 </sequence>
</content>
Schema Declaration
element monogr
{
   att.global.attributes,
   (
      (
         (
            ( author | editor | meeting | respStmt ),
            ( author | editor | meeting | respStmt )*,
            title+,
            ( model.ptrLike | idno | textLang | editor | respStmt )*
         )
       | (
            ( title | model.ptrLike | idno )+,
            ( textLang | author | editor | meeting | respStmt )*
         )
       | ( authority, idno )
      )?,
      availability*,
      model.noteLike*,
      (
         edition,
         ( idno | model.ptrLike | editor | sponsor | funder | respStmt )*
      )*,
      imprint,
      ( imprint | extent | biblScope )*
   )
}

<msContents>

<msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective) att.msClass (@class)
Contained by
msdescription: msDesc msFrag msPart
May contain
core: p textLang
msdescription: msItem msItemStruct summary
Note

Unless it contains a simple prose description, this element should contain at least one of the elements summary, msItem, or msItemStruct. This constraint is not currently enforced by the schema.

Example
<msContents class="#sermons">
 <p>A collection of Lollard sermons</p>
</msContents>
Example
<msContents>
 <msItem n="1">
  <locus>fols. 5r-7v</locus>
  <title>An ABC</title>
  <bibl>
   <title>IMEV</title>
   <biblScope>239</biblScope>
  </bibl>
 </msItem>
 <msItem n="2">
  <locus>fols. 7v-8v</locus>
  <title xml:lang="frm">Lenvoy de Chaucer a Scogan</title>
  <bibl>
   <title>IMEV</title>
   <biblScope>3747</biblScope>
  </bibl>
 </msItem>
 <msItem n="3">
  <locus>fol. 8v</locus>
  <title>Truth</title>
  <bibl>
   <title>IMEV</title>
   <biblScope>809</biblScope>
  </bibl>
 </msItem>
 <msItem n="4">
  <locus>fols. 8v-10v</locus>
  <title>Birds Praise of Love</title>
  <bibl>
   <title>IMEV</title>
   <biblScope>1506</biblScope>
  </bibl>
 </msItem>
 <msItem n="5">
  <locus>fols. 10v-11v</locus>
  <title xml:lang="la">De amico ad amicam</title>
  <title xml:lang="la">Responcio</title>
  <bibl>
   <title>IMEV</title>
   <biblScope>16 &amp; 19</biblScope>
  </bibl>
 </msItem>
 <msItem n="6">
  <locus>fols. 14r-126v</locus>
  <title>Troilus and Criseyde</title>
  <note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note>
 </msItem>
</msContents>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

  <sequence>
   <elementRef key="summaryminOccurs="0"/>
   <elementRef key="textLangminOccurs="0"/>
   <elementRef key="titlePage"
    minOccurs="0"/>

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

    <elementRef key="msItem"/>
    <elementRef key="msItemStruct"/>
   </alternate>
  </sequence>
 </alternate>
</content>
Schema Declaration
element msContents
{
   att.global.attributes,
   att.msExcerpt.attributes,
   att.msClass.attributes,
   (
      model.pLike+
    | ( summary?, textLang?, titlePage?, ( msItem | msItemStruct )* )
   )
}

<msDesc>

<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [10.1. Overview]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.typed (@type, @subtype) att.declaring (@decls) att.docStatus (@status)
Member of
Contained by
May contain
Note

Although the msDesc has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fascicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general <object> may be more suitable.

Example
<msDesc>
 <msIdentifier>
  <settlement>Oxford</settlement>
  <repository>Bodleian Library</repository>
  <idno type="Bod">MS Poet. Rawl. D. 169.</idno>
 </msIdentifier>
 <msContents>
  <msItem>
   <author>Geoffrey Chaucer</author>
   <title>The Canterbury Tales</title>
  </msItem>
 </msContents>
 <physDesc>
  <objectDesc>
   <p>A parchment codex of 136 folios, measuring approx
       28 by 19 inches, and containing 24 quires.</p>
   <p>The pages are margined and ruled throughout.</p>
   <p>Four hands have been identified in the manuscript: the first 44
       folios being written in two cursive anglicana scripts, while the
       remainder is for the most part in a mixed secretary hand.</p>
  </objectDesc>
 </physDesc>
</msDesc>
Content model
<content>
 <sequence>
  <elementRef key="msIdentifier"/>
  <classRef key="model.headLike"
   maxOccurs="unboundedminOccurs="0"/>

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

   <sequence>
    <elementRef key="msContents"
     minOccurs="0"/>

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

    <elementRef key="historyminOccurs="0"/>
    <elementRef key="additional"
     minOccurs="0"/>

    <alternate>
     <elementRef key="msPart"
      maxOccurs="unboundedminOccurs="0"/>

     <elementRef key="msFrag"
      maxOccurs="unboundedminOccurs="0"/>

    </alternate>
   </sequence>
  </alternate>
 </sequence>
</content>
Schema Declaration
element msDesc
{
   att.global.attributes,
   att.sortable.attributes,
   att.typed.attributes,
   att.declaring.attributes,
   att.docStatus.attributes,
   (
      msIdentifier,
      model.headLike*,
      (
         model.pLike+
       | (
            msContents?,
            physDesc?,
            history?,
            additional?,
            ( msPart* | msFrag* )
         )
      )
   )
}

<msFrag>

<msFrag> (manuscript fragment) contains information about a fragment described in relation to a prior context, typically as a description of a virtual reconstruction of a manuscript or other object whose fragments were catalogued separately [10.11. Manuscript Fragments]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
Contained by
msdescription: msDesc
May contain
Example
<msDesc>
 <msIdentifier>
  <msName xml:lang="la">Codex Suprasliensis</msName>
 </msIdentifier>
 <msFrag>
  <msIdentifier>
   <settlement>Ljubljana</settlement>
   <repository>Narodna in univerzitetna knjiznica</repository>
   <idno>MS Kopitar 2</idno>
  </msIdentifier>
  <msContents>
   <summary>Contains ff. 10 to 42 only</summary>
  </msContents>
 </msFrag>
 <msFrag>
  <msIdentifier>
   <settlement>Warszawa</settlement>
   <repository>Biblioteka Narodowa</repository>
   <idno>BO 3.201</idno>
  </msIdentifier>
 </msFrag>
 <msFrag>
  <msIdentifier>
   <settlement>Sankt-Peterburg</settlement>
   <repository>Rossiiskaia natsional'naia biblioteka</repository>
   <idno>Q.p.I.72</idno>
  </msIdentifier>
 </msFrag>
</msDesc>
Content model
<content>
 <sequence>
  <alternate>
   <elementRef key="altIdentifier"/>
   <elementRef key="msIdentifier"/>
  </alternate>
  <classRef key="model.headLike"
   maxOccurs="unboundedminOccurs="0"/>

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

   <sequence>
    <elementRef key="msContents"
     minOccurs="0"/>

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

    <elementRef key="historyminOccurs="0"/>
    <elementRef key="additional"
     minOccurs="0"/>

   </sequence>
  </alternate>
 </sequence>
</content>
Schema Declaration
element msFrag
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( altIdentifier | msIdentifier ),
      model.headLike*,
      ( model.pLike+ | ( msContents?, physDesc?, history?, additional? ) )
   )
}

<msIdentifier>

<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: bibl
msdescription: msDesc msFrag msPart
May contain
Example
<msIdentifier>
 <settlement>San Marino</settlement>
 <repository>Huntington Library</repository>
 <idno>MS.El.26.C.9</idno>
</msIdentifier>
Schematron

<sch:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier' or normalize-space(.)='')">An msIdentifier must contain either a repository or location.</sch:report>
Content model
<content>
 <sequence>
  <sequence>
   <classRef expand="sequenceOptional"
    key="model.placeNamePart"/>

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

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

   <elementRef key="collection"
    maxOccurs="unboundedminOccurs="0"/>

   <elementRef key="idno"
    maxOccurs="unboundedminOccurs="0"/>

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

   <elementRef key="msName"/>
   <elementRef key="objectName"/>
   <elementRef key="altIdentifier"/>
  </alternate>
 </sequence>
</content>
Schema Declaration
element msIdentifier
{
   att.global.attributes,
   (
      (
         placeName?,
         country?,
         region?,
         settlement?,
         district?,
         geogName?,
         institution?,
         repository?,
         collection*,
         idno*
      ),
      ( msName | objectName | altIdentifier )*
   )
}

<msItem>

<msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective) att.msClass (@class)
Member of
Contained by
msdescription: msContents msItem
May contain
Example
<msItem class="#saga">
 <locus>ff. 1r-24v</locus>
 <title>Agrip af Noregs konunga sögum</title>
 <incipit>regi oc h<ex>ann</ex> setiho
 <gap extent="7reason="illegible"/>sc
   heim se<ex>m</ex> þio</incipit>
 <explicit>h<ex>on</ex> hev<ex>er</ex>
  <ex>oc</ex>þa buit hesta .ij. aNan viþ
   fé enh<ex>on</ex>o<ex>m</ex> aNan til
   reiþ<ex>ar</ex>
 </explicit>
 <textLang mainLang="non">Old Norse/Icelandic</textLang>
</msItem>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">

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

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

    <classRef key="model.titlepagePart"/>
    <classRef key="model.msItemPart"/>
    <classRef key="model.global"/>
   </alternate>
  </alternate>
 </sequence>
</content>
Schema Declaration
element msItem
{
   att.global.attributes,
   att.msExcerpt.attributes,
   att.msClass.attributes,
   (
      ( locus | locusGrp )*,
      (
         model.pLike+
       | ( model.titlepagePart | model.msItemPart | model.global )+
      )
   )
}

<msItemStruct>

<msItemStruct> (structured manuscript item) contains a structured description for an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.msExcerpt (@defective) att.msClass (@class)
Member of
Contained by
msdescription: msContents msItem msItemStruct
May contain
Example
<msItemStruct class="#biblComm"
 defective="falsen="2">

 <locus from="24vto="97v">24v-97v</locus>
 <author>Apringius de Beja</author>
 <title type="uniformxml:lang="la">Tractatus in Apocalypsin</title>
 <rubric>Incipit Trac<supplied reason="omitted">ta</supplied>tus
   in apoka<lb/>lipsin eruditissimi uiri <lb/> Apringi ep<ex>iscop</ex>i
   Pacensis eccl<ex>esi</ex>e</rubric>
 <finalRubric>EXPLIC<ex>IT</ex> EXPO<lb/>SITIO APOCALIPSIS
   QVA<ex>M</ex> EXPOSVIT DOM<lb/>NVS APRINGIUS EP<ex>ISCOPU</ex>S.
   DEO GR<ex>ACI</ex>AS AGO. FI<lb/>NITO LABORE ISTO.</finalRubric>
 <bibl>
  <ref target="http://amiBibl.xml#Apringius1900">Apringius</ref>, ed. Férotin</bibl>
 <textLang mainLang="la">Latin</textLang>
</msItemStruct>
Content model
<content>
 <sequence>
  <alternate minOccurs="0">
   <elementRef key="locus"/>
   <elementRef key="locusGrp"/>
  </alternate>
  <alternate>
   <classRef key="model.pLike"
    maxOccurs="unboundedminOccurs="1"/>

   <sequence>
    <elementRef key="author"
     maxOccurs="unboundedminOccurs="0"/>

    <elementRef key="respStmt"
     maxOccurs="unboundedminOccurs="0"/>

    <elementRef key="title"
     maxOccurs="unboundedminOccurs="0"/>

    <elementRef key="rubricminOccurs="0"/>
    <elementRef key="incipitminOccurs="0"/>
    <elementRef key="msItemStruct"
     maxOccurs="unboundedminOccurs="0"/>

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

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

    <elementRef key="colophon"
     maxOccurs="unboundedminOccurs="0"/>

    <elementRef key="decoNote"
     maxOccurs="unboundedminOccurs="0"/>

    <elementRef key="listBibl"
     maxOccurs="unboundedminOccurs="0"/>

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

     <elementRef key="bibl"/>
     <elementRef key="biblStruct"/>
    </alternate>
    <elementRef key="filiation"
     minOccurs="0"/>

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

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

   </sequence>
  </alternate>
 </sequence>
</content>
Schema Declaration
element msItemStruct
{
   att.global.attributes,
   att.msExcerpt.attributes,
   att.msClass.attributes,
   (
      ( locus | locusGrp )?,
      (
         model.pLike+
       | (
            author*,
            respStmt*,
            title*,
            rubric?,
            incipit?,
            msItemStruct*,
            explicit?,
            finalRubric?,
            colophon*,
            decoNote*,
            listBibl*,
            ( bibl | biblStruct )*,
            filiation?,
            model.noteLike*,
            textLang?
         )
      )
   )
}

<msName>

<msName> (alternative name) contains any form of unstructured alternative name used for a manuscript or other object, such as an ‘ocellus nominum’, or nickname. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
Contained by
msdescription: msIdentifier
May contain
core: name
character data
Example
<msName>The Vercelli Book</msName>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="rs"/>
  <elementRef key="name"/>
 </alternate>
</content>
Schema Declaration
element msName
{
   att.global.attributes,
   att.typed.attributes,
   ( text | model.gLike | rs | name )*
}

<msPart>

<msPart> (manuscript part) contains information about an originally distinct manuscript or part of a manuscript, which is now part of a composite manuscript. [10.10. Manuscript Parts]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
Contained by
msdescription: msDesc msPart
May contain
Note

As this last example shows, for compatibility reasons the identifier of a manuscript part may be supplied as a simple altIdentifier rather than using the more structured msIdentifier element. This usage is however deprecated.

Example
<msPart>
 <msIdentifier>
  <idno>A</idno>
  <altIdentifier type="catalog">
   <collection>Becker</collection>
   <idno>48, Nr. 145</idno>
  </altIdentifier>
  <altIdentifier type="catalog">
   <collection>Wiener Liste</collection>
   <idno>4°5</idno>
  </altIdentifier>
 </msIdentifier>
 <head>
  <title xml:lang="la">Gregorius: Homiliae in Ezechielem</title>
  <origPlace key="tgn_7008085">Weissenburg (?)</origPlace>
  <origDate notAfter="0815"
   notBefore="0801">
IX. Jh., Anfang</origDate>
 </head>
</msPart>
Example
<msDesc>
 <msIdentifier>
  <settlement>Amiens</settlement>
  <repository>Bibliothèque Municipale</repository>
  <idno>MS 3</idno>
  <msName>Maurdramnus Bible</msName>
 </msIdentifier>
 <msContents>
  <summary>
   <list>
    <item xml:lang="en">Miscellany of various texts;</item>
    <item xml:lang="la">Prudentius, Psychomachia;</item>
    <item xml:lang="la">Physiologus de natura animantium</item>
   </list>
  </summary>
  <textLang mainLang="la">Latin</textLang>
 </msContents>
 <physDesc>
  <objectDesc form="composite_manuscript"/>
 </physDesc>
 <msPart>
  <msIdentifier>
   <idno>ms. 10066-77 ff. 140r-156v</idno>
  </msIdentifier>
  <msContents>
   <summary xml:lang="la">Physiologus</summary>
   <textLang mainLang="la">Latin</textLang>
  </msContents>
 </msPart>
 <msPart>
  <msIdentifier>
   <altIdentifier>
    <idno>MS 6</idno>
   </altIdentifier>
  </msIdentifier>
<!-- other information specific to this part here -->
 </msPart>
<!-- more parts here -->
</msDesc>
Content model
<content>
 <sequence>
  <elementRef key="msIdentifier"/>
  <classRef key="model.headLike"
   maxOccurs="unboundedminOccurs="0"/>

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

   <sequence>
    <elementRef key="msContents"
     minOccurs="0"/>

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

    <elementRef key="historyminOccurs="0"/>
    <elementRef key="additional"
     minOccurs="0"/>

    <elementRef key="msPart"
     maxOccurs="unboundedminOccurs="0"/>

   </sequence>
  </alternate>
 </sequence>
</content>
Schema Declaration
element msPart
{
   att.global.attributes,
   att.typed.attributes,
   (
      msIdentifier,
      model.headLike*,
      (
         model.pLike+
       | ( msContents?, physDesc?, history?, additional?, msPart* )
      )
   )
}

<musicNotation>

<musicNotation> (music notation) contains description of type of musical notation. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
msdescription: physDesc
May contain
Example
<musicNotation>
 <p>Square notation of 4-line red staves.</p>
</musicNotation>
Example
<musicNotation>Neumes in <term>campo aperto</term> of the St. Gall type.
</musicNotation>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element musicNotation { att.global.attributes, macro.specialPara }

<name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) 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.typed (type, @subtype)
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
person
The name is of a person
place
The name is of a place
org
The name is of an organisation
unknown
The type of name is unknown
other
The name is of another type (you may also provide a custom value)
Member of
Contained by
May contain
Note

Proper nouns referring to people, places, and organizations may be tagged instead with persName, placeName, or orgName, when the TEI module for names and dates is included.

Example
<name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name ref="#HOC001type="person">Occleve</name>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element name
{
   att.global.attributes,
   att.personal.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.typed.attribute.subtype,
   attribute type
   {
      "person" | "place" | "org" | "unknown" | "other" | teidata.enumerated
   }?,
   macro.phraseSeq
}

<note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.placement (@place) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.written (@hand) att.anchoring (@anchored, @targetEnd)
Member of
Contained by
May contain
Example

In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":

And yet it is not only
in the great line of Italian renaissance art, but even in the
painterly <note place="bottomresp="#MDMH"
 type="gloss">

 <term xml:lang="de">Malerisch</term>. This word has, in the German, two
distinct meanings, one objective, a quality residing in the object,
the other subjective, a mode of apprehension and creation. To avoid
confusion, they have been distinguished in English as
<mentioned>picturesque</mentioned> and
<mentioned>painterly</mentioned> respectively.
</note> style of the
Dutch genre painters of the seventeenth century that drapery has this
psychological significance.

<!-- elsewhere in the document -->
<respStmt xml:id="MDMH">
 <resp>translation from German to English</resp>
 <name>Hottinger, Marie Donald Mackie</name>
</respStmt>

For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.

Example

The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:

Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note anchored="truen="126"> The
alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
published by Jacob Mann.

However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.

Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element note
{
   att.global.attributes,
   att.placement.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   att.written.attributes,
   att.anchoring.attributes,
   macro.specialPara
}

<num>

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ranging (@atLeast, @atMost, @min, @max, @confidence) att.typed (type, @subtype)
typeindicates the type of numeric value.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
cardinal
absolute number, e.g. 21, 21.5
ordinal
ordinal number, e.g. 21st
fraction
fraction, e.g. one half or three-quarters
percentage
a percentage
Note

If a different typology is desired, other values can be used for this attribute.

valuesupplies the value of the number in standard form.
Status Optional
Datatype teidata.numeric
Values a numeric value.
Note

The standard form used is defined by the TEI datatype teidata.numeric.

Member of
Contained by
May contain
Note

Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 18. Feature Structures. The num element is intended for use in simple applications.

Example
<p>I reached <num type="cardinalvalue="21">twenty-one</num> on
my <num type="ordinalvalue="21">twenty-first</num> birthday</p>
<p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>
 </num> cm per second.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element num
{
   att.global.attributes,
   att.typed.attribute.subtype,
   att.ranging.attributes,
   attribute type
   {
      "cardinal" | "ordinal" | "fraction" | "percentage" | teidata.enumerated
   }?,
   attribute value { teidata.numeric }?,
   macro.phraseSeq
}

<objectDesc>

<objectDesc> (object description) contains a description of the physical components making up the object which is being described. [10.7.1. Object Description]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
formThe original physical form of the carrier
Status Recommended
Datatype teidata.enumerated
Suggested values include:
codex
Multiple gatherings of leaves, held within a binding of some kind, and used by turning the leaves
roll
a parchment membrane, or two or more such membranes, either sewn together edge-to-edge to form a continuous surface for writing, or laid together in a pile and sewn together at the head, and used by unrolling the membranes
sheet
a single sheet of parchment or paper, not intended to form part of a codex, either kept flat or folded (rather than rolled) for storage
faltbuch
a codex whose leaves are opened by unfolding rather than turning; an ‘almanac’; a 'bat book'
roll-codex
a roll folded and bound in codex form; an 'accordion book'
other
Some other unspecified format
unknown
The format of the object is not known
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: layoutDesc supportDesc
Example
<objectDesc form="codex">
 <supportDesc material="mixed">
  <p>Early modern
  <material>parchment</material> and
  <material>paper</material>.</p>
 </supportDesc>
 <layoutDesc>
  <layout ruledLines="25 32"/>
 </layoutDesc>
</objectDesc>
Schematron

<sch:rule context="//tei:sourceDesc/tei:msDesc[not(tei:msPart)]"
 see="https://msdesc.github.io/consolidated-tei-schema/msdesc.html#objectdescBook">

<sch:assert role="warn"
 test="tei:physDesc/tei:objectDesc[@form]">
The physical form of the carrier should be recorded
in the objectDesc element, with a form attribute.
</sch:assert>
</sch:rule>
<sch:rule context="//tei:sourceDesc/tei:msDesc/tei:msPart">
<sch:assert role="warn"
 test=" tei:physDesc/tei:objectDesc[@form] or ancestor::tei:msDesc/tei:physDesc/tei:objectDesc[@form] ">
The physical form of the carrier should be recorded in
the objectDesc element, with a form attribute, unless it
has been described for the entire manuscript.
</sch:assert>
</sch:rule>
Content model
<content>
 <alternate maxOccurs="1minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

  <sequence maxOccurs="1minOccurs="1">
   <elementRef key="supportDesc"
    minOccurs="0"/>

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

  </sequence>
 </alternate>
</content>
Schema Declaration
element objectDesc
{
   att.global.attributes,
   attribute form
   {
      "codex"
    | "roll"
    | "sheet"
    | "faltbuch"
    | "roll-codex"
    | "other"
    | "unknown"
    | teidata.enumerated
   }?,
   ( model.pLike+ | ( supportDesc?, layoutDesc? ) )
}

<objectType>

<objectType> (object type) contains a word or phrase describing the type of object being referred to. [10.3.2. Material and Object Type]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
Member of
Contained by
May contain
Note

The ref attribute may be used to point to one or more items within a taxonomy of types of object, defined either internally or externally.

Example
<physDesc>
 <p> Paper and vellum <objectType>codex</objectType> in modern cloth binding.</p>
</physDesc>
Example
<physDesc>
 <p>Fragment of a re-used marble <objectType>funerary stele</objectType>.
 </p>
</physDesc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element objectType
{
   att.global.attributes,
   att.canonical.attributes,
   macro.phraseSeq
}

<orgName>

<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
Module namesdates — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.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.editLike (@evidence, @instant) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
Member of
Contained by
May contain
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">
 <placeName key="PEN">Pennsyla.</placeName> Abolition Society
</orgName> [...]
Schematron

<sch:rule context="//tei:msDesc//tei:orgName[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'org_\d+')]">In the medieval
catalogue, the orgName element, when a descendant of msDesc,
must have a key matching the pattern 'org_\d+'.</sch:assert>
</sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element orgName
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

<orig>

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 12. Critical Apparatus]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Example

If all that is desired is to call attention to the original version in the copy text, orig may be used alone:

<l>But this will be a <orig>meere</orig> confusion</l>
<l>And hardly shall we all be <orig>vnderstoode</orig>
</l>
Example

More usually, an orig will be combined with a regularized form within a choice element:

<l>But this will be a <choice>
  <orig>meere</orig>
  <reg>mere</reg>
 </choice> confusion</l>
<l>And hardly shall we all be <choice>
  <orig>vnderstoode</orig>
  <reg>understood</reg>
 </choice>
</l>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element orig { att.global.attributes, macro.paraContent }

<origDate>

<origDate> (origin date) contains any form of date, used to identify the date of origin for a manuscript, manuscript part, or other object. [10.3.1. Origination]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.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.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.editLike (@evidence, @instant) att.typed (@type, @subtype)
Member of
Contained by
May contain
Example
<origDate notAfter="-0200"
 notBefore="-0300">
3rd century BCE</origDate>
Schematron

<sch:rule context="//tei:origDate">
<sch:assert role="error"
 test="@calendar and (@when or @notBefore or @notAfter or @from or @to) and string-length(normalize-space(string())) gt 0">
The origDate element must have two or more attributes - calendar and at least one of
when, notBefore, notAfter, from and/or to - and must contain some text describing the date.
</sch:assert>
</sch:rule>
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 origDate
{
   att.global.attributes,
   att.datable.attributes,
   att.dimensions.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   ( text | model.gLike | model.phrase | model.global )*
}

<origin>

<origin> (origin) contains any descriptive or other information concerning the origin of a manuscript, manuscript part, or other object. [10.8. History]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) 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
<origin evidence="internalnotAfter="1845"
 notBefore="1802resp="#AMH">
Copied in <name type="origPlace">Derby</name>, probably from an
old Flemish original, between 1802 and 1845, according to <persName xml:id="AMH">Anne-Mette Hansen</persName>.
</origin>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element origin
{
   att.global.attributes,
   att.editLike.attributes,
   att.datable.attributes,
   macro.specialPara
}

<origPlace>

<origPlace> (origin place) contains any form of place name, used to identify the place of origin for a manuscript, manuscript part, or other object. [10.3.1. Origination]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) 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.typed (@type, @subtype)
Member of
Contained by
May contain
Note

The type attribute may be used to distinguish different kinds of ‘origin’, for example original place of publication, as opposed to original place of printing.

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

<p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.fragmentable (@part) att.written (@hand)
Member of
Contained by
May contain
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
   done?</q>
</p>
<p>
 <q>I have now arranged that you can be married a second time,</q> replied Thjostolf.
</p>
<p>
 <q>Then you must mean that Thorvald is dead,</q> she said.
</p>
<p>
 <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q>
</p>
Schematron

<sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText |parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q |parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp |parent::tei:stage |parent::tei:cell |parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements.
</sch:report>
Schematron

<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText |parent::tei:figure |parent::tei:note )"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText.
</sch:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element p
{
   att.global.attributes,
   att.declaring.attributes,
   att.fragmentable.attributes,
   att.written.attributes,
   macro.paraContent
}

<pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break)
Member of
Contained by
May contain Empty element
Note

A pb element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the pb element itself.

The type attribute may be used to characterize the page break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page break is word-breaking, or to note the source from which it derives.

Example

Page numbers may vary in different editions of a text.

<p> ... <pb ed="ed2n="145"/>
<!-- Page 145 in edition "ed2" starts here --> ... <pb ed="ed1n="283"/>
<!-- Page 283 in edition "ed1" starts here--> ... </p>
Example

A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute

<body>
 <pb facs="page1.pngn="1"/>
<!-- page1.png contains an image of the page; the text it contains is encoded here -->
 <p>
<!-- ... -->
 </p>
 <pb facs="page2.pngn="2"/>
<!-- similarly, for page 2 -->
 <p>
<!-- ... -->
 </p>
</body>
Content model
<content>
 <empty/>
</content>
Schema Declaration
element pb
{
   att.global.attributes,
   att.typed.attributes,
   att.edition.attributes,
   att.spanning.attributes,
   att.breaking.attributes,
   empty
}

<persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]
Module namesdates — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.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.editLike (@evidence, @instant) 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>Edward</forename>
 <forename>George</forename>
 <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of
 <placeName>Knebworth</placeName>
 </roleName>
</persName>
Schematron

<sch:rule context="//tei:msDesc//tei:persName[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'person_\d+')]">In the
medieval catalogue, the persName element, when a descendant
of msDesc, must have a key matching the pattern
'person_\d+'.</sch:assert>
</sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element persName
{
   att.global.attributes,
   att.datable.attributes,
   att.editLike.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

<physDesc>

<physDesc> (physical description) contains a full physical description of a manuscript, manuscript part, or other object optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
msdescription: msDesc msFrag msPart
May contain
Example
<physDesc>
 <objectDesc form="codex">
  <supportDesc material="perg">
   <support>Parchment.</support>
   <extent>i + 55 leaves
   <dimensions scope="alltype="leaf"
     unit="inch">

     <height></height>
     <width>5⅜</width>
    </dimensions>
   </extent>
  </supportDesc>
  <layoutDesc>
   <layout columns="2">In double columns.</layout>
  </layoutDesc>
 </objectDesc>
 <handDesc>
  <p>Written in more than one hand.</p>
 </handDesc>
 <decoDesc>
  <p>With a few coloured capitals.</p>
 </decoDesc>
</physDesc>
Content model
<content>
 <sequence>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="0"/>

  <classRef expand="sequenceOptional"
   key="model.physDescPart"/>

 </sequence>
</content>
Schema Declaration
element physDesc
{
   att.global.attributes,
   (
      model.pLike*,
      objectDesc?,
      handDesc?,
      typeDesc?,
      scriptDesc?,
      musicNotation?,
      decoDesc?,
      additions?,
      bindingDesc?,
      sealDesc?,
      accMat?
   )
}

<placeName>

<placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names]
Module namesdates — Schema
Attributes 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.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
Member of
Contained by
May contain
Example
<placeName>
 <settlement>Rochester</settlement>
 <region>New York</region>
</placeName>
Example
<placeName>
 <geogName>Arrochar Alps</geogName>
 <region>Argylshire</region>
</placeName>
Example
<placeName>
 <measure>10 miles</measure>
 <offset>Northeast of</offset>
 <settlement>Attica</settlement>
</placeName>
Schematron

<sch:rule context="//tei:msDesc//tei:placeName[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'place_\d+')]">In the medieval
catalogue, the placeName element, when a descendant of
msDesc, must have a key matching the pattern
'place_\d+'.</sch:assert>
</sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element placeName
{
   att.datable.attributes,
   att.editLike.attributes,
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

<postCode>

<postCode> (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. [3.6.2. Addresses]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: address
May contain Character data only
Note

The position and nature of postal codes is highly country-specific; the conventions appropriate to the country concerned should be used.

Example
<postCode>HR1 3LR</postCode>
Example
<postCode>60142-7</postCode>
Content model
<content>
 <textNode/>
</content>
Schema Declaration
element postCode { att.global.attributes, text }

<principal>

<principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) 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
core: bibl
msdescription: msItem
May contain
Example
<principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
element principal
{
   att.global.attributes,
   att.canonical.attributes,
   att.datable.attributes,
   macro.phraseSeq.limited
}

<profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
header: teiHeader
May contain
header: textClass
Note

Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of profileDesc unless these are documenting multiple texts.

Example
<profileDesc>
 <langUsage>
  <language ident="fr">French</language>
 </langUsage>
 <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>
 <settingDesc>
  <setting>
   <name>Paris, France</name>
   <time>Late 19th century</time>
  </setting>
 </settingDesc>
</profileDesc>
Content model
<content>
 <classRef key="model.profileDescPart"
  maxOccurs="unboundedminOccurs="0"/>

</content>
Schema Declaration
element profileDesc { att.global.attributes, model.profileDescPart* }

<projectDesc>

<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
Member of
Contained by
header: encodingDesc
May contain
core: p
Example
<projectDesc>
 <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p>
</projectDesc>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unboundedminOccurs="1"/>

</content>
Schema Declaration
element projectDesc
{
   att.global.attributes,
   att.declarable.attributes,
   model.pLike+
}

<provenance>

<provenance> (provenance) contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript, manuscript part, or other object after its creation but before its acquisition. [10.8. History]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.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.typed (@type, @subtype)
Contained by
msdescription: history
May contain
Example
<provenance>Listed as the property of Lawrence Sterne in 1788.</provenance>
<provenance>Sold at Sothebys in 1899.</provenance>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element provenance
{
   att.global.attributes,
   att.datable.attributes,
   att.typed.attributes,
   macro.specialPara
}

<publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: fileDesc
May contain
Note

Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

Example
<publicationStmt>
 <publisher>C. Muquardt </publisher>
 <pubPlace>Bruxelles &amp; Leipzig</pubPlace>
 <date when="1846"/>
</publicationStmt>
Example
<publicationStmt>
 <publisher>Chadwyck Healey</publisher>
 <pubPlace>Cambridge</pubPlace>
 <availability>
  <p>Available under licence only</p>
 </availability>
 <date when="1992">1992</date>
</publicationStmt>
Example
<publicationStmt>
 <publisher>Zea Books</publisher>
 <pubPlace>Lincoln, NE</pubPlace>
 <date>2017</date>
 <availability>
  <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>
 </availability>
 <ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
</publicationStmt>
Content model
<content>
 <alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="1">

   <classRef key="model.publicationStmtPart.agency"/>
   <classRef key="model.publicationStmtPart.detail"
    maxOccurs="unboundedminOccurs="0"/>

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

 </alternate>
</content>
Schema Declaration
element publicationStmt
{
   att.global.attributes,
   (
      ( model.publicationStmtPart.agency, model.publicationStmtPart.detail* )+
    | model.pLike+
   )
}

<publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
Member of
Contained by
core: bibl imprint
header: publicationStmt
May contain
Note

Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

Example
<imprint>
 <pubPlace>Oxford</pubPlace>
 <publisher>Clarendon Press</publisher>
 <date>1987</date>
</imprint>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element publisher
{
   att.global.attributes,
   att.canonical.attributes,
   macro.phraseSeq
}

<pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Member of
Contained by
core: bibl imprint
header: publicationStmt
May contain
Example
<publicationStmt>
 <publisher>Oxford University Press</publisher>
 <pubPlace>Oxford</pubPlace>
 <date>1989</date>
</publicationStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element pubPlace
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq
}

<q>

<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ascribed.directed (@toWhom) (att.ascribed (@who))
type(type) may be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
Status Optional
Datatype teidata.enumerated
Suggested values include:
spoken
(spoken) representation of speech
thought
(thought) representation of thought, e.g. internal monologue
written
(written) quotation from a written source
soCalled
(so called) authorial distance
foreign
(foreign)
distinct
(distinct) linguistically distinct
term
technical term
emph
(emph) rhetorically emphasized
mentioned
(mentioned) refering to itself, not its normal referent
Member of
Contained by
May contain
Note

May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, q may be thought of as syntactic sugar for hi with a value of rend that indicates the use of such mechanisms as quotation marks.

Example
It is spelled <q>Tübingen</q> — to enter the
letter <q>u</q> with an umlaut hold down the <q>option</q> key and press
<q>0 0 f c</q>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element q
{
   att.global.attributes,
   att.ascribed.directed.attributes,
   attribute type
   {
      "spoken"
    | "thought"
    | "written"
    | "soCalled"
    | "foreign"
    | "distinct"
    | "term"
    | "emph"
    | "mentioned"
    | teidata.enumerated
   }?,
   macro.specialPara
}

<quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective) att.notated (@notation)
Member of
Contained by
May contain
Note

If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the cit element.

Example
Lexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized in his
slogan, <quote>You shall know a word by the company it
keeps</quote>
<ref>(Firth, 1957)</ref>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element quote
{
   att.global.attributes,
   att.typed.attributes,
   att.msExcerpt.attributes,
   att.notated.attributes,
   macro.specialPara
}

<recordHist>

<recordHist> (recorded history) provides information about the source and revision status of the parent manuscript or object description itself. [10.9.1. Administrative Information]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
msdescription: adminInfo
May contain
core: p
header: change
msdescription: source
Example
<recordHist>
 <source>
  <p>Derived from <ref target="#IMEV">IMEV 123</ref> with additional research
     by P.M.W.Robinson</p>
 </source>
 <change when="1999-06-23">
  <name>LDB</name> (editor)
   checked examples against DTD version 3.6
 </change>
</recordHist>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

  <sequence>
   <elementRef key="source"/>
   <elementRef key="change"
    maxOccurs="unboundedminOccurs="0"/>

  </sequence>
 </alternate>
</content>
Schema Declaration
element recordHist
{
   att.global.attributes,
   ( model.pLike+ | ( source, change* ) )
}

<ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links]
Module core — Schema
Attributes att.cReferencing (@cRef) att.declaring (@decls) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.internetMedia (@mimeType) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype)
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second
sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term>
</ref>.
Schematron

<sch:report test="@target and @cRef">Only one of the
attributes @target' and @cRef' may be supplied on <sch:name/>
</sch:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element ref
{
   att.cReferencing.attributes,
   att.declaring.attributes,
   att.global.attributes,
   att.internetMedia.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   macro.paraContent
}

<reg>

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 12. Critical Apparatus]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) 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 regularized, reg may be used alone:

<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg>
</q>
Example

It is also possible to identify the individual responsible for the regularization, and, using the choice and orig elements, to provide both the original and regularized readings:

<q>Please <choice>
  <reg resp="#LB">knock</reg>
  <orig>cnk</orig>
 </choice> if an <choice>
  <reg>answer</reg>
  <orig>nsr</orig>
 </choice> is <choice>
  <reg>required</reg>
  <orig>reqd</orig>
 </choice>
</q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element reg
{
   att.global.attributes,
   att.editLike.attributes,
   att.typed.attributes,
   macro.paraContent
}

<region>

<region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [13.2.3. Place Names]
Module namesdates — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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>
 <region n="ILtype="state">Illinois</region>
</placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element region
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   macro.phraseSeq
}

<relatedItem>

<relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.12.2.7. Related Items]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
targetpoints to the related bibliographic element by means of an absolute or relative URI reference
Status Optional
Datatype teidata.pointer
Member of
Contained by
May contain
msdescription: msDesc
Note

If the target attribute is used to reference the related bibliographic item, the element must be empty.

Example
<biblStruct>
 <monogr>
  <author>Shirley, James</author>
  <title type="main">The gentlemen of Venice</title>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>Readex Microprint</publisher>
   <date>1953</date>
  </imprint>
  <extent>1 microprint card, 23 x 15 cm.</extent>
 </monogr>
 <series>
  <title>Three centuries of drama: English, 1642–1700</title>
 </series>
 <relatedItem type="otherForm">
  <biblStruct>
   <monogr>
    <author>Shirley, James</author>
    <title type="main">The gentlemen of Venice</title>
    <title type="sub">a tragi-comedie presented at the private house in Salisbury
         Court by Her Majesties servants</title>
    <imprint>
     <pubPlace>London</pubPlace>
     <publisher>H. Moseley</publisher>
     <date>1655</date>
    </imprint>
    <extent>78 p.</extent>
   </monogr>
  </biblStruct>
 </relatedItem>
</biblStruct>
Schematron

<sch:report test="@target and count( child::* ) > 0">If the @target attribute on <sch:name/> is used, the
relatedItem element must be empty</sch:report>
<sch:assert test="@target or child::*">A relatedItem element should have either a 'target' attribute
or a child element to indicate the related bibliographic item</sch:assert>
Content model
<content>
 <alternate minOccurs="0">
  <classRef key="model.biblLike"/>
  <classRef key="model.ptrLike"/>
 </alternate>
</content>
Schema Declaration
element relatedItem
{
   att.global.attributes,
   att.typed.attributes,
   attribute target { teidata.pointer }?,
   ( model.biblLike | model.ptrLike )?
}

<repository>

<repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.naming (@role, @nymRef) (att.canonical (@key, @ref))
Contained by
msdescription: altIdentifier msIdentifier
May contain
Example
<msIdentifier>
 <settlement>Oxford</settlement>
 <institution>University of Oxford</institution>
 <repository>Bodleian Library</repository>
 <idno>MS. Bodley 406</idno>
</msIdentifier>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
element repository
{
   att.global.attributes,
   att.naming.attributes,
   macro.phraseSeq.limited
}

<resp>

<resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) 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
core: respStmt
May contain
Note

The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

Example
<respStmt>
 <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>
 <name>Edward Child</name>
</respStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
element resp
{
   att.global.attributes,
   att.canonical.attributes,
   att.datable.attributes,
   macro.phraseSeq.limited
}

<respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
Member of
Contained by
May contain
core: name note resp
namesdates: orgName persName
Example
<respStmt>
 <resp>transcribed from original ms</resp>
 <persName>Claus Huitfeldt</persName>
</respStmt>
Example
<respStmt>
 <resp>converted to XML encoding</resp>
 <name>Alan Morrison</name>
</respStmt>
Content model
<content>
 <sequence>
  <alternate>
   <sequence>
    <elementRef key="resp"
     maxOccurs="unboundedminOccurs="1"/>

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

   </sequence>
   <sequence>
    <classRef key="model.nameLike.agent"
     maxOccurs="unboundedminOccurs="1"/>

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

   </sequence>
  </alternate>
  <elementRef key="note"
   maxOccurs="unboundedminOccurs="0"/>

 </sequence>
</content>
Schema Declaration
element respStmt
{
   att.global.attributes,
   att.canonical.attributes,
   (
      ( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) ),
      note*
   )
}

<revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.docStatus (@status)
Contained by
header: teiHeader
May contain
core: list
header: change
Note

If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any change to record the status at the time of that change. Conventionally change elements should be given in reverse date order, with the most recent change at the start of the list.

Example
<revisionDesc status="embargoed">
 <change when="1991-11-11who="#LB"> deleted chapter 10 </change>
</revisionDesc>
Content model
<content>
 <alternate>
  <elementRef key="list"/>
  <elementRef key="listChange"/>
  <elementRef key="change"
   maxOccurs="unboundedminOccurs="1"/>

 </alternate>
</content>
Schema Declaration
element revisionDesc
{
   att.global.attributes,
   att.docStatus.attributes,
   ( list | listChange | change+ )
}

<rubric>

<rubric> (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 or other object 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, typically in red ink, or by use of different size or type of script, or some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype) att.msExcerpt (@defective)
Member of
Contained by
msdescription: msItem msItemStruct
May contain
Example
<rubric>Nu koma Skyckiu Rym<ex>ur</ex>.</rubric>
<rubric>Incipit liber de consciencia humana a beatissimo Bernardo editus.</rubric>
<rubric>
 <locus>16. f. 28v in margin: </locus>Dicta Cassiodori
</rubric>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element rubric
{
   att.global.attributes,
   att.typed.attributes,
   att.msExcerpt.attributes,
   macro.phraseSeq
}

<scriptDesc>

<scriptDesc> (script description) contains a description of the scripts used in a manuscript or other object. [10.7.2.1. Writing]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
msdescription: physDesc
May contain
core: p
header: scriptNote
msdescription: summary
Example
<scriptDesc>
 <p/>
</scriptDesc>
Example
<scriptDesc>
 <summary>Contains two distinct styles of scripts </summary>
 <scriptNote xml:id="style-1">.</scriptNote>
 <scriptNote xml:id="style-2">.</scriptNote>
</scriptDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

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

  </sequence>
 </alternate>
</content>
Schema Declaration
element scriptDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, scriptNote+ ) )
}

<scriptNote>

<scriptNote> describes a particular script distinguished within the description of a manuscript or similar resource. [10.7.2. Writing, Decoration, and Other Notations]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
Contained by
msdescription: scriptDesc
May contain
Example
<scriptNote scope="sole"/>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element scriptNote
{
   att.global.attributes,
   att.handFeatures.attributes,
   macro.specialPara
}

<seal>

<seal> (seal) contains a description of one seal or similar applied to the object described [10.7.3.2. Seals]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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))
contemporary(contemporary) specifies whether or not the seal is contemporary with the item to which it is affixed
Status Optional
Datatype teidata.xTruthValue
Contained by
msdescription: sealDesc
May contain
core: p
msdescription: decoNote
Example
<seal n="2subtype="cauda_duplex"
 type="pendant">

 <p>The seal of <name>Jens Olufsen</name> in black wax.
   (<ref>DAS 1061</ref>). Legend: <q>S IOHANNES OLAVI</q>.
   Parchment tag on which is written: <q>Woldorp Iohanne G</q>.</p>
</seal>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">

  <classRef key="model.pLike"/>
  <elementRef key="decoNote"/>
 </alternate>
</content>
Schema Declaration
element seal
{
   att.global.attributes,
   att.typed.attributes,
   att.datable.attributes,
   attribute contemporary { teidata.xTruthValue }?,
   ( model.pLike | decoNote )+
}

<sealDesc>

<sealDesc> (seal description) describes the seals or similar items related to the object described, either as a series of paragraphs or as a series of seal elements. [10.7.3.2. Seals]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: condition decoNote seal summary
Example
<sealDesc>
 <seal contemporary="truetype="pendant">
  <p>Green wax vertical oval seal attached at base.</p>
 </seal>
</sealDesc>
Example
<sealDesc>
 <p>Parchment strip for seal in place; seal missing.</p>
</sealDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

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

    <elementRef key="decoNote"/>
    <elementRef key="seal"/>
    <elementRef key="condition"/>
   </alternate>
  </sequence>
 </alternate>
</content>
Schema Declaration
element sealDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, ( decoNote | seal | condition )+ ) )
}

<secFol>

<secFol> (second folio) marks the word or words taken from a fixed point in a codex (typically the beginning of the second leaf) in order to provide a unique identifier for it. [10.3.7. Catchwords, Signatures, Secundo Folio]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Example
<secFol>(con-)versio morum</secFol>
Schematron

<sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element secFol { att.global.attributes, macro.phraseSeq }

<seg>

<seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents]
Module linking — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.segLike (@function) (att.datcat (@datcat, @valueDatcat, @targetDatcat)) (att.fragmentable (@part)) att.typed (@type, @subtype) att.written (@hand) att.notated (@notation)
Member of
Contained by
May contain
Note

The seg element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element.

Example
<seg>When are you leaving?</seg>
<seg>Tomorrow.</seg>
Example
<s>
 <seg rend="capstype="initial-cap">So father's only</seg> glory was the ballfield.
</s>
Example
<seg type="preamble">
 <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>
 <seg>Sinfiotli was the eldest of his sons ...</seg>
 <seg>Borghild, Sigmund's wife, had a brother ... </seg>
</seg>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element seg
{
   att.global.attributes,
   att.segLike.attributes,
   att.typed.attributes,
   att.written.attributes,
   att.notated.attributes,
   macro.paraContent
}

<series>

<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
figures: figure
header: availability idno
transcr: fw
character data
Example
<series xml:lang="de">
 <title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>
 <respStmt>
  <resp>Herausgegeben von</resp>
  <name type="person">Manfred Thaller</name>
  <name type="org">Max-Planck-Institut für Geschichte</name>
 </respStmt>
 <title level="s">Serie A: Historische Quellenkunden</title>
 <biblScope>Band 11</biblScope>
</series>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="biblScope"/>
  <elementRef key="idno"/>
  <elementRef key="textLang"/>
  <classRef key="model.global"/>
  <elementRef key="availability"/>
 </alternate>
</content>
Schema Declaration
element series
{
   att.global.attributes,
   (
      text
    | model.gLiketitlemodel.ptrLikeeditorrespStmtbiblScopeidnotextLangmodel.globalavailability
   )*
}

<settlement>

<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names]
Module namesdates — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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>
 <settlement type="town">Glasgow</settlement>
 <region>Scotland</region>
</placeName>
Schematron

<sch:rule context="//tei:origin//tei:settlement[ancestor::tei:fileDesc[descendant::tei:idno[@type='catalogue']='Western']]">
<sch:assert test="@key[matches(., 'place_\d+')]">In the medieval
catalogue, the settlement element, when a descendant of
origin, must have a key matching the pattern
'place_\d+'.</sch:assert>
</sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element settlement
{
   att.global.attributes,
   att.naming.attributes,
   att.typed.attributes,
   att.datable.attributes,
   macro.phraseSeq
}

<sic>

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Example
for his nose was as sharp as
a pen, and <sic>a Table</sic> of green fields.
Example

If all that is desired is to call attention to the apparent problem in the copy text, sic may be used alone:

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

It is also possible, using the choice and corr elements, to provide a corrected 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?
Example
for his nose was as sharp as
a pen, and <choice>
 <sic>a Table</sic>
 <corr>a' babbld</corr>
</choice> of green fields.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element sic { att.global.attributes, macro.paraContent }

<signatures>

<signatures> (signatures) contains discussion of the leaf or quire signatures found within a codex or similar object. [10.3.7. Catchwords, Signatures, Secundo Folio]
Module msdescription — Schema
Attributes att.typed (@type, @subtype) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Example
<signatures>Quire and leaf signatures in letters, [b]-v, and roman
numerals; those in quires 10 (1) and 17 (s) in red ink and different
from others; every third quire also signed with red crayon in arabic
numerals in the center lower margin of the first leaf recto: "2" for
quire 4 (f. 19), "3" for quire 7 (f. 43); "4," barely visible, for
quire 10 (f. 65), "5," in a later hand, for quire 13 (f. 89), "6," in
a later hand, for quire 16 (f. 113).</signatures>
Schematron

<sch:assert test="ancestor::tei:msDesc or ancestor::tei:egXML">The <sch:name/> element should not be used outside of msDesc.</sch:assert>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element signatures
{
   att.typed.attributes,
   att.global.attributes,
   macro.specialPara
}

<source>

<source> (source) describes the original source for the information contained with a manuscript or object description. [10.9.1.1. Record History]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
msdescription: recordHist
May contain
Example
<source>Derived from <ref>Stanley (1960)</ref>
</source>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element source { att.global.attributes, macro.specialPara }

<sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
Contained by
header: fileDesc
May contain
msdescription: msDesc
Example
<sourceDesc>
 <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>
</sourceDesc>
Example
<sourceDesc>
 <p>Born digital: no previous source exists.</p>
</sourceDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

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

   <classRef key="model.biblLike"/>
   <classRef key="model.sourceDescPart"/>
   <classRef key="model.listLike"/>
  </alternate>
 </alternate>
</content>
Schema Declaration
element sourceDesc
{
   att.global.attributes,
   att.declarable.attributes,
   (
      model.pLike+
    | ( model.biblLike | model.sourceDescPart | model.listLike )+
   )
}
<sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) 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
core: bibl monogr
msdescription: msItem
May contain
Note

Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element funder), who provide the funding but do not necessarily take intellectual responsibility.

Example
<sponsor>Association for Computers and the Humanities</sponsor>
<sponsor>Association for Computational Linguistics</sponsor>
<sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration
element sponsor
{
   att.global.attributes,
   att.canonical.attributes,
   att.datable.attributes,
   macro.phraseSeq.limited
}

<stamp>

<stamp> (stamp) contains a word or phrase describing a stamp or similar device. [10.3.3. Watermarks and Stamps]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) 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
<rubric>Apologyticu TTVLLIANI AC IGNORATIA IN XPO IHV<lb/>
SI NON LICET<lb/>
NOBIS RO<lb/>
manii imperii <stamp>Bodleian stamp</stamp>
 <lb/>
</rubric>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element stamp
{
   att.global.attributes,
   att.typed.attributes,
   att.datable.attributes,
   macro.phraseSeq
}

<street>

<street> contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.6.2. Addresses]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: address
May contain
Note

The order and presentation of house names and numbers and street names, etc., may vary considerably in different countries. The encoding should reflect the order which is appropriate in the country concerned.

Example
<street>via della Faggiola, 36</street>
Example
<street>
 <name>Duntaggin</name>, 110 Southmoor Road
</street>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element street { att.global.attributes, macro.phraseSeq }

<subst>

<subst> (substitution) groups one or more deletions (or surplus text) with one or more additions when the combination is to be regarded as a single intervention in the text. [11.3.1.5. Substitutions]
Module transcr — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.transcriptional (@status, @cause, @seq) (att.editLike (@evidence, @instant)) (att.written (@hand)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May contain
core: add del lb pb
transcr: fw
Example
... are all included. <del hand="#RG">It is</del>
<subst>
 <add>T</add>
 <del>t</del>
</subst>he expressed
Example
that he and his Sister Miſs D — <lb/>who always lived with him, wd. be <subst>
 <del>very</del>
 <lb/>
 <add>principally</add>
</subst> remembered in her Will.
Example
<ab>τ<subst>
  <add place="above">ῶν</add>
  <del>α</del>
 </subst>
συνκυρόντ<subst>
  <add place="above">ων</add>
  <del>α</del>
 </subst>
ἐργαστηρί<subst>
  <add place="above">ων</add>
  <del>α</del>
 </subst>
</ab>
Example
<subst>
 <del>
  <gap quantity="5reason="illegible"
   unit="character"/>

 </del>
 <add>apple</add>
</subst>
Schematron

<sch:assert test="child::tei:add and (child::tei:del or child::tei:surplus)">
<sch:name/> must have at least one child add and at least one child del or surplus</sch:assert>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">

  <elementRef key="add"/>
  <elementRef key="surplus"/>
  <elementRef key="del"/>
  <classRef key="model.milestoneLike"/>
 </alternate>
</content>
Schema Declaration
element subst
{
   att.global.attributes,
   att.transcriptional.attributes,
   att.dimensions.attributes,
   ( add | surplus | del | model.milestoneLike )+
}

<summary>

<summary> contains an overview of the available information concerning some aspect of an item or object (for example, its intellectual content, history, layout, typography etc.) as a complement or alternative to the more detailed information carried by more specific elements. [10.6. Intellectual Content]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
May contain
Example
<summary>This item consists of three books with a prologue and an epilogue.
</summary>
Example
<typeDesc>
 <summary>Uses a mixture of Roman and Black Letter types.</summary>
 <typeNote>Antiqua typeface, showing influence of Jenson's Venetian
   fonts.</typeNote>
 <typeNote>The black letter face is a variant of Schwabacher.</typeNote>
</typeDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element summary { att.global.attributes, macro.specialPara }

<supplied>

<supplied> (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Module transcr — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
reasonone or more words indicating why the text has had to be supplied, e.g. overbinding, faded-ink, lost-folio, omitted-in-original.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May contain
Note

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
I am dr Sr yr
<supplied reason="illegible"
 source="#amanuensis_copy">
very humble Servt</supplied>
Sydney Smith
Example
<supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element supplied
{
   att.global.attributes,
   att.editLike.attributes,
   att.dimensions.attributes,
   attribute reason { list { teidata.word+ } }?,
   macro.paraContent
}

<support>

<support> (support) contains a description of the materials etc. which make up the physical support for the written part of a manuscript or other object. [10.7.1. Object Description]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
msdescription: supportDesc
May contain
Example
<objectDesc form="roll">
 <supportDesc>
  <support> Parchment roll with <material>silk</material> ribbons.
  </support>
 </supportDesc>
</objectDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element support { att.global.attributes, macro.specialPara }

<supportDesc>

<supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript or other object. [10.7.1. Object Description]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
materialThe material composing the majority of the support
Status Recommended
Datatype teidata.word
Suggested values include:
perg
The object is composed of parchment or vellum
chart
The object is composed of any kind of paper. Give more details, if any, in a child support element.
papyrus
The object is composed of papyrus.
palm
The object is composed of palm leaves.
mixed
The object is composed of a combination of paper and parchment. The nature of the combination should be specified in the support element.
other
The object is composed of another material (e.g. wood).
unknown
The material of which is object is composed is not known.
Contained by
msdescription: objectDesc
May contain
core: p
header: extent
Example
<supportDesc>
 <support> Parchment roll with <material>silk</material> ribbons.
 </support>
</supportDesc>
Schematron

<sch:rule context="//tei:sourceDesc/tei:msDesc[not(tei:msPart)]"
 see="https://msdesc.github.io/consolidated-tei-schema/msdesc.html#supportdesc">

<sch:assert role="warn"
 test="tei:physDesc/tei:objectDesc/tei:supportDesc[@material]">
The material (parchment, paper, etc.) of a manuscript should be recorded
in the supportDesc element, with a material attribute.
</sch:assert>
</sch:rule>
<sch:rule context="//tei:sourceDesc/tei:msDesc/tei:msPart">
<sch:assert role="warn"
 test=" tei:physDesc/tei:objectDesc/tei:supportDesc[@material] or ancestor::tei:msDesc/tei:physDesc/tei:objectDesc/tei:supportDesc[@material] ">
The material (parchment, paper, etc.) of each part should be recorded in
the supportDesc element, with a material attribute, unless it has been
described for the entire manuscript.
</sch:assert>
</sch:rule>
Content model
<content>
 <alternate maxOccurs="1minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

  <sequence maxOccurs="1minOccurs="1">
   <elementRef key="supportminOccurs="0"/>
   <elementRef key="extentminOccurs="0"/>
   <elementRef key="foliation"
    maxOccurs="unboundedminOccurs="0"/>

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

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

  </sequence>
 </alternate>
</content>
Schema Declaration
element supportDesc
{
   att.global.attributes,
   attribute material
   {
      "perg"
    | "chart"
    | "papyrus"
    | "palm"
    | "mixed"
    | "other"
    | "unknown"
    | teidata.word
   }?,
   ( model.pLike+ | ( support?, extent?, foliation*, collation?, condition? ) )
}

<surface>

<surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Module transcr — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.declaring (@decls) att.typed (@type, @subtype)
attachmentdescribes the method by which this surface is or was connected to the main surface
Status Optional
Datatype teidata.enumerated
Sample values include:
glued
glued in place
pinned
pinned or stapled in place
sewn
sewn in place
flippingindicates whether the surface is attached and folded in such a way as to provide two writing surfaces
Status Optional
Datatype teidata.truthValue
Contained by
May contain
Note

The surface element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc.

The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high.

The surface element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every zone element contained by this element are to be understood with reference to the same grid.

Where it is useful or meaningful to do so, any grouping of multiple surface elements may be indicated using the surfaceGrp element.

Example
<facsimile>
 <surface lrx="200lry="300ulx="0uly="0">
  <graphic url="Bovelles-49r.png"/>
 </surface>
</facsimile>
Content model
<content>
 <sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">

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

   <alternate>
    <elementRef key="zone"/>
    <elementRef key="line"/>
    <elementRef key="path"/>
    <elementRef key="surface"/>
    <elementRef key="surfaceGrp"/>
   </alternate>
   <classRef key="model.global"
    maxOccurs="unboundedminOccurs="0"/>

  </sequence>
 </sequence>
</content>
Schema Declaration
element surface
{
   att.global.attributes,
   att.coordinated.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   attribute attachment { teidata.enumerated }?,
   attribute flipping { teidata.truthValue }?,
   (
      ( model.global | model.labelLike | model.graphicLike )*,
      ( ( zone | line | path | surface | surfaceGrp ), model.global* )*
   )
}

<surfaceGrp>

<surfaceGrp> (surface group) defines any kind of useful grouping of written surfaces, for example the recto and verso of a single leaf, which the encoder wishes to treat as a single unit. [11.1. Digital Facsimiles]
Module transcr — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype)
Contained by
May contain
core: gap lb note pb
figures: figure
transcr: fw surface surfaceGrp
Note

Where it is useful or meaningful to do so, any grouping of multiple surface elements may be indicated using the surfaceGrp elements.

Example
<sourceDoc>
 <surfaceGrp>
  <surface lrx="200lry="300ulx="0"
   uly="0">

   <graphic url="Bovelles-49r.png"/>
  </surface>
  <surface lrx="200lry="300ulx="0"
   uly="0">

   <graphic url="Bovelles-49v.png"/>
  </surface>
 </surfaceGrp>
</sourceDoc>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">

  <classRef key="model.global"/>
  <elementRef key="surface"/>
  <elementRef key="surfaceGrp"/>
 </alternate>
</content>
Schema Declaration
element surfaceGrp
{
   att.global.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   ( model.global | surface | surfaceGrp )+
}

<surname>

<surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [13.2.1. Personal Names]
Module namesdates — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.typed (@type, @subtype)
Member of
Contained by
May contain
Example
<surname type="combine">St John Stevas</surname>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element surname
{
   att.global.attributes,
   att.personal.attributes,
   att.typed.attributes,
   macro.phraseSeq
}

<surrogates>

<surrogates> (surrogates) contains information about any representations of the manuscript or other object being described which may exist in the holding institution or elsewhere. [10.9. Additional Information]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
msdescription: additional
May contain
Example
<surrogates>
 <bibl>
  <title type="gmd">diapositive</title>
  <idno>AM 74 a, fol.</idno>
  <date>May 1984</date>
 </bibl>
 <bibl>
  <title type="gmd">b/w prints</title>
  <idno>AM 75 a, fol.</idno>
  <date>1972</date>
 </bibl>
</surrogates>
Schematron

<sch:rule context="//tei:surrogates/tei:bibl">
<sch:report role="warn"
 test="contains(@type, 'fascimile')">
The type attribute of "<sch:value-of select="@type"/>" contains a typo (fascimile should be facsimile).
</sch:report>
</sch:rule>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element surrogates { att.global.attributes, macro.specialPara }

<taxonomy>

<taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
May contain
header: category taxonomy
msdescription: msDesc
Note

Nested taxonomies are common in many fields, so the taxonomy element can be nested.

Example
<taxonomy xml:id="tax.b">
 <bibl>Brown Corpus</bibl>
 <category xml:id="tax.b.a">
  <catDesc>Press Reportage</catDesc>
  <category xml:id="tax.b.a1">
   <catDesc>Daily</catDesc>
  </category>
  <category xml:id="tax.b.a2">
   <catDesc>Sunday</catDesc>
  </category>
  <category xml:id="tax.b.a3">
   <catDesc>National</catDesc>
  </category>
  <category xml:id="tax.b.a4">
   <catDesc>Provincial</catDesc>
  </category>
  <category xml:id="tax.b.a5">
   <catDesc>Political</catDesc>
  </category>
  <category xml:id="tax.b.a6">
   <catDesc>Sports</catDesc>
  </category>
 </category>
 <category xml:id="tax.b.d">
  <catDesc>Religion</catDesc>
  <category xml:id="tax.b.d1">
   <catDesc>Books</catDesc>
  </category>
  <category xml:id="tax.b.d2">
   <catDesc>Periodicals and tracts</catDesc>
  </category>
 </category>
</taxonomy>
Example
<taxonomy>
 <category xml:id="literature">
  <catDesc>Literature</catDesc>
  <category xml:id="poetry">
   <catDesc>Poetry</catDesc>
   <category xml:id="sonnet">
    <catDesc>Sonnet</catDesc>
    <category xml:id="shakesSonnet">
     <catDesc>Shakespearean Sonnet</catDesc>
    </category>
    <category xml:id="petraSonnet">
     <catDesc>Petrarchan Sonnet</catDesc>
    </category>
   </category>
   <category xml:id="haiku">
    <catDesc>Haiku</catDesc>
   </category>
  </category>
  <category xml:id="drama">
   <catDesc>Drama</catDesc>
  </category>
 </category>
 <category xml:id="meter">
  <catDesc>Metrical Categories</catDesc>
  <category xml:id="feet">
   <catDesc>Metrical Feet</catDesc>
   <category xml:id="iambic">
    <catDesc>Iambic</catDesc>
   </category>
   <category xml:id="trochaic">
    <catDesc>trochaic</catDesc>
   </category>
  </category>
  <category xml:id="feetNumber">
   <catDesc>Number of feet</catDesc>
   <category xml:id="pentameter">
    <catDesc>>Pentameter</catDesc>
   </category>
   <category xml:id="tetrameter">
    <catDesc>>Tetrameter</catDesc>
   </category>
  </category>
 </category>
</taxonomy>
<!-- elsewhere in document -->
<lg ana="#shakesSonnet #iambic #pentameter">
 <l>Shall I compare thee to a summer's day</l>
<!-- ... -->
</lg>
Content model
<content>
 <alternate>
  <alternate>
   <alternate maxOccurs="unbounded"
    minOccurs="1">

    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
   <sequence>
    <alternate maxOccurs="unbounded"
     minOccurs="1">

     <classRef key="model.descLike"
      maxOccurs="1minOccurs="1"/>

     <elementRef key="equivmaxOccurs="1"
      minOccurs="1"/>

     <elementRef key="glossmaxOccurs="1"
      minOccurs="1"/>

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

     <elementRef key="category"/>
     <elementRef key="taxonomy"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence>
   <classRef key="model.biblLike"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">

    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
  </sequence>
 </alternate>
</content>
Schema Declaration
element taxonomy
{
   att.global.attributes,
   (
      (
         ( category | taxonomy )+
       | ( ( model.descLike | equiv | gloss )+, ( category | taxonomy )* )
      )
    | ( model.biblLike, ( category | taxonomy )* )
   )
}

<TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple TEI elements may be combined within a TEI (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Module textstructure — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type, @subtype)
versionspecifies the version number of the TEI Guidelines against which this document is valid.
Status Optional
Datatype teidata.version
Note

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

Contained by
textstructure: TEI
May contain
header: teiHeader
textstructure: TEI text
transcr: facsimile
Note

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>The shortest TEI Document Imaginable</title>
   </titleStmt>
   <publicationStmt>
    <p>First published as part of TEI P2, this is the P5
         version using a namespace.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <text>
  <body>
   <p>This is about the shortest TEI document imaginable.</p>
  </body>
 </text>
</TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>A TEI Document containing four page images </title>
   </titleStmt>
   <publicationStmt>
    <p>Unpublished demonstration file.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <facsimile>
  <graphic url="page1.png"/>
  <graphic url="page2.png"/>
  <graphic url="page3.png"/>
  <graphic url="page4.png"/>
 </facsimile>
</TEI>
Schematron

<sch:rule context="tei:TEI">
<sch:assert role="fatal"
 test="matches(@xml:id, '^manuscript_\d+$') or contains(base-uri(.), 'genizah-mss')">
The root TEI element must have an @xml:id beginning with
"manuscript_" then a number (which must also be unique
across the entire catalogue).
</sch:assert>
<sch:assert role="fatal"
 test="matches(@xml:id, '^volume_\d+$') or not(contains(base-uri(.), 'genizah-mss'))">
The root TEI element must have an @xml:id beginning with
"volume_" then a number (which must also be unique
across the entire catalogue).
</sch:assert>
</sch:rule>
Schematron

<sch:ns prefix="tei"
 uri="http://www.tei-c.org/ns/1.0"/>

<sch:ns prefix="xs"
 uri="http://www.w3.org/2001/XMLSchema"/>
Schematron

<sch:ns prefix="rng"
 uri="http://relaxng.org/ns/structure/1.0"/>

<sch:ns prefix="rna"
 uri="http://relaxng.org/ns/compatibility/annotations/1.0"/>
Content model
<content>
 <sequence maxOccurs="1minOccurs="1">
  <elementRef key="teiHeader"/>
  <alternate maxOccurs="1minOccurs="1">
   <sequence maxOccurs="1minOccurs="1">
    <classRef key="model.resource"
     maxOccurs="unboundedminOccurs="1"/>

    <elementRef key="TEI"
     maxOccurs="unboundedminOccurs="0"/>

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

  </alternate>
 </sequence>
</content>
Schema Declaration
element TEI
{
   att.global.attributes,
   att.typed.attributes,
   attribute version { teidata.version }?,
   ( teiHeader, ( ( model.resource+, TEI* ) | TEI+ ) )
}

<teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
textstructure: TEI
May contain
derived-module-msdesc: include
Note

One of the few elements unconditionally required in any TEI document.

Example
<teiHeader>
 <fileDesc>
  <titleStmt>
   <title>Shakespeare: the first folio (1623) in electronic form</title>
   <author>Shakespeare, William (1564–1616)</author>
   <respStmt>
    <resp>Originally prepared by</resp>
    <name>Trevor Howard-Hill</name>
   </respStmt>
   <respStmt>
    <resp>Revised and edited by</resp>
    <name>Christine Avern-Carr</name>
   </respStmt>
  </titleStmt>
  <publicationStmt>
   <distributor>Oxford Text Archive</distributor>
   <address>
    <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
   </address>
   <idno type="OTA">119</idno>
   <availability>
    <p>Freely available on a non-commercial basis.</p>
   </availability>
   <date when="1968">1968</date>
  </publicationStmt>
  <sourceDesc>
   <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
       1968)</bibl>
  </sourceDesc>
 </fileDesc>
 <encodingDesc>
  <projectDesc>
   <p>Originally prepared for use in the production of a series of old-spelling
       concordances in 1968, this text was extensively checked and revised for use during the
       editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
  </projectDesc>
  <editorialDecl>
   <correction>
    <p>Turned letters are silently corrected.</p>
   </correction>
   <normalization>
    <p>Original spelling and typography is retained, except that long s and ligatured
         forms are not encoded.</p>
   </normalization>
  </editorialDecl>
  <refsDecl xml:id="ASLREF">
   <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
    replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">

    <p>A reference is created by assembling the following, in the reverse order as that
         listed here: <list>
      <item>the <att>n</att> value of the preceding <gi>lb</gi>
      </item>
      <item>a period</item>
      <item>the <att>n</att> value of the ancestor <gi>div2</gi>
      </item>
      <item>a space</item>
      <item>the <att>n</att> value of the parent <gi>div1</gi>
      </item>
     </list>
    </p>
   </cRefPattern>
  </refsDecl>
 </encodingDesc>
 <revisionDesc>
  <list>
   <item>
    <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
   <item>
    <date when="1989-03-01">1 Mar 89</date> LB made new file</item>
  </list>
 </revisionDesc>
</teiHeader>
Content model
<content>
 <sequence>
  <elementRef key="fileDesc"/>
  <classRef key="model.teiHeaderPart"
   maxOccurs="unboundedminOccurs="0"/>

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

 </sequence>
</content>
Schema Declaration
element teiHeader
{
   att.global.attributes,
   ( fileDesc, model.teiHeaderPart*, revisionDesc? )
}

<term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.canonical (@key, @ref) att.sortable (@sortKey) att.cReferencing (@cRef)
Member of
Contained by
May contain
Note

When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a term element by means of its target attribute.

In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The term element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the term element to be used by practitioners of any persuasion.

As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

Example
A computational device that infers structure
from grammatical strings of words is known as a <term>parser</term>, and much of the history
of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term rend="scxml:id="TDPV1">discoursal point of view</term> as
<gloss target="#TDPV1">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>
Example
We may define <term ref="#TDPV2rend="sc">discoursal point of view</term> as
<gloss xml:id="TDPV2">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>
Example
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2rend="sc">discoursal point of view</term> below.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element term
{
   att.global.attributes,
   att.declaring.attributes,
   att.pointing.attributes,
   att.typed.attributes,
   att.canonical.attributes,
   att.sortable.attributes,
   att.cReferencing.attributes,
   macro.phraseSeq
}

<text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]
Module textstructure — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declaring (@decls) att.typed (@type, @subtype) att.written (@hand)
Member of
Contained by
textstructure: TEI
May contain
core: gap lb note pb
figures: figure
textstructure: body
transcr: fw
Note

This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.

Example
<text>
 <front>
  <docTitle>
   <titlePart>Autumn Haze</titlePart>
  </docTitle>
 </front>
 <body>
  <l>Is it a dragonfly or a maple leaf</l>
  <l>That settles softly down upon the water?</l>
 </body>
</text>
Example

The body of a text may be replaced by a group of nested texts, as in the following schematic:

<text>
 <front>
<!-- front matter for the whole group -->
 </front>
 <group>
  <text>
<!-- first text -->
  </text>
  <text>
<!-- second text -->
  </text>
 </group>
</text>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   maxOccurs="unboundedminOccurs="0"/>

  <sequence minOccurs="0">
   <elementRef key="front"/>
   <classRef key="model.global"
    maxOccurs="unboundedminOccurs="0"/>

  </sequence>
  <alternate>
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   maxOccurs="unboundedminOccurs="0"/>

  <sequence minOccurs="0">
   <elementRef key="back"/>
   <classRef key="model.global"
    maxOccurs="unboundedminOccurs="0"/>

  </sequence>
 </sequence>
</content>
Schema Declaration
element text
{
   att.global.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   att.written.attributes,
   (
      model.global*,
      ( front, model.global* )?,
      ( body | group ),
      model.global*,
      ( back, model.global* )?
   )
}

<textClass>

<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.declarable (@default)
Member of
Contained by
header: profileDesc
May contain
header: keywords
Example
<taxonomy>
 <category xml:id="acprose">
  <catDesc>Academic prose</catDesc>
 </category>
<!-- other categories here -->
</taxonomy>
<!-- ... -->
<textClass>
 <catRef target="#acprose"/>
 <classCode scheme="http://www.udcc.org">001.9</classCode>
 <keywords scheme="http://authorities.loc.gov">
  <list>
   <item>End of the world</item>
   <item>History - philosophy</item>
  </list>
 </keywords>
</textClass>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <elementRef key="classCode"/>
  <elementRef key="catRef"/>
  <elementRef key="keywords"/>
 </alternate>
</content>
Schema Declaration
element textClass
{
   att.global.attributes,
   att.declarable.attributes,
   ( classCode | catRef | keywords )*
}

<textLang>

<textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.6.6. Languages and Writing Systems]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
mainLang(main language) supplies a code which identifies the chief language used in the bibliographic work.
Status Optional
Datatype teidata.language
otherLangs(other languages) one or more codes identifying any other languages used in the bibliographic work.
Status Optional
Datatype 0–∞ occurrences of teidata.language separated by whitespace
Member of
Contained by
May contain
Note

This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for all other TEI elements, such information should be provided by means of the global xml:lang attribute attached to the element containing the description.

In all cases, languages should be identified by means of a standardized ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a <language> element in the TEI header.

Example
<textLang mainLang="enotherLangs="la"> Predominantly in English with Latin
glosses</textLang>
Schematron

<sch:rule context="//tei:msItem">
<sch:assert role="warn"
 test=" tei:textLang or ancestor::tei:msContents/tei:textLang or ancestor::tei:msItem/tei:textLang or ( tei:msItem and (every $i in tei:msItem satisfies $i/descendant-or-self::tei:textLang) ) ">
The language of each item should be recorded in a textLang element,
unless it has been described for the entire manuscript or part. Use
'und' for undetermined or 'zxx' if there is no linguistic content.
</sch:assert>
</sch:rule>
<sch:rule context="//tei:textLang">
<sch:assert role="error"
 test="@mainLang and string-length(normalize-space(string())) gt 0">
The predominant language must be recorded in
using a code in a mainLang attribute (and an otherLang
attribute if there are other languages) and described as
text within the textLang element.
</sch:assert>
</sch:rule>
<sch:rule context="//tei:textLang/@mainLang | //tei:textLang/@otherLangs | //@xml:lang">
<sch:assert role="error"
 test="every $code in tokenize(., ' ') satisfies matches($code, '^[a-z]{2,3}(-|$)')">
Codes in <sch:value-of select="name(.)"/>
attributes must conform to BCP 47
(https://tools.ietf.org/html/bcp47), starting with an ISO
639 code for the language, then optionally further codes for
the script (ISO 15924), region, transliteration, etc.
</sch:assert>
</sch:rule>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element textLang
{
   att.global.attributes,
   attribute mainLang { teidata.language }?,
   attribute otherLangs { list { teidata.language* } }?,
   macro.specialPara
}

<title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) 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)
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
Status Optional
Datatype teidata.enumerated
Suggested values include:
main
The title is the main title
sub
The title is a subtitle or title of a part
alt
The title is an alternate title, translation, or alias
short
The title is an abbreviated form of the main title
desc
The title is a descriptive paraphrase of the work functioning as a title
collection
The title is of a collection
Note

This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single title element.

levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
Status Optional
Datatype teidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
Note

The level of a title is sometimes implied by its context: for example, a title appearing directly within an analytic element is ipso facto of level ‘a’, and one appearing within a series element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

Member of
Contained by
May contain
Note

The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

Example
<title>Information Technology and the Research Process: Proceedings of
a conference held at Cranfield Institute of Technology, UK,
18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable
edition</title>
Example
<title type="full">
 <title type="main">Synthèse</title>
 <title type="sub">an international journal for
   epistemology, methodology and history of
   science</title>
</title>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element title
{
   att.global.attributes,
   att.typed.attribute.subtype,
   att.canonical.attributes,
   att.datable.attributes,
   attribute type
   {
      "main"
    | "sub"
    | "alt"
    | "short"
    | "desc"
    | "collection"
    | teidata.enumerated
   }?,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   macro.paraContent
}

<titleStmt>

<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
Module header — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: fileDesc
May contain
Example
<titleStmt>
 <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
 <respStmt>
  <resp>compiled by</resp>
  <name>P.J. Lucas</name>
 </respStmt>
</titleStmt>
Content model
<content>
 <sequence>
  <elementRef key="title"
   maxOccurs="unboundedminOccurs="1"/>

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

 </sequence>
</content>
Schema Declaration
element titleStmt { att.global.attributes, ( title+, model.respLike* ) }

<typeDesc>

<typeDesc> (typeface description) contains a description of the typefaces or other aspects of the printing of an incunable or other printed source. [10.7.2.1. Writing]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: summary typeNote
Example
<typeDesc>
 <p>Uses an unidentified black letter font, probably from the
   15th century</p>
</typeDesc>
Example
<typeDesc>
 <summary>Contains a mixture of blackletter and Roman (antiqua) typefaces</summary>
 <typeNote xml:id="Frak1">Blackletter face, showing
   similarities to those produced in Wuerzburg after 1470.</typeNote>
 <typeNote xml:id="Rom1">Roman face of Venetian origins.</typeNote>
</typeDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unboundedminOccurs="1"/>

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

  </sequence>
 </alternate>
</content>
Schema Declaration
element typeDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, typeNote+ ) )
}

<typeNote>

<typeNote> (typographic note) describes a particular font or other significant typographic feature distinguished within the description of a printed resource. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope)
Contained by
msdescription: typeDesc
May contain
Example
<typeNote scope="sole"> Printed in an Antiqua typeface showing strong Italianate influence.
</typeNote>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration
element typeNote
{
   att.global.attributes,
   att.handFeatures.attributes,
   macro.specialPara
}

<unclear>

<unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions]
Module core — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.editLike (@evidence, @instant) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
reasonindicates why the material is hard to transcribe.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
illegible
(illegible)
inaudible
(inaudible)
faded
(faded)
background_noise
(background noise)
eccentric_ductus
(eccentric ductus) indicates illegibility due to an unusual, awkward, or incompetent execution of a glyph or glyphs
<div>
 <head>Rx</head>
 <p>500 mg <unclear reason="illegible">placebo</unclear>
 </p>
</div>
Note

One or more words may be used to describe the reason; usually each word will refer to a single cause.

agentWhere the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
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 contain
Note

The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 21. Certainty, Precision, and Responsibility.

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.

The hand attribute points to a definition of the hand concerned, as further discussed in section 11.3.2.1. Document Hands.

Example
<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
element unclear
{
   att.global.attributes,
   att.editLike.attributes,
   att.dimensions.attributes,
   attribute reason
   {
      list
      {
         (
            "illegible"
          | "inaudible"
          | "faded"
          | "background_noise"
          | "eccentric_ductus"
          | teidata.enumerated
         )+
      }
   }?,
   attribute agent { teidata.enumerated }?,
   macro.paraContent
}

<watermark>

<watermark> (watermark) contains a word or phrase describing a watermark or similar device. [10.3.3. Watermarks and Stamps]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Example
<support>
 <p>
  <material>Rag paper</material> with <watermark>anchor</watermark> watermark</p>
</support>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration
element watermark { att.global.attributes, macro.phraseSeq }

<width>

<width> (width) contains a measurement of an object along the axis parallel to its bottom, e.g. perpendicular to the spine of a book or codex. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
Member of
Contained by
May contain Character data only
Note

If used to specify the depth 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 ‘depth’ axis.

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

<zone>

<zone> defines any two-dimensional area within a surface element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Module transcr — Schema
Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.typed (@type, @subtype) att.written (@hand)
rotateindicates the amount by which this zone has been rotated clockwise, with respect to the normal orientation of the parent surface element as implied by the dimensions given in the msDesc element or by the coordinates of the surface itself. The orientation is expressed in arc degrees.
Status Optional
Datatype teidata.count
Default 0
Member of
Contained by
transcr: surface zone
May contain
figures: figure formula
linking: seg
transcr: damage fw surface zone
character data
Note

The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface.

A graphic element contained by a zone represents the whole of the zone.

A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface.

A zone is always a closed polygon. Repeating the initial coordinate at the end of the sequence is optional. To encode an unclosed path, use the <path> element.

Example
<surface lrx="0lry="0ulx="14.54"
 uly="16.14">

 <graphic url="stone.jpg"/>
 <zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375 11.4422,6.7125 8.21722,8.3125 6.2,7.65"/>
</surface>

This example defines a non-rectangular zone: see the illustration in section [ID PH-surfzone in TEI Guidelines].

Example
<facsimile>
 <surface lrx="400lry="280ulx="50"
  uly="20">

  <zone lrx="500lry="321ulx="0uly="0">
   <graphic url="graphic.png"/>
  </zone>
 </surface>
</facsimile>

This example defines a zone which has been defined as larger than its parent surface in order to match the dimensions of the graphic it contains.

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

  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.global"/>
  <elementRef key="surface"/>
  <classRef key="model.linePart"/>
 </alternate>
</content>
Schema Declaration
element zone
{
   att.global.attributes,
   att.coordinated.attributes,
   att.typed.attributes,
   att.written.attributes,
   attribute rotate { teidata.count }?,
   (
      text
    | model.gLikemodel.graphicLikemodel.globalsurfacemodel.linePart
   )*
}

Schema msdesc: Model classes

model.addressLike

model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]
Module tei — Schema
Used by
Members address email

model.addrPart

model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.6.2. Addresses]
Module tei — Schema
Used by
Members model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat] model.persNamePart [addName forename surname] model.placeStateLike [model.placeNamePart [country district geogName placeName region settlement] ] idno] addrLine postCode street

model.attributable

model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]
Module tei — Schema
Used by
Members model.quoteLike [cit quote]

model.availabilityPart

model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]
Module tei — Schema
Used by
Members licence

model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]
Module tei — Schema
Used by
Members bibl biblStruct listBibl msDesc

model.biblPart

model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References]
Module tei — Schema
Used by
Members model.imprintPart [biblScope distributor pubPlace publisher] model.respLike [author editor funder principal respStmt sponsor] availability bibl citedRange decoNote edition explicit extent incipit msIdentifier relatedItem series textLang

model.choicePart

model.choicePart groups elements (other than choice itself) which can be used within a choice alternation. [3.5. Simple Editorial Changes]
Module tei — Schema
Used by
Members abbr am corr ex expan orig reg seg sic supplied unclear

model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Module tei — Schema
Used by
Members model.divPart [model.lLike [l] model.pLike [p] lg] model.inter [model.attributable [model.quoteLike [cit quote] ] model.biblLike [bibl biblStruct listBibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list] model.oddDecl model.stageLike] include q
Note

This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

model.dateLike

model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates]
Module tei — Schema
Used by
Members date

model.descLike

model.descLike groups elements which contain a description of their function.
Module tei — Schema
Used by
Members desc

model.dimLike

model.dimLike groups elements which describe a measurement forming part of the physical dimensions of some object.
Module tei — Schema
Used by
Members depth height width

model.divBottom

model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]
Module tei — Schema
Used by
Members model.divBottomPart model.divWrapper

model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Module tei — Schema
Used by
Members div

model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Module tei — Schema
Used by
Members model.lLike [l] model.pLike [p] lg
Note

Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

model.divTop

model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]
Module tei — Schema
Used by
Members model.divTopPart [model.headLike [head] ] model.divWrapper

model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]
Module tei — Schema
Used by
Members model.headLike [head]

model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
Module tei — Schema
Used by
Members foreign term title

model.encodingDescPart

model.encodingDescPart groups elements which may be used inside encodingDesc and appear multiple times.
Module tei — Schema
Used by
Members classDecl projectDesc

model.global

model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
Module tei — Schema
Used by
Members model.global.edit [gap] model.global.meta model.milestoneLike [fw lb pb] model.noteLike [note] figure

model.global.edit

model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]
Module tei — Schema
Used by
Members gap

model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]
Module tei — Schema
Used by
Members formula graphic

model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Module tei — Schema
Used by
Members head

model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
Module tei — Schema
Used by
Members model.emphLike [foreign term title] model.hiLike [hi q]

model.hiLike

model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]
Module tei — Schema
Used by
Members hi q

model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]
Module tei — Schema
Used by
Members biblScope distributor pubPlace publisher

model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
Module tei — Schema
Used by
Members model.attributable [model.quoteLike [cit quote] ] model.biblLike [bibl biblStruct listBibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list] model.oddDecl model.stageLike

model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Module tei — Schema
Used by
Members desc label

model.limitedPhrase

model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
Module tei — Schema
Used by
Members model.emphLike [foreign term title] model.hiLike [hi q] model.pPart.data [model.addressLike [address email] model.dateLike [date] model.measureLike [depth dim geo height measure num width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat] model.persNamePart [addName forename surname] model.placeStateLike [model.placeNamePart [country district geogName placeName region settlement] ] idno] ] model.pPart.editorial [abbr am choice ex expan subst] model.pPart.msdesc [catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml model.ptrLike [ref]

model.linePart

model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element.
Module tei — Schema
Used by
Members model.hiLike [hi q] add choice damage del seg unclear zone

model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Module tei — Schema
Used by
Members list

model.lLike

model.lLike groups elements representing metrical components such as verse lines.
Module tei — Schema
Used by
Members l

model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.6.3. Numbers and Measures]
Module tei — Schema
Used by
Members depth dim geo height measure num width

model.milestoneLike

model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.11.3. Milestone Elements]
Module tei — Schema
Used by
Members fw lb pb

model.msItemPart

model.msItemPart groups elements which can appear within a manuscript item description.
Module tei — Schema
Used by
Members model.biblLike [bibl biblStruct listBibl msDesc] model.msQuoteLike [colophon explicit finalRubric incipit rubric title] model.quoteLike [cit quote] model.respLike [author editor funder principal respStmt sponsor] decoNote filiation idno msItem msItemStruct textLang

model.msQuoteLike

model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
Module tei — Schema
Used by
Members colophon explicit finalRubric incipit rubric title

model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Module tei — Schema
Used by
Members model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat] model.persNamePart [addName forename surname] model.placeStateLike [model.placeNamePart [country district geogName placeName region settlement] ] idno
Note

A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Module tei — Schema
Used by
Members name orgName persName
Note

This class is used in the content model of elements which reference names of people or organizations.

model.noteLike

model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]
Module tei — Schema
Used by
Members note

model.offsetLike

model.offsetLike groups elements which can appear only as part of a place name. [13.2.3. Place Names]
Module tei — Schema
Used by
Members geogFeat

model.paraPart

model.paraPart groups elements that may appear in paragraphs and similar elements [3.1. Paragraphs]
Module tei — Schema
Used by
Members model.gLike model.global [model.global.edit [gap] model.global.meta model.milestoneLike [fw lb pb] model.noteLike [note] figure] model.inter [model.attributable [model.quoteLike [cit quote] ] model.biblLike [bibl biblStruct listBibl msDesc] model.egLike model.labelLike [desc label] model.listLike [list] model.oddDecl model.stageLike] model.lLike [l] model.phrase [model.graphicLike [formula graphic] model.highlighted [model.emphLike [foreign term title] model.hiLike [hi q] ] model.lPart model.pPart.data [model.addressLike [address email] model.dateLike [date] model.measureLike [depth dim geo height measure num width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat] model.persNamePart [addName forename surname] model.placeStateLike [model.placeNamePart [country district geogName placeName region settlement] ] idno] ] model.pPart.edit [model.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del orig reg sic supplied unclear] ] model.pPart.msdesc [catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml model.ptrLike [ref] model.segLike [seg] model.specDescLike] lg

model.persNamePart

model.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names]
Module namesdates — Schema
Used by
Members addName forename surname

model.phrase

model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]
Module tei — Schema
Used by
Members model.graphicLike [formula graphic] model.highlighted [model.emphLike [foreign term title] model.hiLike [hi q] ] model.lPart model.pPart.data [model.addressLike [address email] model.dateLike [date] model.measureLike [depth dim geo height measure num width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat] model.persNamePart [addName forename surname] model.placeStateLike [model.placeNamePart [country district geogName placeName region settlement] ] idno] ] model.pPart.edit [model.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del orig reg sic supplied unclear] ] model.pPart.msdesc [catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark] model.phrase.xml model.ptrLike [ref] model.segLike [seg] model.specDescLike
Note

This class of elements can occur within paragraphs, list items, lines of verse, etc.

model.physDescPart

model.physDescPart groups specialized elements forming part of the physical description of a manuscript or similar written source.
Module msdescription — Schema
Used by
Members accMat additions bindingDesc decoDesc handDesc musicNotation objectDesc scriptDesc sealDesc typeDesc

model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]
Module tei — Schema
Used by
Members country district geogName placeName region settlement

model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Module tei — Schema
Used by
Members model.placeNamePart [country district geogName placeName region settlement]

model.pLike

model.pLike groups paragraph-like elements.
Module tei — Schema
Used by
Members p

model.pPart.data

model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Module tei — Schema
Used by
Members model.addressLike [address email] model.dateLike [date] model.measureLike [depth dim geo height measure num width] model.nameLike [model.nameLike.agent [name orgName persName] model.offsetLike [geogFeat] model.persNamePart [addName forename surname] model.placeStateLike [model.placeNamePart [country district geogName placeName region settlement] ] idno]

model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]
Module tei — Schema
Used by
Members model.pPart.editorial [abbr am choice ex expan subst] model.pPart.transcriptional [add corr damage del orig reg sic supplied unclear]

model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes]
Module tei — Schema
Used by
Members abbr am choice ex expan subst

model.pPart.msdesc

model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. Manuscript Description]
Module tei — Schema
Used by
Members catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark

model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]
Module tei — Schema
Used by
Members add corr damage del orig reg sic supplied unclear

model.profileDescPart

model.profileDescPart groups elements which may be used inside profileDesc and appear multiple times.
Module tei — Schema
Used by
Members textClass

model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
Module tei — Schema
Used by
Members ref

model.publicationStmtPart.agency

model.publicationStmtPart.agency groups the child elements of a publicationStmt element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
Module tei — Schema
Used by
Members authority distributor publisher
Note

The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element.

See also model.publicationStmtPart.detail.

model.publicationStmtPart.detail

model.publicationStmtPart.detail groups the agency-specific child elements of the publicationStmt element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]
Module tei — Schema
Used by
Members model.ptrLike [ref] address availability date idno pubPlace
Note

A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.

See also model.publicationStmtPart.agency.

model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Module tei — Schema
Used by
Members cit quote

model.resource

model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]
Module tei — Schema
Used by
TEI
Members facsimile text

model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Module tei — Schema
Used by
Members author editor funder principal respStmt sponsor

model.segLike

model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
Module tei — Schema
Used by
Members seg
Note

The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the encodingDesc within the associated TEI header.

model.teiHeaderPart

model.teiHeaderPart groups high level elements which may appear more than once in a TEI header.
Module tei — Schema
Used by
Members encodingDesc include profileDesc

model.titlepagePart

model.titlepagePart groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. Title Pages]
Module tei — Schema
Used by
Members graphic

Schema msdesc: Attribute classes

att.anchoring

att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.
Module tei — Schema
Members note
Attributes
anchored (anchored) indicates whether the copy text shows the exact place of reference for the note.
Status Optional
Datatype teidata.truthValue
Default true
Note

In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

targetEnd (target end) points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 16.2.4.6. range().

Example
<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses
necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p>
<!-- elsewhere in the document -->
<noteGrp targetEnd="#A55234">
 <note xml:lang="en"> Quatuor Tempora, so called dry fast days.
 </note>
 <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.
 </note>
</noteGrp>

att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Module tei — Schema
Members att.ascribed.directed [q] change
Attributes
who indicates the person, or group of people, to whom the element content is ascribed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the who attribute.

<castItem type="role">
 <role xml:id="Barnardo">Bernardo</role>
</castItem>
<castItem type="role">
 <role xml:id="Francisco">Francisco</role>
 <roleDesc>a soldier</roleDesc>
</castItem>
<!-- ... -->
<sp who="#Barnardo">
 <speaker>Bernardo</speaker>
 <l n="1">Who's there?</l>
</sp>
<sp who="#Francisco">
 <speaker>Francisco</speaker>
 <l n="2">Nay, answer me: stand, and unfold yourself.</l>
</sp>
Note

For transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified <person> element.

att.ascribed.directed

att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Module tei — Schema
Members q
Attributes att.ascribed (@who)
toWhomindicates the person, or group of people, to whom a speech act or action is directed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

In the following example from Mary Pix's The False Friend, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the toWhom attribute, which is used to specify who the speech is directed to. Additionally, the <stage> includes toWhom to indicate the directionality of the action.

<castItem type="role">
 <role xml:id="emil">Emilius.</role>
</castItem>
<castItem type="role">
 <role xml:id="lov">Lovisa</role>
</castItem>
<castItem type="role">
 <role xml:id="serv">A servant</role>
</castItem>
<!-- ... -->
<sp toWhom="#lovwho="#emil">
 <speaker>Emil.</speaker>
 <l n="1">My love!</l>
</sp>
<sp toWhom="#emilwho="#lov">
 <speaker>Lov.</speaker>
 <l n="2">I have no Witness of my Noble Birth</l>
 <stage toWhom="#servwho="emil">Pointing to her Woman.</stage>
 <l>But that poor helpless wretch——</l>
</sp>
Note

To indicate the recipient of written correspondence, use the elements used in section 2.4.6. Correspondence Description, rather than a toWhom attribute.

att.breaking

att.breaking provides attributes to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.11.3. Milestone Elements]
Module tei — Schema
Members lb pb
Attributes
break indicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace.
Status Recommended
Datatype teidata.enumerated
Sample values include
yes
the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
no
the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
maybe
the encoding does not take any position on this issue.

In the following lines from the Dream of the Rood, linebreaks occur in the middle of the words lāðost and reord-berendum.

<ab> ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt .
leodum la<lb break="no"/> ðost ærþan ichim lifes
ƿeȝ rihtne ȝerymde reord be<lb break="no"/>
rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer...
</ab>

att.canonical

att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]
Module tei — Schema
Members att.naming [att.personal [addName forename name orgName persName placeName surname] author collection country district editor geogFeat geogName institution origPlace pubPlace region repository settlement] authority catDesc date distributor funder material objectType principal publisher resp respStmt sponsor term title
Attributes
key provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Status Optional
Datatype teidata.text
<author>
 <name key="name 427308"
  type="organisation">
[New Zealand Parliament, Legislative Council]</name>
</author>
<author>
 <name key="Hugo, Victor (1802-1885)"
  ref="http://www.idref.fr/026927608">
Victor Hugo</name>
</author>
Note

The value may be a unique identifier from a database, or any other externally-defined string identifying the referent.

No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project. For the same reason, this attribute is not recommended in data interchange, since there is no way of ensuring that the values used by one project are distinct from those used by another. In such a situation, a preferable approach for magic tokens which follows standard practice on the Web is to use a ref attribute whose value is a tag URI as defined in RFC 4151.

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.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<name ref="http://viaf.org/viaf/109557338"
 type="person">
Seamus Heaney</name>
Note

The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

att.citing

att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
Module tei — Schema
Members biblScope citedRange
Attributes
unit identifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
Status Optional
Datatype teidata.enumerated
Suggested values include:
volume
(volume) the element contains a volume number.
issue
the element contains an issue number, or volume and issue numbers.
page
(page) the element contains a page number or page range.
line
the element contains a line number or line range.
chapter
(chapter) the element contains a chapter indication (number and/or title)
part
the element identifies a part of a book or collection.
column
the element identifies a column.
entry
the element identifies an entry number or label in a list of entries.
from specifies the starting point of the range of units indicated by the unit attribute.
Status Optional
Datatype teidata.word
to specifies the end-point of the range of units indicated by the unit attribute.
Status Optional
Datatype teidata.word

att.coordinated

att.coordinated provides attributes that can be used to position their parent element within a two dimensional coordinate system.
Module transcr — Schema
Members surface zone
Attributes
start indicates the element within a transcription of the text containing at least the start of the writing represented by this zone or surface.
Status Optional
Datatype teidata.pointer
ulx gives the x coordinate value for the upper left corner of a rectangular space.
Status Optional
Datatype teidata.numeric
uly gives the y coordinate value for the upper left corner of a rectangular space.
Status Optional
Datatype teidata.numeric
lrx gives the x coordinate value for the lower right corner of a rectangular space.
Status Optional
Datatype teidata.numeric
lry gives the y coordinate value for the lower right corner of a rectangular space.
Status Optional
Datatype teidata.numeric
points identifies a two dimensional area by means of a series of pairs of numbers, each of which gives the x,y coordinates of a point on a line enclosing the area.
Status Optional
Datatype 3–∞ occurrences of teidata.point separated by whitespace

att.cReferencing

att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer.
Module tei — Schema
Members ref term
Attributes
cRef (canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
Status Optional
Datatype teidata.text
Note

The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 16.2.5. Canonical References) is applied to it the result is a valid URI reference to the intended target.

The <refsDecl> to use may be indicated with the decls attribute.

Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.

att.damaged

att.damaged provides attributes describing the nature of any physical damage affecting a reading. [11.3.3.1. Damage, Illegibility, and Supplied Text 1.3.1. Attribute Classes]
Module tei — Schema
Members damage
Attributes att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.written (@hand)
agentcategorizes the cause of the damage, if it can be identified.
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
degreeprovides a coded representation of the degree of damage, either as a number between 0 (undamaged) and 1 (very extensively damaged), or as one of the codes high, medium, low, or unknown. The damage element with the degree attribute should only be used where the text may be read with some confidence; text supplied from other sources should be tagged as supplied.
Status Optional
Datatype teidata.probCert
Note

The damage element is appropriate where it is desired to record the fact of damage although this has not affected the readability of the text, for example a weathered inscription. Where the damage has rendered the text more or less illegible either the unclear tag (for partial illegibility) or the gap tag (for complete illegibility, with no text supplied) should be used, with the information concerning the damage given in the attribute values of these tags. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of the use of these tags in particular circumstances.

groupassigns an arbitrary number to each stretch of damage regarded as forming part of the same physical phenomenon.
Status Optional
Datatype teidata.count

att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 13.4. Dates]
Module tei — Schema
Members acquisition altIdentifier author binding change country custEvent date district editor foliation funder geogFeat geogName idno licence name orgName origDate origPlace origin persName placeName principal provenance region resp seal settlement sponsor stamp title
Attributes 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)
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@calendar]">
<sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more
systems or calendars to which the date represented by the content of this element belongs,
but this <sch:name/> element has no textual content.</sch:assert>
</sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julianwhen="1732-02-22">Feb. 11, 1731/32,
O.S.</date>).
He was born on <date calendar="#gregorian #julian"
 when="1732-02-22">
Feb. 22, 1732
(Feb. 11, 1731/32, O.S.)</date>.
Note

Note that the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized.

periodsupplies pointers to one or more definitions of named periods of time (typically categorys or <calendar>s) within which the datable item is understood to have occurred.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

att.datable.custom

att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates]
Module namesdates — Schema
Members att.datable [acquisition altIdentifier author binding change country custEvent date district editor foliation funder geogFeat geogName idno licence name orgName origDate origPlace origin persName placeName principal provenance region resp seal settlement sponsor stamp title]
Attributes
when-custom supplies the value of a date or time in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace

The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system

<p>Alhazen died in Cairo on the
<date when="1040-03-06"
  when-custom="431-06-12">
12th day of Jumada t-Tania, 430 AH
 </date>.</p>
<p>The current world will end at the
<date when="2012-12-21"
  when-custom="13.0.0.0.0">
end of B'ak'tun 13</date>.</p>
<p>The Battle of Meggidu
(<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p>
<p>Esidorus bixit in pace annos LXX plus minus sub
<date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date>
</p>

Not all custom date formulations will have Gregorian equivalents.

The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.

notBefore-custom specifies the earliest possible date for the event in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
notAfter-custom specifies the latest possible date for the event in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
from-custom indicates the starting point of the period in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
<event datingMethod="#julian"
 from-custom="1666-09-02to-custom="1666-09-05xml:id="FIRE1">

 <head>The Great Fire of London</head>
 <p>The Great Fire of London burned through a large part
   of the city of London.</p>
</event>
to-custom indicates the ending point of the period in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
datingPoint supplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
Status Optional
Datatype teidata.pointer
datingMethod supplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
Status Optional
Datatype teidata.pointer
Contayning the Originall, Antiquity, Increaſe, Moderne
eſtate, and deſcription of that Citie, written in the yeare
<date calendar="#julian"
 datingMethod="#julianwhen-custom="1598">
1598</date>. by Iohn Stow
Citizen of London.

In this example, the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the date element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.

<date datingMethod="#creationOfWorld"
 when="1382-06-28when-custom="6890-06-20">
μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num>
</date>

In this example, a date is given in a Mediaeval text measured ‘from the creation of the world’, which is normalized (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.

Note

Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the original date in the element.

att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates]
Module namesdates — Schema
Members att.datable [acquisition altIdentifier author binding change country custEvent date district editor foliation funder geogFeat geogName idno licence name orgName origDate origPlace origin persName placeName principal provenance region resp seal settlement sponsor stamp title]
Attributes
when-iso supplies the value of a date or time in a standard form.
Status Optional
Datatype teidata.temporal.iso

The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.

<date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date>
<date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date>
<time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time>
<time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time>
<date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date>
<time when-iso="03:00">3 A.M.</time>
<time when-iso="14">around two</time>
<time when-iso="15,5">half past three</time>

All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.

He likes to be punctual. I said <q>
 <time when-iso="12">around noon</time>
</q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.

The second occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.

notBefore-iso specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso
notAfter-iso specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso
from-iso indicates the starting point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
to-iso indicates the ending point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601:2004, using the Gregorian calendar.

If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date dur-iso="P8Dwhen-iso="2007-06-01"/>
indicates the same time period as
<date when-iso="2007-06-01/P8D"/>

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 13.4. Dates]
Module tei — Schema
Members att.datable [acquisition altIdentifier author binding change country custEvent date district editor foliation funder geogFeat geogName idno licence name orgName origDate origPlace origin persName placeName principal provenance region resp seal settlement sponsor stamp title]
Attributes
when supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c

Examples of W3C date, time, and date & time formats.

<p>
 <date when="1945-10-24">24 Oct 45</date>
 <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>
 <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>
 <time when="14:12:38">fourteen twelve and 38 seconds</time>
 <date when="1962-10">October of 1962</date>
 <date when="--06-12">June 12th</date>
 <date when="---01">the first of the month</date>
 <date when="--08">August</date>
 <date when="2006">MMVI</date>
 <date when="0056">AD 56</date>
 <date when="-0056">56 BC</date>
</p>
This list begins in
the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after
Pentecost, in that year the
<date calendar="#julianwhen="1632-06-06">27th of May (old style)</date>.
<opener>
 <dateline>
  <placeName>Dorchester, Village,</placeName>
  <date when="1828-03-02">March 2d. 1828.</date>
 </dateline>
 <salute>To
   Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time>
</opener>
notBefore specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
notAfter specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
from indicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
to indicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
Schematron

<sch:rule context="//*[not(self::tei:locus or self::tei:biblScope or self::tei:citedRange)] [(@notBefore and @notAfter) or (@from and @to)]">
<sch:let name="f"
 value="(@notBefore,@from)[1]"/>

<sch:let name="t"
 value="(@notAfter,@to)[1]"/>

<sch:let name="bothdates"
 value="$f castable as xs:date and $t castable as xs:date"/>

<sch:let name="bothyears"
 value="$f castable as xs:integer and $t castable as xs:integer"/>

<sch:let name="fd"
 value="if ($bothdates) then xs:date($f) else ()"/>

<sch:let name="td"
 value="if ($bothdates) then xs:date($t) else ()"/>

<sch:let name="fy"
 value="if ($bothyears) then xs:integer($f) else ()"/>

<sch:let name="ty"
 value="if ($bothyears) then xs:integer($t) else ()"/>

<sch:report role="error"
 test="($bothdates and $fd gt $td) or ($bothyears and $fy gt $ty)">
The date range <sch:value-of select="$f"/><sch:value-of select="$t"/> in <sch:value-of select="name(.)"/> is not valid.
</sch:report>
</sch:rule>
Schematron

<sch:rule context="tei:*[@when]">
<sch:report role="nonfatal"
 test="@notBefore|@notAfter|@from|@to">
The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report>
</sch:rule>
Schematron

<sch:rule context="tei:*[@from]">
<sch:report role="nonfatal"
 test="@notBefore">
The @from and @notBefore attributes cannot be used together.</sch:report>
</sch:rule>
Schematron

<sch:rule context="tei:*[@to]">
<sch:report role="nonfatal"
 test="@notAfter">
The @to and @notAfter attributes cannot be used together.</sch:report>
</sch:rule>
Example
<date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

att.datcat

att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [9.5.2. Lexical View 18.3. Other Atomic Feature Values]
Module tei — Schema
Members att.segLike [seg]
Attributes
datcat provides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcat provides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcat provides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Example

The example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.

The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.

<fs>
 <f datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
  name="POS">

  <symbol value="NN"
   valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>

 </f>
<!-- ... -->
</fs>

‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545 is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.

While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.

If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [ID FS in TEI Guidelines].
<fs>
 <f fVal="#commonNounname="POS"/>
<!-- ... -->
</fs>

The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of text or a child of encodingDesc; a taxonomy available resource-wide (e.g., in a shared header) is also an option.

The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories.
<fvLib n="POS values">
 <symbol datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
  value="NNxml:id="commonNoun"/>

 <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"
  value="NPxml:id="properNoun"/>

<!-- ... -->
</fvLib>

Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.

Example

In the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above.

<gramGrp>
 <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
  valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">
NN</pos>
</gramGrp>
Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>:
<tagsDecl partial="true">
<!-- ... -->
 <namespace name="http://www.tei-c.org/ns/1.0">
  <tagUsage gi="pos"
   targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">
Contains the part of speech.</tagUsage>
  <tagUsage gi="case"
   targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">
Contains information about the grammatical case that the described form is inflected for.</tagUsage>
<!-- ... -->
 </namespace>
</tagsDecl>
Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below:
<listPrefixDef>
 <prefixDef ident="ccrmatchPattern="pos"
  replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>

 <prefixDef ident="ccrmatchPattern="adj"
  replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/>

</listPrefixDef>
<!-- ... -->
<entry>
<!--...-->
 <form>
  <orth>isotope</orth>
 </form>
 <gramGrp>
  <pos datcat="ccr:pos"
   valueDatcat="ccr:adj">
adj</pos>
 </gramGrp>
<!--...-->
</entry>

This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.

Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in <equiv> element that is a child of <elementSpec> or <attDef>.

Example

The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.

<fDecl name="POS"
 targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">

 <fDescr>part of speech (morphosyntactic category)</fDescr>
 <vRange>
  <vAlt>
   <symbol datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"
    value="NN"/>

   <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"
    value="NP"/>

<!-- ... -->
  </vAlt>
 </vRange>
</fDecl>

Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.

Note

The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container.

A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute.

In a TEI XML example of two equivalent serializations expressing the name-value pair <part-of-speech,common-noun>, namely <pos>commonNoun</pos> and pos="common-noun", one would classify the element <pos> and the attribute pos as containers (mapping onto the first member of the relevant name-value pair), while the character data content of <pos> or the value of pos would be seen as mapping onto the second member of the pair.

The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech).

The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects.

Historically, datcat and valueDatcat originate from the (the now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example.

Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices.

att.declarable

att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [15.3. Associating Contextual Information with a Text]
Module tei — Schema
Members availability bibl biblStruct listBibl projectDesc sourceDesc textClass
Attributes
default indicates whether or not this element is selected by default when its parent is selected.
Status Optional
Datatype teidata.truthValue
Legal values are:
true
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected. [Default]
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

att.declaring

att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [15.3. Associating Contextual Information with a Text]
Module tei — Schema
Members body div facsimile geo graphic lg msDesc p ref surface surfaceGrp term text
Attributes
decls (declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text.

att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Module tei — Schema
Members att.damaged [damage] add date del depth dim dimensions ex gap geogFeat height origDate subst supplied unclear width
Attributes att.ranging (@atLeast, @atMost, @min, @max, @confidence)
unitnames the unit used for the measurement
Status Optional
Datatype teidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
quantityspecifies the length in the units specified
Status Optional
Datatype teidata.numeric
extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
Status Optional
Datatype teidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
Status Optional
Datatype teidata.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
Status Optional
Datatype teidata.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

att.divLike

att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure]
Module tei — Schema
Members div lg
Attributes att.fragmentable (@part)
org(organization) specifies how the content of the division is organized.
Status Optional
Datatype teidata.enumerated
Legal values are:
composite
no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships.
uniform
the immediate contents of this element are regarded as forming a logical unit, to be processed in sequence. [Default]
sampleindicates whether this division is a sample of the original source and if so, from which part.
Status Optional
Datatype teidata.enumerated
Legal values are:
initial
division lacks material present at end in source.
medial
division lacks material at start and end.
final
division lacks material at start.
unknown
position of sampled material within original unknown.
complete
division is not a sample. [Default]

att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Module tei — Schema
Members bibl biblStruct change msDesc revisionDesc
Attributes
status describes the status of a document either currently or, when associated with a dated element, at the time indicated.
Status Optional
Datatype teidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">
 <change status="published"
  when="2010-10-21"/>

 <change status="clearedwhen="2010-10-02"/>
 <change status="embargoed"
  when="2010-08-02"/>

 <change status="frozenwhen="2010-05-01"
  who="#MSM"/>

 <change status="draftwhen="2010-03-01"
  who="#LB"/>

</revisionDesc>

att.edition

att.edition provides attributes identifying the source edition from which some encoded feature derives.
Module tei — Schema
Members lb pb
Attributes
ed (edition) supplies a sigil or other arbitrary identifier for the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
edRef (edition reference) provides a pointer to the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Example
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example
<listBibl>
 <bibl xml:id="stapledon1937">
  <author>Olaf Stapledon</author>,
 <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>
 </bibl>
 <bibl xml:id="stapledon1968">
  <author>Olaf Stapledon</author>,
 <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>
 </bibl>
</listBibl>
<!-- ... -->
<p>Looking into the future aeons from the supreme moment of
the cosmos, I saw the populations still with all their
strength maintaining the<pb edRef="#stapledon1968n="411"/>essentials of their ancient culture,
still living their personal lives in zest and endless
novelty of action, … I saw myself still
preserving, though with increasing difficulty, my lucid
con-<pb edRef="#stapledon1937n="291"/>sciousness;</p>

att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work]
Module tei — Schema
Members att.transcriptional [add del subst] am corr date ex expan gap geogFeat geogName name orgName origDate origPlace origin persName placeName reg supplied unclear
Attributes
evidence indicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
internal
there is internal evidence to support the intervention.
external
there is external evidence to support the intervention.
conjecture
the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
instant indicates whether this is an instant revision or not.
Status Optional
Datatype teidata.xTruthValue
Default false
Note

The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, msDesc, or bibl element, or another external bibliographic citation, documenting the source concerned.

att.fragmentable

att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
Module tei — Schema
Members att.divLike [div lg] att.segLike [seg] l p
Attributes
part specifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
Status Optional
Datatype teidata.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) the element is not fragmented, or no claim is made as to its completeness [Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

The values I, M, or F should be used only where it is clear how the element may be reconstituted.

att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Module tei — Schema
Members TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category change choice cit citedRange classDecl collation collection colophon condition corr countermark country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw gap geo geogFeat geogName graphic handDesc handNote head height heraldry hi history idno imprint incipit institution item keywords l label layout layoutDesc lb lg licence list listBibl locus locusGrp material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName physDesc placeName postCode principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem repository resp respStmt revisionDesc rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone
Attributes att.global.rendition (@rend, @style, @rendition) att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp) att.global.source (@source)
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
Datatype ID
Note

The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Status Optional
Datatype teidata.text
Note

The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Status Optional
Datatype teidata.language
<p> … The consequences of
this rapid depopulation were the loss of the last
<foreign xml:lang="rap">ariki</foreign> or chief
(Routledge 1920:205,210) and their connections to
ancestral territorial organization.</p>
Note

The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the teiHeader from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see https://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
Status Optional
Datatype teidata.pointer
<div type="bibl">
 <head>Selections from <title level="m">The Collected Letters of Robert Southey. Part 1: 1791-1797</title>
 </head>
 <listBibl xml:base="https://romantic-circles.org/sites/default/files/imported/editions/southey_letters/XML/">
  <bibl>
   <ref target="letterEEd.26.3.xml">
    <title>Robert Southey to Grosvenor Charles Bedford</title>, <date when="1792-04-03">3 April 1792</date>.
   </ref>
  </bibl>
  <bibl>
   <ref target="letterEEd.26.57.xml">
    <title>Robert Southey to Anna Seward</title>, <date when="1793-09-18">18 September 1793</date>.
   </ref>
  </bibl>
  <bibl>
   <ref target="letterEEd.26.85.xml">
    <title>Robert Southey to Robert Lovell</title>, <date from="1794-04-05to="1794-04-06">5-6 April, 1794</date>.
   </ref>
  </bibl>
 </listBibl>
</div>
xml:spacesignals an intention about how white space should be managed by applications.
Status Optional
Datatype teidata.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note

The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

att.global.change

att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
Module transcr — Schema
Members att.global [TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category change choice cit citedRange classDecl collation collection colophon condition corr countermark country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw gap geo geogFeat geogName graphic handDesc handNote head height heraldry hi history idno imprint incipit institution item keywords l label layout layoutDesc lb lg licence list listBibl locus locusGrp material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName physDesc placeName postCode principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem repository resp respStmt revisionDesc rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone] countermark
Attributes
change points to one or more change elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

att.global.facs

att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles]
Module transcr — Schema
Members att.global [TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category change choice cit citedRange classDecl collation collection colophon condition corr countermark country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw gap geo geogFeat geogName graphic handDesc handNote head height heraldry hi history idno imprint incipit institution item keywords l label layout layoutDesc lb lg licence list listBibl locus locusGrp material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName physDesc placeName postCode principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem repository resp respStmt revisionDesc rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone]
Attributes
facs (facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]
Module linking — Schema
Members att.global [TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category change choice cit citedRange classDecl collation collection colophon condition corr countermark country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw gap geo geogFeat geogName graphic handDesc handNote head height heraldry hi history idno imprint incipit institution item keywords l label layout layoutDesc lb lg licence list listBibl locus locusGrp material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName physDesc placeName postCode principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem repository resp respStmt revisionDesc rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone] countermark
Attributes
corresp (corresponds) points to elements that correspond to the current element in some way.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<group>
 <text xml:id="t1-g1-t1xml:lang="mi">
  <body xml:id="t1-g1-t1-body1">
   <div type="chapter">
    <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>
    <p></p>
   </div>
  </body>
 </text>
 <text xml:id="t1-g1-t2xml:lang="en">
  <body corresp="#t1-g1-t1-body1"
   xml:id="t1-g1-t2-body1">

   <div type="chapter">
    <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>
    <p></p>
   </div>
  </body>
 </text>
</group>

In this example a <group> contains two texts, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.


<!-- In a placeography called "places.xml" --><place corresp="people.xml#LOND2 people.xml#GENI1"
 xml:id="LOND1">

 <placeName>London</placeName>
 <desc>The city of London...</desc>
</place>
<!-- In a literary personography called "people.xml" -->
<person corresp="places.xml#LOND1 #GENI1"
 xml:id="LOND2">

 <persName type="lit">London</persName>
 <note>
  <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>
 </note>
</person>
<person corresp="places.xml#LOND1 #LOND2"
 xml:id="GENI1">

 <persName type="lit">London’s Genius</persName>
 <note>
  <p>Personification of London’s genius. Appears as an
     allegorical character in mayoral shows.
  </p>
 </note>
</person>

In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.

synch (synchronous) points to elements that are synchronous with the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
sameAs points to an element that is the same as the current element.
Status Optional
Datatype teidata.pointer
copyOf points to an element of which the current element is a copy.
Status Optional
Datatype teidata.pointer
Note

Any content of the current element should be ignored. Its true content is that of the element being pointed at.

next points to the next element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

prev (previous) points to the previous element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

exclude points to elements that are in exclusive alternation with the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
select selects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute should be placed on an element which is superordinate to all of the alternants from which the selection is being made.

att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Module tei — Schema
Members att.global [TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category change choice cit citedRange classDecl collation collection colophon condition corr countermark country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw gap geo geogFeat geogName graphic handDesc handNote head height heraldry hi history idno imprint incipit institution item keywords l label layout layoutDesc lb lg licence list listBibl locus locusGrp material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName physDesc placeName postCode principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem repository resp respStmt revisionDesc rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone] countermark
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
<head rend="align(center) case(allcaps)">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
<lb/>On Her <lb/>
 <hi rend="case(mixed)">New Blazing-World</hi>.
</head>
Note

These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

style contains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
Status Optional
Datatype teidata.text
<head style="text-align: center; font-variant: small-caps">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
<lb/>
 <hi style="font-variant: normal">New Blazing-World</hi>.
</head>
Note

Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

rendition points to a description of the rendering or presentation used for this element in the source text.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<head rendition="#ac #sc">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
<lb/>
 <hi rendition="#normal">New Blazing-World</hi>.
</head>
<!-- elsewhere... -->
<rendition scheme="cssxml:id="sc">font-variant: small-caps</rendition>
<rendition scheme="cssxml:id="normal">font-variant: normal</rendition>
<rendition scheme="cssxml:id="ac">text-align: center</rendition>
Note

The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

Schematron

<sch:rule context="*[@rend]">
<sch:report role="info"
 test="self::tei:hi and not(every $r in tokenize(@rend, '\s+')[string-length() gt 0] satisfies $r = ('bold', 'italic', 'smallcaps', 'roman', 'superscript', 'subscript', 'underline', 'overline', 'strikethrough'))">
Any values can be used in rend attributes, but the web site currently only supports combinations of:
bold, italic, roman, smallcaps, superscript, subscript, underline, overline, and strikethrough.
</sch:report>
<sch:report role="info"
 test="self::tei:list and not(every $r in tokenize(@rend, '\s+')[string-length() gt 0] satisfies $r = ('numbered', 'ordered', 'ol', 'bulleted', 'unordered', 'ul'))">
Any values can be used in rend attributes, but the web site currently only supports combinations of:
numbered, ordered, ol, bulleted, unordered, and ul.
</sch:report>
<sch:assert role="info"
 test="self::tei:hi or self::tei:list">
The web site currently only supports rend attributes for hi and list elements. Using it on <sch:value-of select="name(.)"/>
elements is valid but will be ignored.
</sch:assert>
</sch:rule>
<sch:rule context="*[@rendition or @style]">
<sch:assert role="infotest="false()"> The web site currently ignores rendition and style attributes.
</sch:assert>
</sch:rule>
Schematron

<sch:rule context="tei:*[@key]">
<sch:assert role="warn"
 test="string-length(normalize-space(string())) gt 1">
Elements with key attributes should have some content (because they will be displayed
as links, and links need text for readers to click on.)
</sch:assert>
</sch:rule>
Schematron

<sch:rule context="tei:height|tei:width">
<sch:assert role="warn"
 test="string-length(normalize-space(string())) gt 0">
For dimensions the website displays the content of height and width elements. Attribute values are not displayed. Empty elements will not display correctly.
</sch:assert>
</sch:rule>

att.global.responsibility

att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]
Module tei — Schema
Members att.global [TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category change choice cit citedRange classDecl collation collection colophon condition corr countermark country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw gap geo geogFeat geogName graphic handDesc handNote head height heraldry hi history idno imprint incipit institution item keywords l label layout layoutDesc lb lg licence list listBibl locus locusGrp material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName physDesc placeName postCode principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem repository resp respStmt revisionDesc rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone] countermark
Attributes
cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
Status Optional
Datatype teidata.probCert
resp (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a respStmt, author, editor or similar element which clarifies the exact role played by the agent. Pointing to multiple respStmts allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).

Example
Blessed are the
<choice>
 <sic>cheesemakers</sic>
 <corr cert="highresp="#editor">peacemakers</corr>
</choice>: for they shall be called the children of God.
Example

<!-- in the <text> ... --><lg>
<!-- ... -->
 <l>Punkes, Panders, baſe extortionizing
   sla<choice>
   <sic>n</sic>
   <corr resp="#JENS1_transcriber">u</corr>
  </choice>es,</l>
<!-- ... -->
</lg>
<!-- in the <teiHeader> ... -->
<!-- ... -->
<respStmt xml:id="JENS1_transcriber">
 <resp when="2014">Transcriber</resp>
 <name>Janelle Jenstad</name>
</respStmt>

att.global.source

att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Module tei — Schema
Members att.global [TEI abbr accMat acquisition add addName additional additions addrLine address adminInfo altIdentifier am analytic author authority availability bibl biblScope biblStruct binding bindingDesc body catDesc catchwords category change choice cit citedRange classDecl collation collection colophon condition corr countermark country custEvent custodialHist damage date decoDesc decoNote del depth desc dim dimensions distributor district div edition editionStmt editor email encodingDesc ex expan explicit extent facsimile figDesc figure fileDesc filiation finalRubric foliation foreign forename formula funder fw gap geo geogFeat geogName graphic handDesc handNote head height heraldry hi history idno imprint incipit institution item keywords l label layout layoutDesc lb lg licence list listBibl locus locusGrp material measure monogr msContents msDesc msFrag msIdentifier msItem msItemStruct msName msPart musicNotation name note num objectDesc objectType orgName orig origDate origPlace origin p pb persName physDesc placeName postCode principal profileDesc projectDesc provenance pubPlace publicationStmt publisher q quote recordHist ref reg region relatedItem repository resp respStmt revisionDesc rubric scriptDesc scriptNote seal sealDesc secFol seg series settlement sic signatures source sourceDesc sponsor stamp street subst summary supplied support supportDesc surface surfaceGrp surname surrogates taxonomy teiHeader term text textClass textLang title titleStmt typeDesc typeNote unclear watermark width zone] countermark
Attributes
source specifies the source from which some aspect of this element is drawn.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@source]">
<sch:let name="srcs"
 value="tokenize( normalize-space(@source),' ')"/>

<sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like
<sch:value-of select="name(.)"/>), the @source attribute
should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.)
</sch:report>
</sch:rule>
Note

The source attribute points to an external source. When used on an element describing a schema component (<classRef>, <dataRef>, <elementRef>, <macroRef>, <moduleRef>, or <schemaSpec>), it identifies the source from which declarations for the components should be obtained.

On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, a private scheme URI of the form tei:x.y.z, where x.y.z indicates the version number, e.g. tei:4.3.2 for TEI P5 release 4.3.2 or (as a special case) tei:current for whatever is the latest release, or a private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.

When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.

Example
<p>
<!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested
   term.</quote>
<!-- ... -->
</p>
Example
<p>
<!-- ... -->
 <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the
   less we seem to know.</quote>
<!-- ... -->
</p>
<!-- ... -->
<bibl xml:id="chicago_15_ed">
 <title level="m">The Chicago Manual of Style</title>,
<edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of
   Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>.

</bibl>
Example
<elementRef key="psource="tei:2.0.1"/>

Include in the schema an element named p available from the TEI P5 2.0.1 release.

Example
<schemaSpec ident="myODD"
 source="mycompiledODD.xml">

<!-- further declarations specifying the components required -->
</schemaSpec>

Create a schema using components taken from the file mycompiledODD.xml.

att.handFeatures

att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [11.3.2.1. Document Hands]
Module tei — Schema
Members handNote scriptNote typeNote
Attributes
scribe gives a name or other identifier for the scribe believed to be responsible for this hand.
Status Optional
Datatype teidata.name
scribeRef points to a full description of the scribe concerned, typically supplied by a <person> element elsewhere in the description.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
script characterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
Status Optional
Datatype 1–∞ occurrences of teidata.name separated by whitespace
scriptRef points to a full description of the script or writing style used by this hand, typically supplied by a scriptNote element elsewhere in the description.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
medium describes the tint or type of ink, e.g. brown, or other writing medium, e.g. pencil
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
scope specifies how widely this hand is used in the manuscript.
Status Optional
Datatype teidata.enumerated
Legal values are:
sole
only this hand is used throughout the manuscript
major
this hand is used through most of the manuscript
minor
this hand is used occasionally in the manuscript
Note

Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied.

att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Module tei — Schema
Members att.media [graphic] ref
Attributes
mimeType (MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Example

In this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.

<ref mimeType="application/tei+xml; charset=UTF-8"
 target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
Note

This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.

att.measurement

att.measurement provides attributes to represent a regularized or normalized measurement.
Module tei — Schema
Members measure
Attributes
unit (unit) indicates the units used for the measurement, usually using the standard symbol for the desired units.
Status Optional
Datatype teidata.enumerated
Suggested values include:
m
(metre) SI base unit of length
kg
(kilogram) SI base unit of mass
s
(second) SI base unit of time
Hz
(hertz) SI unit of frequency
Pa
(pascal) SI unit of pressure or stress
Ω
(ohm) SI unit of electric resistance
L
(litre) 1 dm³
t
(tonne) 10³ kg
ha
(hectare) 1 hm²
Å
(ångström) 10⁻¹⁰ m
mL
(millilitre)
cm
(centimetre)
dB
(decibel) see remarks, below
kbit
(kilobit) 10³ or 1000 bits
Kibit
(kibibit) 2¹⁰ or 1024 bits
kB
(kilobyte) 10³ or 1000 bytes
KiB
(kibibyte) 2¹⁰ or 1024 bytes
MB
(megabyte) 10⁶ or 1 000 000 bytes
MiB
(mebibyte) 2²⁰ or 1 048 576 bytes
Note

If the measurement being represented is not expressed in a particular unit, but rather is a number of discrete items, the unit count should be used, or the unit attribute may be left unspecified.

Wherever appropriate, a recognized SI unit name should be used (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). The list above is indicative rather than exhaustive.

unitRef points to a unique identifier stored in the xml:id of a <unitDef> element that defines a unit of measure.
Status Optional
Datatype teidata.pointer
quantity (quantity) specifies the number of the specified units that comprise the measurement
Status Optional
Datatype teidata.numeric
commodity (commodity) indicates the substance that is being measured
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Note

In general, when the commodity is made of discrete entities, the plural form should be used, even when the measurement is of only one of them.

Schematron

<sch:rule context="tei:*[@unitRef]">
<sch:report role="infotest="@unit">The @unit attribute may be unnecessary when @unitRef is present.</sch:report>
</sch:rule>
Note
This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system.
<l>So weren't you gonna buy <measure commodity="ice cream"
  quantity="0.5unit="gal">
half
   a gallon</measure>, baby</l>
<l>So won't you go and buy <measure commodity="ice cream"
  quantity="1.893unit="L">
half
   a gallon</measure>, baby?</l>

The unit should normally be named using the standard symbol for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters.

att.media

att.media provides attributes for specifying display and related properties of external media.
Module tei — Schema
Members graphic
Attributes att.internetMedia (@mimeType)
widthWhere the media are displayed, indicates the display width
Status Optional
Datatype teidata.outputMeasurement
heightWhere the media are displayed, indicates the display height
Status Optional
Datatype teidata.outputMeasurement
scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size
Status Optional
Datatype teidata.numeric

att.msClass

att.msClass provides attributes to indicate text type or classification. [10.6. Intellectual Content 10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Members msContents msItem msItemStruct
Attributes
class identifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

att.msExcerpt

att.msExcerpt (manuscript excerpt) provides attributes used to describe excerpts from a manuscript placed in a description thereof. [10.6. Intellectual Content]
Module msdescription — Schema
Members colophon explicit finalRubric incipit msContents msItem msItemStruct quote rubric
Attributes
defective indicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
Status Optional
Datatype teidata.xTruthValue
Note

In the case of an incipit, indicates whether the incipit as given is defective, i.e. the first words of the text as preserved, as opposed to the first words of the work itself. In the case of an explicit, indicates whether the explicit as given is defective, i.e. the final words of the text as preserved, as opposed to what the closing words would have been had the text of the work been whole.

att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.6. Names and Nyms]
Module tei — Schema
Members att.personal [addName forename name orgName persName placeName surname] author collection country district editor geogFeat geogName institution origPlace pubPlace region repository settlement
Attributes att.canonical (@key, @ref)
rolemay 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.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Module tei — Schema
Members formula quote seg
Attributes
notation names the notation used for the content of the element.
Status Optional
Datatype teidata.enumerated

att.personal

att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names]
Module tei — Schema
Members addName forename name orgName persName placeName surname
Attributes att.naming (@role, @nymRef) (att.canonical (@key, @ref))
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
Status Optional
Datatype teidata.enumerated
Legal values are:
yes
(yes) the name component is spelled out in full. [Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.
sort(sort) specifies the sort order of the name component in relation to others within the name.
Status Optional
Datatype teidata.count

att.placement

att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 11.3.1.4. Additions and Deletions]
Module tei — Schema
Members add figure fw head label note
Attributes
place specifies where this item is placed.
Status Recommended
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
top
at the top of the page
bottom
at the foot of the page
margin
in the margin (left, right, or both)
opposite
on the opposite, i.e. facing, page
overleaf
on the other side of the leaf
above
above the line
right
to the right, e.g. to the right of a vertical line of text, or to the right of a figure
below
below the line
left
to the left, e.g. to the left of a vertical line of text, or to the left of a figure
end
at the end of e.g. chapter or volume.
inline
within the body of the text.
inspace
in a predefined space, for example left by an earlier scribe.
<add place="margin">[An addition written in the margin]</add>
<add place="bottom opposite">[An addition written at the
foot of the current page and also on the facing page]</add>
<note place="bottom">Ibid, p.7</note>

att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
Module tei — Schema
Members citedRange licence locus note ref term
Attributes
targetLang specifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
Status Optional
Datatype teidata.language
Schematron

<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]">
<sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert>
</sch:rule>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">
 <ptr target="pol/UDHR/text.xml#pol_txt_1-head"
  targetLang="pltype="tuvxml:id="pol-swh_aln_2.1.1-ptr"/>

 <ptr target="swh/UDHR/text.xml#swh_txt_1-head"
  targetLang="swtype="tuvxml:id="pol-swh_aln_2.1.2-ptr"/>

</linkGrp>

In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.

Note

The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

target specifies the destination of the reference by supplying one or more URI References
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

evaluate (evaluate) specifies the intended meaning when the target of a pointer is itself a pointer.
Status Optional
Datatype teidata.enumerated
Legal values are:
all
if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
one
if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
none
no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
Note

If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

att.ranging

att.ranging provides attributes for describing numerical ranges.
Module tei — Schema
Members att.dimensions [att.damaged [damage] add date del depth dim dimensions ex gap geogFeat height origDate subst supplied unclear width] measure num
Attributes
atLeast gives a minimum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
atMost gives a maximum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
min where the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Status Optional
Datatype teidata.numeric
max where the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Status Optional
Datatype teidata.numeric
confidence specifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
Status Optional
Datatype teidata.probability
Schematron

<sch:rule context="//*[(@atLeast and @atMost) or (@min and @max)]">
<sch:let name="f"
 value="(@atLeast,@min)[1]"/>

<sch:let name="tvalue="(@atMost,@max)[1]"/>
<sch:let name="bothnumbers"
 value="$f castable as xs:float and $t castable as xs:float"/>

<sch:let name="fv"
 value="if ($bothnumbers) then xs:float($f) else ()"/>

<sch:let name="tv"
 value="if ($bothnumbers) then xs:float($t) else ()"/>

<sch:report role="warn"
 test="$bothnumbers and $fv gt $tv">
The numerical range <sch:value-of select="$f"/><sch:value-of select="$t"/> in <sch:value-of select="name(.)"/> may not be valid.
</sch:report>
</sch:rule>
Example
The MS. was lost in transmission by mail from <del rend="overstrike">
 <gap atLeast="1atMost="2"
  extent="one or two lettersreason="illegibleunit="chars"/>

</del> Philadelphia to the Graphic office, New York.
Example
Americares has been supporting the health sector in Eastern
Europe since 1986, and since 1992 has provided <measure atLeast="120000000"
 commodity="currencyunit="USD">
more than
$120m</measure> in aid to Ukrainians.

att.resourced

att.resourced provides attributes by which a resource (such as an externally held media file) may be located.
Module tei — Schema
Members graphic
Attributes
url (uniform resource locator) specifies the URL from which the media concerned may be obtained.
Status Required
Datatype teidata.pointer

att.segLike

att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
Module tei — Schema
Members seg
Attributes att.datcat (@datcat, @valueDatcat, @targetDatcat) att.fragmentable (@part)
function(function) characterizes the function of the segment.
Status Optional
Datatype teidata.enumerated
Note

Attribute values will often vary depending on the type of element to which they are attached. For example, a <cl>, may take values such as coordinate, subject, adverbial etc. For a <phr>, such values as subject, predicate etc. may be more appropriate. Such constraints will typically be implemented by a project-defined customization.

att.sortable

att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure]
Module tei — Schema
Members bibl biblStruct idno item list listBibl msDesc term
Attributes
sortKey supplies the sort key for this element in an index, list or group which contains it.
Status Optional
Datatype teidata.word
David's other principal backer, Josiah
ha-Kohen <index indexName="NAMES">
 <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term>
</index> b. Azarya, son of one of the last gaons of Sura was David's own first
cousin.
Note

The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

att.spanning

att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [11.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]
Module tei — Schema
Members lb pb
Attributes
spanTo indicates the end of a span initiated by the element bearing this attribute.
Status Optional
Datatype teidata.pointer
SchematronThe @spanTo attribute must point to an element following the current element

<sch:rule context="tei:*[@spanTo]">
<sch:assert test="id(substring(@spanTo,2)) and following::*[@xml:id=substring(current()/@spanTo,2)]">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current element <sch:name/>
</sch:assert>
</sch:rule>
Note

The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

att.timed

att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information]
Module tei — Schema
Members gap
Attributes
start indicates the location within a temporal alignment at which this element begins.
Status Optional
Datatype teidata.pointer
Note

If no value is supplied, the element is assumed to follow the immediately preceding element at the same hierarchic level.

end indicates the location within a temporal alignment at which this element ends.
Status Optional
Datatype teidata.pointer
Note

If no value is supplied, the element is assumed to precede the immediately following element at the same hierarchic level.

att.transcriptional

att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [11.3.1.4. Additions and Deletions]
Module tei — Schema
Members add del subst
Attributes att.editLike (@evidence, @instant) att.written (@hand)
statusindicates the effect of the intervention, for example in the case of a deletion, strikeouts which include too much or too little text, or in the case of an addition, an insertion which duplicates some of the text already present.
Status Optional
Datatype teidata.enumerated
Sample values include:
duplicate
all of the text indicated as an addition duplicates some text that is in the original, whether the duplication is word-for-word or less exact.
duplicate-partial
part of the text indicated as an addition duplicates some text that is in the original
excessStart
some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
excessEnd
some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
shortStart
some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
shortEnd
some text at the end of the deletion is not marked as deleted even though it clearly should be.
partial
some text in the deletion is not marked as deleted even though it clearly should be.
unremarkable
the deletion is not faulty. [Default]
Note

Status information on each deletion is needed rather rarely except in critical editions from authorial manuscripts; status information on additions is even less common.

Marking a deletion or addition as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.

causedocuments the presumed cause for the intervention.
Status Optional
Datatype teidata.enumerated
seq(sequence) assigns a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred.
Status Optional
Datatype teidata.count

att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.3. Modification of Attribute and Attribute Value Lists]
Module tei — Schema
Members TEI abbr accMat add addName altIdentifier am bibl biblStruct change cit collection corr country custEvent damage date decoNote del desc dim dimensions district div explicit figure filiation finalRubric forename fw geogFeat geogName graphic head idno incipit label layout lb lg list listBibl locus material measure msDesc msFrag msName msPart name note num orgName origDate origPlace pb persName placeName provenance quote ref reg region relatedItem rubric seal seg settlement signatures stamp surface surfaceGrp surname term text title zone
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Datatype teidata.enumerated
<div type="verse">
 <head>Night in Tarras</head>
 <lg type="stanza">
  <l>At evening tramping on the hot white road</l>
  <l></l>
 </lg>
 <lg type="stanza">
  <l>A wind sprang up from nowhere as the sky</l>
  <l></l>
 </lg>
</div>
Note

The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

subtype (subtype) provides a sub-categorization of the element, if needed
Status Optional
Datatype teidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

Schematron

<sch:rule context="tei:*[@subtype]">
<sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert>
</sch:rule>
Note

When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.3. Modification of Attribute and Attribute Value Lists .

att.written

att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
Module tei — Schema
Members att.damaged [damage] att.transcriptional [add del subst] div figure fw head hi label note p seg text zone
Attributes
hand points to a handNote element describing the hand considered responsible for the content of the element concerned.
Status Optional
Datatype teidata.pointer

Schema msdesc: Datatypes

teidata.certainty

teidata.certainty defines the range of attribute values expressing a degree of certainty.
Module tei — Schema
Used by
Content model
<content>
 <valList type="closed">
  <valItem ident="high"/>
  <valItem ident="medium"/>
  <valItem ident="low"/>
  <valItem ident="unknown"/>
 </valList>
</content>
Declaration
teidata.certainty = "high" | "medium" | "low" | "unknown"
Note

Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter.

teidata.count

teidata.count defines the range of attribute values used for a non-negative integer value used as a count.
Module tei — Schema
Used by
Element:
Content model
<content>
 <dataRef name="nonNegativeInteger"/>
</content>
Declaration
teidata.count = xsd:nonNegativeInteger
Note

Any positive integer value or zero is permitted

teidata.duration.iso

teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
Module tei — Schema
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>

</content>
Declaration
teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Example
<time dur-iso="PT0,75H">three-quarters of an hour</time>
Example
<date dur-iso="P1,5D">a day and a half</date>
Example
<date dur-iso="P14D">a fortnight</date>
Example
<time dur-iso="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.

teidata.duration.w3c

teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Module tei — Schema
Used by
Content model
<content>
 <dataRef name="duration"/>
</content>
Declaration
teidata.duration.w3c = xsd:duration
Example
<time dur="PT45M">forty-five minutes</time>
Example
<date dur="P1DT12H">a day and a half</date>
Example
<date dur="P7D">a week</date>
Example
<time dur="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see the W3C specification.

teidata.enumerated

teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Module tei — Schema
Used by
Element:
Content model
<content>
 <dataRef key="teidata.word"/>
</content>
Declaration
teidata.enumerated = teidata.word
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.

teidata.language

teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]
Module tei — Schema
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="language"/>
  <valList>
   <valItem ident=""/>
  </valList>
 </alternate>
</content>
Declaration
teidata.language = xsd:language | ( "" )
Note

The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.

A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.

language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at http://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at http://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes ‘are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags’.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
private use
An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.

Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.

Examples include

sn
Shona
zh-TW
Taiwanese
zh-Hant-HK
Chinese written in traditional script as used in Hong Kong
en-SL
English as spoken in Sierra Leone
pl
Polish
es-MX
Spanish as spoken in Mexico
es-419
Spanish as spoken in Latin America

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

teidata.name

teidata.name defines the range of attribute values expressed as an XML Name.
Module tei — Schema
Used by
Element:
Content model
<content>
 <dataRef name="Name"/>
</content>
Declaration
teidata.name = xsd:Name
Note

Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

teidata.numeric

teidata.numeric defines the range of attribute values used for numeric values.
Module tei — Schema
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="double"/>
  <dataRef name="token"
   restriction="(\-?[\d]+/\-?[\d]+)"/>

  <dataRef name="decimal"/>
 </alternate>
</content>
Declaration
teidata.numeric =
   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
Note

Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.

A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

teidata.outputMeasurement

teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Module tei — Schema
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"/>

</content>
Declaration
teidata.outputMeasurement =
   token
   {
      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"
   }
Example
<figure>
 <head>The TEI Logo</head>
 <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
   between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
   background.</figDesc>
 <graphic height="600px"
  url="http://www.tei-c.org/logos/TEI-600.jpgwidth="600px"/>

</figure>
Note

These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

teidata.pattern

teidata.pattern defines attribute values which are expressed as a regular expression.
Module tei — Schema
Used by
Content model
<content>
 <dataRef name="token"/>
</content>
Declaration
teidata.pattern = token
Note
A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)
Wikipedia

This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema.

teidata.point

teidata.point defines the data type used to express a point in cartesian space.
Module tei — Schema
Used by
Content model
<content>
 <dataRef name="token"
  restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>

</content>
Declaration
teidata.point = token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }
Example
<facsimile>
 <surface lrx="400lry="280ulx="0uly="0">
  <zone points="220,100 300,210 170,250 123,234">
   <graphic url="handwriting.png"/>
  </zone>
 </surface>
</facsimile>
Note

A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not.

teidata.pointer

teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
Module tei — Schema
Used by
Element:
Content model
<content>
 <dataRef name="anyURIrestriction="\S+"/>
</content>
Declaration
teidata.pointer = xsd:anyURI { pattern = "\S+" }
Note

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

teidata.probability

teidata.probability defines the range of attribute values expressing a probability.
Module tei — Schema
Used by
Content model
<content>
 <dataRef name="double"/>
</content>
Declaration
teidata.probability = xsd:double
Note

Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

teidata.probCert

teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.
Module tei — Schema
Used by
Content model
<content>
 <alternate>
  <dataRef key="teidata.probability"/>
  <dataRef key="teidata.certainty"/>
 </alternate>
</content>
Declaration
teidata.probCert = teidata.probability | teidata.certainty

teidata.replacement

teidata.replacement defines attribute values which contain a replacement template.
Module tei — Schema
Used by
Content model
<content>
 <textNode/>
</content>
Declaration
teidata.replacement = text

teidata.temporal.iso

teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
Module tei — Schema
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
  <dataRef name="token"
   restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>

 </alternate>
</content>
Declaration
teidata.temporal.iso =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
 | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

For all representations for which ISO 8601:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format.

teidata.temporal.w3c

teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.
Module tei — Schema
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
 </alternate>
</content>
Declaration
teidata.temporal.w3c =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

teidata.text

teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.
Module tei — Schema
Used by
Element:
Content model
<content>
 <dataRef name="string"/>
</content>
Declaration
teidata.text = string
Note

Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

teidata.truthValue

teidata.truthValue defines the range of attribute values used to express a truth value.
Module tei — Schema
Used by
Element:
Content model
<content>
 <dataRef name="boolean"/>
</content>
Declaration
teidata.truthValue = xsd:boolean
Note

The possible values of this datatype are 1 or true, or 0 or false.

This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue.

teidata.version

teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Module tei — Schema
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+(\.[\d]+){0,2}"/>

</content>
Declaration
teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
Note

The value of this attribute follows the pattern specified by the Unicode consortium for its version number (http://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

teidata.versionNumber

teidata.versionNumber defines the range of attribute values used for version numbers.
Module tei — Schema
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>

</content>
Declaration
teidata.versionNumber =
   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }

teidata.word

teidata.word defines the range of attribute values expressed as a single word or token.
Module tei — Schema
Used by
teidata.enumerated Element:
Content model
<content>
 <dataRef name="token"
  restriction="[^\p{C}\p{Z}]+"/>

</content>
Declaration
teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

teidata.xpath

teidata.xpath defines attribute values which contain an XPath expression.
Module tei — Schema
Used by
Content model
<content>
 <textNode/>
</content>
Declaration
teidata.xpath = text
Note

Any XPath expression using the syntax defined in 6.2. .

When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP.

teidata.xTruthValue

teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Module tei — Schema
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="boolean"/>
  <valList>
   <valItem ident="unknown"/>
   <valItem ident="inapplicable"/>
  </valList>
 </alternate>
</content>
Declaration
teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )
Note

In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

Schema msdesc: Macros

macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]
Module tei — Schema
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
 </alternate>
</content>
Declaration
macro.limitedContent = ( text | model.limitedPhrase | model.inter )*

macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Module tei — Schema
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.paraPart"/>
 </alternate>
</content>
Declaration
macro.paraContent = ( text | model.paraPart )*

macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Module tei — Schema
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Declaration
macro.phraseSeq =
   ( text | model.gLike | model.attributable | model.phrase | model.global )*

macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]
Module tei — Schema
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Declaration
macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*

macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
Module tei — Schema
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Declaration
macro.specialPara =
   (
      text
    | model.gLikemodel.phrasemodel.intermodel.divPartmodel.global
   )*

macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Module tei — Schema
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">

  <textNode/>
  <classRef key="model.gLike"/>
 </alternate>
</content>
Declaration
macro.xtext = ( text | model.gLike )*
Date: 1.0 (April 2020)