Astronautilia

Table of contents

Astronautilia 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 16.1. Varieties of Composite Text]
Moduletextstructure
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
rendition(rendition reference) points to a description of the rendering or presentation used for this element in the source text.
Derived fromatt.global.rendition
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Sample values include
astronautilia_transcript
Dokumenttyp: Transkriptionsdatei
astronautilia_resources
Dokumenttyp: Ressourcendatei (Register oder sonstige Projektressource)
astronautilia_about
Dokumenttyp: Projekteinführungsdatei
astronautilia_commonMetadata
Dokumenttyp: Metadatendatei
versionspecifies the version number of the TEI Guidelines against which this document is valid.
StatusRequired
Datatypeteidata.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
linking: standOff
textstructure: TEI text
Note

As with all elements in the TEI scheme (except <egXML>) this element is in the TEI namespace (see 5.7.2. Namespaces). Thus, when it is used as the outermost element of a TEI document, it is necessary to specify the TEI namespace on it. This is customarily achieved by including http://www.tei-c.org/ns/1.0 as the value of the XML namespace declaration (xmlns), without indicating a prefix, and then not using a prefix on TEI elements in the rest of the document. For example: <TEI version="4.8.1" 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>
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. <ab>

<ab> (anonymous block) contains any component-level unit of text, acting as a container for phrase or inter level elements analogous to, but without the same constraints as, a paragraph. [17.3. Blocks, Segments, and Anchors]
Modulelinking
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusOptional
Datatype1–∞ 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
May contain
Note

The <ab> element may be used at the encoder's discretion to mark any component-level elements in a text for which no other more specific appropriate markup is defined. Unlike paragraphs, <ab> may nest and may use the type and subtype attributes.

Example
<div n="Genesistype="book">  <div n="1type="chapter">   <ab>In the beginning God created the heaven and the earth.</ab>   <ab>And the earth was without form, and void; and      darkness was upon the face of the deep. And the      spirit of God moved upon the face of the waters.</ab>   <ab>And God said, Let there be light: and there was light.</ab> <!-- ...-->  </div> </div>
Schematron
<sch:rule context="tei:l//tei:ab"> <sch:assert test="ancestor::tei:floatingText | parent::tei:figure | parent::tei:note"> Abstract model violation: Metrical lines (<l> elements) may not contain higher-level divisions such as <p> or <ab>, unless <ab> is a child of <figure> or <note>, or is a descendant of <floatingText>. </sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.abContent"/>
</content>
    
Schema Declaration
element ab
{
   attribute rend { list { ( "center" | "right" )+ } }?,
   tei_macro.abContent
}

1.3. <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Modulecore
Attributes
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusOptional
Datatypeteidata.text
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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_att.cmc.attributes,
   attribute n { text }?,
   tei_macro.phraseSeq
}

1.4. <addrLine>

<addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Member of
Contained by
core: address
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
character data
Note

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

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

1.5. <address>

<address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
typecharacterizes the address in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
billing
the address to which a bill for goods or services should be sent.
delivery
the address to which packages should be sent via a private delivery service.
mailing
the address to which mail should be sent via a public postal service.
military
the address to which mail to deployed military personnel should be sent.
physical
the address of a building irrespective of where mail to its occupants should be sent (for example, for the fire department).
rolespecifies further information about the purpose of the address.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Sample values include:
sender
the address of the sender of a piece of correspondence.
return
the address to which undeliverable mail should be returned.
recipient
the address of the intended recipient of a piece of correspondence.
work
the address to which work-related mail should be sent, typically that of the recipient’s employer.
home
the address to which non-work-related mail should be sent, typically the domicile of the recipient.
start
the address of the beginning of a route, for example of a race.
finish
the address of the end of a route, for example of a race.
pickup
the address at which a person or package is picked up, for example by a taxi or delivery service.
dropOff
the address at which a person or package is dropped off, for example by a taxi or delivery service.
Note

Whereas type is used to differentiate the kind of address (e.g. a street address vs. a post office box, or a physical address vs. a mailing address), role is used to differentiate the purpose of the address, for example within a correspondence ecosystem (e.g. the address of the sender vs. that of the intended recipient, or a college student's permanent address vs. address while at school).

Member of
Contained by
May contain
figures: figure
header: idno
linking: anchor
Note

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

ExampleUsing just the elements defined by the core module, an address could be represented as follows:
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <name>Bologna</name>  <name>Italy</name> </address>
ExampleWhen a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic <name>:
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <settlement>Bologna</settlement>  <country>Italy</country> </address>
Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL 60680</addrLine>  <addrLine>USA</addrLine> </address>
Example
<address>  <country key="FR"/>  <settlement type="city">Lyon</settlement>  <postCode>69002</postCode>  <district type="arrondissement">IIème</district>  <district type="quartier">Perrache</district>  <street>   <num>30</num>, Cours de Verdun</street> </address>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.addrPart"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element address
{
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_att.typed.attribute.subtype,
   attribute type
   {
      "billing" | "delivery" | "mailing" | "military" | "physical"
   }?,
   attribute role { list { + } }?,
   ( tei_model.global*, ( ( tei_model.addrPart, tei_model.global* )+ ) )
}

1.6. <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]
Modulecore
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.7. <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 17.5. Correspondence and Alignment]
Modulelinking
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusRequired
Datatypeteidata.text
corresp(corresponds) points to elements that correspond to the current element in some way.
Derived fromatt.global.linking
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
footnote
Anker für Sachanmerkung
subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
editorial
Editorische Sachanmerkung
Member of
Contained by
May containEmpty 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
{
   tei_att.cmc.attributes,
   attribute xml:id { text },
   attribute n { text },
   attribute corresp { list { + } },
   attribute type { "footnote" },
   attribute subtype { "editorial" }?,
   empty
}

1.8. <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]
Modulecore
Member of
Contained by
header: titleStmt
msdescription: msItem
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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.9. <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.]
Moduleheader
Member of
Contained by
May contain
core: p
header: licence
linking: ab
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>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:availability"/> </sch:pattern>
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.10. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
Contained by
textstructure: text
May contain
figures: figure table
linking: ab anchor
textstructure: closer div
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.11. <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 16.3.2. Declarable Elements]
Modulecore
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
Member of
Contained by
May contain
Note

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

Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
<bibl>  <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher>  <date>1968</date>. </bibl>
Example
<bibl subtype="book_chaptertype="article"  xml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde" value="tei:bibl"/> </sch:pattern>
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
{
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   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.12. <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]
Modulecore
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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.13. <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 16.3.2. Declarable Elements]
Modulecore
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Legal values are:
E
Überlieferungsträger-Sigle: E
Member of
Contained by
May contain
Example
<biblStruct>  <monogr>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <edition>first edition</edition>   <imprint>    <publisher>Yale University Press</publisher>    <pubPlace>New Haven and London</pubPlace>    <date>1990</date>   </imprint>  </monogr> </biblStruct>
Example
<biblStruct type="newspaper">  <analytic>   <author>    <forename>David</forename>    <surname>Barstow</surname>   </author>   <author>    <forename>Susanne</forename>    <surname>Craig</surname>   </author>   <author>    <forename>Russ</forename>    <surname>Buettner</surname>   </author>   <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>   <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>  </analytic>  <monogr>   <title level="j">The New York Times</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>A. G. Sulzberger</publisher>    <date when="2018-10-03">Wednesday, October 3, 2018</date>   </imprint>   <biblScope unit="volume">CLXVIII</biblScope>   <biblScope unit="issue">58,104</biblScope>   <biblScope unit="page">1</biblScope>  </monogr> </biblStruct>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:biblStruct"/> </sch:pattern>
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
{
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   attribute xml:id { "E" },
   (
      tei_analytic*,
      ( ( tei_monogr, series* )+ ),
      ( tei_model.noteLike | tei_model.ptrLike | relatedItem | citedRange )*
   )
}

1.14. <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure
Contained by
textstructure: text
May contain
dictionaries: entry
figures: figure table
linking: ab anchor
msdescription: msDesc
textstructure: closer div opener
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.15. <catDesc>

<catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration]
Moduleheader
Contained by
header: category
May contain
header: idno
msdescription: locus
character data
Example
<catDesc>Prose reportage</catDesc>
Example
<catDesc>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose degree="hightype="entertain"/>   <purpose degree="mediumtype="inform"/>  </textDesc> </catDesc>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.catDescPart"/>
 </alternate>
</content>
    
Schema Declaration
element catDesc { ( text | tei_model.limitedPhrase | tei_model.catDescPart )* }

1.16. <category>

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Legal values are:
spondaicGrc
Metrische Notation: Spondeischer Vers (im Griechischen)
spondaicLat
Metrische Notation: Spondeischer Vers (im Lateinischen)
versusTetracoli4Grc
Metrische Notation: Versus tetracoli (im Griechischen) [4 Wörter]
versusTetracoli5Grc
Metrische Notation: Versus tetracoli (im Griechischen) [5 Wörter; enthält Kurzwort τ’/δ’/θ’]
versusTetracoliLat
Metrische Notation: Versus tetracoli (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)
na
Metrische Notation: Zäsur kann oder wird nicht ausgezeichnet
MZ
Metrische Notation: Mittelzäsur (MZ)
monosyllabumGrc
Metrische Notation: Einsilber (im Griechischen)
monosyllabumLat
Metrische Notation: Einsilber (im Lateinischen)
hex
Metrische Notation: Hexameter
prose
Metrische Notation: Prosa
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusRequired
Datatypeteidata.text
Legal values are:
hexameter_type
Metrische Notation: Hexametertyp
caesura
Metrische Notation: Zäsur
syllable_length
Metrische Notation: Silbenlänge
verse_structure
Metrische Notation: Versstruktur
Contained by
May contain
core: desc
Example
<category xml:id="b1">  <catDesc>Prose reportage</catDesc> </category>
Example
<category xml:id="b2">  <catDesc>Prose </catDesc>  <category xml:id="b11">   <catDesc>journalism</catDesc>  </category>  <category xml:id="b12">   <catDesc>fiction</catDesc>  </category> </category>
Example
<category xml:id="LIT">  <catDesc xml:lang="pl">literatura piękna</catDesc>  <catDesc xml:lang="en">fiction</catDesc>  <category xml:id="LPROSE">   <catDesc xml:lang="pl">proza</catDesc>   <catDesc xml:lang="en">prose</catDesc>  </category>  <category xml:id="LPOETRY">   <catDesc xml:lang="pl">poezja</catDesc>   <catDesc xml:lang="en">poetry</catDesc>  </category>  <category xml:id="LDRAMA">   <catDesc xml:lang="pl">dramat</catDesc>   <catDesc xml:lang="en">drama</catDesc>  </category> </category>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="1" minOccurs="1">
   <elementRef key="catDesc"
    maxOccurs="unbounded" minOccurs="1"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.descLike"/>
    <elementRef key="equiv"/>
    <elementRef key="gloss"/>
   </alternate>
  </alternate>
  <elementRef key="category"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element category
{
   attribute xml:id
   {
      "spondaicGrc"
    | "spondaicLat"
    | "versusTetracoli4Grc"
    | "versusTetracoli5Grc"
    | "versusTetracoliLat"
    | "TH"
    | "PH"
    | "HH"
    | "BD"
    | "KTT"
    | "na"
    | "MZ"
    | "monosyllabumGrc"
    | "monosyllabumLat"
    | "hex"
    | "prose"
   },
   attribute n
   {
      "hexameter_type" | "caesura" | "syllable_length" | "verse_structure"
   },
   (
      ( tei_catDesc+ | ( tei_model.descLike | equiv | gloss )* ),
      tei_category*
   )
}

1.17. <cell>

<cell> (cell) contains one cell of a table. [15.1.1. TEI Tables]
Modulefigures
Attributes
  • att.tableDecoration
    • role
    • @rows
    • @cols
role
StatusOptional
Legal values are:
file
Zeichnung: Dateiname
category
Zeichnung: Kategorie
desc
Zeichnung: Beschreibung
id
Zeichnung: Identifier
src
Zeichnung: Quelle
page
Zeichnung: Seite
ref
Zeichnung: Astr.-Referenz
part
Zeichnung: In M zum Sprachteil (Grc./Cs.)
role
StatusOptional
Legal values are:
file
Zeichnung: Dateiname
category
Zeichnung: Kategorie
desc
Zeichnung: Beschreibung
id
Zeichnung: Identifier
src
Zeichnung: Quelle
page
Zeichnung: Seite
ref
Zeichnung: Astr.-Referenz
part
Zeichnung: In M zum Sprachteil (Grc./Cs.)
Contained by
figures: row
May contain
Example
<row>  <cell role="label">General conduct</cell>  <cell role="data">Not satisfactory, on account of his great unpunctuality    and inattention to duties</cell> </row>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element cell
{
   tei_att.tableDecoration.attribute.rows,
   tei_att.tableDecoration.attribute.cols,
   attribute role
   {
      "file" | "category" | "desc" | "id" | "src" | "page" | "ref" | "part"
   }?,
   attribute role
   {
      "file" | "category" | "desc" | "id" | "src" | "page" | "ref" | "part"
   }?,
   tei_macro.specialPara
}

1.18. <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 12.7. Identifying Changes and Revisions]
Moduleheader
Attributes
whoindicates the person, or group of people, to whom the element content is ascribed.
Derived fromatt.ascribed
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
#dhbuw
DH (Bergische Universität Wuppertal)
#editor
EditorIn
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Derived fromatt.datable.w3c
StatusOptional
Datatypeteidata.temporal.w3c
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
Derived fromatt.docStatus
StatusOptional
Datatypeteidata.enumerated
Legal values are:
finished
Status: erledigt
open
Status: offen
notApplicable
Status: für diese Einheit nicht relevant
finishedComplete
Status: vollständig bearbeitet
finishedLight
Status: teilweise bearbeitet
inProgress
Status: in Arbeit
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
created
Bearbeitungsstand: Datei erstellt
hasTranscript
Bearbeitungsstand: Transkription erstellt
readyForQMTrans
Bearbeitungsstand: Auszeichnung (Transkription) vollständig
hasNormalised
Bearbeitungsstand: Diplomatische Versfassung vollständig
hasSimilia
Bearbeitungsstand: Automatische Auszeichnung der Similien vollständig
hasVersusTetracoli
Bearbeitungsstand: Markierung potentieller versus tetracoli durchgeführt
readyForPublicationTrans
Bearbeitungsstand: Bereit zur Veröffentlichung (Transkription)
update
Bearbeitungsstand: Änderungen nach Veröffentlichung
metadata
Bearbeitungsstand intern: Metadaten eingegeben
transcription
Bearbeitungsstand intern: Transkription eingefügt
normalised
Bearbeitungsstand intern: Normalisierte Versfassung vollständig
metrics
Bearbeitungsstand intern: Metrik technisch ausgezeichnet
similia
Bearbeitungsstand intern: Similien technisch ausgezeichnet
neologisms
Bearbeitungsstand intern: Neologismen technisch ausgezeichnet
versusTetracoli
Bearbeitungsstand intern: versus tetracoli technisch ausgezeichnet
indexReferences
Bearbeitungsstand intern: Indexreferenzen technisch ausgezeichnet
statusEdition
Bearbeitungsstand intern: inhaltliche Edition und technische Auszeichnung vollständig
statusPublication
Bearbeitungsstand intern: Anzeige online fertig/in Arbeit
Contained by
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 status
   {
      "finished"
    | "open"
    | "notApplicable"
    | "finishedComplete"
    | "finishedLight"
    | "inProgress"
   }?,
   attribute type
   {
      "created"
    | "hasTranscript"
    | "readyForQMTrans"
    | "hasNormalised"
    | "hasSimilia"
    | "hasVersusTetracoli"
    | "readyForPublicationTrans"
    | "update"
    | "metadata"
    | "transcription"
    | "normalised"
    | "metrics"
    | "similia"
    | "neologisms"
    | "versusTetracoli"
    | "indexReferences"
    | "statusEdition"
    | "statusPublication"
   },
   tei_macro.specialPara
}

1.19. <charDecl>

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

1.20. <classDecl>

<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
Moduleheader
Member of
Contained by
header: encodingDesc
May contain
header: taxonomy
Example
<classDecl>  <taxonomy xml:id="LCSH">   <bibl>Library of Congress Subject Headings</bibl>  </taxonomy> </classDecl> <!-- ... --> <textClass>  <keywords scheme="#LCSH">   <term>Political science</term>   <term>United States -- Politics and government --      Revolution, 1775-1783</term>  </keywords> </textClass>
Content model
<content>
 <elementRef key="taxonomy"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element classDecl { tei_taxonomy+ }

1.21. <closer>

<closer> (closer) groups together salutations, datelines, bylines, 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]
Moduletextstructure
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusOptional
Datatype1–∞ 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
figures: figure table
textstructure: back body div front
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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="byline"/>
  <elementRef key="signed"/>
  <elementRef key="dateline"/>
  <elementRef key="salute"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element closer
{
   tei_att.cmc.attributes,
   attribute rend { list { ( "center" | "right" )+ } }?,
   (
      text
    | tei_model.gLike
    | byline
    | signed
    | dateline
    | salute
    | tei_model.phrase
    | tei_model.global
   )*
}

1.22. <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 16.2.3. The Setting Description 14.4. Dates]
Modulecore
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Derived fromatt.datable.w3c
StatusOptional
Datatypeteidata.temporal.w3c
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.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
pubYear
Entstehungsdatum der Printpublikation
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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
{
   tei_att.cmc.attributes,
   attribute when { text }?,
   attribute type
   {
      "objectCreated"
    | "contentCreatedPresumed"
    | "contentCreatedDocumented"
    | "mediaCreated"
    | "pubYear"
   }?,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

1.23. <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. [23.4.1. Description of Components]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.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
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.

ExampleExample 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>
ExampleExample of a <desc> element in a non-documentation element.
<place xml:id="KERG2">  <placeName>Kerguelen Islands</placeName> <!-- ... -->  <terrain>   <desc>antarctic tundra</desc>  </terrain> <!-- ... --> </place>
SchematronA <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
{
   tei_att.cmc.attributes,
   attribute type { "contentMilestone" },
   tei_macro.limitedContent
}

1.24. <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]
Modulecore
Attributes
typespecifies the sublanguage or register to which the word or phrase is being assigned.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
neologism
Neologismus
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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
{
   tei_att.cmc.attributes,
   attribute type { "neologism" },
   tei_macro.phraseSeq
}

1.25. <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.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 (Teil)
footnotes
Abschnitt: Apparat (Sachanmerkungen)
critNotes
Abschnitt: Apparat (Textkritische Anmerkungen)
msNotes
Abschnitt: Apparat (Anmerkungen zur Manuskriptvorlage)
commentNotes
Abschnitt: Apparat (Kurzkommentar)
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)
quoteTitle
Abschnitt: Anhang (Kurztitelliste)
bibliography
Abschnitt: Register (Bibliographie)
index
Abschnitt: Register (Index / Werke)
lists
Abschnitt: Register (Fundstellenlisten)
fulltextIndex
Abschnitt: Register (Vollwortregister)
about
Abschnitt: About
section
Abschnitt: About (Unterabschnitt) / Glossar (Unterbschnitt)
drawings
Abschnitt: Zeichnungen
edition
Abschnitt: Edition (Übersicht)
subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include
project
About: Projekt
team
About: Team
introduction_editorial
About: Editorische Einführung
introduction_technical
About: Technische Einführung
sourceDesc
About: Überlieferung
documentation_editorial
About: Editionsrichtlinien
documentation_technical
About: Technische Dokumentation
imprint
About: Impressum
Member of
Contained by
textstructure: back body div front
May contain
dictionaries: entry
figures: figure table
linking: ab anchor
msdescription: msDesc
textstructure: closer div opener
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:rule context="tei:l//tei:div"> <sch:assert test="ancestor::tei:floatingText"> Abstract model violation: Metrical lines (<l> elements) may not contain higher-level structural elements such as <div>, unless <div> is a descendant of <floatingText>. </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:div"> <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> </sch:rule>
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
{
   tei_att.placement.attributes,
   attribute xml:id { text }?,
   attribute type
   {
      "introduction"
    | "notesOnTranslation"
    | "notesOnTextConstitution"
    | "contentMilestones"
    | "transcript"
    | "segment"
    | "footnotes"
    | "critNotes"
    | "msNotes"
    | "commentNotes"
    | "similiaNotes"
    | "listSpondiaci"
    | "listNeologisms"
    | "listMonosyllaba"
    | "listIndexReferences"
    | "metadataMetrics"
    | "quoteTitle"
    | "bibliography"
    | "index"
    | "lists"
    | "fulltextIndex"
    | "about"
    | "section"
    | "drawings"
    | "edition"
   },
   attribute subtype { text }?,
   (
      ( 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.26. <editorialDecl>

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader
Member of
Contained by
header: encodingDesc
May contain
core: p
linking: ab
Example
<editorialDecl>  <normalization>   <p>All words converted to Modern American spelling using      Websters 9th Collegiate dictionary   </p>  </normalization>  <quotation marks="all">   <p>All opening quotation marks converted to “ all closing      quotation marks converted to &amp;cdq;.</p>  </quotation> </editorialDecl>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:editorialDecl"/> </sch:pattern>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.pLike"/>
  <classRef key="model.editorialDeclPart"/>
 </alternate>
</content>
    
Schema Declaration
element editorialDecl { ( tei_model.pLike | tei_model.editorialDeclPart )+ }

1.27. <email>

<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
Modulecore
Attributes
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
character data
Note

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

Example
<email>membership@tei-c.org</email>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element email { tei_att.cmc.attributes, tei_macro.phraseSeq }

1.28. <encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
Legal values are:
encodingDesc
ID zum Referenzieren des teiHeader-Subelements
Member of
Contained by
header: teiHeader
May contain
core: p
gaiji: charDecl
linking: ab
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
{
   attribute xml:id { "encodingDesc" }?,
   ( tei_model.encodingDescPart | tei_model.pLike )+
}

1.29. <entry>

<entry> (entry) contains a single structured entry in any kind of lexical resource, such as a dictionary or lexicon. [10.1. Dictionary Body and Overall Structure 10.2. The Structure of Dictionary Entries]
Moduledictionaries
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Member of
Contained by
dictionaries: entry sense
figures: figure
linking: standOff
textstructure: body div
May contain
dictionaries: entry form sense
figures: figure
linking: anchor
msdescription: msDesc
Note

Like all elements, <entry> inherits an xml:id attribute from the class global. No restrictions are placed on the method used to construct xml:ids; one convenient method is to use the orthographic form of the headword, appending a disambiguating number where necessary. Identification codes are sometimes included on machine-readable tapes of dictionaries for in-house use.

It is recommended to use the <sense> element even for an entry that has only one sense to group together all parts of the definition relating to the word sense since this leads to more consistent encoding across entries.

Example
<entry>  <form>   <orth>disproof</orth>   <pron>dIs"pru:f</pron>  </form>  <gramGrp>   <pos>n</pos>  </gramGrp>  <sense n="1">   <def>facts that disprove something.</def>  </sense>  <sense n="2">   <def>the act of disproving.</def>  </sense> </entry>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <elementRef key="hom"/>
  <elementRef key="sense"/>
  <elementRef key="pc"/>
  <classRef key="model.entryPart.top"/>
  <classRef key="model.global"/>
  <classRef key="model.ptrLike"/>
 </alternate>
</content>
    
Schema Declaration
element entry
{
   tei_att.global.change.attribute.change,
   tei_att.global.facs.attribute.facs,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.linking.attribute.synch,
   tei_att.global.linking.attribute.sameAs,
   tei_att.global.linking.attribute.copyOf,
   tei_att.global.linking.attribute.next,
   tei_att.global.linking.attribute.prev,
   tei_att.global.linking.attribute.exclude,
   tei_att.global.linking.attribute.select,
   tei_att.entryLike.attributes,
   tei_att.sortable.attributes,
   attribute xml:id { text },
   (
      hom
    | tei_sense
    | pc
    | tei_model.entryPart.top
    | tei_model.global
    | tei_model.ptrLike
   )+
}

1.30. <expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
Modulecore
Attributes
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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_att.cmc.attributes, tei_macro.phraseSeq }

1.31. <figDesc>

<figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [15.4. Specific Elements for Graphic Images]
Modulefigures
Attributes
Contained by
figures: figure
May contain
Note

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

Example
<figure>  <graphic url="emblem1.png"/>  <head>Emblemi d'Amore</head>  <figDesc>A pair of naked winged cupids, each holding a    flaming torch, in a rural setting.</figDesc> </figure>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element figDesc
{
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.change.attribute.change,
   tei_att.global.facs.attribute.facs,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.linking.attribute.synch,
   tei_att.global.linking.attribute.sameAs,
   tei_att.global.linking.attribute.copyOf,
   tei_att.global.linking.attribute.next,
   tei_att.global.linking.attribute.prev,
   tei_att.global.linking.attribute.exclude,
   tei_att.global.linking.attribute.select,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.rendition.attribute.style,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.responsibility.attribute.resp,
   tei_att.global.source.attribute.source,
   tei_macro.limitedContent
}

1.32. <figure>

<figure> (figure) groups elements representing or containing graphic information such as an illustration, formula, or figure. [15.4. Specific Elements for Graphic Images]
Modulefigures
Attributes
placespecifies where this item is placed.
Derived fromatt.placement
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Sample values include
margin
Zeichnung am Rand
before
Zeichnung darüber
after
Zeichnung darunter
Member of
Contained by
May contain
dictionaries: entry
linking: ab anchor
msdescription: msDesc
textstructure: closer
Example
<figure>  <head>The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc>  <graphic scale="0.5"   url="http://www.example.org/fig1.png"/> </figure>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.headLike"/>
  <classRef key="model.common"/>
  <elementRef key="figDesc"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.global"/>
  <classRef key="model.divBottom"/>
 </alternate>
</content>
    
Schema Declaration
element figure
{
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.change.attribute.change,
   tei_att.global.facs.attribute.facs,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.linking.attribute.synch,
   tei_att.global.linking.attribute.sameAs,
   tei_att.global.linking.attribute.copyOf,
   tei_att.global.linking.attribute.next,
   tei_att.global.linking.attribute.prev,
   tei_att.global.linking.attribute.exclude,
   tei_att.global.linking.attribute.select,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.rendition.attribute.style,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.responsibility.attribute.resp,
   tei_att.global.source.attribute.source,
   tei_att.written.attributes,
   attribute place { list { + } }?,
   (
      tei_model.headLike
    | tei_model.common
    | tei_figDesc
    | tei_model.graphicLike
    | tei_model.global
    | tei_model.divBottom
   )*
}

1.33. <fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Moduleheader
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?,
      extent?,
      tei_publicationStmt,
      seriesStmt*,
      tei_notesStmt?
   ),
   tei_sourceDesc+
}

1.34. <foreign>

<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
Modulecore
Attributes
xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived fromatt.global
StatusRequired
Datatypeteidata.language
Legal values are:
cs
Sprache: Tschechisch
de
Sprache: Deutsch
en
Sprache: Englisch
grc
Sprache: Griechisch
la
Sprache: Latein
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
character data
Note

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

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

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

Example
This is heathen Greek to you still? Your <foreign xml:lang="la">lapis philosophicus</foreign>?
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element foreign
{
   tei_att.cmc.attributes,
   attribute xml:lang { "cs" | "de" | "en" | "grc" | "la" },
   tei_macro.phraseSeq
}

1.35. <form>

<form> (form information group) groups all the information on the written and spoken forms of one headword. [10.3.1. Information on Written and Spoken Forms]
Moduledictionaries
Attributes
typeclassifies form as simple, compound, etc.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
simple
single free lexical item
lemma
the headword itself
variant
a variant form
compound
word formed from simple lexical items
derivative
word derived from headword
inflected
word in other than usual dictionary form
phrase
multiple-word lexical item
Member of
Contained by
dictionaries: entry form sense
May contain
Example
<form>  <orth>zaptié</orth>  <orth>zaptyé</orth> </form>
(from TLFi)
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.formPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element form
{
   tei_att.global.change.attribute.change,
   tei_att.global.facs.attribute.facs,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.linking.attribute.synch,
   tei_att.global.linking.attribute.sameAs,
   tei_att.global.linking.attribute.copyOf,
   tei_att.global.linking.attribute.next,
   tei_att.global.linking.attribute.prev,
   tei_att.global.linking.attribute.exclude,
   tei_att.global.linking.attribute.select,
   tei_att.lexicographic.attributes,
   attribute type
   {
      "simple"
    | "lemma"
    | "variant"
    | "compound"
    | "derivative"
    | "inflected"
    | "phrase"
   }?,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.formPart
    | tei_model.global
   )*
}

1.36. <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]
Moduletextstructure
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Legal values are:
front
Contained by
textstructure: text
May contain
figures: figure
linking: ab anchor
textstructure: closer div
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.37. <g>

<g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes]
Modulegaiji
Attributes
refpoints to a description of the character or glyph intended.
StatusRequired
Datatypeteidata.pointer
Member of
Contained by
May containCharacter 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 ref { text }, text }

1.38. <glyph>

<glyph> (character glyph) provides descriptive information about a character glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Modulegaiji
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Sample values include
html-dez-10216
Zeichen: Einfache öffnende Winkelklammer (z.B. Unicode U+27E8)
html-dez-10217
Zeichen: Einfache schließende Winkelklammer (z.B. Unicode U+27E9)
Contained by
gaiji: charDecl
May contain
figures: figure
Example
<glyph xml:id="rstroke">  <localProp name="Name"   value="LATIN SMALL LETTER R WITH A FUNNY STROKE"/>  <localProp name="entityvalue="rstroke"/>  <figure>   <graphic url="glyph-rstroke.png"/>  </figure> </glyph>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="unicodeProp"/>
  <elementRef key="unihanProp"/>
  <elementRef key="localProp"/>
  <elementRef key="mapping"/>
  <elementRef key="figure"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.noteLike"/>
  <classRef key="model.descLike"/>
 </alternate>
</content>
    
Schema Declaration
element glyph
{
   attribute xml:id { text },
   (
      unicodeProp
    | unihanProp
    | localProp
    | mapping
    | tei_figure
    | tei_model.graphicLike
    | tei_model.noteLike
    | tei_model.descLike
   )*
}

1.39. <graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 12.1. Digital Facsimiles]
Modulecore
Attributes
url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
Derived fromatt.resourced
StatusRequired
Datatypeteidata.pointer
Member of
Contained by
May contain
core: desc
Note

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

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

Example
<figure>  <graphic url="fig1.png"/>  <head>Figure One: The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc> </figure>
Example
<facsimile>  <surfaceGrp n="leaf1">   <surface>    <graphic url="page1.png"/>   </surface>   <surface>    <graphic url="page2-highRes.png"/>    <graphic url="page2-lowRes.png"/>   </surface>  </surfaceGrp> </facsimile>
Example
<facsimile>  <surfaceGrp n="leaf1xml:id="spi001">   <surface xml:id="spi001r">    <graphic subtype="thumbnail"     type="normalurl="spi/thumb/001r.jpg"/>    <graphic subtype="low-restype="normal"     url="spi/normal/lowRes/001r.jpg"/>    <graphic subtype="high-res"     type="normalurl="spi/normal/highRes/001r.jpg"/>    <graphic subtype="low-res"     type="high-contrasturl="spi/contrast/lowRes/001r.jpg"/>    <graphic subtype="high-res"     type="high-contrasturl="spi/contrast/highRes/001r.jpg"/>   </surface>   <surface xml:id="spi001v">    <graphic subtype="thumbnail"     type="normalurl="spi/thumb/001v.jpg"/>    <graphic subtype="low-restype="normal"     url="spi/normal/lowRes/001v.jpg"/>    <graphic subtype="high-res"     type="normalurl="spi/normal/highRes/001v.jpg"/>    <graphic subtype="low-res"     type="high-contrasturl="spi/contrast/lowRes/001v.jpg"/>    <graphic subtype="high-res"     type="high-contrasturl="spi/contrast/highRes/001v.jpg"/>    <zone xml:id="spi001v_detail01">     <graphic subtype="thumbnail"      type="normalurl="spi/thumb/001v-detail01.jpg"/>     <graphic subtype="low-res"      type="normal"      url="spi/normal/lowRes/001v-detail01.jpg"/>     <graphic subtype="high-res"      type="normal"      url="spi/normal/highRes/001v-detail01.jpg"/>     <graphic subtype="low-res"      type="high-contrast"      url="spi/contrast/lowRes/001v-detail01.jpg"/>     <graphic subtype="high-res"      type="high-contrast"      url="spi/contrast/highRes/001v-detail01.jpg"/>    </zone>   </surface>  </surfaceGrp> </facsimile>
Content model
<content>
 <classRef key="model.descLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
    
Schema Declaration
element graphic
{
   tei_att.global.attribute.xmlbase,
   tei_att.global.attribute.xmlspace,
   tei_att.global.change.attribute.change,
   tei_att.global.facs.attribute.facs,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.linking.attribute.synch,
   tei_att.global.linking.attribute.sameAs,
   tei_att.global.linking.attribute.copyOf,
   tei_att.global.linking.attribute.next,
   tei_att.global.linking.attribute.prev,
   tei_att.global.linking.attribute.exclude,
   tei_att.global.linking.attribute.select,
   tei_att.global.rendition.attribute.rend,
   tei_att.global.rendition.attribute.style,
   tei_att.global.responsibility.attribute.cert,
   tei_att.global.responsibility.attribute.resp,
   tei_att.global.source.attribute.source,
   tei_att.declaring.attributes,
   tei_att.media.attributes,
   attribute url { text },
   tei_model.descLike*
}

1.40. <handDesc>

<handDesc> (description of hands) contains a description of all the different hands used in a manuscript or other object. [11.7.2. Writing, Decoration, and Other Notations]
Modulemsdescription
Member of
Contained by
msdescription: physDesc
May contain
core: p
header: handNote
linking: ab
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?, tei_handNote+ ) }

1.41. <handNote>

<handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [11.7.2. Writing, Decoration, and Other Notations]
Moduleheader
Attributes
Contained by
msdescription: handDesc
May contain
Example
<handNotes>  <handNote medium="brown_inkscope="major"   scribe="authorscribeRef="#KLxml:id="yien.major_hand">Handwriting of the copyist Karol Libelt, brown ink, in German cursive script.</handNote>  <handNote medium="pencilscope="minor"   scribe="annotatorxml:id="yien.pencil">A note, pencil, unknown author.</handNote>  <handNote medium="pencilscope="minor"   scribe="archivistxml:id="yien.pencil2">Writer of the title page Józef Łepkowski, pencil.</handNote>  <handNote medium="pencilscope="minor"   scribe="archivist2scribeRef="#BJKxml:id="yien.pencil3">Note on the title page, pencil, by Józef Korzeniowski.</handNote> </handNotes>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element handNote { tei_att.handFeatures.attributes, tei_macro.specialPara }

1.42. <head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Modulecore
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusOptional
Datatype1–∞ 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
figures: figure table
msdescription: msDesc
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.

ExampleThe 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>
ExampleWhen 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>
ExampleThe <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
{
   tei_att.cmc.attributes,
   attribute rend { list { ( "center" | "right" )+ } }?,
   (
      text
    | tei_lg
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.lLike
    | tei_model.global
   )*
}

1.43. <hi>

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusRequired
Datatype1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
italic
Hervorhebung (editorisch): kursiv
underline
Hervorhebung (editorisch): unterstrichen
super
Hervorhebung (editorisch): hochgestellt
sub
Hervorhebung (editorisch): tiefgestellt
strikethrough
Hervorhebung (editorisch): durchgestrichen
bold
Hervorhebung (editorisch): fett
wavyunderline
Hervorhebung (editorisch): unterkringelt
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
{
   tei_att.cmc.attributes,
   attribute rend
   {
      list
      {
         (
            "italic"
          | "underline"
          | "super"
          | "sub"
          | "strikethrough"
          | "bold"
          | "wavyunderline"
         )+
      }
   },
   tei_macro.paraContent
}

1.44. <history>

<history> (history) groups elements describing the full history of a manuscript, manuscript part, or other object. [11.8. History]
Modulemsdescription
Contained by
msdescription: msDesc
May contain
core: p
linking: ab
msdescription: origin
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?, tei_origin?, provenance*, acquisition? )
}

1.45. <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. [14.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]
Moduleheader
Attributes
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived fromatt.typed
StatusRequired
Datatypeteidata.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
{
   tei_att.cmc.attributes,
   attribute type { "VD16" | "VD17" | "VD18" | "shelfmark" | "di" },
   ( text | tei_model.gLike | tei_idno )*
}

1.46. <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]
Modulecore
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.47. <item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Modulecore
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusOptional
Datatypeteidata.text
corresp(corresponds) points to elements that correspond to the current element in some way.
Derived fromatt.global.linking
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
type
StatusOptional
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)
metVersusTetracoli4Grc
Metrikangaben: Versus tetracoli (im Griechischen) [4 Wörter]
metVersusTetracoli5Grc
Metrikangaben: Versus tetracoli (im Griechischen) [5 Wörter; enthält Kurzwort τ’/δ’/θ’]
metMonosyllabaGrc
Metrikangaben: Monosyllaba (im Griechischen)
metCaesuraPHGrc
Metrikangaben: Zäsur Penthemimeres (PH) (im Griechischen)
metCaesuraKTTGrc
Metrikangaben: Zäsur Kata triton trochaion (KTT) (im Griechischen)
metCaesuraOtherGrc
Metrikangaben: Zäsur andere (z.B. Trithemimeres, Hephthemimeres) (im Griechischen)
metCaesuraNAGrc
Metrikangaben: Zäsur nicht zuordnbar (z.B. wegen Textverlust) (im Griechischen)
metMetricalFootGrc
Metrikangaben: Versfuß (D=Daktylus, S=Spondeus) (im Griechischen)
metDeclPart
Metrische Angaben zum Teil (Sprache, Versmaß, Versanzahl)
subtype
StatusOptional
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
group
Indexeintrag Unterkategorie Person(ifizierung): Personengruppe
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 n { text }?,
   attribute corresp { list { + } }?,
   attribute type
   {
      "person"
    | "place"
    | "subject"
    | "metVerse"
    | "metSpondaicGrc"
    | "metVersusTetracoli4Grc"
    | "metVersusTetracoli5Grc"
    | "metMonosyllabaGrc"
    | "metCaesuraPHGrc"
    | "metCaesuraKTTGrc"
    | "metCaesuraOtherGrc"
    | "metCaesuraNAGrc"
    | "metMetricalFootGrc"
    | "metDeclPart"
   }?,
   attribute subtype
   {
      "mythical"
    | "biblical"
    | "classical"
    | "post-classical"
    | "fictional"
    | "group"
    | "none"
   }?,
   tei_macro.specialPara
}

1.48. <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.6. Speech Contents]
Modulecore
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusRequired
Datatypeteidata.text
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
indent-level-1
Versbegin eingezogen
sortKey
StatusRequired
Datatype
Note

Aus att.sortable entlehnt zu Kennzeichnung der absoluten Verszählung (u.U. abweichend von der Originalzählung in @n).

Member of
Contained by
figures: cell figure
linking: ab seg
msdescription: origin
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:rule context="tei:l"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]">Abstract model violation: Metrical lines (<l> elements) may not contain <l> or <lg> elements.</sch:report> </sch:rule>
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
{
   tei_att.cmc.attributes,
   attribute xml:id { text },
   attribute n { text },
   attribute rend { list { "indent-level-1"+ } }?,
   attribute sortKey { text },
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.global
   )*
}

1.49. <lb>

<lb> (line beginning) marks the beginning of a topographic line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.6. Speech Contents]
Modulecore
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusOptional
Datatypeteidata.text
Member of
Contained by
May containEmpty 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 the beginning of each new topographic line on a manuscript or printed page, at the point where it occurs; 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 beginning in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the beginning of the new topographic line is word-breaking, or to note the source from which it derives.

ExampleThis example shows the encoding of the beginning of each new topographic line within a metrical line, indicating where it occurs in both the 1667 and 1674 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>
ExampleThis example shows the encoding of the beginning of a new topographical line as a means of preserving the visual appearance of a title page. The break attribute is used to show that the beginning of the new line 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
{
   tei_att.cmc.attributes,
   attribute xml:id { text }?,
   attribute n { text }?,
   empty
}

1.50. <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.6. Speech Contents]
Modulecore
Attributes
Member of
Contained by
figures: cell figure
linking: ab seg
msdescription: origin
textstructure: body div
transcr: supplied surplus
May contain
figures: figure
linking: anchor
textstructure: closer opener
transcr: supplied surplus
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:rule context="tei:lg"> <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> </sch:rule>
Schematron
<sch:rule context="tei:lg"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]">Abstract model violation: Lines may not contain line groups.</sch:report> </sch:rule>
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"/>
   <classRef key="model.pPart.transcriptional"/>
   <elementRef key="lg"/>
  </alternate>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <classRef key="model.global"/>
   <elementRef key="lg"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element lg
{
   tei_att.cmc.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         tei_model.lLike
       | tei_model.stageLike
       | tei_model.labelLike
       | tei_model.pPart.transcriptional
       | tei_lg
      ),
      (
         tei_model.lLike
       | tei_model.stageLike
       | tei_model.labelLike
       | tei_model.pPart.transcriptional
       | tei_model.global
       | tei_lg
      )*,
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

1.51. <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
targetspecifies the destination of the reference by supplying one or more URI References.
Derived fromatt.pointing
StatusRequired
Datatype1–∞ 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.52. <list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Modulecore
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
Legal values are:
monosyllabaGrc
Fundstellenliste: Monosyllaba (Gr.)
neologismsGrc
Fundstellenliste: Neologismen (Gr.)
spondiaciGrc
Fundstellenliste: Spondiaci (Gr.)
similiaGrc
Fundstellenliste: Similien (Grc.)
similiaAstr
Fundstellenliste: Similien (Astronautilia)
list_chapter
Edition (Übersicht): Transkribierte Texte
list_about
Fundstellenliste: Über die Edition
list_resources
Fundstellenliste: Zusatzmaterialien
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusOptional
Datatypeteidata.text
Legal values are:
metricsListGrc
Metrikangaben: gesammelte Metrikangaben zum Griechischen
metricsListLat
Metrikangaben: gesammelte Metrikangaben zum Lateinischen
corresp(corresponds) points to elements that correspond to the current element in some way.
Derived fromatt.global.linking
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Member of
Contained by
dictionaries: form
linking: ab seg standOff
msdescription: origin
textstructure: back body div
transcr: supplied surplus
May contain
figures: figure
linking: anchor
textstructure: closer opener
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>
ExampleThe 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
{
   tei_att.cmc.attributes,
   attribute xml:id
   {
      "monosyllabaGrc"
    | "neologismsGrc"
    | "spondiaciGrc"
    | "similiaGrc"
    | "similiaAstr"
    | "list_chapter"
    | "list_about"
    | "list_resources"
   }?,
   attribute n { "metricsListGrc" | "metricsListLat" }?,
   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.53. <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 16.3.2. Declarable Elements]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
bibliography
Liste bibliographischer Einträge (in der Projekt-Bibliographie)
copies
Liste bibliographischer Einträge (Exemplare des Drucks / der Handschrift)
editions
Liste bibliographischer Einträge (Ausgaben des Drucks / der Handschrift)
Member of
Contained by
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>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde" value="tei:listBibl"/> </sch:pattern>
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_att.cmc.attributes,
   attribute type { "bibliography" | "copies" | "editions" },
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_model.milestoneLike | relation | listRelation )*,
      (
         (
            tei_model.biblLike+,
            ( tei_model.milestoneLike | relation | listRelation )*
         )+
      )
   )
}

1.54. <listChange>

<listChange> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.6. The Revision Description 12.7. Identifying Changes and Revisions]
Moduleheader
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
processStatus
Stand der Bearbeitungsschritte
fileStatus
Stand der Datei
Member of
Contained by
May contain
core: desc
Note

When this element appears within the <creation> element it documents the set of revision campaigns or stages identified during the evolution of the original text. When it appears within the <revisionDesc> element, it documents only changes made during the evolution of the encoded representation of that text.

Example
<revisionDesc>  <listChange>   <change when="1991-11-11who="#LB"> deleted chapter 10 </change>   <change when="1991-11-02who="#MSM"> completed first draft </change>  </listChange> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange ordered="true">    <change xml:id="CHG-1">First stage, written in ink by a writer</change>    <change xml:id="CHG-2">Second stage, written in Goethe's hand using pencil</change>    <change xml:id="CHG-3">Fixation of the revised passages and further revisions by        Goethe using ink</change>    <change xml:id="CHG-4">Addition of another stanza in a different hand,        probably at a later stage</change>   </listChange>  </creation> </profileDesc>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="desc"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="listChange"/>
   <elementRef key="change"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listChange
{
   attribute type { "processStatus" | "fileStatus" },
   ( tei_desc*, ( tei_listChange | tei_change )+ )
}

1.55. <locus>

<locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [11.3.5. References to Locations within a Manuscript]
Modulemsdescription
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"/> <!-- ... -->
ExampleThe 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.56. <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]
Moduleverse
Member of
Contained by
header: encodingDesc
May contain
core: note p
linking: ab
verse: metSym
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.
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde" value="tei:metDecl"/> </sch:pattern>
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 )+ | tei_metSym+ }

1.57. <metSym>

<metSym> (metrical notation symbol) documents the intended significance of a particular character or character sequence within a metrical notation, either explicitly or in terms of other <metSym> elements in the same <metDecl>. [6.6. Metrical Notation Declaration]
Moduleverse
Attributes
valuespecifies the character or character sequence being documented.
StatusRequired
Datatype1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
D
Metrische Notation: Versfuß Daktylus (D)
S
Metrische Notation: Versfuß Spondeus (S)
-
Metrische Notation: Silbenquantität Lange Silbe
u
Metrische Notation: Silbenquantität Kurze Silbe
Contained by
verse: metDecl
May contain
figures: figure
header: idno
linking: anchor
msdescription: locus
character data
Example
<metSym value="x">a stressed syllable</metSym> <metSym value="o">an unstressed syllable</metSym> <metSym terminal="falsevalue="A">xoo</metSym>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element metSym
{
   attribute value { list { ( "D" | "S" | "-" | "u" )+ } },
   tei_macro.phraseSeq.limited
}

1.58. <milestone>

<milestone> (milestone) marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element. [3.11.3. Milestone Elements]
Modulecore
Attributes
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusRequired
Datatypeteidata.text
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
paragraphBeginning_editor
Editorisch gesetzter Absatzbeginn
Member of
Contained by
May containEmpty element
Note

For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc.

The order in which <milestone> elements are given at a given point is not normally significant.

Example
<milestone ed="Lan="23unit="Dreissiger"/> ... <milestone ed="AVn="24unit="verse"/> ...
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element milestone
{
   attribute n { text },
   attribute type { "paragraphBeginning_editor" },
   empty
}

1.59. <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]
Modulecore
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 | extent | tei_biblScope )*
}

1.60. <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. [11.6. Intellectual Content]
Modulemsdescription
Contained by
msdescription: msDesc
May contain
core: p textLang
linking: ab
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.61. <msDesc>

<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [11.1. Overview]
Modulemsdescription
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Legal values are:
M
Überlieferungsträger-Sigle: M
T
Überlieferungsträger-Sigle: T
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
manuscript
Überlieferungsträger: Manuskript
typescript
Überlieferungsträger: Typoskript
Member of
Contained by
May contain
core: head p
linking: ab
Note

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

Example
<msDesc>  <msIdentifier>   <settlement>Oxford</settlement>   <repository>Bodleian Library</repository>   <idno type="Bod">MS Poet. Rawl. D. 169.</idno>  </msIdentifier>  <msContents>   <msItem>    <author>Geoffrey Chaucer</author>    <title>The Canterbury Tales</title>   </msItem>  </msContents>  <physDesc>   <objectDesc>    <p>A parchment codex of 136 folios, measuring approx        28 by 19 inches, and containing 24 quires.</p>    <p>The pages are margined and ruled throughout.</p>    <p>Four hands have been identified in the manuscript: the first 44        folios being written in two cursive anglicana scripts, while the        remainder is for the most part in a mixed secretary hand.</p>   </objectDesc>  </physDesc> </msDesc>
Schematron
<sch:rule context="tei:msContents|tei:physDesc|tei:history|tei:additional"> <sch:let name="gi" value="name(.)"/> <sch:report test="preceding-sibling::*[ name(.) eq $gi ] and not( following-sibling::*[ name(.) eq $gi ] )"> Only one <<sch:name/>> is allowed as a child of <<sch:value-of select="name(..)"/>>. </sch:report> </sch:rule>
Content model
<content>
 <sequence 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"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="msContents"/>
    <elementRef key="physDesc"/>
    <elementRef key="history"/>
    <elementRef key="additional"/>
    <elementRef key="msPart"/>
    <elementRef key="msFrag"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element msDesc
{
   attribute xml:id { "M" | "T" },
   attribute type { "manuscript" | "typescript" },
   (
      tei_msIdentifier,
      tei_model.headLike*,
      (
         tei_model.pLike+
       | (
            tei_msContents
          | tei_physDesc
          | tei_history
          | additional
          | msPart
          | msFrag
         )*
      )
   )
}

1.62. <msIdentifier>

<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [11.4. The Manuscript Identifier]
Modulemsdescription
Member of
Contained by
core: bibl
msdescription: msDesc
May contain
header: idno
msdescription: repository
namesdates: placeName
Example
<msIdentifier>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <idno>MS.El.26.C.9</idno> </msIdentifier>
Schematron
<sch:rule context="tei:msIdentifier"> <sch:report test="not( parent::tei:msPart ) and ( child::*[1]/self::idno or child::*[1]/self::altIdentifier or normalize-space(.) eq '')">An <msIdentifier> must contain either a <repository> or <location>.</sch:report> </sch:rule>
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?, institution?, tei_repository?, collection*, tei_idno* ),
   ( msName | objectName | altIdentifier )*
}

1.63. <msItem>

<msItem> (manuscript item) describes an individual work or item within the intellectual content of a manuscript, manuscript part, or other object. [11.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
Member of
Contained by
msdescription: msContents msItem
May contain
Example
<msItem class="#saga">  <locus>ff. 1r-24v</locus>  <title>Agrip af Noregs konunga sögum</title>  <incipit>regi oc h<ex>ann</ex> setiho  <gap extent="7reason="illegible"/>sc    heim se<ex>m</ex> þio</incipit>  <explicit>h<ex>on</ex> hev<ex>er</ex>   <ex>oc</ex>þa buit hesta .ij. aNan viþ    fé enh<ex>on</ex>o<ex>m</ex> aNan til    reiþ<ex>ar</ex>  </explicit>  <textLang mainLang="non">Old Norse/Icelandic</textLang> </msItem>
Content model
<content>
 <sequence 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.64. <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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
{
   tei_att.cmc.attributes,
   attribute type { text }?,
   tei_macro.phraseSeq
}

1.65. <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 10.3.5.4. Notes within Entries]
Modulecore
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusOptional
Datatypeteidata.text
corresp(corresponds) points to elements that correspond to the current element in some way.
Derived fromatt.global.linking
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
literature
Überlieferung: Sekundärliteratur
relatedPersons
Überlieferung: Personenbezüge
relatedPlaces
Überlieferung: Ortsbezüge
metDecl
Überlieferung: Metrische Angaben zu den Teilen (Sprache, Versmaß, Versanzahl)
footnote
Apparate: Sachanmerkung
crit
Apparate: Textkritische Anmerkung
ms
Apparate: Anmerkung zur Manuskriptvorlage
comment
Apparate: Kurzkommentar
similia
Apparate: Similienanmerkung
biblScope
Metadaten: Seitenbereiche in den Quellen
subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
grc
Anmerkung bezieht sich auf den altgriechischen Textteil
la
Anmerkung bezieht sich auf den lateinischen Textteil
de
Anmerkung bezieht sich auf den (original) deutschen Textteil
editorial
Editorische Anmerkung
Member of
Contained by
May contain
ExampleIn 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.
ExampleThe 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
{
   tei_att.cmc.attributes,
   attribute xml:id { text }?,
   attribute n { text }?,
   attribute corresp { list { + } }?,
   attribute type
   {
      "literature"
    | "relatedPersons"
    | "relatedPlaces"
    | "metDecl"
    | "footnote"
    | "crit"
    | "ms"
    | "comment"
    | "similia"
    | "biblScope"
   }?,
   attribute subtype { "grc" | "la" | "de" | "editorial" }?,
   tei_macro.specialPara
}

1.66. <notesStmt>

<notesStmt> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description]
Moduleheader
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
Legal values are:
notesStmt
ID zum Referenzieren des teiHeader-Subelements
Contained by
header: fileDesc
May contain
core: note
Note

Information of different kinds should not be grouped together into the same note.

Example
<notesStmt>  <note>Historical commentary provided by Mark Cohen</note>  <note>OCR scanning done at University of Toronto</note> </notesStmt>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.noteLike"/>
  <elementRef key="relatedItem"/>
 </alternate>
</content>
    
Schema Declaration
element notesStmt
{
   attribute xml:id { "notesStmt" }?,
   ( tei_model.noteLike | relatedItem )+
}

1.67. <num>

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]
Modulecore
Attributes
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusOptional
Datatypeteidata.text
typeindicates the type of numeric value.
Derived fromatt.typed
StatusRequired
Datatypeteidata.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
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
character data
Note

Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 19. 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
{
   tei_att.cmc.attributes,
   attribute n { text }?,
   attribute type { "cardinal" | "percentage" | "numGroup" },
   tei_macro.phraseSeq
}

1.68. <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]
Moduletextstructure
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusOptional
Datatype1–∞ 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
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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
{
   tei_att.cmc.attributes,
   attribute rend { list { ( "center" | "right" )+ } }?,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | argument
    | byline
    | dateline
    | epigraph
    | salute
    | signed
    | tei_model.global
   )*
}

1.69. <orgName>

<orgName> (organization name) contains an organizational name. [14.2.2. Organizational Names]
Modulenamesdates
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
character data
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">  <placeName key="PEN">Pennsyla.</placeName> Abolition Society </orgName> [...]
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element orgName { tei_macro.phraseSeq }

1.70. <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 13. Critical Apparatus]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf 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>
ExampleMore 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_att.cmc.attributes, tei_macro.paraContent }

1.71. <origin>

<origin> (origin) contains any descriptive or other information concerning the origin of a manuscript, manuscript part, or other object. [11.8. History]
Modulemsdescription
Contained by
msdescription: history
May contain
Example
<origin evidence="internalnotAfter="1845"  notBefore="1802resp="#AMH">Copied in <name type="origPlace">Derby</name>, probably from an old Flemish original, between 1802 and 1845, according to <persName xml:id="AMH">Anne-Mette Hansen</persName>. </origin>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element origin { tei_macro.specialPara }

1.72. <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.6. Speech Contents]
Modulecore
Attributes
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:rule context="tei:p"> <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> </sch:rule>
Schematron
<sch:rule context="tei:l//tei:p"> <sch:assert test="ancestor::tei:floatingText | parent::tei:figure | parent::tei:note"> Abstract model violation: Metrical lines (<l> elements) 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:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element p { tei_att.cmc.attributes, tei_macro.paraContent }

1.73. <pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]
Modulecore
Attributes
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusRequired
Datatypeteidata.text
Member of
Contained by
May containEmpty 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 beginning 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 beginning is word-breaking, or to note the source from which it derives.

ExamplePage 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>
ExampleA page beginning 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 { tei_att.cmc.attributes, attribute n { text }, empty }

1.74. <persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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_att.cmc.attributes, tei_macro.phraseSeq }

1.75. <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. [11.7. Physical Description]
Modulemsdescription
Contained by
msdescription: msDesc
May contain
core: p
linking: ab
msdescription: handDesc
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_handDesc? }

1.76. <placeName>

<placeName> (place name) contains an absolute or relative place name. [14.2.3. Place Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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_att.cmc.attributes, tei_macro.phraseSeq }

1.77. <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 16.3.2. Declarable Elements]
Moduleheader
Member of
Contained by
header: encodingDesc
May contain
core: p
linking: ab
Example
<projectDesc>  <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:projectDesc"/> </sch:pattern>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element projectDesc { tei_model.pLike+ }

1.78. <ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore
Attributes
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusOptional
Datatypeteidata.text
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
cf
Für Similienanalyse: Ähnlichkeitsgrad der Stelle markiert als "cf."
de_re_cf
Für Similienanalyse: Ähnlichkeitsgrad der Stelle markiert als "de re cf."
eq
Für Similienanalyse: Ähnlichkeitsgrad der Stelle markiert als "="
sim
Für Similienanalyse: Ähnlichkeitsgrad der Stelle markiert als "~"
undefined
Für Similienanalyse: Ähnlichkeitsgrad der Stelle nicht präzisiert.
targetspecifies the destination of the reference by supplying one or more URI References.
Derived fromatt.pointing
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
verse
Verweis auf einen Vers
external
Verweis auf eine externe Website (nur in Lists, sonst 'ref')
Member of
Contained by
May containEmpty element
Note

The target and cRef attributes are mutually exclusive.

Example
<ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/>
Schematron
<sch:rule context="tei:ptr"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <<sch:name/>>.</sch:report> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element ptr
{
   tei_att.cmc.attributes,
   attribute n { text }?,
   attribute rend
   {
      list { ( "cf" | "de_re_cf" | "eq" | "sim" | "undefined" )+ }
   }?,
   attribute target { list { + } },
   attribute type { "verse" | "external" },
   empty
}

1.79. <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]
Modulecore
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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.80. <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]
Moduleheader
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
Legal values are:
publicationStmt
ID zum Referenzieren des teiHeader-Subelements
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
{
   attribute xml:id { "publicationStmt" }?,
   (
      (
         (
            tei_model.publicationStmtPart.agency,
            tei_model.publicationStmtPart.detail*
         )+
      )
    | tei_model.pLike+
   )
}

1.81. <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.]
Modulecore
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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.82. <q>

<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
Modulecore
Attributes
type(type) may be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
similiaOverlap
Similienstelle fällt mit anderer Similienstelle zusammen
subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
overlap
Similienstelle überschneidet sich mit anderer Similienstelle
nesting
Similienstelle ist mit anderer Similienstelle geschachtelt
Member of
Contained by
May contain
Note

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

Example
It is spelled <q>Tübingen</q> — to enter the letter <q>u</q> with an umlaut hold down the <q>option</q> key and press <q>0 0 f c</q>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element q
{
   attribute type { "similiaOverlap" }?,
   attribute subtype { "overlap" | "nesting" }?,
   tei_macro.specialPara
}

1.83. <quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Modulecore
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
next(next) points to the next element of a virtual aggregate of which the current element is part.
Derived fromatt.global.linking
StatusOptional
Datatypeteidata.pointer
prev(previous) points to the previous element of a virtual aggregate of which the current element is part.
Derived fromatt.global.linking
StatusOptional
Datatypeteidata.pointer
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
similia
Similienauszeichnung im Haupttext: zitierte Stelle
subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
complete
Similienauszeichnung im Haupttext: zitierte Stelle (vollständig)
fragmentedStart
Similienauszeichnung im Haupttext: zitierte Stelle (mit Unterbrechungen; Anfang)
fragmentedMiddle
Similienauszeichnung im Haupttext: zitierte Stelle (mit Unterbrechungen; Mitte)
fragmentedEnd
Similienauszeichnung im Haupttext: zitierte Stelle (mit Unterbrechungen; Ende)
rangeStart
Similienauszeichnung im Haupttext: zitierte Stelle (über Versgrenzen hinweg; Anfang)
rangeMiddle
Similienauszeichnung im Haupttext: zitierte Stelle (über Versgrenzen hinweg; Mitte)
rangeEnd
Similienauszeichnung im Haupttext: zitierte Stelle (über Versgrenzen hinweg; Ende)
Member of
Contained by
May contain
Note

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

Example
Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized in his slogan, <quote>You shall know a word by the company it keeps</quote> <ref>(Firth, 1957)</ref>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element quote
{
   tei_att.cmc.attributes,
   attribute xml:id { text }?,
   attribute next { text }?,
   attribute prev { text }?,
   attribute type { "similia" }?,
   attribute subtype
   {
      "complete"
    | "fragmentedStart"
    | "fragmentedMiddle"
    | "fragmentedEnd"
    | "rangeStart"
    | "rangeMiddle"
    | "rangeEnd"
   }?,
   tei_macro.specialPara
}

1.84. <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore
Attributes
corresp(corresponds) points to elements that correspond to the current element in some way.
Derived fromatt.global.linking
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
sameAspoints to an element that is the same as the current element.
Derived fromatt.global.linking
StatusOptional
Datatypeteidata.pointer
rend(rendition) indicates how the element in question was rendered or presented in the source text.
Derived fromatt.global.rendition
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
visible
Eintrag zur Ansicht in der Edition freigegeben
hidden
Eintrag noch nicht zur Ansicht in der Edition freigegeben
targetspecifies the destination of the reference by supplying one or more URI References.
Derived fromatt.pointing
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.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 fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
di
Verweis Unterkategorie: Verweis auf Deutsche Inschriften Online
digitalCopy
Verweis Unterkategorie: Verweis auf ein digitales Faksimile
similia
Verweis Unterkategorie: Verweis auf eine Autorenstelle im Similienapparat
doi
Verweis Unterkategorie: Verweis auf DOI
html
Verweis Unterkategorie: Verweis auf Projekt-HTML
retainContent
Verweis Unterkategorie: Verweis mit vorgegebenem Textinhalt
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:rule context="tei:ref"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <<sch:name/>>.</sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element ref
{
   tei_att.cmc.attributes,
   attribute corresp { list { + } }?,
   attribute sameAs { text }?,
   attribute rend { list { ( "visible" | "hidden" )+ } }?,
   attribute target { list { + } }?,
   attribute type { "internal" | "external" },
   attribute subtype
   {
      "di" | "digitalCopy" | "similia" | "doi" | "html" | "retainContent"
   }?,
   tei_macro.paraContent
}

1.85. <reg>

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf 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>
ExampleIt 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_att.cmc.attributes, tei_macro.paraContent }

1.86. <repository>

<repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [11.4. The Manuscript Identifier]
Modulemsdescription
Contained by
msdescription: msIdentifier
May contain
figures: figure
header: idno
linking: anchor
msdescription: locus
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.87. <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]
Modulecore
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Legal values are:
transcription
Verantwortlichkeiten: Transkription
annotation
Verantwortlichkeiten: Annotation
edition
Verantwortlichkeiten: Edition (hauptverantwortliche/r EditorIn)
transmission
Verantwortlichkeiten: Überlieferung
additionalAnnotation
Verantwortlichkeiten: Ergänzende Annotation (nicht durch HaupteditorIn)
translation
Verantwortlichkeiten: Übersetzung ins Deutsche
similia
Verantwortlichkeiten: Similien
encoding
Verantwortlichkeiten: Kodierung
markup
Verantwortlichkeiten: Auszeichnung
content
Verantwortlichkeiten: Inhalt (fachwissenschaftlich)
contentAutoGenerated
Verantwortlichkeiten: Inhalt (automatisiert erstellt)
dataModel
Verantwortlichkeiten: Datenmodell
dataAnalysis
Verantwortlichkeiten: Datenanalyse
technicalRealisation
Verantwortlichkeiten: Technische Umsetzung
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusRequired
Datatypeteidata.text
Legal values are:
content
Verantwortlichkeiten-Gruppe: Inhalt
tech
Verantwortlichkeiten-Gruppe: Technik
Contained by
core: respStmt
May contain
figures: figure
header: idno
linking: anchor
msdescription: locus
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
{
   attribute xml:id
   {
      "transcription"
    | "annotation"
    | "edition"
    | "transmission"
    | "additionalAnnotation"
    | "translation"
    | "similia"
    | "encoding"
    | "markup"
    | "content"
    | "contentAutoGenerated"
    | "dataModel"
    | "dataAnalysis"
    | "technicalRealisation"
   },
   attribute n { "content" | "tech" },
   tei_macro.phraseSeq.limited
}

1.88. <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]
Modulecore
Member of
Contained by
header: titleStmt
msdescription: msItem
May contain
core: name note resp
namesdates: orgName persName
Example
<respStmt>  <resp>transcribed from original ms</resp>  <persName>Claus Huitfeldt</persName> </respStmt>
Example
<respStmt>  <resp>converted to XML encoding</resp>  <name>Alan Morrison</name> </respStmt>
Content model
<content>
 <sequence 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
{
   (
      ( tei_resp+, tei_model.nameLike.agent+ )
    | ( tei_model.nameLike.agent+, tei_resp+ )
   ),
   tei_note*
}

1.89. <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]
Moduleheader
Contained by
header: teiHeader
May contain
core: list
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"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="listChange"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="change"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element revisionDesc { tei_list+ | tei_listChange+ | tei_change+ }

1.90. <row>

<row> (row) contains one row of a table. [15.1.1. TEI Tables]
Modulefigures
Attributes
  • att.tableDecoration
    • role
    • @rows
    • @cols
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
corresp(corresponds) points to elements that correspond to the current element in some way.
Derived fromatt.global.linking
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
role(role) indicates the kind of information held in this cell or in each cell of this row.
Derived fromatt.tableDecoration
StatusOptional
Datatypeteidata.enumerated
Legal values are:
label
Überschriftenzeile (Tabellen)
Contained by
figures: table
May contain
figures: cell
Example
<row role="data">  <cell role="label">Classics</cell>  <cell>Idle listless and unimproving</cell> </row>
Content model
<content>
 <elementRef key="cell"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element row
{
   tei_att.tableDecoration.attribute.rows,
   tei_att.tableDecoration.attribute.cols,
   attribute xml:id { text }?,
   attribute corresp { list { + } }?,
   attribute role { "label" }?,
   tei_cell+
}

1.91. <rs>

<rs> (referencing string) contains a general purpose name or referring string. [14.2.1. Personal Names 3.6.1. Referring Strings]
Modulecore
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 fromatt.canonical
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.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 fromatt.typed
StatusOptional
Datatypeteidata.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
na
Textstelle im verwiesenen bibliographischen Eintrag nicht prüfbar, da Buchstabenabschnitt nicht vorhanden
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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
{
   tei_att.cmc.attributes,
   attribute ref { list { + } },
   attribute type { "index" | "bibl" },
   attribute subtype { "verified" | "not-verified" | "not-checked" | "na" }?,
   tei_macro.phraseSeq
}

1.92. <seg>

<seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [17.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.6. Speech Contents]
Modulelinking
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusOptional
Datatypeteidata.text
xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived fromatt.global
StatusOptional
Datatypeteidata.language
Legal values are:
cs
Sprache: Tschechisch
de
Sprache: Deutsch
en
Sprache: Englisch
grc
Sprache: Griechisch
la
Sprache: Latein
corresp(corresponds) points to elements that correspond to the current element in some way.
Derived fromatt.global.linking
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
sameAspoints to an element that is the same as the current element.
Derived fromatt.global.linking
StatusOptional
Datatypeteidata.pointer
function(function) characterizes the function of the segment.
Derived fromatt.segLike
StatusOptional
Datatypeteidata.enumerated
Legal values are:
normalised
Normalisierte Textfassung
met(metrical structure, conventional) contains a user-specified encoding for the conventional metrical structure of the element.
Derived fromatt.metrical
StatusOptional
Datatypetoken
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
metDeclLanguage
Metrische Angaben zu den Teilen: Sprachangaben
meter
Metrische Angaben zu den Teilen: Versmaß
verseCount
Metrische Angaben zu den Teilen: Gesamtverszahl
name
Register: Name
nameVariants
Register: Namensvariante
gnd
Register: GND-Nummer
desc
Register: Beschreibung
references
Register: Fundstellen in der Edition
label
Register: Fundstellen in der Edition (ed. Kurztitel)
bibls
Register: Neologismennachweis in Literatur
mainText
Transkription: Haupttext
translationOfMainText
Transkription: Übersetzung des Haupttextes
spondaic
Auszeichnung: Spondiacus
monosyllabum
Auszeichnung: Monosyllabum
initial
Auszeichnung: Initiale/Akrostichon
simQualifier
Similien: Similiengenauigkeit
simAuthor
Similien: Autorname (in Kombination mit Werktitel)
simAuthorSingle
Similien: Autorname (ohne Werktitel)
simTitle
Similien: Werktitel (in Kombination mit Autornamen)
simTitleSingle
Similien: Werktitel (ohne Autornamen)
simNumber
Similien: Stellenangabe
biblScope
Metadaten: Seitenbereich in der Quelle
subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
spondaic
Register: Spondiacus
monosyllabum
Register: Monosyllabum
neologism
Register: Neologismus
similia
Register: Similie
reference
Register: Stellenangabe
fulltextIndex
Register: Wort im Vollwortindex
quoteTitle
Register: ed. Kurztitel
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.cmc.attributes,
   tei_att.datcat.attribute.targetDatcat,
   attribute xml:id { text }?,
   attribute n { text }?,
   attribute xml:lang { "cs" | "de" | "en" | "grc" | "la" }?,
   attribute corresp { list { + } }?,
   attribute sameAs { text }?,
   attribute function { "normalised" }?,
   attribute met { text }?,
   attribute type
   {
      "metDeclLanguage"
    | "meter"
    | "verseCount"
    | "name"
    | "nameVariants"
    | "gnd"
    | "desc"
    | "references"
    | "label"
    | "bibls"
    | "mainText"
    | "translationOfMainText"
    | "spondaic"
    | "monosyllabum"
    | "initial"
    | "simQualifier"
    | "simAuthor"
    | "simAuthorSingle"
    | "simTitle"
    | "simTitleSingle"
    | "simNumber"
    | "biblScope"
   },
   attribute subtype
   {
      "spondaic"
    | "monosyllabum"
    | "neologism"
    | "similia"
    | "reference"
    | "fulltextIndex"
    | "quoteTitle"
   }?,
   tei_macro.paraContent
}

1.93. <sense>

<sense> groups together all information relating to one word sense in a dictionary entry, for example definitions, examples, and translation equivalents. [10.2. The Structure of Dictionary Entries]
Moduledictionaries
Attributes
Contained by
dictionaries: entry sense
May contain
Note

May contain character data mixed with any other elements defined in the dictionary tag set.

Example
<sense n="2">  <usg type="time">Vx.</usg>  <def>Vaillance, bravoure (spécial., au combat)</def>  <cit type="example">   <quote>La valeur n'attend pas le nombre des années</quote>   <bibl>    <author>Corneille</author>   </bibl>  </cit> </sense>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="sense"/>
  <classRef key="model.entryPart.top"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element sense
{
   tei_att.global.change.attribute.change,
   tei_att.global.facs.attribute.facs,
   tei_att.global.linking.attribute.corresp,
   tei_att.global.linking.attribute.synch,
   tei_att.global.linking.attribute.sameAs,
   tei_att.global.linking.attribute.copyOf,
   tei_att.global.linking.attribute.next,
   tei_att.global.linking.attribute.prev,
   tei_att.global.linking.attribute.exclude,
   tei_att.global.linking.attribute.select,
   tei_att.lexicographic.attributes,
   (
      text
    | tei_model.gLike
    | tei_sense
    | tei_model.entryPart.top
    | tei_model.phrase
    | tei_model.global
   )*
}

1.94. <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]
Moduleheader
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusOptional
DatatypeID
Legal values are:
sourceDesc
ID zum Referenzieren des teiHeader-Subelements
Contained by
header: fileDesc
May contain
figures: table
linking: ab
msdescription: msDesc
Example
<sourceDesc>  <bibl>   <title level="a">The Interesting story of the Children in the Wood</title>. In  <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.  <publisher>OUP</publisher>   <date>1968</date>. </bibl> </sourceDesc>
Example
<sourceDesc>  <p>Born digital: no previous source exists.</p> </sourceDesc>
Schematron
<sch:pattern is-a="declarable"> <sch:param name="tde"  value="tei:sourceDesc"/> </sch:pattern>
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
{
   attribute xml:id { "sourceDesc" }?,
   (
      tei_model.pLike+
    | ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+
   )
}

1.95. <standOff>

<standOff> functions as a container element for linked data, contextual information, and stand-off annotations embedded in a TEI document. [17.10. The standOff Container]
Modulelinking
Member of
Contained by
textstructure: TEI
May contain
dictionaries: entry
figures: table
header: listChange
linking: seg
msdescription: msDesc
ExampleThis example shows an encoding of morphosyntactic features similar to the encoding system used by ISO 24611 (MAF).
<TEI xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader> <!-- ... -->  </teiHeader>  <text>   <body> <!-- ... -->    <p>     <w xml:id="w51">I</w>     <w xml:id="w52">wanna</w>     <w xml:id="w53">put</w>     <w xml:id="w54">up</w>     <w xml:id="w55">new</w>     <w xml:id="w56">wallpaper</w>     <pc>.</pc>    </p> <!-- ... -->   </body>  </text>  <standOff type="morphosyntax">   <spanGrp type="wordForm">    <span ana="#fs01target="#w51"/>    <span ana="#fs02target="#w52"/>    <span ana="#fs03target="#w52"/>    <span ana="#fs04target="#w53 #w54"/>    <span ana="#fs05target="#w55"/>    <span ana="#fs06target="#w56"/>   </spanGrp>   <fs xml:id="fs01">    <f name="lemma">     <string>I</string>    </f>    <f name="pos">     <symbol value="PP"/>    </f>   </fs>   <fs xml:id="fs02">    <f name="lemma">     <string>want</string>    </f>    <f name="pos">     <symbol value="VBP"/>    </f>   </fs>   <fs xml:id="fs03">    <f name="lemma">     <string>to</string>    </f>    <f name="pos">     <symbol value="TO"/>    </f>   </fs>   <fs xml:id="fs04">    <f name="lemma">     <string>put up</string>    </f>    <f name="pos">     <symbol value="VB"/>    </f>   </fs>   <fs xml:id="fs05">    <f name="lemma">     <string>new</string>    </f>    <f name="pos">     <symbol value="JJ"/>    </f>   </fs>   <fs xml:id="fs06">    <f name="lemma">     <string>wallpaper</string>    </f>    <f name="pos">     <symbol value="NN"/>    </f>   </fs>  </standOff> </TEI>
ExampleThis example shows an encoding of contextual information which is referred to from the main text.
<TEI xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader> <!-- ... -->  </teiHeader>  <standOff>   <listPlace>    <place xml:id="LATL">     <placeName>Atlanta</placeName>     <location>      <region key="US-GA">Georgia</region>      <country key="USA">United States of America</country>      <geo>33.755 -84.39</geo>     </location>     <population quantity="489359"      source="https://www.biggestuscities.com/city/atlanta-georgiatype="interpolatedCensuswhen="1963"/>    </place>    <place xml:id="LBHM">     <placeName>Birmingham</placeName>     <location>      <region key="US-AL">Alabama</region>      <country key="USA">United States of America</country>      <geo>33.653333 -86.808889</geo>     </location>     <population quantity="332891"      source="https://www.biggestuscities.com/city/birmingham-alabamatype="interpolatedCensuswhen="1963"/>    </place>   </listPlace>  </standOff>  <text>   <body> <!-- ... -->    <p>Moreover, I am <choice>      <sic>congnizant</sic>      <corr>cognizant</corr>     </choice> of the interrelatedness of all communities and    <lb/>states. I cannot sit idly by in <placeName ref="#LATL">Atlanta</placeName> and not be concerned about what happens    <lb/>in <placeName ref="#LBHM">Birmingham</placeName>. <seg xml:id="FQ17">Injustice anywhere is a threat to justice everywhere.</seg> We    <lb/>are caught in an inescapable network of mutuality, tied in a single garment    <lb/>of destiny. Whatever affects one directly affects all indirectly. Never    <lb/>again can we afford to live with the narrow, provincial <soCalled rendition="#Rqms">outside agitator</soCalled>     <lb/>idea. Anyone who lives inside the United States can never be considered    <lb/>an outsider anywhere in this country.</p> <!-- ... -->   </body>  </text> </TEI>
Content model
<content>
 <classRef key="model.standOffPart"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element standOff { tei_model.standOffPart+ }

1.96. <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. [12.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
Member of
Contained by
May contain
Note

The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 12.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.97. <surplus>

<surplus> (surplus) marks text present in the source which the editor believes to be superfluous or redundant. [12.3.3.1. Damage, Illegibility, and Supplied Text]
Moduletranscr
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.98. <table>

<table> (table) contains text displayed in tabular form, in rows and columns. [15.1.1. TEI Tables]
Modulefigures
Member of
Contained by
dictionaries: form
linking: ab seg standOff
msdescription: origin
textstructure: back body div
transcr: supplied surplus
May contain
figures: figure row
linking: anchor
textstructure: closer
Note

Contains an optional heading and a series of rows.

Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.

Example
<table cols="4rows="4">  <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>  <row role="label">   <cell role="data"/>   <cell role="data">Dossing Cribs or Lodging Houses</cell>   <cell role="data">Beds</cell>   <cell role="data">Needys or Nightly Lodgers</cell>  </row>  <row role="data">   <cell role="label">Bury St Edmund's</cell>   <cell role="data">5</cell>   <cell role="data">8</cell>   <cell role="data">128</cell>  </row>  <row role="data">   <cell role="label">Thetford</cell>   <cell role="data">3</cell>   <cell role="data">6</cell>   <cell role="data">36</cell>  </row>  <row role="data">   <cell role="label">Attleboro'</cell>   <cell role="data">3</cell>   <cell role="data">5</cell>   <cell role="data">20</cell>  </row>  <row role="data">   <cell role="label">Wymondham</cell>   <cell role="data">1</cell>   <cell role="data">11</cell>   <cell role="data">22</cell>  </row> </table>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.headLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate maxOccurs="1" minOccurs="1">
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <elementRef key="row"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.graphicLike"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </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 table
{
   ( tei_model.headLike | tei_model.global )*,
   (
      ( ( tei_row, tei_model.global* )+ )
    | ( ( tei_model.graphicLike, tei_model.global* )+ )
   ),
   ( ( tei_model.divBottom, tei_model.global* )* )
}

1.99. <taxonomy>

<taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
Contained by
May contain
msdescription: msDesc
Note

Nested taxonomies are common in many fields, so the <taxonomy> element can be nested.

Example
<taxonomy xml:id="tax.b">  <bibl>Brown Corpus</bibl>  <category xml:id="tax.b.a">   <catDesc>Press Reportage</catDesc>   <category xml:id="tax.b.a1">    <catDesc>Daily</catDesc>   </category>   <category xml:id="tax.b.a2">    <catDesc>Sunday</catDesc>   </category>   <category xml:id="tax.b.a3">    <catDesc>National</catDesc>   </category>   <category xml:id="tax.b.a4">    <catDesc>Provincial</catDesc>   </category>   <category xml:id="tax.b.a5">    <catDesc>Political</catDesc>   </category>   <category xml:id="tax.b.a6">    <catDesc>Sports</catDesc>   </category>  </category>  <category xml:id="tax.b.d">   <catDesc>Religion</catDesc>   <category xml:id="tax.b.d1">    <catDesc>Books</catDesc>   </category>   <category xml:id="tax.b.d2">    <catDesc>Periodicals and tracts</catDesc>   </category>  </category> </taxonomy>
Example
<taxonomy>  <category xml:id="literature">   <catDesc>Literature</catDesc>   <category xml:id="poetry">    <catDesc>Poetry</catDesc>    <category xml:id="sonnet">     <catDesc>Sonnet</catDesc>     <category xml:id="shakesSonnet">      <catDesc>Shakespearean Sonnet</catDesc>     </category>     <category xml:id="petraSonnet">      <catDesc>Petrarchan Sonnet</catDesc>     </category>    </category>    <category xml:id="haiku">     <catDesc>Haiku</catDesc>    </category>   </category>   <category xml:id="drama">    <catDesc>Drama</catDesc>   </category>  </category>  <category xml:id="meter">   <catDesc>Metrical Categories</catDesc>   <category xml:id="feet">    <catDesc>Metrical Feet</catDesc>    <category xml:id="iambic">     <catDesc>Iambic</catDesc>    </category>    <category xml:id="trochaic">     <catDesc>trochaic</catDesc>    </category>   </category>   <category xml:id="feetNumber">    <catDesc>Number of feet</catDesc>    <category xml:id="pentameter">     <catDesc>>Pentameter</catDesc>    </category>    <category xml:id="tetrameter">     <catDesc>>Tetrameter</catDesc>    </category>   </category>  </category> </taxonomy> <!-- elsewhere in document --> <lg ana="#shakesSonnet #iambic #pentameter">  <l>Shall I compare thee to a summer's day</l> <!-- ... --> </lg>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="1" minOccurs="1">
   <alternate maxOccurs="unbounded"
    minOccurs="1">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
   <sequence maxOccurs="1" minOccurs="1">
    <alternate maxOccurs="unbounded"
     minOccurs="1">
     <classRef key="model.descLike"
      maxOccurs="1" minOccurs="1"/>
     <elementRef key="equiv" maxOccurs="1"
      minOccurs="1"/>
     <elementRef key="gloss" maxOccurs="1"
      minOccurs="1"/>
    </alternate>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <elementRef key="category"/>
     <elementRef key="taxonomy"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence maxOccurs="1" minOccurs="1">
   <classRef key="model.biblLike"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element taxonomy
{
   (
      ( tei_category | tei_taxonomy )+
    | (
         ( tei_model.descLike | equiv | gloss )+,
         ( tei_category | tei_taxonomy )*
      )
   )
 | ( tei_model.biblLike, ( tei_category | tei_taxonomy )* )
}

1.100. <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 16.1. Varieties of Composite Text]
Moduleheader
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Sample values include
teiHeader
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.101. <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]
Modulecore
Attributes
Member of
Contained by
May contain
figures: figure
gaiji: g
header: idno
linking: anchor seg
msdescription: locus
transcr: supplied surplus
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_att.cmc.attributes, tei_macro.phraseSeq }

1.102. <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 16.1. Varieties of Composite Text]
Moduletextstructure
Member of
Contained by
textstructure: TEI
May contain
figures: figure
linking: anchor
textstructure: back body front
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>
ExampleThe 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.103. <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 11.6.6. Languages and Writing Systems]
Modulecore
Attributes
mainLang(main language) supplies a code which identifies the chief language used in the bibliographic work.
StatusRequired
Datatypeteidata.language
Legal values are:
cs
Sprache: Tschechisch
de
Sprache: Deutsch
en
Sprache: Englisch
grc
Sprache: Griechisch
la
Sprache: Latein
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 { "cs" | "de" | "en" | "grc" | "la" },
   tei_macro.specialPara
}

1.104. <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]
Modulecore
Attributes
sameAspoints to an element that is the same as the current element.
Derived fromatt.global.linking
StatusOptional
Datatypeteidata.pointer
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.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
{
   tei_att.cmc.attributes,
   attribute sameAs { text }?,
   attribute type
   {
      "file" | "quoteInternal" | "quoteExternal" | "main" | "sub" | "poem"
   }?,
   tei_macro.paraContent
}

1.105. <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]
Moduleheader
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* }

2. Model classes

2.1. model.addrPart

model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.6.2. Addresses]
Moduletei
Used by
Membersmodel.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno rs] addrLine

2.2. model.addressLike

model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]
Moduletei
Used by
Membersaddress email

2.3. model.annotationLike

model.annotationLike groups elements used to represent annotations. [17.10. The standOff Container]
Moduletei
Used by
Membersnote

2.4. 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]
Moduletei
Used by
Membersmodel.quoteLike[quote]

2.5. 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.]
Moduletei
Used by
Memberslicence

2.6. model.biblLike

2.7. model.biblPart

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

2.8. model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.cmc model.divPart[model.lLike[l] model.pLike[ab p] lg] model.entryLike[entry] model.inter[model.attributable[model.quoteLike[quote]] model.biblLike[bibl biblStruct listBibl msDesc] model.egLike model.labelLike[desc] model.listLike[list table] model.oddDecl model.stageLike] q
Note

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

2.9. model.dateLike

model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Used by
Membersdate

2.10. model.descLike

model.descLike groups elements which contain a description of their function.
Moduletei
Used by
Membersdesc

2.11. model.divBottom

model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions]
Moduletei
Used by
Membersmodel.divBottomPart[address 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]
Moduletei
Used by
Membersaddress closer

2.13. model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Moduletei
Used by
Membersdiv

2.14. model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.lLike[l] model.pLike[ab 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]
Moduletei
Used by
Membersmodel.divTopPart[model.headLike[head] address 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]
Moduletei
Used by
Membersmodel.headLike[head] address 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]
Moduletei
Used by
Membersdistinct foreign term title

2.18. model.encodingDescPart

model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.
Moduletei
Used by
MemberscharDecl classDecl editorialDecl metDecl projectDesc

2.19. model.entryLike

model.entryLike groups elements structurally analogous to paragraphs within dictionaries. [10.1. Dictionary Body and Overall Structure 1.3. The TEI Class System]
Moduledictionaries
Used by
Membersentry

2.20. model.entryPart.top

model.entryPart.top groups high level elements within a structured dictionary entry. [10.2. The Structure of Dictionary Entries]
Moduletei
Used by
Membersmodel.biblLike[bibl biblStruct listBibl msDesc] entry form
Note

Members of this class typically contain related parts of a dictionary entry which form a coherent subdivision, for example a particular sense, homonym, etc.

2.21. model.formPart

model.formPart groups elements allowed within a <form> element in a dictionary. [10.3.1. Information on Written and Spoken Forms]
Moduledictionaries
Used by
Membersmodel.gramPart[model.lexicalRefinement model.morphLike] form

2.22. model.frontPart

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

2.23. model.gLike

model.gLike groups elements used to represent individual non-Unicode characters or glyphs.
Moduletei
Used by
Membersg

2.24. model.global

model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.global.edit model.global.meta model.milestoneLike[anchor lb milestone pb] model.noteLike[note] figure

2.25. model.gramPart

model.gramPart groups elements allowed within a <gramGrp> element in a dictionary. [10.3.2. Grammatical Information]
Moduledictionaries
Used by
Membersmodel.lexicalRefinement model.morphLike

2.26. model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]
Moduletei
Used by
Membersgraphic

2.27. model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Moduletei
Used by
Membershead

2.28. 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]
Moduletei
Used by
Membershi q

2.29. model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
Moduletei
Used by
Membersmodel.emphLike[distinct foreign term title] model.hiLike[hi q]

2.30. model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]
Moduletei
Used by
MembersbiblScope pubPlace publisher

2.31. model.inter

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

2.32. model.lLike

model.lLike groups elements representing metrical components such as verse lines.
Moduletei
Used by
Membersl

2.33. model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Moduletei
Used by
Membersdesc

2.34. model.limitedPhrase

2.35. model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Moduletei
Used by
Memberslist table

2.36. 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]
Moduletei
Used by
Membersnum

2.37. model.milestoneLike

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

2.38. model.msItemPart

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

2.39. model.msQuoteLike

model.msQuoteLike groups elements which represent passages such as titles quoted from a manuscript as a part of its description.
Moduletei
Used by
Memberstitle

2.40. model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei
Used by
Membersmodel.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno rs
Note

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

2.41. model.nameLike.agent

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

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

2.42. model.noteLike

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

2.43. model.pLike

2.44. model.pLike.front

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

2.45. 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]
Moduletei
Used by
Membersmodel.addressLike[address email] model.dateLike[date] model.measureLike[num] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno rs]

2.46. model.pPart.edit

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

2.47. 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]
Moduletei
Used by
Membersabbr expan

2.48. model.pPart.msdesc

model.pPart.msdesc groups phrase-level elements used in manuscript description. [11. Manuscript Description]
Moduletei
Used by
Memberslocus

2.49. model.pPart.transcriptional

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

2.51. model.phrase

model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.graphicLike[graphic] model.highlighted[model.emphLike[distinct foreign term title] model.hiLike[hi q]] model.lPart model.pPart.data[model.addressLike[address email] model.dateLike[date] model.measureLike[num] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[placeName]] idno rs]] model.pPart.edit[model.pPart.editorial[abbr expan] model.pPart.transcriptional[orig reg supplied surplus]] model.pPart.msdesc[locus] model.phrase.xml model.ptrLike[ptr ref] model.ptrLike.form model.segLike[seg] model.specDescLike
Note

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

2.52. model.physDescPart

model.physDescPart groups specialized elements forming part of the physical description of a manuscript or similar written source.
Modulemsdescription
Used by
MembershandDesc

2.53. model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [14.2.3. Place Names]
Moduletei
Used by
MembersplaceName

2.54. model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Moduletei
Used by
Membersmodel.placeNamePart[placeName]

2.55. model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
Moduletei
Used by
Membersptr 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.]
Moduletei
Used by
Memberspublisher
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.]
Moduletei
Used by
Membersmodel.ptrLike[ptr ref] address availability date idno pubPlace
Note

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

See also model.publicationStmtPart.agency.

2.58. model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Moduletei
Used by
Membersquote

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]
Moduletei
Used by
MembersstandOff 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.
Moduletei
Used by
Membersauthor respStmt

2.61. model.segLike

model.segLike groups elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories]
Moduletei
Used by
Membersseg
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.standOffPart

model.standOffPart groups elements which may be used as children of <standOff>.
Moduletei
Used by
Membersmodel.annotationLike[note] model.biblLike[bibl biblStruct listBibl msDesc] model.entryLike[entry] model.global.meta model.listLike[list table] listChange seg

2.63. model.teiHeaderPart

model.teiHeaderPart groups high level elements which may appear more than once in a TEI header.
Moduletei
Used by
MembersencodingDesc

2.64. model.titlepagePart

model.titlepagePart groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. Title Pages]
Moduletei
Used by
Membersgraphic

3. Attribute classes

3.1. att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Moduletei
Membersatt.ascribed.directed[q] change
Attributes
whoindicates the person, or group of people, to whom the element content is ascribed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <role> elements in the <castList> using the who attribute.
<castItem type="role">  <role xml:id="Barnardo">Bernardo</role> </castItem> <castItem type="role">  <role xml:id="Francisco">Francisco</role>  <roleDesc>a soldier</roleDesc> </castItem> <!-- ... --> <sp who="#Barnardo">  <speaker>Bernardo</speaker>  <l n="1">Who's there?</l> </sp> <sp who="#Francisco">  <speaker>Francisco</speaker>  <l n="2">Nay, answer me: stand, and unfold yourself.</l> </sp>
Note

For transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified <person> element.

3.2. 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. [14.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.naming[att.personal[name orgName persName placeName] author pubPlace repository rs] address bibl biblStruct catDesc date publisher resp respStmt term title
Attributes
keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
StatusOptional
Datatypeteidata.text
<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.

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.
StatusOptional
Datatype1–∞ 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.

ExampleIn this contrived example, a canonical reference to the same organisation is provided in four different ways.
<author n="1">  <name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="2">  <name ref="nzvn:427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="3">  <name ref="./named_entities.xml#o427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="4">  <name key="name-427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>
The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection, but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire external system for key resolution be available.
Note

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

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

3.3. att.cmc

att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment.
Moduletei
Membersab abbr address anchor bibl biblStruct closer date desc distinct email expan figure foreign graphic head hi idno l lb lg list listBibl milestone name note num opener orgName orig p pb persName placeName ptr q quote ref reg rs seg table term title
Attributes
generatedBy(generated by) categorizes how the content of an element was generated in a CMC environment.
StatusOptional
Datatypeteidata.enumerated
Schematron
<sch:rule context="tei:*[@generatedBy]"> <sch:assert test="ancestor-or-self::tei:post">The @generatedBy attribute is for use within a <post> element.</sch:assert> </sch:rule>
Suggested values include:
human
the content was ‘naturally’ typed or spoken by a human user
template
the content was generated after a human user activated a template for its insertion
system
the content was generated by the system, i.e. the CMC environment
bot
the content was generated by a bot, i.e. a non-human agent, typically one that is not part of the CMC environment itself
unspecified
the content was generated by an unknown or unspecified process
automatic system message in chat: user moves on to another chatroom
<post generatedBy="system"  rend="color:blue"  type="event"  who="#system">  <p>   <name corresp="#A02"    type="nickname">McMike</name> geht    in einen anderen Raum: <name type="roomname">Kreuzfahrt</name>  </p> </post>
automatic system message in chat: user enters a chatroom
<post generatedBy="system"  type="event">  <p>   <name corresp="#A08"    type="nickname">c_bo</name> betritt    den Raum. </p> </post>
automatic system message in chat: user changes his font color
<post generatedBy="system"  rend="color:red"  type="event">  <p>   <name corresp="#A08"    type="nickname">c_bo</name> hat die    Farbe gewechselt.  </p> </post>
An automatic signature of user including an automatic timestamp (Wikipedia discussion, anonymized). The specification of generatedBy at the inner element <signed> is meant to override the specification at the outer element <post>. This is generally possible when the outer generatedBy value is "human".
<post generatedBy="human"  indentLevel="2"  synch="#t00394407"  type="standard"  who="#WU00005582">  <p> Kurze Nachfrage: Die Hieros für den Goldnamen stammen    auch von Beckerath gem. Literatur ? Grüße --</p>  <signed generatedBy="template"   rend="inline">   <gap reason="signatureContent"/>   <time generatedBy="template">18:50, 22. Okt. 2008 (CEST)</time>  </signed> </post>
Wikipedia talk page: user signature
<post generatedBy="human"  type="written"> <!-- ... main content of posting ... -->  <signed generatedBy="template">   <gap reason="signatureContent"/>   <time generatedBy="template">12:01, 12. Jun. 2009 (CEST)</time>  </signed> </post>

3.4. 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). [14.4. Dates]
Modulenamesdates
Membersatt.datable[author change date idno licence name orgName origin persName placeName resp title]
Attributes
when-customsupplies the value of a date or time in some custom standard form.
StatusOptional
Datatype1–∞ 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-customspecifies the earliest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
notAfter-customspecifies the latest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
from-customindicates the starting point of the period in some custom standard form.
StatusOptional
Datatype1–∞ 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-customindicates the ending point of the period in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred.
StatusOptional
Datatypeteidata.pointer
datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
StatusOptional
Datatypeteidata.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.5. 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 14.4. Dates]
Modulenamesdates
Membersatt.datable[author change date idno licence name orgName origin persName placeName resp title]
Attributes
when-isosupplies the value of a date or time in a standard form.
StatusOptional
Datatypeteidata.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 occurrence 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 occurrence could not.
notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.iso
notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.iso
from-isoindicates the starting point of the period in standard form.
StatusOptional
Datatypeteidata.temporal.iso
to-isoindicates the ending point of the period in standard form.
StatusOptional
Datatypeteidata.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.6. 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 14.4. Dates]
Moduletei
Membersatt.datable[author change date idno licence name orgName origin persName placeName resp title]
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.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>
notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.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.7. 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. [10.5.2. Lexical View 19.3. Other Atomic Feature Values]
Moduletei
Membersatt.lexicographic[form sense] att.segLike[seg] category taxonomy
Attributes
datcatprovides 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).
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcatprovides 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.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcatprovides 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.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
ExampleThe 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.
ExampleIn 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 the <equiv> element that is a child of <elementSpec> or <attDef>.
ExampleThe <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.
<encodingDesc> <!-- ... -->  <classDecl> <!-- ... -->   <taxonomy datcat="https://universaldependencies.org/u/dep/index.html"    xml:id="UD-SYN">    <desc>     <term>UD syntactic relations</term>    </desc>    <category valueDatcat="https://universaldependencies.org/u/dep/acl.html"     xml:id="acl">     <catDesc>      <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>    </category>    <category valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html"     xml:id="acl_relcl">     <catDesc>      <term>acl:relcl</term>: relative clause modifier</catDesc>    </category>    <category valueDatcat="https://universaldependencies.org/u/dep/advcl.html"     xml:id="advcl">     <catDesc>      <term>advcl</term>: Adverbial clause modifier</catDesc>    </category> <!-- ... -->   </taxonomy>  </classDecl> </encodingDesc>
The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly.
ExampleThe 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.
ExampleThe att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.
<!-- in the dictionary header --><encodingDesc>  <classDecl>   <taxonomy xml:id="domains"> <!--...-->    <category xml:id="domain.medical_and_health_sciences">     <catDesc xml:lang="en">Medical and Health Sciences</catDesc>     <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>     <category valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025"      xml:id="domain.medical_and_health_sciences.medicine">      <catDesc xml:lang="en">       <term>Medicine</term>       <gloss> <!--...-->       </gloss>      </catDesc>      <catDesc xml:lang="pt">       <term>Medicina</term>       <gloss> <!--...-->       </gloss>      </catDesc>     </category>    </category> <!--...-->   </taxonomy>  </classDecl> </encodingDesc> <!-- inside an <entry> element: --> <usg type="domain"  valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg>
In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH).
Note

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

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

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

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

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

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

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

3.8. 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. [16.3. Associating Contextual Information with a Text]
Moduletei
Membersab back body div front graphic lg msDesc p ptr ref standOff 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.
StatusOptional
Datatype1–∞ 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 16.3. Associating Contextual Information with a Text.

3.9. att.entryLike

att.entryLike provides attributes used to distinguish different styles of dictionary entries. [10.1. Dictionary Body and Overall Structure 10.2. The Structure of Dictionary Entries]
Moduledictionaries
Membersentry
Attributes
  • att.typed
    • type
    • @subtype
typeindicates type of entry, in dictionaries with multiple types.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
main
a main entry (default).[Default]
hom
(homograph) groups information relating to one homograph within an entry.
xref
(cross reference) a reduced entry whose only function is to point to another main entry (e.g. for forms of an irregular verb or for variant spellings: was pointing to be, or esthete to aesthete).
affix
an entry for a prefix, infix, or suffix.
abbr
(abbreviation) an entry for an abbreviation.
supplemental
a supplemental entry (for use in dictionaries which issue supplements to their main work in which they include updated information about entries).
foreign
an entry for a foreign word in a monolingual dictionary.
Note

The global n attribute may be used to encode the homograph numbers attached to entries for homographs.

3.10. att.fragmentable

att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
Moduletei
Membersatt.divLike[div lg] att.segLike[seg] ab l p
Attributes
partspecifies 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.
StatusOptional
Datatypeteidata.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.change

att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
Moduletranscr
Membersatt.global[TEI ab abbr addrLine address analytic anchor author availability back bibl biblScope biblStruct body catDesc category cell change charDecl classDecl closer date desc distinct div editorialDecl email encodingDesc entry expan figDesc figure fileDesc foreign form front g glyph graphic handDesc handNote head hi history idno imprint item l lb lg licence list listBibl listChange locus metDecl metSym milestone monogr msContents msDesc msIdentifier msItem name note notesStmt num opener orgName orig origin p pb persName physDesc placeName projectDesc ptr pubPlace publicationStmt publisher q quote ref reg repository resp respStmt revisionDesc row rs seg sense sourceDesc standOff supplied surplus table taxonomy teiHeader term text textLang title titleStmt]
Attributes
changepoints 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.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

3.12. 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. [12.1. Digital Facsimiles]
Moduletranscr
Membersatt.global[TEI ab abbr addrLine address analytic anchor author availability back bibl biblScope biblStruct body catDesc category cell change charDecl classDecl closer date desc distinct div editorialDecl email encodingDesc entry expan figDesc figure fileDesc foreign form front g glyph graphic handDesc handNote head hi history idno imprint item l lb lg licence list listBibl listChange locus metDecl metSym milestone monogr msContents msDesc msIdentifier msItem name note notesStmt num opener orgName orig origin p pb persName physDesc placeName projectDesc ptr pubPlace publicationStmt publisher q quote ref reg repository resp respStmt revisionDesc row rs seg sense sourceDesc standOff supplied surplus table taxonomy teiHeader term text textLang title titleStmt]
Attributes
facs(facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

3.13. att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [17. Linking, Segmentation, and Alignment]
Modulelinking
Membersatt.global[TEI ab abbr addrLine address analytic anchor author availability back bibl biblScope biblStruct body catDesc category cell change charDecl classDecl closer date desc distinct div editorialDecl email encodingDesc entry expan figDesc figure fileDesc foreign form front g glyph graphic handDesc handNote head hi history idno imprint item l lb lg licence list listBibl listChange locus metDecl metSym milestone monogr msContents msDesc msIdentifier msItem name note notesStmt num opener orgName orig origin p pb persName physDesc placeName projectDesc ptr pubPlace publicationStmt publisher q quote ref reg repository resp respStmt revisionDesc row rs seg sense sourceDesc standOff supplied surplus table taxonomy teiHeader term text textLang title titleStmt]
Attributes
corresp(corresponds) points to elements that correspond to the current element in some way.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
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 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.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
sameAspoints to an element that is the same as the current element.
StatusOptional
Datatypeteidata.pointer
copyOfpoints to an element of which the current element is a copy.
StatusOptional
Datatypeteidata.pointer
Note

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

next(next) points to the next element of a virtual aggregate of which the current element is part.
StatusOptional
Datatypeteidata.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.
StatusOptional
Datatypeteidata.pointer
Note

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

excludepoints to elements that are in exclusive alternation with the current element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
selectselects 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.
StatusOptional
Datatype1–∞ 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.14. 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]
Moduletei
Membersatt.global[TEI ab abbr addrLine address analytic anchor author availability back bibl biblScope biblStruct body catDesc category cell change charDecl classDecl closer date desc distinct div editorialDecl email encodingDesc entry expan figDesc figure fileDesc foreign form front g glyph graphic handDesc handNote head hi history idno imprint item l lb lg licence list listBibl listChange locus metDecl metSym milestone monogr msContents msDesc msIdentifier msItem name note notesStmt num opener orgName orig origin p pb persName physDesc placeName projectDesc ptr pubPlace publicationStmt publisher q quote ref reg repository resp respStmt revisionDesc row rs seg sense sourceDesc standOff supplied surplus table taxonomy teiHeader term text textLang title titleStmt]
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
StatusOptional
Datatype1–∞ 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.

stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text.
StatusOptional
Datatypeteidata.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(rendition reference) points to a description of the rendering or presentation used for this element in the source text.
StatusOptional
Datatype1–∞ 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.

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.

Note

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

3.15. 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 12.3.2.2. Hand, Responsibility, and Certainty Attributes 18.3. Spans and Interpretations 14.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.global[TEI ab abbr addrLine address analytic anchor author availability back bibl biblScope biblStruct body catDesc category cell change charDecl classDecl closer date desc distinct div editorialDecl email encodingDesc entry expan figDesc figure fileDesc foreign form front g glyph graphic handDesc handNote head hi history idno imprint item l lb lg licence list listBibl listChange locus metDecl metSym milestone monogr msContents msDesc msIdentifier msItem name note notesStmt num opener orgName orig origin p pb persName physDesc placeName projectDesc ptr pubPlace publicationStmt publisher q quote ref reg repository resp respStmt revisionDesc row rs seg sense sourceDesc standOff supplied surplus table taxonomy teiHeader term text textLang title titleStmt]
Attributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
StatusOptional
Datatypeteidata.probCert
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
StatusOptional
Datatype1–∞ 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.16. 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]
Moduletei
Membersatt.global[TEI ab abbr addrLine address analytic anchor author availability back bibl biblScope biblStruct body catDesc category cell change charDecl classDecl closer date desc distinct div editorialDecl email encodingDesc entry expan figDesc figure fileDesc foreign form front g glyph graphic handDesc handNote head hi history idno imprint item l lb lg licence list listBibl listChange locus metDecl metSym milestone monogr msContents msDesc msIdentifier msItem name note notesStmt num opener orgName orig origin p pb persName physDesc placeName projectDesc ptr pubPlace publicationStmt publisher q quote ref reg repository resp respStmt revisionDesc row rs seg sense sourceDesc standOff supplied surplus table taxonomy teiHeader term text textLang title titleStmt]
Attributes
sourcespecifies the source from which some aspect of this element is drawn.
StatusOptional
Datatype1–∞ 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.17. att.handFeatures

att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [12.3.2.1. Document Hands]
Moduletei
MembershandNote
Attributes
scribegives a name or other identifier for the scribe believed to be responsible for this hand.
StatusOptional
Datatypeteidata.name
scribeRefpoints to a full description of the scribe concerned, typically supplied by a <person> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
StatusOptional
Datatype1–∞ occurrences of teidata.name separated by whitespace
scriptRefpoints to a full description of the script or writing style used by this hand, typically supplied by a <scriptNote> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
mediumdescribes the tint or type of ink, e.g. brown, or other writing medium, e.g. pencil.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

These guidelines provide no semantic basis or suggested precedence when both script and scriptRef or when both scribe and scribeRef are provided. For this reason simultaneous use of either pair of attributes is not recommended for interchange unless documentation explaining the use is provided, probably in an ODD customization.

3.18. att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei
Membersatt.media[graphic] ptr ref
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
ExampleIn 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.lexicographic

att.lexicographic provides a set of attributes for specifying standard and normalized values, grammatical functions, alternate or equivalent forms, and information about composite parts. [10.2. The Structure of Dictionary Entries]
Moduledictionaries
Membersform sense
Attributes
expand(expand) gives an expanded form of information presented more concisely in the dictionary.
StatusOptional
Datatypeteidata.text
<gramGrp>  <pos expand="noun">n</pos> </gramGrp>
split(split) gives the list of split values for a merged form.
StatusOptional
Datatypeteidata.text
value(value) gives a value which lacks any realization in the printed source text.
StatusOptional
Datatypeteidata.text
location(location) indicates an <anchor> element typically elsewhere in the document, but possibly in another document, which is the original location of this component.
StatusOptional
Datatypeteidata.pointer
mergedIn(merged into) gives a reference to another element, where the original appears as a merged form.
StatusOptional
Datatypeteidata.pointer
opt(optional) indicates whether the element is optional or not.
StatusOptional
Datatypeteidata.truthValue
Defaultfalse

3.20. att.media

att.media provides attributes for specifying display and related properties of external media.
Moduletei
Membersgraphic
Attributes
widthWhere the media are displayed, indicates the display width.
StatusOptional
Datatypeteidata.outputMeasurement
heightWhere the media are displayed, indicates the display height.
StatusOptional
Datatypeteidata.outputMeasurement
scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size.
StatusOptional
Datatypeteidata.numeric

3.21. att.metrical

att.metrical defines a set of attributes that certain elements may use to represent metrical information. [6.4. Rhyme and Metrical Analysis]
Moduleverse
Membersatt.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.
StatusRecommended
Datatypetoken
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.
StatusOptional
Datatypetoken
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.
StatusRecommended
Datatypetoken
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.22. att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 14.3.7. Names and Nyms]
Moduletei
Membersatt.personal[name orgName persName placeName] author pubPlace repository rs
Attributes
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
StatusOptional
Datatype1–∞ 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.
StatusOptional
Datatype1–∞ 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.23. att.placement

att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 12.3.1.4. Additions and Deletions]
Moduletei
Membersdiv figure head note
Attributes
placespecifies where this item is placed.
StatusRecommended
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
top
at the top of the page
bottom
at the foot of the page
margin
in the margin (left, right, or both)
opposite
on the opposite, i.e. facing, page
overleaf
on the other side of the leaf
above
above the line
right
to the right, e.g. to the right of a vertical line of text, or to the right of a figure
below
below the line
left
to the left, e.g. to the left of a vertical line of text, or to the left of a figure
end
at the end of e.g. chapter or volume.
inline
within the body of the text.
inspace
in a predefined space, for example left by an earlier scribe.
<add place="margin">[An addition written in the margin]</add> <add place="bottom opposite">[An addition written at the foot of the current page and also on the facing page]</add>
<note place="bottom">Ibid, p.7</note>

3.24. att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei
Membersatt.dimensions[date supplied surplus] num
Attributes
atLeastgives a minimum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
atMostgives a maximum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
StatusOptional
Datatypeteidata.numeric
maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
StatusOptional
Datatypeteidata.numeric
confidencespecifies 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.
StatusOptional
Datatypeteidata.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.25. att.scope

att.scope provides attributes to describe, in general terms, the scope of an element’s application.
Moduletei
Membersatt.handFeatures[handNote]
Attributes
scopeindicates the scope of application of the element
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
sole
only this particular feature is used throughout the document
major
this feature is used through most of the document
minor
this feature is used occasionally through the document
<langUsage>  <language ident="en"   scope="major"/>  <language ident="es"   scope="minor"/>  <language ident="x-ww"   scope="minor">An invented language the children call <name>Wikwah</name>.</language> </langUsage>
<handNote scope="sole">  <p>Written in insular phase II half-uncial with    interlinear Old English gloss in an Anglo-Saxon    pointed minuscule.</p> </handNote>

3.26. att.sortable

att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [10.1. Dictionary Body and Overall Structure]
Moduletei
Membersbibl biblStruct entry idno item list listBibl listChange msDesc term
Attributes
sortKeysupplies the sort key for this element in an index, list or group which contains it.
StatusOptional
Datatypeteidata.word
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES">  <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura was David's own first cousin.
Note

The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

3.27. 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]
Moduletei
Membersab closer div figure head hi note opener p seg text
Attributes
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
StatusOptional
Datatypeteidata.pointer

4. Macros

4.1. macro.abContent

macro.abContent (anonymous block content) defines the content of anonymous block elements. [1.3. The TEI Class System]
Moduletei
Used by
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.paraPart"/>
  <elementRef key="ab"/>
 </alternate>
</content>
    
Declaration
tei_macro.abContent = ( text | tei_model.paraPart | tei_ab )*

4.2. 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]
Moduletei
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.3. macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Moduletei
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.4. macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Moduletei
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.5. 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]
Moduletei
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.6. 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]
Moduletei
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
   )*

5. Datatypes

5.1. teidata.certainty

teidata.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei
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.
Moduletei
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.
Moduletei
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.
Moduletei
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.
Moduletei
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]
Moduletei
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 https://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at https://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes ‘are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags’.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. There are currently only two extensions in use. Extension T indicates that the content was transformed. For example en-t-it could be used for content in English that was translated from Italian. Extension T is described in the informational RFC 6497. Extension U can be used to embed a variety of locale attributes. It is described in the informational RFC 6067.
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.
Moduletei
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.
Moduletei
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.
Moduletei
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.
Moduletei
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.
Moduletei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?(,-?[0-9]+(\.[0-9]+)?)?)"/>
</content>
    
Declaration
tei_teidata.point =
   token
   {
      pattern = "(-?[0-9]+(\.[0-9]+)?,-?[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 or three numeric values separated by commas. The numeric values should be expressed as decimal numbers which do not 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.
Moduletei
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.
Moduletei
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.
Moduletei
Used by
Content model
<content>
 <dataRef name="double">
  <dataFacet name="minInclusive" value="0"/>
  <dataFacet name="maxInclusive" value="1"/>
 </dataRef>
</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.
Moduletei
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.
Moduletei
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.
Moduletei
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.
Moduletei
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.
Moduletei
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.
Moduletei
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 (https://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

5.21. teidata.versionNumber

teidata.versionNumber defines the range of attribute values used for version numbers.
Moduletei
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.
Moduletei
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.
Moduletei
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.
Moduletei
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.
Moduletei
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: 2026-08-12