TEI P5 Customization and Encoding Guidelines for Greek Manuscripts in Sweden

Table of contents

1. Introduction

This TEI P5 ODD Customization for the cataloguing project Greek Manuscripts in Sweden was created by Patrik Granholm and Eva Nyström, and is released under a Creative Commons Attribution 4.0 International license.

2. Phrase-level Elements

2.1. Foreign Phrases and Words

Phrases or words in other languages than English must be tagged by adding the xml:lang attribute to the element enclosing the text, or where no other element is available with a <foreign> element and a xml:lang attribute.
The total amount paid for the two volumes was 84 <foreign xml:lang="sv">Daler kopparmynt</foreign>.
  • foreign identifies a word or phrase as belonging to some language other than that of the surrounding text.
    xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.

2.2. References to Locations within a Manuscript

References to a specific location or range within a manuscripts should ge given in a locus element with from and to attributes. When referring to a specific folio or page the from and to attributes should be used with identical values. The foliation scheme should be specified in the scheme attribute with the value folios or pages. No text is allowed inside the <locus/> element.
<locus from="119v" to="120r" scheme="folios"/>
If needed line numbers can be provided using the colon followed by the line number.
<locus from="22r:1" to="22r:10" scheme="folios"/>
For left and right flyleaves use L1r (= ir), R1r (= i'r).
<locus from="L1r" to="L2v" scheme="folios"/>
For references to the spine and covers the scheme attribute with the value other should be used. Use the abbreviations LCO (= left cover outside), LCI (= left cover inside), RCI (= right cover inside), RCO (= right cover outside).
<locus from="spine" to="spine" scheme="other"/>
In cases where it is necessary to use different values for the scheme attribute, e.g. when referring to the left or right inside covers and the flyleaves, use <locusGrp>.
<locusGrp>  <locus from="R1r" to="R2v" scheme="folios"/>  <locus from="RCI" to="RCI" scheme="other"/> </locusGrp>
  • locus/ defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references.
    from specifies the starting point of the location in a normalized form, typically a page number.
    to specifies the end-point of the location in a normalized form, typically as a page number.
    scheme identifies the foliation scheme in terms of which the location is being specified by pointing to some <foliation> element defining it, or to some other equivalent resource.
  • locusGrp groups a number of locations which together form a distinct but discontinuous item within a manuscript or manuscript part, according to a specific foliation.

2.3. Personal Names

Should be referred to the persons authority file in a <persName> element with the ref attribute. If the name is supplied the evidence attribute should be used (possible values: internal, external, or conjecture). The certainty can be indicated with the cert attribute (possible values: high, medium, low, or unknown). The role of the person referred to can be indicated in the role attribute (possible values: cataloguer, librarian, or scribe).
<persName ref="#PehAur" role="librarian" evidence="conjecture" cert="medium"/>
  • 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.
    evidence indicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
    cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
    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.

2.4. Place names

Should be referred to the places authority file in a <placeName/> element with the ref attribute, see Guidelines for places.
<placeName ref="#Bologna"/>
  • placeName/ contains an absolute or relative place name.
    ref (reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.

2.5. Technical Terms

Technical terms should be marked up using the <term> element and the type attribute.
<term type="wm_motif">Hat</term>
  • term contains a single-word, multi-word, or symbolic designation which is regarded as a technical term.
    type characterizes the element in some sense, using any convenient classification scheme or typology.

2.6. Bibliographic citations

Bibliographic citations should be made using the <bibl> element with a <ref> element referring to the bibliography authority file with the target attribute. References to the relevant pages, columns, or volume should be made using the <citedRange> element.
<note>Note that this explicit is situated at the bottom of <locus from="83v" to="83v" scheme="folios"/>, not on <locus from="91v" to="91v" scheme="folios"/> as one could have expected. Cf. <bibl>   <ref target="#Migne1857"/>   <citedRange from="118" to="118" unit="volume"/>   <citedRange from="873A" to="873A" unit="column"/>  </bibl> </note>
  • bibl (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.
  • ref (reference) defines a reference to another location, possibly modified by additional text or comment.
    target specifies the destination of the reference by supplying one or more URI References
  • citedRange (cited range) defines the range of cited content, often represented by pages or other units
    from [att.citing] specifies the starting point of the range of units indicated by the unit attribute.
    to [att.citing] specifies the end-point of the range of units indicated by the unit attribute.
    unit [att.citing] identifies the unit of information conveyed by the element, e.g. columns, pages, volume.

2.7. Notation of Greek characters

2.7.1. Greek numerals and ordinals

Greek numerals and ordinals should be noted using the <num> element in the following way: αʹ (Greek Numeral Sign, U+0374)
<num xml:lang="grc" type="cardinal" value="1">αʹ</num>
͵α (Greek Lower Numeral Sign, U+0375)
<num xml:lang="grc" type="cardinal" value="1000">͵α</num>
δου (abbreviation for τετάρτου)
<num xml:lang="grc" type="ordinal" value="4">δ<hi rend="sup">ου</hi> </num>
  • num (number) contains a number, written in any form.
    type indicates the type of numeric value.
    value supplies the value of the number in standard form.

2.7.2. Interpunction

For the Greek question mark the semicolon (U+003B ;) should be used instead of the erotimatiko (U+037E ;).

For the Greek semicolon the middle dot (U+00B7 ·) should be used instead of the Greek ano teleia (U+0387 ·).

For the Greek apostrophe the right single quotation mark (U+2019 ’) should be used instead of the apostrophe (U+0027 ') or the Greek psili (U+1FBF ᾿), cf. TLG Beta Code Manual, p. 7 and The Unicode Standard, Version 6.2, p. 200.

2.7.3. Transcription of Greek

In most cases the Greek should be normalized: the first letter of sentences and names should be capitalized, iota subscripts should be added, and abbreviations expanded. This applies for the <rubric>, <incipit>, <explicit>, and for the <quote> element when it appears within a <msItem>. However, the subscription, see 4.7.1.2.11. Colophon, and text quoted within the physical description should be transcribed as accurately as possible.

The <supplied> element should be used for editorial additions, with the reason attribute (possible values: omitted, illegible, damage, or unknown). The <ex> element should be used for expansions of abbreviations, and the <sic> element for indicating that the word has been transcribed exactly as found in the original source even though it might be erroneous or nonstandard.
<supplied reason="omitted">θ</supplied> <ex>εο</ex>ῦ τὸ δῶρ <ex>ον</ex>
  • 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.
    reason one or more words indicating why the text has had to be supplied, e.g. overbinding, faded-ink, lost-folio, omitted-in-original.
  • ex (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation.
  • sic (Latin for thus or so ) contains text reproduced although apparently incorrect or inaccurate.
Additions should be recorded using the <add> element, with the place attribute (legal values: above, below, or margin), and deletions with the <del> element.
<rubric xml:lang="grc">  <del xml:lang="grc">ἐπληρώθη τὸ τέταρτον</del>  <add place="above" xml:lang="grc">Βίτωνος Μηχανικά</add> </rubric>
  • add (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector.
    place specifies where this item is placed
  • 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.
Gaps and illegible characters should be marked with <gap/> and <unclear/>.
<gap extent="20" reason="damage" unit="mm"/> <unclear extent="60" reason="faded" unit="mm"/> ἰορδάνης ἰορδάνης ἰορδάνου <unclear xml:lang="grc" extent="30" reason="faded" unit="mm">τελ</unclear> αἰδέσιμος, ἀξιοτίμητος
  • 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.
    reason gives the reason for omission. Sample values include sampling, inaudible, irrelevant, cancelled.
    unit names the unit used for the measurement
  • unclear/ contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source.
    reason indicates why the material is hard to transcribe.
    unit names the unit used for the measurement

Line breaks should be indicated with <lb/> elements. Punctuations marks like : and + should be noted. Lower and upper case letters should be kept as they are in the manuscript.

4. Manuscript Description

The manuscript descriptions are structured around the notion of codicological units: the intellectual content, physical description, and history, where applicable, of each unit is described in separate <msPart> elements, whereas information common to all units, e.g. the binding, provenance, and bibliography, is described directly under the <msDesc> element using the following elements:
  • msIdentifier (manuscript identifier) contains the information required to identify the manuscript being described.
  • head (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc.
  • msContents (manuscript contents) describes the intellectual content of a manuscript or manuscript part, either as a series of paragraphs or as a series of structured manuscript items.
  • physDesc (physical description) contains a full physical description of a manuscript or manuscript part, optionally subdivided using more specialized elements from the model.physDescPart class.
  • history groups elements describing the full history of a manuscript or manuscript part.
  • additional groups additional information, combining bibliographic information about a manuscript, or surrogate copies of it with curatorial or administrative information.
<msDesc> <!-- Common information -->  <msPart> <!-- Codicological unit 1 -->  </msPart>  <msPart> <!-- Codicological unit 2 -->  </msPart> </msDesc>

4.1. The Manuscript Identifier

Information about the identity of the manuscripts should be given in the <msIdentifier> element using the following elements in the following order: <country>, <settlement>, <institution>, <repository>, and <idno>.

If the manuscript is known by a another name this should be recorded in a <msName> element. Former shelfmarks should be given inside an <altIdentifier> element in an <idno> element (type attribute with value former_shelfmark). If the manuscript has a reference number in other catalogues, e.g. Nestle-Aland, this should be given inside an <altIdentifier> element in an <idno> element (type attribute with value other).
<msIdentifier>  <country>Sweden</country>  <settlement>Uppsala</settlement>  <institution>Uppsala University</institution>  <repository>Uppsala University Library</repository>  <idno type="shelfmark">Gr. 28A</idno>  <msName xml:lang="la">Codex Rolambianus</msName>  <altIdentifier>   <idno type="former_shelfmark">Benzelius 2</idno>  </altIdentifier> </msIdentifier>
  • msIdentifier (manuscript identifier) contains the information required to identify the manuscript being described.
  • 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.
  • settlement contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit.
  • institution contains the name of an organization such as a university or library, with which a manuscript is identified, generally its holding institution.
  • repository contains the name of a repository within which manuscripts are stored, possibly forming part of an institution.
  • idno (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way.
    type categorizes the identifier, for example as an ISBN, Social Security number, etc.
  • msName (alternative name) contains any form of unstructured alternative name used for a manuscript, such as an ‘ocellus nominum’, or nickname.
    xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
  • altIdentifier (alternative identifier) contains an alternative or former structured identifier used for a manuscript, such as a former catalogue number.

4.2. The Heading

A brief descriptive title in English which summarizes the intellectual content of the whole manuscript should be given in the <head> element. For descriptive titles summarizing the intellectual content of each codicological see 4.7.1.1. Summary.
<head>Aelian, On Animals</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.3. Endleaves

In the <msContents> element endleaves should be listed as distinct <msItem> elements with the class attribute value left_endleaf or right_endleaf. The msItem element must contain at least a <locus/> element and a <note> element. In the note element it should be be recorded if the endleaves have content or are blank. For the guidelines on locus see 2.2. References to Locations within a Manuscript.
<msContents>  <msItem class="left_endleaf">   <locusGrp>    <locus from="LCI" to="LCI" scheme="other"/>    <locus from="L1r" to="L2v" scheme="folios"/>   </locusGrp>   <note>Blank endleaves</note>  </msItem>  <msItem class="left_endleaf">   <locus from="L3r" to="L3v" scheme="folios"/>   <note>Table of contents</note>  </msItem>  <msItem class="right_endleaf">   <locusGrp>    <locus from="R1r" to="R2v" scheme="folios"/>    <locus from="RCI" to="RCI" scheme="other"/>   </locusGrp>   <note>Blank endleaves</note>  </msItem> </msContents>
  • msContents (manuscript contents) describes the intellectual content of a manuscript or manuscript part, either as a series of paragraphs or as a series of structured manuscript items.
  • msItem (manuscript item) describes an individual work or item within the intellectual content of a manuscript or manuscript part.
    class identifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned.
  • locus/ defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references.
    from specifies the starting point of the location in a normalized form, typically a page number.
    to specifies the end-point of the location in a normalized form, typically as a page number.
    scheme identifies the foliation scheme in terms of which the location is being specified by pointing to some <foliation> element defining it, or to some other equivalent resource.
  • note contains a note or annotation.

4.4. Physical description

The physical description common to the whole manuscript should be recorded in the <physDesc> element using following elements:

  • objectDesc contains a description of the physical components making up the object which is being described.
  • handDesc (description of hands) contains a description of all the different kinds of writing used in a manuscript.
  • bindingDesc (binding description) describes the present and former bindings of a manuscript, either as a series of paragraphs or as a series of distinct <binding> elements, one for each binding of the manuscript.

4.4.1. Object Description

In the <objectDesc> element the support, extent, and collation of the endleaves should be decribed, see 4.7.2.1.1.1. Support, 4.7.2.1.1.2. Extent and 4.7.2.1.1.4. Collation. The foliation of the whole manuscript should also be recorded here, see 4.7.2.1.1.3. Foliation.
<physDesc>  <objectDesc>   <supportDesc material="paper">    <support>     <p/>    </support>    <extent>     <measure type="left_flyleaves" quantity="2"/>     <measure type="right_flyleaves" quantity="2"/>    </extent>    <foliation> <!-- ADD EXAMPLE -->    </foliation>    <collation> <!-- ADD EXAMPLE -->    </collation>   </supportDesc>  </objectDesc> </physDesc>
This structure should be used even if the manuscript contains no endleaves.
<msDesc>  <msPart> <!-- Codicological unit 1 -->  </msPart>  <msPart> <!-- Codicological unit 2 -->  </msPart> </msDesc>
  • supportDesc (support description) groups elements describing the physical support for the written part of a manuscript.
    material a short project-defined name for the material composing the majority of the support
  • support contains a description of the materials etc. which make up the physical support for the written part of a manuscript.
  • 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.
  • collation contains a description of how the leaves or bifolia are physically arranged.
  • foliation describes the numbering system or systems used to count the leaves or pages in a codex.
4.4.1.1. Extent
Give the number of folia of left and right flyleaves in the <extent> element with <measure> elements (type attribute with values left_flyleaves and right_flyleaves). The extent for each unit should be given under each respective msPart, see 4.7.2.1.1.2. Extent
<extent>  <measure type="left_flyleaves" quantity="3"/>  <measure type="right_flyleaves" quantity="3"/> </extent>

4.4.2. Description of Hands

Hands belonging to the bookblock should be described here according to 4.7.2.2. Description of Hands.

4.4.3. Binding Description

The binding should be described in one or more paragraphs inside the <bindingDesc> element. Use <term> and <material> elements where applicable. The first paragraph should contain a brief description of the binding type, the structure, cover material, etc. Give the height, width and depth of the binding in mm (with 5 mm precision) in the <dimensions> element (type attribute with value binding). A description of decorative features on the binding should be recorded in one or more <decoNote> elements. The overall condition and restaurations to the binding should be recorded in the <condition> element.
<bindingDesc>  <p>   <term>    <material>Parchment</material> cover</term> over <term>    <material>paper</material> boards</term> with gold tooling. Sewn on three supports.</p>  <p>   <dimensions type="binding">    <height quantity="230" unit="mm"/>    <width quantity="170" unit="mm"/>    <depth quantity="25" unit="mm"/>   </dimensions>  </p>  <decoNote>Gold-tooled <term>centerpiece</term> depicting the Crucifixion of Christ.</decoNote>  <condition>There is a 20 mm tear on left cover.</condition> </bindingDesc>

4.5. History

The <history> element should include information about the origin, provenance and acquisition of the manuscript. In the <origin> element specify date (<origDate>) and place (<origPlace>) with the help of internal or other evidence. Centuries should be spelled with numbers, e.g. 13th century, and further specifications inside a parentheses, e.g. 13th century (2nd half). Only the attributes notBefore, notAfter, and when should be used for <origDate>, e.g. 13th century = 1201–1300, 13th century (1st half) = 1201–1250. Record the different stages in the provenance in one or more <provenance> elements. The <acquisition> element should describe the last stage of the manuscript's history, i.e. how it was acquired by its present owners.
<history>  <origin>Probably written in the <origDate notBefore="1251" notAfter="1300">13th century (2nd half)</origDate>. Place unknown.</origin>  <provenance>At sometime the volume came to <placeName>Venice</placeName>,    where it came on the market in the <date notBefore="1692" notAfter="1694">late seventeenth century</date>.</provenance>  <acquisition>It was acquired there by <persName ref="#JohSpa"/>    , who was staying in Venice <date from="1692" to="1693">from November 1692 to February 1693 and again in October–December 1693</date>;    cf. note on <locus from="L2r" to="L2r" scheme="folios"/>: <quote xml:lang="la">Joh. Chrysostomi homiliae in Acta apost. (absque principio)      et in 14 Epist. Pauli. Codex de caetero magnae antiquitatis et aestimationis, Emptus Venetiis a J. G. Sparwenfeldt</quote>.    Donated to Uppsala University Library in <date when="1705"/>.</acquisition> </history>
  • origin contains any descriptive or other information concerning the origin of a manuscript or manuscript part.
  • provenance contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript or manuscript part, after its creation but before its acquisition.
  • acquisition contains any descriptive or other information concerning the process by which a manuscript or manuscript part entered the holding institution.

4.6. Bibliography

The bibliography of works referring to the manuscript should be recorded in the <additional> element in a <listBibl> element. Each item should be enclosed in a <bibl> element with a <ref> element referring to the bibliography authority file. The works should be listed in a chronological order, with the oldest item first.
<additional>  <listBibl>   <bibl>    <ref target="#Graux1889"/>    <citedRange unit="page" from="64" to="65"/>   </bibl>   <bibl>    <ref target="#TorallasTovar1994"/>    <citedRange unit="page" from="248" to="252"/>   </bibl>  </listBibl> </additional>
  • additional groups additional information, combining bibliographic information about a manuscript, or surrogate copies of it with curatorial or administrative information.
  • listBibl (citation list) contains a list of bibliographic citations of any kind.
  • bibl (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.
  • ref (reference) defines a reference to another location, possibly modified by additional text or comment.
    target specifies the destination of the reference by supplying one or more URI References
  • citedRange (cited range) defines the range of cited content, often represented by pages or other units
    from [att.citing] specifies the starting point of the range of units indicated by the unit attribute.
    to [att.citing] specifies the end-point of the range of units indicated by the unit attribute.
    unit [att.citing] identifies the unit of information conveyed by the element, e.g. columns, pages, volume.

4.7. Codicological Unit(s)

Each codicological unit should be described in a separate <msPart> element using the following elements:

  • msIdentifier (manuscript identifier) contains the information required to identify the manuscript being described.
  • msContents (manuscript contents) describes the intellectual content of a manuscript or manuscript part, either as a series of paragraphs or as a series of structured manuscript items.
  • physDesc (physical description) contains a full physical description of a manuscript or manuscript part, optionally subdivided using more specialized elements from the model.physDescPart class.
  • history groups elements describing the full history of a manuscript or manuscript part.
Each codicological unit should be numbered using arabic numerals inside the <idno> in the <msIdentifier> element. The value for type of the <idno> element should be codicological_unit.
<msPart>  <msIdentifier>   <idno type="codicological_unit">1</idno>  </msIdentifier> </msPart>

4.7.1. Intellectual Content

The intellectual content of the codicological unit should be listed in the <msContents> element.

4.7.1.1. Summary

Give a brief descriptive title in English in the <summary> element which summarizes the intellectual content of the codicological unit. For the descriptive title summarizing the intellectual content of the whole manuscript, see 4.2. The Heading.

  • summary contains an overview of the available information concerning some aspect of an item (for example, its intellectual content, history, layout, typography etc.) as a complement or alternative to the more detailed information carried by more specific elements.
4.7.1.2. Manuscript Item
Each item in the manuscript should be descibed in a distinct <msItem> with the class attribute identifying the text type(s) or classification(s) applicable to this item. Multiple values may be selected separated with whitespace. The values derive from the TLG Canon of Authors and Works.
<msItem class="nat_hist paradox"/>

The items should not be numbered with the n attribute. The numbering will be generated automatically in the XSLT transformation. If the manuscript item is incomplete through loss or damage use the defective attribute with value true (default value is false).

Blank pages should be recorded at the end of a <note> element, in a separate paragraph, with the <locus/> or <locusGrp> element and the text ‘is/are blank’. Pages containing short notes or scribbles by later hands should also be recorded in the <note> element with a reference to the <handNote> if possible. Table of contents may be quoted under <handNote> in <handDesc>.

4.7.1.2.1. Locus
Give the start and end folio of each item according to the guidelines specified in 2.2. References to Locations within a Manuscript. If there are several items on a single folio specify on which line the text starts and ends. For texts scattered over more than one location in the manuscript the <locusGrp> element should be used.
<locusGrp>  <locus from="178r" to="178v" scheme="folios"/>  <locus from="180r" to="180v" scheme="folios"/>  <locus from="28r" to="28r" scheme="folios"/> </locusGrp>
4.7.1.2.2. Text Language
Give the text language for each <msItem> in the mainLang attribute (default value is Greek).
<textLang mainLang="grc"/>
For bilingual or multilingual texts give the other languages in the otherLangs attribute.
<textLang mainLang="grc" otherLangs="la"/>
4.7.1.2.3. Author
The author name should be recorded inside the <author> element in a <persName> element with a reference to the persons authority file, see 2.3. Personal Names. The <author> element should be omitted for anonymous works.
<author>  <persName ref="#ClaAel" evidence="external" cert="high"/> </author>
4.7.1.2.4. Title
The title should be given in Latin according to Pinakes and the type attribute should then be set with the (default) value uniform. Give the URI for the text in Pinakes in a ref attribute. A BHG or CPG reference may also be give in the key attribute. If the work is known under an alternative title, this may be given in a separate <title> element with a key attribute containing the TLG, BHG, or CPG number for the text, and the type attribute with the value alt.
<author>Aelius Aristides</author> <title ref="http://pinakes.irht.cnrs.fr/notices/oeuvre/id/7462" type="uniform" xml:lang="la">In Apellam</title> <title key="TLG0284.010" type="alt" xml:lang="gr">Ἀπελλᾶ γενεθλιακός</title>
For works not included in Pinakes a descriptive title in English should be provided and the type attribute should then be set with the value desc.
<title type="desc" xml:lang="en">Glossary to the Octateuch</title> <rubric xml:lang="gr">ἐκ τῆς ὀκτατεύχου</rubric>
4.7.1.2.5. Rubric
Rubrics should be indicated for all texts. The Greek should be normalized: the first letter of each sentence and of names should be capitalized, iota subscripts should be added, and abbreviations expanded.
<rubric xml:lang="grc">Βίτωνος κατασκευαὶ πολεμικῶν ὀργάνων καὶ καταπελτιστῶν</rubric>
If there is no rubric in the manuscript give the following value:
<rubric>None</rubric>
4.7.1.2.6. Incipit

The incipit should be given for partially or completely unedited works; for excerpts, fragments or paraphrases of edited works; for edited texts where the incipit differs from the edited version. The Greek should be normalized: the first letter of each sentence and of names should be capitalized, iota subscripts should be added, and abbreviations expanded. For mutilated incipits the defective attribute with value true should be used (default value is false). For incipits of excerpts use defective attribute with the value inapplicable.

4.7.1.2.7. Explicit

The explicit should be given for partially or completely unedited works; for excerpts, fragments or paraphrases of edited works; for edited texts where the explicit differs from the edited version. The Greek should be normalized: the first letter of each sentence and of names should be capitalized, iota subscripts should be added, and abbreviations expanded. For mutilated explicits the defective attribute with value true should be used (default value is false). For explicits of excerpts use defective attribute with the value inapplicable.

4.7.1.2.8. Final rubric
The final rubric should be given only when it differs from the rubric. The Greek should be normalized: the first letter of each sentence and of names should be capitalized, iota subscripts should be added, and abbreviations expanded.
<title ref="http://pinakes.irht.cnrs.fr/notices/oeuvre/id/2308" xml:lang="la">De Constructione Bellicarum Machinarum et Catapultarum</title> <title key="TLG 1226.001" xml:lang="grc" type="alt">Κατασκευαὶ πολεμικῶν ὀργάνων καὶ καταπαλτικῶν</title> <rubric xml:lang="grc">Βίτωνος κατασκευαὶ πολεμικῶν ὀργάνων καὶ καταπελτιστῶν</rubric> <finalRubric xml:lang="grc">Βίτωνος κατασκευαὶ πολεμικῶν ὀργάνων καὶ καταπελτικῶν</finalRubric>
4.7.1.2.9. Note
In the note element additional information about the text may be given, e.g. if the text contains anonymous scholia or glosses. Authored scholia should be recorded in a separate <msItem>.
<note> <!-- ADD EXAMPLE --> </note>
For longer texts a table of contents should be given in a <list> element with type attribute (value: toc). In this case use record each chapter/section in a separate paragraph inside a <note> element with type attribute (value: toc).
<note>  <list type="toc">   <item>    <locus from="1r" to="1r" scheme="folios"/>    <title xml:lang="la">Prooemium</title>   </item>   <item>    <locus from="1r" to="8v" scheme="folios"/>    <title xml:lang="la">Liber I</title>   </item>   <item>    <locus from="8v" to="8v" scheme="folios"/>    <title xml:lang="la">Index libri II</title>   </item>  </list> </note>
4.7.1.2.10. Quote

Quotations from the manuscripts can be given in a <quote> element for recording other bits of the text not covered by <rubric>, <incipit>, <explicit>, <finalRubric>, and <colophon>. Longer texts should be transcribed in the <text> element, see Guidelines 10.3.5.2 Linking a location to a transcription or an image. The Greek should be normalized: the first letter of each sentence and of names should be capitalized, iota subscripts should be added, and abbreviations expanded.

4.7.1.2.11. Colophon
Subscription should be given in the <colophon> element in the <msItem> element of the text to which it belongs in the manuscript. The text should be transcribed as accurately as possible using the transcription rules described at 2.7.3. Transcription of Greek. See also discussion on TEI-list.
<colophon xml:lang="grc">  <locus from="119r" to="119r" scheme="folios"/>  <supplied xml:lang="grc" reason="omitted">θ</supplied>  <ex xml:lang="grc">ε</ex>ῷ χάρις :· <supplied xml:lang="grc" reason="omitted">κ</supplied>ε<ex xml:lang="grc">φάλαι</ex>α ἅπαντα <num xml:lang="grc" type="cardinal" value="606">χϛʹ</num> : +<lb/> </colophon>
  • colophon contains the colophon of a manuscript item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript.
4.7.1.2.12. Filiation

Information about the relationship of the present manuscript to other surviving manuscripts of the same text should be recorded in the <filiation> element and type attribute with the value protograph, apograph or antigraph (indirect exemplar). Quoted manuscripts would be enclosed in <idno> elements with a type attribute (value ms_ref).

If the present manuscript is referred to with a siglum in editions and articles, this should be mentioned in a separate <filiation> element and type attribute with the value siglum. Full references to these editions and articles should be given in the <additional> element.
<filiation type="protograph">  <idno type="ms_ref">Codex Vaticanus Palatinus Graecus 267</idno> (15th cent.), cf. <bibl>   <ref target="#DeStefani1902"/>   <citedRange from="209" to="210" unit="page"/>  </bibl> , <bibl>   <ref target="#GarcíaValdés2009"/>   <citedRange from="viii" to="viii" unit="page"/>  </bibl> </filiation> <filiation type="siglum">U ( <bibl>   <ref target="#DeStefani1902"/>  </bibl>, <bibl>   <ref target="#GarcíaValdés2009"/>  </bibl> )</filiation>
4.7.1.2.13. Editions
The standard edition should be enclosed in a <bibl> element with a <ref> element referring to the bibliography authority file. References to the relevant pages/columns of the edition should be made using the <citedRange> element. When listing multiple editions use the <listBibl> element. If the text is found in Patrologia Graeca (PG) this should be listed first.
<listBibl>  <bibl>   <ref target="#Marsden1971"/>   <citedRange from="66" to="103" unit="page"/>  </bibl>  <bibl>   <ref target="#Rehm1929"/>  </bibl> </listBibl>
  • bibl (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.
  • listBibl (citation list) contains a list of bibliographic citations of any kind.
  • ref (reference) defines a reference to another location, possibly modified by additional text or comment.
    target specifies the destination of the reference by supplying one or more URI References
  • citedRange (cited range) defines the range of cited content, often represented by pages or other units
    from [att.citing] specifies the starting point of the range of units indicated by the unit attribute.
    to [att.citing] specifies the end-point of the range of units indicated by the unit attribute.
    unit [att.citing] identifies the unit of information conveyed by the element, e.g. columns, pages, volume.

4.7.2. Physical Description

The Physical Description may contain the following elements:

  • objectDesc contains a description of the physical components making up the object which is being described.
  • handDesc (description of hands) contains a description of all the different kinds of writing used in a manuscript.
  • musicNotation contains description of type of musical notation.
  • decoDesc (decoration description) contains a description of the decoration of a manuscript, either as a sequence of paragraphs, or as a sequence of topically organized <decoNote> elements.
  • bindingDesc (binding description) describes the present and former bindings of a manuscript, either as a series of paragraphs or as a series of distinct <binding> elements, one for each binding of the manuscript.
4.7.2.1. Object Description

The <objectDesc> element should contain the follwing elements:

  • supportDesc (support description) groups elements describing the physical support for the written part of a manuscript.
  • layoutDesc (layout description) collects the set of layout descriptions applicable to a manuscript.
4.7.2.1.1. Support Description

The <supportDesc> element should contain the following elements:

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

The support material for the codicological unit(s) should be recorded in the material attribute (values: paper, parchment or mixed) but not for the bookblock. Further description of the support should be added in the <support> element.

4.7.2.1.1.1. Support

For each kind of support material record the extent inside a paragraph, with the <locus/> element. Specify the support material in a <material> element. (values: Western paper, Western paper without watermark, Arabic paper, Parchment). For paper note if the folding is Folio, Quarto or Octavo in a <measure> element with the type attribute (value: folding). Give the height and width of the leaves in mm (with 5 mm precision) in the <dimensions> element (type attribute with value leaf).

Describe each watermark in the <watermark> element, numbered with the n attribute (values: 1, 2, 3, etc.; twin marks should be numbered 1a, 1b, etc.) Each bifolium containing the watermark should be recorded in <locusGrp> elements with <locus/> elements for the front and back leaf. Describe the watermark using the <term> element with the type attribute (values: wm_motif and proximity) and the <ref> element which may contain <bibl>, <placeName/>, <date> and <persName> elements in accordance with the standard repertories. If the date is approximate use the precision attribute with the value low. If possible, give the dimensions of the watermark, chain-lines, and the number of laid-lines per 20 mm.
<support>  <p>   <locus from="14" to="24" scheme="folios"/>   <material>Western paper</material>   <measure type="folding">Quarto</measure>   <dimensions type="leaf">    <height quantity="220" unit="mm"/>    <width quantity="160" unit="mm"/>   </dimensions>   <watermark n="2a">    <locusGrp>     <locus from="15" to="15" scheme="folios"/>     <locus from="20" to="20" scheme="folios"/>    </locusGrp>    <term type="wm_motif">Hand; flower</term>    <term type="proximity">similar to</term>    <ref>     <bibl>      <ref target="#Briquet1968"/>      <citedRange>Main 10720</citedRange>     </bibl>     <placeName ref="#Perpignan"/>     <date when="1528"/>    </ref>    <dimensions type="chain-lines">     <width quantity="38" unit="mm"/>    </dimensions>    <measure type="laid-lines_in_20mm" quantity="22" unit="lines"/>   </watermark>   <watermark n="2b">    <locusGrp>     <locus from="23" to="23" scheme="folios"/>     <locus from="24" to="24" scheme="folios"/>    </locusGrp>    <term type="wm_motif">Hand; flower</term>    <dimensions type="chain-lines">     <width quantity="38" unit="mm"/>    </dimensions>    <measure type="laid-lines_in_20mm" quantity="22" unit="lines"/>   </watermark>   <watermark n="3">    <locusGrp>     <locus from="17" to="17" scheme="folios"/>     <locus from="18" to="18" scheme="folios"/>    </locusGrp>    <term type="wm_motif">Hand; flower</term>    <term type="proximity">similar to</term>    <ref>     <bibl>      <ref target="#Piccard1997"/>      <citedRange>Hand V, 1571</citedRange>     </bibl>     <placeName ref="#Madrid"/>     <date when="1541"/>    </ref>    <dimensions type="chain-lines">     <width quantity="39" unit="mm"/>    </dimensions>    <measure type="laid-lines_in_20mm" quantity="22" unit="lines"/>   </watermark>  </p> </support>
4.7.2.1.1.2. Extent
Give the number of folia of the codicological unit in the <extent> element in a <measure> element (type attribute with value textblock_leaves). The extent of flyleaves should be given under the bookblock part, see 4.4.1.1. Extent.
<extent>  <measure type="textblock_leaves" quantity="128"/> </extent>
4.7.2.1.1.3. Foliation
The foliation should be recorded in the <foliation> element. If the manuscript consists of multiple codicological units give the foliation formula in the <physDesc> common to the whole manuscript 4.3. Endleaves. Use the <term> element when describing the foliation (suggested choices: "foliation", "pagination", "in pencil", "in ink", "modern hand", "by the scribe")
<foliation>  <term>foliation</term>  <term>in pencil</term> by a <term>modern hand</term>: <supplied reason="omitted">i–iii</supplied>, I–III, 1–34, 34a, 35–46, 47bis, 48–123, <supplied reason="omitted">i´–iii´</supplied>. Older foliation <term>in ink</term> on every tenth leaf. </foliation>
4.7.2.1.1.4. Collation

Describe the quires according to Andrist et al. (2013) 150–169 in a <formula> element inside the <collation> element. Quire numbers should be given in subscript (<hi> element with the rend attribute and value sub), e.g. Q1–3. Use Roman numerals to indicate the number of bifolia in the quire (I = singulion, II = binion, III = ternion, IV = quaternion, etc.). Quires with the same number of bifolia should be grouped together and numbered, e.g. 4.IV = 4 quires containing quaternions. The last folio in the quire or group of quires should be given in superscript (<hi> element with rend attribute and value super). There should be no space between f. (or p.) and the number, cf. Andrist (2007) 28 n. 48. Added leaves should be recorded with +1 and the folio reference in superscript. Missing leaves should be recorded with -1, the term post, and a folio reference to the folio preceding the missing leaf. If the first leaf of a quire is missing use the term ante to indicate its place.

Example: Q1–22.IIf.8 + Q3(III+1f.11+1f.15)f.16 + Q4IIIf.22 + Q5(III+1f.26)f.29 + Q6–94.IVf.61 + Q10(V-1post f.64)f.70 + Q11IVf.78

(Endleaves are described in the 4.3. Endleaves and should not be included here.)

Record the quire signatures in the <signatures> element using relevant <term> elements (possible choices: "lower left margin", "lower center margin", "lower right margin", "upper left margin", "upper center margin", "upper right margin", "last verso", "first recto", "none"). If only a few are visible, record these with <num> and <locus/> elements.

Record the catchwords in the <catchwords> element using relevant <term> elements (possible choices: "horizontal", "vertical", "lower left margin", "lower center margin", "lower right margin", "upper left margin", "upper center margin", "upper right margin", "last verso", "first recto", "none").
<collation>  <formula>   <hi rend="sub">Q1–6</hi>6.VIII<hi rend="super">f.96</hi> + <hi rend="sub">Q7</hi>IX<hi rend="super">f.114</hi> + <hi rend="sub">Q8</hi>III<hi rend="super">f.120</hi>  </formula>  <p>In Q7 <locus from="105" to="106" scheme="folios"/> are loose.</p>  <signatures>In the <term>lower left margin</term> of the <term>last verso</term>, mostly trimmed, but the following are visible:  <num xml:lang="grc" type="cardinal" value="2">βʹ</num>   <locus from="8v" to="8v" scheme="folios"/>   <num xml:lang="grc" type="cardinal" value="6">Ϛʹ</num>   <locus from="37v" to="37v" scheme="folios"/>   <num xml:lang="grc" type="cardinal" value="7">ζʹ</num>   <locus from="45v" to="45v" scheme="folios"/>  </signatures>  <catchwords>   <term>vertical</term>, in the <term>lower right margin</term> of the <term>last verso</term>.</catchwords> </collation>
4.7.2.1.2. Layout Description
Give the number of columns and ruled lines in the <layout> element using the columns and ruledLines attributes (or the writtenLines attribute for unruled manuscripts). The writtenLines can be added also in the description of ruled manuscripts, especially when this number differs from the number of ruled lines. If the number of ruled lines varies give the minimum and maximum values with whitespace in-between. Give the extent in the <locus/> element and use the <term> elements to specify patterns in accordance with Leroy-Sautel where applicable. Give the height and width of the writing area in mm (with 5 mm precision) in the <dimensions> element (type attribute with value written).
<layoutDesc>  <layout columns="1" ruledLines="20" writtenLines="38 39">   <locus from="1r" to="91v" scheme="folios"/>   <term type="layout">ruling pattern</term>   <term type="proximity">identical with</term>   <bibl>    <ref target="#Sautel1995"/>    <citedRange unit="number" from="20D1" to="20D1"/>   </bibl>   <dimensions type="written">    <height min="185" max="190" unit="mm"/>    <width min="125" max="130" unit="mm"/>   </dimensions>  </layout>  <layout column="1" ruledLines="20 24" writtenLines="38 44">   <locus from="121r" to="140v" scheme="folios"/>   <term type="layout">ruling pattern</term>   <term type="proximity">not clear</term>   <dimensions type="written">    <height quantity="145" unit="mm"/>    <width quantity="80" unit="mm"/>   </dimensions>  </layout> </layoutDesc>
If the layout shows great variation and cannot be expressed using the columns, ruledLines or writtenLines attributes, give a prose description in a <note> element instead.
<layoutDesc>  <layout columns="2" writtenLines="24 52">   <locus from="29r" to="30v" scheme="folios"/>   <dimensions type="written">    <height quantity="165" unit="mm"/>    <width quantity="115" unit="mm"/>   </dimensions>   <note>Main text always 24 lines per page. In the commentary surrounding the main text there around twice as many lines per page.</note>  </layout>  <layout>   <locusGrp>    <locus from="25r" to="26r" scheme="folios"/>    <locus from="28r" to="28v" scheme="folios"/>   </locusGrp>   <note>Layout and number of lines varying.</note>  </layout> </layoutDesc>
4.7.2.2. Description of Hands
Each distinct hand should be described in a separate <handNote> element in the <handDesc> element. Give the extent for this hand in a <locus/> or <locusGrp> element. Where the scribe is identifiable, either from the writing or a subscription, give the name (according to Repertorium der Griechischen Kopisten or other relevant authority files, e.g. VIAF) in a <persName> element using a ref attribute pointing to the persons authority file, and the role attribute with value scribe. Specify the certainty of the attribution in the cert attribute (values: high, middle, low, unknown) and the evidence for this in the evidence attribute (values: internal, external, conjecture).
<handDesc>  <handNote>   <locus from="1r" to="119r" scheme="folios"/>   <persName ref="#MicSou" role="scribe" cert="high" evidence="internal"/> based on subscription <locus from="119r" to="119r" scheme="folios"/>. Numerous <foreign xml:lang="grc">σημείωσαι</foreign> and <foreign xml:lang="grc">ὡραῖον</foreign> references in the margins, sometimes partly cut out.  </handNote>  <handNote>   <locus from="1r" to="119r" scheme="folios"/>    Chapter divisions in Latin by unknown hand.  </handNote> </handDesc>
For unidentified hands describe the script and, if possible, classify it using the <term> element with the type attribute (value: script). Minor notes which cannot be attributed to a scribe should be summarized in an separate <handNote> element with a few <locus/> as examples.
<handDesc>  <handNote>   <locus from="1r" to="223v" scheme="folios"/>    Slightly right-sloping <term type="script">minuscule</term>, <term type="script" xml:lang="de">Perlschrift</term>. Rubrics in <term type="script" xml:lang="de">alexandrinischer Auszeichnungsmajuskel</term>.  </handNote>  <handNote>Occasional <term>notes</term> and <term>pen trials</term> by later hands, e.g. <locus from="10r" to="10r" scheme="folios"/>, <locus from="18v" to="18v" scheme="folios"/>, <locus from="193r" to="193r" scheme="folios"/>.  </handNote> </handDesc>
  • handDesc (description of hands) contains a description of all the different kinds of writing used in a manuscript.
  • handNote (note on hand) describes a particular style or hand distinguished within a manuscript.
  • locus/ defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references.
    from specifies the starting point of the location in a normalized form, typically a page number.
    to specifies the end-point of the location in a normalized form, typically as a page number.
    scheme identifies the foliation scheme in terms of which the location is being specified by pointing to some <foliation> element defining it, or to some other equivalent resource.
  • locusGrp groups a number of locations which together form a distinct but discontinuous item within a manuscript or manuscript part, according to a specific foliation.
  • term contains a single-word, multi-word, or symbolic designation which is regarded as a technical term.
    type characterizes the element in some sense, using any convenient classification scheme or typology.
4.7.2.3. Musical Notation
Musical notation should be described in the <musicNotation> element with a <locus/> element.
<locus from="1r" to="8v" scheme="folios"/> <musicNotation>Byzantine musical notation in <term>black and red ink</term>.</musicNotation>
4.7.2.4. Description of the Decoration
Describe the decoration in one or more paragraphs in the <decoDesc> element. Noteworthy features may be listed in <term> elements and exemplified with references in <locus/> or <locusGrp> elements.
<decoDesc>  <p>Rubrics and initials in <term>red ink</term>, some <term>zoomorphic initials</term>, e.g.  <locusGrp>    <locus from="10r" to="10r" scheme="folios"/>    <locus from="25r" to="25r" scheme="folios"/>   </locusGrp>.  <term>Headpieces</term> with <term>interlace pattern</term> in <term>red and black ink</term>   <locus from="1r" to="1r" scheme="folios"/>.  </p> </decoDesc>
4.7.2.5. Additions

Marginalia, notes, and other additions of interest should be recorded in the <additions> element.

4.7.3.

5. Works cited in the Guidelines

  1. Patrick Andrist, Règles de catalogage (Bern 2007)
  2. Patrick Andrist et al., La syntaxe du codex : essai de codicologie structural (Turnhout 2013)

Appendix A Schema

Appendix A.1 Elements

Appendix A.1.1 <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, containing a single TEI header, a single text, one or more members of the model.resourceLike class, or a combination of these. A series of <TEI> elements may be combined together to form a <teiCorpus> element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Module textstructure — Schema
Attributes Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype 
xsd:ID
version specifies the major version number of the TEI Guidelines against which this document is valid.
Status Required
Datatype 
                                                                    data.version
Legal values are:
5.0
TEI P5
Note The major version number is historically prefixed by a P (for Proposal), and is distinct from the version number used for individual releases of the Guidelines, as used by (for example) the source of the <schemaSpec> element. The current version is P5.
Contained by
—
May contain
header: teiHeader
textstructure: text
transcr: facsimile
Declaration 
element TEI
{
   attribute xml:id { xsd:ID },
   attribute version { "5.0" },
   teiHeader,
   text?,
   facsimile
}
Schematron
<s:ns prefix="tei" uri="http://www.tei-c.org/ns/1.0"/> <s:ns prefix="xs" uri="http://www.w3.org/2001/XMLSchema"/>
Schematron
<s:ns prefix="rng" uri="http://relaxng.org/ns/structure/1.0"/>
Example
<TEI version="5.0" xml:id="uub-gr-027" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader xml:lang="en">   <fileDesc>    <titleStmt> <!-- Title information -->    </titleStmt>    <publicationStmt> <!-- Information about the publication -->    </publicationStmt>    <sourceDesc> <!-- The MS description -->    </sourceDesc>   </fileDesc>   <revisionDesc> <!-- Revision history -->   </revisionDesc>  </teiHeader>  <text> <!-- Optional text -->  </text>  <facsimile> <!-- Image information -->  </facsimile> </TEI>
Note This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute.

Appendix A.1.2 <acquisition>

<acquisition> contains any descriptive or other information concerning the process by which a manuscript or manuscript part entered the holding institution. [10.8. History]
Module msdescription — Schema
Contained by
msdescription: history
May contain
core: date foreign quote
header: idno
msdescription: locus
namesdates: persName placeName
Declaration 
element acquisition
{
   (
      text
    | date*
    | foreign*
    | idno*
    | locus*
    | persName*
    | placeName*
    | quote*
   )*
}
Example
<acquisition>It was acquired there by <persName ref="#JohSpa"/>, who was staying in Venice <date from="1692" to="1693"> from November 1692 to February 1693 and again in    October–December 1693</date>; cf. note on <locus from="L2r" to="L2r" scheme="folios"/>: <quote xml:lang="la">Joh. Chrysostomi homiliae    in Acta apost. (absque principio) et in 14 Epist. Pauli. Codex de caetero magnae antiquitatis et    aestimationis, Emptus Venetiis a J. G. Sparwenfeldt</quote>. Donated to Uppsala University Library in <date when="1705"/>.</acquisition>

Appendix A.1.3 <add>

<add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]
Module core — Schema
Attributes 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
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
place specifies where this item is placed
Derived from att.placement
Status Required
Datatype 1–∞ occurrences of 
                                                                    data.enumerated
separated by whitespace
Legal values are:
above
below
margin
Member of
model.pPart.transcriptional
Contained by
msdescription: additions rubric
May contain Character data only
Declaration 
element add
{
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   attribute place { list { ( "above" | "below" | "margin" )+ } },
   text
}
Example
<rubric xml:lang="grc">  <del xml:lang="grc">ἐπληρώθη τὸ τέταρτον</del>  <add place="above" xml:lang="grc">Βίτωνος Μηχανικά</add> </rubric>
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.

Appendix A.1.4 <additional>

<additional> groups additional information, combining bibliographic information about a manuscript, or surrogate copies of it with curatorial or administrative information. [10.9. Additional Information]
Module msdescription — Schema
Contained by
msdescription: msDesc
May contain
core: listBibl
Declaration 
element additional { listBibl }
Example
<additional>  <listBibl>   <bibl>    <ref target="#Aurivillius1806"/>    <citedRange unit="page" from="12" to="14"/>   </bibl>   <bibl>    <ref target="#DeStefani1902"/>    <citedRange unit="page" from="209" to="210"/>   </bibl>   <bibl>    <ref target="#Lampros1907"/>    <citedRange unit="page" from="492" to="492"/>   </bibl>  </listBibl> </additional>

Appendix A.1.5 <additions>

<additions> contains a description of any significant additions found within a manuscript, such as marginalia or other annotations. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Attributes Attributes  att.global (@xml:id, @n, @xml:lang) (att.global.rendition (@rend)) (att.global.facs (@facs)) (att.global.responsibility (@cert))
Contained by
msdescription: physDesc
May contain
core: add bibl date del desc foreign gap graphic hi lb list listBibl measure note num p quote ref sic term title unclear
figures: formula
header: idno
msdescription: catchwords depth dimensions height locus locusGrp material msDesc origDate origPlace signatures watermark width
namesdates: country persName placeName settlement
transcr: ex supplied
Declaration 
element additions { att.global.attributes, macro.specialPara }
Example
<additions>  <p>There are several marginalia in this manuscript. Some consist of    single characters and others are figurative. On 8v is to be found a drawing of    a mans head wearing a hat. At times sentences occurs: On 5v:  <q xml:lang="is">Her er skrif andres isslendin</q>,    on 19r: <q xml:lang="is">þeim go</q>,    on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad      batar þad mælgi ok mal</q>,    On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p> </additions>

Appendix A.1.6 <altIdentifier>

<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript, such as a former catalogue number. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Contained by
msdescription: msIdentifier
May contain
header: idno
Declaration 
element altIdentifier { idno }
Example
<altIdentifier>  <idno type="former_shelfmark">Sparwenfeldt 42</idno> </altIdentifier>

Appendix A.1.7 <author>

<author> in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Module core — Schema
Contained by
msdescription: msItem
May contain
namesdates: persName
Declaration 
element author { persName }
Example
<author>  <persName ref="#ClaAel" evidence="external" cert="high"/> </author>

Appendix A.1.8 <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
header: publicationStmt
May contain Character data only
Legal values are:
Uppsala University Library
Declaration 
element authority { text }
Example
<publicationStmt>  <authority>Uppsala University Library</authority>  <pubPlace>Uppsala</pubPlace> </publicationStmt>

Appendix A.1.9 <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 Attributes
status supplies a code identifying the current availability of the text.
Status Required
Datatype 
                                                                    data.enumerated
Legal values are:
free
Contained by
header: publicationStmt
May contain
header: licence
Declaration 
element availability { attribute status { "free" }, licence }
Example
<publicationStmt>  <authority>Uppsala University Library</authority>  <pubPlace>Uppsala</pubPlace>  <date when="2014"/>  <availability status="free">   <licence target="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International</licence>  </availability> </publicationStmt>

Appendix A.1.10 <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core — Schema
Member of
model.biblLike
Contained by
core: listBibl note p ref
header: handNote
msdescription: additions filiation layout msItem origin provenance signatures
May contain
core: citedRange ref
Declaration 
element bibl { ref, citedRange* }
Example
<bibl>  <ref target="#DeStefani1902"/>  <citedRange from="209" to="210" unit="page"/> </bibl>

Appendix A.1.11 <bindingDesc>

<bindingDesc> (binding description) describes the present and former bindings of a manuscript, either as a series of paragraphs or as a series of distinct <binding> elements, one for each binding of the manuscript. [10.7.3.1. Binding Descriptions]
Module msdescription — Schema
Contained by
msdescription: physDesc
May contain
core: p
msdescription: condition decoNote
Declaration 
element bindingDesc { p+, decoNote?, condition? }
Example
<bindingDesc>  <p>   <term>    <material>Parchment</material> cover</term> over <term>    <material>paper</material> boards</term> with gold tooling. Sewn on three supports.</p>  <p>   <dimensions type="binding" unit="mm">    <height quantity="230"/>    <width quantity="170"/>    <depth quantity="25"/>   </dimensions>  </p>  <decoNote>Gold-tooled <term>centerpiece</term> depicting the Crucifixion of Christ.</decoNote>  <condition>There is a 20 mm tear on left cover.</condition> </bindingDesc>

Appendix A.1.12 <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
textstructure: div
Declaration 
element body { div+ }

Appendix A.1.13 <catchwords>

<catchwords> describes the system used to ensure correct ordering of the quires making up a codex or incunable, typically by means of annotations at the foot of the page. [10.3.7. Catchwords, Signatures, Secundo Folio]
Module msdescription — Schema
Member of
model.pPart.msdesc
Contained by
msdescription: additions collation
May contain
core: term
msdescription: locus
Declaration 
element catchwords { ( text | term | locus )* }
Example
<catchwords>  <term>vertical</term>, in the <term>lower right margin</term> of the <term>last verso</term>. </catchwords>

Appendix A.1.14 <change>

<change> documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.5. The Revision Description 2.4.1. Creation 11.7. Changes]
Module header — Schema
Attributes Attributes
who indicates the person, or group of people, to whom the element content is ascribed.
Derived from att.ascribed
Status Required
Datatype 1–∞ occurrences of 
                                                                    data.pointer
separated by whitespace
when supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Derived from att.datable.w3c
Status Required
Datatype 
                                                                    data.temporal.w3c
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 
                                                                    data.enumerated
Legal values are:
draft
working draft [Default]
published
published version
Contained by
header: revisionDesc
May contain Character data only
Declaration 
element change
{
   attribute who { list { data.pointer+ } },
   attribute when { data.temporal.w3c },
   attribute status { "draft" | "published" },
   text
}
Example
<revisionDesc status="draft">  <change status="draft" when="2015-01-12" who="#PG">Added facsimile</change>  <change status="draft" when="2014-06-11" who="#PG">Changes to modified ODD</change>  <change status="draft" when="2012-11-12" who="#PG">First draft</change> </revisionDesc>
Note The who attribute should point to the xml:id of the <respStmt> in the header, identifying the person responsible for the change and their role in making it. Changes should be recorded with the most recent first.

Appendix A.1.15 <citedRange>

<citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.11.2.5. Scopes and Ranges in Bibliographic Citations]
Module core — Schema
Attributes Attributes  att.citing (@unit, @from, @to)
Contained by
core: bibl
May contain Character data only
Declaration 
element citedRange { att.citing.attributes, text }
Example
<additional>  <listBibl>   <bibl>    <ref target="#Graux1889"/>    <citedRange unit="page" from="64" to="65"/>   </bibl>   <bibl>    <ref target="#TorallasTovar1994"/>    <citedRange unit="page" from="248" to="252"/>   </bibl>  </listBibl> </additional>
Note When the range cited consists of a single page or other unit, use the from and to attributes with an identical value. When no clear endpoint is given the from attribute should be used without to. For example, if the citation has ‘p. 3ff’ as a page reference.

Appendix A.1.16 <collation>

<collation> contains a description of how the leaves or bifolia are physically arranged. [10.7.1. Object Description]
Module msdescription — Schema
Contained by
msdescription: supportDesc
May contain
core: p
figures: formula
msdescription: catchwords signatures
Declaration 
element collation { ( formula?, p? )*, signatures?, catchwords? }
Schematron Check that <signatures> and <catchwords> are used in <collation> for <msPart>.
<sch:rule context="tei:msPart//tei:collation"> <sch:assert test="tei:signatures"> The signatures element must be used in collation for msPart</sch:assert> <sch:assert test="tei:catchwords"> The catchwords element must be used in collation for msPart</sch:assert></sch:rule>
Example
<collation>  <formula>   <hi rend="sub">Q1–6</hi>6.VIII<hi rend="super">f.96</hi> + <hi rend="sub">Q7</hi>IX<hi rend="super">f.114</hi> + <hi rend="sub">Q8</hi>III<hi rend="super">f.120</hi>  </formula>  <p>In Q7 <locus from="105" to="106" scheme="folios"/> are loose.</p>  <signatures>In the <term>lower left margin</term> of the <term>last verso</term>, mostly trimmed, but the following are visible:  <num xml:lang="grc" type="cardinal" value="2">βʹ</num>   <locus from="8v" to="8v" scheme="folios"/>   <num xml:lang="grc" type="cardinal" value="6">Ϛʹ</num>   <locus from="37v" to="37v" scheme="folios"/>   <num xml:lang="grc" type="cardinal" value="7">ζʹ</num>   <locus from="45v" to="45v" scheme="folios"/>  </signatures>  <catchwords>   <term>vertical</term>, in the <term>lower right margin</term> of the <term>last verso</term>.</catchwords> </collation>

Appendix A.1.17 <colophon>

<colophon> contains the colophon of a manuscript item: that is, a statement providing information regarding the date, place, agency, or reason for production of the manuscript. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes 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
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
Contained by
msdescription: msItem
May contain
core: foreign gap lb num sic unclear
msdescription: locus locusGrp
transcr: ex supplied
Declaration 
element colophon
{
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   },
   ( locus | locusGrp ),
   ( text | ex | foreign | gap | lb | num | sic | supplied | unclear )*
}
Example
<colophon xml:lang="grc">  <locus from="119r" to="119r" scheme="folios"/>  <supplied reason="omitted">θ</supplied>  <ex>εο</ex>ῦ τὸ δῶρ<ex>ον</ex>, <ex>καὶ</ex> πόνος μιχαήλου <supplied reason="omitted">ἀ</supplied>ργείου λακώνου : <supplied reason="omitted">ἐ</supplied>ν βουνωνία πόλ<ex>ει</ex>  <supplied>ἰ</supplied>ταλί<ex>ας</ex>, <supplied reason="omitted">κ</supplied>αὶ ταύτ<ex>ην</ex> ἀμυστὶ <lb/> τὴν βίβλον σὺν πολλοῖς ἄλλοις τὸν ἀριθμ<ex>ὸν</ex>· <num xml:lang="grc" type="cardinal" value="150">ρνʹ</num>· ἐξέγραψα, ὑπὲρ π<ex>ατ</ex>ρίδος καὶ γένους : + <lb/> γραφεὺς ἐλεύθερος καὶ χρημάτ<ex>ων</ex> ἀνώ<ex>τερος</ex> : </colophon>

Appendix A.1.18 <condition>

<condition> contains a description of the physical condition of the manuscript. [10.7.1.5. Condition]
Module msdescription — Schema
Contained by
msdescription: bindingDesc supportDesc
May contain
msdescription: locus locusGrp
Declaration 
element condition { ( text | locus | locusGrp )* }
Example
<condition>The spine is badly worn and damaged, the boards now being held together provisionally with the help of a slip of brown paper pasted aroung the spine. The bookblock has come loose completely. A lending slip that used to be pasted to <locus from="L1r" to="L1r" scheme="folios"/> is now unstuck.</condition>

Appendix A.1.19 <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
Member of
model.placeNamePart
Contained by
msdescription: additions msIdentifier
May contain Character data only
Declaration 
element country { text }
Example
<msIdentifier>  <country>Sweden</country>  <settlement>Uppsala</settlement>  <institution>Uppsala University</institution>  <repository>Uppsala University Library</repository>  <idno type="shelfmark">Gr. 27</idno> </msIdentifier>
Note The <country> element should only be used in <msIdentifier>. Elsewhere the <placeName/> element with the ref attribute should be used.

Appendix A.1.20 <date>

<date> contains a date in any format. [3.5.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.5. The Revision Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.3.6. Dates and Times]
Module core — Schema
Attributes Attributes  att.datable (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
Member of
model.dateLike
Contained by
core: note p ref
header: handNote publicationStmt
msdescription: acquisition additions decoNote origin provenance
May contain Character data only
Declaration 
element date { att.datable.attributes, text }
Schematron checks that the <date> element has either a when or to/from attributes, or notAfter/notBefore attributes.
<sch:pattern> <sch:rule context="tei:date">  <sch:assert test="@when or (@notAfter and @notBefore) or (@from and @to)">The date element must have either @when or @to/@from, or @notAfter/@notBefore. </sch:assert></sch:rule></sch:pattern>
Schematron checks that the <date> element is empty when using the when attribute.
<sch:rule context="tei:date[@when]"> <sch:report test="text()">The date element must be empty when using the when attribute.</sch:report></sch:rule>
Example
<date from="1767" to="1779"/>
Example
<date notBefore="1573" notAfter="1580">mid-1570s</date>

Appendix A.1.21 <decoDesc>

<decoDesc> (decoration description) contains a description of the decoration of a manuscript, either as a sequence of paragraphs, or as a sequence of topically organized <decoNote> elements. [10.7.3. Bindings, Seals, and Additional Material]
Module msdescription — Schema
Contained by
msdescription: physDesc
May contain
core: p
Declaration 
element decoDesc { p+ }
Example
<decoDesc>  <p>Very sparingly decorated. Rubricized plain initials, 1–2 lines high, passim;    larger and elaborate ones, 3 lines high, only at the beginning of new text items,    and these are still rather crude and simple in style. On <locus from="28v" to="28v" scheme="folios"/>    a headpiece with interlace pattern in red, black, and white (unfilled outline). On <locus from="57v" to="57v" scheme="folios"/>    a line filler in black and red and a simple interlace knot in the margin. Subtitles are sometimes    written in red ink but without any further embellishment.</p> </decoDesc>

Appendix A.1.22 <decoNote>

<decoNote> (note on decoration) contains a note describing either a decorative component of a manuscript, or a fairly homogenous class of such components. [10.7.3. Bindings, Seals, and Additional Material]
Module msdescription — Schema
Contained by
msdescription: bindingDesc
May contain
core: date foreign measure term
msdescription: dimensions locus locusGrp material
Declaration 
element decoNote
{
   (
      text
    | date
    | dimensions
    | foreign
    | locus
    | locusGrp
    | material
    | measure
    | term
   )*
}
Example
<decoNote>Gold-tooled <term>centerpiece</term> depicting the Crucifixion of Christ.</decoNote>

Appendix A.1.23 <del>

<del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions]
Module core — Schema
Attributes 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
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
Member of
model.pPart.transcriptional
Contained by
msdescription: additions rubric
May contain Character data only
Declaration 
element del
{
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   text
}
Example
<rubric xml:lang="grc">  <del xml:lang="grc">ἐπληρώθη τὸ τέταρτον</del>  <add place="above" xml:lang="grc">Βίτωνος Μηχανικά</add> </rubric>
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.

Appendix A.1.24 <depth/>

<depth/> contains a measurement measured across the spine of a book or codex, or (for other text-bearing objects) perpendicular to the measurement given by the ‘width’ element. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes Attributes
unit names the unit used for the measurement
Derived from att.dimensions
Status Required
Datatype 
                                                                    data.enumerated
Legal values are:
mm
quantity specifies the length in the units specified
Derived from att.dimensions
Status Optional
Datatype 
                                                                    data.numeric
min where the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Derived from att.ranging
Status Optional
Datatype 
                                                                    data.numeric
max where the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Derived from att.ranging
Status Optional
Datatype 
                                                                    data.numeric
Member of
model.measureLike
Contained by
msdescription: additions dimensions
May contain Empty element
Declaration 
element depth
{
   attribute unit { "mm" },
   attribute quantity { data.numeric }?,
   attribute min { data.numeric }?,
   attribute max { data.numeric }?,
   empty
}
Schematron checks that the <depth/> element has either a quantity or min/max attributes.
<sch:pattern> <sch:rule context="tei:depth">  <sch:assert test="@quantity or (@min and @max)">The depth element must have either @quantity or @min/@max. </sch:assert></sch:rule></sch:pattern>
Example
<dimensions type="binding">  <height quantity="240" unit="mm"/>  <width quantity="185" unit="mm"/>  <depth quantity="65" unit="mm"/> </dimensions>

Appendix A.1.25 <desc>

<desc> (description) contains a brief description of the object documented by its parent element, including its intended usage, purpose, or application where this is appropriate. [22.4.1. Description of Components]
Module core — Schema
Member of
model.labelLike
Contained by
msdescription: additions
transcr: surface
May contain Character data only
Declaration 
element desc { text }
Example
<facsimile>  <surface xml:id="uub-gr-021-0001r">   <desc>f. 1r</desc>   <graphic url="alvin-record_94105-ATTACHMENT-0005.ptif"/>  </surface> </facsimile>
Note TEI convention requires that this be expressed as a finite clause, begining with an active verb.

Appendix A.1.26 <dimensions>

<dimensions> contains a dimensional specification. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes Attributes
type indicates which aspect of the object is being measured.
Status Required
Datatype 
                                                                    data.enumerated
Legal values are:
binding
chain-lines
leaf
wm
written
Member of
model.pPart.msdesc
Contained by
core: p
msdescription: additions decoNote layout watermark
May contain
msdescription: depth height width
Declaration 
element dimensions
{
   attribute type { "binding" | "chain-lines" | "leaf" | "wm" | "written" },
   ( height?, width?, depth? )
}
Schematron
<s:report test="count(tei:width)> 1">The element <s:name/> may appear once only </s:report> <s:report test="count(tei:height)> 1">The element <s:name/> may appear once only </s:report> <s:report test="count(tei:depth)> 1">The element <s:name/> may appear once only </s:report>
Example
<dimensions type="binding">  <height quantity="240" unit="mm"/>  <width quantity="185" unit="mm"/>  <depth quantity="65" unit="mm"/> </dimensions>
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.

Appendix A.1.27 <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 Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Optional
Datatype 
xsd:ID
Contained by
textstructure: body
May contain
core: head p
Declaration 
element div { attribute xml:id { xsd:ID }?, head, p+ }
Example
<text>  <body>   <div xml:id="text_65b">    <head>     <title>65b: Chronicon breve</title>     <locus scheme="folios" from="283v" to="283v"/>    </head>    <p xml:lang="grc">ὁ ἔννατος ὁ σουλ<lb/>τα Παγιάζητη <lb/>ὃς ἐπῆρε τη Μεθωκορωνι.    <lb/>δέκατος υἱός του <lb/>ὁ Σελημης ὃς εδουλεσε <lb/>Περσια και Σι<lb/>ρια ὃλη.    <lb/>δέκατος πρῶτος <lb/>υἱός του ὁ Σουλεημαν <lb/>σούλτανος ὁς ἐπηραι    <lb/>τὴν Ροδο καὶ ἑαλοσι <lb/>καὶ τὴν Οὐγκρία το <lb/>α φ κ ϛ ετος ἀπο χῦ    <lb/>ἀγουστου κθ <lb/>... ὁ πολεμος</p>   </div>  </body> </text>

Appendix A.1.28 <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 Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
Member of
model.pPart.editorial
Contained by
core: foreign quote
msdescription: additions colophon
May contain Character data only
Declaration 
element ex
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   macro.xtext
}
Example
δῶρ<ex xml:lang="grc">ον</ex>

Appendix A.1.29 <explicit>

<explicit> contains the explicit of a manuscript item, that is, the closing words of the text proper, exclusive of any rubric or colophon which might follow it. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes 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
Datatype 
                                                                    data.language
Legal values are:
grc
Greek should be normalized: the first letter of each sentence and of names should be capitalized, iota subscripts should be added, and abbreviations expanded.
la
defective indicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
Derived from att.msExcerpt
Status Required
Datatype 
                                                                    data.xTruthValue
Default false
Contained by
msdescription: msItem
May contain
core: foreign gap sic unclear
transcr: supplied
Declaration 
element explicit
{
   attribute xml:lang { "grc" | "la" },
   attribute defective { data.xTruthValue },
   ( text | foreign | gap | supplied | sic | unclear )*
}
Example
<explicit xml:lang="grc" defective="false">ὡς τῶν μελαίνων, τὰ μὲν ψυχρά, τὰ δὲ τερμά</explicit>

Appendix A.1.30 <extent>

<extent> describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]
Module header — Schema
Contained by
msdescription: supportDesc
May contain
core: measure
Declaration 
element extent { measure+ }
Schematron checks that <extent> only contains <measure> with type value textblock_leaves for the codicological unit, and values left_flyleaves and right_flyleaves for the bookblock.
<sch:pattern> <sch:rule context="tei:msPart/tei:physDesc/tei:objectDesc/tei:supportDesc/tei:extent">  <sch:assert test="tei:measure[@type='textblock_leaves']">    Only the extent of the unit should be recorded here. The extent of the flyleaves should be recorded in the bookblock part.</sch:assert></sch:rule> <sch:rule context="tei:msDesc/tei:physDesc/tei:objectDesc/tei:supportDesc/tei:extent">  <sch:assert test="tei:measure[@type='left_flyleaves'][following-sibling::tei:measure[@type='right_flyleaves']]">    Both the left and right flyleaves should be recorded here, even if there are none.</sch:assert>  <sch:report test="tei:measure[@type='textblock_leaves']">    Only the extent of the flyleaves should be recorded here. The extent of the textblock should be recorded under respective msPart.</sch:report></sch:rule></sch:pattern>
Example
<extent>  <measure type="left_flyleaves" quantity="0" unit="folios"/>  <measure type="right_flyleaves" quantity="2" unit="folios"/> </extent>

Appendix A.1.31 <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
Contained by
textstructure: TEI
May contain
transcr: surface
Declaration 
element facsimile { surface+ }
Example
<facsimile>  <surface xml:id="UGr-027-1r">   <desc>f. 1r</desc>   <graphic url="UGr-027-0003.jp2"/>  </surface>  <surface xml:id="UGr-027-1v">   <desc>f. 1v</desc>   <graphic url="UGr-027-0004.jp2"/>  </surface> </facsimile>

Appendix A.1.32 <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: publicationStmt sourceDesc titleStmt
Declaration 
element fileDesc { titleStmt, publicationStmt, sourceDesc }
Example
<fileDesc>  <titleStmt/>  <publicationStmt/>  <sourceDesc/> </fileDesc>

Appendix A.1.33 <filiation>

<filiation> contains information concerning the manuscript's filiation, i.e. its relationship to other surviving manuscripts of the same text, its protographs, antigraphs and apographs. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype 
                                                                    data.enumerated
Legal values are:
siglum
protograph
apograph
antigraph
Contained by
msdescription: msItem
May contain
core: bibl foreign quote
header: idno
Declaration 
element filiation
{
   attribute type { "siglum" | "protograph" | "apograph" | "antigraph" }?,
   ( text | bibl | foreign | idno | quote )*
}
Example
<filiation type="protograph">  <idno type="ms_ref">Codex Vaticanus Palatinus Graecus 267</idno> (15th cent.), cf. <bibl>   <ref target="#DeStefani1902"/>   <citedRange from="209" to="210" unit="page"/>  </bibl> , <bibl>   <ref target="#GarcíaValdés2009"/>   <citedRange from="viii" to="viii" unit="page"/>  </bibl> </filiation> <filiation type="siglum">U ( <bibl>   <ref target="#DeStefani1902"/>  </bibl>, <bibl>   <ref target="#GarcíaValdés2009"/>  </bibl> )</filiation>

Appendix A.1.34 <finalRubric>

<finalRubric> contains the string of words that denotes the end of a text division, often with an assertion as to its author and title, usually set off from the text itself by red ink, by a different size or type of script, or by some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes 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
Datatype 
                                                                    data.language
Legal values are:
grc
Greek should be normalized: the first letter of each sentence and of names should be capitalized, iota subscripts should be added, and abbreviations expanded.
la
Contained by
msdescription: msItem
May contain
core: foreign gap sic unclear
transcr: supplied
Declaration 
element finalRubric
{
   attribute xml:lang { "grc" | "la" },
   ( text | foreign | gap | supplied | sic | unclear )*
}
Example
<finalRubric xml:lang="grc">Βίτωνος κατασκευαὶ πολεμικῶν ὀργάνων καὶ καταπελτικῶν</finalRubric>

Appendix A.1.35 <foliation>

<foliation> describes the numbering system or systems used to count the leaves or pages in a codex. [10.7.1.4. Foliation]
Module msdescription — Schema
Contained by
msdescription: supportDesc
May contain
core: foreign num term
msdescription: locus locusGrp
namesdates: persName
transcr: supplied
Declaration 
element foliation
{
   ( text | foreign | locus | locusGrp | num | persName | supplied | term )*
}
Example
<foliation>  <term>Foliation</term>  <term>in pencil</term> by a <term>modern hand</term> in the <term>lower right margin</term>: 1–220. <term>Pagination</term>  <term>in ink</term> in the <term>upper right margin</term>of recto pages: 1–439. </foliation>

Appendix A.1.36 <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 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
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
Member of
model.emphLike
Contained by
core: note p
header: handNote
msdescription: acquisition additions colophon decoNote explicit filiation finalRubric foliation incipit origin provenance
May contain
core: lb unclear
transcr: ex
Declaration 
element foreign
{
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   },
   ( text | ex* | lb* | unclear* )*
}
Example
The total amount paid for the two volumes was 84 <foreign xml:lang="sv">Daler kopparmynt</foreign>.
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.

Appendix A.1.37 <formula>

<formula> contains a mathematical or other formula. [14.2. Formulæ and Mathematical Expressions]
Module figures — Schema
Member of
model.graphicLike
Contained by
msdescription: additions collation
May contain
core: hi
Declaration 
element formula { ( text | hi )* }
Example
<formula>  <hi rend="sub">Q1–6</hi>6.VIII<hi rend="super">f.96</hi> + <hi rend="sub">Q7</hi>IX<hi rend="super">f.114</hi> + <hi rend="sub">Q8</hi>III<hi rend="super">f.120</hi> </formula>

Appendix A.1.38 <gap/>

<gap/> indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.4.3. Additions, Deletions, and Omissions]
Module core — Schema
Attributes Attributes
unit names the unit used for the measurement
Derived from att.dimensions
Status Required
Datatype 
                                                                    data.enumerated
Legal values are:
chars
characters
lines
mm
quantity specifies the length in the units specified
Derived from att.dimensions
Status Required
Datatype 
                                                                    data.numeric
atLeast gives a minimum estimated value for the approximate measurement.
Derived from att.ranging
Status Optional
Datatype 
                                                                    data.numeric
atMost gives a maximum estimated value for the approximate measurement.
Derived from att.ranging
Status Optional
Datatype 
                                                                    data.numeric
reason gives the reason for omission. Sample values include sampling, inaudible, irrelevant, cancelled.
Status Required
Datatype 1–∞ occurrences of 
                                                                    data.word
separated by whitespace
Legal values are:
damage
Member of
model.global.edit
Contained by
msdescription: additions colophon explicit finalRubric incipit
May contain Empty element
Declaration 
element gap
{
   attribute unit { "chars" | "lines" | "mm" },
   attribute quantity { data.numeric },
   attribute atLeast { data.numeric }?,
   attribute atMost { data.numeric }?,
   attribute reason { list { "damage"+ } },
   empty
}
Example
<gap reason="damage" quantity="20" unit="mm"/> <unclear reason="illegible" quantity="60" unit="mm"/> ἰορδάνης ἰορδάνης ἰορδάνου τελ<unclear reason="illegible" quantity="30" unit="mm"/> αἰδέσιμος, ἀξιοτίμητος

Appendix A.1.39 <graphic/>

<graphic/> indicates the location of an inline graphic, illustration, or figure. [3.9. Graphics and Other Non-textual Components]
Module core — Schema
Attributes Attributes  att.media att.resourced (@url)
Member of
model.graphicLike
Contained by
msdescription: additions
transcr: surface
May contain Empty element
Declaration 
element graphic { att.media.attributes, att.resourced.attributes, empty }
Example
<facsimile>  <surface xml:id="UGr-027-1r">   <desc>f. 1r</desc>   <graphic url="UGr-027-0003.jp2"/>  </surface>  <surface xml:id="UGr-027-1v">   <desc>f. 1v</desc>   <graphic url="UGr-027-0004.jp2"/>  </surface> </facsimile>

Appendix A.1.40 <handDesc>

<handDesc> (description of hands) contains a description of all the different kinds of writing used in a manuscript. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Contained by
msdescription: physDesc
May contain
header: handNote
Declaration 
element handDesc { handNote+ }
Example
<handDesc>  <handNote>   <locus from="1r" to="30v" scheme="folios"/>   <persName ref="#NikMar" role="scribe" cert="low" evidence="conjecture"/>    Responsible for all the main texts, and most of the paratexts including rubricized parts, commentaries and glossae.  </handNote> </handDesc>

Appendix A.1.41 <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
Contained by
msdescription: handDesc
May contain
core: bibl date foreign quote term
header: idno
msdescription: locus locusGrp
namesdates: persName
Declaration 
element handNote
{
   ( locus | locusGrp )?,
   (
      text
    | bibl
    | date
    | foreign
    | idno
    | locus
    | locusGrp
    | term
    | persName
    | quote
   )*
}
Example
<handDesc>  <handNote>   <locus from="1r" to="30v" scheme="folios"/>   <persName ref="#NikMar" role="scribe" cert="low" evidence="conjecture"/>    Responsible for all the main texts, and most of the paratexts including rubricized parts, commentaries and glossae.  </handNote> </handDesc>

Appendix A.1.42 <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
msdescription: msDesc
textstructure: div
May contain
core: title
msdescription: locus locusGrp
Declaration 
element head { text | ( title, ( locus | locusGrp ) ) }
Example
<head>Aelian, On Animals</head>

Appendix A.1.43 <height/>

<height/> contains a measurement measured along the axis at right angles to the bottom of the written surface, i.e. parallel to the spine for a codex or book. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes Attributes
unit names the unit used for the measurement
Derived from att.dimensions
Status Required
Datatype 
                                                                    data.enumerated
Legal values are:
mm
quantity specifies the length in the units specified
Derived from att.dimensions
Status Optional
Datatype 
                                                                    data.numeric
min where the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Derived from att.ranging
Status Optional
Datatype 
                                                                    data.numeric
max where the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Derived from att.ranging
Status Optional
Datatype 
                                                                    data.numeric
Member of
model.measureLike
Contained by
msdescription: additions dimensions
May contain Empty element
Declaration 
element height
{
   attribute unit { "mm" },
   attribute quantity { data.numeric }?,
   attribute min { data.numeric }?,
   attribute max { data.numeric }?,
   empty
}
Schematron checks that the <height/> element has either a quantity or min/max attributes.
<sch:pattern> <sch:rule context="tei:height">  <sch:assert test="@quantity or (@min and @max)">The height element must have either @quantity or @min/@max. </sch:assert></sch:rule></sch:pattern>
Example
<dimensions type="binding">  <height quantity="240" unit="mm"/>  <width quantity="185" unit="mm"/>  <depth quantity="65" unit="mm"/> </dimensions>

Appendix A.1.44 <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 Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Required
Datatype 1–∞ occurrences of 
                                                                    data.word
separated by whitespace
Legal values are:
sub
subscript
super
superscript
Member of
model.hiLike
Contained by
core: num
figures: formula
msdescription: additions
May contain Character data only
Declaration 
element hi { attribute rend { list { ( "sub" | "super" )+ } }, text }
Example
<formula>  <hi rend="sub">Q1–6</hi>6.VIII<hi rend="super">f.96</hi> + <hi rend="sub">Q7</hi>IX<hi rend="super">f.114</hi> + <hi rend="sub">Q8</hi>III<hi rend="super">f.120</hi> </formula>

Appendix A.1.45 <history>

<history> groups elements describing the full history of a manuscript or manuscript part. [10.8. History]
Module msdescription — Schema
Contained by
msdescription: msDesc msPart
May contain
msdescription: acquisition origin provenance
Declaration 
element history { origin?, provenance*, acquisition? }
Example
<history>  <origin>Probably written in <origPlace ref="#Venice"/> in the <origDate notBefore="1535" notAfter="1555">1540s</origDate>.    Watermarks and the handwriting (in so-called <q xml:lang="de">Camillus-Schrift</q> style) may suggest a link to the workshop of <persName ref="#BarZan"/>.    Its present binding stems from the <date notBefore="1746" notAfter="1765">mid-eighteenth century</date>.</origin>  <provenance>The manuscript was acquired by <persName ref="#JacBjö"/> (<date from="1731" to="1779"/>),    most probably during his travels through Europe in the years <date from="1767" to="1779"/>. That it would,    as is the case with several of his other manuscripts, have its provenance in one of the Thessalian monasteries,    is perhaps less likely given its rather costly binding in silk and brocatpapier.  </provenance>  <acquisition>Came to <placeName ref="#UUL"/> in <date when="1784"/> as part of the Björnståhl donation.  </acquisition> </history>

Appendix A.1.46 <idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Module header — Schema
Attributes Attributes
type categorizes the identifier, for example as an ISBN, Social Security number, etc.
Status Required
Datatype 
                                                                    data.enumerated
Legal values are:
codicological_unit
former_shelfmark
ms_ref
shelfmark
other
Member of
model.nameLike
Contained by
core: note p
header: handNote
msdescription: acquisition additions altIdentifier filiation msIdentifier origin provenance
May contain Character data only
Declaration 
element idno
{
   attribute type
   {
      "codicological_unit"
    | "former_shelfmark"
    | "ms_ref"
    | "shelfmark"
    | "other"
   },
   text
}
Example
<msIdentifier>  <country>Sweden</country>  <settlement>Uppsala</settlement>  <institution>Uppsala University</institution>  <repository>Uppsala University Library</repository>  <idno type="shelfmark">Gr. 27</idno> </msIdentifier>

Appendix A.1.47 <incipit>

<incipit> contains the incipit of a manuscript item, that is the opening words of the text proper, exclusive of any rubric which might precede it, of sufficient length to identify the work uniquely; such incipits were, in former times, frequently used a means of reference to a work, in place of a title. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes 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
Datatype 
                                                                    data.language
Legal values are:
grc
Greek should be normalized: the first letter of each sentence and of names should be capitalized, iota subscripts should be added, and abbreviations expanded.
la
defective indicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
Derived from att.msExcerpt
Status Required
Datatype 
                                                                    data.xTruthValue
Default false
Contained by
msdescription: msItem
May contain
core: foreign gap sic unclear
transcr: supplied
Declaration 
element incipit
{
   attribute xml:lang { "grc" | "la" },
   attribute defective { data.xTruthValue },
   ( text | foreign | gap | supplied | sic | unclear )*
}
Example
<incipit xml:lang="grc" defective="false">Πᾶν πρᾶγμα ἢ διαιρετὸν ἢ ἀδιαίρετον</incipit>

Appendix A.1.48 <institution>

<institution> contains the name of an organization such as a university or library, with which a manuscript is identified, generally its holding institution. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Contained by
msdescription: msIdentifier
May contain Character data only
Legal values are:
Uppsala University
Gothenburg University
Linköping Diocesan Library
Lund University
The National Archives
The National Archives, Stockholm
The National Gallery
The National Gallery, Stockholm
Royal Library
Royal Library, Stockholm
Skokloster Castle
Declaration 
element institution { text }
Example
<msIdentifier>  <country>Sweden</country>  <settlement>Uppsala</settlement>  <institution>Uppsala University</institution>  <repository>Uppsala University Library</repository>  <idno type="shelfmark">Gr. 27</idno> </msIdentifier>

Appendix A.1.49 <item>

<item> contains one component of a list. [3.7. Lists 2.5. The Revision Description]
Module core — Schema
Contained by
core: list
May contain
core: title
msdescription: locus locusGrp
Declaration 
element item { ( locus | locusGrp ), title }
Example
<note>  <list type="toc">   <item>    <locus from="1r:4" to="1r:19" scheme="folios"/>    <title xml:lang="la">Prooemium</title>   </item>   <item>    <locus from="1r:19" to="8v:6" scheme="folios"/>    <title xml:lang="la">Liber I</title>   </item>  </list> </note>

Appendix A.1.50 <layout>

<layout> describes how text is laid out on the page, 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 Attributes
columns specifies the number of columns per page
Status Optional
Datatype 1–2 occurrences of 
                                                                    data.count
separated by whitespace
Note If a single number is given, all pages have this number of columns. If two numbers are given, the number of columns per page varies between the values supplied.
ruledLines specifies the number of ruled lines per column
Status Optional
Datatype 1–2 occurrences of 
                                                                    data.count
separated by whitespace
Note If a single number is given, all columns have this number of ruled lines. If two numbers are given, the number of ruled lines per column varies between the values supplied.
writtenLines specifies the number of written lines per column
Status Optional
Datatype 1–2 occurrences of 
                                                                    data.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: bibl note term
msdescription: dimensions locus locusGrp
Declaration 
element layout
{
   attribute columns { list { data.count, data.count? } }?,
   attribute ruledLines { list { data.count, data.count? } }?,
   attribute writtenLines { list { data.count, data.count? } }?,
   ( ( locus | locusGrp ), term*, bibl?, dimensions?, note? )
}
Schematron Check that the <term> element with the type attribute proximity containts the permitted values "similar to", "very similar to", "identical with", or "not clear".
<sch:rule context="//tei:layout/tei:term[@type='proximity']"> <sch:assert test="text()='similar to' or text()='very similar to' or text()='identical with' or text()='not clear'"> Permitted values are "similar to", "very similar to", "identical with", or "not clear".</sch:assert></sch:rule>
Example
<layoutDesc>  <layout columns="1" ruledLines="20" writtenLines="38 39">   <locus from="1r" to="91v" scheme="folios"/>   <term type="layout">ruling pattern</term>   <term type="proximity">identical with</term>   <bibl>    <ref target="#Sautel1995"/>    <citedRange unit="number" from="20D1" to="20D1"/>   </bibl>   <dimensions type="written">    <height min="185" max="190" unit="mm"/>    <width min="125" max="130" unit="mm"/>   </dimensions>  </layout> </layoutDesc>

Appendix A.1.51 <layoutDesc>

<layoutDesc> (layout description) collects the set of layout descriptions applicable to a manuscript. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Contained by
msdescription: objectDesc
May contain
msdescription: layout
Declaration 
element layoutDesc { layout+ }
Example
<layoutDesc>  <layout columns="1" ruledLines="20" writtenLines="38 39">   <locus from="1r" to="91v" scheme="folios"/>   <term type="layout">ruling pattern</term>   <term type="proximity">identical with</term>   <bibl>    <ref target="#Sautel1995"/>    <citedRange unit="number" from="20D1" to="20D1"/>   </bibl>   <dimensions type="written">    <height min="185" max="190" unit="mm"/>    <width min="125" max="130" unit="mm"/>   </dimensions>  </layout> </layoutDesc>

Appendix A.1.52 <lb/>

<lb/> (line break) marks the start of a new (typographic) line in some edition or version of a text. [3.10.3. Milestone Elements 7.2.5. Speech Contents]
Module core — Schema
Member of
model.milestoneLike
Contained by
core: foreign p quote
msdescription: additions colophon
May contain Empty element
Declaration 
element lb { empty }
Example
ἀμυστὶ <lb/> τὴν βίβλον

Appendix A.1.53 <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 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 
                                                                    data.pointer
separated by whitespace
Contained by
header: availability
May contain Character data only
Declaration 
element licence { attribute target { list { data.pointer+ } }, text }
Example
<publicationStmt>  <authority>Uppsala University Library</authority>  <pubPlace>Uppsala</pubPlace>  <date when="2014"/>  <availability status="free">   <licence target="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International</licence>  </availability> </publicationStmt>

Appendix A.1.54 <list>

<list> contains any sequence of items organized as a list. [3.7. Lists]
Module core — Schema
Attributes Attributes
type
Status Required
Legal values are:
toc
Table of contents
Member of
model.listLike
Contained by
core: note
msdescription: additions
May contain
core: item
Declaration 
element list { attribute type { "toc" }, item+ }
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>
Example
<note>  <list type="toc">   <item>    <locus from="1r:4" to="1r:19" scheme="folios"/>    <title xml:lang="la">Prooemium</title>   </item>   <item>    <locus from="1r:19" to="8v:6" scheme="folios"/>    <title xml:lang="la">Liber I</title>   </item>  </list> </note>

Appendix A.1.55 <listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.11.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
msdescription: additional additions msItem
May contain
core: bibl
Declaration 
element listBibl { bibl+ }
Example
<listBibl>  <bibl>   <ref target="#Marsden1971"/>   <citedRange from="66" to="103" unit="page"/>  </bibl>  <bibl>   <ref target="#Rehm1929"/>  </bibl> </listBibl>

Appendix A.1.56 <locus/>

<locus/> defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript]
Module msdescription — Schema
Attributes Attributes
scheme identifies the foliation scheme in terms of which the location is being specified by pointing to some <foliation> element defining it, or to some other equivalent resource.
Status Required
Datatype 
                                                                    data.pointer
Legal values are:
folios
pages
other
Use for spine and covers
from specifies the starting point of the location in a normalized form, typically a page number.
Status Required
Datatype 
                                                                    data.word
to specifies the end-point of the location in a normalized form, typically as a page number.
Status Required
Datatype 
                                                                    data.word
Member of
model.pPart.msdesc
Contained by
core: head item note p
header: handNote
msdescription: acquisition additions catchwords colophon condition decoNote foliation layout locusGrp msItem origin provenance signatures
May contain Empty element
Declaration 
element locus
{
   attribute scheme { "folios" | "pages" | "other" },
   attribute from { data.word },
   attribute to { data.word },
   empty
}
Schematron Check if <locus/> is used more than once when not inside a <locusGrp>
<sch:rule context="//tei:locusGrp"> <sch:report test="count(tei:locus) < 2"> Only use locusGrp when grouping together more than one locus.</sch:report></sch:rule>
Schematron Check for prohibited values in the from and to attributes
<sch:rule context="tei:locus"> <sch:report test="@from[starts-with(., 'i') or starts-with(., 'v') or starts-with(., 'x')] or @to[starts-with(., 'i') or starts-with(., 'v') or starts-with(., 'x')]"> The use of roman numerals is not allowed. Use L1r or L1v for left endleaves and R1r or R1v for right endleaves.</sch:report> <sch:report test="@from[matches(., 'lco')] or @to[matches(., 'lco')]"> Use LCO for left cover outside.</sch:report> <sch:report test="@from[matches(., 'lci')] or @to[matches(., 'lci')]"> Use LCI for left cover inside.</sch:report> <sch:report test="@from[matches(., 'rci')] or @to[matches(., 'rci')]"> Use RCI for right cover inside.</sch:report> <sch:report test="@from[matches(., 'rco')] or @to[matches(., 'rco')]"> Use RCO for right cover outside.</sch:report> <sch:report test="@from[matches(., 'Spine')] or @to[matches(., 'Spine')]"> Use spine with lower-case.</sch:report></sch:rule>
Schematron Check that the scheme attribute has the value folios when referring to folios.
<sch:rule context="tei:locus[@scheme='pages' or @scheme='other']"> <sch:report test="@from[contains(., 'r') or contains(., 'v')]"> Use the scheme attribute with the value folios when referring to folios.</sch:report> <sch:report test="@to[contains(., 'r') or contains(., 'v')]"> Use the scheme attribute with the value folios when referring to folios.</sch:report></sch:rule>
Schematron Check that the scheme attribute has the value other when referring to the spine och covers.
<sch:rule context="tei:locus[@scheme='folios' or @scheme='pages']"> <sch:report test="@from[matches(., 'spine')] or @from[matches(., 'LCO')] or @from[matches(., 'LCI')] or @to[matches(., 'spine')] or @to[matches(., 'RCO')] or @to[matches(., 'RCI')]"> Use the scheme attribute with the value other when referring to the spine or covers.</sch:report></sch:rule>
Example
<locus from="1r" to="119r" scheme="folios"/>
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 first example above. To associate a <locus/> element with a page image or other comparable representation, the global facs attribute should be used instead, as shown in the second example. Use of the target attribute to indicate an image is strongly deprecated. The facs attribute may be used to indicate one or more image files, as above, or alternatively it may point to one or more appropriate XML elements, such as the <surface>, <zone> element, <graphic/>, or <binaryObject> elements.
Note When the location being defined consists of a single page, use the from and to attributes with an identical value. When no clear endpoint is given the from attribute should be used without to. For example, if the manuscript description being transcribed has ‘p. 3ff’ as the locus.

Appendix A.1.57 <locusGrp>

<locusGrp> groups a number of locations which together form a distinct but discontinuous item within a manuscript or manuscript part, according to a specific foliation. [10.3.5. References to Locations within a Manuscript]
Module msdescription — Schema
Member of
model.pPart.msdesc
Contained by
core: head item note p
header: handNote
msdescription: additions colophon condition decoNote foliation layout msItem signatures watermark
May contain
msdescription: locus
Declaration 
element locusGrp { locus+ }
Example
<locusGrp>  <locus from="24r" to="29v" scheme="folios"/>  <locus from="32r" to="32v" scheme="folios"/>  <locus from="31r" to="31v" scheme="folios"/> </locusGrp>

Appendix A.1.58 <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
Member of
model.pPart.msdesc
Contained by
core: p term
msdescription: additions decoNote
May contain Character data only
Declaration 
element material { text }
Schematron Check that <material> for <support> only contains the permitted values "Western paper", "Western paper without watermarks", "Arabic paper", or "Parchment".
<sch:rule context="tei:support//tei:material"> <sch:assert test="text()='Western paper' or text()='Western paper without watermarks' or text()='Arabic paper' or text()='Parchment'"> Permitted values are "Western paper", "Western paper without watermarks", "Arabic paper", or "Parchment".</sch:assert></sch:rule>
Example
<material>Western paper</material>

Appendix A.1.59 <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.5.3. Numbers and Measures]
Module core — Schema
Attributes Attributes
unit indicates the units used for the measurement, usually using the standard symbol for the desired units.
Derived from att.measurement
Status Recommended
Datatype 
                                                                    data.enumerated
Legal values are:
mm
millimeters
lines
laid-lines on paper
folios
folios
quantity specifies the number of the specified units that comprise the measurement
Derived from att.measurement
Status Recommended
Datatype 
                                                                    data.numeric
type specifies the type of measurement in any convenient typology.
Status Required
Datatype 
                                                                    data.enumerated
Legal values are:
left_flyleaves
right_flyleaves
textblock_leaves
laid-lines_in_20mm
Number of laid lines in 20 mm
folding
The folding of the sheets: Folio, Quarto, Octavo
Member of
model.measureLike
Contained by
core: p
header: extent
msdescription: additions decoNote watermark
May contain Character data only
Declaration 
element measure
{
   attribute unit { "mm" | "lines" | "folios" }?,
   attribute quantity { data.numeric }?,
   attribute type
   {
      "left_flyleaves"
    | "right_flyleaves"
    | "textblock_leaves"
    | "laid-lines_in_20mm"
    | "folding"
   },
   text
}
Schematron Check that <measure> type folding only contains the permitted values "Folio", "Quarto", or "Octavo".
<sch:rule context="//tei:measure[@type='folding']"> <sch:assert test="text()='Folio' or text()='Quarto' or text()='Octavo'"> Permitted values are "Folio", "Quarto", or "Octavo".</sch:assert></sch:rule>
Example
<extent>  <measure type="left_flyleaves" quantity="0" unit="folios"/>  <measure type="right_flyleaves" quantity="2" unit="folios"/> </extent>
Example
<measure type="folding">Quarto</measure>

Appendix A.1.60 <msContents>

<msContents> (manuscript contents) describes the intellectual content of a manuscript or manuscript part, either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content]
Module msdescription — Schema
Contained by
msdescription: msDesc msPart
May contain
msdescription: msItem summary
Declaration 
element msContents { summary?, msItem+ }
Example
<msContents>  <msItem class="schol">   <locus from="27v:12" to="27v:31" scheme="folios"/>   <author>    <persName ref="#ManHol"/>   </author>   <title ref="http://pinakes.irht.cnrs.fr/notices/oeuvre/id/1420" type="uniform" xml:lang="la">Commentarius in securim</title>   <rubric xml:lang="grc">Τοῦ Ὁλοβόλου εἰς τὸν Πέλεκυν ἐξήγησις συνοπτική</rubric>   <incipit xml:lang="grc" defective="false">Ὁ πέλεκυς οὐχ <supplied reason="omitted" xml:lang="grc">ὡς</supplied> ὁ Σύριγξ καὶ οἱ Βωμοὶ</incipit>   <explicit xml:lang="grc" defective="false">ὄλβιος καὶ εὐτυχὴς ἀεὶ πνεῖ καὶ ζῇ</explicit>  </msItem> </msContents>
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.

Appendix A.1.61 <msDesc>

<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object. [10.1. Overview]
Module msdescription — Schema
Attributes 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
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
Member of
model.biblLike
Contained by
header: sourceDesc
msdescription: additions
May contain
core: head
msdescription: additional history msContents msIdentifier msPart physDesc
Declaration 
element msDesc
{
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   msIdentifier,
   model.headLike,
   msContents,
   physDesc,
   history,
   additional,
   msPart+
}
Schematron Checks that folio and page references are only given in <locus/> elements and not in the running text.
<sch:pattern> <sch:rule context="tei:msDesc//*">  <sch:report test="text()[matches(., ' f. \p{N}| ff. \p{N}')]"> Do not use f./ff. in the running text for folio references. Use the locus element instead.</sch:report>  <sch:report test="text()[matches(., ' p. \p{N}| pp. \p{N}')]"> Do not use p./pp. in the running text for page references. Use the locus element instead.</sch:report></sch:rule></sch:pattern>
Example
<msDesc>  <msIdentifier>   <country>Sweden</country>   <settlement>Uppsala</settlement>   <institution>Uppsala University</institution>   <repository>Uppsala University Library</repository>   <idno type="shelfmark">Gr. 27</idno>  </msIdentifier>  <head>Aelian, On Animals</head> <!-- MS description --> </msDesc>

Appendix A.1.62 <msIdentifier>

<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript being described. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Contained by
msdescription: msDesc msPart
May contain
header: idno
msdescription: altIdentifier institution msName repository
namesdates: country settlement
Declaration 
element msIdentifier
{
   ( country?, settlement?, institution?, repository?, idno ),
   ( msName | altIdentifier )*
}
Schematron
<s: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 of some type, or a manuscript name</s:report>
Example
<msIdentifier>  <country>Sweden</country>  <settlement>Uppsala</settlement>  <institution>Uppsala University</institution>  <repository>Uppsala University Library</repository>  <idno type="shelfmark">Gr. 28A</idno>  <msName>Codex Rolambianus</msName>  <altIdentifier>   <idno type="former_shelfmark">Benzelius 2</idno>  </altIdentifier> </msIdentifier>

Appendix A.1.63 <msItem>

<msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript or manuscript part. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes Attributes
defective indicates whether the passage being quoted is defective, i.e. incomplete through loss or damage.
Derived from att.msExcerpt
Status Optional
Datatype 
                                                                    data.xTruthValue
Default false
class identifies the text types or classifications applicable to this item by pointing to other elements or resources defining the classification concerned.
Status Required
Datatype 1–∞ occurrences of 
                                                                    data.pointer
separated by whitespace
Legal values are:
left_endleaf
(Left endleaf)
right_endleaf
(Right endleaf)
acta
(Acta)
alchem
(Alchemica)
anthol
(Anthologia) is used to classify postclassical collections such as the Anthologia Graeca that represent a sizeable collection constructed in late antiquity from earlier disparate sources. (http://www.tlg.uci.edu/help/class.html)
apocalyp
(Apocalypsis) defines works of a prophetic nature but with a focus clearly directed "towards the end of things and to the destiny of the world in general." (F.L. Cross, The Oxford dictionary of the Christian church [London 1958] 67). Prophecies that look toward the future but without the apocalyptic vision of a grand terminus are labeled Prophet.
apocryph
(Apocrypha) is used to identify two kinds of works: 1) works that have come down to us as part of the Septuagint but were not part of the traditional Hebrew Bible and 2) works that are generally regarded by Christians as extracanonical in relation to the New Testament. Pseudepigr. on the other hand, has been used for works that belong neither to the Septuagint not to the Hebrew Bible but have been transmitted under the name of a Jewish religious thinker.
astrolog
(Astrologica)
apol
(Apologetica) is applied to works written in defense of the tenets of one religious system against those of another. It is also used of works written in justification of orthodox Christian faith in opposition to heretical beliefs.
biogr
(Biographa) indicates both biographical and autobiographical writings.
bucol
(Bucolica)
caten
(Catena) is restricted to scholiastic comment upon biblical passages and lists of variae lectiones to a given catena on a biblical passage. Commentaries by individual authors ot scriptural texts are classified as Exeget. whereas commenta derived from catenae are tagged both as Exeget. and Caten.
chronogr
(Chronographa)
comic
(Comica)
comm
(Commentarius)
concil
(Concilia) signifies a miscellany of writings including speeches, letters, rosters, and proceedings of ecumenical councils.
dialog
(Dialogus) is reserved for literary works written in the form of a prose dialogue.
doxogr
(Doxographa)
eccl
(Ecclesiastica) is a multipurpose tag attached to works that seem to be ecclesiastical in nature but lack characteristics that would permit a more specific definition. In general, Eccl. refers to themes, concerns, and attitudes associated with the Christian church.
epic
(Epica)
epigr
(Epigrammatica)
epist
(Epistolographa)
evang
(Evangelica)
encom
(Encomiastica) is used for eulogy, panegyric, laudationes or any kind of work (poetry or prose) that falls under the general variety of laudatory literature.
exeget
(Exegetica) distinguishes writings that interpret the texts of the Old and New Testaments from the commentaries that focus upon secular literature.
fab
(Fabula)
geogr
(Geographa)
gnom
(Gnomica)
gramm
(Grammatica) is used to tag those works explicitly entitled Ars grammatica or Fragmenta grammatica, as well as treatises on prosody, orthography, accentuation, parts of speech, and inflection.
hagiogr
(Hagiographica) is used to characterize works whose principal themes are the lives and acts of saints, martyrs, and heroic figures in Judaeo-Christian tradition.
hexametr
(Hexametrica) is used of poems (or fragments of poems) that do not betray a generic affiliation with some species of poetry in terms of theme or tone. The generic tags Epic., Bucol., and Parod., when used, indicate an implicit assumption of the hexameter form. In these cases, the tag Hexametr. is not added.
hist
(Historica) is added to the following categories: extant works of Greek historians; fragments of lost historical works collected in independent editions or generic collections such as FGrH, FHG, and HGM, and works of ecclesiastical writers that focus upon the history of the Church.
homilet
(Homiletica) is used to distinguish homiliae (i.e. discourses on religious and moral topics delivered, or written as though they were intended for delivery to a congregation) from orationes (i.e. discourses on secular topics).
hymn
(Hymnus) is assigned, regardless of meter, to the great variety of hymnal poetry ranging from the Hymni Homerici to the polymetric hymns of Gregory of Nazianzus.
hypoth
(Hypothesis) defines the hypotheses transmitted as prefixes to Greek tragedies and comedies.
iamb
(Iambica)
invectiv
(Invectiva)
jurisprud
(Jurisprudentia)
legal
(Legalia)
lexicogr
(Lexicographa) is used for word-lists and glossaries but also any lexicon that incorporates commentary.
liturg
(Liturgica)
lyr
(Lyrica)
magica
(Magica)
math
(Mathematica)
mech
(Mechanica)
med
(Medica) is applied to a wide range of medical writings (including veterinary treatises and writings that deal with antidotes and pharmacological prescriptions.
metrolog
(Metrologica)
mim
(Mimus)
mus
(Musica) is used to classify theoretical works on music but also musical scales, notations and fragments of music.
myth
(Mythographa) is used to classify the works of mythographers but also works of historians (especially the early logographers) who cited myths as evidence in their historical accounts.
narr_fict
(Narratio Ficta) is used to categorize a variety of novelistic writings that range from novel or romance to novella, story, tale, and vignette.
nat_hist
(Naturalis Historia) includes a broad range of topics such as animal nature, horse breeding and training, colors, stones, rivers, meteorology, and agriculture.
onir
(Onirocritica)
orac
(Oraculum)
orat
(Oratio)
paradox
(Paradoxographa)
parod
(Parodica)
paroem
(Paroemiographica)
perieg
(Periegesis)
phil
(Philosophica)
physiognom
(Physiognomica)
pinax
(Pinax)
poem
(Poema) indicates metrical pieces that do not readily admit generic definition either by reason of meter or in terms of themes and tone.
polyhist
(Polyhistorica)
prophet
(Prophetia)
pseudepigr
(Pseudepigrapha)
relig
(Religiosa) is used exclusively to designate texts that constitute the basis for the scripturae sacrae of Judaeo-Christian tradition. The term has been used only for the 27 books ofr the New Testament and the 59 works of the Septuaginta.
rhet
(Rhetorica) is used to classify works concerned with the art, science, theories, and techniques of persuasion, of which oratory is the principal beneficiary.
satura
(Satura)
satyr
(Satyra)
schol
(Scholia)
tact
(Tactica)
test
(Testimonia)
theol
(Theologica) is used to classify works that can be defined as religious literature insofar as they are concerned primarily with the nature of divinity, the relationship between human and divine, religious doctrine, and other spiritual matters. A distinction is made between Theol. and Eccl. where Eccl. characterizes matters of interest to the Christian church but without principal focus upon divinity.
trag
(Tragica)
zool
(Zoologica)
Contained by
msdescription: msContents msItem
May contain
core: author bibl listBibl note quote textLang title
msdescription: colophon explicit filiation finalRubric incipit locus locusGrp msItem rubric
Declaration 
element msItem
{
   attribute defective { data.xTruthValue }?,
   attribute class
   {
      list
      {
         (
            "left_endleaf"
          | "right_endleaf"
          | "acta"
          | "alchem"
          | "anthol"
          | "apocalyp"
          | "apocryph"
          | "astrolog"
          | "apol"
          | "biogr"
          | "bucol"
          | "caten"
          | "chronogr"
          | "comic"
          | "comm"
          | "concil"
          | "dialog"
          | "doxogr"
          | "eccl"
          | "epic"
          | "epigr"
          | "epist"
          | "evang"
          | "encom"
          | "exeget"
          | "fab"
          | "geogr"
          | "gnom"
          | "gramm"
          | "hagiogr"
          | "hexametr"
          | "hist"
          | "homilet"
          | "hymn"
          | "hypoth"
          | "iamb"
          | "invectiv"
          | "jurisprud"
          | "legal"
          | "lexicogr"
          | "liturg"
          | "lyr"
          | "magica"
          | "math"
          | "mech"
          | "med"
          | "metrolog"
          | "mim"
          | "mus"
          | "myth"
          | "narr_fict"
          | "nat_hist"
          | "onir"
          | "orac"
          | "orat"
          | "paradox"
          | "parod"
          | "paroem"
          | "perieg"
          | "phil"
          | "physiognom"
          | "pinax"
          | "poem"
          | "polyhist"
          | "prophet"
          | "pseudepigr"
          | "relig"
          | "rhet"
          | "satura"
          | "satyr"
          | "schol"
          | "tact"
          | "test"
          | "theol"
          | "trag"
          | "zool"
         )+
      }
   },
   (
      ( locus | locusGrp ),
      (
         (
            textLang?,
            author*,
            title*,
            rubric?,
            msItem*,
            incipit?,
            quote?,
            explicit?,
            finalRubric?,
            note?,
            colophon?,
            filiation*,
            ( listBibl? | bibl? )
         )
       | note
      )
   )
}
Schematron checks that the <meItem> element contains at least a <locus/> or <locusGrp> and a <note>.
<sch:rule context="tei:msItem"> <sch:assert test="tei:note or (tei:textLang or tei:author or tei:title or tei:rubric or tei:msItem or tei:incipit or tei:quote or tei:explicit or tei:finalRubric or tei:colophon or tei:filiation or tei:listBibl or tei:bibl)">The msItem element must contain at least a locus or locusGrp and a note element.</sch:assert></sch:rule>
Example
<msItem class="phil">  <locus from="26r" to="26r" scheme="folios"/>  <textLang mainLang="grc"/>  <title type="desc" xml:lang="en">A diagram on logical categories</title>  <incipit xml:lang="grc" defective="false">Πᾶν πρᾶγμα ἢ διαιρετὸν ἢ ἀδιαίρετον</incipit>  <explicit xml:lang="grc" defective="false">ὡς τῶν μελαίνων, τὰ μὲν ψυχρά, τὰ δὲ τερμά</explicit> </msItem>

Appendix A.1.64 <msName>

<msName> (alternative name) contains any form of unstructured alternative name used for a manuscript, such as an ‘ocellus nominum’, or nickname. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Attributes Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
Contained by
msdescription: msIdentifier
May contain Character data only
Declaration 
element msName
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   macro.xtext
}
Example
<msName xml:lang="la">Codex Rolambianus</msName>

Appendix A.1.65 <msPart>

<msPart> (manuscript part) contains information about an originally distinct manuscript or part of a manuscript, now forming part of a composite manuscript. [10.10. Manuscript Parts]
Module msdescription — Schema
Contained by
msdescription: msDesc
May contain
msdescription: history msContents msIdentifier physDesc
Declaration 
element msPart { msIdentifier, msContents, physDesc, history? }
Schematron The <msIdentifier> element is now allowed as a child of <msPart>, and it (with its <altIdentifier> children if needed) should be used instead of an <altIdentifier> directly within <msPart>.
<sch:report test="child::tei:altIdentifier" role="nonfatal">WARNING: use of deprecated method — the use of the altIdentifier element as a direct child of the msPart element will be removed from the TEI on 2016-09-09</sch:report>
Example
<msDesc> <!-- Common information -->  <msPart> <!-- Codicological unit 1 -->  </msPart>  <msPart> <!-- Codicological unit 2 -->  </msPart> </msDesc>

Appendix A.1.66 <musicNotation>

<musicNotation> contains description of type of musical notation. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription — Schema
Contained by
msdescription: physDesc
May contain
core: term
Declaration 
element musicNotation { ( text | term )* }
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>

Appendix A.1.67 <note>

<note> contains a note or annotation. [3.8.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.11.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]
Module core — Schema
Member of
model.noteLike
Contained by
core: p
msdescription: additions layout msItem watermark
May contain
core: bibl date foreign list p quote ref term
header: idno
msdescription: locus locusGrp
namesdates: persName placeName
Declaration 
element note
{
   (
      text
    | bibl
    | date
    | foreign
    | idno
    | list
    | locus
    | locusGrp
    | p
    | persName
    | placeName
    | quote
    | ref
    | term
   )*
}
Example
<note>With interlinear glosses and a few longer scholia. Following the main text, there are on <locus from="24v" to="25v" scheme="folios"/> also sketches and diagrams relating to it (illustrating e.g. the four elements, agricultural implements, celestial bodies, the zodiac). The sketches may be compared to the illustrations in the Venice print edition from 1537: <bibl>   <ref target="#Trincavelli1537"/>   <citedRange unit="folio" from="CXIIv" to="CXIIv"/>  </bibl>.</note>

Appendix A.1.68 <num>

<num> (number) contains a number, written in any form. [3.5.3. Numbers and Measures]
Module core — Schema
Attributes Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Required
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
type indicates the type of numeric value.
Status Required
Datatype 
                                                                    data.enumerated
Legal values are:
cardinal
absolute number, e.g. 21, 21.5
ordinal
ordinal number, e.g. 21st
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 Required
Datatype 
                                                                    data.numeric
Values a numeric value.
Note The standard form used is defined by the TEI datatype data.numeric.
Member of
model.measureLike
Contained by
msdescription: additions colophon foliation signatures
May contain
core: hi
Declaration 
element num
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   },
   attribute type { "cardinal" | "ordinal" },
   attribute value { data.numeric },
   ( hi | text )*
}
Example
<num xml:lang="grc" type="cardinal" value="1">αʹ</num> <num xml:lang="grc" type="cardinal" value="1000">͵α</num> <num xml:lang="grc" type="ordinal" value="4">δ<hi rend="sup">ου</hi> </num>
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.

Appendix A.1.69 <objectDesc>

<objectDesc> contains a description of the physical components making up the object which is being described. [10.7.1. Object Description]
Module msdescription — Schema
Contained by
msdescription: physDesc
May contain
msdescription: layoutDesc supportDesc
Declaration 
element objectDesc { supportDesc, layoutDesc? }
Example
<objectDesc>  <supportDesc material="parchment">   <support>    <p>     <locus from="92r" to="220v" scheme="folios"/>     <dimensions type="leaf">      <height quantity="225" unit="mm"/>      <width quantity="170" unit="mm"/>     </dimensions>    </p>   </support>   <extent>    <measure type="textblock_leaves" quantity="129"/>   </extent>   <collation>    <formula>     <hi rend="sub">Q17–29</hi>13.IV<hi rend="super">f.195</hi> +    <hi rend="sub">Q30</hi>(IV + 3f.<hi rend="super">f.196–198</hi>)<hi rend="super">f.206</hi>:        3 single leaves pasted together and onto the following quaternion + <hi rend="sub">Q31</hi>IV<hi rend="super">f.214</hi> + <hi rend="sub">Q32</hi>III<hi rend="super">f.220</hi>    </formula>    <signatures>     <term>none</term>    </signatures>    <catchwords>     <term>none</term>    </catchwords>   </collation>  </supportDesc>  <layoutDesc>   <layout columns="1" ruledLines="21" writtenLines="39 41">    <locus from="92r" to="220v" scheme="folios"/>    <term type="layout">ruling pattern</term>    <term type="proximity">identical with</term>    <bibl>     <ref target="#Sautel1995"/>     <citedRange unit="number" from="20D1" to="20D1"/>    </bibl>    <note>On some pages the <term type="layout">ruling pattern</term> is closer to <bibl>      <ref target="#Sautel1995"/>      <citedRange unit="number" from="20A1" to="20A1"/>     </bibl>, although this may be due to the scribe being less accurate in the execution.</note>    <dimensions type="written">     <height min="195" max="200" unit="mm"/>     <width min="130" max="135" unit="mm"/>    </dimensions>   </layout>  </layoutDesc> </objectDesc>

Appendix A.1.70 <origDate>

<origDate> (origin date) contains any form of date, used to identify the date of origin for a manuscript or manuscript part. [10.3.1. Origination]
Module msdescription — Schema
Attributes Attributesatt.datable.w3c (from, to, @when, @notBefore, @notAfter)
Member of
model.pPart.msdesc
Contained by
msdescription: additions origin
May contain Character data only
Declaration 
element origDate
{
   att.datable.w3c.attribute.when,
   att.datable.w3c.attribute.notBefore,
   att.datable.w3c.attribute.notAfter,
   text
}
Schematron
<sch:rule context="tei:origDate"> <sch:assert test="@when or (@notAfter and @notBefore)"> Either @when or @notAfter/@notBefore must be provided. </sch:assert> <sch:report test="not(text())"> A text description for origDate must be provided</sch:report></sch:rule>
Example
<origDate notBefore="1251" notAfter="1300">13th century (2nd half)</origDate>

Appendix A.1.71 <origPlace>

<origPlace> (origin place) contains any form of place name, used to identify the place of origin for a manuscript or manuscript part. [10.3.1. Origination]
Module msdescription — Schema
Member of
model.pPart.msdesc
Contained by
msdescription: additions origin
May contain
namesdates: placeName
Declaration 
element origPlace { placeName }
Example
<origPlace>  <placeName ref="#Bologna"/> </origPlace>

Appendix A.1.72 <origin>

<origin> contains any descriptive or other information concerning the origin of a manuscript or manuscript part. [10.8. History]
Module msdescription — Schema
Contained by
msdescription: history
May contain
core: bibl date foreign quote
header: idno
msdescription: locus origDate origPlace
namesdates: persName
Declaration 
element origin
{
   (
      text
    | bibl*
    | date*
    | foreign*
    | idno*
    | locus*
    | origDate?
    | origPlace?
    | persName*
    | quote*
   )*
}
Example
<origin>Probably written in the <origDate from="1250" to="1300">second half of the thirteenth century</origDate>. Place unknown.</origin>

Appendix A.1.73 <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Module core — Schema
Attributes Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
Member of
model.pLike
Contained by
core: note
msdescription: additions bindingDesc collation decoDesc support
textstructure: div
May contain
core: bibl date foreign lb measure note quote ref term
header: idno
msdescription: dimensions locus locusGrp material watermark
namesdates: persName placeName
Declaration 
element p
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   (
      text
    | bibl
    | date
    | dimensions
    | foreign
    | idno
    | lb
    | locus
    | locusGrp
    | material
    | measure
    | note
    | persName
    | placeName
    | quote
    | ref
    | term
    | watermark
   )*
}
Example
<bindingDesc>  <p>Light yellow <term>parchment</term>   <term>case binding</term> over pasteboard created from manuscript waste paper with Spanish    text on it. Sewn on four supports; only the endband slips are laced through the cover and turn-ins.    Endbands in pink and green with front bead; Two pairs of ties at foredge. Red mottled edges.</p> </bindingDesc>

Appendix A.1.74 <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 Attributes
cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
Derived from att.global.responsibility
Status Optional
Datatype 
                                                                    data.certainty
evidence indicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
Derived from att.editLike
Status Optional
Datatype 1–∞ occurrences of 
                                                                    data.enumerated
separated by whitespace
Legal values are:
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.
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 
                                                                    data.enumerated
separated by whitespace
Legal values are:
cataloguer
librarian
scribe
ref (reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.
Derived from att.canonical
Status Required
Datatype 1–∞ occurrences of 
                                                                    data.pointer
separated by whitespace
Member of
model.nameLike.agent
Contained by
core: author note p ref respStmt title
header: handNote
msdescription: acquisition additions foliation origin provenance
May contain Character data only
Declaration 
element persName
{
   attribute cert { data.certainty }?,
   attribute evidence { list { ( "internal" | "external" | "conjecture" )+ } }?,
   attribute role { list { ( "cataloguer" | "librarian" | "scribe" )+ } }?,
   attribute ref { list { data.pointer+ } },
   text
}
Schematron Check that cert is used when evidence is external or conjecture.
<sch:rule context="tei:persName[@evidence='external' or @evidence='conjecture']"> <sch:assert test="@cert"> Use the cert attribute when the evidence attribute has the value external or conjecture. </sch:assert></sch:rule>
Example
<persName ref="#PehAur" role="librarian" evidence="conjecture" cert="medium"/>

Appendix A.1.75 <physDesc>

<physDesc> (physical description) contains a full physical description of a manuscript or manuscript part, optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description]
Module msdescription — Schema
Contained by
msdescription: msDesc msPart
May contain
msdescription: additions bindingDesc decoDesc handDesc musicNotation objectDesc
Declaration 
element physDesc
{
   objectDesc?, handDesc?, additions?, musicNotation?, decoDesc?, bindingDesc?
}
Example
<physDesc>  <objectDesc> <!-- Object description -->  </objectDesc>  <handDesc> <!-- Hand description -->  </handDesc>  <bindingDesc> <!-- Binding description -->  </bindingDesc> </physDesc>

Appendix A.1.76 <placeName/>

<placeName/> contains an absolute or relative place name. [13.2.3. Place Names]
Module namesdates — Schema
Attributes Attributes
ref (reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.
Derived from att.canonical
Status Required
Datatype 1–∞ occurrences of 
                                                                    data.pointer
separated by whitespace
Member of
model.placeNamePart
Contained by
core: note p ref
msdescription: acquisition additions origPlace provenance
May contain Empty element
Declaration 
element placeName { attribute ref { list { data.pointer+ } }, empty }
Example
<placeName ref="#Bologna"/>

Appendix A.1.77 <provenance>

<provenance> contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript or manuscript part, after its creation but before its acquisition. [10.8. History]
Module msdescription — Schema
Contained by
msdescription: history
May contain
core: bibl date foreign quote
header: idno
msdescription: locus
namesdates: persName placeName
Declaration 
element provenance
{
   (
      text
    | bibl*
    | date*
    | foreign*
    | idno*
    | locus*
    | persName*
    | placeName*
    | quote*
   )*
}
Example
<provenance>At sometime the volume came to <placeName ref="#Venice"/>, where it came on the market in the <date notBefore="1692" notAfter="1694">late seventeenth century</date>.</provenance>

Appendix A.1.78 <pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Module core — Schema
Contained by
header: publicationStmt
May contain Character data only
Declaration 
element pubPlace { text }
Schematron Check that Uppsala is used in <pubPlace> under <publicationStmt>.
<sch:rule context="tei:publicationStmt/tei:pubPlace"> <sch:assert test="text()='Uppsala'"> Uppsala should be used for pubPlace. </sch:assert></sch:rule>
Example
<publicationStmt>  <authority>Uppsala University Library</authority>  <pubPlace>Uppsala</pubPlace> </publicationStmt>

Appendix A.1.79 <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 pubPlace
header: authority availability
Declaration 
element publicationStmt { authority, pubPlace, date, availability }
Example
<publicationStmt>  <authority>Uppsala University Library</authority>  <pubPlace>Uppsala</pubPlace>  <date when="2014"/> </publicationStmt>

Appendix A.1.80 <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 Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
Member of
model.quoteLike
Contained by
core: note p
header: handNote
msdescription: acquisition additions filiation msItem origin provenance
May contain
core: lb sic
transcr: ex supplied
Declaration 
element quote
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   ( text | ex | lb | sic | supplied )*
}
Example
<quote xml:lang="la">Theodorus samius primo clavem mostravit</quote>
Note If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element.

Appendix A.1.81 <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. Simple Links and Cross-References 16.1. Links]
Module core — Schema
Attributes Attributes
target specifies the destination of the reference by supplying one or more URI References
Derived from att.pointing
Status Recommended
Datatype 1–∞ occurrences of 
                                                                    data.pointer
separated by whitespace
Member of
model.ptrLike
Contained by
core: bibl note p
msdescription: additions watermark
May contain
core: bibl date
msdescription: watermark
namesdates: persName placeName
Declaration 
element ref
{
   attribute target { list { data.pointer+ } }?,
   ( text | bibl | date | placeName | persName | watermark )*
}
Schematron checks that the target attribute in the <ref> element starts with # or http
<sch:pattern> <sch:rule context="tei:ref/@target">  <sch:assert test="starts-with(., '#') or starts-with(., 'http')">The target value must start with # or http</sch:assert></sch:rule></sch:pattern>
Schematron checks that the <ref> element has a target attribute when it is a child of the <bibl> element
<sch:pattern> <sch:rule context="tei:bibl/tei:ref">  <sch:assert test="@target">The ref element must have a target attribute</sch:assert></sch:rule></sch:pattern>
Schematron checks that xml:id only contains basic latin characters and numbers.
<sch:pattern> <sch:rule context="tei:bibl/tei:ref/@target">  <sch:assert test="matches(.,'^#[A-Za-z]+\d{4}[a-z]?$')">The target attribute should only consist of #, the authors surname in basic latin characters, followed by the publication year, and optionally characters a, b, c etc.</sch:assert></sch:rule></sch:pattern>
Schematron
<s:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <s:name/></s:report>
Example
<bibl>  <ref target="#DeStefani1902"/> </bibl>

Appendix A.1.82 <repository>

<repository> contains the name of a repository within which manuscripts are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier]
Module msdescription — Schema
Contained by
msdescription: msIdentifier
May contain Character data only
Legal values are:
Uppsala University Library
Gothenburg University Library
Linköping Diocesan Library
Lund University Library
The National Archives
The National Archives, Stockholm
The National Gallery
The National Gallery, Stockholm
Royal Library
Royal Library, Stockholm
Skokloster Castle Library
Declaration 
element repository { text }
Example
<msIdentifier>  <country>Sweden</country>  <settlement>Uppsala</settlement>  <institution>Uppsala University</institution>  <repository>Uppsala University Library</repository>  <idno type="shelfmark">Gr. 27</idno> </msIdentifier>

Appendix A.1.83 <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.11.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 Attributes
key provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Derived from att.canonical
Status Required
Datatype 
                                                                    data.text
Legal values are:
cataloguer
encoder
Contained by
core: respStmt
May contain Empty element
Declaration 
element resp { attribute key { "cataloguer" | "encoder" }, empty }
Example
<respStmt xml:id="EN">  <persName ref="#EvaNys"/>  <resp key="cataloguer"/>  <resp key="encoder"/> </respStmt>

Appendix A.1.84 <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.11.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 Attributesatt.global.responsibility (@cert)
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype 
xsd:ID
Legal values are:
EN
Eva Nyström
PG
Patrik Granholm
BC
Barbara Crostini
Contained by
header: titleStmt
May contain
core: resp
namesdates: persName
Declaration 
element respStmt
{
   att.global.responsibility.attribute.cert,
   attribute xml:id { "EN" | "PG" | "BC" },
   persName,
   resp+
}
Example
<respStmt xml:id="EN">  <persName ref="#EvaNys"/>  <resp key="cataloguer"/>  <resp key="encoder"/> </respStmt>

Appendix A.1.85 <revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.5. The Revision Description 2.1.1. The TEI Header and Its Components]
Module header — Schema
Attributes 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 
                                                                    data.enumerated
Legal values are:
draft
working draft [Default]
published
published version
Contained by
header: teiHeader
May contain
header: change
Declaration 
element revisionDesc { attribute status { "draft" | "published" }, change+ }
Example
<revisionDesc status="draft">  <change status="draft" when="2015-01-12" who="#PG">Added facsimile</change>  <change status="draft" when="2014-06-11" who="#PG">Changes to modified ODD</change>  <change status="draft" when="2012-11-12" who="#PG">First draft</change> </revisionDesc>

Appendix A.1.86 <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 signals the beginning of a text division, often with an assertion as to its author and title, which is in some way set off from the text itself, usually in red ink, or by use of different size or type of script, or some other such visual device. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription — Schema
Attributes Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype 
                                                                    data.language
Legal values are:
grc
Greek should be normalized: the first letter of each sentence and of names should be capitalized, iota subscripts should be added, and abbreviations expanded. [Default]
la
Contained by
msdescription: msItem
May contain
core: add del sic
transcr: supplied
Declaration 
element rubric
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang { "grc" | "la" }?,
   ( text | add | del | sic | supplied )*
}
Example
<rubric xml:lang="grc">  <del xml:lang="grc">ἐπληρώθη τὸ τέταρτον</del>  <add place="above" xml:lang="grc">Βίτωνος Μηχανικά</add> </rubric>

Appendix A.1.87 <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
Member of
model.placeNamePart
Contained by
msdescription: additions msIdentifier
May contain Character data only
Declaration 
element settlement { text }
Example
<msIdentifier>  <country>Sweden</country>  <settlement>Uppsala</settlement>  <institution>Uppsala University</institution>  <repository>Uppsala University Library</repository>  <idno type="shelfmark">Gr. 27</idno> </msIdentifier>

Appendix A.1.88 <sic>

<sic> (Latin for thus or so ) contains text reproduced although apparently incorrect or inaccurate. [3.4.1. Apparent Errors]
Module core — Schema
Attributes Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
Member of
model.pPart.transcriptional
Contained by
core: quote
msdescription: additions colophon explicit finalRubric incipit rubric
May contain Character data only
Declaration 
element sic
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   text
}
Example
<sic xml:lang="grc">γραφεὶς</sic>

Appendix A.1.89 <signatures>

<signatures> contains discussion of the leaf or quire signatures found within a codex. [10.3.7. Catchwords, Signatures, Secundo Folio]
Module msdescription — Schema
Member of
model.pPart.msdesc
Contained by
msdescription: additions collation
May contain
core: bibl num term
msdescription: locus locusGrp
Declaration 
element signatures { ( text | locus | locusGrp | num | bibl | term )* }
Example
<signatures>In the <term>lower left margin</term> of the <term>last verso</term>, mostly trimmed, but the following are visible: <num xml:lang="grc" type="cardinal" value="2">βʹ</num>  <locus from="8v" to="8v" scheme="folios"/>  <num xml:lang="grc" type="cardinal" value="6">Ϛʹ</num>  <locus from="37v" to="37v" scheme="folios"/>  <num xml:lang="grc" type="cardinal" value="7">ζʹ</num>  <locus from="45v" to="45v" scheme="folios"/> </signatures>

Appendix A.1.90 <sourceDesc>

<sourceDesc> (source description) describes the source 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
Declaration 
element sourceDesc { msDesc }
Example
<sourceDesc>  <msDesc> <!-- MS description -->  </msDesc> </sourceDesc>

Appendix A.1.91 <summary>

<summary> contains an overview of the available information concerning some aspect of an item (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
Contained by
msdescription: msContents
May contain Character data only
Declaration 
element summary { text }

Appendix A.1.92 <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 Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
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 Required
Datatype 1–∞ occurrences of 
                                                                    data.word
separated by whitespace
Legal values are:
omitted
illegible
damage
unknown
Member of
model.pPart.transcriptional
Contained by
core: quote title
msdescription: additions colophon explicit finalRubric foliation incipit rubric
May contain Character data only
Declaration 
element supplied
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   attribute reason
   {
      list { ( "omitted" | "illegible" | "damage" | "unknown" )+ }
   },
   text
}
Example
<supplied xml:lang="grc" reason="omitted">τ</supplied>ῷ συντελεστῇ

Appendix A.1.93 <support>

<support> contains a description of the materials etc. which make up the physical support for the written part of a manuscript. [10.7.1. Object Description]
Module msdescription — Schema
Contained by
msdescription: supportDesc
May contain
core: p
Declaration 
element support { p+ }
Schematron Checks that <support> has <material>
<sch:rule context="tei:support/tei:p"> <sch:assert test="tei:locus[following-sibling::tei:material][following-sibling::tei:dimensions[@type='leaf']] or tei:locusGrp[following-sibling::tei:material][following-sibling::tei:dimensions[@type='leaf']]"> The locus, material, and dimensions elements must be used</sch:assert></sch:rule>
Example
<support>  <p>   <locus from="14" to="24" scheme="folios"/>   <material>Western paper</material>   <measure type="folding">Quarto</measure>   <dimensions type="leaf">    <height quantity="220" unit="mm"/>    <width quantity="160" unit="mm"/>   </dimensions>   <watermark n="2a">    <locusGrp>     <locus from="15" to="15" scheme="folios"/>     <locus from="20" to="20" scheme="folios"/>    </locusGrp>    <term type="wm_motif">Hand; flower</term>    <term type="proximity">similar to</term>    <ref>     <bibl>      <ref target="#Briquet1968"/>      <citedRange>Main 10720</citedRange>     </bibl>     <placeName ref="#Perpignan"/>     <date when="1528"/>    </ref>    <dimensions type="chain-lines">     <width quantity="38" unit="mm"/>    </dimensions>    <measure type="laid-lines_in_20mm" quantity="22" unit="lines"/>   </watermark>   <watermark n="2b">    <locusGrp>     <locus from="23" to="23" scheme="folios"/>     <locus from="24" to="24" scheme="folios"/>    </locusGrp>    <term type="wm_motif">Hand; flower</term>    <dimensions type="chain-lines">     <width quantity="38" unit="mm"/>    </dimensions>    <measure type="laid-lines_in_20mm" quantity="22" unit="lines"/>   </watermark>   <watermark n="3">    <locusGrp>     <locus from="17" to="17" scheme="folios"/>     <locus from="18" to="18" scheme="folios"/>    </locusGrp>    <term type="wm_motif">Hand; flower</term>    <term type="proximity">similar to</term>    <ref>     <bibl>      <ref target="#Piccard1997"/>      <citedRange>Hand V, 1571</citedRange>     </bibl>     <placeName ref="#Madrid"/>     <date when="1541"/>    </ref>    <dimensions type="chain-lines">     <width quantity="39" unit="mm"/>    </dimensions>    <measure type="laid-lines_in_20mm" quantity="22" unit="lines"/>   </watermark>  </p> </support>

Appendix A.1.94 <supportDesc>

<supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript. [10.7.1. Object Description]
Module msdescription — Schema
Attributes Attributes
material a short project-defined name for the material composing the majority of the support
Status Optional
Datatype 
                                                                    data.enumerated
Legal values are:
paper
parchment
mixed
Contained by
msdescription: objectDesc
May contain
header: extent
msdescription: collation condition foliation support
Declaration 
element supportDesc
{
   attribute material { "paper" | "parchment" | "mixed" }?,
   ( support?, extent, foliation?, collation?, condition? )
}
Schematron checks that the <supportDesc> element only has a material attribute when it is a descendant of <msPart>
<sch:pattern> <sch:rule context="tei:msPart//tei:supportDesc">  <sch:assert test="@material">Use the material attribute for supportDesc for codicological units.</sch:assert></sch:rule> <sch:rule context="tei:msDesc/tei:physDesc/tei:objectDesc/tei:supportDesc">  <sch:report test="@material">Do not use the material attribute for supportDesc for the bookblock.</sch:report></sch:rule></sch:pattern>

Appendix A.1.95 <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 Attributesatt.global.responsibility (@cert)
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype 
xsd:ID
Contained by
transcr: facsimile
May contain
core: desc graphic
Declaration 
element surface
{
   att.global.responsibility.attribute.cert,
   attribute xml:id { xsd:ID },
   desc,
   graphic
}
Example
<surface xml:id="UGr-027-1r">  <desc>f. 1r</desc>  <graphic url="UGr-027-0003.jp2"/> </surface>

Appendix A.1.96 <teiHeader>

<teiHeader> (TEI header) supplies the descriptive and declarative information making up an electronic title page for every TEI-conformant document. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
Module header — Schema
Attributes Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Required
Datatype 
                                                                    data.language
Legal values are:
en
sv
Contained by
textstructure: TEI
May contain
header: fileDesc revisionDesc
Declaration 
element teiHeader
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang { "en" | "sv" },
   fileDesc,
   revisionDesc
}
Schematron Check that xml:lang with grc is used for Greek characters
<sch:rule context="//*[not(@xml:lang='grc' or @xml:lang='el')]"> <sch:report test="text()[matches(., '\p{IsGreek}|\p{IsGreekExtended}')]"> Use the xml:lang="grc" for Ancient Greek text and xml:lang="el" for Modern Greek text </sch:report></sch:rule>
Schematron Checks that xml:lang with grc is not used for Latin letters or numbers
<sch:rule context="//*[@xml:lang='grc' or @xml:lang='el']"> <sch:report test="text()[matches(., '[(\p{N}|\p{L})-[\p{IsGreek}\p{IsGreekExtended}]]')]"> Only characters from Greek and Greek extended chart range are allowed in elements with the xml:lang="grc" or xml:lang="el".</sch:report></sch:rule>
Schematron Check for forbidden Greek characters
<sch:pattern> <sch:rule context="//*[(@xml:lang='grc' or @xml:lang='el')]">  <sch:report test="contains(., 'Ϛ')"> Use Greek small letter stigma (U+03DB).</sch:report>  <sch:report test="contains(., 'Ϟ')"> Use Greek small letter koppa (U+03DF).</sch:report>  <sch:report test="contains(., 'Ϡ')"> Use Greek small letter sampi (U+03E1).</sch:report>  <sch:report test="contains(., ';')"> Use the semicolon (U+003B) for the Greek question mark.</sch:report>  <sch:report test="contains(., '·')"> Use the middle dot (U+00B7) for the Greek semicolon.</sch:report>  <sch:report test="contains(., "'")"> Use the right single quotation mark (U+2019) for the Greek apostrophe.</sch:report>  <sch:report test="contains(., 'ά')"> Use Greek small letter alpha with tonos (U+03AC).</sch:report>  <sch:report test="contains(., 'έ')"> Use Greek small letter epsilon with tonos (U+03AD).</sch:report>  <sch:report test="contains(., 'ή')"> Use Greek small letter eta with tonos (U+03AE).</sch:report>  <sch:report test="contains(., 'ί')"> Use Greek small letter iota with tonos (U+03AF).</sch:report>  <sch:report test="contains(., 'ό')"> Use Greek small letter omicron with tonos (U+03CC).</sch:report>  <sch:report test="contains(., 'ύ')"> Use Greek small letter upsilon with tonos (U+03CD).</sch:report>  <sch:report test="contains(., 'ώ')"> Use Greek small letter omega with tonos (U+03CE).</sch:report>  <sch:report test="contains(., 'ΐ')"> Use Greek small letter iota with dialytika and tonos (U+0390).</sch:report>  <sch:report test="contains(., 'ΰ')"> Use Greek small letter upsilon with dialytika and tonos (U+03B0).</sch:report></sch:rule></sch:pattern>
Schematron Check for the apostrophe U+0027
<sch:pattern> <sch:rule context="//*[not(@xml:lang='grc' or @xml:lang='el')]">  <sch:assert test="not(contains(., "'"))"> Use the right single quotation mark (U+2019) for apostrophe.</sch:assert></sch:rule></sch:pattern>
Schematron Check for the straight double quotation mark (U+0022)
<sch:pattern> <sch:rule context="text()">  <sch:assert test="not(contains(., '"'))"> The use of quotation marks is not allowed. Use the q element instead.</sch:assert></sch:rule></sch:pattern>
Schematron Check for the left single quotation mark (U+2018)
<sch:pattern> <sch:rule context="text()">  <sch:assert test="not(contains(., '‘'))"> The use of quotation marks is not allowed. Use the q element instead.</sch:assert></sch:rule></sch:pattern>
Example
<teiHeader xml:lang="en">  <fileDesc>   <titleStmt>    <title>Uppsala University Library, Gr. 27</title>    <respStmt xml:id="EN">     <persName ref="#EvaNys"/>     <resp key="cataloguer"/>     <resp key="encoder"/>    </respStmt>    <respStmt xml:id="PG">     <persName ref="#PatGra"/>     <resp key="cataloguer"/>     <resp key="encoder"/>    </respStmt>   </titleStmt>   <publicationStmt>    <authority>Uppsala University Library</authority>    <pubPlace>Uppsala</pubPlace>   </publicationStmt>   <sourceDesc> <!-- Source description -->   </sourceDesc>  </fileDesc> </teiHeader>
Note One of the few elements unconditionally required in any TEI document.

Appendix A.1.97 <term>

<term> contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4. Terms, Glosses, Equivalents, and Descriptions]
Module core — Schema
Attributes Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Schematron
<sch:rule context="//tei:term[@type='proximity']"> <sch:assert test="text()='similar to' or text()='very similar to' or text()='identical with'"> Permitted values are "similar to", "very similar to", or "identical with".</sch:assert></sch:rule>
Datatype 
                                                                    data.enumerated
Legal values are:
layout
proximity
Terms used to describe proximity: "similar to", "very similar to", or "identical with"
script
Description of script
wm_motif
Watermark motif, in English
wm_term
Watermark term according to Briquet, in French
Member of
model.emphLike
Contained by
core: note p
header: handNote
msdescription: additions catchwords decoNote foliation layout musicNotation signatures watermark
May contain
msdescription: material
Declaration 
element term
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   attribute type
   {
      "layout" | "proximity" | "script" | "wm_motif" | "wm_term"
   }?
   >>
   tei:constraintSpec
   [
      ident = "term.proximity"
      scheme = "isoschematron"
      " "
      """ Permitted values are "similar to", "very similar to", or "identical with"."""
   ],
   ( material | text )*
}
Example
<term type="wm_motif">Hat</term>

Appendix A.1.98 <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
Contained by
textstructure: TEI
May contain
textstructure: body
Declaration 
element text { body }
Example
<text>  <body>   <div xml:id="text_65b">    <head>     <title>65b: Chronicon breve</title>     <locus scheme="folios" from="283v" to="283v"/>    </head>    <p xml:lang="grc">ὁ ἔννατος ὁ σουλ<lb/>τα Παγιάζητη <lb/>ὃς ἐπῆρε τη Μεθωκορωνι.    <lb/>δέκατος υἱός του <lb/>ὁ Σελημης ὃς εδουλεσε <lb/>Περσια και Σι<lb/>ρια ὃλη.    <lb/>δέκατος πρῶτος <lb/>υἱός του ὁ Σουλεημαν <lb/>σούλτανος ὁς ἐπηραι    <lb/>τὴν Ροδο καὶ ἑαλοσι <lb/>καὶ τὴν Οὐγκρία το <lb/>α φ κ ϛ ετος ἀπο χῦ    <lb/>ἀγουστου κθ <lb/>... ὁ πολεμος</p>   </div>  </body> </text>
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.

Appendix A.1.99 <textLang/>

<textLang/> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.11.2.4. Imprint, Size of a Document, and Reprint Information 10.6.6. Languages and Writing Systems]
Module core — Schema
Attributes Attributes
mainLang (main language) supplies a code which identifies the chief language used in the bibliographic work.
Status Required
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
la
Latin
otherLangs (other languages) one or more codes identifying any other languages used in the bibliographic work.
Status Optional
Datatype 0–∞ occurrences of 
                                                                    data.language
separated by whitespace
Legal values are:
grc
Ancient Greek (to 1453)
la
Latin
Contained by
msdescription: msItem
May contain Empty element
Declaration 
element textLang
{
   attribute mainLang { "grc" | "la" },
   attribute otherLangs { list { ( "grc" | "la" )* } }?,
   empty
}
Example
<textLang mainLang="grc"/>
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.

Appendix A.1.100 <title>

<title> contains a title for any kind of work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Module core — Schema
Attributes Attributesatt.global.responsibility (@cert)
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
key provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Derived from att.canonical
Status Optional
Datatype 
                                                                    data.text
ref (reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.
Derived from att.canonical
Status Optional
Datatype 1–∞ occurrences of 
                                                                    data.pointer
separated by whitespace
type classifies the title according to some convenient typology.
Derived from att.typed
Status Optional
Datatype 
                                                                    data.enumerated
Legal values are:
uniform
(uniform) standardized distinctive title from Pinakes [Default]
alt
(alternate) alternate title by which the work is also known
desc
(descriptive) descriptive paraphrase in English 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.
Member of
model.emphLike
Contained by
core: head item
header: titleStmt
msdescription: additions msItem
May contain
namesdates: persName
transcr: supplied
Declaration 
element title
{
   att.global.responsibility.attribute.cert,
   attribute xml:lang
   {
      "grc" | "en" | "fr" | "de" | "el" | "it" | "la" | "nl" | "sp" | "sv"
   }?,
   attribute key { data.text }?,
   attribute ref { list { data.pointer+ } }?,
   attribute type { "uniform" | "alt" | "desc" }?,
   ( text | supplied | persName )*
}
Schematron
<sch:rule context="tei:title/@key"> <sch:report test="matches(., 'TLG \p{N}') or matches(., 'TLG_\p{N}')"> Do not use space or underscore between TLG and the number </sch:report> <sch:report test="matches(., 'BHG \p{N}') or matches(., 'BHG_\p{N}')"> Do not use space or underscore between BHG and the number </sch:report> <sch:report test="matches(., 'CPG \p{N}') or matches(., 'CPG_\p{N}')"> Do not use space or underscore between CPG and the number </sch:report></sch:rule>
Example
<title ref="http://pinakes.irht.cnrs.fr/notices/oeuvre/id/3267" type="uniform" xml:lang="la">De natura animalium libri XVII</title>
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.

Appendix A.1.101 <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: respStmt title
Declaration 
element titleStmt { title, respStmt* }
Example
<titleStmt>  <title>Uppsala University Library, Gr. 27</title>  <respStmt xml:id="EN">   <persName ref="#EvaNys"/>   <resp key="cataloguer"/>   <resp key="encoder"/>  </respStmt>  <respStmt xml:id="PG">   <persName ref="#PatGra"/>   <resp key="cataloguer"/>   <resp key="encoder"/>  </respStmt> </titleStmt>

Appendix A.1.102 <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.4.3. Additions, Deletions, and Omissions]
Module core — Schema
Attributes Attributes
unit names the unit used for the measurement
Derived from att.dimensions
Status Required
Datatype 
                                                                    data.enumerated
Legal values are:
chars
characters
lines
mm
quantity specifies the length in the units specified
Derived from att.dimensions
Status Required
Datatype 
                                                                    data.numeric
atLeast gives a minimum estimated value for the approximate measurement.
Derived from att.ranging
Status Optional
Datatype 
                                                                    data.numeric
atMost gives a maximum estimated value for the approximate measurement.
Derived from att.ranging
Status Optional
Datatype 
                                                                    data.numeric
reason indicates why the material is hard to transcribe.
Status Required
Datatype 1–∞ occurrences of 
                                                                    data.word
separated by whitespace
Legal values are:
illegible
<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. Typical examples might thus include faded, illegible, eccentric_ductus background_noise, passing_truck,etc.
Member of
model.pPart.transcriptional
Contained by
core: foreign
msdescription: additions colophon explicit finalRubric incipit
May contain Empty element
Declaration 
element unclear
{
   attribute unit { "chars" | "lines" | "mm" },
   attribute quantity { data.numeric },
   attribute atLeast { data.numeric }?,
   attribute atMost { data.numeric }?,
   attribute reason { list { "illegible"+ } },
   empty
}
Example
<gap reason="damage" quantity="20" unit="mm"/> <unclear reason="illegible" quantity="60" unit="mm"/> ἰορδάνης ἰορδάνης ἰορδάνου τελ<unclear reason="illegible" quantity="30" unit="mm"/> αἰδέσιμος, ἀξιοτίμητος

Appendix A.1.103 <watermark>

<watermark> contains a word or phrase describing a watermark or similar device. [10.3.3. Watermarks and Stamps]
Module msdescription — Schema
Attributes Attributesatt.global.responsibility (@cert)
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Optional
Datatype 
                                                                    data.text
Member of
model.pPart.msdesc
Contained by
core: p ref
msdescription: additions
May contain
core: measure note ref term
msdescription: dimensions locusGrp
Declaration 
element watermark
{
   att.global.responsibility.attribute.cert,
   attribute n { data.text }?,
   ( locusGrp*, term*, ref*, dimensions*, measure*, note? )*
}
Schematron Check if <watermark> is used in <bindingDesc>
<sch:rule context="tei:bindingDesc"> <sch:report test="*//tei:watermark"> Describe watermarks for the flyleaves in the support element. </sch:report></sch:rule>
Schematron Check that n starts with a digit
<sch:pattern> <sch:rule context="tei:watermark">  <sch:assert test="@n[matches(., '\p{N}|\p{N}\p{Ll}')]"> The n attribute should contain digits, or digits and lower-case letters.</sch:assert></sch:rule></sch:pattern>
Example
<watermark n="2a">  <locusGrp>   <locus from="97" to="97" scheme="folios"/>   <locus from="114" to="114" scheme="folios"/>  </locusGrp>  <locusGrp>   <locus from="98" to="98" scheme="folios"/>   <locus from="113" to="113" scheme="folios"/>  </locusGrp>  <locusGrp>   <locus from="100" to="100" scheme="folios"/>   <locus from="111" to="111" scheme="folios"/>  </locusGrp>  <term type="wm_motif">Hat</term>  <term type="proximity">identical with</term>  <ref>   <bibl>    <ref target="#Harlfinger1974"/>    <citedRange>Chapeau 28 (left, from this manuscript)</citedRange>   </bibl>  </ref> </watermark>

Appendix A.1.104 <width/>

<width/> contains a measurement measured along the axis parallel to the bottom of the written surface, i.e. perpendicular to the spine of a book or codex. [10.3.4. Dimensions]
Module msdescription — Schema
Attributes Attributes
unit names the unit used for the measurement
Derived from att.dimensions
Status Required
Datatype 
                                                                    data.enumerated
Legal values are:
mm
quantity specifies the length in the units specified
Derived from att.dimensions
Status Optional
Datatype 
                                                                    data.numeric
min where the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Derived from att.ranging
Status Optional
Datatype 
                                                                    data.numeric
max where the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Derived from att.ranging
Status Optional
Datatype 
                                                                    data.numeric
Member of
model.measureLike
Contained by
msdescription: additions dimensions
May contain Empty element
Declaration 
element width
{
   attribute unit { "mm" },
   attribute quantity { data.numeric }?,
   attribute min { data.numeric }?,
   attribute max { data.numeric }?,
   empty
}
Schematron checks that the <width/> element has either a quantity or min/max attributes.
<sch:pattern> <sch:rule context="tei:width">  <sch:assert test="@quantity or (@min and @max)">The width element must have either @quantity or @min/@max. </sch:assert></sch:rule></sch:pattern>
Example
<dimensions type="binding">  <height quantity="240" unit="mm"/>  <width quantity="185" unit="mm"/>  <depth quantity="65" unit="mm"/> </dimensions>

Appendix A.2 Model classes

Appendix A.2.1 model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.11. Bibliographic Citations and References]
Module tei — Schema
Used by
model.inter
Members bibl listBibl msDesc

Appendix A.2.2 model.dateLike

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

Appendix A.2.3 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
Members model.lLike model.pLike [p]
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.

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

Appendix A.2.5 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
macro.specialPara
Members model.global.edit [gap] model.global.meta model.milestoneLike [lb] model.noteLike [note]

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

Appendix A.2.7 model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.9. Graphics and Other Non-textual Components]
Module tei — Schema
Used by
model.phrase
Members formula graphic

Appendix A.2.8 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
msDesc
Members head

Appendix A.2.9 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
model.highlighted model.limitedPhrase
Members hi

Appendix A.2.10 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]

Appendix A.2.11 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
macro.specialPara
Members model.biblLike [bibl listBibl msDesc] model.egLike model.labelLike [desc] model.listLike [list] model.oddDecl model.qLike [model.quoteLike [quote]] model.stageLike

Appendix A.2.12 model.labelLike

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

Appendix A.2.13 model.limitedPhrase

model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
Module tei — Schema
Used by
Members model.emphLike [foreign term title] model.hiLike [hi] model.pPart.data [model.addressLike model.dateLike [date] model.measureLike [depth height measure num width] model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [country placeName settlement]] idno]] model.pPart.editorial [ex] model.pPart.msdesc [catchwords dimensions locus locusGrp material origDate origPlace signatures watermark] model.phrase.xml model.ptrLike [ref]

Appendix A.2.14 model.listLike

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

Appendix A.2.15 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.5.3. Numbers and Measures]
Module tei — Schema
Used by
model.pPart.data
Members depth height measure num width

Appendix A.2.16 model.milestoneLike

model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.10.3. Milestone Elements]
Module tei — Schema
Used by
model.global
Members lb

Appendix A.2.17 model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Module tei — Schema
Used by
model.pPart.data
Members model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [country placeName settlement]] idno
Note A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

Appendix A.2.18 model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]
Module tei — Schema
Used by
model.nameLike
Members persName
Note This class is used in the content model of elements which reference names of people or organizations.

Appendix A.2.19 model.noteLike

model.noteLike groups globally-available note-like elements. [3.8. Notes, Annotation, and Indexing]
Module tei — Schema
Used by
model.global
Members note

Appendix A.2.20 model.pLike

model.pLike groups paragraph-like elements.
Module tei — Schema
Used by
model.divPart
Members p

Appendix A.2.21 model.pPart.data

model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]
Module tei — Schema
Used by
model.limitedPhrase model.phrase
Members model.addressLike model.dateLike [date] model.measureLike [depth height measure num width] model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [country placeName settlement]] idno]

Appendix A.2.22 model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.4. Simple Editorial Changes]
Module tei — Schema
Used by
model.phrase
Members model.pPart.editorial [ex] model.pPart.transcriptional [add del sic supplied unclear]

Appendix A.2.23 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.4. Simple Editorial Changes]
Module tei — Schema
Used by
model.limitedPhrase model.pPart.edit
Members ex

Appendix A.2.24 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 locus locusGrp material origDate origPlace signatures watermark

Appendix A.2.25 model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.4. Simple Editorial Changes]
Module tei — Schema
Used by
model.pPart.edit
Members add del sic supplied unclear

Appendix A.2.26 model.phrase

model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]
Module tei — Schema
Used by
macro.specialPara
Members model.graphicLike [formula graphic] model.highlighted [model.emphLike [foreign term title] model.hiLike [hi]] model.lPart model.pPart.data [model.addressLike model.dateLike [date] model.measureLike [depth height measure num width] model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [country placeName settlement]] idno]] model.pPart.edit [model.pPart.editorial [ex] model.pPart.transcriptional [add del sic supplied unclear]] model.pPart.msdesc [catchwords dimensions locus locusGrp material origDate origPlace signatures watermark] model.phrase.xml model.ptrLike [ref] model.segLike model.specDescLike
Note This class of elements can occur within paragraphs, list items, lines of verse, etc.

Appendix A.2.27 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
Members country placeName settlement

Appendix A.2.28 model.placeStateLike

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

Appendix A.2.29 model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.6. Simple Links and Cross-References]
Module tei — Schema
Used by
model.limitedPhrase model.phrase
Members ref

Appendix A.2.30 model.qLike

model.qLike groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. Highlighting and Quotation]
Module tei — Schema
Used by
model.inter
Members model.quoteLike [quote]

Appendix A.2.31 model.quoteLike

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

Appendix A.3 Attribute classes

Appendix A.3.1 att.canonical

att.canonical provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced.
Module tei — Schema
Members att.naming [att.personal]
Attributes Attributes
key provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Status Optional
Datatype 
                                                                    data.text
<author>  <name key="name 427308"   type="organisation">[New Zealand Parliament, Legislative Council]</name> </author>
<author>  <name key="Hugo, Victor (1802-1885)"   ref="http://www.idref.fr/026927608">Victor Hugo</name> </author>
Note The value may be a unique identifier from a database, or any other externally-defined string identifying the referent. No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project. For the same reason, this attribute is not recommended in data interchange, since there is no way of ensuring that the values used by one project are distinct from those used by another. In such a situation, a preferable approach for magic tokens which follows standard practice on the Web is to use a ref attribute whose value is a tag URI as defined in RFC 4151.
ref (reference) provides an explicit means of locating a full definition for the entity being named by means of one or more URIs.
Status Optional
Datatype 1–∞ occurrences of 
                                                                    data.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.

Appendix A.3.2 att.citing

att.citing provides attributes for specifying the specific part of a bibliographic item being cited.
Module tei — Schema
Members citedRange
Attributes Attributes
unit identifies the unit of information conveyed by the element, e.g. columns, pages, volume.
Status Recommended
Datatype 
                                                                    data.enumerated
Legal values are:
volume
issue
page
footnote
line
chapter
column
folio
plate
number
Use e.g. for RGK numbers or ruling patterns i Leroy-Sautel
from specifies the starting point of the range of units indicated by the unit attribute.
Status Recommended
Datatype 
                                                                    data.word
to specifies the end-point of the range of units indicated by the unit attribute.
Status Recommended
Datatype 
                                                                    data.word

Appendix A.3.3 att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events.
Module tei — Schema
Members date
Attributes Attributes  att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)

Appendix A.3.4 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.5.4. Dates and Times 13.3.6. Dates and Times]
Module tei — Schema
Members att.datable [date]
Attributes Attributes
when supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype 
                                                                    data.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 
                                                                    data.temporal.w3c
notAfter specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype 
                                                                    data.temporal.w3c
from indicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype 
                                                                    data.temporal.w3c
to indicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype 
                                                                    data.temporal.w3c
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.

Appendix A.3.5 att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Module tei — Schema
Members att.editLike
Attributes Attributes  att.ranging (@atLeast, @atMost, @min, @max)
unit names the unit used for the measurement
Status Optional
Datatype 
                                                                    data.enumerated
Legal values are:
mm
millimeters
chars
characters
lines
lines of text
quantity specifies the length in the units specified
Status Optional
Datatype 
                                                                    data.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 
                                                                    data.text
<gap extent="5 words"/>
<height extent="half the page"/>

Appendix A.3.6 att.global

att.global provides attributes common to all elements in the TEI encoding scheme.
Module tei — Schema
Members additions
Attributes Attributes  att.global.rendition (@rend) att.global.facs (@facs) att.global.responsibility (@cert)
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
Datatype 
xsd:ID
Note The xml:id attribute may be used to specify a canonical reference for an element; see section 3.10. Reference Systems.
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Status Optional
Datatype 
                                                                    data.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 
                                                                    data.language
Legal values are:
grc
Ancient Greek (to 1453)
en
English
fr
French
de
German
el
Modern Greek
it
Italian
la
Latin
nl
Dutch
sp
Spanish
sv
Swedish
<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.The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry . For a good general overview of the construction of language tags, see http://www.w3.org/International/articles/language-tags/ , and for a practical step-by-step guide, see http://www.w3.org/International/questions/qa-choosing-language-tags .
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.

Appendix A.3.7 att.global.facs

att.global.facs groups elements corresponding with all or part of an image, because they contain an alternative representation of it, typically but not necessarily a transcription of it. [11.1. Digital Facsimiles]
Module transcr — Schema
Members att.global [additions]
Attributes Attributes
facs (facsimile) points to all or part of an image which corresponds with the content of the element.
Status Optional
Datatype 1–∞ occurrences of 
                                                                    data.pointer
separated by whitespace

Appendix A.3.8 att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme.
Module tei — Schema
Members att.global [additions]
Attributes Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
Datatype 1–∞ occurrences of 
                                                                    data.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.

Appendix A.3.9 att.global.responsibility

att.global.responsibility provides attributes indicating the agency responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it.
Module tei — Schema
Members att.global [additions]
Attributes Attributes
cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
Status Optional
Datatype 
                                                                    data.certainty

Appendix A.3.10 att.media

att.media provides attributes for specifying display and related properties of external media.
Module tei — Schema
Members graphic
Attributes Attributes

Appendix A.3.11 att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc.
Module tei — Schema
Members att.personal
Attributes Attributes  att.canonical (@key, @ref)
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 
                                                                    data.enumerated
separated by whitespace
Legal values are:
cataloguer
librarian
scribe

Appendix A.3.12 att.ranging

att.ranging provides attributes for describing numerical ranges.
Module tei — Schema
Members att.dimensions [att.editLike]
Attributes Attributes
atLeast gives a minimum estimated value for the approximate measurement.
Status Optional
Datatype 
                                                                    data.numeric
atMost gives a maximum estimated value for the approximate measurement.
Status Optional
Datatype 
                                                                    data.numeric
min where the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Status Optional
Datatype 
                                                                    data.numeric
max where the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Status Optional
Datatype 
                                                                    data.numeric

Appendix A.3.13 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 Attributes
url (uniform resource locator) specifies the URL from which the media concerned may be obtained.
Status Required
Datatype 
                                                                    data.pointer

Appendix A.4 Macros

Appendix A.4.1 data.certainty

data.certainty defines the range of attribute values expressing a degree of certainty.
Module tei — Schema
Used by
Element:
Declaration 
data.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. For more precise indication, data.probability may be used instead or in addition.

Appendix A.4.2 data.count

data.count defines the range of attribute values used for a non-negative integer value used as a count.
Module tei — Schema
Used by
Element:
Declaration 
data.count = xsd:nonNegativeInteger
Note Only positive integer values (including zero) are permitted

Appendix A.4.3 data.enumerated

data.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Module tei — Schema
Used by
Element:
Declaration 
data.enumerated = data.word
Note Attributes using this datatype must contain a single word matching the pattern defined for this datatype: for example it cannot include whitespace but may begin with digits. 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.

Appendix A.4.4 data.language

data.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:
Declaration 
data.language = xsd:language | ""
Note The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 4646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.
language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at http://www.iana.org/assignments/language-subtag-registry . It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at http://unicode.org/iso15924/iso15924-codes.html . The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case. The list of codes can be found at http://www.iso.org/iso/home/standards/country_codes/iso-3166-1_decoding_table.htm . 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.

Appendix A.4.5 data.numeric

data.numeric defines the range of attribute values used for numeric values.
Module tei — Schema
Used by
Element:
Declaration 
data.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.

Appendix A.4.6 data.pointer

data.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:
Declaration 
data.pointer = xsd:anyURI
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/

Appendix A.4.7 data.temporal.w3c

data.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
Element:
Declaration 
data.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.

Appendix A.4.8 data.text

data.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:
Declaration 
data.text = string
Note Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

Appendix A.4.9 data.version

data.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:
Declaration 
data.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
Note The value of this attribute follows the pattern specified by the Unicode consortium for its version number ( http://unicode.org/versions/ ). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

Appendix A.4.10 data.word

data.word defines the range of attribute values expressed as a single word or token.
Module tei — Schema
Used by
data.enumerated Element:
Declaration 
data.word = token { pattern = "(\p{L}|\p{N}|\p{P}|\p{S})+" }
Note Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

Appendix A.4.11 data.xTruthValue

data.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:
Declaration 
data.xTruthValue = xsd:boolean | "unknown" | "inapplicable"
Note In cases where where uncertainty is inappropriate, use the datatype data.TruthValue.

Appendix A.4.12 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
additions
Declaration 
macro.specialPara =
   (
      text
    | model.gLike
    | model.phrase
    | model.inter
    | model.divPart
    | model.global
   )*

Appendix A.4.13 macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Module tei — Schema
Used by
ex institution msName repository
Declaration 
macro.xtext = ( text | model.gLike )*
Home 
Patrik Granholm and Eva Nyström. Date: 2014-11-27