Rhodomanologia

Table of contents

Rhodomanologia ODD

1. Elements

1.1. <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Module textstructure
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
rendition points to a description of the rendering or presentation used for this element in the source text.
Derived from att.global.rendition
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
version specifies the version number of the TEI Guidelines against which this document is valid.
Status Required
Datatype teidata.version
Note

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

Contained by
textstructure: TEI
May contain
header: teiHeader
textstructure: TEI text
Note

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>The shortest TEI Document Imaginable</title>    </titleStmt>    <publicationStmt>     <p>First published as part of TEI P2, this is the P5          version using a namespace.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <text>   <body>    <p>This is about the shortest TEI document imaginable.</p>   </body>  </text> </TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>A TEI Document containing four page images </title>    </titleStmt>    <publicationStmt>     <p>Unpublished demonstration file.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <facsimile>   <graphic url="page1.png"/>   <graphic url="page2.png"/>   <graphic url="page3.png"/>   <graphic url="page4.png"/>  </facsimile> </TEI>
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:ns prefix="xs"  uri="http://www.w3.org/2001/XMLSchema"/>
Schematron
<sch:ns prefix="rng"  uri="http://relaxng.org/ns/structure/1.0"/>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="teiHeader"/>
  <alternate maxOccurs="1" minOccurs="1">
   <sequence maxOccurs="1" minOccurs="1">
    <classRef key="model.resource"
     maxOccurs="unbounded" minOccurs="1"/>
    <elementRef key="TEI"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
   <elementRef key="TEI"
    maxOccurs="unbounded" minOccurs="1"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element TEI
{
   attribute xml:id { text },
   attribute rendition { list { + } },
   attribute version { text },
   ( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) )
}

1.2. <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Module core
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Note

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

Example
<choice>  <expan>North Atlantic Treaty Organization</expan>  <abbr cert="low">NorATO</abbr>  <abbr cert="high">NATO</abbr>  <abbr cert="highxml:lang="fr">OTAN</abbr> </choice>
Example
<choice>  <abbr>SPQR</abbr>  <expan>senatus populusque romanorum</expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element abbr { tei_macro.phraseSeq }

1.3. <additional>

<additional> (additional) groups additional information, combining bibliographic information about a manuscript or other object, or surrogate copies of it, with curatorial or administrative information. [10.9. Additional Information]
Module msdescription
Contained by
msdescription: msDesc
namesdates: object
May contain
core: listBibl
Example
<additional>  <adminInfo>   <recordHist>    <p> <!-- record history here -->    </p>   </recordHist>   <custodialHist>    <p> <!-- custodial history here -->    </p>   </custodialHist>  </adminInfo>  <surrogates>   <p> <!-- information about surrogates here -->   </p>  </surrogates>  <listBibl>   <bibl> <!-- ... -->   </bibl> <!-- full bibliography here -->  </listBibl> </additional>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="adminInfo" minOccurs="0"/>
  <elementRef key="surrogates"
   minOccurs="0"/>
  <elementRef key="listBibl" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element additional { adminInfo?, surrogates?, tei_listBibl? }

1.4. <analytic>

<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
Module core
Contained by
May contain
Note

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

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

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope>377–380</biblScope>  </monogr> </biblStruct>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="author"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="date"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element analytic
{
   (
      tei_author
    | editor
    | tei_respStmt
    | tei_title
    | tei_model.ptrLike
    | tei_date
    | tei_textLang
    | tei_idno
    | tei_availability
   )*
}

1.5. <anchor>

<anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.5. Correspondence and Alignment]
Module linking
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Required
Datatype teidata.text
corresp (corresponds) points to elements that correspond to the current element in some way.
Derived from att.global.linking
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
footnote
Anker für Sachanmerkung
Member of
Contained by
May contain Empty element
Note

On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.

Example
<s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s> <s>Help me find it.<ptr target="#A234"/> </s>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element anchor
{
   attribute xml:id { text },
   attribute n { text },
   attribute corresp { list { + } },
   attribute type { "footnote" },
   empty
}

1.6. <author>

<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Module core
Member of
Contained by
header: titleStmt
msdescription: msItem
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Note

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.

In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.

Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

Example
<author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author>  <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author>  <orgName key="BBC">British Broadcasting    Corporation</orgName>: Radio 3 Network </author>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element author { tei_macro.phraseSeq }

1.7. <availability>

<availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Module header
Member of
Contained by
May contain
core: p
header: licence
Note

A consistent format should be adopted

Example
<availability status="restricted">  <p>Available for academic research purposes only.</p> </availability> <availability status="free">  <p>In the public domain</p> </availability> <availability status="restricted">  <p>Available under licence from the publishers.</p> </availability>
Example
<availability>  <licence target="http://opensource.org/licenses/MIT">   <p>The MIT License      applies to this document.</p>   <p>Copyright (C) 2011 by The University of Victoria</p>   <p>Permission is hereby granted, free of charge, to any person obtaining a copy      of this software and associated documentation files (the "Software"), to deal      in the Software without restriction, including without limitation the rights      to use, copy, modify, merge, publish, distribute, sublicense, and/or sell      copies of the Software, and to permit persons to whom the Software is      furnished to do so, subject to the following conditions:</p>   <p>The above copyright notice and this permission notice shall be included in      all copies or substantial portions of the Software.</p>   <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR      IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,      FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE      AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER      LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,      OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN      THE SOFTWARE.</p>  </licence> </availability>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element availability { ( tei_model.availabilityPart | tei_model.pLike )+ }

1.8. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Module textstructure
Contained by
textstructure: text
May contain
analysis: interp interpGrp
linking: anchor
namesdates: listObject
textstructure: closer div
transcr: space
Note

Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the <back> and <front> elements are identical.

Example
<back>  <div type="appendix">   <head>The Golden Dream or, the Ingenuous Confession</head>   <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets      and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she      had like to have been, too fond of Money <!-- .... -->   </p>  </div> <!-- ... -->  <div type="epistle">   <head>A letter from the Printer, which he desires may be inserted</head>   <salute>Sir.</salute>   <p>I have done with your Copy, so you may return it to the Vatican, if you please;    <!-- ... -->   </p>  </div>  <div type="advert">   <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr      Newbery's at the Bible and Sun in St Paul's Church-yard.</head>   <list>    <item n="1">The Christmas Box, Price 1d.</item>    <item n="2">The History of Giles Gingerbread, 1d.</item> <!-- ... -->    <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,        10 Vol, Pr. bound 1l.</item>   </list>  </div>  <div type="advert">   <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.      Paul's Church-Yard.</head>   <list>    <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.        6d</item>    <item n="2">Dr. Hooper's Female Pills, 1s.</item> <!-- ... -->   </list>  </div> </back>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.pLike"/>
   <classRef key="model.listLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate maxOccurs="1" minOccurs="0">
   <sequence maxOccurs="1" minOccurs="1">
    <classRef key="model.div1Like"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.frontPart"/>
     <classRef key="model.div1Like"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <classRef key="model.divLike"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.frontPart"/>
     <classRef key="model.divLike"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence maxOccurs="1" minOccurs="0">
   <classRef key="model.divBottomPart"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.divBottomPart"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element back
{
   (
      tei_model.frontPart
    | tei_model.pLike.front
    | tei_model.pLike
    | tei_model.listLike
    | tei_model.global
   )*,
   (
      (
         tei_model.div1Like,
         ( tei_model.frontPart | tei_model.div1Like | tei_model.global )*
      )
    | (
         tei_model.divLike,
         ( tei_model.frontPart | tei_model.divLike | tei_model.global )*
      )
   )?,
   ( tei_model.divBottomPart, ( tei_model.divBottomPart | tei_model.global )* )?
}

1.9. <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
Member of
Contained by
linking: seg
msdescription: msItem provenance support
namesdates: object
textcrit: lem
textstructure: body div
transcr: supplied surplus
May contain
Note

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

Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
<bibl>  <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher>  <date>1968</date>. </bibl>
Example
<bibl subtype="book_chaptertype="article"  xml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element bibl
{
   attribute xml:id { text },
   (
      text
    | tei_model.gLike
    | tei_model.highlighted
    | tei_model.pPart.data
    | tei_model.pPart.edit
    | tei_model.segLike
    | tei_model.ptrLike
    | tei_model.biblPart
    | tei_model.global
   )*
}

1.10. <biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Module core
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Note

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff</biblScope>.

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

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

1.11. <biblStruct>

<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
print
Überlieferungsträger: Druck
subtype (subtype) provides a sub-categorization of the element, if needed
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
letter
Unterkategorie Brief
Member of
Contained by
linking: seg
msdescription: msItem provenance support
namesdates: object
textcrit: lem
textstructure: body div
transcr: supplied surplus
May contain
Example
<biblStruct>  <monogr>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <edition>first edition</edition>   <imprint>    <publisher>Yale University Press</publisher>    <pubPlace>New Haven and London</pubPlace>    <date>1990</date>   </imprint>  </monogr> </biblStruct>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="analytic"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="monogr"/>
   <elementRef key="series"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element biblStruct
{
   attribute type { "print" },
   attribute subtype { "letter" }?,
   (
      tei_analytic*,
      ( tei_monogr, series* )+,
      ( tei_model.noteLike | tei_model.ptrLike | relatedItem | citedRange )*
   )
}

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
Contained by
textstructure: text
May contain
analysis: interp interpGrp
linking: anchor
msdescription: msDesc
namesdates: listObject
textstructure: closer div opener
transcr: space
Example
<body>  <l>Nu scylun hergan hefaenricaes uard</l>  <l>metudæs maecti end his modgidanc</l>  <l>uerc uuldurfadur sue he uundra gihuaes</l>  <l>eci dryctin or astelidæ</l>  <l>he aerist scop aelda barnum</l>  <l>heben til hrofe haleg scepen.</l>  <l>tha middungeard moncynnæs uard</l>  <l>eci dryctin æfter tiadæ</l>  <l>firum foldu frea allmectig</l>  <trailer>primo cantauit Cædmon istud carmen.</trailer> </body>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="1" minOccurs="0">
   <classRef key="model.divTop"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence maxOccurs="1" minOccurs="0">
   <classRef key="model.divGenLike"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate maxOccurs="1" minOccurs="1">
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.divLike"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.div1Like"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <alternate maxOccurs="1" minOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
    <alternate maxOccurs="1" minOccurs="0">
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <classRef key="model.divLike"/>
      <alternate maxOccurs="unbounded"
       minOccurs="0">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <classRef key="model.div1Like"/>
      <alternate maxOccurs="unbounded"
       minOccurs="0">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element body
{
   tei_model.global*,
   ( tei_model.divTop, ( tei_model.global | tei_model.divTop )* )?,
   ( tei_model.divGenLike, ( tei_model.global | tei_model.divGenLike )* )?,
   (
      ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+
    | ( tei_model.div1Like, ( tei_model.global | tei_model.divGenLike )* )+
    | (
         ( ( schemaSpec | tei_model.common ), tei_model.global* )+,
         (
            ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+
          | (
               tei_model.div1Like,
               ( tei_model.global | tei_model.divGenLike )*
            )+
         )?
      )
   ),
   ( tei_model.divBottom, tei_model.global* )*
}

1.13. <change>

<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]
Module header
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 teidata.pointer separated by whitespace
Legal values are:
#dhbuw
DH (Bergische Universität Wuppertal)
#editor
EditorIn
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 teidata.temporal.w3c
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
created
Bearbeitungsstand: Datei erstellt
hasTranscript
Bearbeitungsstand: Transkription erstellt
readyForQMMeta
Bearbeitungsstand: Auszeichnung (Metadaten) vollständig
readyForQMTrans
Bearbeitungsstand: Auszeichnung (Transkription) vollständig
readyForPublicationMeta
Bearbeitungsstand: Bereit zur Veröffentlichung (Metadaten)
readyForPublicationTrans
Bearbeitungsstand: Bereit zur Veröffentlichung (Transkription)
update
Bearbeitungsstand: Änderungen nach Veröffentlichung
Contained by
header: revisionDesc
May contain
Note

The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

Example
<titleStmt>  <title> ... </title>  <editor xml:id="LDB">Lou Burnard</editor>  <respStmt xml:id="BZ">   <resp>copy editing</resp>   <name>Brett Zamir</name>  </respStmt> </titleStmt> <!-- ... --> <revisionDesc status="published">  <change status="publicwhen="2008-02-02"   who="#BZ">Finished chapter 23</change>  <change status="draftwhen="2008-01-02"   who="#BZ">Finished chapter 2</change>  <change n="P2.2when="1991-12-21"   who="#LDB">Added examples to section 3</change>  <change when="1991-11-11who="#MSM">Deleted chapter 10</change> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange>    <change xml:id="DRAFT1">First draft in pencil</change>    <change notBefore="1880-12-09"     xml:id="DRAFT2">First revision, mostly        using green ink</change>    <change notBefore="1881-02-13"     xml:id="DRAFT3">Final corrections as        supplied to printer.</change>   </listChange>  </creation> </profileDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element change
{
   attribute who { list { ( "#dhbuw" | "#editor" )+ } },
   attribute when { text },
   attribute type
   {
      "created"
    | "hasTranscript"
    | "readyForQMMeta"
    | "readyForQMTrans"
    | "readyForPublicationMeta"
    | "readyForPublicationTrans"
    | "update"
   },
   tei_macro.specialPara
}

1.14. <closer>

<closer> (closer) groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions]
Module textstructure
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
center
Ausrichtung im Original: zentriert
right
Ausrichtung im Original: rechtsbündig
Member of
Contained by
core: lg list
textstructure: back body div front
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
<div type="letter">  <p> perhaps you will favour me with a sight of it when convenient.</p>  <closer>   <salute>I remain, &amp;c. &amp;c.</salute>   <signed>H. Colburn</signed>  </closer> </div>
Example
<div type="chapter">  <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="signed"/>
  <elementRef key="dateline"/>
  <elementRef key="salute"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element closer
{
   attribute rend { list { ( "center" | "right" )+ } }?,
   (
      text
    | tei_model.gLike
    | signed
    | dateline
    | salute
    | tei_model.phrase
    | tei_model.global
   )*
}

1.15. <correspAction>

<correspAction> (correspondence action) contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. [2.4.6. Correspondence Description]
Module header
Attributes
type describes the nature of the action.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
sent
Bei Briefen: Absender
received
Bei Briefen: Empfänger
Member of
Contained by
header: correspDesc
May contain
Example
<correspAction type="sent">  <persName>Adelbert von Chamisso</persName>  <settlement>Vertus</settlement>  <date when="1807-01-29"/> </correspAction>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.correspActionPart"
   maxOccurs="unbounded" minOccurs="1"/>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element correspAction
{
   attribute type { "sent" | "received" },
   ( tei_model.correspActionPart+ | tei_model.pLike+ )
}

1.16. <correspDesc>

<correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence. [2.4.6. Correspondence Description]
Module header
Member of
Contained by
header: profileDesc
May contain
core: note p
Example
<correspDesc>  <correspAction type="sent">   <persName>Carl Maria von Weber</persName>   <settlement>Dresden</settlement>   <date when="1817-06-23">23 June 1817</date>  </correspAction>  <correspAction type="received">   <persName>Caroline Brandt</persName>   <settlement>Prag</settlement>  </correspAction>  <correspContext>   <ref target="http://www.weber-gesamtausgabe.de/A041209"    type="prev">Previous letter of   <persName>Carl Maria von Weber</persName>      to <persName>Caroline Brandt</persName>:   <date from="1817-06-19to="1817-06-20">June 19/20, 1817</date>   </ref>   <ref target="http://www.weber-gesamtausgabe.de/A041217"    type="next">Next letter of   <persName>Carl Maria von Weber</persName> to   <persName>Caroline Brandt</persName>:   <date when="1817-06-27">June 27, 1817</date>   </ref>  </correspContext> </correspDesc>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.correspDescPart"
   maxOccurs="unbounded" minOccurs="1"/>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element correspDesc { tei_model.correspDescPart+ | tei_model.pLike+ }

1.17. <country>

<country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [13.2.3. Place Names]
Module namesdates
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Note

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

Example
<country key="DK">Denmark</country>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element country { tei_macro.phraseSeq }

1.18. <date>

<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.4. Dates]
Module core
Attributes
when supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Derived from att.datable.w3c
Status Optional
Datatype teidata.temporal.w3c
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
objectCreated
Entstehungsdatum des Überlieferungsträgers (z.B. Druckjahr)
contentCreatedPresumed
Entstehungsdatum des ed. Textes (editorisch ermittelt)
contentCreatedDocumented
Entstehungsdatum des ed. Textes (Angabe im Original nachgewiesen)
mediaCreated
Entstehungsdatum des Mediums
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element date
{
   attribute when { text }?,
   attribute type
   {
      "objectCreated"
    | "contentCreatedPresumed"
    | "contentCreatedDocumented"
    | "mediaCreated"
   }?,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

1.19. <depth>

<depth> (depth) contains a measurement from the front to the back of an object, perpendicular to the measurement given by the <width> element. [10.3.4. Dimensions]
Module msdescription
Member of
Contained by
May contain
gaiji: g
character data
Example
<depth quantity="4unit="in"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element depth { tei_macro.xtext }

1.20. <desc>

<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [22.4.1. Description of Components]
Module core
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
contentMilestone
Sprungmarken zu relevanten Textstellen
<dataSpec ident="teidata.point"  module="tei"  validUntil="2050-02-25">  <desc type="deprecationInfo"   versionDate="2018-09-14"   xml:lang="en">Several standards bodies, including NIST in the USA,    strongly recommend against ending the representation of a number    with a decimal point. So instead of <q>3.</q> use either <q>3</q>    or <q>3.0</q>.</desc> <!-- ... --> </dataSpec>
Member of
Contained by
analysis: interp interpGrp
header: change licence
linking: seg
msdescription: provenance support
namesdates: listObject
textcrit: lem
textstructure: body div
May contain
Note

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

Example Example of a <desc> element inside a documentation element.
<dataSpec ident="teidata.point"  module="tei">  <desc versionDate="2010-10-17"   xml:lang="en">defines the data type used to express a point in cartesian space.</desc>  <content>   <dataRef name="token"    restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>  </content> <!-- ... --> </dataSpec>
Example Example of a <desc> element in a non-documentation element.
<place xml:id="KERG2">  <placeName>Kerguelen Islands</placeName> <!-- ... -->  <terrain>   <desc>antarctic tundra</desc>  </terrain> <!-- ... --> </place>
Schematron A <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when <desc> is a valid child of that element.
<sch:rule context="tei:desc[ @type eq 'deprecationInfo']"> <sch:assert test="../@validUntil">Information about a deprecation should only be present in a specification element that is being deprecated: that is, only an element that has a @validUntil attribute should have a child <desc type="deprecationInfo">.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element desc
{
   attribute type { "contentMilestone" },
   tei_macro.limitedContent
}

1.21. <dimensions>

<dimensions> (dimensions) contains a dimensional specification. [10.3.4. Dimensions]
Module msdescription
Attributes
unit names the unit used for the measurement
Derived from att.dimensions
Status Required
Datatype teidata.enumerated
Legal values are:
cm
Einheit für Maßangaben: cm
Member of
Contained by
May contain
msdescription: depth height width
Note

Contains no more than one of each of the specialized elements used to express a three-dimensional object's height, width, and depth, combined with any number of other kinds of dimensional specification.

Example
<dimensions type="leaves">  <height scope="range">157-160</height>  <width>105</width> </dimensions> <dimensions type="ruled">  <height scope="most">90</height>  <width scope="most">48</width> </dimensions> <dimensions unit="in">  <height>12</height>  <width>10</width> </dimensions>
Example This element may be used to record the dimensions of any text-bearing object, not necessarily a codex. For example:
<dimensions type="panels">  <height scope="all">7004</height>  <width scope="all">1803</width>  <dim type="reliefunit="mm">345</dim> </dimensions>
This might be used to show that the inscribed panels on some (imaginary) monument are all the same size (7004 by 1803 cm) and stand out from the rest of the monument by 345 mm.
Example When simple numeric quantities are involved, they may be expressed on the quantity attribute of any or all of the child elements, as in the following example:
<dimensions type="leaves">  <height scope="range">157-160</height>  <width quantity="105"/> </dimensions> <dimensions type="ruled">  <height quantity="90scope="most"   unit="cm"/>  <width quantity="48scope="mostunit="cm"/> </dimensions> <dimensions unit="in">  <height quantity="12"/>  <width quantity="10"/> </dimensions>
Schematron
<sch:report test="count(tei:width)> 1">The element <sch:name/> may appear once only </sch:report> <sch:report test="count(tei:height)> 1">The element <sch:name/> may appear once only </sch:report> <sch:report test="count(tei:depth)> 1">The element <sch:name/> may appear once only </sch:report>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="dim"/>
  <classRef key="model.dimLike"/>
 </alternate>
</content>
    
Schema Declaration
element dimensions { attribute unit { "cm" }, ( dim | tei_model.dimLike )* }

1.22. <distinct>

<distinct> identifies any word or phrase which is regarded as linguistically distinct, for example as archaic, technical, dialectal, non-preferred, etc., or as forming part of a sublanguage. [3.3.2.3. Other Linguistically Distinct Material]
Module core
Attributes
type specifies the sublanguage or register to which the word or phrase is being assigned
Derived from att.typed
Status Required
Datatype teidata.enumerated
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
Next morning a boy in that dormitory confided to his bosom friend, a <distinct type="ps_slang">fag</distinct> of Macrea's, that there was trouble in their midst which King <distinct type="archaic">would fain</distinct> keep secret.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element distinct { attribute type { text }, tei_macro.phraseSeq }

1.23. <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Module textstructure
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Optional
Datatype ID
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
introduction
Abschnitt: Einleitung (Inhaltliche Einleitung)
notesOnTranslation
Abschnitt: Einleitung (Anmerkungen zur Übersetzung)
notesOnTextConstitution
Abschnitt: Einleitung (Anmerkungen zu Textkonstitution)
contentMilestones
Abschnitt: Einleitung (Textsprungmarken)
transcript
Abschnitt: Transkription (gesamt)
segment
Abschnitt: Transkription (Gedicht)
footnotes
Abschnitt: Apparat (Sachanmerkungen)
critNotes
Abschnitt: Apparat (Textkritische Anmerkungen)
similiaNotes
Abschnitt: Apparat (Similienanmerkungen)
listSpondiaci
Abschnitt: Anhang (Spondiaci)
listNeologisms
Abschnitt: Anhang (Neologismen)
listMonosyllaba
Abschnitt: Anhang (Monosyllaba)
listIndexReferences
Abschnitt: Anhang (Indexreferenzen)
metadataMetrics
Abschnitt: Anhang (Metrische Angaben)
bibliography
Abschnitt: Register (Bibliographie)
index
Abschnitt: Register (Index)
index
Abschnitt: Register (Werke)
metadataDisplay
Abschnitt: Technik
Member of
Contained by
textcrit: lem
textstructure: back body div front
May contain
analysis: interp interpGrp
linking: anchor
msdescription: msDesc
namesdates: listObject
textstructure: closer div opener
transcr: space
Example
<body>  <div type="part">   <head>Fallacies of Authority</head>   <p>The subject of which is Authority in various shapes, and the object, to repress all      exercise of the reasoning faculty.</p>   <div n="1type="chapter">    <head>The Nature of Authority</head>    <p>With reference to any proposed measures having for their object the greatest        happiness of the greatest number [...]</p>    <div n="1.1type="section">     <head>Analysis of Authority</head>     <p>What on any given occasion is the legitimate weight or influence to be attached to          authority [...] </p>    </div>    <div n="1.2type="section">     <head>Appeal to Authority, in What Cases Fallacious.</head>     <p>Reference to authority is open to the charge of fallacy when [...] </p>    </div>   </div>  </div> </body>
Schematron
<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report>
Schematron
<sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence maxOccurs="1" minOccurs="0">
   <alternate maxOccurs="1" minOccurs="1">
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <alternate maxOccurs="1" minOccurs="1">
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
    <sequence maxOccurs="1" minOccurs="1">
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <alternate maxOccurs="1"
       minOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       maxOccurs="unbounded" minOccurs="0"/>
     </sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="0">
      <alternate maxOccurs="1"
       minOccurs="1">
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       maxOccurs="unbounded" minOccurs="0"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div
{
   attribute xml:id { text }?,
   attribute type
   {
      "introduction"
    | "notesOnTranslation"
    | "notesOnTextConstitution"
    | "contentMilestones"
    | "transcript"
    | "segment"
    | "footnotes"
    | "critNotes"
    | "similiaNotes"
    | "listSpondiaci"
    | "listNeologisms"
    | "listMonosyllaba"
    | "listIndexReferences"
    | "metadataMetrics"
    | "bibliography"
    | "index"
    | "index"
    | "metadataDisplay"
   },
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            ( ( tei_model.divLike | tei_model.divGenLike ), tei_model.global* )+
          | (
               ( ( schemaSpec | tei_model.common ), tei_model.global* )+,
               (
                  ( tei_model.divLike | tei_model.divGenLike ),
                  tei_model.global*
               )*
            )
         ),
         ( tei_model.divBottom, tei_model.global* )*
      )?
   )
}

1.24. <encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Module header
Member of
Contained by
header: teiHeader
May contain
core: p
header: projectDesc
verse: metDecl
Example
<encodingDesc>  <p>Basic encoding, capturing lexical information only. All    hyphenation, punctuation, and variant spellings normalized. No    formatting or layout information preserved.</p> </encodingDesc>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.encodingDescPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element encodingDesc { ( tei_model.encodingDescPart | tei_model.pLike )+ }

1.25. <expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
Module core
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Note

The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.

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

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

1.26. <extent>

<extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]
Module header
Member of
Contained by
core: bibl monogr
header: fileDesc
msdescription: supportDesc
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
<extent>3200 sentences</extent> <extent>between 10 and 20 Mb</extent> <extent>ten 3.5 inch high density diskettes</extent>
Example The <measure> element may be used to supply normalized or machine tractable versions of the size or sizes concerned.
<extent>  <measure quantity="4.2unit="MiB">About four megabytes</measure>  <measure quantity="245unit="pages">245 pages of source    material</measure> </extent>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element extent { tei_macro.phraseSeq }

1.27. <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
Contained by
header: teiHeader
May contain
Note

The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

Example
<fileDesc>  <titleStmt>   <title>The shortest possible TEI document</title>  </titleStmt>  <publicationStmt>   <p>Distributed as part of TEI P5</p>  </publicationStmt>  <sourceDesc>   <p>No print source exists: this is an original digital text</p>  </sourceDesc> </fileDesc>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <sequence maxOccurs="1" minOccurs="1">
   <elementRef key="titleStmt"/>
   <elementRef key="editionStmt"
    minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="publicationStmt"/>
   <elementRef key="seriesStmt"
    maxOccurs="unbounded" minOccurs="0"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   maxOccurs="unbounded" minOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element fileDesc
{
   (
      tei_titleStmt,
      editionStmt?,
      tei_extent?,
      tei_publicationStmt,
      seriesStmt*,
      notesStmt?
   ),
   tei_sourceDesc+
}

1.28. <front>

<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Module textstructure
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
Legal values are:
front
Contained by
textstructure: text
May contain
analysis: interp interpGrp
linking: anchor
textstructure: closer div
transcr: space
Note

Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the <front> and <back> elements are identical.

Example
<front>  <epigraph>   <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla      pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί        θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q>   </quote>  </epigraph>  <div type="dedication">   <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>   </p>  </div> </front>
Example
<front>  <div type="dedication">   <p>To our three selves</p>  </div>  <div type="preface">   <head>Author's Note</head>   <p>All the characters in this book are purely imaginary, and if the      author has used names that may suggest a reference to living persons      she has done so inadvertently. ...</p>  </div> </front>
Example
<front>  <div type="abstract">   <div>    <head> BACKGROUND:</head>    <p>Food insecurity can put children at greater risk of obesity because        of altered food choices and nonuniform consumption patterns.</p>   </div>   <div>    <head> OBJECTIVE:</head>    <p>We examined the association between obesity and both child-level        food insecurity and personal food insecurity in US children.</p>   </div>   <div>    <head> DESIGN:</head>    <p>Data from 9,701 participants in the National Health and Nutrition        Examination Survey, 2001-2010, aged 2 to 11 years were analyzed.        Child-level food insecurity was assessed with the US Department of        Agriculture's Food Security Survey Module based on eight        child-specific questions. Personal food insecurity was assessed with        five additional questions. Obesity was defined, using physical        measurements, as body mass index (calculated as kg/m2) greater than        or equal to the age- and sex-specific 95th percentile of the Centers        for Disease Control and Prevention growth charts. Logistic        regressions adjusted for sex, race/ethnic group, poverty level, and        survey year were conducted to describe associations between obesity        and food insecurity.</p>   </div>   <div>    <head> RESULTS:</head>    <p>Obesity was significantly associated with personal food insecurity        for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to        2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95%        CI 0.51 to 1.51). Child-level food insecurity was not associated        with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p>   </div>   <div>    <head> CONCLUSIONS:</head>    <p>Personal food insecurity is associated with an increased risk of        obesity only in children aged 6 to 11 years. Personal        food-insecurity measures may give different results than aggregate        food-insecurity measures in children.</p>   </div>  </div> </front>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence maxOccurs="1" minOccurs="0">
   <alternate maxOccurs="1" minOccurs="1">
    <sequence maxOccurs="1" minOccurs="1">
     <classRef key="model.div1Like"/>
     <alternate maxOccurs="unbounded"
      minOccurs="0">
      <classRef key="model.div1Like"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
    <sequence maxOccurs="1" minOccurs="1">
     <classRef key="model.divLike"/>
     <alternate maxOccurs="unbounded"
      minOccurs="0">
      <classRef key="model.divLike"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
   </alternate>
   <sequence maxOccurs="1" minOccurs="0">
    <classRef key="model.divBottom"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.divBottom"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element front
{
   attribute xml:id { "front" },
   (
      (
         tei_model.frontPart
       | tei_model.pLike
       | tei_model.pLike.front
       | tei_model.global
      )*,
      (
         (
            (
               tei_model.div1Like,
               ( tei_model.div1Like | tei_model.frontPart | tei_model.global )*
            )
          | (
               tei_model.divLike,
               ( tei_model.divLike | tei_model.frontPart | tei_model.global )*
            )
         ),
         ( tei_model.divBottom, ( tei_model.divBottom | tei_model.global )* )?
      )?
   )
}

1.29. <g>

<g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes]
Module gaiji
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
paragraph
Sonderzeichen Paragraphenzeichen (§)
Member of
Contained by
May contain Character data only
Note

The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph.

Example
<g ref="#ctlig">ct</g>
This example points to a <glyph> element with the identifier ctlig like the following:
<glyph xml:id="ctlig"> <!-- here we describe the particular ct-ligature intended --> </glyph>
Example
<g ref="#per-glyph">per</g>
The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per-glyph as follows:
<glyph xml:id="per-glyph"> <!-- ... --> </glyph>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element g { attribute type { "paragraph" }, text }

1.30. <handDesc>

<handDesc> (description of hands) contains a description of all the different hands used in a manuscript or other object. [10.7.2. Writing, Decoration, and Other Notations]
Module msdescription
Member of
Contained by
msdescription: physDesc
May contain
core: p
Example
<handDesc>  <handNote scope="major">Written throughout in <term>angelicana formata</term>.</handNote> </handDesc>
Example
<handDesc hands="2">  <p>The manuscript is written in two contemporary hands, otherwise    unknown, but clearly those of practised scribes. Hand I writes    ff. 1r-22v and hand II ff. 23 and 24. Some scholars, notably    Verner Dahlerup and Hreinn Benediktsson, have argued for a third hand    on f. 24, but the evidence for this is insubstantial.</p> </handDesc>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence maxOccurs="1" minOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="handNote"
    maxOccurs="unbounded" minOccurs="1"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element handDesc { tei_model.pLike+ | ( summary?, handNote+ ) }

1.31. <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
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
center
Ausrichtung im Original: zentriert
right
Ausrichtung im Original: rechtsbündig
Member of
Contained by
msdescription: msDesc
namesdates: listObject object
textstructure: back body div front
May contain
Note

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

Example The most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:
<div1 n="Itype="book">  <head>In the name of Christ here begins the first book of the ecclesiastical history of    Georgius Florentinus, known as Gregory, Bishop of Tours.</head>  <div2 type="section">   <head>In the name of Christ here begins Book I of the history.</head>   <p>Proposing as I do ...</p>   <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve      years passed.</p>   <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six      years from the beginning of the world down to the death of Saint Martin.</trailer>  </div2> </div1>
Example When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.
<div type="subsection">  <head place="margin">Secunda conclusio</head>  <p>   <lb n="1251"/>   <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>   </hi>   <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium    [...]  </p> </div>
Example The <head> element is also used to mark headings of other units, such as lists:
With a few exceptions, connectives are equally useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">  <head>Connectives</head>  <item>above</item>  <item>accordingly</item>  <item>across from</item>  <item>adjacent to</item>  <item>again</item>  <item> <!-- ... -->  </item> </list>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element head
{
   attribute rend { list { ( "center" | "right" )+ } }?,
   (
      text
    | tei_lg
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.lLike
    | tei_model.global
   )*
}

1.32. <height>

<height> (height) contains a measurement measured along the axis at a right angle to the bottom of the object. [10.3.4. Dimensions]
Module msdescription
Member of
Contained by
May contain
gaiji: g
character data
Example
<height quantity="7unit="in"/>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element height { tei_macro.xtext }

1.33. <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
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 teidata.word separated by whitespace
Legal values are:
italic
Hervorhebung (editorisch): kursiv
bold
Hervorhebung (editorisch): fett
underline
Hervorhebung (editorisch): unterstrichen
Member of
Contained by
May contain
Example
<hi rend="gothic">And this Indenture further witnesseth</hi> that the said <hi rend="italic">Walter Shandy</hi>, merchant, in consideration of the said intended marriage ...
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element hi
{
   attribute rend { list { ( "italic" | "bold" | "underline" )+ } },
   tei_macro.paraContent
}

1.34. <history>

<history> (history) groups elements describing the full history of a manuscript, manuscript part, or other object. [10.8. History]
Module msdescription
Contained by
msdescription: msDesc
namesdates: object
May contain
core: p
msdescription: provenance
Example
<history>  <origin>   <p>Written in Durham during the mid twelfth      century.</p>  </origin>  <provenance>   <p>Recorded in two medieval      catalogues of the books belonging to Durham Priory, made in 1391 and      1405.</p>  </provenance>  <provenance>   <p>Given to W. Olleyf by William Ebchester, Prior (1446-56)      and later belonged to Henry Dalton, Prior of Holy Island (Lindisfarne)      according to inscriptions on ff. 4v and 5.</p>  </provenance>  <acquisition>   <p>Presented to Trinity College in 1738 by      Thomas Gale and his son Roger.</p>  </acquisition> </history>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence maxOccurs="1" minOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="origin" minOccurs="0"/>
   <elementRef key="provenance"
    maxOccurs="unbounded" minOccurs="0"/>
   <elementRef key="acquisition"
    minOccurs="0"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element history
{
   tei_model.pLike+ | ( summary?, origin?, tei_provenance*, acquisition? )
}

1.35. <idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [13.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module header
Attributes
type categorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
vd16
VD16-Nummer
vd17
VD17-Nummer
vd18
VD18-Nummer
shelfmark
Signatur
di
Deutsche Inschriften Online (Band und Nummer)
Member of
Contained by
May contain
gaiji: g
header: idno
character data
Note

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

Example
<idno type="ISBN">978-1-906964-22-1</idno> <idno type="ISSN">0143-3385</idno> <idno type="DOI">10.1000/123</idno> <idno type="URI">http://www.worldcat.org/oclc/185922478</idno> <idno type="URI">http://authority.nzetc.org/463/</idno> <idno type="LT">Thomason Tract E.537(17)</idno> <idno type="Wing">C695</idno> <idno type="oldCat">  <g ref="#sym"/>345 </idno>
In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>
    
Schema Declaration
element idno
{
   attribute type { "vd16" | "vd17" | "vd18" | "shelfmark" | "di" },
   ( text | tei_model.gLike | tei_idno )*
}

1.36. <imprint>

<imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module core
Contained by
core: monogr
May contain
Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="classCode"/>
   <elementRef key="catRef"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <alternate maxOccurs="1" minOccurs="1">
    <classRef key="model.imprintPart"/>
    <classRef key="model.dateLike"/>
   </alternate>
   <elementRef key="respStmt"
    maxOccurs="unbounded" minOccurs="0"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element imprint
{
   ( classCode | catRef )*,
   (
      ( tei_model.imprintPart | tei_model.dateLike ),
      tei_respStmt*,
      tei_model.global*
   )+
}

1.37. <interp>

<interp> (interpretation) summarizes a specific interpretative annotation which can be linked to a span of text. [17.3. Spans and Interpretations]
Module analysis
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
Legal values are:
spondaicGrc
Metrische Notation: Spondeischer Vers (im Griechischen)
spondaicLat
Metrische Notation: Spondeischer Vers (im Lateinischen)
TH
Metrische Notation: Trithemimeres (TH)
PH
Metrische Notation: Penthemimeres (PH)
HH
Metrische Notation: Hephthemimeres (HH)
BD
Metrische Notation: Bukolische Dihärese (BD)
KTT
Metrische Notation: Kata triton trochaion (KTT)
MZ
Metrische Notation: Mittelzäsur (MZ)
D
Metrische Notation: Daktylus (D)
S
Metrische Notation: Spondeus (S)
-
Metrische Notation: Lange Silbe
u
Metrische Notation: Kurze Silbe
monosyllabumGrc
Metrische Notation: Einsilber (im Griechischen)
monosyllabumLat
Metrische Notation: Einsilber (im Lateinischen)
type indicates what kind of phenomenon is being noted in the passage.
Derived from att.interpLike
Status Required
Datatype teidata.enumerated
Legal values are:
hexameter_type
Metrische Notation: Hexametertyp
caesura
Metrische Notation: Zäsur
metrical_foot
Metrische Notation: Versfuß
syllable_weight
Metrische Notation: Silbenquantität
syllable_length
Metrische Notation: Silbenlänge
Member of
Contained by
May contain
core: desc
gaiji: g
character data
Note

Generally, each <interp> element carries an xml:id attribute. This permits the encoder to explicitly associate the interpretation represented by the content of an <interp> with any textual element through its ana attribute.

Alternatively (or, in addition) an <interp> may carry an inst attribute that points to one or more textual elements to which the analysis represented by the content of the <interp> applies.

Example
<interp type="structuralunit"  xml:id="ana_am">aftermath</interp>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element interp
{
   attribute xml:id
   {
      "spondaicGrc"
    | "spondaicLat"
    | "TH"
    | "PH"
    | "HH"
    | "BD"
    | "KTT"
    | "MZ"
    | "D"
    | "S"
    | "-"
    | "u"
    | "monosyllabumGrc"
    | "monosyllabumLat"
   },
   attribute type
   {
      "hexameter_type"
    | "caesura"
    | "metrical_foot"
    | "syllable_weight"
    | "syllable_length"
   },
   ( text | tei_model.gLike | tei_model.descLike | tei_model.certLike )*
}

1.38. <interpGrp>

<interpGrp> (interpretation group) collects together a set of related interpretations which share responsibility or type. [17.3. Spans and Interpretations]
Module analysis
Member of
Contained by
May contain
analysis: interp
core: desc
Note

Any number of <interp> elements.

Example
<interpGrp resp="#TMA"  type="structuralunit">  <desc>basic structural organization</desc>  <interp xml:id="I1">introduction</interp>  <interp xml:id="I2">conflict</interp>  <interp xml:id="I3">climax</interp>  <interp xml:id="I4">revenge</interp>  <interp xml:id="I5">reconciliation</interp>  <interp xml:id="I6">aftermath</interp> </interpGrp> <bibl xml:id="TMA"> <!-- bibliographic citation for source of this interpretive framework --> </bibl>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.descLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="interp"
   maxOccurs="unbounded" minOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element interpGrp { tei_model.descLike*, tei_interp+ }

1.39. <item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Module core
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Optional
Datatype ID
corresp (corresponds) points to elements that correspond to the current element in some way.
Derived from att.global.linking
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type
Status Optional
Legal values are:
person
Indexeintrag: Person oder Personifizierung
place
Indexeintrag: Geographischer Eintrag
subject
Indexeintrag: Gegenstand, Sacheintrag oder Sachverhalt
metVerse
Metrikangaben: Gesamtverszahl
metSpondaicGrc
Metrikangaben: Spondiaci (im Griechischen)
metSpondaicLat
Metrikangaben: Spondiaci (im Lateinischen)
metMonosyllabaGrc
Metrikangaben: Monosyllaba (im Griechischen)
metMonosyllabaLat
Metrikangaben: Monosyllaba (im Lateinischen)
metCaesuraPHGrc
Metrikangaben: Zäsur Penthemimeres (PH) (im Griechischen)
metCaesuraPHLat
Metrikangaben: Zäsur Penthemimeres (PH) (im Lateinischen)
metCaesuraKTTGrc
Metrikangaben: Zäsur Kata triton trochaion (KTT) (im Griechischen)
metCaesuraKTTLat
Metrikangaben: Zäsur Kata triton trochaion (KTT) (im Lateinischen)
metCaesuraOtherGrc
Metrikangaben: Zäsur andere (z.B. Trithemimeres, Hephthemimeres) (im Griechischen)
metCaesuraOtherLat
Metrikangaben: Zäsur andere (z.B. Trithemimeres, Hephthemimeres) (im Lateinischen)
metMetricalFootGrc
Metrikangaben: Versfuß (D=Daktylus, S=Spondeus) (im Griechischen)
metMetricalFootLat
Metrikangaben: Versfuß (D=Daktylus, S=Spondeus) (im Lateinischen)
metDeclPoem
Metrische Angaben zum Gedicht (Sprache, Versmaß, Versanzahl)
subtype
Status Optional
Legal values are:
mythical
Indexeintrag Unterkategorie Person(ifizierung): mythisch
biblical
Indexeintrag Unterkategorie Person(ifizierung): biblisch-christlich
classical
Indexeintrag Unterkategorie Person(ifizierung): antik-historisch
post-classical
Indexeintrag Unterkategorie Person(ifizierung): nach-antik-historisch
fictional
Indexeintrag Unterkategorie Person(ifizierung): fitktiv/Personifizierung
none
Indexeintrag Unterkategorie Person(ifizierung): nicht definiert
Contained by
core: list
May contain
Note

May contain simple prose or a sequence of chunks.

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

Example
<list rend="numbered">  <head>Here begin the chapter headings of Book IV</head>  <item n="4.1">The death of Queen Clotild.</item>  <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>  <item n="4.3">The wives and children of Lothar.</item>  <item n="4.4">The Counts of the Bretons.</item>  <item n="4.5">Saint Gall the Bishop.</item>  <item n="4.6">The priest Cato.</item>  <item> ...</item> </list>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element item
{
   attribute xml:id { text }?,
   attribute corresp { list { + } }?,
   attribute type
   {
      "person"
    | "place"
    | "subject"
    | "metVerse"
    | "metSpondaicGrc"
    | "metSpondaicLat"
    | "metMonosyllabaGrc"
    | "metMonosyllabaLat"
    | "metCaesuraPHGrc"
    | "metCaesuraPHLat"
    | "metCaesuraKTTGrc"
    | "metCaesuraKTTLat"
    | "metCaesuraOtherGrc"
    | "metCaesuraOtherLat"
    | "metMetricalFootGrc"
    | "metMetricalFootLat"
    | "metDeclPoem"
   }?,
   attribute subtype
   {
      "mythical"
    | "biblical"
    | "classical"
    | "post-classical"
    | "fictional"
    | "none"
   }?,
   tei_macro.specialPara
}

1.40. <keywords>

<keywords> (keywords) contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]
Module header
Contained by
header: textClass
May contain
core: list term
Note

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

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

Example
<keywords scheme="http://classificationweb.net">  <term>Babbage, Charles</term>  <term>Mathematicians - Great Britain - Biography</term> </keywords>
Example
<keywords>  <term>Fermented beverages</term>  <term>Central Andes</term>  <term>Schinus molle</term>  <term>Molle beer</term>  <term>Indigenous peoples</term>  <term>Ethnography</term>  <term>Archaeology</term> </keywords>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <elementRef key="term"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="list"/>
 </alternate>
</content>
    
Schema Declaration
element keywords { tei_term+ | tei_list }

1.41. <l>

<l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
Module core
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Required
Datatype teidata.text
ana (analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived from att.global.analytic
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
indent
Status Optional
Legal values are:
yes
Versbegin eingezogen
Member of
Contained by
header: change licence
linking: seg
msdescription: provenance support
textcrit: lem
textstructure: body div
transcr: supplied surplus
May contain
Example
<l met="x/x/x/x/x/real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l>
Schematron
<sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]"> Abstract model violation: Lines may not contain lines or lg elements. </sch:report>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element l
{
   attribute xml:id { text },
   attribute n { text },
   attribute ana { list { + } }?,
   attribute indent { "yes" }?,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.global
   )*
}

1.42. <lb>

<lb> (line beginning) marks the beginning of a new (typographic) line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.5. Speech Contents]
Module core
Member of
Contained by
May contain Empty element
Note

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

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

Example This example shows typographical line breaks within metrical lines, where they occur at different places in different editions:
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word.
<titlePart>  <lb/>With Additions, ne-<lb break="no"/>ver before Printed. </titlePart>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element lb { empty }

1.43. <lem>

<lem> (lemma) contains the lemma, or base text, of a textual variation. [12.1. The Apparatus Entry, Readings, and Witnesses]
Module textcrit
Contained by
May contain
Note

The term lemma is used in text criticism to describe the reading given in the main text, which may be used as a heading in the apparatus itself. This usage connects it to mathematics (where a lemma is a proven proposition used as a step in a proof, a "given") and natural-language processing (where a lemma is the dictionary headword associated with an inflected form in the running text).

Example
<app>  <lem wit="#El #Hg">Experience</lem>  <rdg type="substantivewit="#La">Experiment</rdg>  <rdg type="substantivewit="#Ra2">Eryment</rdg> </app>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.divLike"/>
  <classRef key="model.divPart"/>
  <elementRef key="titlePage"/>
  <elementRef key="argument"/>
  <elementRef key="byline"/>
  <elementRef key="docAuthor"/>
  <elementRef key="docDate"/>
  <elementRef key="docEdition"/>
  <elementRef key="docImprint"/>
  <elementRef key="docTitle"/>
  <elementRef key="epigraph"/>
  <elementRef key="imprimatur"/>
  <elementRef key="titlePart"/>
  <elementRef key="epilogue"/>
  <elementRef key="performance"/>
  <elementRef key="prologue"/>
  <elementRef key="set"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
  <classRef key="model.rdgPart"/>
 </alternate>
</content>
    
Schema Declaration
element lem
{
   (
      text
    | tei_model.divLike
    | tei_model.divPart
    | titlePage
    | argument
    | byline
    | docAuthor
    | docDate
    | docEdition
    | docImprint
    | docTitle
    | epigraph
    | imprimatur
    | titlePart
    | epilogue
    | performance
    | prologue
    | set
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.global
    | tei_model.rdgPart
   )*
}

1.44. <lg>

<lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
Module core
Member of
Contained by
header: change licence
linking: seg
msdescription: provenance support
textcrit: lem
textstructure: body div
transcr: supplied surplus
May contain
analysis: interp interpGrp
linking: anchor
textstructure: closer opener
transcr: space
Note

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

Example
<lg type="free">  <l>Let me be my own fool</l>  <l>of my own making, the sum of it</l> </lg> <lg type="free">  <l>is equivocal.</l>  <l>One says of the drunken farmer:</l> </lg> <lg type="free">  <l>leave him lay off it. And this is</l>  <l>the explanation.</l> </lg>
Schematron
<sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element must contain at least one child l, lg, or gap element.</sch:assert>
Schematron
<sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]"> Abstract model violation: Lines may not contain line groups. </sch:report>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate maxOccurs="1" minOccurs="1">
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <elementRef key="lg"/>
  </alternate>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.global"/>
   <elementRef key="lg"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element lg
{
   ( tei_model.divTop | tei_model.global )*,
   ( tei_model.lLike | tei_model.stageLike | tei_model.labelLike | tei_lg ),
   (
      tei_model.lLike
    | tei_model.stageLike
    | tei_model.labelLike
    | tei_model.global
    | tei_lg
   )*,
   ( tei_model.divBottom, tei_model.global* )*
}

1.45. <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Module header
Attributes
target specifies the destination of the reference by supplying one or more URI References
Derived from att.pointing
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
header: availability
May contain
Note

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

Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence </licence>
Example
<availability>  <licence notBefore="2013-01-01"   target="http://creativecommons.org/licenses/by/3.0/">   <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence      applies to this document.</p>   <p>The licence was added on January 1, 2013.</p>  </licence> </availability>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element licence { attribute target { list { + } }, tei_macro.specialPara }

1.46. <list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Module core
Attributes
corresp (corresponds) points to elements that correspond to the current element in some way.
Derived from att.global.linking
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
linking: seg
msdescription: provenance support
textcrit: lem
textstructure: back body div
transcr: supplied surplus
May contain
analysis: interp interpGrp
linking: anchor
textstructure: closer opener
transcr: space
Note

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

Example
<list rend="numbered">  <item>a butcher</item>  <item>a baker</item>  <item>a candlestick maker, with  <list rend="bulleted">    <item>rings on his fingers</item>    <item>bells on his toes</item>   </list>  </item> </list>
Example
<list rend="bulletedtype="syllogism">  <item>All Cretans are liars.</item>  <item>Epimenides is a Cretan.</item>  <item>ERGO Epimenides is a liar.</item> </list>
Example
<list rend="simpletype="litany">  <item>God save us from drought.</item>  <item>God save us from pestilence.</item>  <item>God save us from wickedness in high places.</item>  <item>Praise be to God.</item> </list>
Example The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):
<div1 type="section">  <head>Athelstan's Ordinance</head>  <list rend="numbered">   <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with      the stolen goods, [if he is] over twelve years and [if the value of the goods is] over      eightpence.   <list rend="numbered">     <item n="1.1">And if anyone does spare one, he is to pay for the thief with his          wergild — and the thief is to be no nearer a settlement on that account — or to          clear himself by an oath of that amount.</item>     <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is          not to be spared [whether younger or older than twelve].</item>     <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may          then be redeemed with 120 shillings; and the kindred are to stand surety for him          that he will desist for ever.</item>     <item n="1.4">And if he steals after that, they are to pay for him with his wergild,          or to bring him back there.</item>     <item n="1.5">And if he steals after that, they are to pay for him with his wergild,          whether to the king or to him to whom it rightly belongs; and everyone of those who          supported him is to pay 120 shillings to the king as a fine.</item>    </list>   </item>   <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom      no justice can be obtained, that one should order their kindred to fetch back such a      person to justice and to find him a lord in public meeting.   <list rend="numbered">     <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,          he is then to be a fugitive afterwards, and he who encounters him is to strike him          down as a thief.</item>     <item n="2.2">And he who harbours him after that, is to pay for him with his wergild          or to clear himself by an oath of that amount.</item>    </list>   </item>   <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds      his guilty man, so that the king is appealed to, is to repay the value of the goods and      120 shillings to the king; and he who appeals to the king before he demands justice as      often as he ought, is to pay the same fine as the other would have done, if he had      refused him justice.   <list rend="numbered">     <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes          known about him, is to forfeit the slave and be liable to his wergild on the first          occasionp if he does it more often, he is to be liable to pay all that he owns.</item>     <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been          an accessory of thieves who have committed theft, is to liable to the same.</item>    </list>   </item>   <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to      a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is      afterwards convicted at the three-fold ordeal.</item>  </list> </div1>
Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.
Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy Cross. <list rend="simple">   <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have      subscribed to the pious and catholic validity of this document with the sign of the Holy      Cross.</item>   <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with      the sign of the Holy Cross.</item>   <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the      sign of the Holy Cross.</item>   <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the      sign of the Holy Cross.</item>   <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of      the Holy Cross.</item>   <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>   <item>I, Æthelwine, bishop, have subscribed through delegates.</item>   <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy      Cross.</item>  </list> </p>
Schematron
<sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert> </sch:rule>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc"
    maxOccurs="unbounded" minOccurs="0"/>
  </alternate>
  <alternate maxOccurs="1" minOccurs="1">
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <elementRef key="item"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <elementRef key="headLabel"
     minOccurs="0"/>
    <elementRef key="headItem"
     minOccurs="0"/>
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <elementRef key="label"/>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
     <elementRef key="item"/>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element list
{
   attribute corresp { list { + } }?,
   (
      ( tei_model.divTop | tei_model.global | tei_desc* )*,
      (
         ( tei_item, tei_model.global* )+
       | (
            headLabel?,
            headItem?,
            ( label, tei_model.global*, tei_item, tei_model.global* )+
         )
      ),
      ( tei_model.divBottom, tei_model.global* )*
   )
}

1.47. <listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Module core
Member of
Contained by
linking: seg
namesdates: object
textcrit: lem
textstructure: back body div front
transcr: supplied surplus
May contain
linking: anchor
msdescription: msDesc
Example
<listBibl>  <head>Works consulted</head>  <bibl>Blain, Clements and Grundy: Feminist Companion to    Literature in English (Yale, 1990)  </bibl>  <biblStruct>   <analytic>    <title>The Interesting story of the Children in the Wood</title>   </analytic>   <monogr>    <title>The Penny Histories</title>    <author>Victor E Neuberg</author>    <imprint>     <publisher>OUP</publisher>     <date>1968</date>    </imprint>   </monogr>  </biblStruct> </listBibl>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.headLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="desc"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.milestoneLike"
    maxOccurs="1" minOccurs="1"/>
   <elementRef key="relation" maxOccurs="1"
    minOccurs="1"/>
   <elementRef key="listRelation"
    maxOccurs="1" minOccurs="1"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.biblLike"
    maxOccurs="unbounded" minOccurs="1"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.milestoneLike"
     maxOccurs="1" minOccurs="1"/>
    <elementRef key="relation"
     maxOccurs="1" minOccurs="1"/>
    <elementRef key="listRelation"
     maxOccurs="1" minOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listBibl
{
   tei_model.headLike*,
   tei_desc*,
   ( tei_model.milestoneLike | relation | listRelation )*,
   (
      tei_model.biblLike+,
      ( tei_model.milestoneLike | relation | listRelation )*
   )+
}

1.48. <listObject>

<listObject> (list of objects) contains a list of descriptions, each of which provides information about an identifiable physical object. [13.3.5. Objects]
Module namesdates
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
epigraphicInscription
Überlieferungsträger: Steinplatte / Inschrift
Member of
Contained by
linking: seg
msdescription: provenance support
namesdates: listObject
textcrit: lem
textstructure: back body div
transcr: supplied surplus
May contain
core: desc head
namesdates: listObject object
Note

The type attribute may be used to distinguish different types of objects.

Example
<listObject>  <object xml:id="AlfredJewel">   <objectIdentifier>    <country>United Kingdom</country>    <region>Oxfordshire</region>    <settlement>Oxford</settlement>    <institution>University of Oxford</institution>    <repository>Ashmolean Museum</repository>    <collection>English Treasures</collection>    <idno type="ashmolean">AN1836p.135.371</idno>    <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>    <objectName>Alfred Jewel</objectName>   </objectIdentifier>   <physDesc>    <p> The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed <material>gold</material>        surrounding a polished teardrop shaped piece of transparent <material>quartz</material>. Underneath the rock crystal        is a cloisonné enamel image of a man with ecclesiastical symbols. The sides of the jewel holding the crystal in        place contain an openwork inscription saying "AELFRED MEC HEHT GEWYRCAN", meaning 'Alfred ordered me made'. </p>   </physDesc>   <history>    <origin>It is generally accepted that the Alfred Jewel dates from the <origDate>late 9th Century</origDate> and was        most likely made in <origPlace>England</origPlace>. </origin>    <provenance when="1693">The jewel was discovered in 1693 at Petherton Park, North Petherton in the English county of        Somerset, on land owned by Sir Thomas Wroth. North Petherton is about 8 miles away from Athelney, where King Alfred        founded a monastery. </provenance>    <provenance when="1698">A description of the Alfred Jewel was first published in 1698, in the Philosophical        Transactions of the Royal Society.</provenance>    <acquisition> It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in the        Ashmolean Museum in Oxford. </acquisition>   </history>  </object> </listObject>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.headLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="desc"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="relation" maxOccurs="1"
    minOccurs="1"/>
   <elementRef key="listRelation"
    maxOccurs="1" minOccurs="1"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.objectLike"
    maxOccurs="unbounded" minOccurs="1"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="relation"
     maxOccurs="1" minOccurs="1"/>
    <elementRef key="listRelation"
     maxOccurs="1" minOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listObject
{
   attribute type { "epigraphicInscription" },
   (
      tei_model.headLike*,
      tei_desc*,
      ( relation | listRelation )*,
      ( tei_model.objectLike+, ( relation | listRelation )* )+
   )
}

1.49. <locus>

<locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [10.3.5. References to Locations within a Manuscript]
Module msdescription
Member of
Contained by
May contain
core: hi
gaiji: g
msdescription: locus
character data
Note

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

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

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <locus from="3">p. 3ff</locus>.

Example
<!-- within ms description --><msItem n="1">  <locus from="1rtarget="#F1r #F1v #F2r"   to="2r">ff. 1r-2r</locus>  <author>Ben Jonson</author>  <title>Ode to himself</title>  <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric>  <incipit>Com leaue the loathed stage</incipit>  <explicit>And see his chariot triumph ore his wayne.</explicit>  <bibl>   <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl> </msItem> <!-- within transcription ... --> <pb xml:id="F1r"/> <!-- ... --> <pb xml:id="F1v"/> <!-- ... --> <pb xml:id="F2r"/> <!-- ... -->
Example The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example:
<msItem>  <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus>  <title>Birds Praise of Love</title>  <bibl>   <title>IMEV</title>   <biblScope>1506</biblScope>  </bibl> </msItem>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="hi"/>
  <elementRef key="locus"/>
 </alternate>
</content>
    
Schema Declaration
element locus { ( text | tei_model.gLike | tei_hi | tei_locus )* }

1.50. <media>

<media> indicates the location of any form of external media such as an audio or video clip etc. [3.10. Graphics and Other Non-textual Components]
Module core
Attributes att.declaring (@decls) att.media (@width, @height, @scale) att.timed (@start, @end)
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
mimeType (MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
Derived from att.internetMedia
Status Required
Datatype 1–∞ occurrences of teidata.word separated by whitespace
url (uniform resource locator) specifies the URL from which the media concerned may be obtained.
Derived from att.resourced
Status Required
Datatype teidata.pointer
Member of
Contained by
May contain
core: desc
Note

The attributes available for this element are not appropriate in all cases. For example, it makes no sense to specify the temporal duration of a graphic. Such errors are not currently detected.

The mimeType attribute must be used to specify the MIME media type of the resource specified by the url attribute.

Example
<figure>  <media mimeType="image/pngurl="fig1.png"/>  <head>Figure One: The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc> </figure>
Example
<media dur="PT10SmimeType="audio/wav"  url="dingDong.wav">  <desc>Ten seconds of bellringing sound</desc> </media>
Example
<media dur="PT45MmimeType="video/mp4"  url="clip45.mp4width="500px">  <desc>A 45 minute video clip to be displayed in a window 500    px wide</desc> </media>
Content model
<content>
 <classRef key="model.descLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
    
Schema Declaration
element media
{
   tei_att.media.attribute.width,
   tei_att.media.attribute.height,
   tei_att.media.attribute.scale,
   tei_att.declaring.attributes,
   tei_att.timed.attribute.start,
   tei_att.timed.attribute.end,
   attribute xml:id { text },
   attribute mimeType { list { + } },
   attribute url { text },
   tei_model.descLike*
}

1.51. <metDecl>

<metDecl> (metrical notation declaration) documents the notation employed to represent a metrical pattern when this is specified as the value of a met, real, or rhyme attribute on any structural element of a metrical text (e.g. <lg>, <l>, or <seg>). [6.6. Metrical Notation Declaration 6.4. Rhyme and Metrical Analysis]
Module verse
Member of
Contained by
header: encodingDesc
May contain
core: note p
Note

The encoder may choose whether to define the notation formally or informally. However, the two methods may not be mixed. That is, <metDecl> may contain either a sequence of <metSym> elements or, alternately, a series of paragraphs or other components. If the pattern attribute is specified and <metSym> elements are used, then all the codes appearing within the pattern attribute should be documented.

Only usable within the header if the verse module is used.

Example
<metDecl pattern="((SU|US)USUSUSUS/)"  type="metxml:id="ip">  <metSym value="S">stressed syllable</metSym>  <metSym value="U">unstressed syllable</metSym>  <metSym value="/">metrical line boundary</metSym> </metDecl>
This example is intended for the far more restricted case typified by the Shakespearean iambic pentameter. Only metrical patterns containing exactly ten syllables, alternately stressed and unstressed, (except for the first two which may be in either order) to each metrical line can be expressed using this notation.
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.pLike"/>
   <classRef key="model.noteLike"/>
  </alternate>
  <elementRef key="metSym"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element metDecl { ( tei_model.pLike | tei_model.noteLike )+ | metSym+ }

1.52. <monogr>

<monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels]
Module core
Contained by
May contain
Note

May contain specialized bibliographic elements, in a prescribed order.

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

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope from="377to="380unit="page">377–380</biblScope>  </monogr> </biblStruct>
Example
<biblStruct type="book">  <monogr>   <author>    <persName>     <forename>Leo Joachim</forename>     <surname>Frachtenberg</surname>    </persName>   </author>   <title level="mtype="main">Lower Umpqua Texts</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Columbia University Press</publisher>    <date>1914</date>   </imprint>  </monogr>  <series>   <title level="stype="main">Columbia University Contributions to      Anthropology</title>   <biblScope unit="volume">4</biblScope>  </series> </biblStruct>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="1" minOccurs="0">
   <sequence maxOccurs="1" minOccurs="1">
    <alternate maxOccurs="1" minOccurs="1">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <elementRef key="title"
     maxOccurs="unbounded" minOccurs="1"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
     <elementRef key="textLang"/>
     <elementRef key="editor"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <alternate maxOccurs="unbounded"
     minOccurs="1">
     <elementRef key="title"/>
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
    </alternate>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <elementRef key="textLang"/>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <elementRef key="authority"/>
    <elementRef key="idno"/>
   </sequence>
  </alternate>
  <elementRef key="availability"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.noteLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="edition"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="idno"/>
    <classRef key="model.ptrLike"/>
    <elementRef key="editor"/>
    <elementRef key="sponsor"/>
    <elementRef key="funder"/>
    <elementRef key="respStmt"/>
   </alternate>
  </sequence>
  <elementRef key="imprint"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="imprint"/>
   <elementRef key="extent"/>
   <elementRef key="biblScope"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element monogr
{
   (
      (
         ( tei_author | editor | meeting | tei_respStmt ),
         ( tei_author | editor | meeting | tei_respStmt )*,
         tei_title+,
         (
            tei_model.ptrLike
          | tei_idno
          | tei_textLang
          | editor
          | tei_respStmt
         )*
      )
    | (
         ( tei_title | tei_model.ptrLike | tei_idno )+,
         ( tei_textLang | tei_author | editor | meeting | tei_respStmt )*
      )
    | ( authority, tei_idno )
   )?,
   tei_availability*,
   tei_model.noteLike*,
   (
      edition,
      (
         tei_idno
       | tei_model.ptrLike
       | editor
       | sponsor
       | funder
       | tei_respStmt
      )*
   )*,
   tei_imprint,
   ( tei_imprint | tei_extent | tei_biblScope )*
}

1.53. <msContents>

<msContents> (manuscript contents) describes the intellectual content of a manuscript, manuscript part, or other object either as a series of paragraphs or as a series of structured manuscript items. [10.6. Intellectual Content]
Module msdescription
Contained by
msdescription: msDesc
namesdates: object
May contain
core: p textLang
msdescription: msItem
Note

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

Example
<msContents class="#sermons">  <p>A collection of Lollard sermons</p> </msContents>
Example
<msContents>  <msItem n="1">   <locus>fols. 5r-7v</locus>   <title>An ABC</title>   <bibl>    <title>IMEV</title>    <biblScope>239</biblScope>   </bibl>  </msItem>  <msItem n="2">   <locus>fols. 7v-8v</locus>   <title xml:lang="frm">Lenvoy de Chaucer a Scogan</title>   <bibl>    <title>IMEV</title>    <biblScope>3747</biblScope>   </bibl>  </msItem>  <msItem n="3">   <locus>fol. 8v</locus>   <title>Truth</title>   <bibl>    <title>IMEV</title>    <biblScope>809</biblScope>   </bibl>  </msItem>  <msItem n="4">   <locus>fols. 8v-10v</locus>   <title>Birds Praise of Love</title>   <bibl>    <title>IMEV</title>    <biblScope>1506</biblScope>   </bibl>  </msItem>  <msItem n="5">   <locus>fols. 10v-11v</locus>   <title xml:lang="la">De amico ad amicam</title>   <title xml:lang="la">Responcio</title>   <bibl>    <title>IMEV</title>    <biblScope>16 &amp; 19</biblScope>   </bibl>  </msItem>  <msItem n="6">   <locus>fols. 14r-126v</locus>   <title>Troilus and Criseyde</title>   <note>Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout</note>  </msItem> </msContents>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence maxOccurs="1" minOccurs="1">
   <elementRef key="summary" minOccurs="0"/>
   <elementRef key="textLang" minOccurs="0"/>
   <elementRef key="titlePage"
    minOccurs="0"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="msItem"/>
    <elementRef key="msItemStruct"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element msContents
{
   tei_model.pLike+
 | ( summary?, tei_textLang?, titlePage?, ( tei_msItem | msItemStruct )* )
}

1.54. <msDesc>

<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [10.1. Overview]
Module msdescription
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
manuscript
Überlieferungsträger: Manuskript
subtype (subtype) provides a sub-categorization of the element, if needed
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
letter
Überlieferungsträger Unterkategorie: Brief
Member of
Contained by
linking: seg
msdescription: msItem provenance support
namesdates: object
textcrit: lem
textstructure: body div
transcr: supplied surplus
May contain
Note

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

Example
<msDesc>  <msIdentifier>   <settlement>Oxford</settlement>   <repository>Bodleian Library</repository>   <idno type="Bod">MS Poet. Rawl. D. 169.</idno>  </msIdentifier>  <msContents>   <msItem>    <author>Geoffrey Chaucer</author>    <title>The Canterbury Tales</title>   </msItem>  </msContents>  <physDesc>   <objectDesc>    <p>A parchment codex of 136 folios, measuring approx        28 by 19 inches, and containing 24 quires.</p>    <p>The pages are margined and ruled throughout.</p>    <p>Four hands have been identified in the manuscript: the first 44        folios being written in two cursive anglicana scripts, while the        remainder is for the most part in a mixed secretary hand.</p>   </objectDesc>  </physDesc> </msDesc>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="msIdentifier"/>
  <classRef key="model.headLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="1" minOccurs="1">
   <classRef key="model.pLike"
    maxOccurs="unbounded" minOccurs="1"/>
   <sequence maxOccurs="1" minOccurs="1">
    <elementRef key="msContents"
     minOccurs="0"/>
    <elementRef key="physDesc"
     minOccurs="0"/>
    <elementRef key="history" minOccurs="0"/>
    <elementRef key="additional"
     minOccurs="0"/>
    <alternate maxOccurs="1" minOccurs="1">
     <elementRef key="msPart"
      maxOccurs="unbounded" minOccurs="0"/>
     <elementRef key="msFrag"
      maxOccurs="unbounded" minOccurs="0"/>
    </alternate>
   </sequence>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msDesc
{
   attribute type { "manuscript" },
   attribute subtype { "letter" }?,
   (
      tei_msIdentifier,
      tei_model.headLike*,
      (
         tei_model.pLike+
       | (
            tei_msContents?,
            tei_physDesc?,
            tei_history?,
            tei_additional?,
            ( msPart* | msFrag* )
         )
      )
   )
}

1.55. <msIdentifier>

<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [10.4. The Manuscript Identifier]
Module msdescription
Member of
Contained by
core: bibl
msdescription: msDesc
May contain
header: idno
msdescription: repository
Example
<msIdentifier>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <idno>MS.El.26.C.9</idno> </msIdentifier>
Schematron
<sch:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or local-name(*[1])='altIdentifier' or normalize-space(.)='')">An msIdentifier must contain either a repository or location.</sch:report>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <sequence maxOccurs="1" minOccurs="1">
   <classRef expand="sequenceOptional"
    key="model.placeNamePart"/>
   <elementRef key="institution"
    minOccurs="0"/>
   <elementRef key="repository"
    minOccurs="0"/>
   <elementRef key="collection"
    maxOccurs="unbounded" minOccurs="0"/>
   <elementRef key="idno"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="msName"/>
   <elementRef key="objectName"/>
   <elementRef key="altIdentifier"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msIdentifier
{
   (
      tei_placeName?,
      tei_country?,
      tei_settlement?,
      institution?,
      tei_repository?,
      collection*,
      tei_idno*
   ),
   ( msName | tei_objectName | altIdentifier )*
}

1.56. <msItem>

<msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [10.6.1. The msItem and msItemStruct Elements]
Module msdescription
Member of
Contained by
msdescription: msContents msItem
May contain
analysis: interp interpGrp
header: idno
linking: anchor
msdescription: locus msDesc msItem
transcr: space
Example
<msItem class="#saga">  <locus>ff. 1r-24v</locus>  <title>Agrip af Noregs konunga sögum</title>  <incipit>regi oc h<ex>ann</ex> setiho  <gap extent="7reason="illegible"/>sc    heim se<ex>m</ex> þio</incipit>  <explicit>h<ex>on</ex> hev<ex>er</ex>   <ex>oc</ex>þa buit hesta .ij. aNan viþ    fé enh<ex>on</ex>o<ex>m</ex> aNan til    reiþ<ex>ar</ex>  </explicit>  <textLang mainLang="non">Old Norse/Icelandic</textLang> </msItem>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="locus"/>
   <elementRef key="locusGrp"/>
  </alternate>
  <alternate maxOccurs="1" minOccurs="1">
   <classRef key="model.pLike"
    maxOccurs="unbounded" minOccurs="1"/>
   <alternate maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.titlepagePart"/>
    <classRef key="model.msItemPart"/>
    <classRef key="model.global"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msItem
{
   ( tei_locus | locusGrp )*,
   (
      tei_model.pLike+
    | ( tei_model.titlepagePart | tei_model.msItemPart | tei_model.global )+
   )
}

1.57. <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Module core
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
sender
Bei Briefen: Abesender
recipient
Bei Briefen: Empfänger
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Note

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

Example
<name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name ref="#HOC001type="person">Occleve</name>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element name
{
   attribute type { "sender" | "recipient" }?,
   tei_macro.phraseSeq
}

1.58. <note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]
Module core
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Optional
Datatype ID
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Optional
Datatype teidata.text
corresp (corresponds) points to elements that correspond to the current element in some way.
Derived from att.global.linking
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
resp (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Derived from att.global.responsibility
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
#additionalAnnotation
Verantwortliche/r für die Anmerkung (nicht HaupteditorIn)
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
editions
Überlieferung: Angaben zu weiteren Ausgaben/Auflagen
copies
Überlieferung: Angaben zu wichtigsten Standorten / Hauptüberlieferungsträger
literature
Überlieferung: Sekundärliteratur
references
Überlieferung: weiterführende Deutungen
relatedPersons
Überlieferung: Personenbezüge
relatedPlaces
Überlieferung: Ortsbezüge
metDecl
Überlieferung: Metrische Angaben zu den Gedichten (Sprache, Versmaß, Versanzahl)
footnote
Apparate: Sachanmerkung
crit
Apparate: Textkritische Anmerkung
similia
Apparate: Similienanmerkung
legalNotes
Medien: Rechtesegment
legalNotice
Medien: Herkunft (rechtlich)
rightsHolder
Medien: RechteinhaberIn
subtype (subtype) provides a sub-categorization of the element, if needed
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
grc
Anmerkung bezieht sich auf den altgriechischen Textteil
grc-dor
Anmerkung bezieht sich auf den altgriechisch-dorischen Textteil
la
Anmerkung bezieht sich auf den lateinischen Textteil
private
Medien: RechteinhaberIn ist Privatperson
Member of
Contained by
May contain
Example In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note place="bottomresp="#MDMH"  type="gloss">  <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. <!-- elsewhere in the document --> <respStmt xml:id="MDMH">  <resp>translation from German to English</resp>  <name>Hottinger, Marie Donald Mackie</name> </respStmt>
For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.
Example The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century, <note anchored="truen="126"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann.
However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element note
{
   attribute xml:id { text }?,
   attribute n { text }?,
   attribute corresp { list { + } }?,
   attribute resp { list { "#additionalAnnotation"+ } }?,
   attribute type
   {
      "editions"
    | "copies"
    | "literature"
    | "references"
    | "relatedPersons"
    | "relatedPlaces"
    | "metDecl"
    | "footnote"
    | "crit"
    | "similia"
    | "legalNotes"
    | "legalNotice"
    | "rightsHolder"
   }?,
   attribute subtype { "grc" | "grc-dor" | "la" | "private" }?,
   tei_macro.specialPara
}

1.59. <num>

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]
Module core
Attributes
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Optional
Datatype teidata.text
type indicates the type of numeric value.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
cardinal
Metrikangaben: Angabe als Kardinalzahl
percentage
Metrikangaben: Angabe als Prozentzahl
numGroup
Metrikangaben: Zahlengruppe (Anzahl+Prozent)
Note

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

Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Note

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

Example
<p>I reached <num type="cardinalvalue="21">twenty-one</num> on my <num type="ordinalvalue="21">twenty-first</num> birthday</p> <p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>  </num> cm per second.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element num
{
   attribute n { text }?,
   attribute type { "cardinal" | "percentage" | "numGroup" },
   tei_macro.phraseSeq
}

1.60. <object>

<object> contains a description of a single identifiable physical object. [13.3.5. Objects]
Module namesdates
Member of
Contained by
namesdates: listObject object
May contain
Note

The <object> element is a recent addition to the TEI P5 Guidelines as of version 3.5.0 and as such may be more prone to further revision in the next few releases as its use develops. This may be particularly evident where its contents have been borrowed from <msDesc> and have yet to be generalized from their use in the context of manuscript descriptions.

The <object> element may be used for describing any object, text-bearing or not, though where the textuality of the object is the primary concern or a collection is mostly composed of manuscripts, encoders may prefer the <msDesc> element (a more specific form of <object>) which may be used not only to describe manuscripts but any form of text-bearing objects such as early printed books.

Example
<listObject>  <object xml:id="Alfred_Jewel">   <objectIdentifier>    <country>United Kingdom</country>    <region>Oxfordshire</region>    <settlement>Oxford</settlement>    <institution>University of Oxford</institution>    <repository>Ashmolean Museum</repository>    <collection>English Treasures</collection>    <idno type="ashmolean">AN1836p.135.371</idno>    <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>    <objectName>Alfred Jewel</objectName>   </objectIdentifier>   <physDesc>    <p> The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed <material>gold</material>        surrounding a polished teardrop shaped piece of transparent <material>quartz</material>. Underneath the rock        crystal is a cloisonné enamel image of a man with ecclesiastical symbols. The sides of the jewel holding the        crystal in place contain an openwork inscription saying "AELFRED MEC HEHT GEWYRCAN", meaning 'Alfred ordered        me made'. </p>   </physDesc>   <history>    <origin>It is generally accepted that the Alfred Jewel dates from the <origDate>late 9th Century</origDate> and        was most likely made in <origPlace>England</origPlace>. </origin>    <provenance when="1693">The jewel was discovered in 1693 at Petherton Park, North Petherton in the English        county of Somerset, on land owned by Sir Thomas Wroth. North Petherton is about 8 miles away from Athelney,        where King Alfred founded a monastery. </provenance>    <provenance when="1698">A description of the Alfred Jewel was first published in 1698, in the Philosophical        Transactions of the Royal Society.</provenance>    <acquisition> It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in        the Ashmolean Museum in Oxford. </acquisition>   </history>  </object> </listObject> <!-- Elsewhere in document --> <p> The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the <objectName ref="#Alfred_Jewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster    Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>. </p>
Example
<listObject>  <object xml:id="MaskOfTutankhamun">   <objectIdentifier>    <objectName xml:lang="en">Mask of Tutankhamun</objectName>    <idno type="carter">256a</idno>    <idno type="JournalD'Entrée">60672</idno>    <idno type="exhibition">220</idno>    <institution>Museum of Egyptian Antiquities</institution>    <address>     <street>15 Meret Basha</street>     <district>Ismailia</district>     <settlement>Cairo</settlement>     <country>Egypt</country>     <location>      <geo>30.047778, 31.233333</geo>     </location>    </address>   </objectIdentifier>   <msContents>    <p>The back and shoulders of the mask is inscribed with a protective spell in Egyptian hieroglyphs formed of ten        vertical and horizontal lines. This spell first appeared on masks in the Middle Kingdom at least 500 years        before Tutankhamun, and comes from chapter 151 of the <title>Book of the Dead</title>.</p>   </msContents>   <physDesc>    <p> The mask of Tutankhamun is 54cm x 39.3cm x 49cm. It is constructed from two layers of high-karat gold that        varies in thickness from 1.5-3mm. It weighs approximately 10.23kg and x-ray crystallography shows that it is        composed of two alloys of gold with a lighter 18.4 karat shade being used for the face and neck while a heavier        22.5 karat gold was used for the rest of the mask.</p>    <p>In the mask Tutankhamun wears a nemes headcloth which has the royal insignia of a cobra (Wadjet) and vulture        (Nekhbet) on it. These are thought respectively to symbolize Tutankhamun's rule of both Lower Egypt and Upper        Egypt. His ears are pierced for earrings. The mask has rich inlays of coloured glass and gemstones, including        lapis lazuli surrounding the eye and eyebrows, quartz for the eyes, obsidian for the pupils. The broad collar is        made up of carnelian, feldspar, turquoise, amazonite, faience and other stones.</p>   </physDesc>   <history>    <origin>     <p>The mask of Tutankhamun was created in <origPlace>Egypt</origPlace> around <origDate type="circawhen="-1323">1323 BC</origDate>. It is a death mask of the 18th-dynasty ancient Egyptian Pharaoh Tutankhamun          who reigned 1332–1323 BC. </p>    </origin>    <provenance>     <p>The mask of Tutankhamun was found in his burial chamber at Theban Necropolis in the Valley of the Kings in          1922. On 28 October 1925 the excavation team led by English archaeologist Howard Carter opened the heavy          sarcophagus and three coffins and were the first people in around 3,250 years to see the mask of Tutankhamun.          Carter wrote in his diary: <quote> The pins removed, the lid was raised. The penultimate scene was disclosed –            a very neatly wrapped mummy of the young king, with golden mask of sad but tranquil expression, symbolizing            Osiris … the mask bears that god's attributes, but the likeness is that of Tut.Ankh.Amen – placid and            beautiful, with the same features as we find upon his statues and coffins. The mask has fallen slightly            back, thus its gaze is straight up to the heavens. </quote>     </p>    </provenance>    <acquisition> In December 1925, the mask was removed from the tomb, placed in a crate and transported 635        kilometres (395 mi) to the Egyptian Museum in Cairo, where it remains on public display. </acquisition>   </history>   <additional>    <adminInfo>     <custodialHist>      <custEvent when="1944">When it was discovered in 1925, the 2.5kg narrow gold beard was no longer attached to            the mask and was reattached to the chin by use of a wooden dowel in 1944.</custEvent>      <custEvent when="2014-08"> In August 2014 when the mask was removed from its display case for cleaning, the            beard fell off again. Those working in the museum unadvisedly used a quick-drying epoxy to attempt to fix            it, but left the beard off-centre. </custEvent>      <custEvent when="2015-01">The damage was noticed and repaired in January 2015 by a German-Egyptian team who            used beeswax, a material known to be used as adhesives by the ancient Egyptians.</custEvent>     </custodialHist>    </adminInfo>   </additional>  </object> </listObject>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="objectIdentifier"
   maxOccurs="unbounded" minOccurs="1"/>
  <classRef key="model.headLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="1" minOccurs="1">
   <classRef key="model.pLike"
    maxOccurs="unbounded" minOccurs="0"/>
   <sequence maxOccurs="1" minOccurs="1">
    <elementRef key="msContents"
     minOccurs="0"/>
    <elementRef key="physDesc"
     minOccurs="0"/>
    <elementRef key="history" minOccurs="0"/>
    <elementRef key="additional"
     minOccurs="0"/>
   </sequence>
  </alternate>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
  </alternate>
  <elementRef key="object"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element object
{
   tei_objectIdentifier+,
   tei_model.headLike*,
   (
      tei_model.pLike*
    | ( tei_msContents?, tei_physDesc?, tei_history?, tei_additional? )
   ),
   ( tei_model.noteLike | tei_model.biblLike | linkGrp | link )*,
   tei_object*
}

1.61. <objectDesc>

<objectDesc> (object description) contains a description of the physical components making up the object which is being described. [10.7.1. Object Description]
Module msdescription
Member of
Contained by
msdescription: physDesc
May contain
core: p
msdescription: supportDesc
Example
<objectDesc form="codex">  <supportDesc material="mixed">   <p>Early modern   <material>parchment</material> and   <material>paper</material>.</p>  </supportDesc>  <layoutDesc>   <layout ruledLines="25 32"/>  </layoutDesc> </objectDesc>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence maxOccurs="1" minOccurs="1">
   <elementRef key="supportDesc"
    minOccurs="0"/>
   <elementRef key="layoutDesc"
    minOccurs="0"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element objectDesc { tei_model.pLike+ | ( tei_supportDesc?, layoutDesc? ) }

1.62. <objectIdentifier>

<objectIdentifier> (object identifier) groups one or more identifiers or pieces of locating information concerning a single object. [13.3.5. Objects]
Module namesdates
Member of
Contained by
core: bibl
namesdates: object
May contain
header: idno
msdescription: repository
Example
<objectIdentifier>  <country>United Kingdom</country>  <region>Oxfordshire</region>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Ashmolean Museum</repository>  <collection>English Treasures</collection>  <idno type="ashmolean">AN1836p.135.371</idno>  <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>  <objectName>Alfred Jewel</objectName> </objectIdentifier>
Example
<object xml:id="Excalibur-MultipleNames">  <objectIdentifier>   <objectName type="main">Excalibur</objectName>   <objectName type="alt">Caliburn</objectName>   <objectName xml:lang="cy">Caledfwlch</objectName>   <objectName xml:lang="cnx">Calesvol</objectName>   <objectName xml:lang="br">Kaledvoulc'h</objectName>   <objectName xml:lang="la">Caliburnus</objectName>   <country>Wales</country>  </objectIdentifier>  <p>Excalibur is the name for the legendary sword of King Arthur, in Welsh it is called Caledfwlch,    in Cornish it is called Calesvol, in Breton it is called Kaledvoulc'h, and in Latin it is called Caliburnus.    In some versions Excalibur's blade was engraved with phrases on opposite sides which in translation read:    "Take me up" and "Cast me away" (or similar).</p> </object>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.placeNamePart"/>
  <elementRef key="institution"/>
  <elementRef key="repository"/>
  <elementRef key="collection"/>
  <elementRef key="idno"/>
  <elementRef key="msName"/>
  <elementRef key="objectName"/>
  <elementRef key="altIdentifier"/>
  <elementRef key="address"/>
 </alternate>
</content>
    
Schema Declaration
element objectIdentifier
{
   (
      tei_model.placeNamePart
    | institution
    | tei_repository
    | collection
    | tei_idno
    | msName
    | tei_objectName
    | altIdentifier
    | address
   )+
}

1.63. <objectName>

<objectName> (name of an object) contains a proper noun or noun phrase used to refer to an object. [13.2.4. Object Names]
Module namesdates
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
<p> The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the <objectName ref="#AlfredJewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster    Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>. </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element objectName { tei_macro.phraseSeq }

1.64. <opener>

<opener> (opener) groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. [4.2. Elements Common to All Divisions]
Module textstructure
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
center
Ausrichtung im Original: zentriert
right
Ausrichtung im Original: rechtsbündig
Member of
Contained by
core: lg list
textstructure: body div
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
<opener>  <dateline>Walden, this 29. of August 1592</dateline> </opener>
Example
<opener>  <dateline>   <name type="place">Great Marlborough Street</name>   <date>November 11, 1848</date>  </dateline>  <salute>My dear Sir,</salute> </opener> <p>I am sorry to say that absence from town and other circumstances have prevented me from earlier enquiring...</p>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="argument"/>
  <elementRef key="byline"/>
  <elementRef key="dateline"/>
  <elementRef key="epigraph"/>
  <elementRef key="salute"/>
  <elementRef key="signed"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element opener
{
   attribute rend { list { ( "center" | "right" )+ } }?,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | argument
    | byline
    | dateline
    | epigraph
    | salute
    | signed
    | tei_model.global
   )*
}

1.65. <orig>

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 12. Critical Apparatus]
Module core
Member of
Contained by
May contain
Example If all that is desired is to call attention to the original version in the copy text, <orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l> <l>And hardly shall we all be <orig>vnderstoode</orig> </l>
Example More usually, an <orig> will be combined with a regularized form within a <choice> element:
<l>But this will be a <choice>   <orig>meere</orig>   <reg>mere</reg>  </choice> confusion</l> <l>And hardly shall we all be <choice>   <orig>vnderstoode</orig>   <reg>understood</reg>  </choice> </l>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element orig { tei_macro.paraContent }

1.66. <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Module core
Member of
Contained by
May contain
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you    done?</q> </p> <p>  <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. </p> <p>  <q>Then you must mean that Thorvald is dead,</q> she said. </p> <p>  <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> </p>
Schematron
<sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText |parent::tei:exemplum |parent::tei:item |parent::tei:note |parent::tei:q |parent::tei:quote |parent::tei:remarks |parent::tei:said |parent::tei:sp |parent::tei:stage |parent::tei:cell |parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. </sch:report>
Schematron
<sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not( ancestor::tei:floatingText |parent::tei:figure |parent::tei:note )"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. </sch:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element p { tei_macro.paraContent }

1.67. <pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]
Module core
Attributes
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Required
Datatype teidata.text
Member of
Contained by
May contain Empty element
Note

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

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

Example Page numbers may vary in different editions of a text.
<p> ... <pb ed="ed2n="145"/> <!-- Page 145 in edition "ed2" starts here --> ... <pb ed="ed1n="283"/> <!-- Page 283 in edition "ed1" starts here--> ... </p>
Example A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute
<body>  <pb facs="page1.pngn="1"/> <!-- page1.png contains an image of the page; the text it contains is encoded here -->  <p> <!-- ... -->  </p>  <pb facs="page2.pngn="2"/> <!-- similarly, for page 2 -->  <p> <!-- ... -->  </p> </body>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element pb { attribute n { text }, empty }

1.68. <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
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
<persName>  <forename>Edward</forename>  <forename>George</forename>  <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of  <placeName>Knebworth</placeName>  </roleName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element persName { tei_macro.phraseSeq }

1.69. <physDesc>

<physDesc> (physical description) contains a full physical description of a manuscript, manuscript part, or other object optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description]
Module msdescription
Contained by
msdescription: msDesc
namesdates: object
May contain
core: p
msdescription: handDesc objectDesc
Example
<physDesc>  <objectDesc form="codex">   <supportDesc material="perg">    <support>Parchment.</support>    <extent>i + 55 leaves    <dimensions scope="alltype="leaf"      unit="inch">      <height></height>      <width>5⅜</width>     </dimensions>    </extent>   </supportDesc>   <layoutDesc>    <layout columns="2">In double columns.</layout>   </layoutDesc>  </objectDesc>  <handDesc>   <p>Written in more than one hand.</p>  </handDesc>  <decoDesc>   <p>With a few coloured capitals.</p>  </decoDesc> </physDesc>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef expand="sequenceOptional"
   key="model.physDescPart"/>
 </sequence>
</content>
    
Schema Declaration
element physDesc { tei_model.pLike*, tei_objectDesc?, tei_handDesc? }

1.70. <placeName>

<placeName> (place name) contains an absolute or relative place name. [13.2.3. Place Names]
Module namesdates
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
<placeName>  <settlement>Rochester</settlement>  <region>New York</region> </placeName>
Example
<placeName>  <geogName>Arrochar Alps</geogName>  <region>Argylshire</region> </placeName>
Example
<placeName>  <measure>10 miles</measure>  <offset>Northeast of</offset>  <settlement>Attica</settlement> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element placeName { tei_macro.phraseSeq }

1.71. <profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Module header
Member of
Contained by
header: teiHeader
May contain
Note

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

Example
<profileDesc>  <langUsage>   <language ident="fr">French</language>  </langUsage>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose degree="hightype="entertain"/>   <purpose degree="mediumtype="inform"/>  </textDesc>  <settingDesc>   <setting>    <name>Paris, France</name>    <time>Late 19th century</time>   </setting>  </settingDesc> </profileDesc>
Content model
<content>
 <classRef key="model.profileDescPart"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
    
Schema Declaration
element profileDesc { tei_model.profileDescPart* }

1.72. <projectDesc>

<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]
Module header
Member of
Contained by
header: encodingDesc
May contain
core: p
Example
<projectDesc>  <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element projectDesc { tei_model.pLike+ }

1.73. <provenance>

<provenance> (provenance) contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript, manuscript part, or other object after its creation but before its acquisition. [10.8. History]
Module msdescription
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
dedication
Widmung
Contained by
msdescription: history
May contain
Example
<provenance>Listed as the property of Lawrence Sterne in 1788.</provenance> <provenance>Sold at Sothebys in 1899.</provenance>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element provenance { attribute type { "dedication" }, tei_macro.specialPara }

1.74. <ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 16.1. Links]
Module core
Attributes
target specifies the destination of the reference by supplying one or more URI References
Derived from att.pointing
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
verse
Verweis auf einen Vers
Member of
Contained by
May contain Empty element
Example
<ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/>
Schematron
<sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element ptr
{
   attribute target { list { + } },
   attribute type { "verse" },
   empty
}

1.75. <pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module core
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
<publicationStmt>  <publisher>Oxford University Press</publisher>  <pubPlace>Oxford</pubPlace>  <date>1989</date> </publicationStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element pubPlace { tei_macro.phraseSeq }

1.76. <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
Contained by
header: fileDesc
May contain
Note

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

Example
<publicationStmt>  <publisher>C. Muquardt </publisher>  <pubPlace>Bruxelles &amp; Leipzig</pubPlace>  <date when="1846"/> </publicationStmt>
Example
<publicationStmt>  <publisher>Chadwyck Healey</publisher>  <pubPlace>Cambridge</pubPlace>  <availability>   <p>Available under licence only</p>  </availability>  <date when="1992">1992</date> </publicationStmt>
Example
<publicationStmt>  <publisher>Zea Books</publisher>  <pubPlace>Lincoln, NE</pubPlace>  <date>2017</date>  <availability>   <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>  </availability>  <ptr target="http://digitalcommons.unl.edu/zeabook/55"/> </publicationStmt>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.publicationStmtPart.agency"/>
   <classRef key="model.publicationStmtPart.detail"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element publicationStmt
{
   (
      tei_model.publicationStmtPart.agency,
      tei_model.publicationStmtPart.detail*
   )+
 | tei_model.pLike+
}

1.77. <publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Module core
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Note

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

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

1.78. <recording>

<recording> (recording event) provides details of an audio or video recording event used as the source of a spoken text, either directly or from a public broadcast. [8.2. Documenting the Source of Transcribed Speech 15.3.2. Declarable Elements]
Module spoken
Attributes att.duration (att.duration.w3c (@dur)) (att.duration.iso (@dur-iso))
type the kind of recording.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
audio
Medien: Medientyp Audio[Default]
Contained by
May contain
Note

The dur attribute is used to indicate the original duration of the recording.

Example
<recording dur="P30Mtype="audio">  <equipment>   <p>Recorded on a Sony TR444 walkman by unknown participants; remastered      to digital tape at <placeName>Borehamwood Studios</placeName> by   <orgName>Transcription Services Inc</orgName>.</p>  </equipment> </recording>
Example
<recording dur="P10Mtype="audio">  <equipment>   <p>Recorded from FM Radio to digital tape</p>  </equipment>  <broadcast>   <bibl>    <title>Interview on foreign policy</title>    <author>BBC Radio 5</author>    <respStmt>     <resp>interviewer</resp>     <name>Robin Day</name>    </respStmt>    <respStmt>     <resp>interviewee</resp>     <name>Margaret Thatcher</name>    </respStmt>    <series>     <title>The World Tonight</title>    </series>    <note>First broadcast on    <date when="1989-11-27">27 Nov 89</date>    </note>   </bibl>  </broadcast> </recording>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.recordingPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element recording
{
   tei_att.duration.attributes,
   attribute type { "audio" },
   ( tei_model.recordingPart | tei_model.pLike )*
}

1.79. <recordingStmt>

<recordingStmt> (recording statement) describes a set of recordings used as the basis for transcription of a spoken text. [8.2. Documenting the Source of Transcribed Speech 2.2.7. The Source Description]
Module spoken
Member of
Contained by
header: sourceDesc
May contain
core: p
spoken: recording
Example
<recordingStmt>  <recording dur="P30Mtype="audio">   <respStmt>    <resp>Location recording by</resp>    <name>Sound Services Ltd.</name>   </respStmt>   <equipment>    <p>Multiple close microphones mixed down to stereo Digital        Audio Tape, standard play, 44.1 KHz sampling frequency</p>   </equipment>   <date>12 Jan 1987</date>  </recording> </recordingStmt>
Example
<recordingStmt>  <p>Three    distinct recordings made by hidden microphone in early February    2001.</p> </recordingStmt>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="recording"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element recordingStmt { tei_model.pLike+ | tei_recording+ }

1.80. <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 16.1. Links]
Module core
Attributes
sameAs points to an element that is the same as the current element.
Derived from att.global.linking
Status Optional
Datatype teidata.pointer
target specifies the destination of the reference by supplying one or more URI References
Derived from att.pointing
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
internal
Interner Verweis (z.B. auf eine andere Editionseinheit)
external
Externer Verweis (z.B. auf eine externe Website)
subtype (subtype) provides a sub-categorization of the element, if needed
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
di
Verweis Unterkategorie: Verweis auf Deutsche Inschriften Online
digitalCopy
Verweis Unterkategorie: Verweis auf ein digitales Faksimile
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term> </ref>.
Schematron
<sch:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <sch:name/> </sch:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element ref
{
   attribute sameAs { text }?,
   attribute target { list { + } },
   attribute type { "internal" | "external" },
   attribute subtype { "di" | "digitalCopy" }?,
   tei_macro.paraContent
}

1.81. <reg>

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 12. Critical Apparatus]
Module core
Member of
Contained by
May contain
Example If all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg> </q>
Example It is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings:
<q>Please <choice>   <reg resp="#LB">knock</reg>   <orig>cnk</orig>  </choice> if an <choice>   <reg>answer</reg>   <orig>nsr</orig>  </choice> is <choice>   <reg>required</reg>   <orig>reqd</orig>  </choice> </q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element reg { tei_macro.paraContent }

1.82. <repository>

<repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier]
Module msdescription
Contained by
msdescription: msIdentifier
namesdates: objectIdentifier
May contain
analysis: interp interpGrp
header: idno
linking: anchor
transcr: space
character data
Example
<msIdentifier>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Bodleian Library</repository>  <idno>MS. Bodley 406</idno> </msIdentifier>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element repository { tei_macro.phraseSeq.limited }

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.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Module core
Contained by
core: respStmt
May contain
analysis: interp interpGrp
header: idno
linking: anchor
transcr: space
character data
Note

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

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

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.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Module core
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
Legal values are:
transcription
Verantwortlichkeiten: Transkription
annotation
Verantwortlichkeiten: Annotation
edition
Verantwortlichkeiten: Edition (hauptverantwortliche/r EditorIn)
transmission
Verantwortlichkeiten: Überlieferung
introduction
Verantwortlichkeiten: Einleitung
additionalAnnotation
Verantwortlichkeiten: Ergänzende Annotation (nicht durch HaupteditorIn)
translation
Verantwortlichkeiten: Übersetzung ins Deutsche
similia
Verantwortlichkeiten: Similien
encoding
Verantwortlichkeiten: Kodierung
markup
Verantwortlichkeiten: Auszeichnung
Member of
Contained by
header: titleStmt
msdescription: msItem
spoken: recording
May contain
core: name note resp
namesdates: persName
Example
<respStmt>  <resp>transcribed from original ms</resp>  <persName>Claus Huitfeldt</persName> </respStmt>
Example
<respStmt>  <resp>converted to XML encoding</resp>  <name>Alan Morrison</name> </respStmt>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="1" minOccurs="1">
   <sequence maxOccurs="1" minOccurs="1">
    <elementRef key="resp"
     maxOccurs="unbounded" minOccurs="1"/>
    <classRef key="model.nameLike.agent"
     maxOccurs="unbounded" minOccurs="1"/>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <classRef key="model.nameLike.agent"
     maxOccurs="unbounded" minOccurs="1"/>
    <elementRef key="resp"
     maxOccurs="unbounded" minOccurs="1"/>
   </sequence>
  </alternate>
  <elementRef key="note"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element respStmt
{
   attribute xml:id
   {
      "transcription"
    | "annotation"
    | "edition"
    | "transmission"
    | "introduction"
    | "additionalAnnotation"
    | "translation"
    | "similia"
    | "encoding"
    | "markup"
   },
   (
      (
         ( tei_resp+, tei_model.nameLike.agent+ )
       | ( tei_model.nameLike.agent+, tei_resp+ )
      ),
      tei_note*
   )
}

1.85. <revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Module header
Attributes
status describes the status of a document either currently or, when associated with a dated element, at the time indicated.
Derived from att.docStatus
Status Required
Datatype teidata.enumerated
Legal values are:
core_collection_file
Kernbestand (Einheit vollständig ediert, enthält Metadaten und Transkription)
auxiliary_collection_file
Erweiterter Bestand (Einheit nicht ediert, enthält Metadaten aber keine Transkription)
Contained by
header: teiHeader
May contain
core: list
header: change
Note

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

Example
<revisionDesc status="embargoed">  <change when="1991-11-11who="#LB"> deleted chapter 10 </change> </revisionDesc>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <elementRef key="list"/>
  <elementRef key="listChange"/>
  <elementRef key="change"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element revisionDesc
{
   attribute status { "core_collection_file" | "auxiliary_collection_file" },
   ( tei_list | listChange | tei_change+ )
}

1.86. <rs>

<rs> (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.6.1. Referring Strings]
Module core
Attributes
ref (reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
Derived from att.canonical
Status Required
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
index
Verweis ins Register (Index)
bibl
Verweis ins Register (Bibliographie)
subtype (subtype) provides a sub-categorization of the element, if needed
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
verified
Textstelle im verwiesenen bibliographischen Eintrag nachgewiesen
not-verified
Textstelle im verwiesenen bibliographischen Eintrag nicht nachgewiesen
not-checked
Textstelle im verwiesenen bibliographischen Eintrag nicht geprüft
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
<q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs> to him one day, <q>have you heard that <rs type="place">Netherfield Park</rs> is let at last?</q>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rs
{
   attribute ref { list { + } },
   attribute type { "index" | "bibl" },
   attribute subtype { "verified" | "not-verified" | "not-checked" }?,
   tei_macro.phraseSeq
}

1.87. <seg>

<seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents]
Module linking
Attributes att.datcat (datcat, valueDatcat, @targetDatcat)
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 teidata.language
Legal values are:
la
Sprache: Lateinisch
grc
Sprache: Altgriechisch
grc-dor
Sprache: Altgriechisch-dorisch
de
Sprache: Deutsch
de-enh
Sprache: Frühneuhochdeutsch
ana (analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Derived from att.global.analytic
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
met (metrical structure, conventional) contains a user-specified encoding for the conventional metrical structure of the element.
Derived from att.metrical
Status Optional
Datatype token
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
metDeclLanguage
Metrische Angaben zu den Gedichten: Sprachangaben
meter
Metrische Angaben zu den Gedichten: Versmaß
verseCount
Metrische Angaben zu den Gedichten: Gesamtverszahl
name
Register: Name
nameVariants
Register: Namensvariante
gnd
Register: GND-Nummer
desc
Register: Beschreibung
mainText
Transkription: Haupttext
marginalia
Transkription: Marginalie
translationOfMainText
Transkription: Übersetzung des Haupttextes
translationOfMarginalia
Transkription: Übersetzung der Marginalie
spondaic
Auszeichnung: Spondiacus
monosyllabum
Auszeichnung: Monosyllabum
subtype (subtype) provides a sub-categorization of the element, if needed
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
mainText
Marginalie | Übersetzung (Marg.) bezieht sich auf den Haupttext
translationOfMainText
Marginalie | Übersetzung (Marg.) bezieht sich nicht auf den Haupttext
all
Übersetzung (Marg.) bezieht sich auf alle Marginalien im Vers
name
Register: Name
nameVariants
Register: Namensvariante
gnd
Register: GND-Nummer
desc
Register: Beschreibung
mainText
Transkription: Haupttext
marginalia
Transkription: Marginalie
translationOfMainText
Transkription: Übersetzung des Haupttextes
translationOfMarginalia
Transkription: Übersetzung der Marginalie
spondaic
Auszeichnung: Spondiacus
monosyllabum
Auszeichnung: Monosyllabum
refName
Interner Verweis: Namenskürzel
refTitle
Interner Verweis: Kurztitel
refNumber
Interner Verweis: Gedichtanzahl
refVerse
Interner Verweis: Vers
Member of
Contained by
May contain
Note

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

Example
<seg>When are you leaving?</seg> <seg>Tomorrow.</seg>
Example
<s>  <seg rend="capstype="initial-cap">So father's only</seg> glory was the ballfield. </s>
Example
<seg type="preamble">  <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>  <seg>Sinfiotli was the eldest of his sons ...</seg>  <seg>Borghild, Sigmund's wife, had a brother ... </seg> </seg>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element seg
{
   tei_att.datcat.attribute.targetDatcat,
   attribute xml:lang { "la" | "grc" | "grc-dor" | "de" | "de-enh" }?,
   attribute ana { list { + } }?,
   attribute met { text }?,
   attribute type
   {
      "metDeclLanguage"
    | "meter"
    | "verseCount"
    | "name"
    | "nameVariants"
    | "gnd"
    | "desc"
    | "mainText"
    | "marginalia"
    | "translationOfMainText"
    | "translationOfMarginalia"
    | "spondaic"
    | "monosyllabum"
   },
   attribute subtype
   {
      "mainText"
    | "translationOfMainText"
    | "all"
    | "name"
    | "nameVariants"
    | "gnd"
    | "desc"
    | "mainText"
    | "marginalia"
    | "translationOfMainText"
    | "translationOfMarginalia"
    | "spondaic"
    | "monosyllabum"
    | "refName"
    | "refTitle"
    | "refNumber"
    | "refVerse"
   }?,
   tei_macro.paraContent
}

1.88. <settlement>

<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [13.2.3. Place Names]
Module namesdates
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Example
<placeName>  <settlement type="town">Glasgow</settlement>  <region>Scotland</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element settlement { tei_macro.phraseSeq }

1.89. <sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
Module header
Contained by
header: fileDesc
May contain
msdescription: msDesc
namesdates: listObject
Example
<sourceDesc>  <bibl>   <title level="a">The Interesting story of the Children in the Wood</title>. In  <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.  <publisher>OUP</publisher>   <date>1968</date>. </bibl> </sourceDesc>
Example
<sourceDesc>  <p>Born digital: no previous source exists.</p> </sourceDesc>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.biblLike"/>
   <classRef key="model.sourceDescPart"/>
   <classRef key="model.listLike"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element sourceDesc
{
   tei_model.pLike+
 | ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+
}

1.90. <space>

<space> (space) indicates the location of a significant space in the text. [11.4.1. Space]
Module transcr
Member of
Contained by
May contain
core: desc
Note

This element should be used wherever it is desired to record an unusual space in the source text, e.g. space left for a word to be filled in later, for later rubrication, etc. It is not intended to be used to mark normal inter-word space or the like.

Example
By god if wommen had writen storyes As <space quantity="7unit="minims"/> han within her oratoryes
Example
στρατηλάτ<space quantity="1unit="chars"/>ου
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element space { ( tei_model.descLike | tei_model.certLike )* }

1.91. <supplied>

<supplied> (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Module transcr
Member of
Contained by
May contain
Note

The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

Example
I am dr Sr yr <supplied reason="illegible"  source="#amanuensis_copy">very humble Servt</supplied> Sydney Smith
Example
<supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element supplied { tei_macro.paraContent }

1.92. <support>

<support> (support) contains a description of the materials etc. which make up the physical support for the written part of a manuscript or other object. [10.7.1. Object Description]
Module msdescription
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 teidata.word separated by whitespace
Legal values are:
surviving
Steinplatte erhalten
lost
Steinplatte nicht erhalten
Contained by
msdescription: supportDesc
May contain
Example
<objectDesc form="roll">  <supportDesc>   <support> Parchment roll with <material>silk</material> ribbons.   </support>  </supportDesc> </objectDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element support
{
   attribute rend { list { ( "surviving" | "lost" )+ } },
   tei_macro.specialPara
}

1.93. <supportDesc>

<supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript or other object. [10.7.1. Object Description]
Module msdescription
Contained by
msdescription: objectDesc
May contain
core: p
header: extent
msdescription: support
Example
<supportDesc>  <support> Parchment roll with <material>silk</material> ribbons.  </support> </supportDesc>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence maxOccurs="1" minOccurs="1">
   <elementRef key="support" minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="foliation"
    maxOccurs="unbounded" minOccurs="0"/>
   <elementRef key="collation"
    minOccurs="0"/>
   <elementRef key="condition"
    minOccurs="0"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element supportDesc
{
   tei_model.pLike+
 | ( tei_support?, tei_extent?, foliation*, collation?, condition? )
}

1.94. <surplus>

<surplus> (surplus) marks text present in the source which the editor believes to be superfluous or redundant. [11.3.3.1. Damage, Illegibility, and Supplied Text]
Module transcr
Member of
Contained by
May contain
Example
I am dr Sr yrs <surplus reason="repeated">yrs</surplus> Sydney Smith
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element surplus { tei_macro.paraContent }

1.95. <teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
Module header
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Required
Datatype ID
Contained by
textstructure: TEI
May contain
Note

One of the few elements unconditionally required in any TEI document.

Example
<teiHeader>  <fileDesc>   <titleStmt>    <title>Shakespeare: the first folio (1623) in electronic form</title>    <author>Shakespeare, William (1564–1616)</author>    <respStmt>     <resp>Originally prepared by</resp>     <name>Trevor Howard-Hill</name>    </respStmt>    <respStmt>     <resp>Revised and edited by</resp>     <name>Christine Avern-Carr</name>    </respStmt>   </titleStmt>   <publicationStmt>    <distributor>Oxford Text Archive</distributor>    <address>     <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>    </address>    <idno type="OTA">119</idno>    <availability>     <p>Freely available on a non-commercial basis.</p>    </availability>    <date when="1968">1968</date>   </publicationStmt>   <sourceDesc>    <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,        1968)</bibl>   </sourceDesc>  </fileDesc>  <encodingDesc>   <projectDesc>    <p>Originally prepared for use in the production of a series of old-spelling        concordances in 1968, this text was extensively checked and revised for use during the        editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>   </projectDesc>   <editorialDecl>    <correction>     <p>Turned letters are silently corrected.</p>    </correction>    <normalization>     <p>Original spelling and typography is retained, except that long s and ligatured          forms are not encoded.</p>    </normalization>   </editorialDecl>   <refsDecl xml:id="ASLREF">    <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"     replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">     <p>A reference is created by assembling the following, in the reverse order as that          listed here: <list>       <item>the <att>n</att> value of the preceding <gi>lb</gi>       </item>       <item>a period</item>       <item>the <att>n</att> value of the ancestor <gi>div2</gi>       </item>       <item>a space</item>       <item>the <att>n</att> value of the parent <gi>div1</gi>       </item>      </list>     </p>    </cRefPattern>   </refsDecl>  </encodingDesc>  <revisionDesc>   <list>    <item>     <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>    <item>     <date when="1989-03-01">1 Mar 89</date> LB made new file</item>   </list>  </revisionDesc> </teiHeader>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="fileDesc"/>
  <classRef key="model.teiHeaderPart"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="revisionDesc"
   minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element teiHeader
{
   attribute xml:id { text },
   ( tei_fileDesc, tei_model.teiHeaderPart*, tei_revisionDesc? )
}

1.96. <term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Module core
Member of
Contained by
May contain
analysis: interp interpGrp
gaiji: g
header: idno
linking: anchor seg
character data
Note

When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a <term> element by means of its target attribute.

In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion.

As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

Example
A computational device that infers structure from grammatical strings of words is known as a <term>parser</term>, and much of the history of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term rend="scxml:id="TDPV1">discoursal point of view</term> as <gloss target="#TDPV1">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Example
We may define <term ref="#TDPV2rend="sc">discoursal point of view</term> as <gloss xml:id="TDPV2">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Example
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2rend="sc">discoursal point of view</term> below.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element term { tei_macro.phraseSeq }

1.97. <text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text]
Module textstructure
Member of
Contained by
textstructure: TEI
May contain
analysis: interp interpGrp
core: lb note pb
linking: anchor
textstructure: back body front
transcr: space
Note

This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.

Example
<text>  <front>   <docTitle>    <titlePart>Autumn Haze</titlePart>   </docTitle>  </front>  <body>   <l>Is it a dragonfly or a maple leaf</l>   <l>That settles softly down upon the water?</l>  </body> </text>
Example The body of a text may be replaced by a group of nested texts, as in the following schematic:
<text>  <front> <!-- front matter for the whole group -->  </front>  <group>   <text> <!-- first text -->   </text>   <text> <!-- second text -->   </text>  </group> </text>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="1" minOccurs="0">
   <elementRef key="front"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate maxOccurs="1" minOccurs="1">
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="1" minOccurs="0">
   <elementRef key="back"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element text
{
   tei_model.global*,
   ( tei_front, tei_model.global* )?,
   ( tei_body | group ),
   tei_model.global*,
   ( tei_back, tei_model.global* )?
}

1.98. <textClass>

<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
Module header
Attributes
type
Status Required
Legal values are:
workPurpose
Werkgruppe (z.B. Haupttext, Private Kommunikation)
literaryGenre
Editorische Gattungszuordnung (z.B. Epos, Lehrgedicht, Totengedicht, Dankgedicht)
literaryGenreRhodoman
Gattungszuordnung wie im Original
creativePeriod
Schaffensphase (z.B. Ilfelder Periode, Harburger Periode)
Member of
Contained by
header: profileDesc
May contain
header: keywords
Example
<taxonomy>  <category xml:id="acprose">   <catDesc>Academic prose</catDesc>  </category> <!-- other categories here --> </taxonomy> <!-- ... --> <textClass>  <catRef target="#acprose"/>  <classCode scheme="http://www.udcc.org">001.9</classCode>  <keywords scheme="http://authorities.loc.gov">   <list>    <item>End of the world</item>    <item>History - philosophy</item>   </list>  </keywords> </textClass>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="classCode"/>
  <elementRef key="catRef"/>
  <elementRef key="keywords"/>
 </alternate>
</content>
    
Schema Declaration
element textClass
{
   attribute type
   {
      "workPurpose"
    | "literaryGenre"
    | "literaryGenreRhodoman"
    | "creativePeriod"
   },
   ( classCode | catRef | tei_keywords )*
}

1.99. <textLang>

<textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 10.6.6. Languages and Writing Systems]
Module core
Attributes
mainLang (main language) supplies a code which identifies the chief language used in the bibliographic work.
Status Required
Datatype teidata.language
Legal values are:
la
Sprache: Lateinisch
grc
Sprache: Altgriechisch
grc-dor
Sprache: Altgriechisch-dorisch
de
Sprache: Deutsch
de-enh
Sprache: Frühneuhochdeutsch
Member of
Contained by
msdescription: msContents msItem
May contain
Note

This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for all other TEI elements, such information should be provided by means of the global xml:lang attribute attached to the element containing the description.

In all cases, languages should be identified by means of a standardized ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a <language> element in the TEI header.

Example
<textLang mainLang="enotherLangs="la"> Predominantly in English with Latin glosses</textLang>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element textLang
{
   attribute mainLang { "la" | "grc" | "grc-dor" | "de" | "de-enh" },
   tei_macro.specialPara
}

1.100. <title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Module core
Attributes
type classifies the title according to some convenient typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
file
Titel der Datei
quoteInternal
Internes Kürzel
quoteExternal
Zitationsvorschlag
main
Haupttitel
sub
Untertitel
poem
Gedichttitel
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
Contained by
May contain
Note

The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

Example
<title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title>
Example
<title type="full">  <title type="main">Synthèse</title>  <title type="sub">an international journal for    epistemology, methodology and history of    science</title> </title>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element title
{
   attribute type
   {
      "file" | "quoteInternal" | "quoteExternal" | "main" | "sub" | "poem"
   }?,
   tei_macro.paraContent
}

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
Contained by
header: fileDesc
May contain
Example
<titleStmt>  <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>  <respStmt>   <resp>compiled by</resp>   <name>P.J. Lucas</name>  </respStmt> </titleStmt>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="title"
   maxOccurs="unbounded" minOccurs="1"/>
  <classRef key="model.respLike"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element titleStmt { tei_title+, tei_model.respLike* }

1.102. <width>

<width> (width) contains a measurement of an object along the axis parallel to its bottom, e.g. perpendicular to the spine of a book or codex. [10.3.4. Dimensions]
Module msdescription
Member of
Contained by
May contain
gaiji: g
character data
Note

If used to specify the depth of a non text-bearing portion of some object, for example a monument, this element conventionally refers to the axis facing the observer, and perpendicular to that indicated by the ‘depth’ axis.

Example
<width unit="in">4</width>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element width { tei_macro.xtext }

2. Model classes

2.1. model.attributable

model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]
Module tei
Used by
Members model.quoteLike

2.2. model.availabilityPart

model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]
Module tei
Used by
Members licence

2.3. model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]
Module tei
Used by
Members bibl biblStruct listBibl msDesc

2.4. model.biblPart

model.biblPart groups elements which represent components of a bibliographic description. [3.12. Bibliographic Citations and References]
Module tei
Used by
Members model.imprintPart[biblScope pubPlace publisher] model.respLike[author respStmt] availability bibl extent msIdentifier objectIdentifier textLang

2.5. model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Module tei
Used by
Members model.divPart[model.divPart.spoken model.lLike[l] model.pLike[p] lg] model.inter[model.attributable[model.quoteLike] model.biblLike[bibl biblStruct listBibl msDesc] model.egLike model.labelLike[desc] model.listLike[list listObject] model.oddDecl model.stageLike]
Note

This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions.

2.6. model.correspActionPart

model.correspActionPart groups elements which define the parts (usually names, dates and places) of one action related to the correspondence.
Module tei
Used by
Members model.addressLike model.dateLike[date] model.nameLike[model.nameLike.agent[name persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[country placeName settlement]] idno objectName rs] note

2.7. model.correspDescPart

model.correspDescPart groups together metadata elements for describing correspondence
Module tei
Used by
Members correspAction note

2.8. model.dateLike

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

2.9. model.descLike

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

2.10. model.dimLike

model.dimLike groups elements which describe a measurement forming part of the physical dimensions of some object.
Module tei
Used by
Members depth height width

2.11. model.divBottom

model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]
Module tei
Used by
Members model.divBottomPart[closer] model.divWrapper

2.12. model.divBottomPart

model.divBottomPart groups elements which can occur only at the end of a text division. [4.6. Title Pages]
Module tei
Used by
Members closer

2.13. model.divLike

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

2.14. model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Module tei
Used by
Members model.divPart.spoken model.lLike[l] model.pLike[p] lg
Note

Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

2.15. model.divTop

model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions]
Module tei
Used by
Members model.divTopPart[model.headLike[head] opener] model.divWrapper

2.16. model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]
Module tei
Used by
Members model.headLike[head] opener

2.17. 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
Used by
Members distinct term title

2.18. model.encodingDescPart

model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.
Module tei
Used by
Members metDecl projectDesc

2.19. model.frontPart

model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ]
Module tei
Used by
Members model.frontPart.drama listBibl

2.20. model.gLike

model.gLike groups elements used to represent individual non-Unicode characters or glyphs.
Module tei
Used by
Members g

2.21. model.global

2.22. model.global.edit

model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]
Module tei
Used by
Members space

2.23. model.global.meta

model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]
Module tei
Used by
Members interp interpGrp
Note

Elements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text.

2.24. model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]
Module tei
Used by
Members media

2.25. model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Module tei
Used by
Members head

2.26. 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
Used by
Members hi

2.27. model.highlighted

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

2.28. model.imprintPart

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

2.29. model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
Module tei
Used by
Members model.attributable[model.quoteLike] model.biblLike[bibl biblStruct listBibl msDesc] model.egLike model.labelLike[desc] model.listLike[list listObject] model.oddDecl model.stageLike

2.30. model.lLike

model.lLike groups elements representing metrical components such as verse lines.
Module tei
Used by
Members l

2.31. model.labelLike

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

2.32. 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
Used by
Members model.emphLike[distinct term title] model.hiLike[hi] model.pPart.data[model.addressLike model.dateLike[date] model.measureLike[depth height num width] model.nameLike[model.nameLike.agent[name persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[country placeName settlement]] idno objectName rs]] model.pPart.editorial[abbr expan] model.pPart.msdesc[dimensions locus] model.phrase.xml model.ptrLike[ptr ref]

2.33. model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Module tei
Used by
Members list listObject

2.34. model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.6.3. Numbers and Measures]
Module tei
Used by
Members depth height num width

2.35. model.milestoneLike

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

2.36. model.msItemPart

model.msItemPart groups elements which can appear within a manuscript item description.
Module tei
Used by
Members model.biblLike[bibl biblStruct listBibl msDesc] model.msQuoteLike[title] model.quoteLike model.respLike[author respStmt] idno msItem textLang

2.37. model.msQuoteLike

model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
Module tei
Used by
Members title

2.38. model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Module tei
Used by
Members model.nameLike.agent[name persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[country placeName settlement]] idno objectName rs
Note

A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

2.39. model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Module tei
Used by
Members name persName
Note

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

2.40. model.noteLike

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

2.41. model.objectLike

model.objectLike groups elements which describe objects.
Module tei
Used by
Members listObject object

2.43. model.pLike.front

model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]
Module tei
Used by
Members head

2.44. model.pPart.data

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

2.45. model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]
Module tei
Used by
Members model.pPart.editorial[abbr expan] model.pPart.transcriptional[orig reg supplied surplus]

2.46. model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes]
Module tei
Used by
Members abbr expan

2.47. model.pPart.msdesc

model.pPart.msdesc groups phrase-level elements used in manuscript description. [10. Manuscript Description]
Module tei
Used by
Members dimensions locus

2.48. model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]
Module tei
Used by
Members orig reg supplied surplus

2.50. 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
Used by
Members model.graphicLike[media] model.highlighted[model.emphLike[distinct term title] model.hiLike[hi]] model.lPart model.pPart.data[model.addressLike model.dateLike[date] model.measureLike[depth height num width] model.nameLike[model.nameLike.agent[name persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[country placeName settlement]] idno objectName rs]] model.pPart.edit[model.pPart.editorial[abbr expan] model.pPart.transcriptional[orig reg supplied surplus]] model.pPart.msdesc[dimensions locus] model.phrase.xml model.ptrLike[ptr ref] model.segLike[seg] model.specDescLike
Note

This class of elements can occur within paragraphs, list items, lines of verse, etc.

2.51. model.physDescPart

model.physDescPart groups specialized elements forming part of the physical description of a manuscript or similar written source.
Module msdescription
Used by
Members handDesc objectDesc

2.52. model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [13.2.3. Place Names]
Module tei
Used by
Members country placeName settlement

2.53. model.placeStateLike

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

2.54. model.profileDescPart

model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.
Module tei
Used by
Members correspDesc textClass

2.55. model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
Module tei
Used by
Members ptr ref

2.56. model.publicationStmtPart.agency

model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
Module tei
Used by
Members publisher
Note

The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element.

See also model.publicationStmtPart.detail.

2.57. model.publicationStmtPart.detail

model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]
Module tei
Used by
Members model.ptrLike[ptr ref] availability date idno pubPlace
Note

A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.

See also model.publicationStmtPart.agency.

2.58. model.recordingPart

model.recordingPart groups elements used to describe details of an audio or video recording. [8.2. Documenting the Source of Transcribed Speech]
Module spoken
Used by
Members model.dateLike[date] media respStmt

2.59. model.resource

model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]
Module tei
Used by
Members text

2.60. model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Module tei
Used by
Members author respStmt

2.61. model.segLike

model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories]
Module tei
Used by
Members seg
Note

The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header.

2.62. model.sourceDescPart

model.sourceDescPart groups elements which may be used inside <sourceDesc> and appear multiple times.
Module tei
Used by
Members recordingStmt

2.63. model.teiHeaderPart

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

3. Attribute classes

3.1. att.canonical

att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]
Module tei
Members att.naming[att.personal[name objectName persName placeName] author country pubPlace repository rs settlement] correspDesc date object publisher resp respStmt term title
Attributes
key provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Status Optional
Datatype teidata.text
<author>  <name key="name 427308"   type="organisation">[New Zealand Parliament, Legislative Council]</name> </author>
<author>  <name key="Hugo, Victor (1802-1885)"   ref="http://www.idref.fr/026927608">Victor Hugo</name> </author>
Note

The value may be a unique identifier from a database, or any other externally-defined string identifying the referent.

No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project. For the same reason, this attribute is not recommended in data interchange, since there is no way of ensuring that the values used by one project are distinct from those used by another. In such a situation, a preferable approach for magic tokens which follows standard practice on the Web is to use a ref attribute whose value is a tag URI as defined in RFC 4151.

ref (reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<name ref="http://viaf.org/viaf/109557338"  type="person">Seamus Heaney</name>
Note

The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

3.2. att.datable.custom

att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.4. Dates]
Module namesdates
Members att.datable[author change country date idno licence name objectName persName placeName provenance resp settlement title]
Attributes
when-custom supplies the value of a date or time in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system
<p>Alhazen died in Cairo on the <date when="1040-03-06"   when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH  </date>.</p> <p>The current world will end at the <date when="2012-12-21"   when-custom="13.0.0.0.0">end of B'ak'tun 13</date>.</p> <p>The Battle of Meggidu (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p> <p>Esidorus bixit in pace annos LXX plus minus sub <date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date> </p>
Not all custom date formulations will have Gregorian equivalents.The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
notBefore-custom specifies the earliest possible date for the event in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
notAfter-custom specifies the latest possible date for the event in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
from-custom indicates the starting point of the period in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
<event datingMethod="#julian"  from-custom="1666-09-02"  to-custom="1666-09-05"  xml:id="FIRE1">  <head>The Great Fire of London</head>  <p>The Great Fire of London burned through a large part    of the city of London.</p> </event>
to-custom indicates the ending point of the period in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
datingPoint supplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
Status Optional
Datatype teidata.pointer
datingMethod supplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
Status Optional
Datatype teidata.pointer
Contayning the Originall, Antiquity, Increaſe, Moderne eſtate, and deſcription of that Citie, written in the yeare <date calendar="#julian"  datingMethod="#julian"  when-custom="1598">1598</date>. by Iohn Stow Citizen of London.
In this example, the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the <date> element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.
<date datingMethod="#creationOfWorld"  when="1382-06-28"  when-custom="6890-06-20"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num> </date>
In this example, a date is given in a Mediaeval text measured ‘from the creation of the world’, which is normalized (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.
Note

Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the original date in the element.

3.3. att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 13.4. Dates]
Module namesdates
Members att.datable[author change country date idno licence name objectName persName placeName provenance resp settlement title]
Attributes
when-iso supplies the value of a date or time in a standard form.
Status Optional
Datatype teidata.temporal.iso
The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.
<date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date> <date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date> <time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time> <time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time> <date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date> <time when-iso="03:00">3 A.M.</time> <time when-iso="14">around two</time> <time when-iso="15,5">half past three</time>
All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.
He likes to be punctual. I said <q>  <time when-iso="12">around noon</time> </q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.
The second occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.
notBefore-iso specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso
notAfter-iso specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso
from-iso indicates the starting point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
to-iso indicates the ending point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601:2004, using the Gregorian calendar.

If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date dur-iso="P8Dwhen-iso="2007-06-01"/>
indicates the same time period as
<date when-iso="2007-06-01/P8D"/>

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

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.6.4. Dates and Times 13.4. Dates]
Module tei
Members att.datable[author change country date idno licence name objectName persName placeName provenance resp settlement title]
Attributes
when supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
Examples of W3C date, time, and date & time formats.
<p>  <date when="1945-10-24">24 Oct 45</date>  <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>  <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>  <time when="14:12:38">fourteen twelve and 38 seconds</time>  <date when="1962-10">October of 1962</date>  <date when="--06-12">June 12th</date>  <date when="---01">the first of the month</date>  <date when="--08">August</date>  <date when="2006">MMVI</date>  <date when="0056">AD 56</date>  <date when="-0056">56 BC</date> </p>
This list begins in the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after Pentecost, in that year the <date calendar="#julian"  when="1632-06-06">27th of May (old style)</date>.
<opener>  <dateline>   <placeName>Dorchester, Village,</placeName>   <date when="1828-03-02">March 2d. 1828.</date>  </dateline>  <salute>To    Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time> </opener>
notBefore specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
notAfter specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
from indicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
to indicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
Schematron
<sch:rule context="tei:*[@when]"> <sch:report role="nonfatal"  test="@notBefore|@notAfter|@from|@to">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@from]"> <sch:report role="nonfatal"  test="@notBefore">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@to]"> <sch:report role="nonfatal"  test="@notAfter">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule>
Example
<date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

3.5. att.datcat

att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [9.5.2. Lexical View 18.3. Other Atomic Feature Values]
Module tei
Members att.segLike[seg]
Attributes
datcat provides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcat provides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcat provides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Example The example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.
<fs>  <f datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"   name="POS">   <symbol value="NN"    valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>  </f> <!-- ... --> </fs>
‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545 is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [[undefined FS]].
<fs>  <f fVal="#commonNounname="POS"/> <!-- ... --> </fs>
The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories.
<fvLib n="POS values">  <symbol datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"   value="NNxml:id="commonNoun"/>  <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"   value="NPxml:id="properNoun"/> <!-- ... --> </fvLib>
Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.
Example In the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above.
<gramGrp>  <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"   valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos> </gramGrp>
Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>:
<tagsDecl partial="true"> <!-- ... -->  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="pos"    targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage>   <tagUsage gi="case"    targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage> <!-- ... -->  </namespace> </tagsDecl>
Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below:
<listPrefixDef>  <prefixDef ident="ccrmatchPattern="pos"   replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <prefixDef ident="ccrmatchPattern="adj"   replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/> </listPrefixDef> <!-- ... --> <entry> <!--...-->  <form>   <orth>isotope</orth>  </form>  <gramGrp>   <pos datcat="ccr:pos"    valueDatcat="ccr:adj">adj</pos>  </gramGrp> <!--...--> </entry>
This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in <equiv> element that is a child of <elementSpec> or <attDef>.
Example The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.
<fDecl name="POS"  targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">  <fDescr>part of speech (morphosyntactic category)</fDescr>  <vRange>   <vAlt>    <symbol datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"     value="NN"/>    <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"     value="NP"/> <!-- ... -->   </vAlt>  </vRange> </fDecl>
Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.
Note

The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container.

A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute.

In a TEI XML example of two equivalent serializations expressing the name-value pair <part-of-speech,common-noun>, namely <pos>commonNoun</pos> and pos="common-noun", one would classify the element <pos> and the attribute pos as containers (mapping onto the first member of the relevant name-value pair), while the character data content of <pos> or the value of pos would be seen as mapping onto the second member of the pair.

The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech).

The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects.

Historically, datcat and valueDatcat originate from the (the now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example.

Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices.

3.6. att.declaring

att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [15.3. Associating Contextual Information with a Text]
Module tei
Members back body div front lg media msDesc object p ptr ref term text
Attributes
decls (declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text.

3.7. att.duration

att.duration provides attributes for normalization of elements that contain datable events.
Module spoken
Members att.timed[media] date recording
Attributes att.duration.w3c (@dur) att.duration.iso (@dur-iso)
Note

This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.duration.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.duration.iso class. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes is rarely needed, and there exists much greater software support for the W3C datatypes.

3.8. att.duration.iso

att.duration.iso provides attributes for recording normalized temporal durations. [3.6.4. Dates and Times 13.4. Dates]
Module tei
Members att.duration[att.timed[media] date recording]
Attributes
dur-iso (duration) indicates the length of this element in time.
Status Optional
Datatype teidata.duration.iso
Note

If both when and dur or dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. In order to represent a time range by a duration and its ending time the when-iso attribute must be used.

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

3.9. att.duration.w3c

att.duration.w3c provides attributes for recording normalized temporal durations. [3.6.4. Dates and Times 13.4. Dates]
Module tei
Members att.duration[att.timed[media] date recording]
Attributes
dur (duration) indicates the length of this element in time.
Status Optional
Datatype teidata.duration.w3c
Note

If both when and dur are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. In order to represent a time range by a duration and its ending time the when-iso attribute must be used.

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

3.10. att.fragmentable

att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
Module tei
Members att.divLike[div lg] att.segLike[seg] l p
Attributes
part specifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
Status Optional
Datatype teidata.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) the element is not fragmented, or no claim is made as to its completeness[Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

The values I, M, or F should be used only where it is clear how the element may be reconstituted.

3.11. att.global.analytic

att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.2. Global Attributes for Simple Analyses 17.3. Spans and Interpretations]
Module analysis
Members att.global[TEI abbr additional analytic anchor author availability back bibl biblScope biblStruct body change closer correspAction correspDesc country date depth desc dimensions distinct div encodingDesc expan extent fileDesc front g handDesc head height hi history idno imprint interp interpGrp item keywords l lb lem lg licence list listBibl listObject locus media metDecl monogr msContents msDesc msIdentifier msItem name note num object objectDesc objectIdentifier objectName opener orig p pb persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher recordingStmt ref reg repository resp respStmt revisionDesc rs seg settlement sourceDesc space supplied support supportDesc surplus teiHeader term text textClass textLang title titleStmt width]
Attributes
ana (analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

When multiple values are given, they may reflect either multiple divergent interpretations of an ambiguous text, or multiple mutually consistent interpretations of the same passage in different contexts.

3.12. att.global.change

att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
Module transcr
Members att.global[TEI abbr additional analytic anchor author availability back bibl biblScope biblStruct body change closer correspAction correspDesc country date depth desc dimensions distinct div encodingDesc expan extent fileDesc front g handDesc head height hi history idno imprint interp interpGrp item keywords l lb lem lg licence list listBibl listObject locus media metDecl monogr msContents msDesc msIdentifier msItem name note num object objectDesc objectIdentifier objectName opener orig p pb persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher recordingStmt ref reg repository resp respStmt revisionDesc rs seg settlement sourceDesc space supplied support supportDesc surplus teiHeader term text textClass textLang title titleStmt width]
Attributes
change points to one or more <change> elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

3.13. att.global.facs

att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [11.1. Digital Facsimiles]
Module transcr
Members att.global[TEI abbr additional analytic anchor author availability back bibl biblScope biblStruct body change closer correspAction correspDesc country date depth desc dimensions distinct div encodingDesc expan extent fileDesc front g handDesc head height hi history idno imprint interp interpGrp item keywords l lb lem lg licence list listBibl listObject locus media metDecl monogr msContents msDesc msIdentifier msItem name note num object objectDesc objectIdentifier objectName opener orig p pb persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher recordingStmt ref reg repository resp respStmt revisionDesc rs seg settlement sourceDesc space supplied support supportDesc surplus teiHeader term text textClass textLang title titleStmt width]
Attributes
facs (facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

3.14. att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [16. Linking, Segmentation, and Alignment]
Module linking
Members att.global[TEI abbr additional analytic anchor author availability back bibl biblScope biblStruct body change closer correspAction correspDesc country date depth desc dimensions distinct div encodingDesc expan extent fileDesc front g handDesc head height hi history idno imprint interp interpGrp item keywords l lb lem lg licence list listBibl listObject locus media metDecl monogr msContents msDesc msIdentifier msItem name note num object objectDesc objectIdentifier objectName opener orig p pb persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher recordingStmt ref reg repository resp respStmt revisionDesc rs seg settlement sourceDesc space supplied support supportDesc surplus teiHeader term text textClass textLang title titleStmt width]
Attributes
corresp (corresponds) points to elements that correspond to the current element in some way.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<group>  <text xml:id="t1-g1-t1"   xml:lang="mi">   <body xml:id="t1-g1-t1-body1">    <div type="chapter">     <head>He Whakamaramatanga mo te Ture Hoko, Riihi hoki, i nga Whenua Maori, 1876.</head>     <p></p>    </div>   </body>  </text>  <text xml:id="t1-g1-t2"   xml:lang="en">   <body corresp="#t1-g1-t1-body1"    xml:id="t1-g1-t2-body1">    <div type="chapter">     <head>An Act to regulate the Sale, Letting, and Disposal of Native Lands, 1876.</head>     <p></p>    </div>   </body>  </text> </group>
In this example a <group> contains two <text>s, each containing the same document in a different language. The correspondence is indicated using corresp. The language is indicated using xml:lang, whose value is inherited; both the tag with the corresp and the tag pointed to by the corresp inherit the value from their immediate parent.
<!-- In a placeography called "places.xml" --><place corresp="people.xml#LOND2 people.xml#GENI1"  xml:id="LOND1">  <placeName>London</placeName>  <desc>The city of London...</desc> </place> <!-- In a literary personography called "people.xml" --> <person corresp="places.xml#LOND1 #GENI1"  xml:id="LOND2">  <persName type="lit">London</persName>  <note>   <p>Allegorical character representing the city of <placeName ref="places.xml#LOND1">London</placeName>.</p>  </note> </person> <person corresp="places.xml#LOND1 #LOND2"  xml:id="GENI1">  <persName type="lit">London’s Genius</persName>  <note>   <p>Personification of London’s genius. Appears as an      allegorical character in mayoral shows.   </p>  </note> </person>
In this example, a <place> element containing information about the city of London is linked with two <person> elements in a literary personography. This correspondence represents a slightly looser relationship than the one in the preceding example; there is no sense in which an allegorical character could be substituted for the physical city, or vice versa, but there is obviously a correspondence between them.
synch (synchronous) points to elements that are synchronous with the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
sameAs points to an element that is the same as the current element.
Status Optional
Datatype teidata.pointer
copyOf points to an element of which the current element is a copy.
Status Optional
Datatype teidata.pointer
Note

Any content of the current element should be ignored. Its true content is that of the element being pointed at.

next points to the next element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

prev (previous) points to the previous element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.

exclude points to elements that are in exclusive alternation with the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
select selects one or more alternants; if one alternant is selected, the ambiguity or uncertainty is marked as resolved. If more than one alternant is selected, the degree of ambiguity or uncertainty is marked as reduced by the number of alternants not selected.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute should be placed on an element which is superordinate to all of the alternants from which the selection is being made.

3.15. att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Module tei
Members att.global[TEI abbr additional analytic anchor author availability back bibl biblScope biblStruct body change closer correspAction correspDesc country date depth desc dimensions distinct div encodingDesc expan extent fileDesc front g handDesc head height hi history idno imprint interp interpGrp item keywords l lb lem lg licence list listBibl listObject locus media metDecl monogr msContents msDesc msIdentifier msItem name note num object objectDesc objectIdentifier objectName opener orig p pb persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher recordingStmt ref reg repository resp respStmt revisionDesc rs seg settlement sourceDesc space supplied support supportDesc surplus teiHeader term text textClass textLang title titleStmt width]
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
<head rend="align(center) case(allcaps)">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rend="case(mixed)">New Blazing-World</hi>. </head>
Note

These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

style contains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
Status Optional
Datatype teidata.text
<head style="text-align: center; font-variant: small-caps">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi style="font-variant: normal">New Blazing-World</hi>. </head>
Note

Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

rendition points to a description of the rendering or presentation used for this element in the source text.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<head rendition="#ac #sc">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rendition="#normal">New Blazing-World</hi>. </head> <!-- elsewhere... --> <rendition scheme="css"  xml:id="sc">font-variant: small-caps</rendition> <rendition scheme="css"  xml:id="normal">font-variant: normal</rendition> <rendition scheme="css"  xml:id="ac">text-align: center</rendition>
Note

The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

3.16. att.global.responsibility

att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]
Module tei
Members att.global[TEI abbr additional analytic anchor author availability back bibl biblScope biblStruct body change closer correspAction correspDesc country date depth desc dimensions distinct div encodingDesc expan extent fileDesc front g handDesc head height hi history idno imprint interp interpGrp item keywords l lb lem lg licence list listBibl listObject locus media metDecl monogr msContents msDesc msIdentifier msItem name note num object objectDesc objectIdentifier objectName opener orig p pb persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher recordingStmt ref reg repository resp respStmt revisionDesc rs seg settlement sourceDesc space supplied support supportDesc surplus teiHeader term text textClass textLang title titleStmt width]
Attributes
cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
Status Optional
Datatype teidata.probCert
resp (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple <respStmt>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).

Example
Blessed are the <choice>  <sic>cheesemakers</sic>  <corr cert="highresp="#editor">peacemakers</corr> </choice>: for they shall be called the children of God.
Example
<!-- in the <text> ... --><lg> <!-- ... -->  <l>Punkes, Panders, baſe extortionizing    sla<choice>    <sic>n</sic>    <corr resp="#JENS1_transcriber">u</corr>   </choice>es,</l> <!-- ... --> </lg> <!-- in the <teiHeader> ... --> <!-- ... --> <respStmt xml:id="JENS1_transcriber">  <resp when="2014">Transcriber</resp>  <name>Janelle Jenstad</name> </respStmt>

3.17. att.global.source

att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Module tei
Members att.global[TEI abbr additional analytic anchor author availability back bibl biblScope biblStruct body change closer correspAction correspDesc country date depth desc dimensions distinct div encodingDesc expan extent fileDesc front g handDesc head height hi history idno imprint interp interpGrp item keywords l lb lem lg licence list listBibl listObject locus media metDecl monogr msContents msDesc msIdentifier msItem name note num object objectDesc objectIdentifier objectName opener orig p pb persName physDesc placeName profileDesc projectDesc provenance ptr pubPlace publicationStmt publisher recordingStmt ref reg repository resp respStmt revisionDesc rs seg settlement sourceDesc space supplied support supportDesc surplus teiHeader term text textClass textLang title titleStmt width]
Attributes
source specifies the source from which some aspect of this element is drawn.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@source]"> <sch:let name="srcs"  value="tokenize( normalize-space(@source),' ')"/> <sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like <sch:value-of select="name(.)"/>), the @source attribute should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.) </sch:report> </sch:rule>
Note

The source attribute points to an external source. When used on an element describing a schema component (<classRef>, <dataRef>, <elementRef>, <macroRef>, <moduleRef>, or <schemaSpec>), it identifies the source from which declarations for the components should be obtained.

On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, a private scheme URI of the form tei:x.y.z, where x.y.z indicates the version number, e.g. tei:4.3.2 for TEI P5 release 4.3.2 or (as a special case) tei:current for whatever is the latest release, or a private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.

When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.

Example
<p> <!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested    term.</quote> <!-- ... --> </p>
Example
<p> <!-- ... -->  <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the    less we seem to know.</quote> <!-- ... --> </p> <!-- ... --> <bibl xml:id="chicago_15_ed">  <title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of    Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl>
Example
<elementRef key="psource="tei:2.0.1"/>
Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
Example
<schemaSpec ident="myODD"  source="mycompiledODD.xml"> <!-- further declarations specifying the components required --> </schemaSpec>
Create a schema using components taken from the file mycompiledODD.xml.

3.18. att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Module tei
Members att.media[media] ptr ref
Attributes
mimeType (MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Example In this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.
<ref mimeType="application/tei+xml; charset=UTF-8"  target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
Note

This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.

3.19. att.metrical

att.metrical defines a set of attributes that certain elements may use to represent metrical information. [6.4. Rhyme and Metrical Analysis]
Module verse
Members att.divLike[div lg] att.segLike[seg] l
Attributes
met (metrical structure, conventional) contains a user-specified encoding for the conventional metrical structure of the element.
Status Recommended
Datatype token
Note

The pattern may be specified by means of either a standard term for the kind of metrical unit (e.g. hexameter) or an encoded representation for the metrical pattern (e.g. +--+-+-+-+-). In either case, the notation used should be documented by a <metDecl> element within the <encodingDesc> of the associated header.

Where this attribute is not specified, the metrical pattern for the element concerned is understood to be inherited from its parent.

real (metrical structure, realized) contains a user-specified encoding for the actual realization of the conventional metrical structure applicable to the element.
Status Optional
Datatype token
Note

The pattern may be specified by means of either a standard term for the kind of metrical unit (e.g. hexameter) or an encoded representation for the metrical pattern (e.g. +--+-+-+-+-). In either case, the notation used should be documented by a <metDecl> element within the <encodingDesc> of the associated header.

Where this attribute is not specified, the metrical realization for the element concerned is understood to be identical to that specified or implied for the met attribute.

rhyme (rhyme scheme) specifies the rhyme scheme applicable to a group of verse lines.
Status Recommended
Datatype token
Note

By default, the rhyme scheme is expressed as a string of alphabetic characters each corresponding with a rhyming line. Any non-rhyming lines should be represented by a hyphen or an X. Alternative notations may be defined as for met by use of the <metDecl> element in the TEI header.

When the default notation is used, it does not make sense to specify this attribute on any unit smaller than a line. Nor does the default notation provide any way to record internal rhyme, or to specify non-conventional rhyming practice. These extensions would require user-defined alternative notations.

3.20. att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 13.3.6. Names and Nyms]
Module tei
Members att.personal[name objectName persName placeName] author country pubPlace repository rs settlement
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 teidata.enumerated separated by whitespace
nymRef (reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

3.21. att.ranging

att.ranging provides attributes for describing numerical ranges.
Module tei
Members att.dimensions[date depth dimensions height space supplied surplus width] num
Attributes
atLeast gives a minimum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
atMost gives a maximum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
min where the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Status Optional
Datatype teidata.numeric
max where the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Status Optional
Datatype teidata.numeric
confidence specifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
Status Optional
Datatype teidata.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike">  <gap atLeast="1atMost="2"   extent="one or two lettersreason="illegibleunit="chars"/> </del> Philadelphia to the Graphic office, New York.
Example
Americares has been supporting the health sector in Eastern Europe since 1986, and since 1992 has provided <measure atLeast="120000000"  commodity="currencyunit="USD">more than $120m</measure> in aid to Ukrainians.

3.22. att.written

att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
Module tei
Members att.textCritical[lem] closer div head hi note opener p seg text
Attributes
hand points to a <handNote> element describing the hand considered responsible for the content of the element concerned.
Status Optional
Datatype teidata.pointer

4. Macros

4.1. macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]
Module tei
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
 </alternate>
</content>
    
Declaration
tei_macro.limitedContent =
   ( text | tei_model.limitedPhrase | tei_model.inter )*

4.2. macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Module tei
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.paraPart"/>
 </alternate>
</content>
    
Declaration
tei_macro.paraContent = ( text | tei_model.paraPart )*

4.3. macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Module tei
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.phraseSeq =
   (
      text
    | tei_model.gLike
    | tei_model.attributable
    | tei_model.phrase
    | tei_model.global
   )*

4.4. macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]
Module tei
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.phraseSeq.limited =
   ( text | tei_model.limitedPhrase | tei_model.global )*

4.5. macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
Module tei
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.specialPara =
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.divPart
    | tei_model.global
   )*

4.6. macro.xtext

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

5. Datatypes

5.1. teidata.certainty

teidata.certainty defines the range of attribute values expressing a degree of certainty.
Module tei
Used by
Content model
<content>
 <valList type="closed">
  <valItem ident="high"/>
  <valItem ident="medium"/>
  <valItem ident="low"/>
  <valItem ident="unknown"/>
 </valList>
</content>
    
Declaration
tei_teidata.certainty = "high" | "medium" | "low" | "unknown"
Note

Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter.

5.2. teidata.count

teidata.count defines the range of attribute values used for a non-negative integer value used as a count.
Module tei
Used by
Content model
<content>
 <dataRef name="nonNegativeInteger"/>
</content>
    
Declaration
tei_teidata.count = xsd:nonNegativeInteger
Note

Any positive integer value or zero is permitted

5.3. teidata.duration.iso

teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
Module tei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</content>
    
Declaration
tei_teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Example
<time dur-iso="PT0,75H">three-quarters of an hour</time>
Example
<date dur-iso="P1,5D">a day and a half</date>
Example
<date dur-iso="P14D">a fortnight</date>
Example
<time dur-iso="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.

5.4. teidata.duration.w3c

teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Module tei
Used by
Content model
<content>
 <dataRef name="duration"/>
</content>
    
Declaration
tei_teidata.duration.w3c = xsd:duration
Example
<time dur="PT45M">forty-five minutes</time>
Example
<date dur="P1DT12H">a day and a half</date>
Example
<date dur="P7D">a week</date>
Example
<time dur="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see the W3C specification.

5.5. teidata.enumerated

teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Module tei
Used by
Element:
Content model
<content>
 <dataRef key="teidata.word"/>
</content>
    
Declaration
tei_teidata.enumerated = teidata.word
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.

5.6. teidata.language

teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]
Module tei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="language"/>
  <valList>
   <valItem ident=""/>
  </valList>
 </alternate>
</content>
    
Declaration
tei_teidata.language = xsd:language | ( "" )
Note

The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.

A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.

language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at http://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at http://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
private use
An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.

Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.

Examples include

sn
Shona
zh-TW
Taiwanese
zh-Hant-HK
Chinese written in traditional script as used in Hong Kong
en-SL
English as spoken in Sierra Leone
pl
Polish
es-MX
Spanish as spoken in Mexico
es-419
Spanish as spoken in Latin America

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

5.7. teidata.name

teidata.name defines the range of attribute values expressed as an XML Name.
Module tei
Used by
Content model
<content>
 <dataRef name="Name"/>
</content>
    
Declaration
tei_teidata.name = xsd:Name
Note

Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

5.8. teidata.numeric

teidata.numeric defines the range of attribute values used for numeric values.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef name="double"/>
  <dataRef name="token"
   restriction="(\-?[\d]+/\-?[\d]+)"/>
  <dataRef name="decimal"/>
 </alternate>
</content>
    
Declaration
tei_teidata.numeric =
   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
Note

Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.

A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

5.9. teidata.outputMeasurement

teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Module tei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"/>
</content>
    
Declaration
tei_teidata.outputMeasurement =
   token
   {
      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"
   }
Example
<figure>  <head>The TEI Logo</head>  <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in    between and <mentioned>text encoding initiative</mentioned> underneath, all on a white    background.</figDesc>  <graphic height="600px"   url="http://www.tei-c.org/logos/TEI-600.jpgwidth="600px"/> </figure>
Note

These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

5.10. teidata.pattern

teidata.pattern defines attribute values which are expressed as a regular expression.
Module tei
Used by
Content model
<content>
 <dataRef name="token"/>
</content>
    
Declaration
tei_teidata.pattern = token
Note
A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)
Wikipedia

This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema.

5.11. teidata.point

teidata.point defines the data type used to express a point in cartesian space.
Module tei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
    
Declaration
tei_teidata.point =
   token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }
Example
<facsimile>  <surface lrx="400lry="280ulx="0uly="0">   <zone points="220,100 300,210 170,250 123,234">    <graphic url="handwriting.png"/>   </zone>  </surface> </facsimile>
Note

A point is defined by two numeric values, which should be expressed as decimal numbers. Neither number can end in a decimal point. E.g., both 0.0,84.2 and 0,84 are allowed, but 0.,84. is not.

5.12. teidata.pointer

teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
Module tei
Used by
Element:
Content model
<content>
 <dataRef name="anyURI" restriction="\S+"/>
</content>
    
Declaration
tei_teidata.pointer = xsd:anyURI { pattern = "\S+" }
Note

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

5.13. teidata.probCert

teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef key="teidata.probability"/>
  <dataRef key="teidata.certainty"/>
 </alternate>
</content>
    
Declaration
tei_teidata.probCert = teidata.probability | teidata.certainty

5.14. teidata.probability

teidata.probability defines the range of attribute values expressing a probability.
Module tei
Used by
Content model
<content>
 <dataRef name="double"/>
</content>
    
Declaration
tei_teidata.probability = xsd:double
Note

Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

5.15. teidata.replacement

teidata.replacement defines attribute values which contain a replacement template.
Module tei
Used by
Content model
<content>
 <textNode/>
</content>
    
Declaration
tei_teidata.replacement = text

5.16. teidata.temporal.iso

teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
  <dataRef name="token"
   restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
 </alternate>
</content>
    
Declaration
tei_teidata.temporal.iso =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
 | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

For all representations for which ISO 8601:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format.

5.17. teidata.temporal.w3c

teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.
Module tei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
 </alternate>
</content>
    
Declaration
tei_teidata.temporal.w3c =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

5.18. teidata.text

teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.
Module tei
Used by
Element:
Content model
<content>
 <dataRef name="string"/>
</content>
    
Declaration
tei_teidata.text = string
Note

Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

5.19. teidata.truthValue

teidata.truthValue defines the range of attribute values used to express a truth value.
Module tei
Used by
Content model
<content>
 <dataRef name="boolean"/>
</content>
    
Declaration
tei_teidata.truthValue = xsd:boolean
Note

The possible values of this datatype are 1 or true, or 0 or false.

This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue.

5.20. teidata.version

teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Module tei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
    
Declaration
tei_teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
Note

The value of this attribute follows the pattern specified by the Unicode consortium for its version number (http://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

5.21. teidata.versionNumber

teidata.versionNumber defines the range of attribute values used for version numbers.
Module tei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>
</content>
    
Declaration
tei_teidata.versionNumber =
   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }

5.22. teidata.word

teidata.word defines the range of attribute values expressed as a single word or token.
Module tei
Used by
teidata.enumeratedElement:
Content model
<content>
 <dataRef name="token"
  restriction="[^\p{C}\p{Z}]+"/>
</content>
    
Declaration
tei_teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

5.23. teidata.xTruthValue

teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Module tei
Used by
Content model
<content>
 <alternate>
  <dataRef name="boolean"/>
  <valList>
   <valItem ident="unknown"/>
   <valItem ident="inapplicable"/>
  </valList>
 </alternate>
</content>
    
Declaration
tei_teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )
Note

In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

5.24. teidata.xmlName

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

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

5.25. teidata.xpath

teidata.xpath defines attribute values which contain an XPath expression.
Module tei
Used by
Content model
<content>
 <textNode/>
</content>
    
Declaration
tei_teidata.xpath = text
Note

Any XPath expression using the syntax defined in 6.2..

When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP.

Jennifer Bunselmeier. Date: 2023-03-24