Syriac Manuscripts in the British Library: TEI P5 Customization and Encoding Guidelines for Manuscript Description

This version of the encoding guidelines for Syriac Manuscripts in the British Library: A New Digital Edition of Wright’s Catalogue were drafted in 2024 by David A. Michelson with assistance from William L. Potter and Daniel L. Schwartz. These guidelines are part of a larger a community effort to develop uniform good practice in the cataloguing manuscripts using TEI. They are derived from a common consolidated schema 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 hosted by Syriaca.org. They are licensced under a Creative Commons Attribution 4.0 International license. Users may cite the guidelines in this way: David A. Michelson, et. al., eds. Syriac Manuscripts in the British Library: TEI P5 Customization and Encoding Guidelines for Manuscript Description (Syriaca.org: 2024), https://github.com/srophe/britishLibrary/blob/main/documentation/schema/Syriacamsdesc.html.

Table of contents

1. Encoding guidelines

1.1. Introduction

Welcome to the encoding guidelines for Syriac Manuscripts in the British Library: A New Digital Edition of Wright’s Catalogue. These guidelines describe the methodology used to create TEI XML files for describing Syriac manuscripts according to the schema implemented by Syriaca.org in the project Syriac Manuscripts in the British Library. For the moment, these guidelines cover only the description rather than the transcription of manuscripts. Syriaca,org hopes to expand these guidelines to include transcription in the future. We have chosen to use the TEI guidelines because they allow both a high level of detail and flexibility. We anticipate that this schema can be easily adapted for other Syriac manuscript catalogues and we invite comments and suggestions for improvement.

1.2. Acknowledgements

These guidelines are based on the following sources. The general editors began by following the encoding guidelines for the Fihrist Union Catalogue of Manuscripts from the Islamicate World and the ENRICH TEI P5 ODD, which were then modified by Syriaca.org into a Syriaca TEI for MSS Manual (now deprecated). In many cases, we reproduced the Fihrist guidelines verbatim. In turn these earlier encoding guidelines were updated in 2024 to be largely compatible with the Consolidated TEI P5 Customization and Encoding Guidelines for Manuscript Description for western 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) and James Cummings. When applicable, we have reproduced the consolidated guidelines verbatim in our own guidelines. (Those consolidated guidelines in turn draw in places on earlier western medieval manuscript guidelines created by Patrick Granholm and Eva Nyström for manuscripta.se.)

1.3. General Principles

It is essential to note that we have customized these guidelines specifically for use in digitally encoding the manuscript descriptions made by William Wright in his Catalogue of Syriac Manuscripts in the British Museum (3 vols., 1870-1872). Due to this specialized use, these guidelines do not include all possible TEI XML features which might be desired either for cataloguing Syriac manuscripts or for medieval manuscripts in general. For example, because Wright does not provide detailed descriptions ofthe modern custodial history of the manuscripts we have not utlized those features in these guidelines. Similarly, because the main language of Wright's catalogue is English, these guidelines assume that each file will have English as its main language.

In addition, we have followed the guidelines below with the assumption that the resulting XML files for the Syriac Manuscripts in the British Library project (hereafter SMBL) will be displayed using the custom Srophe App developed by Syriaca.org. We have also made an effort to ensure compatibility (as much as possible) with the HTML tools and transformations developed for the Consolidated TEI P5 Guidelines for Manuscript Description.

1.3.1. Editorial Notes and Interventions

Syriac Manuscripts in the British Library: A New Digital Edition of Wright’s Catalogue has been concieved of as a digital representation of William Wright's catalogue. SMBL is not intended to be a revision of Wright or a re-cataloguing of the manuscripts themselves. For the vast majority of manuscripts described in this project, we (the editors of SMBL) have reproduced Wright's prose verbatim without verifying his descriptions against the manuscripts. While that level of comparison is beyond the scope of this present project, we hope that the digital encoding of SMBL might serve as a foundation for such a new cataloguing effort in the future.

In general we make no claims about the reliability of Wright's descriptions as reproduced in SMBL. Because our goal was to encode Wright's catalogue as written, we have reproduced his attributions of authorship and his dating of the manuscripts, even in cases where these may now be disputed or revised by subsequent scholarship. We, ofcourse, agree that such an update to his catalogue would be valuable in the future. SMBL is published under an open access license and we would be delighted to collaborate with any interested scholars in such a future update. Such a revision, however, needs a base text as a starting point, hence our decision to encode Wright's catalogue "as is" in the first edition of SMBL.

Even with the stated goal of verbatim reproduction, we have had to make a few editorial interventions during the course of encoding. In most casese, these interventions were necessitated by the precision of encoding which required us to make explicit some data which Wright may have left implicit or imprecise in his prose. These interventions have occured in the following primary cases (each of which follow the principles of Wright's own descriptions):

  • When our editors have found a clear typographical or internal inconsistency in Wright's descriptions, we have corrected these errors for the sake of clarity.
  • When our editors have discovered inconsistency in Wright's identification of codicological units, we have further divided single shelfmarks into further manuscript parts in a method similar to that used by Wright himself. Most often our editorial interventions in this regard have been to identify fly-leaves as separate manuscript fragments when Wright may have grouped them together. These new codicological divisions are identifiable because they will share the same roman numeral from Wright's print catalogue but each have a different URI.
  • When Wright has lapsed from his usually methodical listing and numbering of manuscript items, we have attempted in some cases to adapt Wright's prose back to the form of a list of manuscript contents. For example, we have frequently made this editorial intervention when Wright has chosen to describe the undertext of a palimpsest in a paragraph rather than an as an outline of contents.

Finally, SMBL has made one further type of modern editorial intervention in Wright's prose. In the century and a half that have passed since Wright wrote, scholarly values concerning the preservation of cultural heritage have changed profoundly. In some cases, Wright's descriptions reflect his prejudices as a European scholar in the nineteenth century. Because SMBL is an open access resource widely available on the internet, we did not wish to reproduce Wright's prose without context. Accordingly, in some places in which Wright expressed pejorative or other derogratory opinions, we have added an editorial note to indicate that these opinions do not reflect the opinions of the editors of SMBL nor do they represent the approach of contemporary scholars in the field of Syriac studies. ]

Editorial notes made by SMBL related to the various interventions described above have been encoded with the <note> element with type of ‘editorial’. This type distinguishes these editorial notes from notes made by Wright himself which are either without any type or marked as type of ‘footnote’. An example of an modern editorial note is as follows:
<note type="editorial"> <!-- Need to make example from https://bl.syriac.uk/ms/363 --> </note>

1.3.2. References to Locations within a Manuscript

References to a specific location or range of folia within a manuscripts are given in a <locus> element which can be inserted within a number of different elements. The <locus> element marks the location of the parent element’s material within the manuscript and thus should be nested within the element it modifies. Typically the <locus> will refer to a folio or a range of folio numbers within the manuscript. When describing folio numbers, it is our policy to follow Wright's usage and use ‘a’ to refer to the recto of a folio, and ‘b’ to refer to the verso. Where Wright does not specify recto or verso, we encoded a folio number without ‘a’ or ‘b’. In prose, there should always be a whitespace between the folio number and the ‘a’ or ‘b’. But in attribute values, there should be no whitespace, e.g. ‘232b’:
<locus from="232b">Fol. 232 b</locus>

A text node (eg. ‘foll. 21 a-22 b’) is not required for many uses of <locus> (such as when it is used nested in an <msItem>), but least one attribute value must also be encoded with every <locus>, either from or to or both. (Since Wright's catalogue does not often give ending ranges, the to occurs less in the data). These attribute values may be used in the future to enable links to folio images or calculation of lengths of manuscript items. Frequently in Wright’s catalogue the beginning location of a manuscript item is given, but not the ending location. In this situation, our policy is to record only the listed opening location in Wright’s catalogue as the beginning of the range in the attribute from. We do not supply a to attribute unless Wright has indicated on what folio the msItem ends, for example by citing an <explicit> or <finalRubric>.

The following examples illustrate common uses of <locus>. Whenever possible, the designation folio/folia and their abbreviations were included in the text node of <locus>. as in the exampls below. (Please be aware that Wright uses "Fol." for a single folio and "Foll." for a range of folia. We adapt Wright's capitalization of based on context. If "Fol." stands alone in a list it is capitalized. If "fol." occurs in the middle of other prose it is capitalized according to the rules of the sentence.):
<msItem>  <locus from="232b">Fol. 232 b</locus>  <title ref="http://syriaca.org/work/9687"   xml:lang="en">The    Gospel of S. Matthew</title> </msItem> <!--...--> <additions>  <list>   <item>    <label>Colophon</label>    <locus from="184a"/>    <p>Of the note written by the scribe on <locus from="184a">fol. 184 a</locus> the greater part        has been erased, but from what remains it appears        that this book was copied for <persName>a priest          named Lazarus</persName>.</p>   </item>  </list> </additions>

Notes for Review Editors (2024)

Please ignore the missing white space in the text node of <locus> For example, in the text nodes of locus for folia numbers, such as
<locus from="81a">fol. 81a</locus>
this text node should have a space between ‘81’ and ‘a’ like this
<locus from="81a">fol. 81 a</locus>
, but you do not need to change it, we have a script make this correction across all the data. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

Deprecated Practices and Legacy Data:

As a legacy of an earlier encoding model, the SMBL data contains some folio ranges encoded as numerals in to without "a" or "b". In this earlier data model, we attempted to deduce the end of ranges for manuscript items when not specified by Wright. Similarly when Wright's prose indicated that his description applied only to a single folio (for example when describing a marginal note), our policy was previously to list that location in both from and to attributes. After 2022, we ceased to encode in this way. While we have left these estimates in the data, documents revised since 2022 longer add estimated data in this way.

Divergences from Consolidated Schema:

In SMBL we have assumed that <locus> refers to a folio or folio range unless otherwise indicated. Accordingly, we do not use the scheme attribute to indicate the foliation scheme except in cases where the <locus> refers to something other than a folio, such as a column.

1.3.3. Indentification of Persons, Places, Titles, Citations, and Manuscripts with Syriaca.org URIs

One of the distinctive features of SMBL is that we have integrated our catalogue with the reference works published by Syriaca.org in order identify the following entities: persons, places, literary works, citations of published bibliography, and references to manuscripts. For each of these entity types, Syriaca.org has published an ‘authority file’ which assigns a URI or Uniform Resource Identifier to every unique entry. These authority files include The Syriac Biographical Dictionary, The Syriac Gazetteer, The New Handbook of Syriac Literature , and A Comprehensive Bibliography on Syriac Studies, in addition to Syriac Manuscripts in the British Library.

In these authority files, each entity is an individual abstract concept identified by a unique URI. For example, the person known as Ephrem the Syrian is identified by the URI: http://syriaca.org/person/13 and the city of Edessa where he spent much of his life is identified as http://syriaca.org/place/78. The necessity of using unique strings of characters instead of traditional names arises from the occurrence of homonymous entities. For example, The Syriac Gazetteer has entries for 69 different churches and monasteries each with the name ‘Mar George’. Accordingly, all Syriaca.org URIs are unique—each identifying only one conceptual entity. Thus, every ‘Church of Mar George’ is assigned a separate URI.

Syriaca.org URIs are not merely random strings of text and numbers; they are HTTP URIs, meaning that each URI is also a URL (a Uniform Resource Locator, e.g. an HTTP address). Thus, Syriaca.org’s URI for Ephrem the Syrian, http://syriaca.org/person/13, is also a valid HTTP address. The benefit of using HTTP URIs is that these URIs are ‘self-descriptive’ in that each URI is also an HTTP link to a web document describing or defining the concept identified by the URI. Although perhaps obvious to state, the web document which is returned from a Syriaca.org URI is only a definition of the concept named by the URI, not the entity itself (thus the address http://syriaca.org/place/78 does not allow one to download the real-world city of Edessa, but a web page describing that city!).

In the Syriaca.org data model, each URI represents a conceptual thing with a mental existence related to, but not reducible to, its historical or physical manifestation. Syriaca.org adopted this broad definition so that mythological and other ahistorical persons, places, and concepts can be assigned URIs. For example, the concept identified by the URI http://syriaca.org/person/13 identifies not only the historical person Ephrem the Syrian, but also the supra-historical hagiographical and pseudepigraphal traditions about him. Following this same logic, any historical concept can be described in the Syriaca.org URI model, even if its historical existence was only in the cultural imaginary.

The Syriaca.org authority files and URIs are central to the data model of SMBL, accordingly the sections below describe in greater detail how we have encoded these entities throughout the data.

Notes for Review Editors (2024)

If you find that a <persName>, a <placeName>, or a <bibl> used for a modern bibliographic citation is missing a URI, please follow these steps: Search for a URI at Syriaca.org or the Comprehensive Syriac Bibliography If you do not find a URI, create a temporary URI following the guidelines provided to you. Insert the new temporary id into the ref for the <persName> or <placeName> or in bibl/ref/target (you will need to create the <ref> and add it inside the <bibl>). Note: You do NOT need to add URIs to <title> or <ref> elements for Syriac literary works except in the case of books of the Bible. There are Syriaca.org URIs available for those, so please mark those if possible. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

1.3.3.1. Personal Names

As a general rule personal names have been tagged, for example when they occure inside the elements <author>, <editor> or in any descriptive element such as the <handNote> or an <item> in <additions>. In these cases, the name is wrapped with the element <persName> and the language(s) of the name supplied with attribute xml:lang. Exceptions to this rule were made when a personal names occurs as part of a title of a work (Extracts from the Homilies of John Chrysostom) or as part of a place name (e.g. The Convent of Mar Isaac). In these cases the prose was marked as a title or place name instead and the personal names were not tagged:
<msItem>  <title xml:lang="en">Works of Gregory bar Hebraeus</title> </msItem>
<origPlace ref="http://syriaca.org/place/360">Convent of S. Mary Deipara.</origPlace>
All <persName> elements (or else the containing <author> or <editor> element) are required to have a ref attribute which points to a Syriaca.org person URI published in the Syriac Biographical Dictionary. A URI is a Uniform Resource Identifier which is a unique identifying number for each person. For example the URI https://syriaca.org/person/13 identifies Ephrem the Syrian in this first example:
<author ref="http://syriaca.org/person/13">  <persName xml:lang="en">Ephraim</persName> </author>
The <persName> element can also be used inside prose descriptions.
<note>  <persName ref="http://syriaca.org/person/51">Severus</persName> is cited on <locus from="224a">fol.    224 a</locus>. </note>

Notes for Review Editors (2024)

In some files we may have previously over-normalized the spelling of author names compared to what Wright provides (e.g., changing Jacob of Batnae to Jacob of Serugh). We now wish to revert these changes, so please check and restore the name spelling as Wright provides it. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

Deprecated Practices and Legacy Data:

Our policy is to report the names in the same prose given by Wright. In a future update of SMBL, we may also provide a uniform name where the spelling or name used by Wright is no longer commonly used in scholarship. A few examples of these are already present in our data in the form below (where the "supplied" type reflects Wright's Romanization of the name. Encoders should not enter these "uniform" names as they will be inserted later by a script.
<author ref="http://syriaca.org/person/10">  <persName xml:lang="en" type="uniform">Aphrahaṭ</persName>  <persName xml:lang="en" type="supplied">Aphraates</persName> </author>

Divergences from Consolidated Schema:

Because Syriaca.org already provides an integrated authority file for persons using Syriaca.org URIs, we do not use the key attribute required by the Consolidated Schema. We also do not use the element <orgName> since it is not a useful entity for our historical data, instead Syriaca.org uses the <persName> element in a slightly broader manner than the TEI guidelines. A <persName> element may be used to refer to a name for a single person or a group of persons.

1.3.3.2. Place Names

As a general rule place names have been tagged with either <origPlace> or with <placeName>, for example when they occur inside in any descriptive element such as <note>, <handNote>, or an <item> in <additions>. In most cases, the place name is wrapped with the element <placeName> and the language(s) of the name supplied with attribute xml:lang. Exceptions to this rule are as follows:

  • In the description of the manuscript origin (on which, see more documentation below), the prose place name is placed directly in the text node of the <origPlace> element (without using <placeName>) while any other place names mentioned in reference to the place of origin are wrapped in <placeName>:
    <origPlace ref="http://syriaca.org/place/360">Convent of S. Mary Deipara, in the desert of <placeName ref="http://syriaca.org/place/289">Scete</placeName>.</origPlace>
    .
  • When a place name occurs as part of a title of a work, it is not marked as a <placeName>:
    <title>Hom. liii. On the calamities reported to have befallen the city of Alexandria</title>
    nor is a place name marked when it is part of a personal name:
    <persName>Paul of Callinicus</persName>
    In these cases (shown above) the prose was marked as a title (using either <title> or <ref>) or <persName> instead and the internal references t0 place names were not tagged.
All <placeName> elements or <origPlace> elements are required to have a ref attribute which points to a Syriaca.org place URI published in The Syriac Gazetteer. A URI is a Uniform Resource Identifier which is a unique identifying number for each place. For example the URI http://syriaca.org/place/78 identifies the city of Edessa in these examples:
<origPlace>  <placeName ref="http://syriaca.org/place/78">Edessa</placeName> </origPlace>
<p>On <locus from="258a">fol. 258 a</locus>, after the doxology, we read the following note, giving the date and stating that the volume was written at <placeName ref="http://syriaca.org/place/78">Edessa</placeName>, at the expense of the deacon <persName>Thomas of Zěmārtā    Castra</persName>.</p>

Our policy is to report the place names in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform name where the spelling or name used by Wright is no longer commonly used in scholarship.

Divergences from Consolidated Schema:

Because Syriaca.org already provides an integrated authority file for places using Syriaca.org URIs, we do not use the key attribute required by the Consolidated Schema nor do we include the nested information in <origPlace> such as <country>, <region> and <settlement>. These relationships can be found separately in The Syriac Gazetteer.

1.3.3.3. References to Literary Works

As a general rule references to titles of literary works have been tagged in one of two methods.

  • When the title is identifying the intellectual contents of a manuscript item, it is encoded with <title> as a child of <msItem>. When encoding with the <title> element, the language of the prose in the <title> text node must also be indicated with attribute xml:lang. Rules for encoding titles as part of manuscript items are discussed in greater detail below.
  • When a reference to a literary work is made elsewhere in the XML document it is encoded with <ref> as a child of <note>.
At present the state of authority control for titles of Syriac works is incomplete, so we have not required references to URIs for works in SMBL. When possible we have included URIs published in The New Handbook of Syriac Literature . A URI is a Uniform Resource Identifier which is a unique identifying number for each literary work (as a conceptual entity). References to URIs for literary works, (using either <title> or <ref>) are marked up in an attribute value. For <title> the URI is placed in a ref attribute. For the element <ref> the URI is placed in a target attribute. For example the URI http://syriaca.org/work/1 identifies the book of Genesis in the Peshitta Version in this <title>:
<msItem xml:id="a1" n="1" defective="true">  <locus from="1a"/>  <title xml:lang="en"   ref="http://syriaca.org/work/1">The    book of Genesis, according to the Peshitta    version.</title>  <rubric xml:lang="syr">   <locus from="2b" to="2b"/>ܒܪܝܬܐ ܣ̣ܦܪܐ    ܩܕܡܝܐ ܕܐܘܪܝܬܐ</rubric> </msItem>
In this example, a <note> refers to an unspecified version of the book of 2 Maccabees using the URI https://syriaca.org/work/9578:
<note>See <ref target="http://syriaca.org/work/9578">2    Maccabees, ch. i. 18, seqq.</ref> </note>
In this example, a <note> refers to a work, the Constitutiones Apostolorum, for which there is no Syriaca.org URI. In this case no target is used, but the instead a type attribute value of "work" must be applied (to distiguish from other uses of <ref> in the XML document.
<note>These are extracts from <ref type="work">the eighth book    of the Constitutiones Apostolorum</ref>; see <bibl>Labbe, t. i., coll. 153, seqq.</bibl>.</note>

Our policy is to report the references to works in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform name where the form used by Wright is no longer commonly used in scholarship.

Divergences from Consolidated Schema:

Because Syriaca.org already provides an integrated URI authority file for works using Syriaca.org URIs, we do not use the key attribute recommended by the Consolidated Schema.

1.3.3.4. Bibliographic Citations

Citations of printed biblographic items (books, articles, etc.) have been tagged with the <bibl> element. These citations can be found in two places:

  • They may be grouped in a bibliography located in the <additional> section of each entry. Guidelines for this bibliography (including examples of child elements nested in <bibl>) are given below.
  • Citations have also been marked up with <bibl> throughout the manuscript description occuring as child elements of <msItem>, <note>, or other descriptive elements. For this second form of citation, we have generally refrained from adding additional markup inside the <bibl> element except for linking to URIs.

In both cases, the bibliographic citation may be linked with a URI by using a child element <ref> with the URI is placed in a target attribute on <ref>. At present the state of authority control for Syriac bibliography is incomplete. Accordingly, we have only encoded URIs for bibliographic citations when available. Currently we rely on two sources of URIs. Some citations are linked with uris of the format ‘http://syriaca.org/bibl/8’ from Syriaca.org. Others are marked with URIs from The Comprehensive Bibliography on Syriac Studies of the format ‘https://www.zotero.org/groups/4861694/a_comprehensive_bibliography_on_syriac_studies/items/WMADLJWW/library’. In a future development, all of these citation URIs will be merged to a format of ‘http://syriaca.org/cbss/WMADLJWW’.

This modified example from https://bl.syriac.uk/ms/28 illustrates the use of the second type of citation:
<note>See<bibl>Assemani, Bibl. Or., t. ii., p. 335 <ref target="https://www.zotero.org/groups/4861694/a_comprehensive_bibliography_on_syriac_studies/items/WMADLJWW/library"/>  </bibl>.</note>

Our policy is to report the references to bibliography in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform citation where the form used by Wright is no longer commonly used in scholarship.

1.3.3.5. Cross-References to Other Manuscripts

Cross-references in the description to other manuscripts should be enclosed in <bibl> tags with type of value MS. When possible the cross-reference may also be linked linked with a child <ptr> element with target attribute pointing to the URI for the other manuscript.

At present the state of authority control for Syriac manuscripts is incomplete. Accordingly, we have only encoded URIs in the case of cross-reference to manuscripts within SMBL. This example from manuscript Add. 14,533 https://bl.syriac.uk/ms/260 shows how SMBL URIs are encoded to show a relationship between Add. 14,533 and two other manuscripts (Add. 12,155 and Add. 14,532):
<note>In part identical with the contents of <bibl type="MS">Add. 12,155<ptr target="https://bl.syriac.uk/ms/30"/>  </bibl> and <bibl type="MS">Add. 14,532<ptr target="https://bl.syriac.uk/ms/259"/>  </bibl>.</note>
When a manuscript reference refers either to a folio locus or to an entry number in Wright's catalogue, then a <citedRange> element should be added inside the <bibl>.
<note>See <bibl>Add. 14,728<ptr target="https://bl.syriac.uk/ms/628"/>, <citedRange unit="fol">fol. 239 a</citedRange>  </bibl>.</note>
<note>See <bibl>Add. 14,575<ptr target="https://bl.syriac.uk/ms/311"/>, <citedRange unit="entry">no. 5</citedRange>  </bibl>.</note>
For references to manuscripts outside of SMBL we do not include a URI as illustrated in this modifed example from https://bl.syriac.uk/ms/739
<note type="footnote" xml:lang="en">See the similar heading in the <bibl type="MS">Bodleian manuscript, Hunt.    109</bibl>.</note>

Our policy is to report the references to manuscripts in exactly the same prose given by Wright. In a future update of SMBL, we may also provide a uniform shelfmark where the form used by Wright is no longer commonly used in scholarship.

Divergences from Consolidated Schema:

SMBL has used <citedRange> which is not mentioned in the Consolidated Schema guidelines but is conformant with the TEI guidelines.

1.3.4. Formatting

We have avoided marking up formatting using the <hi> element. The empty element <lb> has been used to indicate line breaks (e.g. line beginnings) when Wright provides transcriptions of Syriac or Arabic text.

1.3.5. Attribute values

Some attributes can take more than one value, in which case the values are separated by a single whitespace. For example, in this case two Syriaca.org work URIs are included in the same ref:
<title xml:lang="en"  ref="http://syriaca.org/work/9568 http://syriaca.org/work/9542">Jeremiah and Lamentations</title>
Attribute values forming more than one word in natural language have been separated by a hyphen, - (U+2010), as in this example of medium:
<handNote xml:id="handNote2" scope="minor"  script="syr" medium="red-ink">  <ref target="#a2"/>The Ammonian sections and Eusebian canons are marked in the text with red ink. </handNote>

In a few rare cases, ‘camelCase’, has been used for attribute values forming more than one word in natural language.

Divergences from Consolidated Schema:

SMBL has prefered to use a hyphen rather that camelCase for attribute values longer than one word in length.

1.3.6. Transcription

The <rubric>, <incipit>, <explicit>, <finalRubric>, and <quote> elements are used to encode Syriac text transcribed from the manuscripts. The have been reproduced verbatim from William Wright's catalogue. Caveat lector! Transcriptions have not been re-checked against the original manuscripts. In addition, the <quote> element has been used to encode prose (in any language) which Wright marked with quotation marks (e.g. inverted commas).

In all cases these elements should be marked with the an xml:lang attribute to indicate the language of the transcribed text.

1.3.6.1. Abbreviations and Expansions

Sometimes Wright offers an expansion of abbreviations found in the manuscripts. In these cases we have provided Wright's expanded prose using the nesting elements <choice> and children <abbr>, and <expan>. In these cases, Wright is credited as the one responsible for the expansion through the use of resp with a value pointing to the xml:id for Wright: https://bl.syriac.uk/documentation/editors.xml#wwright. See this modified example from Add. 17,262 (https://bl.syriac.uk/ms/1078) in which Wright expands a Syriac abbreviation:
<choice>  <abbr>   <foreign xml:lang="syr">ܘܡ܏ܣܪ</foreign>  </abbr>  <expan resp="https://bl.syriac.uk/documentation/editors.xml#wwright">   <foreign xml:lang="syr">ܘܡܣܪܩܘܬܐ</foreign>  </expan> </choice>
For the sake of clarity, the SMBL editors have sometimes expanded abbreviations in Wright's own prose using the nesting elements <choice> and children <abbr>, and <expan>. This is one of the few ways in which we have modified Wright's original publication. See this example in which we have expanded ‘Ps.’ to ‘Psalm’ to facilitate search results:
<title>Commentary on <choice>   <abbr>Ps.</abbr>   <expan>Psalm</expan>  </choice> xcii.</title>

Divergences from Consolidated Schema:

SMBL has prefered to use a <abbr>, and <expan> rather than <ex> as used in the Consolidated Schema.

1.3.6.2. Sic [UNDER REVISION]

SMBL uses <sic> to both to mark errors reported by Wright using ‘sic’ and to report mistakes made by Wright identified by the SMBL editors. At present we are still revising our guidelines on the use of <sic> and those will be added here once this revision is complete. We are also considering how to represent questions marks used by Wright in the text.

Notes for Review Editors (2024)

Please ignore the use of <sic> as an element or in prose. Similarly please ignore Wright's use of square brackets [...]. These will be normalized by a script at a later stage. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

1.3.6.3. Supplied [UNDER REVISION]

The <supplied> element has been used both for Wright's own editorial additions and for editorial additions to Wright's catalogue made by the editors of SMBL, At present we are still revising our guidelines on the use of <supplied> and those will be added here once this revision is complete. These guidelines will include the use of resp with a value pointing to the xml:id for Wright or the modern SMBL editors and the use of the nesting elements <choice> and children <orig>, and <reg>.

Notes for Review Editors (2024)

Please ignore the use of <supplied> as an element, as an attribute value or in prose. These will be normalized by a script at a later stage. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

1.3.6.4. Deletions [UNDER REVISION]

in rare cases, deletions by the scribe or later annotators which are reported by Wright have be recorded using the <del> element. At present we are still revising our guidelines on the use of <supplied> and those will be added here once this revision is complete.

1.3.6.5. Gaps [UNDER REVISION]

In rare cases, gaps in the manuscriptwhich are reported by Wright have be recorded using the <gap> element. At present we are still revising our guidelines on the use of <supplied> and those will be added here once this revision is complete.

1.3.7. Quotations from the Manuscript

When Wright gives a quotations from a manuscript, outside of elements such as <incipit>, <explicit> and so on, these have been enclosed in the <quote> element and marked with an xml:lang attribute.

In addition, <quote> has been used whenever Wright provides text in quotation marks, which may be a quotation of a third source (beyond the manuscripts and his catalogue) or which may be his English translation of a quotation from a manuscript.

Divergences from Consolidated Schema:

SMBL uses the <quote> element instead of the <q> element used in the Consolidated Schema.

1.3.8. Phrases and Words in Languages Other Than English

Phrases or words in other languages than English are 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.

This is a modified example from https://bl.syriac.uk/ms/3:
<TEI xml:lang="en" xmlns="http://www.tei-c.org/ns/1.0"> ... <rubric xml:lang="syr">   <locus from="112a" to="112a"/>ܟܬܒܐ ܕܝܫܘܥ ܒܪܗ ܕܢܘܢ </rubric> </TEI>

By default the Srophe App will display text in the <foreign> in italic unless it is marked as Syriac, in which case additional right-to-left formatting will be applied. For a list of allowed language attribute values see below.

1.3.9. Transcription of Characters, Symbols, and Diacritics in Unicode

All text and symbols have been encoded using the Unicode Standard. When Wright has Romanized Syriac characters, we have followed his Romanization system and used unicode diacritics for macrons, dots above, below, etc. For representation of alaph (ܐ) and ʿayin (ʿē, ܥ) we have changed Wright's use of apostrophe (') for the unicode half-ring characters, U+02BE ʾ Modifier Letter Right Half Ring and U+02BF ʿ Modifier Letter Left Half Ring, respectively.

1.3.9.1. Images and Characters that Cannot be Encoded

Wright's printed catalogue includes characters and symbols for which there is not yet a unicode character or code point. Examples include the use of omega as a Syriac vowel or the use of crosses, circles, and dots as end of paragraph markers. In the cases where unicode characters are not available or where Wright provides a diagram or image which cannot be reproduced using XML (for example characters arranged as a cross or circle), we have included a note in the <decoDesc> referring users to a .pdf version of Wright's catalogue.

This is a modified example from https://bl.syriac.uk/ms/3:
<decoDesc>  <decoNote type="missingContent">The printed edition of    Wright's catalogue contains characters or images which    cannot be encoded for display as electronic text. Please    refer to the printed catalogue to view these characters    or images. </decoNote> </decoDesc>

Notes for Review Editors (2024)

If you need to enter transliterated or Romanized Syriac using Latin characters, please use combined Unicode characters (e.g. U+1E6D Latin Small Letter T with Dot Below) for dots and diacritics to represent characters such as ḥ, ṭ, ṣ, š, etc. For representation of alaph (ܐ) and ʿayin (ʿē, ܥ), please change Wright's use of apostrophe to the unicode half-ring characters, U+02BE ʾ MODIFIER LETTER RIGHT HALF RING (for aleph) and U+02BF ʿ MODIFIER LETTER LEFT HALF RING (for ʿayin, respectively). You can cut and paste most of these characters from the list here. In some cases you may find the characters $ or % in the text. These were used in an early stage to mark where to enter non-Roman text. $ indicates Syriac text should be entered. In most cases you should check to see if the Syriac is complete, most likely it was entered but this character was not deleted, if so you may delete it. If needed, add the missing Syriac and then delete. The % character was used to indicate that text in Arabic, Greek, Armenian or other non-Roman script should be entered. If you are able, enter that text as described above. Lastly, when you find that the PDF of Wright's catalogue contains either images or special characters which cannot be displayed using Syriac or Greek unicode fonts, please open a GitHub issue, apply the label "cannot display", and include this message in the title of your issue: “PDF contains characters or images which cannot be displayed in XML.” Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

1.5. Subject Classifications [UNDER REVISION]

SMBL reproduces the subject classifications used by Wright in his catalogue. A further description of this taxonomy will be added here.

1.6. Manuscript Description

All manuscript description takes place in the <msDesc> element which is contained in a parent <sourceDesc> element. Within <msDesc> and its descendent elements 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. In the case of the Syriac manuscripts in the British Library, it is often the case that manuscripts which were originally physically distinct, are now bound together. In such cases, multiple codicological units can be found sharing a single shelfmark. Add. 12,133 is an example of one binding containing multiple manuscripts.

If the manuscript forms a single codicological unit, its intellectual content, physical description, and history are described directly under the <msDesc> element.

If the manuscript comprises multiple codicological units, each unit has been described in a separate <msPart> element, and only information common to the whole manuscript is described directly under the <msDesc> element in this manner:
<msDesc xml:id="manuscript-1"> <!-- Common information -->  <msPart xml:id="Part1" n="1"> <!-- Codicological unit 1 -->  </msPart>  <msPart xml:id="Part2" n="2"> <!-- Codicological unit 2 -->  </msPart> </msDesc>
As show above, the <msDesc> element should always have a unique xml:id which is formed from the URI for the manuscript according to the pattern manuscript-(URI number). For mult-part manuscript, the <msPart> element will also have an xml:id and an n created from the number of the manuscript part.

1.6.1. The Manuscript Identifier

Information about the location and shelfmark of the manuscript is given in the <msIdentifier> element using the following elements in the following order: <country>, <settlement>, <repository>, <collection>, and <idno>.

The Syriac manuscripts in the British Library have had a number of variant indentifiers. Not only can the current shelfmarks be expressed with or without commas (Add. 12,178 or Add. 12178) or the prefixes ‘Additional’, ‘Add’. or ‘MS’, but Wright also assigned roman numerals to his entries which have been widely used in later scholarship. One goal of publishing SMBL is to create permanent URIs to facilitate easier citation of the manuscripts in digital databases. Accordingly, SMBL has assigned a URI as the primary identifier encoded in the <idno> in the <msIdentifier>. Using these URIs, the <msIdentifier> in each file looks similar to this example from Add. 12,178 which is URI https://bl.syriac.uk/ms/10:
<msIdentifier>  <country>United Kingdom</country>  <settlement>London</settlement>  <repository>British Library</repository>  <collection>Oriental Manuscripts</collection>  <idno type="URI">https://bl.syriac.uk/ms/10</idno>  <altIdentifier>   <idno type="BL-Shelfmark">Add. 12,178</idno>  </altIdentifier>  <altIdentifier>   <idno type="BL-Shelfmark-display">London, BL, Add.      12,178</idno>  </altIdentifier>  <altIdentifier>   <idno type="BL-Shelfmark-simplified">BL Add MS 12178</idno>  </altIdentifier>  <altIdentifier>   <collection>William Wright, Catalogue of the Syriac      Manuscripts in the British Museum Acquired since the      Year 1838</collection>   <idno type="Wright-BL-Arabic">161</idno>  </altIdentifier>  <altIdentifier>   <collection>William Wright, Catalogue of the Syriac      Manuscripts in the British Museum Acquired since the      Year 1838</collection>   <idno type="Wright-BL-Roman">CLXI</idno>  </altIdentifier> </msIdentifier>
In the example above the type values on the element <idno> are controlled to facilitate searching by type of shelfmark or URI.
For a multi-part manuscript, the <msIdentifier> which is a direct child of <msDesc> will contain the shelfmarks which are shared by both parts (for example if both are part of Add. 12,133). The identifiers and shelfmarks which are unique to the individual parts will be contained by separate <msIdentifier> elements which are direct children of <msPart>, as in this example:
<sourceDesc>  <msDesc xml:id="manuscript-1">   <msIdentifier>    <country>United Kingdom</country>    <settlement>London</settlement>    <repository>British Library</repository>    <collection>Oriental Manuscripts</collection>    <idno type="URI">https://bl.syriac.uk/ms/1</idno>    <altIdentifier>     <idno type="BL-Shelfmark">Add. 12,133</idno>    </altIdentifier>    <altIdentifier>     <idno type="BL-Shelfmark-display">London, BL, Add.          12,133</idno>    </altIdentifier>    <altIdentifier>     <idno type="BL-Shelfmark-simplified">BL Add MS          12133</idno>    </altIdentifier>   </msIdentifier> <!--...-->   <msPart xml:id="Part1" n="1">    <msIdentifier>     <idno type="URI">https://bl.syriac.uk/ms/2</idno>     <altIdentifier>      <idno type="BL-Shelfmark">Add. 12,133, foll.            1–108</idno>     </altIdentifier>     <altIdentifier>      <idno type="BL-Shelfmark-display">London, BL, Add.            12,133, foll. 1–108</idno>     </altIdentifier>     <altIdentifier>      <idno type="BL-Shelfmark-simplified">BL Add MS            12133, foll. 1-108</idno>     </altIdentifier>     <altIdentifier>      <collection>William Wright, Catalogue of the            Syriac Manuscripts in the British Museum Acquired            since the Year 1838</collection>      <idno type="Wright-BL-Arabic">9</idno>     </altIdentifier>     <altIdentifier>      <collection>William Wright, Catalogue of the            Syriac Manuscripts in the British Museum Acquired            since the Year 1838</collection>      <idno type="Wright-BL-Roman">IX</idno>     </altIdentifier>    </msIdentifier>   </msPart> <!--...-->   <msPart xml:id="Part2" n="2">    <msIdentifier>     <idno type="URI">https://bl.syriac.uk/ms/3</idno>     <altIdentifier>      <idno type="BL-Shelfmark">Add. 12,133, foll.            109–169</idno>     </altIdentifier>     <altIdentifier>      <idno type="BL-Shelfmark-display">London, BL, Add.            12,133, foll. 109–169</idno>     </altIdentifier>     <altIdentifier>      <idno type="BL-Shelfmark-simplified">BL Add MS            12133, foll. 109-169</idno>     </altIdentifier>     <altIdentifier>      <collection>William Wright, Catalogue of the            Syriac Manuscripts in the British Museum Acquired            since the Year 1838</collection>      <idno type="Wright-BL-Arabic">51</idno>     </altIdentifier>     <altIdentifier>      <collection>William Wright, Catalogue of the            Syriac Manuscripts in the British Museum Acquired            since the Year 1838</collection>      <idno type="Wright-BL-Roman">LI</idno>     </altIdentifier>    </msIdentifier>   </msPart>  </msDesc> </sourceDesc>

Divergences from Consolidated Schema:

SMBL uses a different set of type values.

1.6.2. The Heading

SMBL has used the <head> element to provide summary information about the manuscript or manuscript part.

An auto-generated paragraph describing the masnucript contents has been inserted into the <head> element as a <note> with a type attribute whose value is contents-note. This note provides the title(s) of the first five top-level <msItem> elements. Their values are copied from the <title> element of each item; final elipsis indicates that there are more than five top-level manuscript items. Finally, the total number of <msItem> elements, including descendant manuscript items, is included in the note.

See the following example, from https://bl.syriac.uk/ms/1023:
<note type="contents-note">This manuscript contains: Severus. The Hymns of Severus, etc., here only 159 (ܩܢܛ) in number.; Supplicatory hymns of every kind, arranged according to the eight tones.; Cantus ad Magnificat, arranged according to the eight tones.; Additional hymns, arranged according to the eight tones.; Additional.; ... In total, including sub-sections, this manuscript contains 26 items.</note>

For composite manuscripts, the contents note will instead direct the reader to the individual parts for a summary of the contents.

Following the contents note, the <head> element may have a number of <listRelation> elements.

SMBL has recorded the genre classification provided in Wright's Catalogue in a <listRelation> element with type whose value is Wright-BL-Taxonomy. The taxonomy is recorded in a child <relation> element given a name attribute of dcterms:type and a ref attribute of http://purl.org/dc/terms/type. The manuscript or part URI is given as the value of the active attribute. A corresponding xml:id attribute value from the <category> in the <taxonomy> element is referenced as the value of the passive attribute. Finally, the human-readable label from the same <category> element is used as a text node of the relation's child <desc> element.

An example of Wright's taxonomy encoded in the <head> element:

<listRelation type="Wright-BL-Taxonomy">  <relation name="dcterms:type"   ref="http://purl.org/dc/terms/type" active="https://bl.syriac.uk/ms/1020"   passive="#choral">   <desc>Choral Books</desc>  </relation> </listRelation>

For composite manuscripts, which contain one or more <msPart> elements, the manuscript record as well as each individual part will have a <listRelation> element defining the part-to-whole relationships between the composite manuscript and its parts.

The <listRelation> element has been given a type attribute with the values composite-to-parts or part-to-composite. A child <desc> element provides a human-readable explanation of the list of relations. It is followed by a series of <relation> elements that define the part-to-whole or whole-to-part relationships.

The <relation> element includes active and passive attributes whose values are the SMBL URIs for the composite manuscript and the specific manuscript part. Each element also includes a name attribute and ref attribute that define the relationship. The active, passive, and ref attributes can be understood as a triple, so in the example below one migh read: https://bl.syriac.uk/ms/100 has-unspecified-codicological-part https://bl.syriac.uk/ms/101. Finally, a child <desc> element provides a human-readable label consisting of the shelfmark, and folios if applicable, of the composite or part referenced in the passive attribute.

SMBL has used the following values for the name and ref attributes for composite-to-parts type <listRelation> elements:

Name attribute Ref attribute
syriaca:has-unspecified-codicological-part #syriaca:has-unspecified-codicological-part
syriaca:has-palimpsest-upper #syriaca:has-palimpsest-upper
syriaca:has-palimpsest-lower #syriaca:has-palimpsest-lower
The following example from https://bl.syriac.uk/ms/100 shows the use of a <listRelation> element for relating composites and their parts:
<listRelation type="composite-to-parts">  <desc>This composite manuscript consists of 3 distinct parts:</desc>  <relation name="syriaca:has-unspecified-codicological-part"   ref="#syriaca:has-unspecified-codicological-part" active="https://bl.syriac.uk/ms/100"   passive="https://bl.syriac.uk/ms/101">   <desc>Add. 14,438, foll. 1–49</desc>  </relation>  <relation name="syriaca:has-unspecified-codicological-part"   ref="#syriaca:has-unspecified-codicological-part" active="https://bl.syriac.uk/ms/100"   passive="https://bl.syriac.uk/ms/1183">   <desc>Add. 14,438, foll. 50–52</desc>  </relation>  <relation name="syriaca:has-unspecified-codicological-part"   ref="#syriaca:has-unspecified-codicological-part" active="https://bl.syriac.uk/ms/100"   passive="https://bl.syriac.uk/ms/102">   <desc>Add. 14,438, foll. 53–101</desc>  </relation> </listRelation>

SMBL has used the following values for the name and ref attributes for part-to-composite type <listRelation> elements:

Name attribute Ref attribute
syriaca:is-unspecified-codicological-part-of #syriaca:is-unspecified-codicological-part-of

The following example from https://bl.syriac.uk/ms/101 shows a full <head> element for a manuscript part.

<head>  <note type="contents-note">This manuscript contains:    The book of Deuteronomy, according to the Peshitta version. In total, including sub-sections,    this manuscript contains 1 item.</note>  <listRelation type="Wright-BL-Taxonomy">   <relation name="dcterms:type"    ref="http://purl.org/dc/terms/type" active="https://bl.syriac.uk/ms/101"    passive="#bible-ot">    <desc>Old Testament</desc>   </relation>  </listRelation>  <listRelation type="part-to-composite">   <desc>This unit is a part of a composite manuscript:</desc>   <relation name="syriaca:is-unspecified-codicological-part-of"    ref="#syriaca:is-unspecified-codicological-part-of" active="https://bl.syriac.uk/ms/101"    passive="https://bl.syriac.uk/ms/100">    <desc>Add. 14,438</desc>   </relation>  </listRelation> </head>

Notes for Review Editors (2024)

Please ignore any errors in the <head> element and its summary. These will be regenerated by a script at a later stage. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

Divergences from Consolidated Schema:

SMBL has used the <head> element differently than the Consolidated schema and has not provided a summary title or origin place and date information. Instead, we have used dedicated <note> and <listRelation> elements to record summary information about the manuscript and part records.

1.6.3. Intellectual Content

The element <msContents> is used to describe the intellectual content of the manuscript (title, author, editor, textual additions, filiation and bibliographical references). Every conceptual work contained in the manuscript is treated as a separate <msItem>.

1.6.3.1. Language(s) of the Manuscript as a Whole

The element <textLang> encodes a description of the languages and writing systems used in the manuscript. The element itself contains a prose description of the language or languages and scripts used. The mainLang and otherLangs attributes contain the ISO 639-1 and -3 codes for the languages as well as a script code if relevant. Either attribute can take multiple values, as a space-separated list.

We have conformed to the BCP 47 standard which recommends using the two letter language code when available from ISO 639-1 codes and then using three letter language codes from ISO 639-3 only for languages not included in ISO 639-1, then an ISO 15924 code for the script, and finally IANA language subtags for other information, such as methods of transliteration.

In the case of Christian Palestinian Aramaic, no ISO 639 code has been established. For this language, we use a code in the range (qaa-qtz) ISO 639 leaves 'reserved for local use'. While codes in this range are considered private, we follow the assignment published by Linguist List for Middle Aramaic, that is qhy, which is further specified via a private use subtag resulting in the language tag: qhy-x-cpas.

The accepted language codes are:

Arabic ar
Syro-Arabic Garshuni ar-Syrc
Coptic cop
German de
English en
French fr
Ancient Greek grc
Hebrew he
Armenian hy
Italian it
Latin la
Syriac syr
Arabo-Syriac Garshuni syr-Arab
Turkish tr
Syro-Turkish Garshuni tr-Syrc
Christian Palestinian Aramaic qhy-x-cpas
Classical Armenian xcl
Undetermined und

Divergences from Consolidated Schema:

SMBL uses a different set of language codes given its scope. SMBL has also chosen not to use the <textLang> at the <msItem> level; likewise, the mainLang attribute permits multiple, space-separated language codes to handle cases of bilingual or mutli-lingual manuscripts (e.g., bilingual, parallel Gospel manuscripts)

Notes for Review Editors (2024)

Please ignore the <textLang> and the mainLang contents. These will be updated by script. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

1.6.3.2. Manuscript Item

The element <msItem> contains the intellectual information for each individual work contained within the manuscript. If a manuscript contains multiple works, it will have multiple <msItem> elements; if a manuscript contains a single work, it will only have one <msItem>.

Folia containing short notes, addenda, or scribbles by later hands should be recorded in the <additions> element, see 1.7.4. Additions [UNDER REVISION].

1.6.3.2.1. Numbering of Manuscript Items

All manuscript items have been numbered with the n attribute in a sequential manner without regard for the location of the items in the hierarchy of items and sub-items. This sequential number is relative to the manuscript part. Thus a multi-part manuscript would restart the numbering at n=‘1’ in each part. In addition, we have used a pattern for the creation of xml:id values which reflects nesting in manuscript parts and/or the position of the item in the outline hierarchy (with ‘a’ being the top level, then ‘b’, etc.

In this example from https://bl.syriac.uk/ms/3the msItem is in the second part of the multi-part manuscript and is the second item at the ‘b’ level of the outline. It is also the 3rd msItem in the second part of the manuscript based on sequence.
<msItem xml:id="p2b2" n="3" defective="true"> <!-- ... --> </msItem>

NOTA BENE: SMBL has not used Wright's outline numbering system, but instead has re-numbered the manuscript items sequentially. While there is some loss to not continuing to use Wright's numbering, we found the re-numbering to be necessary for two reasons. First, the sequential numbering allows one to navigate the nested elements much easier than Wright's system (where the same manuscript could potentially have repeated numbers due to outline levels). Second, in our encoding we occaisionally discovered manuscript items which Wright had conflated. The need to number these items necessitated re-numbering.

Notes for Review Editors (2024)

Please ignore any errors in numbering in either n or xml:id. You do not need to renumber if you delete an <msItem> or add a new <msItem> or find errors in the numbering. These will be renumbered by a script at a later stage. Similarly, if you delete an item, there is no change needed to the xml:id or the n values of the other items, leave them numbered as. If you add a new <msItem>, you should just use the letter ‘x’ as place holders: xml:id=‘x1’ n=‘x’ (if you insert multiple items, the XML validation rules require that every xml:id have a unique value, so please increment use xml:id=‘x2’, etc.). These will be renumbered by a script at a later stage. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

1.6.3.2.2. Defective Manuscript Items

defective can be used to indicate if any text or folia originally present are now missing (as determined by Wright based on missing intellectual content or physical state of the manuscript). Defective here refers only to the physical state of the manuscript. In a case where the manuscript, contains only a portion of a literary work by design (such as an abbreviated text or an extract), the manuscript item is not considered defective. The following values are permitted:

  • ‘true’ means that the item is defective either because Wright states as much (‘leaves are wanting’ or ‘fragments of’) or because clear deduction by the SMBL editor indicates missing content.
  • ‘unknown’ means that the SMBL editor suspects the manuscript is incomplete but it is not discussed by Wright.
  • ‘false’ is the default value and it is not necessary to enter it. If the item is not defective our altogether.

In the case of nested <msItem> elements, the defective value was also marked for any higher-level items if one of their child items was defective.

1.6.3.2.3. What is a Manuscript Item?

We have followed the definition proposed by the Consolidated Guidelines where a manuscript item is defined as ‘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 we have used the <msItem> element to markup up both the work as a whole its self-contained parts through the nesting of <msItem> elements. In a few cases (primarily with florilegia or catenae) is has not been possible to encode individual manuscript items based on Wright's descriptions. In those cases, we have placed his descriptions into <note> elements.

1.6.3.2.3.1. Encoding the Outline of Nested Manuscript Items

For the most part, Wright's catalogue employs an sequential outline pattern that describes manuscript items and their sub-items in a way compatible with the TEI Guidlines. In a few cases, however, we have had to modify Wright's outlines to better model the manuscript in the tree structure of the .xml file. Specifically, in some instances we have had to create a new top-level manuscript item which contains all of the items in a manuscript. Often in such cases, Wright provided a title and description of this top-level item, but he did not include this item in his numbered outline. At other times, we have found Wright's outline to be partial or incomplete. For example, Wright might only list some but not all of the sub-items in a manuscript. In these cases, our policy has been to encode only the sub-items that Wright mentions. In these cases, our .xml document matches Wright's description but not the actual contents of the manuscript (of course, we hope the a future recataloguing will capture the contents which Wright did not describe in detail). The examples below illustrate what this might look like.

In this modified example from https://bl.syriac.uk/ms/763 Wright notes that there are 18 hymns in the collection but he only provides information about two of them, thus only two <msItem> elements are encoded as child elements:
<msItem xml:id="c153" n="329"  defective="false">  <locus from="62a" to="65">62a-65</locus>  <title xml:lang="en">Paraenetic hymns, 18 in    number</title>  <rubric xml:lang="syr">ܕܡܪܬܝܢܘܬܐ<locus from="62a" to="62a"/>  </rubric> <!-- ... -->  <msItem xml:id="d1" n="330">   <locus from="62a" to="65">62a-65</locus>   <title xml:lang="en">Fourth hymn</title>   <rubric xml:lang="syr">ܥܠ ܗ̇ܢܘܢ ܕܡܬܐܡܪܝܢ ܣܟ̈ܘܠܝܛܐ      ܐܘܟܝܬ ܪ̈ܚܡܝ ܥܡ̣ܠܐ. ܐܝܟܢܐ ܕܠܐ ܢܚܙܘܢ ܬܐܛܪ̈ܐ<locus from="62a" to="65"/>   </rubric>  </msItem>  <msItem xml:id="d2" n="331">   <locus from="62a" to="65">62a-65</locus>   <title xml:lang="en">Ninth hymn</title>   <rubric xml:lang="syr">ܡܥܢܝܬܐ ܕܡܪܬܝܢܘܬܐ ܘܕܬܘ̣ܬ      ܢܦܫܐ ܕܡܬܩܪܝܐ ܐܝܬܝܩܝ<locus from="62a" to="65"/>   </rubric>  </msItem> </msItem>
In this modified example from https://bl.syriac.uk/ms/265 Wright describes a large collection but he only provides information about the first two parts of the collection, thus only two <msItem> elements are encoded as child elements. In this case we did not create a third <msItem> which might contain ‘everything else after the definitions and introduction’ even though it is clear by context that the manuscript containts more thanjust these two sections. In this case, the top-level <msItem> is assumed to contain the other sections not specifically identified by Wright.
<msItem xml:id="a1" n="1" defective="true">  <locus from="1b"/>  <title xml:lang="en">A large collection of chapters    on the Body and its Members, the Soul, the    Resurrection, the Incarnation, the holy Eucharist,    Baptism, etc.</title>  <msItem xml:id="b1" n="2">   <locus from="1b"/>   <title xml:lang="en">A section containing      definitions of various scientific terms</title>  </msItem>  <msItem xml:id="b2" n="3" defective="true">   <locus from="1b"/>   <title xml:lang="en">The introductory      section</title>  </msItem> </msItem>

Notes for Review Editors (2024)

As described above, it is not necessary to create extra <msItem> elements for itemns not described directly by Wright. Alternately, in some cases these may have already been added to the file, in which case it is not necessary to delete these extra <msItem> elements if they exist. Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

Deprecated Practices and Legacy Data:

In an earlier stage of the project, we did attempt to create placeholder <msItem> elements for content not described by Wright so some files do contain sub-items with minimal description which were not found in Wright's description. We discontinued this practice after 2022 but have left the legacy data in place, since it may be of use to future cataloguing.

1.6.3.2.3.2. Alternate Encoding with <note> in <msItem>
While Wright usually describes the manuscript contents in a methodical manner creating an outline sequentially in order from the first folio to the last, there are places where he abandons this approach and offers a prose description of the contents that does not follow the order of the document. In the most frequent example, Wright may choose to describe a florilegium in a manner organized by alphabetically by author cited rather than by folio order. In this modified example from https://bl.syriac.uk/ms/265, Wright offers an alphabetical list: ‘The authorities cited are--Didymus of Alexandria. Fol. 24 b. Dionysius the Areopagite: epistle to Timothy, fol. 19 b; to Titus, fol. 27 b. Epiphanius: the Ancoratus. Fol. 26 a. Ephraim: foll. 21 a, 25 a, 30 a, 31 b;’. Wright's description does not offer enough information to encode individual manuscript items. In those cases, we have placed these descriptions into one or more <note> elements with the following XPath: msItem/note/p. Inside this <note>, we have encoded as much of the relevant information about authors, titles, and loci as possible. As illustrated in this modified example from https://bl.syriac.uk/ms/265:
<msItem xml:id="a1" n="1" defective="true">  <locus from="1b"/>  <title xml:lang="en">A large collection of chapters    on the Body and its Members, the Soul, the    Resurrection, the Incarnation, the holy Eucharist,    Baptism, etc.</title> <!-- ... -->  <note>   <p>The authorities cited are--</p> <!-- ... -->   <p>    <author>     <persName xml:lang="en">Didymus of Alexandria</persName>    </author>. Fol.   <locus from="24b">24 b</locus>.</p>   <p>    <author ref="http://syriaca.org/person/452">     <persName xml:lang="en">Dionysius the Areopagite</persName>    </author>: <title xml:lang="en">epistle to Timothy </title>, fol.   <locus from="19b">19 b</locus>; <title xml:lang="en">to Titus </title>, fol. <locus from="27b">27 b</locus>.</p>   <p>    <author ref="http://syriaca.org/person/477">     <persName xml:lang="en">Epiphanius</persName>    </author>: <title xml:lang="en">the        Ancoratus</title>. Fol. <locus from="26a">26        a</locus>.</p>   <p>    <author ref="http://syriaca.org/person/13">     <persName xml:lang="en">Ephraim</persName>    </author>: foll. <locus from="21a">21        a</locus>, <locus from="25a">25 a</locus>, <locus from="30a">30 a</locus>, <locus from="31b">31        b</locus>; <rubric xml:lang="syr">ܥܠ ܣܒܐ        ܝܘܠܝܢܐ</rubric>, fol. <locus from="25a">25        a</locus>; <rubric xml:lang="syr">ܡܢ ܩܠܐ ܕܚܡܫܐ        ܕܦܪܕܝܣܐ</rubric>, fol. <locus from="30a">30        a</locus>.</p> <!-- ... -->  </note> </msItem>
1.6.3.2.4. Wright's Notes on the Manuscript Item
When Wright provides a comment related to an <msItem> or another aspect of the contents, we have encoded his commentary as a <note> within each <msItem> or other element as applicable. When Wright's catalogue has a footnote, we have inserted the <note> element at the point in the prose where the footnote marker occurs and marked the <note> with type of ‘footnote’. Some examples are:
<msItem xml:id="a2" n="2" defective="true">  <locus from="1" to="100">Foll. 1-100</locus>  <title ref="http://syriaca.org/work/26"   xml:lang="en">Ezekiel, according to the Peshitta version</title>  <note>The following portions of the text are missing:    Ch. 14:14-16:17, 16:32-53, 17:3-22:2, and    24:18-25:3.</note>  <note>The lessons are rubricated in the text.</note> </msItem>
As described above, when a note contains a bibliographic citation, that citation is wrapped in a <bibl> element and linked to a Syriaca.org URI using <ref> and target:
<msItem xml:id="a1" n="1" defective="true">  <locus from="1b"/>  <title xml:lang="en">The Acts of the Second Council of    Ephesus</title>  <note type="footnote">A small part of this volume has    been edited by the <persName>Rev. S. G. F.      Perry</persName>, under the title of <bibl>    <ref target="https://www.zotero.org/groups/4861694/a_comprehensive_bibliography_on_syriac_studies/items/P4VVZ7P6/library"/>"An Ancient Syriac Document, purporting to be      the record, in its chief features, of the second      Synod of Ephesus," etc., Oxford, 1867.</bibl>  </note> </msItem>
1.6.3.2.5. Locus

We have given the starting folio of each manuscript item according to the guidelines specified above for <locus>. If Wright does not give a folio location for a <msItem>, we have added one using the closest folio that he mentions in his description, even though this may not be very accurate. For example if Wright mentions an msItem on folio 12 b and then fails to give a locus for the next msItem, we have reused the locus so that both items are listed as being on 12 b.

1.6.3.2.6. Author
The author of a manuscript item, if given by Wright, was recorded inside the <author> element and wrapped with a <persName> child element (with xml:lang attribute). As described above in the discussion of URIs, all <author> elements are required to have a Syriaca.org person URI as the value of a ref, For anonymous works, no <author> was included in the <msItem>. The form of the name given by Wright was encoded as given without standardization. Where Wright records multiple name variants for the same person (e.g. translations or transliterations) we added these as child <persName> elements (with xml:lang attributes) within the <author> element (see further below for an example of multiple names for George, bishop of the Arabs).
<msItem xml:id="b2" n="3" defective="true">  <locus from="7a" to="17b">Foll. 7a-17b</locus>  <author ref="http://syriaca.org/person/13">   <persName xml:lang="en">Ephraim</persName>  </author>  <title xml:lang="en">On the Lord's Supper</title>  <rubric xml:lang="syr">ܕܦܛܝܪ̈ܐ<locus from="7a"/>  </rubric> </msItem>

When a <msItem> contains nested <msItem> elements, the author element should be repeated if applicable to the sub-items.

Divergences from Consolidated Schema:

SMBL uses Syriaca.org URIs and thus does not use key as specified in the Consolidated Schema.

1.6.3.2.6.1. Multiple Authors
Multiple authors have been indicated using repeated <author> elements.
<msItem xml:id="p2a1" n="1">  <locus from="65"/>  <author ref="http://syriaca.org/person/376">   <persName xml:lang="en">Basil</persName>  </author>  <author ref="http://syriaca.org/person/511">   <persName xml:lang="en">Gregory      (Nazianzen)</persName>  </author>  <title xml:lang="en">Questions and answers of Basil    and Gregory (Nazianzen) </title> </msItem>
When a <msItem> contains nested <msItem> elements, the author element should be repeated if applicable to the sub-items. When a top-level <msItem> contains sub-items with different authors, all authors should be encoded in the top level <msItem> as seen in this example from https://bl.syriac.uk/ms/427. Note: When Wright gives multiple name variants, those varients were recorded only in the first/highest-level instance.
<msItem xml:id="a1" n="1" defective="true">  <locus from="1a" to="263b">foll. 1 a-263 b</locus>  <author ref="http://syriaca.org/person/122">   <persName xml:lang="en">George, bishop of the      Arabs</persName>   <persName xml:lang="en">George the      Jacobite</persName>   <persName xml:lang="syr">ܓܘܪܓܝ (ܓܝܘܪܓܝ)      ܕܥܡ̈ܡܐ</persName>   <persName xml:lang="syr">ܓܝܘܪܓܝ      ܝܥܩܘܒܝܐܐ</persName>  </author> <!-- ... -->  <author ref="http://syriaca.org/person/342">   <persName xml:lang="en">Aristotle</persName>  </author>  <title xml:lang="en">Part of the Organon of    Aristotle, with introductions, notes and    commentaries by George, bishop of the Arabs </title> <!-- ... -->  <msItem xml:id="b1" n="2" defective="true">   <locus from="1a" to="59">foll. 1a-59</locus>   <title xml:lang="en">The Ten Categories</title>   <author ref="http://syriaca.org/person/122">    <persName xml:lang="en">George, bishop of the        Arabs</persName>   </author>   <author ref="http://syriaca.org/person/342">    <persName xml:lang="en">Aristotle</persName>   </author>   <msItem xml:id="c1" n="3" defective="true">    <locus from="1a" to="2b">foll. 1a-2b</locus>    <author ref="http://syriaca.org/person/122">     <persName xml:lang="en">George, bishop of the          Arabs</persName>    </author>    <title xml:lang="en">Introduction</title> <!-- ... -->   </msItem>   <msItem xml:id="c2" n="4">    <locus from="3a" to="28">foll. 3a-28</locus>    <author ref="http://syriaca.org/person/342">     <persName xml:lang="en">Aristotle</persName>    </author>    <title xml:lang="en">Text</title> <!-- ... -->   </msItem>  </msItem> </msItem>
1.6.3.2.6.2. Pseudonymous, Uncertain, Disputed and Attributed Authorship [UNDER REVISION]

Guidelines for these cases will be added in the future.

1.6.3.2.7. Translator

When Wright's description or a manuscript mentions the translator of a manuscript item, we have encoded the name of the translator in addition to any authors of the manuscript item. Such secondary statements of responsibility for the intellectual content in an <msItem> are marked with an <editor> element and a role attribute with the value ‘translator’. An <msItem> may have both an <editor> element and an <author> element if both are given in Wright's catalogue entry.

In all other respects, <editor> elements should contain the same child elements as <author> (eg. multiple <persName> elements) and attributes (e.g. a ref attribute with a Syriaca.org URI linking them to an entry The Syriac Biographical Dictionary. If Wright provides details about their role in the creation of the work that has been be encoded in a separate <note>.

<msItem xml:id="p2a1" n="1">  <locus from="82a">Fol. 82 a</locus>  <editor role="translator"   ref="http://syriaca.org/person/82">   <persName xml:lang="en">Paul of Tellā</persName>  </editor>  <title ref="http://syriaca.org/work/158"   xml:lang="en">The Psalms, translated from the Septuagint by Paul    of Tellā</title> </msItem>

Divergences from Consolidated Schema:

SMBL does not, yet, use the three-letter code (or multiple codes separated by spaces) selected from the MARC relators list (https://www.loc.gov/marc/relators/relaterm.html by the Consolidated Schema. This may be added at a later date.

SMBL uses Syriaca.org URIs and thus does not use key as specified in the Consolidated Schema.

1.6.3.2.8. Title
Within the <msItem>, we have used the <title> element to encode the descriptive titles which Wright gives for each manuscript item. These descriptive titles are usually in English, though occaisionally in Latin or a mixture of languages. These are not standardized titles and at times can be very long sentence or paragraph type titles (as was more common in 19th-century English) as in this example:
<msItem>  <title xml:lang="en">Fragments of the second volume of    the Commentary of Daniel of Salach on the Psalms,    viz. part of the homilies on Pss. li., lviii., and    lxii </title> </msItem>
We have made every effort to encode these titles exactly as written by Wright, though in some cases we have made silent emmendations for grammar or when Wright's prose was not clear. One change we have made throughout is to capitalize the first word of each title. More notably, if Wright's title was abbreviated due to context, we have supplied additional words to make the context clear. In addition, in the cases where Wright did not supply an English title we have constructed one so that every <msItem> has a non-Syriac title (usually in English) to appear in search and browse results (see discussion below).
As can be seen in the example just given (‘Fragments of the second volume of the Commentary of Daniel of Salach on the Psalms, viz. part of the homilies on Pss. li., lviii., and lxii’), many manuscript items are themselves composed of sub-items. In these cases, we have taken advantage ofthe tree structure of the XML encoding since it is possible to infinitely nest <msItem> elements inside of parent <msItem> elements. Thus in many cases a manuscript may contain one parent <msItem> to which Wright has given a general title, such as ‘The metrical works of Ephraim, containing 160 discourses on the Church, the Mysteries of our Lord, Virginity, and against Heresies’. Whenever Wright gives such a title, we have tried to encode such a parent <msItem>, even when Wright's own numbering system did not account for it. Within this parent item, multiple levels of sub-items (each encoded with <msItem>) have been encoded. In this modified example there are three levels of nested <msItem> which are a tree model of ‘The metrical works of Ephraim’ which contains ‘Discourses on the Church’ which itself contains individual hymns numbered ‘11’, ‘12’, etc.:
<msItem xml:id="p2a1" n="1" defective="true">  <locus from="20" to="33">Foll. 20-33</locus>  <author ref="http://syriaca.org/person/13">   <persName xml:lang="en">Ephrem</persName>  </author>  <title xml:lang="en">The metrical works of Ephraim,    containing 160 discourses on the Church, the    Mysteries of our Lord, Virginity, and against    Heresies</title>  <msItem xml:id="p2b1" n="2"   defective="true">   <locus from="20a" to="29b">Foll. 20a-29b</locus>   <author ref="http://syriaca.org/person/13">    <persName xml:lang="en">Ephrem</persName>   </author>   <title xml:lang="en">Discourses on the      Church</title>   <msItem xml:id="p2c1" n="3"    defective="true">    <locus from="20a" to="20b">Foll. 20a-20b</locus>    <author ref="http://syriaca.org/person/13">     <persName xml:lang="en">Ephrem</persName>    </author>    <title xml:lang="en">Number 11</title>   </msItem>   <msItem xml:id="p2c2" n="4">    <locus from="20b" to="21">Foll. 20b-21</locus>    <author ref="http://syriaca.org/person/13">     <persName xml:lang="en">Ephrem</persName>    </author>    <title xml:lang="en">Number 12</title>   </msItem>  </msItem> </msItem>

As noted above in the guidelines for encoding URI entities, when the prose given by Wright for a <title> also contains a person name or a place name, we have NOT tagged those names with <persName> or <placeName>. See the example above from the ‘Fragments of the second volume of the Commentary of Daniel of Salach’.

Divergences from Consolidated Schema:

SMBL does not use the same type values on <title> as used in the Consolidated Schema. We may choose to do so in a future revision.

1.6.3.2.8.1. Untitled Parts

In some cases of such nested sub-items, Wright will only give a Roman or Greek numeral/character in lieu of an English title. This is particularly the case for lower-level nested <msItem> elements for which he has already given a longer descriptive title for the containing <msItem>. In such cases, we have pre-pended the word ‘Part’ to the Roman or Greek character according to the following pattern ‘Part c’. According to rules of XML, the enclosing <msItem> element's title is assumed to be inherited by the nested <msItem>. Thus the part designation is unambiguously associated with the work of which it is a part, and the <title> element of the child <msItem> needs only indicate the part.

In rare cases, Wright describes excerpts of a single work which are broken up among non-contiguous manuscript items. That is, the work may begin, be interrupted by another <msItem>, and then resume. In such cases, whe have pre-pended "Continuation of " to the title of any subsequent non-contiguous instances of a work.

1.6.3.2.9. Paratextual Materials: Rubrics, Incipits, Explicits, Quotes, Final Rubrics, and Colophons.

We have used a number of differen elements to encode the paratextual phrases which Wright transcribes in his catalogue. These include <rubric>, <incipit>, <explicit>, <finalRubric>, and <quote>. In a related way, the <colophon> and <item> elements are also used to encode data related to paratextual materials. As noted above, the same principles have been used to encode the transcriptions given Wright's catalogue across all of these elements. When Wright records the location of the transcription, a <locus> element is used within each of these elements to specify the location of the component within the manuscript. Because these elements imply verbatim quotation we have not added any additional markup (e.g. quotation marks) to convey that fact. In addition all elements containing transcription of text are required to have an xml:lang to specify the language.

Divergences from Consolidated Schema:

Because of the variety of languages found in the paratextual materials of Syriac manuscripts, SMBL requires an xml:lang where the Consolidated Schema does not. In addition, we report whatever punctuation is reported in Wright's catalogue and do not remove final punctuation for the transcriptions.

1.6.3.2.9.1. Rubic

We have used the TEI element <rubric> to encode the original language titles given in the manuscripts and reported by Wright. While Wright may sometimes denote this Syriac title with the phrase ‘entitled...’ or ‘Title:...’, most commonly he simply records it without any designation immediately after he provides an English language title. Sometimes Wright only provides a Syriac language title and no English translation. In both cases, we have encoded the Syriac titles reported by Wright within <rubric> with an xml:lang to specify the language.

In some cases, a manuscript item will have multiple Syriac titles. For instance, a liturgical manuscript may include both a traditional title of the work and a title which indicates the liturgical occasion on which the work should be read. In such cases, we have encoded both the literary title and the liturgical calendar title with multiple <rubric> elements.

Because every <msItem> element already has a <title> element where a Syriaca.org work URI could be linked, we have not linked Syriaca.org URIs to Syriac titles.

When Wright indicates that a title is a running title, we have encoded this by wrapping the title in both a <fw> (forme work) element with type of ‘header’and a containing <rubric> element.

<msItem xml:id="d1" n="8"  defective="unknown">  <locus from="91" to="161">Foll. 91-161</locus>  <title ref="http://syriaca.org/work/154"   xml:lang="en">The second book of Samuel, according to the    recension of Jacob of Edessa</title>  <rubric xml:lang="syr">ܟܬܒܐ ܕܬܪ̈ܝܢ ܕܡ̈ܠܟܘܬܐ<locus from="91b" to="91b"/>  </rubric>  <rubric xml:lang="syr">   <fw type="header">ܫܡܘܐܝܠ</fw>  </rubric> </msItem>
1.6.3.2.9.2. Incipit
If Wright records the the opening lines of the text proper of the <msItem> we record this transcription in an <incipit> element. Wright sometimes denotes the incipit with the phrase ‘it begins...’ or ‘beginning...’. The incipit should not be confused with the rubic. The TEI defines the incipit as ‘the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely.’ In most cases, if Wright provides an incipit he also provides a rubric (though the reverse is not the case). See this example:
<msItem xml:id="p1b9" n="28">  <author ref="http://syriaca.org/person/42">   <persName xml:lang="en">Jacob of Batnae</persName>  </author>  <locus from="194b">Foll. 194 b</locus>  <title xml:lang="en">On the Deluge.</title>  <rubric xml:lang="syr">ܡܐܡܪܐ ܕܥܠ ܛܘܦܢܐ</rubric>  <incipit xml:lang="syr">ܟܐܢܐ ܕܩܦܚ ܒܓܙܪ ܕܝܢ̣ܗ ܠܕܪܐ    ܕܒܝܬ ܢܘܚ. ܦܬ̣ܚ ܠܗ̇ ܠܡܠܬܝ ܬܪ̈ܥܐ ܪ̈ܘܝܚܐ ܕܬܦܩ    ܫܪ̈ܒܝܟ.</incipit> </msItem>
1.6.3.2.9.3. Explicit
In the exceedingly rare cases in which Wright records the the closing lines of the text proper of the <msItem>, we marked this transcription in an <expicit> element. The explicit should not be confused with the final rubic (subscription) or colophon. The TEI defines the explicit as ‘the closing words of the text proper, exclusive of any rubric or colophon which might follow it.’ (In other scholarly usage, what the TEI defines as ‘explicit’ is also called a ‘desinit’). Here is an example of how we have encoded an <expicit>:
<msItem xml:id="p2_1b1" n="2"  defective="true">  <locus from="16a"/>  <author ref="http://syriaca.org/person/13">   <persName xml:lang="en">Ephraim</persName>  </author>  <title xml:lang="en">On the Dead</title>  <rubric xml:lang="syr">ܕܥܢ̈ܝܕܐ</rubric>  <explicit xml:lang="syr">ܐܦܢܢܝ ܕܐ̇ܦܢܐ ܠܝܕܥܬܟ̇ ܘܐܛܦܣ    ܒܟ ܘܐܬܚܣܐ ܒܟ<locus from="17b"/>  </explicit>  <note>Imperfect at the beginning.</note> </msItem>
1.6.3.2.9.4. Final Rubric or Subscription
Wright frequently records a ‘subscription’ or Syriac phrase in the manuscript which denotes the end or division of one manuscript item from the next. We have encoded these subscriptions with the TEI element <finalRubric>. The TEI guidelines distinguish between a <finalRubric> which contains a statement relating to the end of a particular work, and the <colophon>, which indentifies a statement about the end of an entire manuscript or about the scribe and/or date and/or place of writing.
<msItem xml:id="b7" n="32">  <locus from="207b">Foll. 207 b</locus>  <title xml:lang="en">Madrāshē for all ranks.</title>  <rubric xml:lang="syr">ܡܕܪ̈ܫܐ ܥܠ ܟܗ̈ܢܐ ܘܪ̈ܫܝ ܟܗ̈ܢܐ    ܘܟܠܢܫ</rubric>  <finalRubric xml:lang="syr">ܫܠܡܸܘ ܡܕܪ̈ܫܐ ܕܥܠ ܟܠ    ܬܓܡ̈ܝܢ ܕܗ̇ܘܝܢ ܒܡܢܝܢܐ ܫܒܥܝܢ ܘܬܠܬܐ </finalRubric>  <note>They are 73 in number, according to the    subscription.</note> </msItem>

In the case of <msItem> elements nested inside other <msItem> elements, it may be that Wright has quoted a <finalRubric> (e.g. a subscription) immediately after the last lower level <msItem> (for example after the last of 12 homilies in a collection). Since this subscription applies to the higher level <msItem> (for example it is a subscription noting the end of the whole collection of homilies), in these cases we have included this <finalRubric> inside the appropriate higher-level <msItem> rather than as part of the last sub-item.

Notes for Review Editors (2024)

In the case of <msItem> elements nested inside other <msItem> elements, it may be that a <finalRubric> (e.g. a subscription) has been nested inside a lower level <msItem> (say inside xml:id=‘b12’, the last of 12 homilies in a collection) when in fact the subscription applies to the higher level <msItem> (for example it is a subscription noting the end of the whole collection of homilies). In these cases delete the <finalRubric> from the lower level <msItem> (b12) and move it up in the document and higher in the outline so that you paste it into the appropriate higher level <msItem> (a1, etc.). Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

1.6.3.2.9.5. Quote

The <quote> element is used for any other quotation from the original manuscript that does not fit the description of any of the above categories of <rubric>, <incipit>, <explicit> or <finalRubric>. See the full discussion of this element's usage under Quotations from the Manuscript.

1.6.3.2.9.6. Colophon

The TEI guidelines define a colophon as ‘the original statement providing information regarding the date, place, agency, or reason for production of the manuscript’. Unfortunately, Wright did not always report the presence of colophons in a standardized way. He only sometimes uses the word ‘colophon’ in the same sense as the definition of the TEI. Sometimes he uses the word to describe a doxology written by the scribe. Accordingly it has been difficult to distinguish his transcription of colophons from other marginalia and additions to the manuscripts. In our encoding, we have choosen to encode all colophons together the additions of the manuscript (see the guidelines for <additions> below. We have, however, also made an effort to mark manuscripts in which either Wright reports the existence of a colophon in the sense meant by the TEI or in which we determine (based on Wright's description) that a colophon is present. In these cases, we have included a <colophon> element in the <msItem> either as an empty element or with a prose note referring the reader to consult the additions section of the manuscript description. The inclusion of this element allows users to search for manuscripts with colophons. This is an example of that encoding:

<msItem xml:id="a3" n="22">  <locus from="137a"/>  <title xml:lang="en">Supplicatory hymns for the    Resurrection</title>  <rubric xml:lang="syr">ܬܟܫ̈ܦܬܐ ܕܩܝܡ̣ܬܐ</rubric>  <colophon>See additions.</colophon> </msItem> <!-- --> <physDesc>  <additions>   <list>    <item xml:id="addition4" n="4">     <label>Colophon</label>     <locus from="138a"/>     <p>The colophon, fol. 138 a, states that the first          part of this book (foll. 1—110) was written in the          year 1386 (A.D. 1075) by one Benjamin, and the          remainder by one of his disciples, whose name          appears from a subsequent note to have been          Theodore</p>     <p>      <quote xml:lang="syr">ܫܘ: ܠܐܒܐ: ܘܠܒܪܐ: ܘܠܪܘܚܐ:            ܏ܩܕ ܠܥܠܡ: ܥܠܡܝܢ: ܫܩܠ ܣܟܐ ܟܬܒܘܢܐ ܗܢܐ ܒܥܘܕܪܢ            ܬܠܝܬܝܘܬܐ ܕܡ̈ܥܢܝܬܐ ܕܩܝܫܐ (sic) ܡ̇ܪܝ ܣܘܐܝܪܐ ܘܕܐܢ̈ܫܝܢ            ܐܚܪ̈ܢܐ. ܫܢܬ ܐܠܦ ܘܬܠܬܡܐ ܘܬܡ̈ܢܥܝܢ (sic) ܘܫܝܬ.            ܒܕ̈ܝܘܢܝܐ ܡܒܪ̈ܟܐ. ܟܬܒܗ ܪܒܐ ܕܝܠܢ ܒܢܝܡܢ ܡܚܣܐ ܡܪܝܐ            ܠܢܦܗ (sic) ܘܚܬܡܗ ܬܠܡܝܕܐ ܕܝܠܗ ܐܢܫ ܚܛܝܐ ܘܡܦܠܦܠ            ܒܣܝܢܐ. ܟܠ ܕܩܪܐ ܢܨܠܐ ܥܠܝܗܘܢ ܏ܘܫ.</quote>     </p>    </item>   </list>  </additions> </physDesc>

The colophon reported by Wright is encoded using <quote> and following the guidelines for additions.

Divergences from Consolidated Schema:

Our method of encoding colophons diverges from the Consolidated Schema but was chosen because it allows a greater amount of descriptive markup

1.6.3.2.10. Filiation
In one test case we have used the <filiation> element to encode information that Wright provides about the relationship of one manuscript to other surviving manuscripts in terms of their content. For example:
<msItem xml:id="a1" n="1" defective="true">  <locus from="1" to="148">Foll. 1-148</locus>  <author ref="http://syriaca.org/person/51">   <persName xml:lang="en">Severus of      Antioch</persName>  </author>  <title xml:lang="en">The sixth book of the select    epistles of Severus of Antioch</title>  <filiation>The sixth book of the select epistles of    Severus of Antioch, in the same translation as <bibl type="MS">Add. 12,181<ptr target="https://bl.syriac.uk/ms/80"/>   </bibl>.</filiation> </msItem>
In the future, we may chose to convert other references to this usage of <filiation>.

Notes for Review Editors (2024)

Please ignore instances of this element, and for now instead encode any information about the relationships between manuscripts in terms of their contents using a <note> element.

1.7. Physical Description

We have used the physical description section <physDesc> to encode several 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 script used, any decorative features, any annotations or marginalia, and transcription of colophons.

Wright typically presents his physical description of the manuscript in a concise paragraph at the start of each entry. For ease of use, we have encoded this paragraph as a <p> (TEI paragraph) at the start of each <physDesc> in this way:

<physDesc>  <p>Paper, about 6 5/8 in. by 5 1/8, consisting of 138 leaves, many of    which are much stained and torn, especially foll. 1, 5, 18, 24, 33,    and 34. The quires, signed with letters, are 17 in number; but the    first six are very imperfect, leaves being wanting at the beginning,    as well as after foll. 4, 5, 12, 17, 23, 25, and 31. There are from    16 to 25 lines in each page.</p>  <objectDesc form="codex"> <!-- ... -->  </objectDesc> <!-- ... --> </physDesc>

In addition we have used several of the child elements of <physDesc> to encode the same data in more detail.

1.7.1. Object Description

The <objectDesc> element is used to group together those parts of the physical description which relate specifically to the text-bearing object. We have encoded the form attribute of the <objectDesc> element to refer to the form of the object in its original state, before any mutilation, rebinding etc. Since all of the British Library MSS are currently codices, the majority of our MSS are marked as codex, unless we were aware of a point in time in which the item circulated as membra disjecta. We have used the following values :
  • ‘codex’: used for multiple gatherings of leaves, held within a binding of some kind
  • ‘leaf’: used for single leaves which may now be bound in a codex, but must, by definition, be membra disjecta from an earlier codex or a single leaf created for insertion or repair
  • ‘other’: used for all cases which do not fit either codex or leaf for which Wright does not provide sufficient information to describe in greater detail
<physDesc>  <objectDesc form="codex"> <!-- -->  </objectDesc> </physDesc>
The <objectDesc> contains the <supportDesc> and the <layoutDesc> elements.

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

We have reported the support material for the codicological unit(s) in the material attribute of <supportDesc>. Allowed values are: ‘chart’ (for all kinds of paper), ‘perg’ (for parchment and vellum), ‘mixed’, ‘unknown’, or ‘other’. For example:

<objectDesc form="codex">  <supportDesc material="perg">   <extent>    <measure type="composition" unit="leaf"     quantity="115">115 ff.</measure>   </extent>  </supportDesc> </objectDesc>
1.7.1.1.1. Extent

The <extent> element specifies the number of leaves in the manuscript using a nested <measure> element.

<objectDesc form="codex">  <supportDesc material="perg">   <extent>    <measure type="composition" unit="leaf"     quantity="115">115 ff.</measure>   </extent>  </supportDesc> </objectDesc>

Deprecated Practices and Legacy Data:

As a legacy of an earlier encoding model, in some files we used the embedded <dimensions> element to specify leaf dimensions, including unit of measurement. After 2022, we ceased to encode in this way. While we have left these dimensions in the data, documents revised since 2022 no longer add data in this way.

1.7.1.1.2. Foliation

We have used the <foliation> element only rarely to provide information about the ordering of folios in the manuscript. We have not included numerica data, only prose comments by Wright. For example:

<foliation>  <p>Evidently one of the fly leaves of a manuscript.</p> </foliation>
1.7.1.1.3. Condition

Deprecated Practices and Legacy Data:

As a legacy of an earlier encoding model, in some files we used the <condition> element is used to provide a brief description of the overall condition of the manuscript. After 2022, we ceased to encode in this way. While we have left these <condition> in the data, documents revised since 2022 no longer add data in this way.

1.7.1.2. Layout Description

We have used the layout description element, <layoutDesc> to record the number of columns and number of written lines if reported by Wright.

We give the number of columns and 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.

<layoutDesc>  <layout columns="1" writtenLines="19 21">   <locus from="1" to="10"/>   <p>The number of lines in each page varies from 19 to      21.</p>  </layout> </layoutDesc>

1.7.2. Hand Description

Each distinct hand and/or script in the codicological unit has been described in a separate <handNote> element in the <handDesc> element. The <handDesc> element itself has an attribute hands which has been used to record the number of hands identified, including both those involved in the original production of the unit and those contributing later additions.

Each <handNote> element must have an xml:id attribute.

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 provides a classification of the script. Oftentimes, only the broadest classification is possible. SMBL has used a combination of an ISO 639 Language Code with an optional ISO 15924 script code to encode a hand's script information. The script can take multiple, space-separated script values

The accepted script values are:

ar Unspecified Arabic script
ar-Syrc Syro-Arabic garshunography in unspecified Syriac script
ar-Syrn Syro-Arabic garshunography in East Syriac script
cop Unspecified Coptic script
de Unspecified German script
en Unspecified English script
fr Unspecified French script
grc Unspecified Greek script
he Unspecified Hebrew script
hy Unspecified Armenian script
it Unspecified Italian script
la Unspecified Latin script
qhy-x-cpas Christian Palestinian Aramaic script
syr Unspecified Syriac script
syr-Arab Arabo-Syriac garshunography in unspecified Arabic script
syr-Syre Estrangela script
syr-Syrj West Syriac script
syr-Syrn East Syriac script
syr-x-syrm Melkite Syriac script
tr Unspecified Turkish script
tr-Syrc Syro-Turkish garshunography in unspecified Syriac script
xcl Unspecified Classical Armenian script
und Undetermined
mul Multiple scripts

Each <handNote> should contain a medium attribute describing the tint or type of ink used by the hand, if known. Typically this will be "unknown" unless Wright provides information about the ink, as in this modifed example from https://bl.syriac.uk/ms/25

<handNote xml:id="handNote1" scope="major"  script="syr-Syre" medium="black-green-and-yellow-paint"> This volume is written throughout in a beautiful Edessene character, and dated <date datingMethod="Seleucid"   when-custom="0723">A. Gr. 723</date>, <date calendar="Gregorian" when="0412">A.D. 412</date>. The colophon is written with green paint, and the doxology with yellow. </handNote>

A <handNote> may contain references to folios, optionally tagged with a <locus> element; composition dates, or paleographic estimates, tagged with <date> elements; or the name of the scribe(s), tagged with <persName> elements.

Divergences from Consolidated Schema:

SMBL has included in the calculation of the hands attribute, in <handDesc>, both the hands involved in the original production of the manuscript, and those responsible for later additions.

SMBL has not made use of the sameAs attribute for cross-referencing the occurence of a given hand across two codicological units.

SMBL employs a different set of values for the script attribute to better fit the scope of the British Library collection. Likewise, we have not used the execution attribute, as there is no standard classification for Syriac manuscripts. Nor have we used the <term> element for further classifying script or punctation characteristics. Wright's description, when present, of the execution and punctuation have been recorded but left untagged.

1.7.3. Decoration Description

SMBL has used <decoNote> elements within the <decoDesc> to record information about decorative features in a manuscript. Each <decoNote> element may have a <locus> element, which records the folio location(s) on which the decorative elements appear using from, and optionally to, attributes. A prose text node records Wright's description of the decorative feature, with the exception of rubrication where a text node was omitted if Wright does not provide additional details.

Each <decoNote> element has a type attribute. SMBL uses a subset of the Fihrist vocabulary, with one addition ornamentation which refers to any sort of undifferentiated ornamentation. The allowed values are as follows:

  • border
  • diagram
  • illustration
  • initial
  • marginal
  • mixed
  • ornamentation
  • rubrication
  • vignette

Multiple instances of decoration have been recorded in separate <decoNote> elements, as in the following example from https://bl.syriac.uk/ms/122:

<decoDesc>  <decoNote type="initial"> Ornamented capitals in the <ref target="#a1">Ammonian sections and Eusebian canons</ref>.  </decoNote>  <decoNote type="ornamentation"> Ornamentation at the top of <locus from="14b" to="14b">fol. 14b</locus>.  </decoNote>  <decoNote type="illustration"> The figure of a fish on the lower margin of <locus from="14b" to="14b">fol. 14b</locus>.  </decoNote> </decoDesc>

Optionally, SMBL has employed a subtype attribute to incorporate the decoration vocabulary of the Hill Museum and Manuscripts Library.

The following terms derive from the vHMML Features List, employed by the Hill Museum and Manuscript Library:

SMBL Subtype Value vHMML Feature Term vHMML Scope notes
hmml:border Border(s), Decorative A continuous decorative design which creates a frame around part or all of a page
hmml:canon-table Canon table(s) A Gospel concordance system devised in the fourth century by Eusebius of Caesarea, in which Gospel passages are numbered in the text (generally in the margins) and correspond to tables, arranged in columnar form, indicating the concordance of passages among the Gospels
hmm:chart Chart(s) Use for display of information arranged in graphic form other than a table
hmml:coat-of-arms Coat(s) of arms
hmml:anthropomorphic Decoration, Anthropomorphic Decoration which incorporates all or part of the human body
hmml:architectural Decoration, Architectural
hmml:calligraphic Decoration, Calligraphic Do not apply if it is 'plain' writing within a decorative element.
hmml:full-page Decoration, Full-page
hmml:geometric Decoration, Geometric
hmml:vegetative Decoration, Vegetative Decoration which incorporates plant forms
hmml:zoomorphic Decoration, Zoomorphic Decoration which incorporates animal forms
hmml:diagram Diagram(s) Representation of information graphically, excluding tables
hmml:drawing Drawing(s) Use for pen & ink drawings; some may have color. May or may not be Illustration(s) to the text.
hmml:drollery Drolleries Amusing figures, often of a grotesque character
hmml:engraving Engraving(s) A print taken from an engraved plate
hmml:genealogical-table Genealogical table(s)
hmml:headpiece Headpiece(s) Decoration at the head of a book title/chapter/division. USE: particularly for Armenian, Islamic, Persian, and Western manuscripts
hmml:illumination Illumination Use of colors, especially gold or silver, for decoration
hmml:illustration Illustration(s) Use for printed works. For manuscripts, may be used in conjunction with Drawing(s) if appropriate
hmml:decorated-initial Initial(s), Decorated An initial composed of non-figural, non-zoomorphic decorative elements
hmml:historiated-initial Initial(s), Historiated A letter containing an identifiable scene or figures, sometimes relating to the text
hmml:zoomorphic-initial Initial(s), Zoomorphic An initial partly or wholly composed of animal forms
hmml:map Map(s)
hmml:marginalia Marginalia Notes on the text written in the margins
hmml:miniature Miniature(s) A color illustration, not part of the decorative element. The term is from the Latin word 'miniare' (to color with red), and does not refer their size, which can be full-page. For pen & ink drawings in manuscripts, see Drawing(s) and Illustration(s)
hmml:music Music
hmml:photograph Photograph(s)
hmml:plan Plan(s)
hmml:portrait Portrait(s)
hmml:printer-device Printer's device(s)
hmml:seal Seal(s)
hmml:table Table(s) Use for display of information, typically in rectangular form, arranged in rows and/or columns. Do not use for Canon tables or for tables of contents
hmml:volvelle Volvelle(s) Wheel chart constructed with rotating parts of one or more layers attacted to a page/leaf. For examples, see: https://medievalbooks.nl/tag/volvelle for manuscripts, http://collation.folger.edu/2012/12/volvelles for early printed ones, and http://volvellery.tumblr.com/ for 20th century examples.
hmml:woodcut Woodcut(s) A print taken from an inked wood block with a raised design

The use of terms from the vHMML Features List allow greater specification, as in this example from https://bl.syriac.uk/ms/122:

<decoNote type="illustration"  subtype="hmml:zoomorphic"> On fol. <locus from="1b">1 b</locus> there is a rude drawing of an antelope. </decoNote>

Divergences from Consolidated Schema:

SMBL has not ordered <decoNote> elements according to any particular hierarchy. SMBL has likewise not employed the primary, hierarchical list of values for the type attribute. Instead, we have employed a subset of the Fihrist typology, with the addition of the generic ornamentation value. The following terms from the Fihrist typology have been excluded due to being outside the scope of the SMBL project:

  • frieze
  • map
  • miniature
  • paratext
  • secondary
  • tooling
  • unspecified

Given the scope of descriptions provided by Wright, SMBL does not employ <persName> elements for artist names; nor have we included additional structure in the <decoNote> elements, instead providing the prose description from Wright. Finally, SMBL has not employed the <term> element for classifying subjects of the decorations.

1.7.4. Additions [UNDER REVISION]

We have used the <additions> element to describe any additions to the manuscript such as marginalia, notes by readers or owners, colophons, and other additions of interest.

Notes for Review Editors (2024)

You may come across examples of additions/list/item with empty content which were generated by a script in an earlier stage of encoding. If the manuscript does not have anything to report in additions, then you can delete the whole additions element (triple-clicking on the element name in oXygen will select the full element). Note: This section is provided for the convenience of the editors undertaking a revision of the data in 2024 and will be deleted from the final documentation.

1.8. History [UNDER REVISION]

The <history> element is used to include information about the origin, provenance and acquisition of the manuscript, if such is reported by Wright.

1.8.1. Origin

Within the <origin> element we have specified the date (<origDate>) and place (<origPlace>) (if known) of the manuscript's production. As has been our policy throughout SMBL, we have encoded the information as reported by Wright. We have not corrected his estimated dates for manuscripts based on subsequent scholarship.

Divergences from Consolidated Schema:

When a Wright does not mention a date, we have not indicated date unknown. The absence of an <origDate> element itself indicates that there is no date reported. This is a divergence from the Consolidated Schema which includes such a statement of date unknown in a <p>.

1.8.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:

<history>  <origin>   <origDate calendar="Gregorian"    when="0611">AD 611</origDate>  </origin> </history>

When a precise date was not given by Wright, we have use the tables for conversion of approximate dates published by Syriaca.org to create numberic ranges. For example, if Wright describes a manuscript as being ‘early 9th century’ we have used a 50-year (half-century) range from 0800 to 0850.

<history>  <origin>   <origDate calendar="Gregorian"    notBefore="0800" notAfter="0850">early 9th century</origDate>  </origin> </history>

In all cases we have silently change Wright's Roman numerals for centuries to a more readable Arabic numeral equivalent.

Information about use of alternate calendars and regnal years will be added soon.

1.8.1.2. origPlace [Under Revision]

1.9. Provenance [UNDER REVISION]

We have used the <provenance> to record notes by Wright about the provenance of the manuscript.

1.10. Acquisition [UNDER REVISION]

Guidelines will be added here in the future.

1.11. 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.11.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.

<additional>  <adminInfo>   <recordHist>    <source>Manuscript description based on <bibl>      <ref target="#Wrightpart3">Wright's            Catalogue</ref>     </bibl>. abbreviated by the Syriaca.org        editors.</source>   </recordHist>  </adminInfo>  <listBibl>   <bibl xml:id="Wrightpart3">    <author>William Wright</author>    <title xml:lang="en">Catalogue of Syriac Manuscripts in        the British Museum Acquired since the Year        1838</title>    <pubPlace>London</pubPlace>    <date>1870</date>    <ptr target="http://syriaca.org/bibl/8"/>    <citedRange unit="entry">LXXV. III.</citedRange>    <citedRange unit="p">1:51</citedRange>    <ref type="internet-archive-pdf"     target="https://archive.org/details/catalogueofsyria01brituoft/page/51"/>   </bibl>  </listBibl> </additional>

1.11.2. Bibliography

The bibliography of works from which the manuscript description was derived (i.e. Wright's catalogue) are recorded in the <additional> element in a <listBibl> element..

This section is also used to provide links to online resources such as Archive.org.

<listBibl>  <bibl xml:id="Wrightpart">   <author>William Wright</author>   <title xml:lang="en">Catalogue of Syriac Manuscripts in the      British Museum Acquired since the Year 1838</title>   <pubPlace>London</pubPlace>   <date>1870</date>   <ptr target="http://syriaca.org/bibl/8"/>   <citedRange unit="entry">LXIII</citedRange>   <citedRange unit="p">1:40-41</citedRange>   <ref type="internet-archive-pdf"    target="https://archive.org/details/catalogueofsyria01brituoft/page/40"/>  </bibl> </listBibl>

1.12. Palimpsests and Other Composite or Multi-Part Manuscripts [UNDER REVISION]

2. Schema

2.1. Elements

2.1.1. <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
version specifies 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 test="matches(@xml:id, '^manuscript_\d+$') or contains(base-uri(.), 'genizah-mss')"  role="fatal"> 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 test="matches(@xml:id, '^volume_\d+$') or not(contains(base-uri(.), 'genizah-mss'))"  role="fatal"> 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> <sch:rule context="//tei:TEI/@xml:id"> <sch:let name="fileNo"  value="replace(document-uri(/), '.*?(\d{1,5}).xml', '$1')"/> <sch:let name="TEIIDno"  value="replace(., '.+?(\d+)', '$1')"/> <sch:assert test="$TEIIDno = $fileNo"> The @xml:id attribute must match the number portion of the file name: "manuscript_<sch:value-of select="$fileNo"/>". </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"/>
Schematron
<sch:ns prefix="sch"  uri="http://purl.oclc.org/dsdl/schematron"/> <sch:ns prefix="sch1x"  uri="http://www.ascc.net/xml/schematron"/>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="teiHeader"/>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1" maxOccurs="1">
    <classRef key="model.resource"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="TEI" minOccurs="0"
     maxOccurs="unbounded"/>
   </sequence>
   <elementRef key="TEI" minOccurs="1"
    maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    ⚓
Schema Declaration 
element TEI
{
   att.global.attributes,
   att.typed.attributes,
   attribute version { text }?,
   ( teiHeader, ( ( model.resource+, TEI* ) | TEI+ ) )
}⚓

2.1.2. <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Module core — Schema
Attributes
type (type) allows the encoder to classify the abbreviation according to some convenient typology.
Derived from att.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
model.pPart.editorial
Contained by
core: add addrLine biblScope choice corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: foreign sic
character data
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="high" xml:lang="fr">OTAN</abbr> </choice>
Example
<choice>  <abbr>SPQR</abbr>  <expan>senatus populusque romanorum</expan> </choice>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element abbr
{
   att.global.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   ( foreign* & sic* & text )
}⚓

2.1.3. <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
Contained by
msdescription: physDesc
May contain
core: p
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>
 <elementRef key="p" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element accMat { p+ }⚓

2.1.4. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Contained by
msdescription: history
May contain
core: p
Example
<acquisition>Left to the <name type="place">Bodleian</name> by <name type="person">Richard Rawlinson</name> in 1755. </acquisition>
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>
Content model 
<content>
 <elementRef key="p" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element acquisition { attribute calendar { list { + } }?, p+ }⚓

2.1.5. <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
Member of
model.linePart model.pPart.transcriptional
Contained by
core: add addrLine biblScope corr del editor email l lg num orig p publisher q quote reg street term unclear
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: am subst supplied zone
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.6. <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
Member of
model.persNamePart
Contained by
core: add addrLine address biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.7. <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
Contained by
msdescription: msDesc msFrag msPart
May contain
core: listBibl
msdescription: adminInfo
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 minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="adminInfo" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="listBibl" minOccurs="1"
   maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element additional { adminInfo & listBibl }⚓

2.1.8. <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
Contained by
msdescription: physDesc
May contain
core: list note p
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="list" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="p" minOccurs="0"
   maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element additions { list? & note* & p? }⚓

2.1.9. <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
Member of
model.addrPart
Contained by
core: address
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 }⚓

2.1.10. <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
Member of
model.addressLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: addrLine gap lb name note pb postCode street
figures: figure
header: idno
namesdates: addName country district forename geogFeat geogName persName placeName region settlement surname
transcr: fw
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"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.addrPart"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    ⚓
Schema Declaration 
element address
{
   att.global.attributes,
   ( model.global*, ( model.addrPart, model.global* )+ )
}⚓

2.1.11. <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
Contained by
msdescription: additional
May contain
core: note
msdescription: 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 minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="note" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="recordHist"
   minOccurs="1" maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element adminInfo { note? & recordHist }⚓

2.1.12. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Contained by
msdescription: msFrag msIdentifier
May contain
header: idno
msdescription: collection
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>
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>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="collection"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="idno" minOccurs="1"
   maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element altIdentifier
{
   att.typed.attributes,
   attribute calendar { list { + } }?,
   ( collection? & idno )
}⚓

2.1.13. <am>

<am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [11.3.1.2. Abbreviation and Expansion]
Module transcr — Schema
Attributes
Member of
model.pPart.editorial
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: add corr del orig reg sic unclear
gaiji: g
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 minOccurs="0"
  maxOccurs="unbounded">
  <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 )*
}⚓

2.1.14. <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
Contained by
core: biblStruct
May contain
core: author date editor ptr ref respStmt textLang title
header: availability idno
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 minOccurs="0"
  maxOccurs="unbounded">
  <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,
   (
      author
    | editor
    | respStmt
    | title
    | model.ptrLike
    | date
    | textLang
    | idno
    | availability
   )*
}⚓

2.1.15. <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
resp (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Derived from att.global.responsibility
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
role may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
Derived from att.naming
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.respLike
Contained by
core: analytic bibl monogr
msdescription: msItem msItemStruct
May contain
namesdates: persName
character data
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:*[@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>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element author
{
   att.global.responsibility.attribute.cert,
   att.canonical.attribute.ref,
   attribute resp { list { + } }?,
   attribute role { list { + } }?,
   attribute calendar { list { + } }?,
   ( persName* & text )
}⚓

2.1.16. <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
Contained by
core: monogr
header: publicationStmt
May contain
core: sic
character data
Example
<authority>John Smith</authority>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element authority { sic*, text }⚓

2.1.17. <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
status (status) supplies a code identifying the current availability of the text.
Status Optional
Datatype teidata.enumerated
Legal values are:
free
(free) the text is freely available.
unknown
(unknown) the status of the text is unknown.
restricted
(restricted) the text is not freely available.
Contained by
core: analytic monogr series
header: publicationStmt
May contain
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>
 <elementRef key="licence" minOccurs="1"
  maxOccurs="1"/>
</content>
    ⚓
Schema Declaration 
element availability
{
   attribute status { "free" | "unknown" | "restricted" }?,
   licence
}⚓

2.1.18. <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
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
MS
The reference is to a manuscript
Member of
model.biblLike
Contained by
core: add cit corr del desc item l listBibl note orig p q quote reg relatedItem unclear
figures: figDesc figure
header: change handNote scriptNote taxonomy
linking: seg
msdescription: binding condition custEvent decoNote filiation foliation msItem msItemStruct musicNotation provenance signatures source summary surrogates typeNote
namesdates: person place
textstructure: div
transcr: supplied
May contain
core: author choice citedRange date foreign ptr pubPlace ref sic title
character data
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 type="article" subtype="book_chapter"  xml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
Schematron
<sch:rule context="//tei:bibl[not(ancestor::tei:additional)]"> <sch:report test="tei:author"> Element <author> not allowed here. </sch:report> </sch:rule> <sch:rule context="//tei:bibl[not(ancestor::tei:additional)]"> <sch:report test="tei:date"> Element <date> not allowed here. </sch:report> </sch:rule> <sch:rule context="//tei:bibl[not(ancestor::tei:additional)]"> <sch:report test="tei:pubPlace"> Element <pubPlace> not allowed here. </sch:report> </sch:rule> <sch:rule context="//tei:bibl[not(ancestor::tei:additional)]"> <sch:report test="tei:title"> Element <title> not allowed here. </sch:report> </sch:rule>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="author" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="choice" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="citedRange"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="date" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ptr" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="pubPlace" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="title" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element bibl
{
   att.global.attributes,
   att.declarable.attributes,
   att.typed.attribute.subtype,
   att.sortable.attributes,
   att.docStatus.attributes,
   attribute type { "MS" }?,
   (
      author*
    & choice*
    & citedRange*
    & date*
    & foreign*
    & ptr*
    & pubPlace*
    & ref*
    & sic*
    & title*
    & text
   )
}⚓

2.1.19. <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
Member of
model.imprintPart
Contained by
core: imprint monogr series
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 unit="page" from="12" to="34"/> <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
}⚓

2.1.20. <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
Member of
model.biblLike
Contained by
core: add cit corr del l orig p q quote reg relatedItem unclear
figures: figDesc figure
header: scriptNote
linking: seg
msdescription: condition custEvent foliation msItem msItemStruct musicNotation signatures summary surrogates typeNote
namesdates: person place
textstructure: div
transcr: supplied
May contain
core: analytic citedRange monogr note ptr ref relatedItem series
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" minOccurs="0"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="monogr"/>
   <elementRef key="series" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <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 )*
   )
}⚓

2.1.21. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
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: bibl ref sic
msdescription: locus
namesdates: persName placeName
character data
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 test="@when or @notBefore or @notAfter or @contemporary='true' or @contemporary='unknown'"  role="warn"> The binding element should have dating attributes (when or notBefore/notAfter) or a contemporary attribute (with the value 'true'). </sch:assert> </sch:rule>
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>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="bibl" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element binding
{
   attribute calendar { list { + } }?,
   attribute contemporary { text }?,
   ( bibl* & locus* & persName* & placeName* & ref* & sic* & text )
}⚓

2.1.22. <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
Contained by
msdescription: physDesc
May contain
msdescription: binding condition
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 minOccurs="1" maxOccurs="1">
  <elementRef key="binding"/>
  <elementRef key="condition"/>
 </alternate>
</content>
    ⚓
Schema Declaration 
element bindingDesc { binding | condition }⚓

2.1.23. <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
Contained by
textstructure: text
May contain
core: p
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>
 <elementRef key="p" minOccurs="1"
  maxOccurs="1"/>
</content>
    ⚓
Schema Declaration 
element body { p }⚓

2.1.24. <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
Contained by
header: category
May contain
core: sic
character data
Example
<catDesc>Prose reportage</catDesc>
Example
<catDesc>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertain" degree="high"/>   <purpose type="inform" degree="medium"/>  </textDesc> </catDesc>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element catDesc { sic*, text }⚓

2.1.25. <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
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 }⚓

2.1.26. <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
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
Contained by
header: category taxonomy
May contain
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>
 <alternate minOccurs="1" maxOccurs="1">
  <elementRef key="catDesc" maxOccurs="1"/>
  <elementRef key="category"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    ⚓
Schema Declaration 
element category
{
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   att.datcat.attributes,
   attribute xml:id { text },
   ( catDesc | category+ )
}⚓

2.1.27. <cell>

<cell> (cell) contains one cell of a table. [14.1.1. TEI Tables]
Module figures — Schema
Contained by
figures: row
May contain
core: foreign ref sic
msdescription: locus
character data
Example
<row>  <cell role="label">General conduct</cell>  <cell role="data">Not satisfactory, on account of his great unpunctuality    and inattention to duties</cell> </row>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element cell { foreign* & locus* & ref* & sic* & text }⚓

2.1.28. <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
who indicates the person, or group of people, to whom the element content is ascribed.
Derived from att.ascribed
Status Required
Schematron
<sch:rule context="//tei:revisionDesc//tei:change/@who"> <sch:let name="edsDoc"  value="doc('https://raw.githubusercontent.com/srophe/britishLibrary/main/documentation/editors.xml')"/> <sch:let name="eds"  value="$edsDoc//tei:text/tei:body/tei:listPerson/tei:person/@xml:id | $edsDoc//tei:text/tei:body/tei:listPerson/tei:org/@xml:id"/> <sch:let name="refValues"  value="for $i in $eds return concat('https://bl.syriac.uk/documentation/editors.xml#', $i)"/> <sch:assert test="every $i in . satisfies $i = $refValues"> Acceptable values for this @who attribute include: <sch:value-of select="string-join($refValues, ' | ')"/>. </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
subtype (subtype) provides a sub-categorization of the element, if needed
Derived from att.typed
Status Optional
Datatype teidata.enumerated
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
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
core: bibl ref sic
tagdocs: gi
character data
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 who="#BZ" when="2008-02-02"   status="public">Finished chapter 23</change>  <change who="#BZ" when="2008-01-02"   status="draft">Finished chapter 2</change>  <change n="P2.2" when="1991-12-21"   who="#LDB">Added examples to section 3</change>  <change when="1991-11-11" who="#MSM">Deleted chapter 10</change> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange>    <change xml:id="DRAFT1">First draft in pencil</change>    <change xml:id="DRAFT2"     notBefore="1880-12-09">First revision, mostly        using green ink</change>    <change xml:id="DRAFT3"     notBefore="1881-02-13">Final corrections as        supplied to printer.</change>   </listChange>  </creation> </profileDesc>
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>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="bibl" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="gi" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element change
{
   att.datable.w3c.attributes,
   attribute who { list { + } },
   attribute type { text }?,
   attribute subtype { text }?,
   attribute calendar { list { + } }?,
   attribute target { list { + } }?,
   ( bibl* & gi* & ref* & sic* & text )
}⚓

2.1.29. <charDecl>

<charDecl> (character declarations) provides information about nonstandard characters and glyphs. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Module gaiji — Schema
Attributes
Contained by
—
May contain
core: desc
gaiji: glyph
Example
<charDecl>  <char xml:id="aENL">   <unicodeProp name="Name"    value="LATIN LETTER ENLARGED SMALL A"/>   <mapping type="standard">a</mapping>  </char> </charDecl>
Content model 
<content>
 <sequence>
  <elementRef key="desc" minOccurs="0"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="char"/>
   <elementRef key="glyph"/>
  </alternate>
 </sequence>
</content>
    ⚓
Schema Declaration 
element charDecl { att.global.attributes, ( desc?, ( char | glyph )+ ) }⚓

2.1.30. <choice>

<choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
Module core — Schema
Member of
model.linePart model.pPart.editorial
Contained by
core: add addrLine bibl biblScope corr del editor email item l note num orig p publisher q quote ref reg street term title unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent finalRubric foliation heraldry incipit institution musicNotation objectType rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName persName placeName region surname
transcr: supplied zone
May contain
core: abbr corr expan orig reg sic
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 minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1"
   preserveOrder="false">
   <elementRef key="sic" minOccurs="0"
    maxOccurs="unbounded"/>
   <elementRef key="corr" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1" maxOccurs="1"
   preserveOrder="false">
   <elementRef key="orig" minOccurs="0"
    maxOccurs="unbounded"/>
   <elementRef key="reg" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1" maxOccurs="1"
   preserveOrder="false">
   <elementRef key="abbr" minOccurs="0"
    maxOccurs="unbounded"/>
   <elementRef key="expan" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    ⚓
Schema Declaration 
element choice { ( sic* & corr* ) | ( orig* & reg* ) | ( abbr* & expan* ) }⚓

2.1.31. <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
Member of
model.quoteLike
Contained by
core: add addrLine biblScope cit corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc figure
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry msItem musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
textstructure: div
transcr: supplied
May contain
core: bibl biblStruct cit gap graphic lb listBibl note pb ptr q quote ref
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="translation" xml:lang="en">   <quote>to horrify</quote>  </cit>  <cit type="example">   <quote>elle était horrifiée par la dépense</quote>   <cit type="translation" xml: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 url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"   mimeType="audio/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 minOccurs="1"
  maxOccurs="unbounded">
  <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.biblLike
    | model.egLike
    | model.entryPart
    | model.global
    | model.graphicLike
    | model.ptrLike
    | model.attributable
    | pc
    | q
   )+
}⚓

2.1.32. <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
unit identifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
Derived from att.citing
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.
Contained by
core: bibl biblStruct
May contain
core: sic
character data
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 unit="page" from="12" to="13"/> <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>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element citedRange
{
   att.citing.attribute.from,
   att.citing.attribute.to,
   attribute unit
   {
      "volume"
    | "issue"
    | "page"
    | "line"
    | "chapter"
    | "part"
    | "column"
    | "entry"
   }?,
   sic*,
   text
}⚓

2.1.33. <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
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" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element classDecl { taxonomy+ }⚓

2.1.34. <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
Contained by
msdescription: supportDesc
May contain
core: p
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>
 <elementRef key="p" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element collation { p* }⚓

2.1.35. <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
Contained by
msdescription: altIdentifier msIdentifier
May contain
core: sic
character data
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>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element collection { sic*, text }⚓

2.1.36. <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
Member of
model.msQuoteLike
Contained by
msdescription: msItem msItemStruct
May contain
core: ref sic
msdescription: locus
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element colophon { att.global.attributes, ( locus* & ref? & sic* & text ) }⚓

2.1.37. <condition>

<condition> (condition) contains a description of the physical condition of the manuscript or object. [10.7.1.5. Condition]
Module msdescription — Schema
Contained by
msdescription: bindingDesc sealDesc supportDesc
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 { macro.specialPara }⚓

2.1.38. <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
Member of
model.pPart.transcriptional
Contained by
core: add addrLine biblScope choice corr del editor email l lg num orig p publisher q quote reg street term unclear
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: am supplied
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.39. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.placeNamePart
Contained by
core: add addrLine address biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msIdentifier musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName place region surname
transcr: supplied
May contain
core: sic
character data
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:*[@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>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element country { attribute calendar { list { + } }?, sic*, text }⚓

2.1.40. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Contained by
msdescription: custodialHist
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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,
   attribute calendar { list { + } }?,
   macro.specialPara
}⚓

2.1.41. <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
Contained by
—
May contain
core: p
msdescription: custEvent
Example
<custodialHist>  <custEvent type="conservation"   notBefore="1961-03" notAfter="1963-02">Conserved between March 1961 and February 1963 at    Birgitte Dalls Konserveringsværksted.</custEvent>  <custEvent type="photography"   notBefore="1988-05-01" notAfter="1988-05-30">Photographed in    May 1988 by AMI/FA.</custEvent>  <custEvent type="transfer-dispatch"   notBefore="1989-11-13" notAfter="1989-11-13">Dispatched to Iceland    13 November 1989.</custEvent> </custodialHist>
Content model 
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="custEvent" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    ⚓
Schema Declaration 
element custodialHist { att.global.attributes, ( model.pLike+ | custEvent+ ) }⚓

2.1.42. <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
unit names the unit used for the measurement
Derived from att.dimensions
Status Optional
Datatype teidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
Member of
model.linePart model.pPart.transcriptional
Contained by
core: add addrLine biblScope corr del editor email l lg num orig p publisher q quote reg street term unclear
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: am supplied zone
May contain
core: sic
character data
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="water" group="1">es; and</damage> having writ,</l> <l>Moves <damage agent="water" group="1">   <supplied>on: nor all your</supplied>  </damage> Piety nor Wit</l>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element damage
{
   att.damaged.attribute.agent,
   att.damaged.attribute.degree,
   att.damaged.attribute.group,
   att.dimensions.attribute.quantity,
   att.dimensions.attribute.extent,
   att.dimensions.attribute.precision,
   att.dimensions.attribute.scope,
   att.ranging.attribute.atLeast,
   att.ranging.attribute.atMost,
   att.ranging.attribute.min,
   att.ranging.attribute.max,
   att.ranging.attribute.confidence,
   att.written.attribute.hand,
   attribute unit { "cm" | "mm" | "in" | "line" | "char" }?,
   sic*,
   text
}⚓

2.1.43. <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
Member of
model.dateLike
Contained by
core: add addrLine analytic bibl biblScope corr del desc editor email foreign imprint item l note num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor handNote publicationStmt scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType provenance secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: foreign ref sic
namesdates: persName placeName
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element date
{
   att.datable.attributes,
   att.calendarSystem.attributes,
   att.editLike.attributes,
   ( foreign* & persName* & placeName* & ref* & sic* & text )
}⚓

2.1.44. <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
Contained by
msdescription: physDesc
May contain
msdescription: decoNote
Example
<decoDesc>  <p>The start of each book of the Bible with a 10-line historiated    illuminated initial; prefaces decorated with 6-line blue initials with red    penwork flourishing; chapters marked by 3-line plain red initials; verses    with 1-line initials, alternately blue or red.</p> </decoDesc>
Content model 
<content>
 <elementRef key="decoNote" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element decoDesc { decoNote+ }⚓

2.1.45. <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
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
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
ornamentation
The decoration note concerns any sort of undifferentiated ornamentation. This term is more general than those found in the vocabulary of the consolidated schema.
other
The decoration note concerns other/unspecified aspects (you may also provide a custom value)
paratext
rubrication
The decoration note concerns the rubrication or other highlighting
subtype (subtype) provides a sub-categorization of the element, if needed
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Member of
model.msItemPart
Contained by
msdescription: decoDesc msItem msItemStruct seal sealDesc
May contain
core: bibl foreign quote ref sic
msdescription: locus
namesdates: persName placeName
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="bibl" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="quote" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element decoNote
{
   attribute type
   {
      "border"
    | "diagram"
    | "illustration"
    | "initial"
    | "marginal"
    | "ornamentation"
    | "other"
    | "paratext"
    | "rubrication"
   }?,
   attribute subtype { text }?,
   (
      bibl*
    & foreign*
    & locus*
    & persName*
    & placeName*
    & quote*
    & ref*
    & sic*
    & text
   )
}⚓

2.1.46. <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
Member of
model.linePart model.pPart.transcriptional
Contained by
core: add addrLine biblScope corr del editor email l lg num orig p publisher q quote reg street term unclear
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: am subst supplied zone
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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="overstrike" type="primary">schwebt</del> weht der Wind </l>
Example
<del rend="overstrike">  <gap reason="illegible" quantity="5"   unit="character"/> </del>
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
    ⚓
Schema Declaration 
element del
{
   att.transcriptional.attributes,
   att.typed.attributes,
   att.dimensions.attributes,
   macro.paraContent
}⚓

2.1.47. <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
Member of
model.measureLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
gaiji: g
character data
Example
<depth unit="in" quantity="4"/>
Content model 
<content>
 <macroRef key="macro.xtext"/>
</content>
    ⚓
Schema Declaration 
element depth { att.global.attributes, att.dimensions.attributes, macro.xtext }⚓

2.1.48. <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
Member of
model.descLike model.labelLike
Contained by
core: add corr del graphic l lg orig p q quote reg unclear
figures: figDesc figure
gaiji: charDecl glyph
header: scriptNote
linking: seg
msdescription: condition custEvent foliation musicNotation signatures summary surrogates typeNote
namesdates: listRelation place relation
textstructure: div
transcr: supplied surface
May contain
core: bibl date foreign quote ref sic title
msdescription: locus
namesdates: persName placeName
character data
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 module="tei"  ident="teidata.point">  <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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="bibl" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="date" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="quote" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="title" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element desc
{
   bibl*
 & date*
 & foreign*
 & locus*
 & persName*
 & placeName*
 & quote*
 & ref*
 & sic*
 & title*
 & text
}⚓

2.1.49. <dim>

<dim> contains any single measurement forming part of a dimensional specification of some sort. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes
Member of
model.measureLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
gaiji: g
character data
Note

The specific elements <width>, <height>, and <depth> should be used in preference to this generic element wherever appropriate.
Example
<dim type="circumference" extent="4.67 in"/>
Content model 
<content>
 <macroRef key="macro.xtext"/>
</content>
    ⚓
Schema Declaration 
element dim
{
   att.global.attributes,
   att.typed.attributes,
   att.dimensions.attributes,
   macro.xtext
}⚓

2.1.50. <dimensions>

<dimensions> (dimensions) contains a dimensional specification. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes
unit names the unit used for the measurement
Derived from att.dimensions
Status Required
Datatype teidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
type indicates which aspect of the object is being measured.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
leaf
The dimensions concerns the leaf
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor extent scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
msdescription: 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="relief" unit="mm">345</dim> </dimensions>
This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm.
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 unit="cm" scope="most"   quantity="90"/>  <width unit="cm" scope="most" quantity="48"/> </dimensions> <dimensions unit="in">  <height quantity="12"/>  <width quantity="10"/> </dimensions>
Schematron
<sch:rule context="//tei:dimensions"> <sch:assert test="@unit" role="error"> 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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="height" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="width" minOccurs="0"
   maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element dimensions
{
   att.dimensions.attribute.quantity,
   att.dimensions.attribute.extent,
   att.dimensions.attribute.precision,
   att.dimensions.attribute.scope,
   att.ranging.attribute.atLeast,
   att.ranging.attribute.atMost,
   att.ranging.attribute.min,
   att.ranging.attribute.max,
   att.ranging.attribute.confidence,
   att.typed.attribute.subtype,
   attribute unit { "cm" | "mm" | "in" | "line" | "char" },
   attribute type { "leaf" }?,
   ( height?, width? )
}⚓

2.1.51. <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
Member of
model.imprintPart
Contained by
core: imprint
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.52. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.placeNamePart
Contained by
core: add addrLine address biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msIdentifier musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName place region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}⚓

2.1.53. <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
Member of
model.divLike
Contained by
textstructure: div
May contain
core: bibl biblStruct cit desc gap head l label lb lg list listBibl note p pb q quote
figures: figure table
msdescription: msDesc
namesdates: listRelation
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="1" type="chapter">    <head>The Nature of Authority</head>    <p>With reference to any proposed measures having for their object the greatest        happiness of the greatest number [...]</p>    <div n="1.1" type="section">     <head>Analysis of Authority</head>     <p>What on any given occasion is the legitimate weight or influence to be attached to          authority [...] </p>    </div>    <div n="1.2" type="section">     <head>Appeal to Authority, in What Cases Fallacious.</head>     <p>Reference to authority is open to the charge of fallacy when [...] </p>    </div>   </div>  </div> </body>
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 minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate>
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate>
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </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* )*
      )?
   )
}⚓

2.1.54. <edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Module header — Schema
Attributes
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Required
Datatype teidata.text
Contained by
core: monogr
header: editionStmt
May contain
core: sic
character data
Example
<edition>First edition <date>Oct 1990</date> </edition> <edition n="S2">Students' edition</edition>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element edition
{
   att.global.attribute.xmlid,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   attribute n { text },
   sic*,
   text
}⚓

2.1.55. <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
Contained by
header: fileDesc
May contain
header: edition
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>
 <elementRef key="edition" minOccurs="1"
  maxOccurs="1"/>
</content>
    ⚓
Schema Declaration 
element editionStmt { edition }⚓

2.1.56. <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
role may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
Derived from att.naming
Status Required
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
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.
Derived from att.canonical
Status Optional
Schematron
<sch:rule context="//tei:titleStmt/tei:editor/@ref"> <sch:let name="edsDoc"  value="doc('https://raw.githubusercontent.com/srophe/britishLibrary/main/documentation/editors.xml')"/> <sch:let name="eds"  value="$edsDoc//tei:text/tei:body/tei:listPerson/tei:person/@xml:id | $edsDoc//tei:text/tei:body/tei:listPerson/tei:org/@xml:id"/> <sch:let name="refValues"  value="for $i in $eds return concat('https://bl.syriac.uk/documentation/editors.xml#', $i)"/> <sch:assert test="every $i in . satisfies $i = $refValues"> Acceptable values for this @ref attribute include: <sch:value-of select="string-join($refValues, ' | ')"/>. </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.respLike
Contained by
core: analytic monogr series
header: titleStmt
msdescription: msItem
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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>
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>
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    ⚓
Schema Declaration 
element editor
{
   att.global.attributes,
   attribute role { list { + } },
   attribute ref { list { + } }?,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}⚓

2.1.57. <editorialDecl>

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
Module header — Schema
Contained by
header: encodingDesc
May contain
header: interpretation
Example
<editorialDecl>  <normalization>   <p>All words converted to Modern American spelling using      Websters 9th Collegiate dictionary   </p>  </normalization>  <quotation marks="all">   <p>All opening quotation marks converted to “ all closing      quotation marks converted to &amp;cdq;.</p>  </quotation> </editorialDecl>
Content model 
<content>
 <elementRef key="interpretation"
  minOccurs="1" maxOccurs="1"/>
</content>
    ⚓
Schema Declaration 
element editorialDecl { interpretation }⚓

2.1.58. <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
Member of
model.addressLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 }⚓

2.1.59. <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
Member of
model.teiHeaderPart
Contained by
header: teiHeader
May contain
header: classDecl editorialDecl
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="editorialDecl"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="classDecl" minOccurs="1"
   maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element encodingDesc { editorialDecl, classDecl }⚓

2.1.60. <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
Member of
model.pPart.editorial
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
gaiji: g
character data
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
}⚓

2.1.61. <expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
Module core — Schema
Attributes
Member of
model.pPart.editorial
Contained by
core: add addrLine biblScope choice corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: foreign sic
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element expan
{
   att.global.responsibility.attributes,
   ( foreign* & sic* & text )
}⚓

2.1.62. <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
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Required
Schematron
<sch:rule context="//tei:explicit/@xml:lang"> <sch:let name="langIdents"  value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/> <sch:assert test=". = $langIdents"> Attribute value must match one of the following language codes in the <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>. </sch:assert> </sch:rule>
Datatype teidata.language
Member of
model.msQuoteLike
Contained by
msdescription: msItem msItemStruct
May contain
core: foreign note ref sic
msdescription: locus
namesdates: persName placeName
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element explicit
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   attribute xml:lang { text },
   ( foreign* & locus* & note* & persName* & placeName* & ref* & sic* & text )
}⚓

2.1.63. <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
Contained by
core: monogr
msdescription: supportDesc
May contain
core: measure
msdescription: dimensions
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 unit="MiB" quantity="4.2">About four megabytes</measure>  <measure unit="pages" quantity="245">245 pages of source    material</measure> </extent>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="measure" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="dimensions"
   minOccurs="0" maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element extent { measure, dimensions? }⚓

2.1.64. <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
Member of
model.resource
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 ulx="0" uly="0" lrx="200" lry="300">   <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="front" minOccurs="0"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.graphicLike"/>
   <elementRef key="surface"/>
   <elementRef key="surfaceGrp"/>
  </alternate>
  <elementRef key="back" minOccurs="0"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element facsimile
{
   att.global.attributes,
   att.declaring.attributes,
   ( front?, ( model.graphicLike | surface | surfaceGrp )+, back? )
}⚓

2.1.65. <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
Contained by
figures: figure
May contain
core: abbr address bibl biblStruct choice cit date desc email expan foreign hi label list listBibl measure name num ptr q quote ref term title
figures: table
header: idno
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am ex subst
character data
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 }⚓

2.1.66. <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
Member of
model.global
Contained by
core: add addrLine address biblScope cit corr del editor email imprint l lg num orig p publisher q quote reg series street term unclear
figures: figure table
gaiji: glyph
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msItem musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName person region surname
textstructure: div
transcr: supplied surface surfaceGrp zone
May contain
core: bibl biblStruct cit desc gap graphic head l label lb lg list listBibl note p pb q quote
figures: figDesc figure formula table
msdescription: msDesc
namesdates: listRelation
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 url="http://www.example.org/fig1.png"   scale="0.5"/> </figure>
Content model 
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <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.headLike
    | model.common
    | figDesc
    | model.graphicLike
    | model.global
    | model.divBottom
   )*
}⚓

2.1.67. <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
Contained by
header: teiHeader
May contain
header: editionStmt publicationStmt sourceDesc titleStmt
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 minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="titleStmt" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="editionStmt"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="publicationStmt"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="sourceDesc"
   minOccurs="1" maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element fileDesc { titleStmt, editionStmt, publicationStmt, sourceDesc }⚓

2.1.68. <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
Member of
model.msItemPart
Contained by
msdescription: msItem msItemStruct
May contain
core: bibl sic
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="bibl" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element filiation { bibl* & sic* & text }⚓

2.1.69. <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
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Required
Schematron
<sch:rule context="//tei:finalRubric/@xml:lang"> <sch:let name="langIdents"  value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/> <sch:assert test=". = $langIdents"> Attribute value must match one of the following language codes in the <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>. </sch:assert> </sch:rule>
Datatype teidata.language
Member of
model.msQuoteLike
Contained by
msdescription: msItem msItemStruct
May contain
core: choice foreign gap note quote ref sic
msdescription: locus
namesdates: persName placeName
transcr: supplied
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="choice" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="gap" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="quote" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="supplied" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element finalRubric
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   att.typed.attributes,
   attribute xml:lang { text },
   (
      choice*
    & foreign*
    & gap*
    & locus*
    & note*
    & persName*
    & placeName*
    & quote*
    & ref*
    & sic*
    & supplied*
    & text
   )
}⚓

2.1.70. <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
Contained by
msdescription: supportDesc
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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, macro.specialPara }⚓

2.1.71. <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
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Required
Schematron
<sch:rule context="//tei:foreign/@xml:lang"> <sch:let name="langIdents"  value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/> <sch:assert test=". = $langIdents"> Attribute value must match one of the following language codes in the <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>. </sch:assert> </sch:rule>
Datatype teidata.language
Member of
model.emphLike
Contained by
core: abbr add addrLine bibl biblScope corr date del desc editor email expan foreign l note num orig p publisher q quote ref reg street term title unclear
figures: cell figDesc
header: distributor handNote scriptNote
linking: seg
msdescription: catchwords condition custEvent decoNote explicit finalRubric foliation heraldry incipit institution musicNotation objectType origPlace rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName persName placeName region surname
transcr: supplied
May contain
core: date foreign ref sic
msdescription: locus
namesdates: persName placeName
transcr: supplied
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="date" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="supplied" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element foreign
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   attribute xml:lang { text },
   (
      date*
    & foreign*
    & locus*
    & persName*
    & placeName*
    & ref*
    & sic*
    & supplied*
    & text
   )
}⚓

2.1.72. <forename>

<forename> (forename) contains a forename, given or baptismal name. [13.2.1. Personal Names]
Module namesdates — Schema
Attributes
Member of
model.persNamePart
Contained by
core: add addrLine address biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.73. <formula>

<formula> (formula) contains a mathematical or other formula. [14.2. Formulæ and Mathematical Expressions]
Module figures — Schema
Attributes
Member of
model.graphicLike
Contained by
core: add addrLine biblScope cit corr del editor email l num orig p publisher q quote reg street term unclear
figures: figure formula table
gaiji: glyph
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: facsimile supplied surface zone
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 minOccurs="0"
  maxOccurs="unbounded">
  <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 )*
}⚓

2.1.74. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.respLike
Contained by
core: monogr
header: titleStmt
msdescription: msItem
May contain
core: sic
character data
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>
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>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element funder { attribute calendar { list { + } }?, sic*, text }⚓

2.1.75. <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
type classifies the material encoded according to some useful typology.
Derived from att.typed
Status Required
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
model.milestoneLike
Contained by
core: add addrLine address biblScope cit corr del editor email imprint l lg num orig p publisher q quote reg series street term unclear
figures: figure table
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msItem musicNotation objectType rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName person region surname
textstructure: div
transcr: subst supplied surface surfaceGrp zone
May contain
core: sic
msdescription: locus
character data
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 type="sig" place="bottom">C3</fw>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element fw
{
   att.typed.attribute.subtype,
   att.written.attributes,
   attribute type { text },
   ( locus* & sic* & text )
}⚓

2.1.76. <g>

<g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes]
Module gaiji — Schema
Attributes
ref points to a description of the character or glyph intended.
Status Optional
Datatype teidata.pointer
Member of
model.gLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg series street term unclear
gaiji: mapping
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent depth dim foliation heraldry locus msName musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: am ex supplied zone
May contain Character data only
Note

The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph.
Example
<g ref="#ctlig">ct</g>
This example points to a <glyph> element with the identifier ctlig like the following:
<glyph xml:id="ctlig"> <!-- here we describe the particular ct-ligature intended --> </glyph>
Example
<g ref="#per-glyph">per</g>
The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per-glyph as follows:
<glyph xml:id="per-glyph"> <!-- ... --> </glyph>
Content model 
<content>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element g
{
   att.global.attributes,
   att.typed.attributes,
   attribute ref { text }?,
   text
}⚓

2.1.77. <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
unit names the unit used for the measurement
Derived from att.dimensions
Status Optional
Datatype teidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
reason (reason) gives the reason for omission
Status Required
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
model.global.edit
Contained by
core: add addrLine address biblScope cit corr del editor email imprint l lg num orig p publisher q quote reg series street term unclear
figures: figure table
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent finalRubric foliation heraldry institution msItem musicNotation objectType rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName person region surname
textstructure: div
transcr: supplied surface surfaceGrp zone
May contain Empty element
Note

The <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion.
Example
<gap quantity="4" unit="chars"  reason="illegible"/>
Example
<gap quantity="1" unit="essay"  reason="sampling"/>
Example
<del>  <gap atLeast="4" atMost="8" unit="chars"   reason="illegible"/> </del>
Example
<gap extent="several lines" reason="lost"/>
Content model 
<content>
 <empty/>
</content>
    ⚓
Schema Declaration 
element gap
{
   att.dimensions.attribute.quantity,
   att.dimensions.attribute.extent,
   att.dimensions.attribute.precision,
   att.dimensions.attribute.scope,
   att.ranging.attribute.atLeast,
   att.ranging.attribute.atMost,
   att.ranging.attribute.min,
   att.ranging.attribute.max,
   att.ranging.attribute.confidence,
   attribute unit { "cm" | "mm" | "in" | "line" | "char" }?,
   attribute reason
   {
      list
      {
         (
            "cancelled"
          | "deleted"
          | "editorial"
          | "illegible"
          | "inaudible"
          | "irrelevant"
          | "sampling"
         )+
      }
   },
   attribute agent { text }?,
   empty
}⚓

2.1.78. <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
Member of
model.measureLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
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 xml:id="WGS" datum="WGS84">World Geodetic System</geoDecl> <geoDecl xml:id="OS" datum="OSGB36">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 }⚓

2.1.79. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.offsetLike
Contained by
core: add addrLine address biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}⚓

2.1.80. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.placeNamePart
Contained by
core: add addrLine address biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msIdentifier musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName place region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}⚓

2.1.81. <gi>

<gi> (element name) contains the name (generic identifier) of an element. [22. Documentation Elements 22.5. Element Specifications]
Module tagdocs — Schema
Attributes
scheme supplies the name of the scheme in which this name is defined.
Status Optional
Datatype teidata.enumerated
Sample values include:
TEI
this element is part of the TEI scheme.[Default]
DBK
(docbook) this element is part of the Docbook scheme.
XX
(unknown) this element is part of an unknown scheme.
Schematron
this element is from Schematron.
HTML
this element is from the HTML scheme.
Member of
model.phrase.xml
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: change distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
XSD Name
Example
<p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the <gi scheme="DBK">listItem</gi> element.</p>
This example shows the use of both a namespace prefix and the scheme attribute as alternative ways of indicating that the <gi> in question is not a TEI element name: in practice only one method should be adopted.
Content model 
<content>
 <dataRef key="teidata.name"/>
</content>
    ⚓
Schema Declaration 
element gi { att.global.attributes, attribute scheme { text }?, teidata.name }⚓

2.1.82. <glyph>

<glyph> (character glyph) provides descriptive information about a character glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Module gaiji — Schema
Attributes
Contained by
gaiji: charDecl
May contain
core: desc graphic note
figures: figure formula
gaiji: mapping
Example
<glyph xml:id="rstroke">  <localProp name="Name"   value="LATIN SMALL LETTER R WITH A FUNNY STROKE"/>  <localProp name="entity" value="rstroke"/>  <figure>   <graphic url="glyph-rstroke.png"/>  </figure> </glyph>
Content model 
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="unicodeProp"/>
  <elementRef key="unihanProp"/>
  <elementRef key="localProp"/>
  <elementRef key="mapping"/>
  <elementRef key="figure"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.noteLike"/>
  <classRef key="model.descLike"/>
 </alternate>
</content>
    ⚓
Schema Declaration 
element glyph
{
   att.global.attributes,
   (
      unicodeProp
    | unihanProp
    | localProp
    | mapping
    | figure
    | model.graphicLike
    | model.noteLike
    | model.descLike
   )*
}⚓

2.1.83. <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
Member of
model.graphicLike model.titlepagePart
Contained by
core: add addrLine biblScope cit corr del editor email l num orig p publisher q quote reg street term unclear
figures: figure formula table
gaiji: glyph
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry msItem musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: facsimile supplied surface zone
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="leaf1" xml:id="spi001">   <surface xml:id="spi001r">    <graphic type="normal"     subtype="thumbnail" url="spi/thumb/001r.jpg"/>    <graphic type="normal" subtype="low-res"     url="spi/normal/lowRes/001r.jpg"/>    <graphic type="normal"     subtype="high-res" url="spi/normal/highRes/001r.jpg"/>    <graphic type="high-contrast"     subtype="low-res" url="spi/contrast/lowRes/001r.jpg"/>    <graphic type="high-contrast"     subtype="high-res" url="spi/contrast/highRes/001r.jpg"/>   </surface>   <surface xml:id="spi001v">    <graphic type="normal"     subtype="thumbnail" url="spi/thumb/001v.jpg"/>    <graphic type="normal" subtype="low-res"     url="spi/normal/lowRes/001v.jpg"/>    <graphic type="normal"     subtype="high-res" url="spi/normal/highRes/001v.jpg"/>    <graphic type="high-contrast"     subtype="low-res" url="spi/contrast/lowRes/001v.jpg"/>    <graphic type="high-contrast"     subtype="high-res" url="spi/contrast/highRes/001v.jpg"/>    <zone xml:id="spi001v_detail01">     <graphic type="normal"      subtype="thumbnail" url="spi/thumb/001v-detail01.jpg"/>     <graphic type="normal"      subtype="low-res"      url="spi/normal/lowRes/001v-detail01.jpg"/>     <graphic type="normal"      subtype="high-res"      url="spi/normal/highRes/001v-detail01.jpg"/>     <graphic type="high-contrast"      subtype="low-res"      url="spi/contrast/lowRes/001v-detail01.jpg"/>     <graphic type="high-contrast"      subtype="high-res"      url="spi/contrast/highRes/001v-detail01.jpg"/>    </zone>   </surface>  </surfaceGrp> </facsimile>
Content model 
<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element graphic
{
   att.global.attributes,
   att.media.attributes,
   att.resourced.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   model.descLike*
}⚓

2.1.84. <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
hands (hands) specifies the number of distinct hands identified within the manuscript
Status Required
Datatype teidata.count
Contained by
msdescription: physDesc
May contain
header: handNote
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>
 <elementRef key="handNote" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element handDesc { attribute hands { text }, handNote+ }⚓

2.1.85. <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
script characterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
Derived from att.handFeatures
Status Required
Schematron
<sch:rule context="//tei:handNote/@script"> <sch:let name="langIdents"  value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/> <sch:assert test="every $i in tokenize(., '\s') satisfies $i = $langIdents"> Attribute value(s) must match one of the following language codes in the <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>. </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.name separated by whitespace
Contained by
msdescription: handDesc
May contain
core: bibl date foreign note quote ref sic
msdescription: locus
namesdates: persName placeName
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="bibl" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="date" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="quote" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</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 { + } },
   (
      bibl*
    & date*
    & foreign*
    & locus*
    & note*
    & persName*
    & placeName*
    & quote*
    & ref*
    & sic*
    & text
   )
}⚓

2.1.86. <head>

<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
Member of
model.headLike
Contained by
core: lg
figures: figure table
msdescription: msDesc msFrag msPart
namesdates: place
textstructure: div
May contain
core: note sic
namesdates: listRelation
character data
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="I" type="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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="listRelation"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element head { listRelation* & note* & sic* & text }⚓

2.1.87. <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
quantity specifies the length in the units specified
Derived from att.dimensions
Status Required
Datatype teidata.numeric
Member of
model.measureLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent dimensions foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: sic
character data
Example
<height unit="in" quantity="7"/>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element height
{
   att.dimensions.attribute.unit,
   att.dimensions.attribute.extent,
   att.dimensions.attribute.precision,
   att.dimensions.attribute.scope,
   att.ranging.attribute.atLeast,
   att.ranging.attribute.atMost,
   att.ranging.attribute.min,
   att.ranging.attribute.max,
   att.ranging.attribute.confidence,
   attribute quantity { text },
   sic*,
   text
}⚓

2.1.88. <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
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 }⚓

2.1.89. <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
rend
Status Required
Legal values are:
italic
Member of
model.hiLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc formula
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution locus musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied zone
May contain
core: sic
character data
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>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element hi { attribute rend { "italic" }, sic*, text }⚓

2.1.90. <history>

<history> (history) groups elements describing the full history of a manuscript, manuscript part, or other object. [10.8. History]
Module msdescription — Schema
Contained by
msdescription: msDesc msFrag msPart
May contain
msdescription: acquisition origin provenance
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="acquisition"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="origin" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="provenance"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element history { acquisition* & origin* & provenance* }⚓

2.1.91. <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
type categorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived from att.typed
Status Required
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.
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.msItemPart model.nameLike model.personPart
Contained by
core: add addrLine address analytic biblScope corr del editor email l monogr num orig p publisher q quote reg series street term unclear
figures: figDesc
header: distributor publicationStmt scriptNote
linking: seg
msdescription: altIdentifier catchwords condition custEvent foliation heraldry institution msIdentifier msItem musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName person place region surname
transcr: supplied
May contain
core: sic
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.
Schematron
<sch:rule context="//tei:publicationStmt/tei:idno[@type='URI']/text()"> <sch:let name="fileNo"  value="replace(document-uri(/), '.*?(\d{1,5}).xml', '$1')"/> <sch:let name="docURIno"  value="replace(., '.+?(\d+).+', '$1')"/> <sch:let name="msDescIdnoNo"  value="replace(./following::tei:msDesc/tei:msIdentifier/tei:idno[@type='URI']/text(), '.+?(\d+)', '$1')"/> <sch:let name="id" value="@xml:id"/> <sch:assert test="$fileNo = $docURIno"> The number portion of the <idno> element must be the same as the URI number in the file name: <sch:value-of select="$fileNo"/> </sch:assert> <sch:assert test="$docURIno = $msDescIdnoNo"> The number portion of this <idno> element must match the number portion of the <idno> in <publicationStmt>: <sch:value-of select="$docURIno"/> </sch:assert> <sch:report test="preceding-sibling::element()[@xml:id = $id]">This @xml:id is already in use.</sch:report> </sch:rule>
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>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element idno
{
   att.typed.attribute.subtype,
   attribute type
   {
      "ISBN" | "ISSN" | "DOI" | "URI" | "VIAF" | "ESTC" | "OCLC"
   },
   attribute calendar { list { + } }?,
   sic*,
   text
}⚓

2.1.92. <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
Contained by
core: monogr
May contain
core: biblScope date gap lb note pb pubPlace publisher respStmt
figures: figure
header: distributor
transcr: fw
Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model 
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="classCode"/>
   <elementRef key="catRef"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate>
    <classRef key="model.imprintPart"/>
    <classRef key="model.dateLike"/>
   </alternate>
   <elementRef key="respStmt" minOccurs="0"
    maxOccurs="unbounded"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    ⚓
Schema Declaration 
element imprint
{
   att.global.attributes,
   (
      ( classCode | catRef )*,
      ( ( model.imprintPart | model.dateLike ), respStmt*, model.global* )+
   )
}⚓

2.1.93. <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
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Required
Schematron
<sch:rule context="//tei:incipit/@xml:lang"> <sch:let name="langIdents"  value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/> <sch:assert test=". = $langIdents"> Attribute value must match one of the following language codes in the <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>. </sch:assert> </sch:rule>
Datatype teidata.language
Member of
model.msQuoteLike
Contained by
msdescription: msItem msItemStruct
May contain
core: choice foreign lb note quote ref sic
msdescription: locus
namesdates: persName placeName
transcr: supplied
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="choice" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="lb" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="quote" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="supplied" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element incipit
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   attribute xml:lang { text },
   (
      choice*
    & foreign*
    & lb*
    & locus*
    & note*
    & quote*
    & persName*
    & placeName*
    & ref*
    & sic*
    & supplied*
    & text
   )
}⚓

2.1.94. <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
Contained by
msdescription: msIdentifier
May contain
core: abbr address choice date email expan foreign gap hi lb measure name note num pb ptr q ref term title
figures: figure
header: idno
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am ex fw subst
character data
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
}⚓

2.1.95. <interpretation>

<interpretation> (interpretation) describes the scope of any analytic or interpretive information added to the text in addition to the transcription. [2.3.3. The Editorial Practices Declaration]
Module header — Schema
Contained by
header: editorialDecl
May contain
core: p
Example
<interpretation>  <p>The part of speech analysis applied throughout section 4 was added by hand and has not    been checked</p> </interpretation>
Content model 
<content>
 <elementRef key="p" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element interpretation { p+ }⚓

2.1.96. <item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Module core — Schema
Attributes
Contained by
core: list
May contain
core: bibl choice date label note p quote ref
msdescription: locus
namesdates: persName
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="choice" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="bibl" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="date" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="label" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="p" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="quote" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element item
{
   att.global.attributes,
   (
      choice*
    & bibl*
    & date*
    & label*
    & locus*
    & note*
    & p*
    & persName*
    & quote*
    & ref*
   )
}⚓

2.1.97. <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
scheme identifies the controlled vocabulary within which the set of keywords concerned is defined, for example by a <taxonomy> element, or by some other resource.
Status Required
Datatype teidata.pointer
Contained by
header: textClass
May contain
core: list
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>
 <elementRef key="list" minOccurs="1"
  maxOccurs="1"/>
</content>
    ⚓
Schema Declaration 
element keywords { attribute scheme { text }, list }⚓

2.1.98. <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
Member of
model.lLike
Contained by
core: add corr del lg orig p q quote reg unclear
figures: figure
header: scriptNote
linking: seg
msdescription: condition custEvent foliation musicNotation signatures summary surrogates typeNote
textstructure: div
transcr: supplied
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi label lb list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 minOccurs="0"
  maxOccurs="unbounded">
  <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 )*
}⚓

2.1.99. <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
Member of
model.labelLike
Contained by
core: add corr del item l lg orig p q quote reg unclear
figures: figDesc figure
header: scriptNote
linking: seg
msdescription: condition custEvent foliation musicNotation signatures summary surrogates typeNote
namesdates: place
textstructure: div
transcr: supplied surface
May contain
core: sic
character data
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="gloss" xml: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="runon" type="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>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element label { sic*, text }⚓

2.1.100. <langUsage>

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]
Module header — Schema
Contained by
header: profileDesc
May contain
header: language
Example
<langUsage>  <language ident="fr-CA" usage="60">Québecois</language>  <language ident="en-CA" usage="20">Canadian business English</language>  <language ident="en-GB" usage="20">British English</language> </langUsage>
Content model 
<content>
 <elementRef key="language" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element langUsage { language+ }⚓

2.1.101. <language>

<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Module header — Schema
Attributes
ident (identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which may be referenced by the global xml:lang attribute.
Status Required
Schematron
<sch:rule context="//tei:language/@ident"> <sch:let name="langIdents"  value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/> <sch:assert test=". = $langIdents"> Attribute value must match one of the following language codes in the <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>. </sch:assert> </sch:rule>
Datatype teidata.language
usage specifies the approximate percentage of the text which uses this language.
Status Optional
Datatype nonNegativeInteger
Contained by
header: langUsage
May contain
core: sic
character data
Note

Particularly for sublanguages, an informal prose characterization should be supplied as content for the element.
Example
<langUsage>  <language ident="en-US" usage="75">modern American English</language>  <language ident="az-Arab" usage="20">Azerbaijani in Arabic script</language>  <language ident="x-lap" usage="05">Pig Latin</language> </langUsage>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element language
{
   attribute ident { text },
   attribute usage { text }?,
   sic*,
   text
}⚓

2.1.102. <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
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.
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
core: p
msdescription: locus
Example
<layout columns="1" ruledLines="25 32">Most pages have between 25 and 32 long lines ruled in lead.</layout>
Example
<layout columns="2" ruledLines="42">  <p>2 columns of 42 lines ruled in ink, with central rule    between the columns.</p> </layout>
Example
<layout columns="1 2" writtenLines="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 streams="3" columns="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>
 <elementRef key="locus" minOccurs="0"
  maxOccurs="unbounded"/>
 <elementRef key="p" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element layout
{
   attribute columns { list { ? } }?,
   attribute writtenLines { list { ? } }?,
   locus*,
   p*
}⚓

2.1.103. <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
Contained by
msdescription: objectDesc
May contain
msdescription: layout
Example
<layoutDesc>  <p>Most pages have between 25 and 32 long lines ruled in lead.</p> </layoutDesc>
Example
<layoutDesc>  <layout columns="2" ruledLines="42">   <p>    <locus from="f12r" to="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>
 <elementRef key="layout" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element layoutDesc { layout+ }⚓

2.1.104. <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
Member of
model.milestoneLike
Contained by
core: add addrLine address biblScope cit corr del editor email imprint l lg num orig p publisher q quote reg series street term unclear
figures: figure table
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry incipit institution msItem musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName person region surname
textstructure: div
transcr: subst supplied surface surfaceGrp zone
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
}⚓

2.1.105. <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
Member of
model.divPart model.paraPart
Contained by
core: add corr del lg orig p q quote reg unclear
figures: figure
header: scriptNote
linking: seg
msdescription: condition custEvent foliation musicNotation signatures summary surrogates typeNote
textstructure: div
transcr: supplied
May contain
core: add corr del desc gap head l label lb lg note orig pb reg sic unclear
figures: figure
transcr: damage fw supplied
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 minOccurs="0"
   maxOccurs="unbounded">
   <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 minOccurs="0"
   maxOccurs="unbounded">
   <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 minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    ⚓
Schema Declaration 
element lg
{
   att.global.attributes,
   att.divLike.attributes,
   att.typed.attributes,
   att.declaring.attributes,
   (
      ( model.divTop | model.global )*,
      (
         model.lLike
       | model.stageLike
       | model.labelLike
       | model.pPart.transcriptional
       | lg
      ),
      (
         model.lLike
       | model.stageLike
       | model.labelLike
       | model.pPart.transcriptional
       | model.global
       | lg
      )*,
      ( model.divBottom, model.global* )*
   )
}⚓

2.1.106. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Contained by
header: availability
May contain
core: p
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 target="http://creativecommons.org/licenses/by/3.0/"   notBefore="2013-01-01">   <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>
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>
Content model 
<content>
 <elementRef key="p" minOccurs="1"
  maxOccurs="1"/>
</content>
    ⚓
Schema Declaration 
element licence
{
   att.pointing.attributes,
   attribute calendar { list { + } }?,
   p
}⚓

2.1.107. <list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Module core — Schema
Member of
model.listLike
Contained by
core: add corr del l note orig p q quote reg unclear
figures: figDesc figure
header: keywords scriptNote
linking: seg
msdescription: additions condition custEvent foliation musicNotation signatures summary surrogates typeNote
textstructure: div
transcr: supplied
May contain
core: item
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 type="syllogism" rend="bulleted">  <item>All Cretans are liars.</item>  <item>Epimenides is a Cretan.</item>  <item>ERGO Epimenides is a liar.</item> </list>
Example
<list type="litany" rend="simple">  <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>
 <elementRef key="item" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element list { item+ }⚓

2.1.108. <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
Member of
model.biblLike
Contained by
core: add cit corr del l orig p q quote reg relatedItem unclear
figures: figDesc figure
header: scriptNote
linking: seg
msdescription: additional condition custEvent foliation msItem msItemStruct musicNotation signatures summary surrogates typeNote
namesdates: person place
textstructure: div
transcr: supplied
May contain
core: bibl
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>
 <elementRef key="bibl" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element listBibl { bibl+ }⚓

2.1.109. <listRelation>

<listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [13.3.2.3. Personal Relationships]
Module namesdates — Schema
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Member of
model.listLike
Contained by
core: add corr del head l orig p q quote reg unclear
figures: figDesc figure
header: scriptNote
linking: seg
msdescription: condition custEvent foliation musicNotation signatures summary surrogates typeNote
textstructure: div
transcr: supplied
May contain
core: desc
namesdates: relation
Note

May contain a prose description organized as paragraphs, or a sequence of <relation> elements.
Example
<listPerson>  <person xml:id="pp1"> <!-- data about person pp1 -->  </person>  <person xml:id="pp2"> <!-- data about person pp1 -->  </person> <!-- more person (pp3, pp4) elements here -->  <listRelation type="personal">   <relation name="parent"    active="#pp1 #pp2" passive="#pp3 #pp4"/>   <relation name="spouse"    mutual="#pp1 #pp2"/>  </listRelation>  <listRelation type="social">   <relation name="employer" active="#pp1"    passive="#pp3 #pp5 #pp6 #pp7"/>  </listRelation> </listPerson>
The persons with identifiers pp1 and pp2 are the parents of pp3 and pp4; they are also married to each other; pp1 is the employer of pp3, pp5, pp6, and pp7.
Example
<listPerson>  <person xml:id="en_pp1"> <!-- data about person en_pp1 -->  </person>  <person xml:id="en_pp2"> <!-- data about person en_pp2 -->  </person> <!-- more person (en_pp3, en_pp4) elements here --> </listPerson> <listPlace>  <place xml:id="en_pl1"> <!-- data about place en_pl1 -->  </place> <!-- more place (en_pl2, en_pl3) elements here --> </listPlace> <listRelation>  <relation name="residence"   active="#en_pp1 #en_pp2" passive="#en_pl1"/> </listRelation>
The persons with identifiers en_pp1 and en_pp2 live in en_pl1.
Example
<listRelation>  <p>All speakers are members of the Ceruli family, born in Naples.</p> </listRelation>
Content model 
<content>
 <elementRef key="desc" minOccurs="0"
  maxOccurs="1"/>
 <elementRef key="relation" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element listRelation
{
   att.typed.attribute.subtype,
   attribute type { text },
   desc?,
   relation+
}⚓

2.1.110. <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
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
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del desc editor email foreign item l note num orig p publisher q quote ref reg street term title unclear
figures: cell figDesc
header: distributor handNote scriptNote
linking: seg
msdescription: binding catchwords colophon condition custEvent decoNote explicit finalRubric foliation heraldry incipit institution layout locusGrp material msItem msItemStruct musicNotation objectType provenance rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: fw supplied
May contain
core: hi q sic
gaiji: g
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 target="#F1r #F1v #F2r" from="1r"   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 minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.hiLike"/>
 </alternate>
</content>
    ⚓
Schema Declaration 
element locus
{
   attribute from { text }?,
   attribute to { text }?,
   ( sic* | text | model.gLike | model.hiLike )*
}⚓

2.1.111. <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
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
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msItem msItemStruct musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
msdescription: locus
Example
<msItem>  <locusGrp>   <locus from="13" to="26">Bl. 13--26</locus>   <locus from="37" to="58">37--58</locus>   <locus from="82" to="96">82--96</locus>  </locusGrp>  <note>Stücke von Daniel Ecklin’s Reise ins h. Land</note> </msItem>
Content model 
<content>
 <elementRef key="locus" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element locusGrp { att.global.attributes, attribute scheme { text }?, locus+ }⚓

2.1.112. <mapping>

<mapping> (character mapping) contains one or more characters which are related to the parent character or glyph in some respect, as specified by the type attribute. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Module gaiji — Schema
Attributes
Contained by
gaiji: glyph
May contain
gaiji: g
character data
Note

Suggested values for the type attribute include exact for exact equivalences, uppercase for uppercase equivalences, lowercase for lowercase equivalences, and simplified for simplified characters. The <g> elements contained by this element can point to either another <char> or <glyph> element or contain a character that is intended to be the target of this mapping.
Example
<mapping type="modern">r</mapping> <mapping type="standard">人</mapping>
Content model 
<content>
 <macroRef key="macro.xtext"/>
</content>
    ⚓
Schema Declaration 
element mapping { att.global.attributes, att.typed.attributes, macro.xtext }⚓

2.1.113. <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
function describes 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.
target identifies one or more elements to which the metamark applies.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary support surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: sic
msdescription: locus
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element material
{
   attribute function { text }?,
   attribute target { list { + } }?,
   ( locus* & sic* & text )
}⚓

2.1.114. <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
type specifies the type of measurement in any convenient typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
unit (unit) indicates the units used for the measurement, usually using the standard symbol for the desired units.
Derived from att.measurement
Status Required
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
quantity (quantity) specifies the number of the specified units that comprise the measurement
Derived from att.measurement
Status Required
Datatype teidata.numeric
Member of
model.measureLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor extent scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: sic
character data
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="area" unitRef="#merk">2 <unit>merks</unit> of old extent</measure> <!-- In the TEI Header: --> <encodingDesc>  <unitDecl>   <unitDef xml:id="merk" type="area">    <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 quantity="40" unit="hogshead"  commodity="rum">2 score hh rum</measure> <measure quantity="12" unit="count"  commodity="roses">1 doz. roses</measure> <measure quantity="1" unit="count"  commodity="tulips">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 max="500" unit="count"   commodity="words">500    words</measure>. This presentation type is suitable for substantial research, theoretical or critical discussions.</p>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element measure
{
   att.typed.attribute.subtype,
   attribute type { text },
   attribute unit
   {
      "m"
    | "kg"
    | "s"
    | "Hz"
    | "Pa"
    | "Ω"
    | "L"
    | "t"
    | "ha"
    | "Å"
    | "mL"
    | "cm"
    | "dB"
    | "kbit"
    | "Kibit"
    | "kB"
    | "KiB"
    | "MB"
    | "MiB"
   },
   attribute quantity { text },
   sic*,
   text
}⚓

2.1.115. <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
Contained by
core: biblStruct
May contain
core: author biblScope editor imprint note ptr ref respStmt textLang title
header: authority availability edition extent funder idno sponsor
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 unit="page" from="377" to="380">377–380</biblScope>  </monogr> </biblStruct>
Example
<biblStruct type="book">  <monogr>   <author>    <persName>     <forename>Leo Joachim</forename>     <surname>Frachtenberg</surname>    </persName>   </author>   <title type="main" level="m">Lower Umpqua Texts</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Columbia University Press</publisher>    <date>1914</date>   </imprint>  </monogr>  <series>   <title type="main" level="s">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 minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <elementRef key="title" minOccurs="1"
     maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
     <elementRef key="textLang"/>
     <elementRef key="editor"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="title"/>
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <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"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.noteLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="edition"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <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 minOccurs="0"
   maxOccurs="unbounded">
   <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 )*
   )
}⚓

2.1.116. <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
Contained by
msdescription: msDesc msFrag msPart
May contain
core: textLang
msdescription: msItem
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="textLang" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="msItem" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element msContents { textLang, msItem+ }⚓

2.1.117. <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
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Optional
Schematron
<sch:rule context="//tei:msDesc/@xml:id"> <sch:let name="docURIno"  value="replace(ancestor::tei:fileDesc/tei:publicationStmt/tei:idno[@type='URI']/text(), '.+?(\d+).+', '$1')"/> <sch:let name="msDescIDno"  value="replace(., '.+?(\d+)', '$1')"/> <sch:assert test="$msDescIDno = $docURIno"> The number portion of this @xml:id attribute must match the number portion of the <idno> in <publicationStmt>: <sch:value-of select="$docURIno"/> </sch:assert> </sch:rule>
Datatype ID
Member of
model.biblLike
Contained by
core: add cit corr del l orig p q quote reg relatedItem unclear
figures: figDesc figure
header: scriptNote sourceDesc
linking: seg
msdescription: condition custEvent foliation msItem musicNotation signatures summary surrogates typeNote
namesdates: person place
textstructure: div
transcr: supplied
May contain
core: head p
msdescription: additional history msContents msFrag msIdentifier msPart physDesc
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>
Schematron
<sch:rule context="tei:msContents|tei:physDesc|tei:history|tei:additional"> <!-- Note: This rule applies to <msContents>, <physDesc>, <history>, and <additional> wherever they occur. Luckily they are only allowed in places where they are constrained to 0 or 1 occurence. If that changes someday, this constraint may will likely need to be updated, too. --> <!-- Also worth noting that a) if &amp; when we can use abstract patterns, this would be better handled as a single abstract rule somewhere, and concrete rules in the individual <elementSpec>s; and b) I did not test for the existence of "../*[name(.) eq $gi][2]" because then an error would be generated for each of the multiple occurences of $gi. --> <sch:let name="gi" value="name(.)"/> <sch:report test="preceding-sibling::*[ name(.) eq $gi ] and not( following-sibling::*[ name(.) eq $gi ] )"> Only one <sch:name/> is allowed as a child of <sch:value-of select="name(..)"/>. </sch:report> </sch:rule>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="msIdentifier"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="msContents"/>
    <elementRef key="physDesc"/>
    <elementRef key="history"/>
    <elementRef key="additional"/>
    <elementRef key="msPart"/>
    <elementRef key="msFrag"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    ⚓
Schema Declaration 
element msDesc
{
   att.global.attribute.n,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   attribute xml:id { text }?,
   (
      msIdentifier,
      model.headLike*,
      (
         model.pLike+
       | ( msContents | physDesc | history | additional | msPart | msFrag )*
      )
   )
}⚓

2.1.118. <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
Contained by
msdescription: msDesc
May contain
core: head p
msdescription: additional altIdentifier history msContents msIdentifier physDesc
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"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="msContents"/>
    <elementRef key="physDesc"/>
    <elementRef key="history"/>
    <elementRef key="additional"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    ⚓
Schema Declaration 
element msFrag
{
   att.global.attributes,
   att.typed.attributes,
   (
      ( altIdentifier | msIdentifier ),
      model.headLike*,
      ( model.pLike+ | ( msContents | physDesc | history | additional )* )
   )
}⚓

2.1.119. <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
Contained by
msdescription: msDesc msFrag msPart
May contain
header: idno
msdescription: altIdentifier collection institution msName repository
namesdates: country district geogName placeName region settlement
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 minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <classRef key="model.placeNamePart"
    expand="sequenceOptional"/>
   <elementRef key="institution"
    minOccurs="0"/>
   <elementRef key="repository"
    minOccurs="0"/>
   <elementRef key="collection"
    minOccurs="0" maxOccurs="unbounded"/>
   <elementRef key="idno" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="msName"/>
   <elementRef key="objectName"/>
   <elementRef key="altIdentifier"/>
  </alternate>
 </sequence>
</content>
    ⚓
Schema Declaration 
element msIdentifier
{
   (
      placeName?,
      country?,
      region?,
      settlement?,
      district?,
      geogName?,
      institution?,
      repository?,
      collection*,
      idno*
   ),
   ( msName | objectName | altIdentifier )*
}⚓

2.1.120. <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
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Required
Datatype teidata.text
defective indicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
Derived from att.msExcerpt
Status Optional
Schematron
<sch:rule context="tei:msItem[descendant::tei:msItem[@defective='true']]"> <sch:assert test="@defective='true'"> This <msItem> element must have a @defective attribute with the value "true" because its contains a descendant <msItem> element indicating that it is defective. </sch:assert> </sch:rule>
Datatype teidata.xTruthValue
Member of
model.msItemPart
Contained by
msdescription: msContents msItem
May contain
core: author bibl biblStruct cit editor gap graphic lb listBibl note p pb quote respStmt textLang title
figures: figure
header: funder idno principal sponsor
msdescription: colophon decoNote explicit filiation finalRubric incipit locus locusGrp msDesc msItem msItemStruct rubric
transcr: fw
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 reason="illegible" extent="7"/>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 minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="locus"/>
   <elementRef key="locusGrp"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.titlepagePart"/>
    <classRef key="model.msItemPart"/>
    <classRef key="model.global"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    ⚓
Schema Declaration 
element msItem
{
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   attribute xml:id { text },
   attribute n { text },
   attribute defective { text }?,
   (
      ( locus | locusGrp )*,
      (
         model.pLike+
       | ( model.titlepagePart | model.msItemPart | model.global )+
      )
   )
}⚓

2.1.121. <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
Member of
model.msItemPart
Contained by
msdescription: msItem msItemStruct
May contain
core: author bibl biblStruct listBibl note p respStmt textLang title
msdescription: colophon decoNote explicit filiation finalRubric incipit locus locusGrp msItemStruct rubric
Example
<msItemStruct n="2" defective="false"  class="#biblComm">  <locus from="24v" to="97v">24v-97v</locus>  <author>Apringius de Beja</author>  <title type="uniform" xml: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"
    minOccurs="1" maxOccurs="unbounded"/>
   <sequence>
    <elementRef key="author" minOccurs="0"
     maxOccurs="unbounded"/>
    <elementRef key="respStmt"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="title" minOccurs="0"
     maxOccurs="unbounded"/>
    <elementRef key="rubric" minOccurs="0"/>
    <elementRef key="incipit" minOccurs="0"/>
    <elementRef key="msItemStruct"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="explicit"
     minOccurs="0"/>
    <elementRef key="finalRubric"
     minOccurs="0"/>
    <elementRef key="colophon"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="decoNote"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="listBibl"
     minOccurs="0" maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="bibl"/>
     <elementRef key="biblStruct"/>
    </alternate>
    <elementRef key="filiation"
     minOccurs="0"/>
    <classRef key="model.noteLike"
     minOccurs="0" maxOccurs="unbounded"/>
    <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?
         )
      )
   )
}⚓

2.1.122. <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
Contained by
msdescription: msIdentifier
May contain
core: name
gaiji: g
character data
Example
<msName>The Vercelli Book</msName>
Content model 
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <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 )*
}⚓

2.1.123. <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
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Required
Datatype teidata.text
Contained by
msdescription: msDesc msPart
May contain
core: head p
msdescription: additional history msContents msIdentifier msPart physDesc
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 notBefore="0801"    notAfter="0815">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 minOccurs="1" maxOccurs="1">
  <elementRef key="msIdentifier"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="msContents"/>
    <elementRef key="physDesc"/>
    <elementRef key="history"/>
    <elementRef key="additional"/>
    <elementRef key="msPart"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    ⚓
Schema Declaration 
element msPart
{
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   attribute xml:id { text },
   attribute n { text },
   (
      msIdentifier,
      model.headLike*,
      (
         model.pLike+
       | ( msContents | physDesc | history | additional | msPart )*
      )
   )
}⚓

2.1.124. <musicNotation>

<musicNotation> (music notation) contains description of type of musical notation. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Attributes
Contained by
—
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 }⚓

2.1.125. <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Module core — Schema
Attributes
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.
Derived from att.canonical
Status Required
Schematron
<sch:rule context="//tei:name/@ref"> <sch:let name="edsDoc"  value="doc('https://raw.githubusercontent.com/srophe/britishLibrary/main/documentation/editors.xml')"/> <sch:let name="eds"  value="$edsDoc//tei:text/tei:body/tei:listPerson/tei:person/@xml:id | $edsDoc//tei:text/tei:body/tei:listPerson/tei:org/@xml:id"/> <sch:let name="refValues"  value="for $i in $eds return concat('https://bl.syriac.uk/documentation/editors.xml#', $i)"/> <sch:assert test="every $i in . satisfies $i = $refValues"> Acceptable values for this @ref attribute include: <sch:value-of select="string-join($refValues, ' | ')"/>. </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
org
The name is of an organisation
person
The name is of a person
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.nameLike.agent model.personPart
Contained by
core: add addrLine address biblScope corr del editor email l num orig p publisher q quote reg respStmt street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msName musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName person place region surname
transcr: supplied
May contain Character data only
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 type="person" ref="#HOC001">Occleve</name>
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>
Content model 
<content>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element name
{
   att.global.attributes,
   att.typed.attribute.subtype,
   attribute ref { list { + } },
   attribute type { "org" | "person" },
   attribute calendar { list { + } }?,
   text
}⚓

2.1.126. <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
resp (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Derived from att.global.responsibility
Status Optional
Schematron
<sch:rule context="//tei:note/@resp"> <sch:let name="edsDoc"  value="doc('https://raw.githubusercontent.com/srophe/britishLibrary/main/documentation/editors.xml')"/> <sch:let name="eds"  value="$edsDoc//tei:text/tei:body/tei:listPerson/tei:person/@xml:id | $edsDoc//tei:text/tei:body/tei:listPerson/tei:org/@xml:id"/> <sch:let name="refValues"  value="for $i in $eds return concat('https://bl.syriac.uk/documentation/editors.xml#', $i)"/> <sch:assert test="every $i in . satisfies $i = $refValues"> Acceptable values for this @resp attribute include: <sch:value-of select="string-join($refValues, ' | ')"/>. </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Member of
model.noteLike
Contained by
core: add addrLine address biblScope biblStruct cit corr del editor email head imprint item l lg monogr note num orig p publisher q quote reg series street term unclear
figures: figure table
gaiji: glyph
header: distributor handNote scriptNote
linking: seg
msdescription: additions adminInfo catchwords condition custEvent explicit finalRubric foliation heraldry incipit institution msItem msItemStruct musicNotation objectType origin rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName person place region surname
textstructure: div
transcr: supplied surface surfaceGrp zone
May contain
core: bibl choice date foreign list note p ptr quote ref sic title
figures: table
msdescription: locus
namesdates: persName placeName
character data
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="bottom" type="gloss"  resp="#MDMH">  <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 n="126" anchored="true"> 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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="bibl" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="choice" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="date" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="list" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="p" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ptr" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="quote" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="table" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="title" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element note
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.source.attribute.source,
   att.typed.attribute.subtype,
   attribute resp { list { + } }?,
   attribute type { text }?,
   (
      bibl*
    & choice*
    & date*
    & foreign*
    & list*
    & locus*
    & note*
    & p*
    & persName*
    & placeName*
    & ptr*
    & quote*
    & ref*
    & sic*
    & table*
    & title*
    & text
   )
}⚓

2.1.127. <num>

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]
Module core — Schema
Attributes
type indicates the type of numeric value.
Derived from att.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.
value supplies 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
model.measureLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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="cardinal" value="21">twenty-one</num> on my <num type="ordinal" value="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" }?,
   attribute value { text }?,
   macro.phraseSeq
}⚓

2.1.128. <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
form (form) a short project-specific name identifying the physical form of the carrier, for example as a codex, roll, fragment, partial leaf, cutting etc.
Status Required
Datatype teidata.enumerated
Note

Definitions for the terms used may typically be provided by a <valList> element in the project schema specification.
Contained by
msdescription: physDesc
May contain
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 see="https://msdesc.github.io/consolidated-tei-schema/msdesc.html#objectdescBook"  context="//tei:sourceDesc/tei:msDesc[not(tei:msPart)]"> <sch:assert test="tei:physDesc/tei:objectDesc[@form]"  role="warn"> 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 test=" tei:physDesc/tei:objectDesc[@form] or ancestor::tei:msDesc/tei:physDesc/tei:objectDesc[@form] "  role="warn"> 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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="supportDesc"
   minOccurs="1"/>
  <elementRef key="layoutDesc"
   minOccurs="0"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element objectDesc { attribute form { text }, ( supportDesc, layoutDesc? ) }⚓

2.1.129. <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
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.130. <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
Member of
model.pPart.transcriptional
Contained by
core: add addrLine biblScope choice corr del editor email l lg num orig p publisher q quote reg street term unclear
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: am supplied
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 }⚓

2.1.131. <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
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType origin secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: sic
character data
Example
<origDate notBefore="-0300"  notAfter="-0200">3rd century BCE</origDate>
Schematron
<sch:rule context="//tei:origDate"> <sch:assert test="@calendar and ((@when or @notBefore or @notAfter or @from or @to) or (@when-custom or @notBefore-custom or @notAfter-custom or @from-custom or @to-custom)) and string-length(normalize-space(string())) gt 0"  role="error"> The origDate element must have two or more attributes - calendar and at least one of the regular date attributes (when, notBefore, notAfter, from, and/or to) -OR- custom dates (when-custom, notBefore-custom, notAfter-custom, from-custom, and/or to-custom) and must contain some text describing the date. </sch:assert> </sch:rule>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element origDate
{
   att.datable.attributes,
   att.calendarSystem.attributes,
   att.editLike.attributes,
   att.typed.attribute.subtype,
   attribute type { text }?,
   sic*,
   text
}⚓

2.1.132. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType origin secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: foreign sic
namesdates: placeName
character data
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>
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>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element origPlace
{
   att.canonical.attributes,
   att.global.attributes,
   att.editLike.attributes,
   attribute calendar { list { + } }?,
   ( foreign* & placeName* & sic* & text )
}⚓

2.1.133. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Contained by
msdescription: history
May contain
core: note
msdescription: origDate origPlace
Example
<origin notBefore="1802" notAfter="1845"  evidence="internal" resp="#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>
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>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="origDate" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="origPlace" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element origin
{
   attribute calendar { list { + } }?,
   ( note* & origDate+ & origPlace* )
}⚓

2.1.134. <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Module core — Schema
Member of
model.pLike
Contained by
core: item note q quote
figures: figure
header: interpretation licence projectDesc scriptNote
msdescription: accMat acquisition additions collation condition custEvent custodialHist foliation layout msDesc msFrag msItem msItemStruct msPart musicNotation physDesc scriptDesc seal sealDesc signatures summary supportDesc surrogates typeDesc typeNote
namesdates: person place
textstructure: body div
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 { macro.paraContent }⚓

2.1.135. <pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]
Module core — Schema
Attributes
Member of
model.milestoneLike
Contained by
core: add addrLine address biblScope cit corr del editor email imprint l lg num orig p publisher q quote reg series street term unclear
figures: figure table
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msItem musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName person region surname
textstructure: div
transcr: subst supplied surface surfaceGrp zone
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 n="145" ed="ed2"/> <!-- Page 145 in edition "ed2" starts here --> ... <pb n="283" ed="ed1"/> <!-- 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 n="1" facs="page1.png"/> <!-- page1.png contains an image of the page; the text it contains is encoded here -->  <p> <!-- ... -->  </p>  <pb n="2" facs="page2.png"/> <!-- 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
}⚓

2.1.136. <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
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.
Derived from att.canonical
Status Optional
Schematron
<sch:rule context="tei:persName/@ref"> <sch:let name="personIndex"  value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/persons.xml')"/> <sch:let name="personURIs"  value="$personIndex//tei:person/@ref"/> <sch:let name="error" value="."/> <sch:assert test="starts-with(., 'http://syriaca.org/person/') or starts-with(., 'smbl')"> The @ref attribute must begin with either "http://syriaca.org/person/" or with "smbl". </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.nameLike.agent model.persStateLike
Contained by
core: add addrLine address author biblScope corr date del desc editor email foreign item l note num orig p publisher q quote ref reg street term unclear
figures: figDesc
header: distributor handNote scriptNote
linking: seg
msdescription: binding catchwords condition custEvent decoNote explicit finalRubric foliation heraldry incipit institution musicNotation objectType provenance rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName persName person region surname
transcr: supplied
May contain
core: choice foreign sic
namesdates: persName placeName
transcr: supplied
character data
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:persName/tei:choice"> <sch:assert test="((tei:sic and tei:corr) or (tei:abbr and tei:expan))"> As child of <persName>, <choice> can either be used to correct a mistake in the original print volume (using <sic> and <corr>) or to indicate an abbreviation and an expansion of that abbreviation (using <abbr> and <expan>). The <choice> element should not be used to mark up a name in different languages. </sch:assert> </sch:rule>
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>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="choice" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="supplied" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element persName
{
   att.global.attributes,
   att.editLike.attributes,
   att.typed.attribute.subtype,
   attribute ref { list { + } }?,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   ( choice* & foreign* & persName? & placeName* & sic* & supplied* & text )
}⚓

2.1.137. <person>

<person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element 15.2.2. The Participant Description]
Module namesdates — Schema
Attributes
role specifies a primary role or classification for the person.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.
sex specifies the sex of the person.
Status Optional
Datatype 1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.
gender specifies the gender of the person.
Status Optional
Datatype 1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.
age specifies an age group for the person.
Status Optional
Datatype teidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.
Contained by
—
May contain
core: bibl biblStruct gap lb listBibl name note p pb ptr
figures: figure
header: idno
msdescription: msDesc
namesdates: persName
transcr: fw
Note

May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.
Example
<person sex="F" age="adult">  <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic    status B2.</p> </person>
Example
<person sex="intersex" role="god"  age="immortal">  <persName>Hermaphroditos</persName>  <persName xml:lang="grc">Ἑρμαφρόδιτος</persName> </person>
Example
<person xml:id="Ovi01" sex="M" role="poet">  <persName xml:lang="en">Ovid</persName>  <persName xml:lang="la">Publius Ovidius Naso</persName>  <birth when="-0044-03-20"> 20 March 43 BC <placeName>    <settlement type="city">Sulmona</settlement>    <country key="IT">Italy</country>   </placeName>  </birth>  <death notBefore="0017" notAfter="0018">17 or 18 AD <placeName>    <settlement type="city">Tomis (Constanta)</settlement>    <country key="RO">Romania</country>   </placeName>  </death> </person>
Example The following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character.
<person xml:id="ariel" gender="U">  <persName>Ariel</persName>  <note>Character in <title level="m">The Tempest</title>.</note> </person>
Content model 
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
   <elementRef key="ptr"/>
  </alternate>
 </alternate>
</content>
    ⚓
Schema Declaration 
element person
{
   att.global.attributes,
   att.editLike.attributes,
   att.sortable.attributes,
   attribute role { list { + } }?,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   ( model.pLike+ | ( model.personPart | model.global | ptr )* )
}⚓

2.1.138. <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
Contained by
msdescription: msDesc msFrag msPart
May contain
core: p
msdescription: accMat additions bindingDesc decoDesc handDesc objectDesc
Example
<physDesc>  <objectDesc form="codex">   <supportDesc material="perg">    <support>Parchment.</support>    <extent>i + 55 leaves    <dimensions scope="all" type="leaf"      unit="inch">      <height>7¼</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 minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="p" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="objectDesc"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="handDesc" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="decoDesc" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="additions" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="bindingDesc"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="accMat" minOccurs="0"
   maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element physDesc
{
   p+, objectDesc, handDesc?, decoDesc?, additions?, bindingDesc?, accMat?
}⚓

2.1.139. <place>

<place> (place) contains data about a geographic location [13.3.4. Places]
Module namesdates — Schema
Attributes
Member of
model.placeLike
Contained by
namesdates: place
May contain
core: bibl biblStruct desc head label listBibl name note p ptr
header: idno
msdescription: msDesc
namesdates: country district geogName place placeName region settlement
Example
<place>  <country>Lithuania</country>  <country xml:lang="lt">Lietuva</country>  <place>   <settlement>Vilnius</settlement>  </place>  <place>   <settlement>Kaunas</settlement>  </place> </place>
Content model 
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.placeStateLike"/>
    <classRef key="model.eventLike"/>
    <elementRef key="name"/>
   </alternate>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="idno"/>
   <elementRef key="ptr"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.placeLike"/>
   <elementRef key="listPlace"/>
  </alternate>
 </sequence>
</content>
    ⚓
Schema Declaration 
element place
{
   att.global.attributes,
   att.typed.attributes,
   att.editLike.attributes,
   att.sortable.attributes,
   (
      model.headLike*,
      (
         model.pLike*
       | ( model.labelLike | model.placeStateLike | model.eventLike | name )*
      ),
      ( model.noteLike | model.biblLike | idno | ptr | linkGrp | link )*,
      ( model.placeLike | listPlace )*
   )
}⚓

2.1.140. <placeName>

<placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names]
Module namesdates — Schema
Attributes
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.
Derived from att.canonical
Status Optional
Schematron
<sch:rule context="//tei:text//tei:placeName/@ref"> <sch:let name="placeIndex"  value="doc('https://raw.githubusercontent.com/srophe/syriaca/master/documentation/indexes/places.xml')"/> <sch:let name="placeURIs"  value="$placeIndex//tei:place/@ref"/> <sch:let name="error" value="."/> <sch:assert test="starts-with(., 'http://syriaca.org/place/') or starts-with(., 'smbl')"> The @ref attribute must begin with either "http://syriaca.org/person/" or with "smbl". </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.placeNamePart
Contained by
core: add addrLine address biblScope corr date del desc editor email foreign l note num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor handNote scriptNote
linking: seg
msdescription: binding catchwords condition custEvent decoNote explicit finalRubric foliation heraldry incipit institution msIdentifier musicNotation objectType origPlace provenance rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName persName place placeName region surname
transcr: supplied
May contain
core: choice foreign sic
namesdates: placeName
transcr: supplied
character data
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:placeName/tei:choice"> <sch:assert test="((tei:sic and tei:corr) or (tei:abbr and tei:expan))"> As child of <persName>, <choice> can either be used to correct a mistake in the original print volume (using <sic> and <corr>) or to indicate an abbreviation and an expansion of that abbreviation (using <abbr> and <expan>). The <choice> element should not be used to mark up a name in different languages. </sch:assert> </sch:rule>
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>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="choice" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="supplied" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element placeName
{
   att.editLike.attributes,
   att.global.attributes,
   att.typed.attributes,
   attribute ref { list { + } }?,
   attribute calendar { list { + } }?,
   ( choice* & foreign* & placeName* & sic* & supplied* & text )
}⚓

2.1.141. <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
Member of
model.addrPart
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 }⚓

2.1.142. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.respLike
Contained by
header: titleStmt
msdescription: msItem
May contain
core: sic
character data
Example
<principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal>
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>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element principal { attribute calendar { list { + } }?, sic*, text }⚓

2.1.143. <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
Member of
model.teiHeaderPart
Contained by
header: teiHeader
May contain
header: langUsage 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 type="entertain" degree="high"/>   <purpose type="inform" degree="medium"/>  </textDesc>  <settingDesc>   <setting>    <name>Paris, France</name>    <time>Late 19th century</time>   </setting>  </settingDesc> </profileDesc>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="langUsage" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="textClass" minOccurs="1"
   maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element profileDesc { langUsage, textClass }⚓

2.1.144. <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
Contained by
—
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" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element projectDesc
{
   att.global.attributes,
   att.declarable.attributes,
   model.pLike+
}⚓

2.1.145. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Contained by
msdescription: history
May contain
core: bibl date ref sic
msdescription: locus
namesdates: persName placeName
character data
Example
<provenance>Listed as the property of Lawrence Sterne in 1788.</provenance> <provenance>Sold at Sothebys in 1899.</provenance>
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>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="bibl" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="date" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element provenance
{
   attribute calendar { list { + } }?,
   ( bibl* & date* & locus* & persName* & placeName* & ref* & sic* & text )
}⚓

2.1.146. <ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links]
Module core — Schema
Attributes
target specifies the destination of the reference by supplying one or more URI References
Derived from att.pointing
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Member of
model.ptrLike
Contained by
core: add addrLine analytic bibl biblScope biblStruct cit corr del editor email l monogr note num orig p publisher q quote reg relatedItem series street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName person place region surname
transcr: supplied
May contain Empty element
Example
<ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/>
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>
 <empty/>
</content>
    ⚓
Schema Declaration 
element ptr
{
   att.cReferencing.attributes,
   attribute target { list { + } },
   empty
}⚓

2.1.147. <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
Member of
model.imprintPart
Contained by
core: bibl imprint
May contain
core: sic
character data
Example
<publicationStmt>  <publisher>Oxford University Press</publisher>  <pubPlace>Oxford</pubPlace>  <date>1989</date> </publicationStmt>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element pubPlace { sic*, text }⚓

2.1.148. <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
Contained by
header: fileDesc
May contain
core: date
header: authority availability idno
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="authority" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="idno" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="availability"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="date" minOccurs="1"
   maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element publicationStmt { authority, idno, availability, date }⚓

2.1.149. <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
Member of
model.imprintPart
Contained by
core: imprint
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.150. <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
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) foreign words
distinct
(distinct) linguistically distinct
term
technical term
emph
(emph) rhetorically emphasized
mentioned
(mentioned) refering to itself, not its normal referent
Member of
model.common model.hiLike
Contained by
core: add addrLine biblScope cit corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc figure formula
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution locus musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
textstructure: div
transcr: supplied zone
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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,
   attribute type
   {
      "spoken"
    | "thought"
    | "written"
    | "soCalled"
    | "foreign"
    | "distinct"
    | "term"
    | "emph"
    | "mentioned"
   }?,
   macro.specialPara
}⚓

2.1.151. <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
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Required
Schematron
<sch:rule context="//tei:quote/@xml:lang"> <sch:let name="langIdents"  value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/> <sch:assert test=". = $langIdents"> Attribute value must match one of the following language codes in the <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>. </sch:assert> </sch:rule>
Datatype teidata.language
Member of
model.quoteLike
Contained by
core: add addrLine biblScope cit corr del desc editor email item l note num orig p publisher q quote reg street term title unclear
figures: figDesc figure
header: distributor handNote scriptNote
linking: seg
msdescription: catchwords condition custEvent decoNote finalRubric foliation heraldry incipit msItem musicNotation objectType rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
textstructure: div
transcr: supplied
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   attribute xml:lang { text },
   macro.specialPara
}⚓

2.1.152. <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
Contained by
msdescription: adminInfo
May contain
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="source" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="change" minOccurs="0"
   maxOccurs="1"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element recordHist { source, change? }⚓

2.1.153. <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
target specifies the destination of the reference by supplying one or more URI References
Derived from att.pointing
Status Optional
Schematron
<sch:rule context="//tei:ref/@target[contains(., 'hand')]"> <sch:let name="handIDs"  value="//@xml:id[contains(., 'hand')]"/> <sch:let name="IDsToPointers"  value="for $i in $handIDs return concat('#', $i)"/> <sch:assert test=". = $IDsToPointers"> Attribute value must match one of the following @xml:id attributes: <sch:value-of select="string-join($IDsToPointers, ' | ')"/>. </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Member of
model.ptrLike
Contained by
core: add addrLine analytic bibl biblScope biblStruct cit corr date del desc editor email foreign item l monogr note num orig p publisher q quote reg relatedItem series street term unclear
figures: cell figDesc
header: change distributor handNote scriptNote
linking: seg
msdescription: binding catchwords colophon condition custEvent decoNote explicit finalRubric foliation heraldry incipit institution musicNotation objectType provenance rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: choice foreign sic
msdescription: locus
namesdates: persName
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="choice" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element ref
{
   att.cReferencing.attributes,
   att.typed.attribute.subtype,
   attribute target { list { + } }?,
   attribute type { text }?,
   ( choice* & foreign* & locus* & persName* & sic* & text )
}⚓

2.1.154. <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
Member of
model.pPart.transcriptional
Contained by
core: add addrLine biblScope choice corr del editor email l lg num orig p publisher q quote reg street term unclear
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: am supplied
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.155. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.placeNamePart
Contained by
core: add addrLine address biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msIdentifier musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName place region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
Example
<placeName>  <region type="state" n="IL">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,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}⚓

2.1.156. <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
target points to the related bibliographic element by means of an absolute or relative URI reference
Status Optional
Datatype teidata.pointer
Contained by
core: biblStruct
May contain
core: bibl biblStruct listBibl ptr ref
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 { text }?,
   ( model.biblLike | model.ptrLike )?
}⚓

2.1.157. <relation>

<relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [13.3.2.3. Personal Relationships]
Module namesdates — Schema
Attributes
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.
Derived from att.canonical
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
active identifies the ‘active’ participants in a non-mutual relationship, or all the participants in a mutual one.
Status Optional
Schematron
<sch:rule context="//tei:msDesc/tei:head//tei:relation/@active"> <sch:let name="msDescURI"  value="ancestor::tei:msDesc/tei:msIdentifier/tei:idno[@type='URI']/text()"/> <sch:assert test=". = $msDescURI"> The value of @active must match the <idno> in the containing <msDesc>: <sch:value-of select="$msDescURI"/> </sch:assert> </sch:rule> <sch:rule context="//tei:msPart/tei:head//tei:relation/@active"> <sch:let name="msPartURI"  value="ancestor::tei:msPart/tei:msIdentifier/tei:idno[@type='URI']/text()"/> <sch:assert test=". = $msPartURI"> The value of @active must match the <idno> in the containing <msPart>: <sch:value-of select="$msPartURI"/> </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
mutual supplies a list of participants amongst all of whom the relationship holds equally.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
name supplies a name for the kind of relationship of which this is an instance.
Status Required
Datatype teidata.enumerated
passive identifies the ‘passive’ participants in a non-mutual relationship.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
namesdates: listRelation
May contain
core: desc
Note

Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages.
Example
<relation type="social" name="supervisor"  active="#p1" passive="#p2 #p3 #p4"/>
This indicates that the person with identifier p1 is supervisor of persons p2, p3, and p4.
Example
<relation type="personal" name="friends"  mutual="#p2 #p3 #p4"/>
This indicates that p2, p3, and p4 are all friends.
Example
<relation type="CRM"  name="P89_falls_within"  active="http://id.clarosnet.org/places/metamorphoses/place/italy-orvieto"  passive="http://id.clarosnet.org/places/metamorphoses/country/IT"/>
This indicates that there is a relation, defined by CIDOC CRM, between two resources identified by URLs.
Example
<relation resp="http://viaf.org/viaf/44335536/"  ref="http://purl.org/saws/ontology#isVariantOf"  active="http://www.ancientwisdoms.ac.uk/cts/urn:cts:greekLit:tlg3017.Syno298.sawsGrc01:divedition.divsection1.o14.a107"  passive="http://data.perseus.org/citations/urn:cts:greekLit:tlg0031.tlg002.perseus-grc1:9.35"/>
This example records a relationship, defined by the SAWS ontology, between a passage of text identified by a CTS URN, and a variant passage of text in the Perseus Digital Library, and assigns the identification of the relationship to a particular editor (all using resolvable URIs).
Schematron
<sch:assert test="@ref or @key or @name">One of the attributes 'name', 'ref' or 'key' must be supplied</sch:assert>
Schematron
<sch:report test="@active and @mutual">Only one of the attributes @active and @mutual may be supplied</sch:report>
Schematron
<sch:report test="@passive and not(@active)">the attribute 'passive' may be supplied only if the attribute 'active' is supplied</sch:report>
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>
Content model 
<content>
 <elementRef key="desc" minOccurs="0"
  maxOccurs="1"/>
</content>
    ⚓
Schema Declaration 
element relation
{
   attribute ref { list { + } },
   ( attribute active { list { + } }? | attribute mutual { list { + } }? ),
   attribute calendar { list { + } }?,
   attribute name { text },
   attribute passive { list { + } }?,
   desc?
}⚓

2.1.158. <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
Contained by
msdescription: msIdentifier
May contain
core: sic
character data
Example
<msIdentifier>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Bodleian Library</repository>  <idno>MS. Bodley 406</idno> </msIdentifier>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element repository { sic*, text }⚓

2.1.159. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Contained by
core: respStmt
May contain
core: sic
character data
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>
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>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element resp { attribute calendar { list { + } }?, sic*, text }⚓

2.1.160. <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
Member of
model.respLike
Contained by
core: analytic imprint monogr series
header: titleStmt
msdescription: msItem msItemStruct
May contain
core: name resp
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 minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="resp" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="name" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element respStmt { resp, name+ }⚓

2.1.161. <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
status describes the status of a document either currently or, when associated with a dated element, at the time indicated.
Derived from att.docStatus
Status Required
Datatype teidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Contained by
header: teiHeader
May contain
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-11" who="#LB"> deleted chapter 10 </change> </revisionDesc>
Content model 
<content>
 <elementRef key="change" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element revisionDesc { attribute status { text }, change+ }⚓

2.1.162. <row>

<row> (row) contains one row of a table. [14.1.1. TEI Tables]
Module figures — Schema
Contained by
figures: table
May contain
figures: cell
Example
<row role="data">  <cell role="label">Classics</cell>  <cell>Idle listless and unimproving</cell> </row>
Content model 
<content>
 <elementRef key="cell" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element row { cell+ }⚓

2.1.163. <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
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Required
Schematron
<sch:rule context="//tei:rubric/@xml:lang"> <sch:let name="langIdents"  value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/> <sch:assert test=". = $langIdents"> Attribute value must match one of the following language codes in the <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>. </sch:assert> </sch:rule>
Datatype teidata.language
Member of
model.msQuoteLike
Contained by
msdescription: msItem msItemStruct
May contain
core: choice foreign gap note quote ref sic
msdescription: locus
namesdates: persName placeName
transcr: fw supplied
character data
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="choice" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="fw" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="gap" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="persName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="placeName" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="quote" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="ref" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="supplied" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element rubric
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   att.typed.attributes,
   attribute xml:lang { text },
   (
      choice*
    & locus*
    & foreign*
    & fw*
    & gap*
    & note*
    & persName*
    & placeName*
    & quote*
    & ref*
    & sic*
    & supplied*
    & text
   )
}⚓

2.1.164. <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
Contained by
—
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" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="scriptNote"
    minOccurs="1" maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    ⚓
Schema Declaration 
element scriptDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, scriptNote+ ) )
}⚓

2.1.165. <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
Contained by
msdescription: scriptDesc
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
Example
<scriptNote scope="sole"/>
Content model 
<content>
 <macroRef key="macro.specialPara"/>
</content>
    ⚓
Schema Declaration 
element scriptNote
{
   att.global.attributes,
   att.handFeatures.attributes,
   macro.specialPara
}⚓

2.1.166. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
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="2" type="pendant"  subtype="cauda_duplex">  <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 minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <elementRef key="decoNote"/>
 </alternate>
</content>
    ⚓
Schema Declaration 
element seal
{
   att.global.attributes,
   att.typed.attributes,
   att.datable.attributes,
   attribute calendar { list { + } }?,
   attribute contemporary { text }?,
   ( model.pLike | decoNote )+
}⚓

2.1.167. <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
Contained by
—
May contain
core: p
msdescription: condition decoNote seal summary
Example
<sealDesc>  <seal type="pendant" contemporary="true">   <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" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="summary" minOccurs="0"/>
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <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 )+ ) )
}⚓

2.1.168. <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
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 }⚓

2.1.169. <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
Member of
model.linePart model.segLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied zone
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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="caps" type="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
}⚓

2.1.170. <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
Contained by
core: biblStruct
May contain
core: biblScope editor gap lb note pb ptr ref respStmt textLang title
figures: figure
gaiji: g
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 minOccurs="0"
  maxOccurs="unbounded">
  <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.gLike
    | title
    | model.ptrLike
    | editor
    | respStmt
    | biblScope
    | idno
    | textLang
    | model.global
    | availability
   )*
}⚓

2.1.171. <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
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.placeNamePart
Contained by
core: add addrLine address biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msIdentifier musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName place region surname
transcr: supplied
May contain
core: sic
character data
Example
<placeName>  <settlement type="town">Glasgow</settlement>  <region>Scotland</region> </placeName>
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>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element settlement { attribute calendar { list { + } }?, sic*, text }⚓

2.1.172. <sic>

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
Module core — Schema
Attributes
Member of
model.pPart.transcriptional
Contained by
core: abbr add addrLine bibl biblScope choice citedRange corr date del desc editor email expan foreign head hi l label lg measure note num orig p pubPlace publisher q quote ref reg resp street term textLang title unclear
figures: cell
header: authority catDesc change distributor edition funder handNote idno language principal scriptNote sponsor
linking: seg
msdescription: binding catchwords collection colophon condition custEvent decoNote explicit filiation finalRubric foliation height heraldry incipit locus material musicNotation objectType origDate origPlace provenance repository rubric secFol signatures source stamp summary surrogates typeNote watermark width
namesdates: addName country district forename geogFeat geogName persName placeName region settlement surname
transcr: am damage fw supplied
May contain Character data only
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>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element sic { att.global.attributes, text }⚓

2.1.173. <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
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.174. <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
Contained by
msdescription: recordHist
May contain
core: bibl sic
character data
Example
<source>Derived from <ref>Stanley (1960)</ref> </source>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="bibl" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element source { bibl+ & sic* & text }⚓

2.1.175. <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
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>
 <elementRef key="msDesc" minOccurs="1"
  maxOccurs="1"/>
</content>
    ⚓
Schema Declaration 
element sourceDesc { msDesc }⚓

2.1.176. <sponsor>

<sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]
Module header — Schema
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.respLike
Contained by
core: monogr
header: titleStmt
msdescription: msItem
May contain
core: sic
character data
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>
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>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element sponsor { attribute calendar { list { + } }?, sic*, text }⚓

2.1.177. <stamp>

<stamp> (stamp) contains a word or phrase describing a stamp or similar device. [10.3.3. Watermarks and Stamps]
Module msdescription — Schema
Attributes
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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,
   attribute calendar { list { + } }?,
   macro.phraseSeq
}⚓

2.1.178. <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
Member of
model.addrPart
Contained by
core: address
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 }⚓

2.1.179. <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
Member of
model.pPart.editorial
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
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 reason="illegible" quantity="5"    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 minOccurs="1"
  maxOccurs="unbounded">
  <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 )+
}⚓

2.1.180. <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
Contained by
msdescription: scriptDesc sealDesc typeDesc
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 }⚓

2.1.181. <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
resp (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Derived from att.global.responsibility
Status Required
Schematron
<sch:rule context="//tei:supplied/@resp"> <sch:let name="edsDoc"  value="doc('https://raw.githubusercontent.com/srophe/britishLibrary/main/documentation/editors.xml')"/> <sch:let name="eds"  value="$edsDoc//tei:text/tei:body/tei:listPerson/tei:person/@xml:id | $edsDoc//tei:text/tei:body/tei:listPerson/tei:org/@xml:id"/> <sch:let name="refValues"  value="for $i in $eds return concat('https://bl.syriac.uk/documentation/editors.xml#', $i)"/> <sch:assert test="every $i in . satisfies $i = $refValues"> Acceptable values for this @resp attribute include: <sch:value-of select="string-join($refValues, ' | ')"/>. </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
reason one 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
model.pPart.transcriptional
Contained by
core: add addrLine biblScope corr del editor email foreign l lg num orig p publisher q quote reg street term title unclear
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent finalRubric foliation heraldry incipit musicNotation objectType rubric secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName persName placeName region surname
transcr: am supplied
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.source.attribute.source,
   attribute resp { list { + } },
   attribute reason { list { + } }?,
   macro.paraContent
}⚓

2.1.182. <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
Contained by
msdescription: supportDesc
May contain
msdescription: material
Example
<objectDesc form="roll">  <supportDesc>   <support> Parchment roll with <material>silk</material> ribbons.   </support>  </supportDesc> </objectDesc>
Content model 
<content>
 <elementRef key="material" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element support { material+ }⚓

2.1.183. <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
material The material composing the support
Status Required
Datatype teidata.word
Legal values are:
chart
The object is composed of any kind of paper. Give more details, if any, in a child <support> element.
mixed
The object is composed of a combination of paper and parchment. The nature of the combination should be specified in the <support> element.
perg
The object is composed of parchment or vellum
unknown
The material of which is object is composed is not known.
Contained by
msdescription: objectDesc
May contain
core: p
header: extent
msdescription: collation condition foliation support
Example
<supportDesc>  <support> Parchment roll with <material>silk</material> ribbons.  </support> </supportDesc>
Schematron
<sch:rule see="https://msdesc.github.io/consolidated-tei-schema/msdesc.html#supportdesc"  context="//tei:sourceDesc/tei:msDesc[not(tei:msPart)]"> <sch:assert test="tei:physDesc/tei:objectDesc/tei:supportDesc[@material]"  role="warn"> 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 test=" tei:physDesc/tei:objectDesc/tei:supportDesc[@material] or ancestor::tei:msDesc/tei:physDesc/tei:objectDesc/tei:supportDesc[@material] "  role="warn"> 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 minOccurs="1" maxOccurs="1">
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="support" minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="foliation"
    minOccurs="0" maxOccurs="unbounded"/>
   <elementRef key="collation"
    minOccurs="0"/>
   <elementRef key="condition"
    minOccurs="0"/>
  </sequence>
 </alternate>
</content>
    ⚓
Schema Declaration 
element supportDesc
{
   attribute material { "chart" | "mixed" | "perg" | "unknown" },
   ( model.pLike+ | ( support?, extent?, foliation*, collation?, condition? ) )
}⚓

2.1.184. <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
attachment describes 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
flipping indicates whether the surface is attached and folded in such a way as to provide two writing surfaces
Status Optional
Datatype teidata.truthValue
Contained by
transcr: facsimile surface surfaceGrp zone
May contain
core: desc gap graphic label lb note pb
figures: figure formula
transcr: fw surface surfaceGrp zone
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 ulx="0" uly="0" lrx="200" lry="300">   <graphic url="Bovelles-49r.png"/>  </surface> </facsimile>
Content model 
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.graphicLike"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <alternate>
    <elementRef key="zone"/>
    <elementRef key="line"/>
    <elementRef key="path"/>
    <elementRef key="surface"/>
    <elementRef key="surfaceGrp"/>
   </alternate>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    ⚓
Schema Declaration 
element surface
{
   att.global.attributes,
   att.coordinated.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   attribute attachment { text }?,
   attribute flipping { text }?,
   (
      ( model.global | model.labelLike | model.graphicLike )*,
      ( ( zone | line | path | surface | surfaceGrp ), model.global* )*
   )
}⚓

2.1.185. <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
Contained by
transcr: facsimile surface surfaceGrp
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 ulx="0" uly="0" lrx="200"    lry="300">    <graphic url="Bovelles-49r.png"/>   </surface>   <surface ulx="0" uly="0" lrx="200"    lry="300">    <graphic url="Bovelles-49v.png"/>   </surface>  </surfaceGrp> </sourceDoc>
Content model 
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <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 )+
}⚓

2.1.186. <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
Member of
model.persNamePart
Contained by
core: add addrLine address biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.187. <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
Contained by
—
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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>
Content model 
<content>
 <macroRef key="macro.specialPara"/>
</content>
    ⚓
Schema Declaration 
element surrogates { att.global.attributes, macro.specialPara }⚓

2.1.188. <table>

<table> (table) contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables]
Module figures — Schema
Attributes
rows (rows) indicates the number of rows in the table.
Status Optional
Datatype teidata.count
Note

If no number is supplied, an application must calculate the number of rows.

Rows should be presented from top to bottom.
cols (columns) indicates the number of columns in each row of the table.
Status Optional
Datatype teidata.count
Note

If no number is supplied, an application must calculate the number of columns.

Within each row, columns should be presented left to right.
Member of
model.listLike
Contained by
core: add corr del l note orig p q quote reg unclear
figures: figDesc figure
header: scriptNote
linking: seg
msdescription: condition custEvent foliation musicNotation signatures summary surrogates typeNote
textstructure: div
transcr: supplied
May contain
core: gap graphic head lb note pb
figures: figure formula row
transcr: fw
Note

Contains an optional heading and a series of rows.

Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.
Example
<table rows="4" cols="4">  <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>  <row role="label">   <cell role="data"/>   <cell role="data">Dossing Cribs or Lodging Houses</cell>   <cell role="data">Beds</cell>   <cell role="data">Needys or Nightly Lodgers</cell>  </row>  <row role="data">   <cell role="label">Bury St Edmund's</cell>   <cell role="data">5</cell>   <cell role="data">8</cell>   <cell role="data">128</cell>  </row>  <row role="data">   <cell role="label">Thetford</cell>   <cell role="data">3</cell>   <cell role="data">6</cell>   <cell role="data">36</cell>  </row>  <row role="data">   <cell role="label">Attleboro'</cell>   <cell role="data">3</cell>   <cell role="data">5</cell>   <cell role="data">20</cell>  </row>  <row role="data">   <cell role="label">Wymondham</cell>   <cell role="data">1</cell>   <cell role="data">11</cell>   <cell role="data">22</cell>  </row> </table>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.headLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="1" maxOccurs="1">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="row"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.graphicLike"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    ⚓
Schema Declaration 
element table
{
   attribute rows { text }?,
   attribute cols { text }?,
   (
      ( model.headLike | model.global )*,
      ( ( row, model.global* )+ | ( model.graphicLike, model.global* )+ ),
      ( model.divBottom, model.global* )*
   )
}⚓

2.1.189. <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
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
Contained by
header: classDecl
May contain
core: bibl
header: category
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>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="bibl" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="category" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element taxonomy
{
   att.global.attribute.n,
   att.global.attribute.xmllang,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.global.source.attribute.source,
   attribute xml:id { text },
   ( bibl, category+ )
}⚓

2.1.190. <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
Contained by
textstructure: TEI
May contain
header: encodingDesc fileDesc profileDesc revisionDesc
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"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="revisionDesc"
   minOccurs="0"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element teiHeader
{
   att.global.attributes,
   ( fileDesc, model.teiHeaderPart*, revisionDesc? )
}⚓

2.1.191. <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
Member of
model.emphLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 xml:id="TDPV1" rend="sc">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="#TDPV2" rend="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#TDPV2" rend="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
}⚓

2.1.192. <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
Member of
model.resource
Contained by
textstructure: TEI
May contain
textstructure: body
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>
 <elementRef key="body" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    ⚓
Schema Declaration 
element text
{
   att.global.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   att.written.attributes,
   body+
}⚓

2.1.193. <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
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>
 <elementRef key="keywords" minOccurs="1"
  maxOccurs="1"/>
</content>
    ⚓
Schema Declaration 
element textClass { keywords }⚓

2.1.194. <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
mainLang (main language) supplies a code which identifies the chief language used in the bibliographic work.
Status Required
Schematron
<sch:rule context="//tei:textLang/@mainLang"> <sch:let name="langIdents"  value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/> <sch:assert test=". = $langIdents"> Attribute value must match one of the following language codes in the <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>. </sch:assert> </sch:rule>
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
model.msItemPart
Contained by
core: analytic monogr series
msdescription: msContents msItem msItemStruct
May contain
core: sic
character data
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="en" otherLangs="la"> Predominantly in English with Latin glosses</textLang>
Schematron
<sch:rule context="//tei:msItem"> <sch:assert 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) ) "  role="warn"> 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 test="@mainLang and string-length(normalize-space(string())) gt 0"  role="error"> 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>
Content model 
<content>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element textLang
{
   attribute mainLang { text },
   attribute otherLangs { list { * } }?,
   sic*,
   text
}⚓

2.1.195. <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
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Schematron
<sch:rule context="//tei:title/@xml:lang"> <sch:let name="langIdents"  value="//tei:profileDesc/tei:langUsage/tei:language/@ident"/> <sch:assert test=". = $langIdents"> Attribute value must match one of the following language codes in the <profileDesc>: <sch:value-of select="string-join($langIdents, ' | ')"/>. </sch:assert> </sch:rule>
Datatype teidata.language
resp (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Derived from att.global.responsibility
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type classifies the title according to some convenient typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Sample values include:
main
main title
sub
(subordinate) subtitle, title of part
alt
(alternate) alternate title, often in another language, by which the work is also known
short
abbreviated form of title
desc
(descriptive) descriptive paraphrase of the work functioning as a title
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.
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.
Derived from att.canonical
Status Optional
Schematron
<sch:rule context="//tei:title/@ref"> <sch:assert test="matches(., 'http://syriaca.org/work/\d{1,5}$')"> The value of @ref must be a Syriaca.org work URI, "http://syriaca.org/work/" followed by 1-5 digits. Please confirm that this URI matches the correct work record. </sch:assert> </sch:rule>
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecated will be removed on 2024-11-11
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>
level indicates 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
model.emphLike model.msQuoteLike
Contained by
core: add addrLine analytic bibl biblScope corr del desc editor email l monogr note num orig p publisher q quote reg series street term unclear
figures: figDesc
header: distributor scriptNote titleStmt
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution msItem msItemStruct musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: choice foreign quote sic
msdescription: locus
transcr: supplied
character data
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>
Schematron
<sch:rule context="tei:msItem/tei:title"> <sch:assert test="@xml:lang"> This <title> element must have an @xml:lang attribute. </sch:assert> </sch:rule>
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>
Content model 
<content>
 <sequence minOccurs="1" maxOccurs="1"
  preserveOrder="false">
  <elementRef key="choice" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="foreign" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="locus" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="quote" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="sic" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="supplied" minOccurs="0"
   maxOccurs="unbounded"/>
  <textNode/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element title
{
   att.global.attribute.xmlid,
   att.global.attribute.n,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.rendition.attribute.style,
   att.global.rendition.attribute.rendition,
   att.global.linking.attribute.corresp,
   att.global.linking.attribute.synch,
   att.global.linking.attribute.sameAs,
   att.global.linking.attribute.copyOf,
   att.global.linking.attribute.next,
   att.global.linking.attribute.prev,
   att.global.linking.attribute.exclude,
   att.global.linking.attribute.select,
   att.global.facs.attribute.facs,
   att.global.change.attribute.change,
   att.global.responsibility.attribute.cert,
   att.global.source.attribute.source,
   att.typed.attribute.subtype,
   attribute xml:lang { text }?,
   attribute resp { list { + } }?,
   attribute type { text }?,
   attribute ref { list { + } }?,
   attribute calendar { list { + } }?,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   ( choice* & foreign* & locus* & quote* & sic* & supplied* & text )
}⚓

2.1.196. <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
Contained by
header: fileDesc
May contain
core: editor respStmt title
header: funder principal sponsor
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 minOccurs="1" maxOccurs="1"
  preserveOrder="true">
  <elementRef key="title" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="sponsor" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="funder" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="principal" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="editor" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="respStmt" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    ⚓
Schema Declaration 
element titleStmt { title+, sponsor+, funder+, principal+, editor+, respStmt+ }⚓

2.1.197. <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
Contained by
—
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" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="typeNote" minOccurs="1"
    maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    ⚓
Schema Declaration 
element typeDesc
{
   att.global.attributes,
   ( model.pLike+ | ( summary?, typeNote+ ) )
}⚓

2.1.198. <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
Contained by
msdescription: typeDesc
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig p pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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
}⚓

2.1.199. <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
reason indicates 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.
agent Where 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
model.linePart model.pPart.transcriptional
Contained by
core: add addrLine biblScope corr del editor email l lg num orig p publisher q quote reg street term unclear
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: am supplied zone
May contain
core: abbr add address bibl biblStruct choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula table
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName listRelation persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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"
         )+
      }
   }?,
   attribute agent { text }?,
   macro.paraContent
}⚓

2.1.200. <watermark>

<watermark> (watermark) contains a word or phrase describing a watermark or similar device. [10.3.3. Watermarks and Stamps]
Module msdescription — Schema
Attributes
Member of
model.pPart.msdesc
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: abbr add address choice cit corr date del email expan foreign gap graphic hi lb measure name note num orig pb ptr q quote ref reg sic term title unclear
figures: figure formula
gaiji: g
header: idno
linking: seg
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName country district forename geo geogFeat geogName persName placeName region settlement surname
tagdocs: gi
transcr: am damage ex fw subst supplied
character data
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 }⚓

2.1.201. <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
Member of
model.measureLike
Contained by
core: add addrLine biblScope corr del editor email l num orig p publisher q quote reg street term unclear
figures: figDesc
header: distributor scriptNote
linking: seg
msdescription: catchwords condition custEvent dimensions foliation heraldry institution musicNotation objectType secFol signatures stamp summary surrogates typeNote watermark
namesdates: addName district forename geogFeat geogName region surname
transcr: supplied
May contain
core: sic
character data
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>
 <elementRef key="sic" minOccurs="0"
  maxOccurs="unbounded"/>
 <textNode/>
</content>
    ⚓
Schema Declaration 
element width { att.global.attributes, att.dimensions.attributes, sic*, text }⚓

2.1.202. <zone>

<zone> defines any two-dimensional area within a <surface> element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Module transcr — Schema
Attributes
rotate indicates 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
model.linePart
Contained by
transcr: surface zone
May contain
core: add choice del gap graphic hi lb note pb q unclear
figures: figure formula
gaiji: g
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 ulx="14.54" uly="16.14" lrx="0"  lry="0">  <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 [[undefined PH-surfzone]].
Example
<facsimile>  <surface ulx="50" uly="20" lrx="400"   lry="280">   <zone ulx="0" uly="0" lrx="500" lry="321">    <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 minOccurs="0"
  maxOccurs="unbounded">
  <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 { text }?,
   (
      text
    | model.gLike
    | model.graphicLike
    | model.global
    | surface
    | model.linePart
   )*
}⚓

2.2. Model classes

2.2.1. 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
address
Members model.nameLike[model.nameLike.agent[name persName] model.offsetLike[geogFeat] model.persNamePart[addName forename surname] model.placeStateLike[model.placeNamePart[country district geogName placeName region settlement]] idno] addrLine postCode street

2.2.2. model.addressLike

model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]
Module tei — Schema
Used by
model.pPart.data
Members address email

2.2.3. 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
cit macro.phraseSeq model.inter
Members model.quoteLike[cit quote]

2.2.4. model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]
Module tei — Schema
Used by
cit model.inter model.msItemPart model.personPart place relatedItem
Members bibl biblStruct listBibl msDesc

2.2.5. model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Module tei — Schema
Used by
div figure
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 listRelation table] model.oddDecl model.stageLike] 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.

2.2.6. model.dateLike

model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 13.4. Dates]
Module tei — Schema
Used by
imprint model.pPart.data
Members date

2.2.7. model.descLike

model.descLike groups elements which contain a description of their function.
Module tei — Schema
Used by
glyph graphic
Members desc

2.2.8. 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
div figure lg table
Members model.divBottomPart model.divWrapper

2.2.9. model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Module tei — Schema
Used by
div
Members div

2.2.10. model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Module tei — Schema
Used by
macro.specialPara model.common
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.

2.2.11. 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
div lg
Members model.divTopPart[model.headLike[head]] model.divWrapper

2.2.12. 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
model.divTop
Members model.headLike[head]

2.2.13. 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
model.highlighted model.limitedPhrase
Members foreign term title

2.2.14. model.gLike

model.gLike groups elements used to represent individual non-Unicode characters or glyphs.
Module tei — Schema
Used by
am l locus macro.phraseSeq macro.specialPara macro.xtext model.paraPart msName series zone
Members g

2.2.15. 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
address cit div figure imprint l lg macro.phraseSeq macro.phraseSeq.limited macro.specialPara model.paraPart msItem person series surface surfaceGrp table zone
Members model.global.edit[gap] model.global.meta model.milestoneLike[fw lb pb] model.noteLike[note] figure

2.2.16. 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
model.global
Members gap

2.2.17. 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
cit facsimile figure formula glyph model.phrase surface table zone
Members formula graphic

2.2.18. 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
figure model.divTopPart msDesc msFrag msPart place table
Members head

2.2.19. 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
formula locus model.highlighted model.limitedPhrase model.linePart
Members hi q

2.2.20. model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
Module tei — Schema
Used by
model.phrase
Members model.emphLike[foreign term title] model.hiLike[hi q]

2.2.21. model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]
Module tei — Schema
Used by
imprint
Members biblScope distributor pubPlace publisher

2.2.22. 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
l macro.limitedContent macro.specialPara model.common model.paraPart
Members model.attributable[model.quoteLike[cit quote]] model.biblLike[bibl biblStruct listBibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list listRelation table] model.oddDecl model.stageLike

2.2.23. model.lLike

model.lLike groups elements representing metrical components such as verse lines.
Module tei — Schema
Used by
lg model.divPart model.paraPart
Members l

2.2.24. model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Module tei — Schema
Used by
lg model.inter place surface
Members desc label

2.2.26. 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
zone
Members model.hiLike[hi q] add choice damage del seg unclear zone

2.2.27. model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Module tei — Schema
Used by
model.inter
Members list listRelation table

2.2.28. 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
model.pPart.data
Members depth dim geo height measure num width

2.2.29. 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
model.global subst
Members fw lb pb

2.2.30. model.msItemPart

model.msItemPart groups elements which can appear within a manuscript item description.
Module tei — Schema
Used by
msItem
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

2.2.31. 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
model.msItemPart
Members colophon explicit finalRubric incipit rubric title

2.2.32. model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Module tei — Schema
Used by
model.addrPart model.pPart.data
Members model.nameLike.agent[name 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.

2.2.33. 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
model.nameLike
Members name persName
Note

This class is used in the content model of elements which reference names of people or organizations.

2.2.34. model.noteLike

model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]
Module tei — Schema
Used by
biblStruct glyph model.global monogr msItemStruct place
Members note

2.2.35. 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
model.nameLike
Members geogFeat

2.2.36. model.pLike

model.pLike groups paragraph-like elements.
Module tei — Schema
Used by
custodialHist model.divPart msDesc msFrag msItem msItemStruct msPart person place projectDesc scriptDesc seal sealDesc supportDesc typeDesc
Members p

2.2.38. 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
model.phrase
Members model.pPart.editorial[abbr am choice ex expan subst] model.pPart.transcriptional[add corr damage del orig reg sic supplied unclear]

2.2.39. 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
model.limitedPhrase model.pPart.edit
Members abbr am choice ex expan subst

2.2.40. model.pPart.msdesc

model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. Manuscript Description]
Module tei — Schema
Used by
model.limitedPhrase model.phrase
Members catchwords dimensions heraldry locus locusGrp material objectType origDate origPlace secFol signatures stamp watermark

2.2.41. 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
am lg model.pPart.edit
Members add corr damage del orig reg sic supplied unclear

2.2.43. model.persNamePart

model.persNamePart groups elements which form part of a personal name. [13.2.1. Personal Names]
Module namesdates — Schema
Used by
model.nameLike
Members addName forename surname

2.2.44. model.persStateLike

model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
Module tei — Schema
Used by
model.personPart
Members persName
Note

These characteristics of an individual are typically a consequence of their own action or that of others.

2.2.45. model.personPart

model.personPart groups elements which form part of the description of a person. [15.2.2. The Participant Description]
Module tei — Schema
Used by
person
Members model.biblLike[bibl biblStruct listBibl msDesc] model.eventLike model.persStateLike[persName] idno name

2.2.47. model.phrase.xml

model.phrase.xml groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values [22. Documentation Elements]
Module tei — Schema
Used by
model.limitedPhrase model.phrase
Members gi

2.2.48. model.placeLike

model.placeLike groups elements used to provide information about places and their relationships.
Module tei — Schema
Used by
place
Members place

2.2.49. model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]
Module tei — Schema
Used by
model.placeStateLike msIdentifier
Members country district geogName placeName region settlement

2.2.50. model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Module tei — Schema
Used by
model.nameLike place
Members model.placeNamePart[country district geogName placeName region settlement]

2.2.51. 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
analytic biblStruct cit model.limitedPhrase model.phrase monogr relatedItem series
Members ptr ref

2.2.52. model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Module tei — Schema
Used by
model.attributable model.msItemPart
Members cit quote

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

2.2.54. 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
model.msItemPart
Members author editor funder principal respStmt sponsor

2.2.55. 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
model.phrase
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.

2.2.56. model.teiHeaderPart

model.teiHeaderPart groups high level elements which may appear more than once in a TEI header.
Module tei — Schema
Used by
teiHeader
Members encodingDesc profileDesc

2.2.57. 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
msItem
Members graphic

2.3. Attribute classes

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

2.3.2. 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 ptr 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.

2.3.3. att.calendarSystem

att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 13.4. Dates]
Module tei — Schema
Members date origDate
Attributes
calendar indicates 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="#julian"  when="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 declares the calendar system used to interpret the textual content of an element, as it appears on an original source. It does not modify the interpretation of the normalization attributes provided by att.datable.w3c, att.datable.iso, or att.datable.custom. Attributes from those first two classes are always interpreted as Gregorian or proleptic Gregorian dates, as per the respective standards on which they are based. The calender system used to interpret the last (att.datable.custom) may be specified with datingMethod.

2.3.4. 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 surname] author district editor geogFeat geogName institution region] distributor name objectType origPlace persName placeName publisher relation term title
Attributes
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.
Example In this contrived example, a canonical reference to the same organisation is provided in four different ways.
<author n="1">  <name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="2">  <name ref="nzvn:427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="3">  <name ref="./named_entities.xml#o427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="4">  <name key="name-427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>
The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection, but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire external system for key resolution be available.
Note

The key attribute is more flexible and general-purpose, but its use in interchange requires that documentation about how the key is to be resolved be sent to the recipient of the TEI document. In contrast values of the ref attribute are resolved using the widely accepted protocols for a URI, and thus less documentation, if any, is likely required by the recipient in data interchange.

These guidelines provide no semantic basis or suggested precedence when both key and ref are provided. For this reason simultaneous use of both is not recommended unless documentation explaining the use is provided, probably in an ODD customizaiton, for interchange.

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

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

2.3.7. 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 custEvent date district foliation geogFeat geogName origDate region seal stamp
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
period supplies pointers to one or more definitions of named periods of time (typically <category>s, <date>s or <event>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.

2.3.8. 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[custEvent date district foliation geogFeat geogName origDate region seal stamp]
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 xml:id="FIRE1"  datingMethod="#julian"  from-custom="1666-09-02"  to-custom="1666-09-05">  <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 when-custom="1598"  calendar="#julian"  datingMethod="#julian">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 when="1382-06-28"  when-custom="6890-06-20"  datingMethod="#creationOfWorld"> μηνὶ Ἰουνίου εἰς <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.

2.3.9. 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[custEvent date district foliation geogFeat geogName origDate region seal stamp]
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 when-iso="2007-06-01" dur-iso="P8D"/>
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.

2.3.10. 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[custEvent date district foliation geogFeat geogName origDate region seal stamp] change
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="#julian"  when="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 test="($bothdates and $fd gt $td) or ($bothyears and $fy gt $ty)"  role="error"> 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 test="@notBefore|@notAfter|@from|@to"  role="nonfatal">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 test="@notBefore"  role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@to]"> <sch:report test="@notAfter"  role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule>
Example
<date from="1863-05-28" to="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.

2.3.11. 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] category
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 name="POS"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">   <symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"    value="NN"/>  </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 [[undefined FS]].
<fs>  <f name="POS" fVal="#commonNoun"/> <!-- ... --> </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 xml:id="commonNoun" value="NN"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <symbol xml:id="properNoun" value="NP"   datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... --> </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="ccr" matchPattern="pos"   replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <prefixDef ident="ccr" matchPattern="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 the <equiv> element that is a child of <elementSpec> or <attDef>.
Example The <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.
<encodingDesc> <!-- ... -->  <classDecl> <!-- ... -->   <taxonomy xml:id="UD-SYN"    datcat="https://universaldependencies.org/u/dep/index.html">    <desc>     <term>UD syntactic relations</term>    </desc>    <category xml:id="acl"     valueDatcat="https://universaldependencies.org/u/dep/acl.html">     <catDesc>      <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>    </category>    <category xml:id="acl_relcl"     valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html">     <catDesc>      <term>acl:relcl</term>: relative clause modifier</catDesc>    </category>    <category xml:id="advcl"     valueDatcat="https://universaldependencies.org/u/dep/advcl.html">     <catDesc>      <term>advcl</term>: Adverbial clause modifier</catDesc>    </category> <!-- ... -->   </taxonomy>  </classDecl> </encodingDesc>
The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly.
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 value="NN"     datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>    <symbol value="NP"     datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... -->   </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.
Example The att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.
<!-- in the dictionary header --><encodingDesc>  <classDecl>   <taxonomy xml:id="domains"> <!--...-->    <category xml:id="domain.medical_and_health_sciences">     <catDesc xml:lang="en">Medical and Health Sciences</catDesc>     <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>     <category xml:id="domain.medical_and_health_sciences.medicine"      valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025">      <catDesc xml:lang="en">       <term>Medicine</term>       <gloss> <!--...-->       </gloss>      </catDesc>      <catDesc xml:lang="pt">       <term>Medicina</term>       <gloss> <!--...-->       </gloss>      </catDesc>     </category>    </category> <!--...-->   </taxonomy>  </classDecl> </encodingDesc> <!-- inside an <entry> element: --> <usg type="domain"  valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg>
In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH).
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 (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.

2.3.12. 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 bibl biblStruct projectDesc
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.

2.3.13. 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 div facsimile geo graphic lg 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.

2.3.14. att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Module tei — Schema
Members att.damaged[damage] add del depth dim dimensions ex gap geogFeat height subst unclear width
Attributes
unit names 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
quantity specifies the length in the units specified
Status Optional
Datatype teidata.numeric
extent indicates 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"/>
precision characterizes the precision of the values specified by the other attributes.
Status Optional
Datatype teidata.certainty
scope where 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.

2.3.15. 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
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]
sample indicates 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]

2.3.16. att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Module tei — Schema
Members bibl biblStruct 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 when="2010-10-21"   status="published"/>  <change when="2010-10-02" status="cleared"/>  <change when="2010-08-02"   status="embargoed"/>  <change when="2010-05-01" status="frozen"   who="#MSM"/>  <change when="2010-03-01" status="draft"   who="#LB"/> </revisionDesc>

2.3.17. 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 geogFeat geogName origDate origPlace persName person place placeName reg 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.

2.3.18. 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 n="411" edRef="#stapledon1968"/>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 n="291" edRef="#stapledon1937"/>sciousness;</p>

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

2.3.20. 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 add addName addrLine address am analytic bibl biblScope biblStruct catchwords category charDecl cit colophon corr custEvent custodialHist depth dim distributor district div edition editor email ex explicit facsimile figDesc figure finalRubric foreign forename formula g geo geogFeat geogName gi glyph graphic handNote heraldry imprint incipit institution item l lb lg locusGrp mapping monogr msDesc msFrag msItem msItemStruct msName msPart musicNotation name note num objectType orig origPlace pb persName person place placeName postCode projectDesc publisher q quote reg region relatedItem rubric scriptDesc scriptNote seal sealDesc secFol seg series sic signatures stamp street subst summary supplied surface surfaceGrp surname surrogates taxonomy teiHeader term text title typeDesc typeNote unclear watermark width zone
Attributes
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 https://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:base provides 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-05"      to="1794-04-06">5-6 April, 1794</date>.    </ref>   </bibl>  </listBibl> </div>
xml:space signals 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.

2.3.21. 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 add addName addrLine address am analytic bibl biblScope biblStruct catchwords category charDecl cit colophon corr custEvent custodialHist depth dim distributor district div edition editor email ex explicit facsimile figDesc figure finalRubric foreign forename formula g geo geogFeat geogName gi glyph graphic handNote heraldry imprint incipit institution item l lb lg locusGrp mapping monogr msDesc msFrag msItem msItemStruct msName msPart musicNotation name note num objectType orig origPlace pb persName person place placeName postCode projectDesc publisher q quote reg region relatedItem rubric scriptDesc scriptNote seal sealDesc secFol seg series sic signatures stamp street subst summary supplied surface surfaceGrp surname surrogates taxonomy teiHeader term text title typeDesc typeNote unclear watermark width zone]
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

2.3.23. 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 add addName addrLine address am analytic bibl biblScope biblStruct catchwords category charDecl cit colophon corr custEvent custodialHist depth dim distributor district div edition editor email ex explicit facsimile figDesc figure finalRubric foreign forename formula g geo geogFeat geogName gi glyph graphic handNote heraldry imprint incipit institution item l lb lg locusGrp mapping monogr msDesc msFrag msItem msItemStruct msName msPart musicNotation name note num objectType orig origPlace pb persName person place placeName postCode projectDesc publisher q quote reg region relatedItem rubric scriptDesc scriptNote seal sealDesc secFol seg series sic signatures stamp street subst summary supplied surface surfaceGrp surname surrogates taxonomy teiHeader term text title typeDesc typeNote unclear watermark width zone]
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-t1"   xml: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-t2"   xml:lang="en">   <body xml:id="t1-g1-t2-body1"    corresp="#t1-g1-t1-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 <text>s, 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 xml:id="LOND1"  corresp="people.xml#LOND2 people.xml#GENI1">  <placeName>London</placeName>  <desc>The city of London...</desc> </place> <!-- In a literary personography called "people.xml" --> <person xml:id="LOND2"  corresp="places.xml#LOND1 #GENI1">  <persName type="lit">London</persName>  <note>   <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>  </note> </person> <person xml:id="GENI1"  corresp="places.xml#LOND1 #LOND2">  <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.

2.3.24. 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 add addName addrLine address am analytic bibl biblScope biblStruct catchwords category charDecl cit colophon corr custEvent custodialHist depth dim distributor district div edition editor email ex explicit facsimile figDesc figure finalRubric foreign forename formula g geo geogFeat geogName gi glyph graphic handNote heraldry imprint incipit institution item l lb lg locusGrp mapping monogr msDesc msFrag msItem msItemStruct msName msPart musicNotation name note num objectType orig origPlace pb persName person place placeName postCode projectDesc publisher q quote reg region relatedItem rubric scriptDesc scriptNote seal sealDesc secFol seg series sic signatures stamp street subst summary supplied surface surfaceGrp surname surrogates taxonomy teiHeader term text title typeDesc typeNote unclear watermark width zone]
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 xml:id="sc"  scheme="css">font-variant: small-caps</rendition> <rendition xml:id="normal"  scheme="css">font-variant: normal</rendition> <rendition xml:id="ac"  scheme="css">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.

2.3.25. 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 add addName addrLine address am analytic bibl biblScope biblStruct catchwords category charDecl cit colophon corr custEvent custodialHist depth dim distributor district div edition editor email ex explicit facsimile figDesc figure finalRubric foreign forename formula g geo geogFeat geogName gi glyph graphic handNote heraldry imprint incipit institution item l lb lg locusGrp mapping monogr msDesc msFrag msItem msItemStruct msName msPart musicNotation name note num objectType orig origPlace pb persName person place placeName postCode projectDesc publisher q quote reg region relatedItem rubric scriptDesc scriptNote seal sealDesc secFol seg series sic signatures stamp street subst summary supplied surface surfaceGrp surname surrogates taxonomy teiHeader term text title typeDesc typeNote unclear watermark width zone] author expan
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 <respStmt>s 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 resp="#editor" cert="high">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>

2.3.26. 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 add addName addrLine address am analytic bibl biblScope biblStruct catchwords category charDecl cit colophon corr custEvent custodialHist depth dim distributor district div edition editor email ex explicit facsimile figDesc figure finalRubric foreign forename formula g geo geogFeat geogName gi glyph graphic handNote heraldry imprint incipit institution item l lb lg locusGrp mapping monogr msDesc msFrag msItem msItemStruct msName msPart musicNotation name note num objectType orig origPlace pb persName person place placeName postCode projectDesc publisher q quote reg region relatedItem rubric scriptDesc scriptNote seal sealDesc secFol seg series sic signatures stamp street subst summary supplied surface surfaceGrp surname surrogates taxonomy teiHeader term text title typeDesc typeNote unclear watermark width zone]
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="p" source="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.

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

2.3.28. 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]
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.

2.3.29. att.media

att.media provides attributes for specifying display and related properties of external media.
Module tei — Schema
Members graphic
Attributes
width Where the media are displayed, indicates the display width
Status Optional
Datatype teidata.outputMeasurement
height Where the media are displayed, indicates the display height
Status Optional
Datatype teidata.outputMeasurement
scale Where the media are displayed, indicates a scale factor to be applied when generating the desired display size
Status Optional
Datatype teidata.numeric

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

2.3.31. 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 msItem msItemStruct
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.

2.3.32. att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.7. Names and Nyms]
Module tei — Schema
Members att.personal[addName forename surname] author district editor geogFeat geogName institution region
Attributes
role may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
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.

2.3.33. att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Module tei — Schema
Members formula seg
Attributes
notation names the notation used for the content of the element.
Status Optional
Datatype teidata.enumerated

2.3.34. 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 surname
Attributes
full indicates 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

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

2.3.36. 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 licence ptr 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 xml:id="pol-swh_aln_2.1.1-ptr"   target="pol/UDHR/text.xml#pol_txt_1-head"   type="tuv"   targetLang="pl"/>  <ptr xml:id="pol-swh_aln_2.1.2-ptr"   target="swh/UDHR/text.xml#swh_txt_1-head"   type="tuv"   targetLang="sw"/> </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.

2.3.37. att.ranging

att.ranging provides attributes for describing numerical ranges.
Module tei — Schema
Members att.dimensions[att.damaged[damage] add del depth dim dimensions ex gap geogFeat height subst unclear width] 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="t" value="(@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 test="$bothnumbers and $fv gt $tv"  role="warn"> 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 reason="illegible"   extent="one or two letters" atLeast="1" atMost="2" unit="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" unit="USD"  commodity="currency">more than $120m</measure> in aid to Ukrainians.

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

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

2.3.40. 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 person place 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.

2.3.41. 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
Schematron The @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.

2.3.42. 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
status indicates 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.
cause documents 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

2.3.43. 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 add addName altIdentifier am bibl biblStruct change cit corr custEvent decoNote del dim dimensions district div figure finalRubric forename fw g geogFeat geogName graphic idno lb lg listRelation mapping measure msFrag msName name note num origDate pb persName place placeName ref reg region relatedItem rubric seal seg 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 .

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

2.4. Macros

2.4.1. 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
figDesc
Content model 
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
 </alternate>
</content>
    ⚓
Declaration 
macro.limitedContent = ( text | model.limitedPhrase | model.inter )*⚓

2.4.2. 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
add corr del orig p reg seg supplied unclear
Content model 
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.paraPart"/>
 </alternate>
</content>
    ⚓
Declaration 
macro.paraContent = ( text | model.paraPart )*⚓

2.4.3. 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
addName addrLine biblScope catchwords distributor district editor email forename geogFeat geogName heraldry num objectType publisher region secFol stamp street surname term watermark
Content model 
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <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 )*⚓

2.4.4. 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
institution
Content model 
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    ⚓
Declaration 
macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )*⚓

2.4.5. 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
condition custEvent foliation musicNotation q quote scriptNote signatures summary surrogates typeNote
Content model 
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <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.gLike
    | model.phrase
    | model.inter
    | model.divPart
    | model.global
   )*⚓

2.4.6. macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Module tei — Schema
Used by
depth dim ex mapping
Content model 
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
 </alternate>
</content>
    ⚓
Declaration 
macro.xtext = ( text | model.gLike )*⚓

2.5. Datatypes

2.5.1. teidata.certainty

teidata.certainty defines the range of attribute values expressing a degree of certainty.
Module tei — Schema
Used by
teidata.probCert
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.

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

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

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

2.5.5. 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
teidata.gender teidata.sex 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.

2.5.6. teidata.gender

teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character.
Module tei — Schema
Used by
Element:
Content model 
<content>
 <dataRef key="teidata.enumerated"/>
</content>
    ⚓
Declaration 
teidata.gender = teidata.enumerated⚓
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

Values for this datatype should not be used to encode morphological gender (cf. <gen>, msd as defined in att.linguistic, and 9.3.1. Information on Written and Spoken Forms).

2.5.7. 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 https://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 https://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.

2.5.8. teidata.name

teidata.name defines the range of attribute values expressed as an XML Name.
Module tei — Schema
Used by
gi 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.

2.5.9. teidata.namespace

teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.
Module tei — Schema
Used by
Content model 
<content>
 <dataRef restriction="\S+" name="anyURI"/>
</content>
    ⚓
Declaration 
teidata.namespace = xsd:anyURI { pattern = "\S+" }⚓
Note

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax

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

2.5.11. 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" width="600px"   url="http://www.tei-c.org/logos/TEI-600.jpg"/> </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.

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

2.5.13. 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 ulx="0" uly="0" lrx="400" lry="280">   <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.

2.5.14. 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 restriction="\S+" name="anyURI"/>
</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/

2.5.15. 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⚓

2.5.16. teidata.probability

teidata.probability defines the range of attribute values expressing a probability.
Module tei — Schema
Used by
teidata.probCert
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.

2.5.17. 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⚓

2.5.18. teidata.sex

teidata.sex defines the range of attribute values used to identify the sex of an organism.
Module tei — Schema
Used by
Element:
Content model 
<content>
 <dataRef key="teidata.enumerated"/>
</content>
    ⚓
Declaration 
teidata.sex = teidata.enumerated⚓
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

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

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

2.5.21. teidata.temporal.working

teidata.temporal.working defines the range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition specification, expressing a date or a date and a time within the working life of the document.
Module tei — Schema
Used by
Content model 
<content>
 <alternate>
  <dataRef name="date"
   restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
  <dataRef name="dateTime"
   restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
 </alternate>
</content>
    ⚓
Declaration 
teidata.temporal.working =
   xsd:date { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
 | xsd:dateTime { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }⚓
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.

The earliest time expressable with this datatype is 01 January 1970 (the Unix Epoch), which could be written as either 1970-01-01 or 1970-01-01T00:00:00Z.

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

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

2.5.24. teidata.unboundedCount

teidata.unboundedCount defines the range of values used for a counting number or the string unbounded for infinity.
Module tei — Schema
Used by
Content model 
<content>
 <alternate>
  <dataRef name="nonNegativeInteger"/>
  <valList type="closed">
   <valItem ident="unbounded"/>
  </valList>
 </alternate>
</content>
    ⚓
Declaration 
teidata.unboundedCount = xsd:nonNegativeInteger | ( "unbounded" )⚓

2.5.25. 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 (https://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.

2.5.26. 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}" }⚓

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

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

2.5.29. teidata.xmlName

teidata.xmlName defines attribute values which contain an XML name.
Module tei — Schema
Used by
Content model 
<content>
 <dataRef name="NCName"/>
</content>
    ⚓
Declaration 
teidata.xmlName = xsd:NCName⚓
Note

The rules defining an XML name form a part of the XML Specification.

2.5.30. 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.
Home 
Date: 1.0 (May 2024)