Niklas Luhmann-Archiv: ODD-Dokumentation für die Auszeichnung von Zetteltranskriptionen

Table of contents

TEI Customization for notes used within the Niklas Luhmann-Archive. All descriptions are given in German language.

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
Contained by
textstructure: TEI
May contain
header: teiHeader
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
{
   teiatt.global.rendition.attribute.rendition,
   ( teiteiHeader, ( ( teimodel.resource+, teiTEI* ) | teiTEI+ ) )
}

1.2. <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

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

1.3. <add>

<add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
placespecifies where this item is placed.
Derived fromatt.placement
StatusRequired
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
ueber-der-zeile
Hinzufügung über der Zeile
innerhalb-der-zeile
Hinzufügung innerhalb der Zeile
unterhalb-der-zeile
Hinzufügung unterhalb der Zeile
rand_rechts
Hinzufügung am Rand rechts
rand_links
Hinzufügung am Rand links
rand
Hinzufügung am Rand
unter-dem-absatz
Hinzufügung steht unter dem Absatz, auf den sie sich bezieht
nach-dem-Absatz
Hinzufügung steht nach dem Absatz, auf den sie sich bezieht
ueber-dem-absatz
Hinzufügung steht über dem Absatz, auf den sie sich bezieht
ueberschrieben
Überschreibung
von-anderem-zettel
Hinzufügung von einem anderen Zettel
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
Derived fromatt.written
StatusRequired
Datatypeteidata.pointer
Legal values are:
#typewritten
Maschinenschriftliche Hinzufügung im Manuskript
#handwritten
Handschriftliche Hinzufügung im Manuskript
#handwritten_bleistift
Handschriftliche Hinzufügung (Bleistift) im Manuskript
#editor
Nachträgliche Hinzufügung durch die Herausgeber (Niklas Luhmann-Archiv)
Member of
Contained by
May contain
Note

In a diplomatic edition attempting to represent an original source, the <add> element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended.

In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of <add> may be appropriate, dependent on the editorial philosophy of the project.

Example
The story I am going to relate is true as to its main facts, and as to the consequences <add place="above">of these facts</add> from which this tale takes its title.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element add
{
   teiatt.cmc.attributes,
   attribute place
   {
      list
      {
         (
            "ueber-der-zeile"
          | "innerhalb-der-zeile"
          | "unterhalb-der-zeile"
          | "rand_rechts"
          | "rand_links"
          | "rand"
          | "unter-dem-absatz"
          | "nach-dem-Absatz"
          | "ueber-dem-absatz"
          | "ueberschrieben"
          | "von-anderem-zettel"
         )+
      }
   },
   attribute hand
   {
      "#typewritten" | "#handwritten" | "#handwritten_bleistift" | "#editor"
   },
   teimacro.paraContent
}

1.4. <addSpan>

<addSpan> (added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also <add>). [12.3.1.4. Additions and Deletions]
Moduletranscr
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
luhmann_wichtig
Anstreichung am Rand als besonders wichtig durch Luhmann
luhmann_fraglich
Anstreichung am Rand als fraglich durch Luhmann
Member of
Contained by
May containEmpty element
Note

Both the beginning and the end of the added material must be marked; the beginning by the <addSpan> element itself, the end by the spanTo attribute.

Example
<handNote scribe="HelgiÓlafsson"  xml:id="HEOL"/> <!-- ... --> <body>  <div> <!-- text here -->  </div>  <addSpan hand="#HEOLn="added_gathering"   spanTo="#P025"/>  <div> <!-- text of first added poem here -->  </div>  <div> <!-- text of second added poem here -->  </div>  <div> <!-- text of third added poem here -->  </div>  <div> <!-- text of fourth added poem here -->  </div>  <anchor xml:id="P025"/>  <div> <!-- more text here -->  </div> </body>
Schematron
<sch:rule context="tei:addSpan"> <sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:addSpan"> <sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element addSpan
{
   teiatt.spanning.attributes,
   attribute type { "luhmann_wichtig" | "luhmann_fraglich" }?,
   empty
}

1.5. <altIdentifier>

<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript or other object, such as a former catalogue number. [11.4. The Manuscript Identifier]
Modulemsdescription
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
file
Informationen zur Faksimiledatei (Speicherort, Dateiname)
position
Informationen zum Fundort bei Nachlassübernahme
logical_position
Inhaltliche-logische Zuordnung
luhmann
Luhmannsche Zettelnummer
editor-kennung
Von den Editoren vergebene Kennung
Contained by
msdescription: msIdentifier
May contain
core: note
header: idno
namesdates: settlement
Note

An identifying number of some kind must be supplied if known; if it is not known, this should be stated.

Example
<altIdentifier>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <idno>MS.El.26.C.9</idno> </altIdentifier>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef expand="sequenceOptional"
   key="model.placeNamePart"/>
  <elementRef key="institution"
   minOccurs="0"/>
  <elementRef key="repository"
   minOccurs="0"/>
  <elementRef key="collection"
   minOccurs="0"/>
  <elementRef key="idno"/>
  <elementRef key="note" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element altIdentifier
{
   attribute type
   {
      "file" | "position" | "logical_position" | "luhmann" | "editor-kennung"
   }?,
   (
      teisettlement?,
      teiinstitution?,
      teirepository?,
      teicollection?,
      teiidno,
      teinote?
   )
}

1.6. <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
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
luhmann_wichtig
Anstreichung am Rand als besonders wichtig durch Luhmann
luhmann_fraglich
Anstreichung am Rand als fraglich durch Luhmann
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
{
   teiatt.global.attribute.xmlid,
   teiatt.cmc.attributes,
   attribute type { "luhmann_wichtig" | "luhmann_fraglich" }?,
   empty
}

1.7. <availability>

<availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
status(status) supplies a code identifying the current availability of the text.
StatusRequired
Datatypeteidata.enumerated
Legal values are:
free
Zettelseite kann frei genutzt werden - Creative Commons Attribution-ShareAlike 4.0 International (CC BY-NC-SA 4.0)
restricted
Zettelrückseite unterliegt rechtlicher Beschränkung
Member of
Contained by
core: bibl
May contain
core: p
header: licence
Note

A consistent format should be adopted

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

1.8. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
Contained by
textstructure: text
May contain
analysis: span
figures: figure table
textstructure: 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
{
   (
      teimodel.frontPart
    | teimodel.pLike.front
    | teimodel.pLike
    | teimodel.listLike
    | teimodel.global
   )*,
   (
      (
         teimodel.div1Like,
         ( teimodel.frontPart | teimodel.div1Like | teimodel.global )*
      )
    | (
         teimodel.divLike,
         ( teimodel.frontPart | teimodel.divLike | teimodel.global )*
      )
   )?,
   (
      ( teimodel.divBottomPart, ( teimodel.divBottomPart | teimodel.global )* )?
   )
}

1.9. <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 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:
undefined
Bibliographische Angabe, nicht weiter klassifiziert
ZK_1_einzel
Bibliographische Angabe auf Notizzettel aus ZK 1
ZK_2_BG1a
Bibliographie 1 (A-Z, listenförmig) des ZK 1, Standort: ZK 2/Auszug 17
ZK_2_BG1b
Bibliographie 2 (A-Z, listenförmig) des ZK 1, Standort: ZK 2/Auszug 17
ZK_2_BG2a
Bibliographie 1 (A-Z, listenförmig) des ZK 2, Standort: ZK 2/ Auszug 17
ZK_2_BG2b
Bibliographie 2 (A-Z, listenförmig) des ZK 2, Standort: ZK 2/ Auszug 15, 16, 17
ZK_1_sammel
Bibliographie auf Sammlungszettel meist zu Beginn einer Abteilung in ZK 1, seltener am Beginn von Unterabteilungen und in der Mitte von Abteilungen (neue Dateinamenlogik)
ms-sic
Bibliographische Angabe in einem Manuskript, in Originalnotation
ms-suhrkamp
Bibliographische Angabe in einem Manuskript, für Suhrkamp optimiert
relatedItem
Für bibl-in-bibl-Schachtelung
Niklas-Luhmann-Arbeitsbibliothek
Verweis (von Luhmann) auf ein Exemplar in seiner Arbeitsbibliothek (durch Signatur, "meine Bibl" etc.) (Ziel ist der BiblDS)
Niklas-Luhmann-Werk
Verweis (von Luhmann) auf einen Manuskript-/Werkkomplex/Publikationsprojekt, nicht auf ein konkretes einzelnes Manuskript (Ziel ist die Werkbeschreibung)
Member of
Contained by
May contain
Note

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

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

1.10. <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
analysis: span
figures: figure table
msdescription: msDesc
textstructure: div
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
{
   teimodel.global*,
   ( ( teimodel.divTop, ( teimodel.global | teimodel.divTop )* )? ),
   ( ( teimodel.divGenLike, ( teimodel.global | teimodel.divGenLike )* )? ),
   (
      ( ( teimodel.divLike, ( teimodel.global | teimodel.divGenLike )* )+ )
    | ( ( teimodel.div1Like, ( teimodel.global | teimodel.divGenLike )* )+ )
    | (
         ( ( ( schemaSpec | teimodel.common ), teimodel.global* )+ ),
         (
            (
               ( teimodel.divLike, ( teimodel.global | teimodel.divGenLike )* )+
            )
          | (
               (
                  teimodel.div1Like,
                  ( teimodel.global | teimodel.divGenLike )*
               )+
            )
         )?
      )
   ),
   ( ( teimodel.divBottom, teimodel.global* )* )
}

1.11. <cell>

<cell> (cell) contains one cell of a table. [15.1.1. TEI Tables]
Modulefigures
Attributes
  • att.tableDecoration
    • role
    • @rows
    • @cols
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
{
   teiatt.tableDecoration.attribute.rows,
   teiatt.tableDecoration.attribute.cols,
   teimacro.specialPara
}

1.12. <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
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
Sample values include:
base_1
XML-Rumpfdatei wurde erstellt auf Basis der Scandateien und ihrer Bennungslogik.
hasBranchVisualization
Branch-Visualisierung wurde erstellt.
ready-for-publication
Datensatz ist freigegeben für die Veröffentlichung im Portal - Verlinkung mit bibliographischem Bestand ist erfolgt.
hasCorrectedImage
Für diese Zettelseite existiert ein weiteres Digitalisat, das aufgrund der schlechten Lesbarkeit des Originals für die Portalansicht erstellt wurde.
Contained by
header: revisionDesc
May contain
Note

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

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

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

1.13. <charDecl>

<charDecl> (character declarations) provides information about nonstandard characters and glyphs. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Modulegaiji
Attributes
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>
  <elementRef key="desc" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="char"/>
   <elementRef key="glyph"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element charDecl
{
   teiatt.global.attributes,
   ( teidesc?, ( char | teiglyph )+ )
}

1.14. <choice>

<choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
Modulecore
Attributes
Member of
Contained by
May contain
Note

Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

Note also that <choice> elements may self-nest.

Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 13.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

ExampleAn American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.
<p>Lastly, That, upon his solemn oath to observe all the above articles, the said man-mountain shall have a daily allowance of meat and drink sufficient for the support of <choice>   <sic>1724</sic>   <corr>1728</corr>  </choice> of our subjects, with free access to our royal person, and other marks of our <choice>   <orig>favour</orig>   <reg>favor</reg>  </choice>.</p>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="2">
  <classRef key="model.choicePart"/>
  <elementRef key="choice"/>
 </alternate>
</content>
    
Schema Declaration
element choice
{
   teiatt.cmc.attributes,
   ( teimodel.choicePart | teichoice ),
   ( teimodel.choicePart | teichoice ),
   ( teimodel.choicePart | teichoice )*
}

1.15. <collection>

<collection> (collection) contains the name of a collection of manuscripts or other objects, not necessarily located within a single repository. [11.4. The Manuscript Identifier]
Modulemsdescription
Contained by
May contain
Example
<msIdentifier>  <country>USA</country>  <region>California</region>  <settlement>San Marino</settlement>  <repository>Huntington Library</repository>  <collection>Ellesmere</collection>  <idno>El 26 C 9</idno>  <msName>The Ellesmere Chaucer</msName> </msIdentifier>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element collection { teimacro.phraseSeq.limited }

1.16. <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
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
mentioned
Datumsangabe, die auf einem Zettel erwähnt wird
Member of
Contained by
May contain
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element date
{
   teiatt.cmc.attributes,
   attribute type { "mentioned" }?,
   ( text | teimodel.gLike | teimodel.phrase | teimodel.global )*
}

1.17. <del>

<del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
renditionpoints 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
Legal values are:
#strikethrough
Durchstreichung im Manuskript
#overwritten
Maschinenschriftliche Überschreibung mit xxx
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
Derived fromatt.written
StatusRequired
Datatypeteidata.pointer
Legal values are:
#typewritten
Maschinenschriftliche Hinzufügung im Manuskript
#handwritten
Handschriftliche Hinzufügung im Manuskript
#editor
Nachträgliche Hinzufügung durch die Herausgeber (Niklas Luhmann-Archiv)
Member of
Contained by
May contain
Note

This element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.

The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the <gap> tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the <gap> element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way.

Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 22. Certainty, Precision, and Responsibility).

There is a clear distinction in the TEI between <del> and <surplus> on the one hand and <gap> or <unclear> on the other. <del> indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. <gap> or <unclear>, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 12.3.1.7. Text Omitted from or Supplied in the Transcription and 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription.

Example
<l>  <del rend="overtyped">Mein</del> Frisch <del rend="overstriketype="primary">schwebt</del> weht der Wind </l>
Example
<del rend="overstrike">  <gap quantity="5reason="illegible"   unit="character"/> </del>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element del
{
   teiatt.cmc.attributes,
   teiatt.placement.attribute.place,
   attribute rendition { list { ( "#strikethrough" | "#overwritten" )+ } },
   attribute hand { "#typewritten" | "#handwritten" | "#editor" },
   teimacro.paraContent
}

1.18. <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
Member of
Contained by
May contain
figures: table
header: idno
msdescription: msDesc
namesdates: eventName settlement
character data
Note

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

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 { teiatt.cmc.attributes, teimacro.limitedContent }

1.19. <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
zettel-vorderseite
Das div-Element enthält eine Zettelvorderseite
zettel-rueckseite
Das div-Element enthält eine Zettelrueckseite
notes
[back] Gruppiert Anmerkungen in Manuskripten und Editorische Anmerkungen zu Zetteln
navigation
[back] Gruppiert Verweise zur Einbettung des Zettels in den Zettelkasten
index
[back] Gruppiert ergänzende Verschlagwortung auf Zetteln
farbkarte
div-Element einer Farbkarte
subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
N_NB_Notiz-Verweiszettel
Kombinierter Notiz- und Verweiszettel - im normalen Bestand des ZK
N_NB
Notizzettel - im normalen Bestand des ZK
N_NB_Verweiszettel
Verweiszettel - im normalen Bestand des ZK
N_NB_Literaturzettel
Literaturzettel - im normalen Bestand des ZK
N_NB_Verweis-Literaturzettel
Kombinierter Verweis- und Literaturzettel - im normalen Bestand des ZK
N_EW
Notizzettel - Zettel mit Wortlisten und Seminarideen (Abt. im ZKII/a17)
N_VS
Notizzettel - in der Sammlung VS
N_PR2
Notizzettel: Zettel des Personenregisters des ZKII (Abt. im ZKII/a17)
B_NB
Bibliographiezettel - im normalen Bestand des ZK
B_BG1a
Bibliographie 1 (A-Z, listenförmig) des ZK 1, Standort: ZK 2/Auszug 17
B_BG1b
Bibliographie 2 (A-Z, listenförmig) des ZK 1, Standort: ZK 2/Auszug 17
B_BG2a
Bibliographiezettel
D_VS
Rückseitentyp: bedruckte / mit Maschine beschriebene, d.h. nichthandschriftliche Rückseiten – Zettel der VS-Sammlung (Abt. im ZKII/a17)
T_PR2
Rückseitentyp: der Text der Vorderseite wird auf der Rückseite weitergeführt (gilt insbes. für die Schlagwort- und Personenregister (s.u.), aber nicht für Exzerpte) – Zettel des Personenregisters des ZKII (Abt. im ZKII/a17)
L_PR2
Rückseitentyp: Leere Rückseite – Zettel des Personenregisters des ZKII (Abt. im ZKII/a17)
D_BG1a
Rückseitentyp: bedruckte / mit Maschine beschriebene, d.h. nichthandschriftliche Rückseiten – Bibliographie 1 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
N_BG1a
Veraltet Notizzettel: Bibliographie 1 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
N_BG2a
Bibliographiezettel: Bibliographie, Standort: ZK II/Auszug 15, 16, 17
R_BG1a
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind, Bibliographie 1 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
R_BG2a
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind
X_BG2a
Exzerptzettel: Vorderseite zeigt (bibliographische Kurzangabe und) ein Exzerpt – Zettel in Bibliographie 1 (Einzeleinträge incl. Exzerpte, Scha-She (a15), L-Sch (a16), She-Zwi (a17)) des ZK II, Standort: ZK II/Auszug 15-17
N_TU1
Registerzettel: Notizzettel, Zettel mit Themenübersicht des ZKI (Abt. im ZKII/a17)
U_BG1a
Bibliographiezettel: RB+unecht: unechte bibliographischen Angaben, Bibliographie 1 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
U_BG2a
Bibliographiezettel: Vorderseite zeigt eine bibliographische Angabe, die vom Normalmodus abweicht (mehrere Angaben auf einem Zettel), Zettel in Bibliographie 1 (Einzeleinträge incl. Exzerpte, Scha-She (a15), L-Sch (a16), She-Zwi (a17)) des ZK II, Standort: ZK II/Auszug 15-17
D_TU1
Rückseitentyp: bedruckte / mit Maschine beschriebene, d.h. nichthandschriftliche Rückseiten – Zettel mit Themenübersicht des ZKI (Abt. im ZKII/a17)
L_BG1b
Rückseitentyp: Leere Rückseite – Bibliographie 2 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
L_BG2a
Undefinierter Zettel
N_BG1b
Bibliographiezettel: Notizzettel – Bibliographie 2 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
T_BG1b
Bibliographiezettel: der Text der Vorderseite wird auf der Rückseite weitergeführt (gilt insbes. für die Schlagwort- und Personenregister (s.u.), aber nicht für Exzerpte) – Bibliographie 2 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
R_TU1
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind – Zettel mit Themenübersicht des ZKI (Abt. im ZKII/a17)
X_BG1b
Exzerptzettel: Bibliographie 2 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
N_SW1
Registerzettel: Notizzettel – Zettel des Schlagwortregisters des ZKI (Abt. im ZKII/a17)
T_SW1
Registerzettel: der Text der Vorderseite wird auf der Rückseite weitergeführt (gilt insbes. für die Schlagwort- und Personenregister (s.u.), aber nicht für Exzerpte) – Zettel des Schlagwortregisters des ZKI (Abt. im ZKII/a17)
L_SW1
Rückseitentyp: Leere Rückseite – Zettel des Schlagwortregisters des ZKI (Abt. im ZKII/a17)
N_SW2a
Notizzettel - Zettel des 1. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
T_SW2a
Rückseitentyp: der Text der Vorderseite wird auf der Rückseite weitergeführt (gilt insbes. für die Schlagwort- und Personenregister (s.u.) - Zettel des 1. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
L_SW2a
Rückseitentyp: leere Rückseiten - Zettel des 1. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
R_SW2a
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind - Zettel des 1. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
N_SW2b
Notizzettel - Zettel des 2. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
T_SW2b
Rückseitentyp: der Text der Vorderseite wird auf der Rückseite weitergeführt (gilt insbes. für die Schlagwort- und Personenregister (s.u.) - Zettel des 2. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
L_SW2b
Rückseitentyp: leere Rückseiten - Zettel des 2. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
R_SW2b
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind - Zettel des 2. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
N_SW2c
Notizzettel - Zettel des 3. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
T_SW2c
Rückseitentyp: der Text der Vorderseite wird auf der Rückseite weitergeführt (gilt insbes. für die Schlagwort- und Personenregister (s.u.) - Zettel des 3. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
L_SW2c
Rückseitentyp: leere Rückseiten - Zettel des 3. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
R_SW2c
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind - Zettel des 3. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
N_SW2d
Notizzettel - Zettel des 4. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
T_SW2d
Rückseitentyp: der Text der Vorderseite wird auf der Rückseite weitergeführt (gilt insbes. für die Schlagwort- und Personenregister (s.u.) - Zettel des 4. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
L_SW2d
Rückseitentyp: leere Rückseiten - Zettel des 4. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
R_SW2d
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind - Zettel des 4. Schlagwortregisters des ZKII (Abt. im ZKII/a17)
R_BG1b
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind – Bibliographie 2 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
N_TU1
Registerzettel: Notizzettel – Zettel mit Themenübersicht des ZKI (Abt. im ZKII/a17)
L_BG1a
Undefinierter Zettel: Leere Rückseite – Bibliographie 1 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
T_BG1a
Bibliographiezettel: der Text der Vorderseite wird auf der Rückseite weitergeführt (gilt insbes. für die Schlagwort- und Personenregister (s.u.), aber nicht für Exzerpte) – Bibliographie 1 (A-Z, listenförmig) des ZK I, Standort: ZK II/Auszug 17
V_NB
Rückseitentyp: auf diesen Rückseite wurde von der Vorderseite verweisen (meist mit einem roten "R") - im normalen Bestand des ZK
L_NB
Rückseitentyp: leere Rückseiten - im normalen Bestand des ZK
L_EW
Rückseitentyp: leere Rückseiten - Zettel mit Wortlisten und Seminarideen (Abt. im ZKII/a17)
L_VS
Rückseitentyp: leere Rückseiten
S_NB
Rückseitentyp: Kombination zweier Merkmale: RX und RV - im normalen Bestand des ZK
T_NB
Rückseitentyp: der Text der Vorderseite wird auf der Rückseite weitergeführt (gilt insbes. für die Schlagwort- und Personenregister (s.u.) - im normalen Bestand des ZK
T_EW
Rückseitentyp: der Text der Vorderseite wird auf der Rückseite weitergeführt (gilt insbes. für die Schlagwort- und Personenregister (s.u.) - Zettel mit Wortlisten und Seminarideen (Abt. im ZKII/a17)
D_NB
Rückseitentyp: bedruckte / mit Maschine beschriebene, d.h. nichthandschriftliche Rückseiten - im normalen Bestand des ZK
R_NB
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind - im normalen Bestand des ZK
R_VS
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind – Zettel der VS-Sammlung (Abt. im ZKII/a17)
R_EW
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind – Zettel mit Wortlisten und Seminarideen (Abt. im ZKII/a17)
D_EW
Rückseitentyp: bedruckte / mit Maschine beschriebene, d.h. nichthandschriftliche Rückseiten – Zettel mit Wortlisten und Seminarideen (Abt. im ZKII/a17)
O_NB
Rückseitentyp: Rückseite eines Notizzettels zeigt ein Exzerpt noch ohne Zuordnung - im normalen Bestand des ZK
X_NB
Rückseitentyp: Exzerpt - im normalen Bestand des ZK
P_NB
Rückseitentyp: RB+RX: Rückseite zeigt bibliographische Angabe und ein Exzerpt - im normalen Bestand des ZK
U_NB
Rückseitentyp: RB+unecht: unechte bibliographischen Angaben - im normalen Bestand des ZK
W_NB
Rückseitentyp: Kombination zweier Merkmale: RT und RV - im normalen Bestand des ZK
E_NB
Rückseitentyp: bei Notizen zu einem rechtswissenschaftlichen Projekt mit der Nummer E/ - im normalen Bestand des ZK
F_NB
Rückseitentyp: Zettel in rekonstruierter Sammlung E / Notiz nach Verweis von der Vorderseite / Diese Notiz befindet sich auf der Rückseite eines Notizzettels im normalen Bestand
G_NB
Rückseitentyp: Zettel in Bibliographie (vom NL-Archiv rekonstruiert) / Notiz nach Verweis von der Vorderseite/ Dieses Exzerpt befindet sich auf der Rückseite eines Notizzettels im normalen Bestand
Z_NB
Rückseitentyp: Rückseite zeigt vorderseitentypischen Inhalt (Einzelfall? Bisher nur I01-47-082_17-1e2_17-1e_RZ) - im normalen Bestand des ZK
A_NB
Rückseitentyp: Rückseite zeigt RV+RB - im normalen Bestand des ZK
Q_NB
Bibliographiezettel / Exzerptzettel: RU+RX: Rückseite zeigt unechte bibliographische Angabe und ein Exzerpt – Notizzettel im normalen Bestand des ZK
Y_NB
Bibliographiezettel: Notizzettel – Notizzettel im normalen Bestand des ZK
V_PE
Notizzettel: Zettel mit Publikationsentwürfen (Abt. im ZKII/a17)
N_PE
Notizzettel - Zettel mit Publikationsentwürfen (Abt. im ZKII/a17)
L_PE
Rückseitentyp: leere Rückseiten - Zettel mit Publikationsentwürfen (Abt. im ZKII/a17)
D_PE
Rückseitentyp: Zettel mit Publikationsentwürfen (Abt. im ZKII/a17)
Z_PE
Rückseitentyp: Rückseite zeigt einen Publikationsplan aus der Abteilung PE in Auszug 17 (dh ehemals Vorderseite in dieser Abteilung, von NL aber herausgenommen und die ehemalige Rückseite als Vorderseite im NB verwendet) - Zettel mit Publikationsentwürfen (Abt. im ZKII/a17)
D_BG2a
Undefinierter Zettel
R_PE
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind (und ohne Bezug zur Vorderseite) - Zettel mit Publikationsentwürfen (Abt. im ZKII/a17)
U_VS
Bibliographiezettel: RB+unecht: unechte bibliographischen Angaben – Zettel der VS-Sammlung (Abt. im ZKII/a17)
T_VS
Notizzettel: Zettel der VS-Sammlung (Abt. im ZKII/a17)
none
z.B. bei Farbkarten
V_NB_Literaturzettel
Rückseitentyp: Literaturzettel - im normalen Bestand des ZK
V_NB_Verweiszettel
Rückseitentyp: Verweiszettel - im normalen Bestand des ZK
V_NB_Notiz-Verweiszettel
Rückseitentyp: Kombinierter Notiz- und Verweiszettel - im normalen Bestand des ZK
V_NB_Verweis-Literaturzettel
Rückseitentyp: Kombinierter Verweis- und Literaturzettel - im normalen Bestand des ZK
TODO
Zettelinhalt sollte weiter klassifiziert werden
B_BG2b
Bibliographiezettel
N_BG2b
Bibliographiezettel Zettel in Bibliographie 2 (Einzeleinträge incl. Exzerpte, A-D (a18), E-K (a19), A-Z (a20) in einzelnen Pappkästen, Standort: ZK II/Auszug 18-20)
R_BG2b
Rückseitentyp: bei handschriftlichen Notizen, die nicht den vorgenannten Punkten zuzuordnen sind
X_BG2b
Exzerptzettel: Rückseite zeigt ein Exzerpt
U_BG2b
Bibliographiezettel
L_BG2b
Undefinierter Zettel
D_BG2b
Undefinierter Zettel
Member of
Contained by
textstructure: back body div
May contain
analysis: span
figures: figure table
msdescription: msDesc
textstructure: div
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 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
{
   teiatt.global.attribute.xmlid,
   teiatt.placement.attributes,
   attribute type
   {
      "zettel-vorderseite"
    | "zettel-rueckseite"
    | "notes"
    | "navigation"
    | "index"
    | "farbkarte"
   }?,
   attribute subtype
   {
      "N_NB_Notiz-Verweiszettel"
    | "N_NB"
    | "N_NB_Verweiszettel"
    | "N_NB_Literaturzettel"
    | "N_NB_Verweis-Literaturzettel"
    | "N_EW"
    | "N_VS"
    | "N_PR2"
    | "B_NB"
    | "B_BG1a"
    | "B_BG1b"
    | "B_BG2a"
    | "D_VS"
    | "T_PR2"
    | "L_PR2"
    | "D_BG1a"
    | "N_BG1a"
    | "N_BG2a"
    | "R_BG1a"
    | "R_BG2a"
    | "X_BG2a"
    | "N_TU1"
    | "U_BG1a"
    | "U_BG2a"
    | "D_TU1"
    | "L_BG1b"
    | "L_BG2a"
    | "N_BG1b"
    | "T_BG1b"
    | "R_TU1"
    | "X_BG1b"
    | "N_SW1"
    | "T_SW1"
    | "L_SW1"
    | "N_SW2a"
    | "T_SW2a"
    | "L_SW2a"
    | "R_SW2a"
    | "N_SW2b"
    | "T_SW2b"
    | "L_SW2b"
    | "R_SW2b"
    | "N_SW2c"
    | "T_SW2c"
    | "L_SW2c"
    | "R_SW2c"
    | "N_SW2d"
    | "T_SW2d"
    | "L_SW2d"
    | "R_SW2d"
    | "R_BG1b"
    | "N_TU1"
    | "L_BG1a"
    | "T_BG1a"
    | "V_NB"
    | "L_NB"
    | "L_EW"
    | "L_VS"
    | "S_NB"
    | "T_NB"
    | "T_EW"
    | "D_NB"
    | "R_NB"
    | "R_VS"
    | "R_EW"
    | "D_EW"
    | "O_NB"
    | "X_NB"
    | "P_NB"
    | "U_NB"
    | "W_NB"
    | "E_NB"
    | "F_NB"
    | "G_NB"
    | "Z_NB"
    | "A_NB"
    | "Q_NB"
    | "Y_NB"
    | "V_PE"
    | "N_PE"
    | "L_PE"
    | "D_PE"
    | "Z_PE"
    | "D_BG2a"
    | "R_PE"
    | "U_VS"
    | "T_VS"
    | "none"
    | "V_NB_Literaturzettel"
    | "V_NB_Verweiszettel"
    | "V_NB_Notiz-Verweiszettel"
    | "V_NB_Verweis-Literaturzettel"
    | "TODO"
    | "B_BG2b"
    | "N_BG2b"
    | "R_BG2b"
    | "X_BG2b"
    | "U_BG2b"
    | "L_BG2b"
    | "D_BG2b"
   }?,
   (
      ( teimodel.divTop | teimodel.global )*,
      (
         (
            (
               (
                  (
                     ( teimodel.divLike | teimodel.divGenLike ),
                     teimodel.global*
                  )+
               )
             | (
                  ( ( ( schemaSpec | teimodel.common ), teimodel.global* )+ ),
                  (
                     (
                        ( teimodel.divLike | teimodel.divGenLike ),
                        teimodel.global*
                     )*
                  )
               )
            ),
            ( ( teimodel.divBottom, teimodel.global* )* )
         )?
      )
   )
}

1.20. <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
Example
<editorialDecl>  <normalization>   <p>All words converted to Modern American spelling using      Websters 9th Collegiate dictionary   </p>  </normalization>  <quotation marks="all">   <p>All opening quotation marks converted to “ all closing      quotation marks converted to &amp;cdq;.</p>  </quotation> </editorialDecl>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.pLike"/>
  <classRef key="model.editorialDeclPart"/>
 </alternate>
</content>
    
Schema Declaration
element editorialDecl { ( teimodel.pLike | teimodel.editorialDeclPart )+ }

1.21. <ellipsis>

<ellipsis> (deliberately marked omission) indicates a purposeful marking in the source document signalling that content has been omitted, and may also supply or describe the omitted content. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
Contained by
May contain
core: desc
transcr: metamark
Note

Unlike <gap>, which indicates content that the encoder cannot or chooses not to represent, <ellipsis> indicates a passage explicitly signalled in the source document as absent. The <ellipsis> element is not appropriate for every use of ellipsis points, such as when they indicate that a speaker is pausing.

Example
<lg>  <l>What projects men make—what queer turns they take,</l>  <l>Since <emph>steam</emph> has improved our condition;</l>  <l>They never are still, but must cure or must kill</l>  <l>With steam physic or steam ammunition.</l>  <l>But a short time ago, to a quack you would go,</l>  <l>To steam a fat man to a thinner;</l>  <l>Now changed from all that, if you wish to get <emph>fat</emph>,</l>  <l>Come to Barton’s and eat a <emph>steam dinner!</emph>  </l>  <l>Oh dear! think of a scheme, odd though it seem—</l>  <l>I’m sure ’twill succeed if you make it by steam.</l> </lg> <lg>  <l>You may sleep, you may dream, you may travel by steam,</l>  <l>For the outcry is still to go faster;</l>  <l>And what does it reck, should you e’en break your neck,</l>  <l>If ’tis <emph>steam</emph> that brings on the disaster?</l>  <ellipsis resp="#ChambersEdnbrghJrnl1880">   <metamark function="multilineEllipsis"> * * * * </metamark>   <desc resp="#teiProjectEditor2021">The printer omits four lines here,      skipping the second half of the second octave, before the refrain.</desc>  </ellipsis>  <l>Oh dear! think of a scheme, odd though it seem—</l>  <l>I’m sure ’twill succeed if you make it by steam.</l> </lg>
Example
<lg>  <l>You think you’ve lost your love </l>  <l>Well, I saw her yesterday </l>  <l>It’s you she's thinking of </l>  <l>And she told me what to say</l> </lg> <lg xml:id="chorus">  <label>[Refrain]</label>  <l>She says she loves you </l>  <l>And you know that can’t be bad </l>  <l>Yes, she loves you </l>  <l>And you know you should be glad</l> </lg> <lg>  <l>She said you hurt her so </l>  <l>She almost lost her mind </l>  <l>But now she said she knows </l>  <l>You’re not the hurting kind</l> </lg> <ellipsis>  <metamark>******</metamark>  <supplied copyOf="#chorus"/> </ellipsis>
Content model
<content>
 <sequence>
  <elementRef key="metamark"/>
  <classRef key="model.descLike"
   maxOccurs="1" minOccurs="0"/>
  <elementRef key="supplied" maxOccurs="1"
   minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element ellipsis
{
   teiatt.global.attributes,
   teiatt.dimensions.attributes,
   teiatt.timed.attributes,
   ( teimetamark, teimodel.descLike?, supplied? )
}

1.22. <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
Member of
Contained by
header: teiHeader
May contain
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
{
   teiatt.global.attribute.xmlid,
   teiatt.global.attribute.xmllang,
   teiatt.global.attribute.xmlbase,
   ( teimodel.encodingDescPart | teimodel.pLike )+
}

1.23. <eventName>

<eventName> (name of an event) contains a proper noun or noun phrase used to refer to an event. [14.2.4. Event Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<listEvent>  <event from="1939-09-01to="1945-09-02">   <eventName xml:lang="de">Zweiter Weltkrieg</eventName>   <eventName xml:lang="en">World War II</eventName>   <idno type="GND">https://d-nb.info/gnd/4079167-1</idno>   <idno type="Wikidata">https://www.wikidata.org/wiki/Q362</idno>   <event from="1939-09-01to="1939-10-06"    xml:id="UeberfallAufPolen">    <eventName xml:lang="de">Überfall auf Polen</eventName>    <eventName xml:lang="en">Invasion of Poland</eventName>    <idno type="GND">https://d-nb.info/gnd/4175002-0</idno>    <idno type="LOC">https://id.loc.gov/authorities/sh85148341</idno>    <listPlace type="affected">     <place>      <placeName xml:lang="pl">Gdańsk</placeName>      <location>       <geo>54.350556 18.652778</geo>      </location>     </place>    </listPlace>   </event>   <event from="1941-06-22to="1945-05-09">    <eventName xml:lang="de">Deutsch-Sowjetischer Krieg</eventName>    <eventName xml:lang="ru">Великая Отечественная война</eventName>    <idno type="GND">https://d-nb.info/gnd/4076906-9</idno>    <idno type="Wikidata">https://www.wikidata.org/wiki/Q189266</idno>   </event>  </event> </listEvent>
Example
<p>On <date when="1719-03-19">Monday</date>, <rs type="person">she</rs> was writing about the <eventName ref="#SecondDefPrague">1618 Defenestration of Prague</eventName> which initiated the <rs ref="#ThirtyYearsWartype="event">long war</rs>.</p>
Example
<event from="2019-09-16to="2019-09-20"  xml:id="tei2019graz">  <eventName type="full">TEI 2019: What is text, really? TEI and beyond</eventName>  <eventName type="short">TEI 2019</eventName>  <note> The abstract leading to the <gi>eventName</gi> element is available at <ref target="https://gams.uni-graz.at/o:tei2019.141">https://gams.uni-graz.at/o:tei2019.141</ref>.    Other related documents are available through <ref target="https://gams.uni-graz.at/tei2019">https://gams.uni-graz.at/tei2019</ref>, as well as in the  <ref target="https://zenodo.org/communities/tei2019">TEI 2019 Zenodo community</ref>.  </note>  <listPerson type="LocalOrganizers">   <person>    <persName>     <surname>Raunig</surname>     <forename>Elisabeth</forename>    </persName>   </person>   <person>    <persName>     <surname>Scholger</surname>     <forename>Martina</forename>    </persName>   </person>   <person>    <persName>     <surname>Scholger</surname>     <forename>Walter</forename>    </persName>   </person>   <person>    <persName>     <surname>Steiner</surname>     <forename>Elisabeth</forename>    </persName>   </person>   <person>    <persName>     <surname>Vogeler</surname>     <forename>Georg</forename>    </persName>   </person>  </listPerson>  <place xml:lang="de">   <placeName>Universität Graz</placeName>   <location>    <address>     <addrLine>ReSoWi Gebäude</addrLine>     <addrLine>Universitätsstraße 15</addrLine>     <postCode>8010</postCode>     <settlement>Graz</settlement>     <country>Österreich</country>    </address>    <geo>15.451651587656 47.078215112534</geo>   </location>  </place>  <listRelation>   <relation active="#tei2019graz"    name="P31_is_instance_ofpassive="#AnnualTEIConference"    ref="https://www.wikidata.org/wiki/Property:P31type="CRM"/>  </listRelation> </event>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element eventName
{
   teiatt.global.attributes,
   teiatt.datable.attributes,
   teiatt.editLike.attributes,
   teiatt.personal.attributes,
   teiatt.typed.attributes,
   teimacro.phraseSeq
}

1.24. <expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

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

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

1.25. <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
Contained by
figures: figure
May contain
figures: table
header: idno
msdescription: msDesc
namesdates: eventName settlement
character data
Note

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

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

1.26. <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
Member of
Contained by
May contain
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
{
   teiatt.cmc.attributes,
   teiatt.typed.attribute.type,
   (
      teimodel.headLike
    | teimodel.common
    | teifigDesc
    | teimodel.graphicLike
    | teimodel.global
    | teimodel.divBottom
   )*
}

1.27. <fileDesc>

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

1.28. <filiation>

<filiation> (filiation) contains information concerning the manuscript or other object's filiation, i.e. its relationship to other surviving manuscripts or other objects of the same text or contents, its protographs, antigraphs and apographs. [11.6.1. The msItem and msItemStruct Elements]
Modulemsdescription
Attributes
Member of
Contained by
msdescription: msItem
May contain
Example
<msContents>  <msItem>   <title>Beljakovski sbornik</title>   <filiation type="protograph">Bulgarian</filiation>   <filiation type="antigraph">Middle Bulgarian</filiation>   <filiation type="apograph">    <ref target="#DN17">Dujchev N 17</ref>   </filiation>  </msItem> </msContents> <!-- ... --> <msDesc xml:id="DN17">  <msIdentifier>   <settlement>Faraway</settlement>  </msIdentifier> <!-- ... --> </msDesc>
In this example, the reference to ‘Dujchev N17’ includes a link to some other manuscript description which has the identifier DN17.
Example
<msItem>  <title>Guan-ben</title>  <filiation>   <p>The "Guan-ben" was widely current among mathematicians in the      Qing dynasty, and "Zhao Qimei version" was also read. It is      therefore difficult to know the correct filiation path to follow.      The study of this era is much indebted to Li Di. We explain the      outline of his conclusion here. Kong Guangsen      (1752-1786)(17) was from the same town as Dai Zhen, so he obtained      "Guan-ben" from him and studied it(18). Li Huang (d. 1811)      (19) took part in editing Si Ku Quan Shu, so he must have had      "Guan-ben". Then Zhang Dunren (1754-1834) obtained this version,      and studied "Da Yan Zong Shu Shu" (The General Dayan      Computation). He wrote Jiu Yi Suan Shu (Mathematics      Searching for One, 1803) based on this version of Shu Xue Jiu      Zhang (20).</p>   <p>One of the most important persons in restoring our knowledge      concerning the filiation of these books was Li Rui (1768(21)      -1817)(see his biography). ... only two volumes remain of this      manuscript, as far as chapter 6 (chapter 3 part 2) p.13, that is,      question 2 of "Huan Tian San Ji" (square of three loops),      which later has been lost.</p>  </filiation> </msItem> <!--http://www2.nkfust.edu.tw/~jochi/ed1.htm-->
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element filiation { teiatt.typed.attribute.type, teimacro.specialPara }

1.29. <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) Kürzelvergabe folgt IANA/ISO 639 2-letter language code.
Derived fromatt.global
StatusRequired
Datatypeteidata.language
Legal values are:
de
Deutsch
en
Englisch
es
Spanisch
fr
Französisch
el
Modern Greek (1453-)
he
Hebrew
it
Italienisch
la
Latein
grc
Griechisch in bei Suhrkamp gedruckten Luhmann-Manuskript - sollte perspektivisch zu "el" standardisiert werden
Member of
Contained by
May contain
Note

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

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

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

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

1.30. <fw>

<fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [12.6. Headers, Footers, and Similar Matter]
Moduletranscr
Attributes
typeclassifies the material encoded according to some useful typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
header
a running title at the top of the page
footer
a running title at the bottom of the page
pageNum
(page number) a page number or foliation symbol
lineNum
(line number) a line number, either of prose or poetry
sig
(signature) a signature or gathering symbol
catch
(catchword) a catch-word
Member of
Contained by
May contain
Note

Where running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The <fw> element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance.

Example
<fw place="bottomtype="sig">C3</fw>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element fw { attribute type { text }?, teimacro.phraseSeq }

1.31. <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.
StatusOptional
Datatypeteidata.pointer
Legal values are:
#hellip
Auslassungspunkte - horizontal ellipsis
#nl_klammer_links-oeffnend
U+300C LEFT CORNER BRACKET
#nl_klammer_rechts-schliessend
U+300D RIGHT CORNER BRACKET
#malzeichen
Malzeichen/Mittelpunkt: Luhmann setzt dies in Formeln (https://de.wikipedia.org/wiki/Malzeichen)
#provable
Logiksymbol: provable: Luhmann setzt dies in Formeln (https://en.wikipedia.org/wiki/List_of_logic_symbols)
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
   {
      "#hellip"
    | "#nl_klammer_links-oeffnend"
    | "#nl_klammer_rechts-schliessend"
    | "#malzeichen"
    | "#provable"
   }?,
   text
}

1.32. <gap>

<gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
Contained by
May contain
core: desc
Note

The <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 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.

The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion.

Example
<gap quantity="4reason="illegible"  unit="chars"/>
Example
<gap quantity="1reason="sampling"  unit="essay"/>
Example
<del>  <gap atLeast="4atMost="8"   reason="illegibleunit="chars"/> </del>
Example
<gap extent="several linesreason="lost"/>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element gap
{
   teiatt.cmc.attributes,
   ( teimodel.descLike | teimodel.certLike )*
}

1.33. <gender>

<gender> (gender) specifies the gender identity of a person, persona, or character. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
valuesupplies a coded value for gender identity.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

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

Contained by
May contain
Note

As with other culturally-constructed traits such as age and sex, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail.

Example
<gender value="W">woman</gender>
Example
<gender value="NB">non-binary</gender>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element gender
{
   teiatt.global.attributes,
   teiatt.datable.attributes,
   teiatt.editLike.attributes,
   teiatt.typed.attributes,
   attribute value { list { + } }?,
   teimacro.phraseSeq
}

1.34. <glyph>

<glyph> (character glyph) provides descriptive information about a character glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs]
Modulegaiji
Attributes
Contained by
gaiji: charDecl
May contain
figures: figure
gaiji: mapping
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
{
   teiatt.global.attribute.xmlid,
   (
      unicodeProp
    | unihanProp
    | localProp
    | teimapping
    | teifigure
    | teimodel.graphicLike
    | teimodel.noteLike
    | teimodel.descLike
   )*
}

1.35. <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
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
{
   teiatt.cmc.attributes,
   teiatt.resourced.attributes,
   teiatt.typed.attributes,
   teimodel.descLike*
}

1.36. <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
Member of
Contained by
core: list
figures: figure table
msdescription: msDesc msPart
textstructure: back body div
May contain
Note

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

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
{
   teiatt.cmc.attributes,
   (
      text
    | lg
    | teimodel.gLike
    | teimodel.phrase
    | teimodel.inter
    | teimodel.lLike
    | teimodel.global
   )*
}

1.37. <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
renditionpoints 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
Legal values are:
#u
Unterstrichen (in der Farbe des Textes)
#u_geschlaengelt
Geschlängelt unterstrichen (in der Farbe des Textes)
#red
Rote Schriftfarbe
#green
Grüne Schriftfarbe
#blue
Blaue Schriftfarbe
#bleistift
Mit Bleistift geschrieben
#u_red
Rot unterstrichen
#u_geschlaengelt_red
Geschlängelt rot unterstrichen
#u_green
Grün unterstrichen
#u_geschlaengelt_green
Geschlängelt grün unterstrichen
#u_blue
Blau unterstrichen
#u_geschlaengelt_blue
Geschlängelt blau unterstrichen
#u_bleistift
Mit Bleisstift unterstrichen
#u_geschlaengelt_bleistift
Geschlängelt mit Bleistift unterstrichen
#b
Gefettet
#i
Kursiv
#sup
Kleinerer Schriftgrad, hochgestellt
#sub
Kleinerer Schriftgrad, tiefgestellt
#center
Textpassage zentriert
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
{
   teiatt.cmc.attributes,
   attribute rendition
   {
      list
      {
         (
            "#u"
          | "#u_geschlaengelt"
          | "#red"
          | "#green"
          | "#blue"
          | "#bleistift"
          | "#u_red"
          | "#u_geschlaengelt_red"
          | "#u_green"
          | "#u_geschlaengelt_green"
          | "#u_blue"
          | "#u_geschlaengelt_blue"
          | "#u_bleistift"
          | "#u_geschlaengelt_bleistift"
          | "#b"
          | "#i"
          | "#sup"
          | "#sub"
          | "#center"
         )+
      }
   },
   teimacro.paraContent
}

1.38. <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:
luhmann_zettelnummer
Von Luhmann selbst vergebene Zettelnummer
orig_position
Nummer gibt die Position an, an der Zettel zum Zeitpunkt des Scannens in einem bestimmten Auszug vorgefunden wurde.
logical_position
Nummer gibt den Zettelkasten an, zu dem der Zettel logisch gehört
file_location
Enthält Informationen zum Speicherot und Namen der Zetteldatei
dir-zettelkasten
Gibt das Verzeichnis der Zettel-XML-Datei auf Zettelkastenebene an
dir-auszug
Gibt das Verzeichnis der Zettel-XML-Datei auf Auszugsebene an
dir-batch
Gibt das Verzeichnis der Zettel-XML-Datei auf Batchebene an
file-in-dir-batch
Gibt den Dateinamen der Zettel-XML-Datei im Batchverzeichnis an
corrected_physical_sequence
Korrigierte Zettelabfolge, kann abweichen beim Scannen vorgefundenen zettelabfolge.
scan_kennung
Aus Luhmannscher Zettelnummer separierte Ergänzung zur Ordnungsnummer (2. Teil)
zettelkasten
Zettelkastennummer (gibt bei Zettel-Dummies, an zu welchem Zettelkasten der Dummy gehört)
auszug
Auszugsnummer im aktuellen Zettelkasten
zettelscan-im-auszug
Positionsnummer des Scans im aktuellen Auszug
ordnungsnummer
Aus Luhmannscher Zettelnummer separierte Ordnungsnummer (1. Teil)
ergaenzung
Aus Luhmannscher Zettelnummer separierte Ergänzung zur Ordnungsnummer (2. Teil)
editor-kennung
Von den Editoren vergebene Kennung
GND
Gemeinsame Normdatei (GND)
bibliothekssignatur
Bibliothekssignatur einer externen Bibliothek; Link innerhalb als ref kodiert
subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
uni_muenster
Uni Münster
uni_bielefeld
Uni Bielefeld
verwaltungshochschule_speyer
Verwaltungshochschule Speyer
forschungsstelle_dortmund
Forschungsstelle Dortmund
fernleihe
Fernleihe
sonstige
Sonstige
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
{
   teiatt.global.attribute.n,
   teiatt.cmc.attributes,
   attribute type
   {
      "luhmann_zettelnummer"
    | "orig_position"
    | "logical_position"
    | "file_location"
    | "dir-zettelkasten"
    | "dir-auszug"
    | "dir-batch"
    | "file-in-dir-batch"
    | "corrected_physical_sequence"
    | "scan_kennung"
    | "zettelkasten"
    | "auszug"
    | "zettelscan-im-auszug"
    | "ordnungsnummer"
    | "ergaenzung"
    | "editor-kennung"
    | "GND"
    | "bibliothekssignatur"
   },
   attribute subtype
   {
      "uni_muenster"
    | "uni_bielefeld"
    | "verwaltungshochschule_speyer"
    | "forschungsstelle_dortmund"
    | "fernleihe"
    | "sonstige"
   }?,
   ( text | teimodel.gLike | teiidno )*
}

1.39. <index>

<index> (index entry) marks a location to be indexed for whatever purpose. [3.9.2. Index Entries]
Modulecore
Attributes
Member of
Contained by
May contain
core: index term
Example
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES">  <term>Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura <index indexName="PLACES">  <term>Sura</term> </index> was David's own first cousin.
Content model
<content>
 <sequence maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="term"/>
  <elementRef key="index" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element index { teiatt.cmc.attributes, ( ( teiterm, teiindex? )* ) }

1.40. <institution>

<institution> (institution) contains the name of an organization such as a university or library, with which a manuscript or other object is identified, generally its holding institution. [11.4. The Manuscript Identifier]
Modulemsdescription
Contained by
May contain
Example
<msIdentifier>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Bodleian Library</repository>  <idno>MS. Bodley 406</idno> </msIdentifier>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element institution { teimacro.phraseSeq.limited }

1.41. <item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Modulecore
Attributes
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
{
   teiatt.global.attribute.xmlid,
   teiatt.global.attribute.n,
   teiatt.global.linking.attribute.corresp,
   teiatt.global.rendition.attribute.rendition,
   teimacro.specialPara
}

1.42. <join>

<join> (join) identifies a possibly fragmented segment of text, by pointing at the possibly discontiguous elements which compose it. [17.7. Aggregation]
Modulelinking
Attributes
Member of
Contained by
May contain
core: desc
ExampleThe following example is discussed in section [[undefined SAAG]]:
<sp>  <speaker>Hughie</speaker>  <p>How does it go? <q>    <l xml:id="frog_x1">da-da-da</l>    <l xml:id="frog_l2">gets a new frog</l>    <l>...</l>   </q>  </p> </sp> <sp>  <speaker>Louie</speaker>  <p>   <q>    <l xml:id="frog_l1">When the old pond</l>    <l>...</l>   </q>  </p> </sp> <sp>  <speaker>Dewey</speaker>  <p>   <q>... <l xml:id="frog_l3">It's a new pond.</l>   </q>  </p>  <join result="lgscope="root"   target="#frog_l1 #frog_l2 #frog_l3"/> </sp>
The <join> element here identifies a linegroup (<lg>) comprising the three lines indicated by the target attribute. The value root for the scope attribute indicates that the resulting virtual element contains the three <l> elements linked to at #frog_l1 #frog_l2 #frog_l3, rather than their character data content.
ExampleIn this example, the attribute scope is specified with the value of branches to indicate that the virtual list being constructed is to be made by taking the lists indicated by the target attribute of the <join> element, discarding the <list> tags which enclose them, and combining the items contained within the lists into a single virtual list:
<p>Southern dialect (my own variety, at least) has only <list xml:id="LP1">   <item>    <s>I done gone</s>   </item>   <item>    <s>I done went</s>   </item>  </list> whereas Negro Non-Standard basilect has both these and <list xml:id="LP2">   <item>    <s>I done go</s>   </item>  </list>.</p> <p>White Southern dialect also has <list xml:id="LP3">   <item>    <s>I've done gone</s>   </item>   <item>    <s>I've done went</s>   </item>  </list> which, when they occur in Negro dialect, should probably be considered as borrowings from other varieties of English.</p> <join result="listscope="branches"  target="#LP1 #LP2 #LP3xml:id="LST1">  <desc>Sample sentences in Southern speech</desc> </join>
Schematron
<sch:rule context="tei:join"> <sch:assert test="contains( normalize-space( @target ),' ')"> You must supply at least two values for @target on <sch:name/> </sch:assert> </sch:rule>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element join
{
   teiatt.cmc.attributes,
   teiatt.pointing.attribute.target,
   ( teimodel.descLike | teimodel.certLike )*
}

1.43. <label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Modulecore
Attributes
Member of
Contained by
msdescription: filiation
textstructure: body div
transcr: metamark mod
May contain
ExampleLabels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:
<list type="glossxml:lang="enm">  <head xml:lang="en">Vocabulary</head>  <headLabel xml:lang="en">Middle English</headLabel>  <headItem xml:lang="en">New English</headItem>  <label>nu</label>  <item xml:lang="en">now</item>  <label>lhude</label>  <item xml:lang="en">loudly</item>  <label>bloweth</label>  <item xml:lang="en">blooms</item>  <label>med</label>  <item xml:lang="en">meadow</item>  <label>wude</label>  <item xml:lang="en">wood</item>  <label>awe</label>  <item xml:lang="en">ewe</item>  <label>lhouth</label>  <item xml:lang="en">lows</item>  <label>sterteth</label>  <item xml:lang="en">bounds, frisks (cf. <cit>    <ref>Chaucer, K.T.644</ref>    <quote>a courser, <term>sterting</term>as the fyr</quote>   </cit>  </item>  <label>verteth</label>  <item xml:lang="la">pedit</item>  <label>murie</label>  <item xml:lang="en">merrily</item>  <label>swik</label>  <item xml:lang="en">cease</item>  <label>naver</label>  <item xml:lang="en">never</item> </list>
ExampleLabels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:
I will add two facts, which have seldom occurred in the composition of six, or at least of five quartos. <list rend="runontype="ordered">  <label>(1)</label>  <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>  <label>(2) </label>  <item>Not a sheet has been seen by any human eyes, excepting those of the author and the    printer: the faults and the merits are exclusively my own.</item> </list>
ExampleLabels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:
<list type="gloss">  <label>March 1757.</label>  <item>I wrote some critical observations upon Plautus.</item>  <label>March 8th.</label>  <item>I wrote a long dissertation upon some lines of Virgil.</item>  <label>June.</label>  <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus      amori.</quote>  </item>  <label>August.</label>  <item>I went to Crassy, and staid two days.</item> </list>
Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.
ExampleLabels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it.
<p>[...] <lb/>&amp; n’entrer en mauuais &amp; mal-heu- <lb/>ré meſnage. Or des que le conſente- <lb/>ment des parties y eſt le mariage eſt <lb/> arreſté, quoy que de faict il ne ſoit <label place="margin">Puiſſance maritale    entre les Romains.</label>  <lb/> conſommé. Depuis la conſomma- <lb/>tion du mariage la femme eſt ſoubs <lb/> la puiſſance du mary, s’il n’eſt eſcla- <lb/>ue ou enfant de famille : car en ce <lb/> cas, la femme, qui a eſpouſé vn en- <lb/>fant de famille, eſt ſous la puiſſance [...]</p>
In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element label { teiatt.cmc.attributes, teimacro.phraseSeq }

1.44. <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.5. Speech Contents]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
inWord
Zeilentrennung in Wortmitte (line break wird bei Auflösung als "-" angezeigt)
inCompositum
Zeilentrennung direkt nach dem koppelnden Bindestrich in Kompositum - Bindestrich zusätzlich erfassen! (line break entfällt ersatzlos bei Auflösung)
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
{
   teiatt.cmc.attributes,
   attribute type { "inWord" | "inCompositum" }?,
   empty
}

1.45. <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
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 { teiatt.pointing.attribute.target, teimacro.specialPara }

1.46. <linkGrp>

<linkGrp> (link group) defines a collection of associations or hypertextual links. [17.1. Links]
Modulelinking
Attributes
Member of
Contained by
May contain
core: desc ptr
Note

May contain one or more <link> or <ptr> elements.

A web or link group is an administrative convenience, which should be used to collect a set of links together for any purpose, not simply to supply a default value for the type attribute.

Example
<linkGrp type="translation">  <link target="#CCS1 #SW1"/>  <link target="#CCS2 #SW2"/>  <link target="#CCS #SW"/> </linkGrp> <div type="volumexml:id="CCS"  xml:lang="fr">  <p>   <s xml:id="CCS1">Longtemps, je me suis couché de bonne heure.</s>   <s xml:id="CCS2">Parfois, à peine ma bougie éteinte, mes yeux se fermaient si vite que je n'avais pas le temps de me dire : "Je m'endors."</s>  </p> <!-- ... --> </div> <div type="volumexml:id="SWxml:lang="en">  <p>   <s xml:id="SW1">For a long time I used to go to bed early.</s>   <s xml:id="SW2">Sometimes, when I had put out my candle, my eyes would close so quickly that I had not even time to say "I'm going to sleep."</s>  </p> <!-- ... --> </div>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.descLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="link"/>
   <elementRef key="ptr"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element linkGrp
{
   teiatt.cmc.attributes,
   teiatt.typed.attribute.type,
   ( teimodel.descLike*, ( link | teiptr )+ )
}

1.47. <list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Modulecore
Attributes
type(type) describes the nature of the items in the list.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
index
Index
aufzaehlung
Aufzählung unspez. im Text
Note

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

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

subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
schlagwortregister
Schlagwortregister
personenregister
Personenregister
themenregister
Themenregister
diverse
Unspezifizierte Aufzählung
Member of
Contained by
May contain
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
{
   teiatt.global.attribute.n,
   teiatt.cmc.attributes,
   attribute type { "index" | "aufzaehlung" },
   attribute subtype
   {
      "schlagwortregister" | "personenregister" | "themenregister" | "diverse"
   },
   (
      ( teimodel.divTop | teimodel.global | teidesc* )*,
      (
         ( ( teiitem, teimodel.global* )+ )
       | (
            headLabel?,
            headItem?,
            ( ( teilabel, teimodel.global*, teiitem, teimodel.global* )+ )
         )
      ),
      ( ( teimodel.divBottom, teimodel.global* )* )
   )
}

1.48. <mapping>

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

Suggested values for the type attribute include exact for exact equivalences, uppercase for uppercase equivalences, lowercase for lowercase equivalences, and simplified for simplified characters. The <g> elements contained by this element can point to either another <char> or <glyph> element or contain a character that is intended to be the target of this mapping.

Example
<mapping type="modern">r</mapping> <mapping type="standard"></mapping>
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element mapping
{
   teiatt.datable.attributes,
   teiatt.typed.attribute.type,
   teimacro.xtext
}

1.49. <metamark>

<metamark> contains or describes any kind of graphic or written signal within a document the function of which is to determine how it should be read rather than forming part of the actual content of the document. [12.3.4.2. Metamarks]
Moduletranscr
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
Legal values are:
winkelzeichen
Winkelzeichen markiert Stelle der Hinzufügung im Text
anschlusspunkte
Manuskripte: Anschlusspunkte am Ende einer Einfügung (ggf. wiederholtes Anschlusswort hier mit einschließen)
pfeilsymbol
Manuskripte: Pfeilsymbol als Einschubmarker
rueckseitenymbol
Manuskripte: R als Einschubmarker
klammer_geschweift_rechts
Geschweifte Klammer (schließend)
klammer_geschweift_links
Geschweifte Klammer (öffnend)
klammer_eckig_links
Eckige Klammer (öffnend)
strich_senkrecht
Senkrechter Strich
Member of
Contained by
May contain
Example
<surface>  <metamark function="usedrend="line"   target="#X2"/>  <zone xml:id="zone-X2">   <line>I am that halfgrown <add>angry</add> boy, fallen asleep</line>   <line>The tears of foolish passion yet undried</line>   <line>upon my cheeks.</line> <!-- ... -->   <line>I pass through <add>the</add> travels and <del>fortunes</del> of   <retrace>thirty</retrace>   </line>   <line>years and become old,</line>   <line>Each in its due order comes and goes,</line>   <line>And thus a message for me comes.</line>   <line>The</line>  </zone>  <metamark function="used"   target="#zone-X2">Entered - Yes</metamark> </surface>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element metamark
{
   attribute n
   {
      "winkelzeichen"
    | "anschlusspunkte"
    | "pfeilsymbol"
    | "rueckseitenymbol"
    | "klammer_geschweift_rechts"
    | "klammer_geschweift_links"
    | "klammer_eckig_links"
    | "strich_senkrecht"
   },
   teimacro.specialPara
}

1.50. <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
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
{
   teiatt.cmc.attributes,
   teiatt.milestoneUnit.attributes,
   empty
}

1.51. <mod>

<mod> represents any kind of modification identified within a single document. [12.3.4.1. Generic Modification]
Moduletranscr
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
addition
Hinzufügung
deletion-addition
Löschung + Hinzufügung
deletion-addition-inword
Löschung + Hinzufügung in Wortmitte
deletion
Löschung
correction
Korrektur
Member of
Contained by
May contain
Example
<mod type="subst">  <add>pleasing</add>  <del>agreable</del> </mod>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element mod
{
   teiatt.placement.attribute.place,
   attribute type
   {
      "addition"
    | "deletion-addition"
    | "deletion-addition-inword"
    | "deletion"
    | "correction"
   },
   teimacro.paraContent
}

1.52. <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
Attributes
Contained by
msdescription: msDesc msPart
May contain
core: p
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
{
   teiatt.global.attribute.xmlid,
   teiatt.global.attribute.xmllang,
   teiatt.global.attribute.xmlbase,
   (
      teimodel.pLike+
    | ( summary?, textLang?, titlePage?, ( teimsItem | msItemStruct )* )
   )
}

1.53. <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
Member of
Contained by
May contain
Note

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

Example
<msDesc>  <msIdentifier>   <settlement>Oxford</settlement>   <repository>Bodleian Library</repository>   <idno type="Bod">MS Poet. Rawl. D. 169.</idno>  </msIdentifier>  <msContents>   <msItem>    <author>Geoffrey Chaucer</author>    <title>The Canterbury Tales</title>   </msItem>  </msContents>  <physDesc>   <objectDesc>    <p>A parchment codex of 136 folios, measuring approx        28 by 19 inches, and containing 24 quires.</p>    <p>The pages are margined and ruled throughout.</p>    <p>Four hands have been identified in the manuscript: the first 44        folios being written in two cursive anglicana scripts, while the        remainder is for the most part in a mixed secretary hand.</p>   </objectDesc>  </physDesc> </msDesc>
Schematron
<sch:rule context="tei:msContents|tei:physDesc|tei:history|tei:additional"> <!-- Note: This rule applies to <msContents>, <physDesc>, <history>, and <additional> wherever they occur. Luckily they are only allowed in places where they are constrained to 0 or 1 occurence. If that changes someday, this constraint may will likely need to be updated, too. --> <!-- Also worth noting that a) if &amp; when we can use abstract patterns, this would be better handled as a single abstract rule somewhere, and concrete rules in the individual <elementSpec>s; and b) I did not test for the existence of "../*[name(.) eq $gi][2]" because then an error would be generated for each of the multiple occurences of $gi. --> <sch:let name="gi" value="name(.)"/> <sch:report test="preceding-sibling::*[ name(.) eq $gi ] and not( following-sibling::*[ name(.) eq $gi ] )"> Only one <sch:name/> is allowed as a child of <sch:value-of select="name(..)"/>. </sch:report> </sch:rule>
Content model
<content>
 <sequence 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
{
   teimsIdentifier,
   teimodel.headLike*,
   (
      teimodel.pLike+
    | (
         teimsContents
       | teiphysDesc
       | history
       | additional
       | teimsPart
       | msFrag
      )*
   )
}

1.54. <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 msPart
May contain
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
{
   (
      teisettlement?,
      teiinstitution?,
      teirepository?,
      teicollection*,
      teiidno*
   ),
   ( teimsName | objectName | teialtIdentifier )*
}

1.55. <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
analysis: span
figures: figure
header: idno
msdescription: filiation msDesc msItem
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
{
   ( locus | locusGrp )*,
   (
      teimodel.pLike+
    | ( teimodel.titlepagePart | teimodel.msItemPart | teimodel.global )+
   )
}

1.56. <msName>

<msName> (manuscript name) contains a proper noun or noun phrase used for a manuscript, or other object, as opposed to a formal identification number or classmark. [11.4. The Manuscript Identifier]
Modulemsdescription
Attributes
Contained by
msdescription: msIdentifier
May contain
core: name
gaiji: g
character data
Example
<msName>The Vercelli Book</msName>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="rs"/>
  <elementRef key="name"/>
 </alternate>
</content>
    
Schema Declaration
element msName
{
   teiatt.global.attributes,
   teiatt.typed.attributes,
   ( text | teimodel.gLike | rs | teiname )*
}

1.57. <msPart>

<msPart> (manuscript part) contains information about an originally distinct manuscript or part of a manuscript, which is now part of a composite manuscript. [11.10. Manuscript Parts]
Modulemsdescription
Attributes
Contained by
msdescription: msDesc msPart
May contain
Note

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

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

1.58. <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
StatusRequired
Datatypeteidata.enumerated
Legal values are:
Schlagwortregistereintrag
Schlagwortregistereintrag
Personenregistereintrag
Personenregistereintrag
Member of
Contained by
May contain
Note

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

Example
<name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name ref="#HOC001type="person">Occleve</name>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element name
{
   teiatt.cmc.attributes,
   teiatt.canonical.attribute.key,
   attribute type { "Schlagwortregistereintrag" | "Personenregistereintrag" },
   teimacro.phraseSeq
}

1.59. <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
  • att.cmc
    • @generatedBy
  • att.anchoring
    • targetEnd
    • @anchored
placespecifies where this item is placed.
Derived fromatt.placement
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
ueber-der-zeile
Anmerkung über der Zeile
innerhalb-der-zeile
Anmerkung innerhalb der Zeile
unterhalb-der-zeile
Anmerkung unterhalb der Zeile
rand_rechts
Anmerkung am Rand rechts
rand_links
Anmerkung am Rand links
rand_oben
Anmerkung am Rand oben
rand_unten
Anmerkung am Rand unten
bottom
Manuskripte: Anmerkung am Rand unten (ggf. vereinheitlichen mit analogem Zettelwertattributwert)
below
Manuskripte: Anmerkung darüber (ggf. vereinheitlichen mit analogem Zettelwertattributwert)
inline
Manuskripte: Anmerkung innerhalb der Zeile (ggf. vereinheitlichen mit analogem Zettelwertattributwert)
overleaf
Manuskripte: Anmerkung auf der Rückseite (ggf. vereinheitlichen mit analogem Zettelwertattributwert)
opposite
Manuskripte: Anmerkung auf der gegenüberliegenden Blattseite (ggf. vereinheitlichen mit analogem Zettelwertattributwert)
inspace
Manuskripte: Anmerkung inspace (ggf. vereinheitlichen mit analogem Zettelwertattributwert)
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
luhmann
Anmerkung von Niklas Luhmann
editor
Anmerkung durch die Herausgeber (Niklas Luhmann-Archiv)
editor_link
Zettelanhang-Anmerkung durch die Herausgeber (Niklas Luhmann-Archiv) - zusätzliche Verlinkung
editor_note
Zettelanhang-Anmerkung durch die Herausgeber (Niklas Luhmann-Archiv)
header_editor
Zettelhead-Anmerkung durch die Herausgeber (Niklas Luhmann-Archiv)
luhmann_inhaltsnotiz
Inhaltliche Notiz von Niklas Luhmann (Bibliographiezettel)
luhmann_bearbeitungsvermerk
Bearbeitungsvermerk von Niklas Luhmann oder der Sekretärin (vorgemerkt, bestellt, leihen,…)
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
{
   teiatt.anchoring.attribute.anchored,
   teiatt.cmc.attributes,
   attribute place
   {
      list
      {
         (
            "ueber-der-zeile"
          | "innerhalb-der-zeile"
          | "unterhalb-der-zeile"
          | "rand_rechts"
          | "rand_links"
          | "rand_oben"
          | "rand_unten"
          | "bottom"
          | "below"
          | "inline"
          | "overleaf"
          | "opposite"
          | "inspace"
         )+
      }
   }?,
   attribute type
   {
      "luhmann"
    | "editor"
    | "editor_link"
    | "editor_note"
    | "header_editor"
    | "luhmann_inhaltsnotiz"
    | "luhmann_bearbeitungsvermerk"
   },
   teimacro.specialPara
}

1.60. <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
xml:lang(language) Kürzelvergabe folgt IANA/ISO 639 2-letter language code.
Derived fromatt.global
StatusRequired
Datatypeteidata.language
Legal values are:
de
Deutsch
en
Englisch
es
Spanisch
fr
Französisch
grc
Ancient Greek (to 1453)
el
Modern Greek (1453-)
he
Hebrew
it
Italienisch
la
Latein
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
{
   teiatt.cmc.attributes,
   attribute xml:lang
   {
      "de" | "en" | "es" | "fr" | "grc" | "el" | "he" | "it" | "la"
   },
   teimacro.paraContent
}

1.61. <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore
Attributes
renditionpoints to a description of the rendering or presentation used for this element in the source text.
Derived fromatt.global.rendition
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
#center
Absatz zentriert
#right
Absatz rechtsbündig (text-align: right;)
#ind-1
1. Zeile des Absatzes hängend (text-indent: -1em)
#ind-2
Absatz 2 Einheiten nach rechts eingerückt und 1. Zeile des Absatzes hängend (margin-left: 2em; text-indent: -1em;)
#ind-3
Absatz 2 Einheiten nach rechts eingerückt und 1. Zeile des Absatzes hängend- beginnt auf gleicher Höhe mit Standardabsatz (margin-left: 2em; text-indent: -2em;)
#l1em
Absatz 1 Einheit nach rechts eingerückt (margin-left: 1em;)
#l2em
Absatz 2 Einheiten nach rechts eingerückt (margin-left: 2em;)
#l3em
Absatz 3 Einheiten nach rechts eingerückt (margin-left: 3em;)
#item-lead
Erster Absatz innerhalb eines Listenpunkts soll diesen Wert tragen, im Unterschied zu den folgenden Abätzen, die über kein @rendition verfügen.
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 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
{
   teiatt.global.analytic.attribute.ana,
   teiatt.cmc.attributes,
   attribute rendition
   {
      list
      {
         (
            "#center"
          | "#right"
          | "#ind-1"
          | "#ind-2"
          | "#ind-3"
          | "#l1em"
          | "#l2em"
          | "#l3em"
          | "#item-lead"
         )+
      }
   }?,
   teimacro.paraContent
}

1.62. <pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]
Modulecore
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.
Derived fromatt.global.change
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Legal values are:
rotate_0
Faksimiledatei des Zettels soll in identischer Ausrichtung präsentiert werden. [Default-Wert bei Rumpfdatei-Erstellung]
rotate_90
Faksimiledatei des Zettels sollte für die Präsentation um 90° im Uhrzeigersinn gedreht werden.
rotate_180
Faksimiledatei des Zettels sollte für die Präsentation um 180° im Uhrzeigersinn gedreht werden.
rotate_270
Faksimiledatei des Zettels sollte für die Präsentation um 270° im Uhrzeigersinn gedreht werden.
rotate_0-corr
Faksimiledatei des Zettels soll in identischer Ausrichtung präsentiert werden, sollte aber hisichtlich Farbe und Helligkeit korrigiert werden.
rotate_90-corr
Faksimiledatei des Zettels sollte für die Präsentation um 90° im Uhrzeigersinn gedreht und hisichtlich Farbe und Helligkeit korrigiertund werden.
rotate_180-corr
Faksimiledatei des Zettels sollte für die Präsentation um 180° im Uhrzeigersinn gedreht und hisichtlich Farbe und Helligkeit korrigiertund werden.
rotate_270-corr
Faksimiledatei des Zettels sollte für die Präsentation um 270° im Uhrzeigersinn gedreht und hisichtlich Farbe und Helligkeit korrigiertund werden.
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:
a6_landscape
Originalformat und Ausrichtung des Zettels: DINA6 quer
a6_portrait
Originalformat und Ausrichtung des Zettels: DINA6 hochkant
a5_landscape
Originalformat und Ausrichtung des Zettels: DINA5 quer
a5_portrait
Originalformat und Ausrichtung des Zettels: DINA5 hochkant
a4_landscape
Originalformat und Ausrichtung des Zettels: DINA4 quer.
a4_portrait
Originalformat und Ausrichtung des Zettels: DINA4 hochkant
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
{
   teiatt.global.facs.attribute.facs,
   teiatt.cmc.attributes,
   attribute change
   {
      list
      {
         (
            "rotate_0"
          | "rotate_90"
          | "rotate_180"
          | "rotate_270"
          | "rotate_0-corr"
          | "rotate_90-corr"
          | "rotate_180-corr"
          | "rotate_270-corr"
         )+
      }
   }?,
   attribute rend
   {
      list
      {
         (
            "a6_landscape"
          | "a6_portrait"
          | "a5_landscape"
          | "a5_portrait"
          | "a4_landscape"
          | "a4_portrait"
         )+
      }
   }?,
   empty
}

1.63. <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
Attributes
Contained by
msdescription: msDesc msPart
May contain
core: p
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
{
   teiatt.global.attribute.xmlid,
   teiatt.global.attribute.xmllang,
   teiatt.global.attribute.xmlbase,
   ( teimodel.pLike* )
}

1.64. <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
Example
<projectDesc>  <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element projectDesc { teimodel.pLike+ }

1.65. <ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore
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
Sample values include:
#TODO
Soll während der Transkription mit xml:id des Zettels auf den verwiesen wird, eigenleitet durch "#", gefüllt werden, z.B. "#zkI_21-5". [#TODO ist Default-Wert bei Rumpfdatei-Erstellung]
#none
Ist im Fall von als Default-Wert eingetragen. Soll durch xml:id ersetzt wird, wenn der Sonderfall einer Textweiterführung auf der Zettelrückseite vorliegt.
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
vorwaerts-in-diesem-Strang
Vorwärts in diesem Strang
vorwaerts-in-eingeschobenem-Strang
Vorwärts in eingeschobenem Strang
vorwaerts-in-ergaenzendem-Strang
Vorwärts in ergänzendem Strang
vorwaerts-in-parallelem-Strang
Vorwärts in prallelem Strang
vorwaerts-im-nummerierten-Gliederungsverlauf
Vorwärts im nummerierten Gliederungsverlauf
rueckwaerts-in-diesem-Strang
Rückwarts in parallelem Strang
rueckwaerts-im-nummerierten-Gliederungsverlauf
Rückwarts im nummerierten Gliederungsverlauf
zurueck-zu-hoeherem-Strang
Zurück zu höherem Strang
Anfang-des-Strangs
Anfangszettel des Strangs
Anfang-des-naechsten-Komplexes
Anfang des naechsten Komplexes
Anfang-des-vorherigen-Komplexes
Anfang des vorherigen Komplexes
Zum-Einstiegspunkt
Zum Einstiegspunkt
kehrseite
Kehrseite - soll weiter spezifiziert werden über type-Attribut
naechste-vorderseite-im-zettelkasten
naechste-vorderseite-im-zettelkasten
vorherige-vorderseite-im-zettelkasten
vorherige-vorderseite-im-zettelkasten
naechster-scan-im-zettelkasten
naechster-scan-im-zettelkasten
vorheriger-scan-im-zettelkasten
vorheriger-scan-im-zettelkasten
Vorderseite-des-vorherigen-Zettels-in-corrected-physical-sequence
naechste-relevante-seite-im-zettelkasten
Vorderseite-des-naechsten-Zettels-in-corrected-physical-sequence
vorherige-relevante-seite-im-zettelkasten
note-anchor
Hilfsanker für "notes" in Manuskripten zur besseren Darstellung im oxygen-Framework. Sollte ggf später wieder entfernt werden, da im TEI unnötig.
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
{
   teiatt.cmc.attributes,
   teiatt.typed.attribute.subtype,
   attribute target { list { + } },
   attribute type
   {
      "vorwaerts-in-diesem-Strang"
    | "vorwaerts-in-eingeschobenem-Strang"
    | "vorwaerts-in-ergaenzendem-Strang"
    | "vorwaerts-in-parallelem-Strang"
    | "vorwaerts-im-nummerierten-Gliederungsverlauf"
    | "rueckwaerts-in-diesem-Strang"
    | "rueckwaerts-im-nummerierten-Gliederungsverlauf"
    | "zurueck-zu-hoeherem-Strang"
    | "Anfang-des-Strangs"
    | "Anfang-des-naechsten-Komplexes"
    | "Anfang-des-vorherigen-Komplexes"
    | "Zum-Einstiegspunkt"
    | "kehrseite"
    | "naechste-vorderseite-im-zettelkasten"
    | "vorherige-vorderseite-im-zettelkasten"
    | "naechster-scan-im-zettelkasten"
    | "vorheriger-scan-im-zettelkasten"
    | "Vorderseite-des-vorherigen-Zettels-in-corrected-physical-sequence"
    | "Vorderseite-des-naechsten-Zettels-in-corrected-physical-sequence"
    | "note-anchor"
   },
   empty
}

1.66. <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
core: bibl
May contain
Example
<publicationStmt>  <publisher>Oxford University Press</publisher>  <pubPlace>Oxford</pubPlace>  <date>1989</date> </publicationStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element pubPlace { teimacro.phraseSeq }

1.67. <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
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
{
   (
      (
         teimodel.publicationStmtPart.agency,
         teimodel.publicationStmtPart.detail*
      )+
   )
 | teimodel.pLike+
}

1.68. <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
core: bibl
May contain
Note

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

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

1.69. <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
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
nl_vw_gliederung
Verweise im Rahmen einer Gliederungsstruktur: Hier notierte Luhmann am Beginn eines größeren Gedankengangs auf einem Zettel mehrere zu behandelnde Aspekte und markiert diese mit jeweils einem Großbuchstaben, der auf einen entsprechend nummerierten Zettel (bzw. eine Zettelfolge) verweist, die zumindest in relativer räumlicher Nähe zu dem Gliederungszettel steht. Vgl. Beispielzettel aus Zettelkasten I 17-11e
nl_vw_einzel_nah
Einzelverweise (nah): Im Rahmen von Notizen vermerkte Luhmann sehr häufig einen Verweis auf einen anderen Zettel in der Sammlung, der für das behandelte Thema ebenfalls relevant ist. Hier: Verzettelungsverweis auf einen Nebengedanken, der dann auf einem eingeschobenen Zettel in räumlicher Nähe zum Verweiszettel steht. Der Verweis erfolgt mit einer rot geschriebenen Zahl oder einem Buchstaben, die/der sich dann zusätzlich zur eiegntlichen Nummerierung auch auf dem Zettel befindet, auf den verwiesen wird. Vgl. Beispielzettel aus Zettelkasten I 17,1b9 und 17,1b9,2 (Vgl. Beispielbild UB: http://ds.ub.uni-bielefeld.de/viewer/image/ZK_digital_17/77/)
nl_vw_einzel_entf
Einzelverweise (entfernt): Im Rahmen von Notizen vermerkte Luhmann sehr häufig einen Verweis auf einen anderen Zettel in der Sammlung, der für das behandelte Thema ebenfalls relevant ist. Hier: Verweis auf einen anderen Zettel, der für das behandelte Thema/den Begriff von Interesse ist, der sich aber an einer ganz anderen Stelle des Kastens und damt dann häufig auch in einem ganz anderen Diskussiponskontext wiederfindet. Beim Verweis wird die entsprechende Zettelnummer notiert. Vgl. Beispielzettel aus Zettelkasten I 17,1b9
nl_vw_rueckseite
Einzelverweise auf Zettelrückseiten:
nl_vw_reg_intern_SW1
Interner Verweis von einem Registereintrag zu einem anderen Eintrag innerhalb desselben Registers - SW1
nl_vw_reg_intern_SW2a
Interner Verweis von einem Registereintrag zu einem anderen Eintrag innerhalb desselben Registers - SW2a
nl_vw_sammlung_E
Einzelverweise (entfernt) auf einen Zettel der Sammlung E:
Niklas-Luhmann-Bibliographie
Interne Verweise innerhalb der Bibliographie der Luhmannschen Publikationen (Niklas-Luhmann-Bibliographie)
nl_vw_unknown
ToDo
pageref
Von le-tex für Drucklegung in Datei eingeführt: Seitenreferenz
noteref
Von le-tex für Drucklegung in Datei eingeführt: Fußnoten/Anmerkungsreferenz
editor
Einzelverweis durch Herausgeber ergänzt
extern
Einzelverweis extern
ms
Verweis (von Luhmann) auf ein konkretes eigenes Manuskript (Ziel ist die Manuskripttranskription)
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
{
   teiatt.global.linking.attribute.corresp,
   teiatt.cmc.attributes,
   teiatt.pointing.attribute.target,
   attribute type
   {
      "nl_vw_gliederung"
    | "nl_vw_einzel_nah"
    | "nl_vw_einzel_entf"
    | "nl_vw_rueckseite"
    | "nl_vw_reg_intern_SW1"
    | "nl_vw_reg_intern_SW2a"
    | "nl_vw_sammlung_E"
    | "Niklas-Luhmann-Bibliographie"
    | "nl_vw_unknown"
    | "pageref"
    | "noteref"
    | "editor"
    | "extern"
    | "ms"
   }?,
   teimacro.paraContent
}

1.70. <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
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
translation
Übersetzung des vorhergehenden Wortes/Begriffes
normalization
Normalisierte Schreibweise des vorhergehenden Wortes/Begriffes
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
{
   teiatt.cmc.attributes,
   attribute type { "translation" | "normalization" },
   teimacro.paraContent
}

1.71. <relatedItem>

<relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.12.2.7. Related Items]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
translation
Übersetzung
translationOf
Übersetzung von
related-translations
Übersetzungen anderer Ausgaben dieses Textes
reprint
Nachdruck
reprintOf
Nachdruck von
firstPrint
Erstdruck
reviewOf
Review zu
partOf
Teil von
continuedBy
Fortgesetzt von
continuationOf
Fortsetzung von
same-series-other-volume
Schwesterband eines mehrbändigen Werks
articleIncluded
Einzelner Artikel der im übergeordneten Item enthalten ist
Member of
Contained by
core: bibl
May contain
core: bibl ptr ref
msdescription: msDesc
Note

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

Example
<biblStruct>  <monogr>   <author>Shirley, James</author>   <title type="main">The gentlemen of Venice</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Readex Microprint</publisher>    <date>1953</date>   </imprint>   <extent>1 microprint card, 23 x 15 cm.</extent>  </monogr>  <series>   <title>Three centuries of drama: English, 1642–1700</title>  </series>  <relatedItem type="otherForm">   <biblStruct>    <monogr>     <author>Shirley, James</author>     <title type="main">The gentlemen of Venice</title>     <title type="sub">a tragi-comedie presented at the private house in Salisbury          Court by Her Majesties servants</title>     <imprint>      <pubPlace>London</pubPlace>      <publisher>H. Moseley</publisher>      <date>1655</date>     </imprint>     <extent>78 p.</extent>    </monogr>   </biblStruct>  </relatedItem> </biblStruct>
Schematron
<sch:rule context="tei:relatedItem"> <sch:report test="@target and count( child::* ) > 0">If the @target attribute on <sch:name/> is used, the relatedItem element must be empty</sch:report> <sch:assert test="@target or child::*">A relatedItem element should have either a @target attribute or a child element to indicate the related bibliographic item</sch:assert> </sch:rule>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="0">
  <classRef key="model.biblLike"/>
  <classRef key="model.ptrLike"/>
 </alternate>
</content>
    
Schema Declaration
element relatedItem
{
   attribute type
   {
      "translation"
    | "translationOf"
    | "related-translations"
    | "reprint"
    | "reprintOf"
    | "firstPrint"
    | "reviewOf"
    | "partOf"
    | "continuedBy"
    | "continuationOf"
    | "same-series-other-volume"
    | "articleIncluded"
   },
   ( teimodel.biblLike | teimodel.ptrLike )?
}

1.72. <rendition>

<rendition> (rendition) supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]
Moduleheader
Attributes
scopewhere CSS is used, provides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
first-line
styling applies to the first line of the target element
first-letter
styling applies to the first letter of the target element
before
styling should be applied immediately before the content of the target element
after
styling should be applied immediately after the content of the target element
selectorcontains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute.
StatusOptional
Datatypeteidata.text
<rendition scheme="css"  selector="text, front, back, body, div, p, ab"> display: block; </rendition>
<rendition scheme="css"  selector="*[rend*=italic]"> font-style: italic; </rendition>
Note

Since the default value of the scheme attribute is assumed to be CSS, the default expectation for this attribute, in the absence of scheme, is that CSS selector syntax will be used.

While rendition is used to point from an element in the transcribed source to a <rendition> element in the header which describes how it appears, the selector attribute allows the encoder to point in the other direction: from a <rendition> in the header to a collection of elements which all share the same renditional features. In both cases, the intention is to record the appearance of the source text, not to prescribe any particular output rendering.

Contained by
header: tagsDecl
May contain
figures: table
header: idno
msdescription: msDesc
namesdates: eventName settlement
character data
Example
<tagsDecl>  <rendition scheme="cssxml:id="r-center">text-align: center;</rendition>  <rendition scheme="cssxml:id="r-small">font-size: small;</rendition>  <rendition scheme="cssxml:id="r-large">font-size: large;</rendition>  <rendition scheme="css"   scope="first-letterxml:id="initcaps">font-size: xx-large</rendition> </tagsDecl>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element rendition
{
   teiatt.global.attributes,
   teiatt.styleDef.attributes,
   attribute scope { text }?,
   attribute selector { text }?,
   teimacro.limitedContent
}

1.73. <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
May contain
Example
<msIdentifier>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Bodleian Library</repository>  <idno>MS. Bodley 406</idno> </msIdentifier>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element repository { teimacro.phraseSeq.limited }

1.74. <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
header: change
Note

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

Example
<revisionDesc status="embargoed">  <change when="1991-11-11who="#LB"> deleted chapter 10 </change> </revisionDesc>
Content model
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <elementRef key="list"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="listChange"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="change"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element revisionDesc { teilist+ | listChange+ | teichange+ }

1.75. <row>

<row> (row) contains one row of a table. [15.1.1. TEI Tables]
Modulefigures
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 { teicell+ }

1.76. <settlement>

<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [14.2.3. Place Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<placeName>  <settlement type="town">Glasgow</settlement>  <region>Scotland</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element settlement { teiatt.cmc.attributes, teimacro.phraseSeq }

1.77. <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
Contained by
header: fileDesc
May contain
core: bibl list p
figures: table
msdescription: msDesc
Example
<sourceDesc>  <bibl>   <title level="a">The Interesting story of the Children in the Wood</title>. In  <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.  <publisher>OUP</publisher>   <date>1968</date>. </bibl> </sourceDesc>
Example
<sourceDesc>  <p>Born digital: no previous source exists.</p> </sourceDesc>
Content model
<content>
 <alternate 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
{
   teimodel.pLike+
 | ( teimodel.biblLike | teimodel.sourceDescPart | teimodel.listLike )+
}

1.78. <space>

<space> (space) indicates the location of a significant space in the text. [12.4.1. Space]
Moduletranscr
Attributes
dim(dimension) indicates whether the space is horizontal or vertical.
StatusRecommended
Datatypeteidata.enumerated
Legal values are:
horizontal
the space is horizontal.
vertical
the space is vertical.
Note

For irregular shapes in two dimensions, the value for this attribute should reflect the more important of the two dimensions. In conventional left-right scripts, a space with both vertical and horizontal components should be classed as vertical.

Member of
Contained by
May contain
core: desc
Note

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

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

1.79. <span>

<span> associates an interpretative annotation directly with a span of text. [18.3. Spans and Interpretations]
Moduleanalysis
Attributes
typeindicates what kind of phenomenon is being noted in the passage.
Derived fromatt.interpLike
StatusRequired
Datatypeteidata.enumerated
Legal values are:
title
nla_intern
range
fromgives the identifier of the node which is the starting point of the span of text being annotated; if not accompanied by a to attribute, gives the identifier of the node of the entire span of text being annotated.
StatusOptional
Datatypeteidata.pointer
togives the identifier of the node which is the end-point of the span of text being annotated.
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
May contain
Example
<p xml:id="para2">(The "aftermath" starts here)</p> <p xml:id="para3">(The "aftermath" continues here)</p> <p xml:id="para4">(The "aftermath" ends in this paragraph)</p> <!-- ... --> <span from="#para2to="#para4"  type="structure">aftermath</span>
Schematron
<sch:rule context="tei:span"> <sch:report test="@from and @target"> Only one of the attributes @target and @from may be supplied on <sch:name/> </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:span"> <sch:report test="@to and @target"> Only one of the attributes @target and @to may be supplied on <sch:name/> </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:span"> <sch:report test="@to and not(@from)"> If @to is supplied on <sch:name/>, @from must be supplied as well </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:span"> <sch:report test="contains(normalize-space(@to),' ') or contains(normalize-space(@from),' ')"> The attributes @to and @from on <sch:name/> may each contain only a single value </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element span
{
   teiatt.cmc.attributes,
   attribute type { "title" | "nla_intern" | "range" },
   attribute from { text }?,
   attribute to { text }?,
   teimacro.phraseSeq.limited
}

1.80. <table>

<table> (table) contains text displayed in tabular form, in rows and columns. [15.1.1. TEI Tables]
Modulefigures
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:
boxed_left
Tabelle mit Gitterlinien - Ausreichtung Standard (links)
boxed_center
Tabelle mit Gitterlinien - Ausreichtung zentriert
boxed_right
Tabelle mit Gitterlinien - Ausreichtung rechts
boxed-light_left
Tabelle mit angedeuteten Gitterlinien - Ausreichtung Standard (links)
boxed-light_center
Tabelle mit angedeuteten Gitterlinien - Ausreichtung zentriert
boxed-light_right
Tabelle mit angedeuteten Gitterlinien - Ausreichtung rechts
unboxed_left
Tabelle ohne Gitterlinien - Ausreichtung Standard (links)
unboxed_center
Tabelle ohne Gitterlinien - Ausreichtung zentriert
unboxed_right
Tabelle ohne Gitterlinien - Ausreichtung rechts
sonderfall_1
Anzeige im Portal über Sonderfallregelung 1
sonderfall_2
Anzeige im Portal über Sonderfallregelung 2
sonderfall_3
Anzeige im Portal über Sonderfallregelung 3
sonderfall_4
Anzeige im Portal über Sonderfallregelung 4
sonderfall_5
Anzeige im Portal über Sonderfallregelung 5
Member of
Contained by
May contain
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
{
   teiatt.cmc.attributes,
   attribute rend
   {
      list
      {
         (
            "boxed_left"
          | "boxed_center"
          | "boxed_right"
          | "boxed-light_left"
          | "boxed-light_center"
          | "boxed-light_right"
          | "unboxed_left"
          | "unboxed_center"
          | "unboxed_right"
          | "sonderfall_1"
          | "sonderfall_2"
          | "sonderfall_3"
          | "sonderfall_4"
          | "sonderfall_5"
         )+
      }
   },
   (
      ( teimodel.headLike | teimodel.global )*,
      (
         ( ( teirow, teimodel.global* )+ )
       | ( ( teimodel.graphicLike, teimodel.global* )+ )
      ),
      ( ( teimodel.divBottom, teimodel.global* )* )
   )
}

1.81. <tagsDecl>

<tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]
Moduleheader
Member of
Contained by
header: encodingDesc
May contain
header: rendition
Example
<tagsDecl partial="true">  <rendition scheme="css"   selector="emph, hi, name, titlexml:id="rend-it">font-style: italic;</rendition>  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="hioccurs="467"/>   <tagUsage gi="titleoccurs="45"/>  </namespace>  <namespace name="http://docbook.org/ns/docbook">   <tagUsage gi="paraoccurs="10"/>  </namespace> </tagsDecl>
If the partial attribute were not specified here, the implication would be that the document in question contains only <hi>, <title>, and <para> elements.
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="rendition"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="namespace"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element tagsDecl { teirendition*, namespace* }

1.82. <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
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 { teifileDesc, teimodel.teiHeaderPart*, teirevisionDesc? }

1.83. <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
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
{
   teiatt.canonical.attribute.key,
   teiatt.cmc.attributes,
   teiatt.typed.attribute.type,
   teimacro.phraseSeq
}

1.84. <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
Attributes
Member of
Contained by
textstructure: TEI
May contain
analysis: span
figures: figure
textstructure: back body
Note

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

Example
<text>  <front>   <docTitle>    <titlePart>Autumn Haze</titlePart>   </docTitle>  </front>  <body>   <l>Is it a dragonfly or a maple leaf</l>   <l>That settles softly down upon the water?</l>  </body> </text>
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
{
   teiatt.global.attribute.xmlid,
   teiatt.global.attribute.n,
   teiatt.typed.attribute.type,
   (
      teimodel.global*,
      ( ( front, teimodel.global* )? ),
      ( teibody | group ),
      teimodel.global*,
      ( ( teiback, teimodel.global* )? )
   )
}

1.85. <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
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
main
Haupttitel
sub
Untertitel
short
Kurztitel
zetteltyp
Zetteltyp
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
{
   teiatt.cmc.attributes,
   attribute type { "main" | "sub" | "short" | "zetteltyp" }?,
   teimacro.paraContent
}

1.86. <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
core: title
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 { teititle+, teimodel.respLike* }

1.87. <unclear>

<unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [12.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 22. Certainty, Precision, and Responsibility.

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.

The hand attribute points to a definition of the hand concerned, as further discussed in section 12.3.2.1. Document Hands.

Example
<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element unclear { teiatt.cmc.attributes, teimacro.paraContent }

1.88. <unitDecl>

<unitDecl> (unit declarations) provides information about units of measurement that are not members of the International System of Units. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May containEmpty element
Example
<unitDecl>  <unitDef type="weightxml:id="">   <label xml:lang="ja"></label>   <label xml:lang="ja-Latn">kin</label>   <conversion formula="16fromUnit="#両"    toUnit="#斤"/>  </unitDef>  <unitDef type="weightxml:id="">   <label xml:lang="ja"></label>   <label xml:lang="ja-Latn">ryo</label>   <conversion formula="4fromUnit="#分"    toUnit="#両"/>  </unitDef>  <unitDef type="weightxml:id="">   <label xml:lang="ja"></label>   <label xml:lang="ja-Latn">Bu</label>   <conversion formula="6fromUnit="#銖"    toUnit="#分"/>  </unitDef>  <unitDef type="weightxml:id="">   <label xml:lang="ja"></label>   <label xml:lang="ja-Latn">Shu</label>  </unitDef> </unitDecl>
Content model
<content>
 <elementRef key="unitDef"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element unitDecl
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   teiatt.datable.attributes,
   unitDef+
}

2. Model classes

2.1. model.attributable

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

2.2. model.availabilityPart

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

2.3. model.biblLike

model.biblLike groups elements containing a bibliographic description. [3.12. Bibliographic Citations and References]
Moduletei
Used by
Membersbibl msDesc

2.4. model.biblPart

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

2.5. model.choicePart

model.choicePart groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.5. Simple Editorial Changes]
Moduletei
Used by
Membersabbr expan orig reg unclear

2.6. 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 model.pLike[p]] model.inter[model.attributable[model.quoteLike] model.biblLike[bibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list table] model.oddDecl model.stageLike]
Note

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

2.7. model.dateLike

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

2.8. model.descLike

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

2.9. 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 model.divWrapper

2.10. model.divLike

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

2.11. model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.lLike model.pLike[p]
Note

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

2.12. 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]] model.divWrapper

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

2.14. 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
Membersforeign term title

2.15. model.encodingDescPart

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

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

2.17. model.gLike

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

2.19. model.global.edit

model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]
Moduletei
Used by
MembersaddSpan ellipsis gap space

2.20. model.global.meta

model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]
Moduletei
Used by
Membersindex join linkGrp span
Note

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

2.21. 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.22. 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.23. 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

2.24. model.highlighted

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

2.25. model.imprintPart

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

2.26. 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] model.biblLike[bibl msDesc] model.egLike model.labelLike[desc label] model.listLike[list table] model.oddDecl model.stageLike

2.27. model.labelLike

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

2.28. model.limitedPhrase

model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.emphLike[foreign term title] model.hiLike[hi] model.pPart.data[model.addressLike model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[settlement]] eventName idno]] model.pPart.editorial[abbr choice expan] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr ref]

2.29. model.listLike

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

2.30. 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 fw lb milestone pb

2.31. model.msItemPart

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

2.32. 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.33. model.nameLike

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

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

2.34. 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
Note

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

2.35. model.noteLike

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

2.36. model.pLike

2.37. 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.38. 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 model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[settlement]] eventName idno]

2.39. 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 choice expan] model.pPart.transcriptional[add del mod orig reg unclear]

2.40. 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 choice expan

2.41. model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]
Moduletei
Used by
Membersadd del mod orig reg unclear

2.42. model.paraPart

2.43. 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[foreign term title] model.hiLike[hi]] model.lPart model.pPart.data[model.addressLike model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart[settlement]] eventName idno]] model.pPart.edit[model.pPart.editorial[abbr choice expan] model.pPart.transcriptional[add del mod orig reg unclear]] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr ref] model.segLike model.specDescLike
Note

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

2.44. model.placeNamePart

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

2.45. model.placeStateLike

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

2.46. 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.47. 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.48. 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] 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.49. 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
Memberstext

2.50. model.teiHeaderPart

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

2.51. 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
Memberschange
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[eventName name] collection institution pubPlace repository settlement] bibl date publisher term title unitDecl
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 customizaiton, 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
Membersabbr add anchor bibl choice date del desc expan figure foreign gap graphic head hi idno index join label lb linkGrp list milestone name note orig p pb ptr ref reg settlement span table term title unclear
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

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
MembersaltIdentifier change date eventName gender idno licence mapping name settlement title unitDecl
Attributes
periodsupplies pointers to one or more definitions of named periods of time (typically <category>s, <date>s, or <event>s) within which the datable item is understood to have occurred.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

3.5. 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[altIdentifier change date eventName gender idno licence mapping name settlement title unitDecl]
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.6. 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[altIdentifier change date eventName gender idno licence mapping name settlement title unitDecl]
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 occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.
notBefore-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.7. 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[altIdentifier change date eventName gender idno licence mapping name settlement title unitDecl]
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.8. att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Moduletei
Membersadd addSpan date del ellipsis gap mod space unclear
Attributes
unitnames the unit used for the measurement
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
quantityspecifies the length in the units specified
StatusOptional
Datatypeteidata.numeric
extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
StatusOptional
Datatypeteidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
StatusOptional
Datatypeteidata.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

3.9. att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 11.3.1. Origination 14.3.2. The Person Element 12.3.1.1. Core Elements for Transcriptional Work]
Moduletei
Membersatt.transcriptional[add addSpan del mod] date eventName expan gap gender name reg unclear
Attributes
evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
internal
there is internal evidence to support the intervention.
external
there is external evidence to support the intervention.
conjecture
the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
instantindicates whether this is an instant revision or not.
StatusOptional
Datatypeteidata.xTruthValue
Defaultfalse
Note

The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned.

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

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Moduletei
MembersTEI abbr add addSpan altIdentifier anchor availability back bibl body cell change charDecl choice collection date del desc div editorialDecl ellipsis encodingDesc eventName expan figDesc figure fileDesc filiation foreign fw g gap gender glyph graphic head hi idno index institution item join label lb licence linkGrp list mapping metamark milestone mod msContents msDesc msIdentifier msItem msName msPart name note orig p pb physDesc projectDesc ptr pubPlace publicationStmt publisher ref reg relatedItem rendition repository revisionDesc row settlement sourceDesc space span table tagsDecl teiHeader term text title titleStmt unclear unitDecl
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
StatusOptional
DatatypeID
Note

The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
StatusOptional
Datatypeteidata.text
Note

The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
StatusOptional
Datatypeteidata.language
<p> … The consequences of this rapid depopulation were the loss of the last <foreign xml:lang="rap">ariki</foreign> or chief (Routledge 1920:205,210) and their connections to ancestral territorial organization.</p>
Note

The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the <teiHeader> from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

The authoritative list of registered language subtags is maintained by IANA and is available at https://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see https://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
StatusOptional
Datatypeteidata.pointer
<div type="bibl">  <head>Selections from <title level="m">The Collected Letters of Robert Southey. Part 1: 1791-1797</title>  </head>  <listBibl xml:base="https://romantic-circles.org/sites/default/files/imported/editions/southey_letters/XML/">   <bibl>    <ref target="letterEEd.26.3.xml">     <title>Robert Southey to Grosvenor Charles Bedford</title>, <date when="1792-04-03">3 April 1792</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.57.xml">     <title>Robert Southey to Anna Seward</title>, <date when="1793-09-18">18 September 1793</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.85.xml">     <title>Robert Southey to Robert Lovell</title>, <date from="1794-04-05"      to="1794-04-06">5-6 April, 1794</date>.    </ref>   </bibl>  </listBibl> </div>
xml:spacesignals an intention about how white space should be managed by applications.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note

The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

3.12. att.global.analytic

att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [18.2. Global Attributes for Simple Analyses 18.3. Spans and Interpretations]
Moduleanalysis
Membersatt.global[TEI abbr add addSpan altIdentifier anchor availability back bibl body cell change charDecl choice collection date del desc div editorialDecl ellipsis encodingDesc eventName expan figDesc figure fileDesc filiation foreign fw g gap gender glyph graphic head hi idno index institution item join label lb licence linkGrp list mapping metamark milestone mod msContents msDesc msIdentifier msItem msName msPart name note orig p pb physDesc projectDesc ptr pubPlace publicationStmt publisher ref reg relatedItem rendition repository revisionDesc row settlement sourceDesc space span table tagsDecl teiHeader term text title titleStmt unclear unitDecl]
Attributes
ana(analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

3.13. 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 abbr add addSpan altIdentifier anchor availability back bibl body cell change charDecl choice collection date del desc div editorialDecl ellipsis encodingDesc eventName expan figDesc figure fileDesc filiation foreign fw g gap gender glyph graphic head hi idno index institution item join label lb licence linkGrp list mapping metamark milestone mod msContents msDesc msIdentifier msItem msName msPart name note orig p pb physDesc projectDesc ptr pubPlace publicationStmt publisher ref reg relatedItem rendition repository revisionDesc row settlement sourceDesc space span table tagsDecl teiHeader term text title titleStmt unclear unitDecl]
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.14. 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 abbr add addSpan altIdentifier anchor availability back bibl body cell change charDecl choice collection date del desc div editorialDecl ellipsis encodingDesc eventName expan figDesc figure fileDesc filiation foreign fw g gap gender glyph graphic head hi idno index institution item join label lb licence linkGrp list mapping metamark milestone mod msContents msDesc msIdentifier msItem msName msPart name note orig p pb physDesc projectDesc ptr pubPlace publicationStmt publisher ref reg relatedItem rendition repository revisionDesc row settlement sourceDesc space span table tagsDecl teiHeader term text title titleStmt unclear unitDecl]
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.15. att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [17. Linking, Segmentation, and Alignment]
Modulelinking
Membersatt.global[TEI abbr add addSpan altIdentifier anchor availability back bibl body cell change charDecl choice collection date del desc div editorialDecl ellipsis encodingDesc eventName expan figDesc figure fileDesc filiation foreign fw g gap gender glyph graphic head hi idno index institution item join label lb licence linkGrp list mapping metamark milestone mod msContents msDesc msIdentifier msItem msName msPart name note orig p pb physDesc projectDesc ptr pubPlace publicationStmt publisher ref reg relatedItem rendition repository revisionDesc row settlement sourceDesc space span table tagsDecl teiHeader term text title titleStmt unclear unitDecl]
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.

nextpoints 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.16. 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 abbr add addSpan altIdentifier anchor availability back bibl body cell change charDecl choice collection date del desc div editorialDecl ellipsis encodingDesc eventName expan figDesc figure fileDesc filiation foreign fw g gap gender glyph graphic head hi idno index institution item join label lb licence linkGrp list mapping metamark milestone mod msContents msDesc msIdentifier msItem msName msPart name note orig p pb physDesc projectDesc ptr pubPlace publicationStmt publisher ref reg relatedItem rendition repository revisionDesc row settlement sourceDesc space span table tagsDecl teiHeader term text title titleStmt unclear unitDecl]
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.

renditionpoints 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. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

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

3.17. 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 abbr add addSpan altIdentifier anchor availability back bibl body cell change charDecl choice collection date del desc div editorialDecl ellipsis encodingDesc eventName expan figDesc figure fileDesc filiation foreign fw g gap gender glyph graphic head hi idno index institution item join label lb licence linkGrp list mapping metamark milestone mod msContents msDesc msIdentifier msItem msName msPart name note orig p pb physDesc projectDesc ptr pubPlace publicationStmt publisher ref reg relatedItem rendition repository revisionDesc row settlement sourceDesc space span table tagsDecl teiHeader term text title titleStmt unclear unitDecl]
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.18. 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 abbr add addSpan altIdentifier anchor availability back bibl body cell change charDecl choice collection date del desc div editorialDecl ellipsis encodingDesc eventName expan figDesc figure fileDesc filiation foreign fw g gap gender glyph graphic head hi idno index institution item join label lb licence linkGrp list mapping metamark milestone mod msContents msDesc msIdentifier msItem msName msPart name note orig p pb physDesc projectDesc ptr pubPlace publicationStmt publisher ref reg relatedItem rendition repository revisionDesc row settlement sourceDesc space span table tagsDecl teiHeader term text title titleStmt unclear unitDecl]
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.19. 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.20. att.milestoneUnit

att.milestoneUnit provides attributes to indicate the type of section which is changing at a specific milestone. [3.11.3. Milestone Elements 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]
Modulecore
Membersmilestone
Attributes
unitprovides a conventional name for the kind of section changing at this milestone.
StatusRequired
Datatypeteidata.enumerated
Suggested values include:
page
physical page beginnings (synonymous with the <pb> element).
column
column beginnings.
line
line beginnings (synonymous with the <lb> element).
book
any units termed book, liber, etc.
poem
individual poems in a collection.
canto
cantos or other major sections of a poem.
speaker
changes of speaker or narrator.
stanza
stanzas within a poem, book, or canto.
act
acts within a play.
scene
scenes within a play or act.
section
sections of any kind.
absent
passages not present in the reference edition.
unnumbered
passages present in the text, but not to be included as part of the reference.
<milestone ed="La"  n="23"  unit="Dreissiger"/> ... <milestone ed="AV"  n="24"  unit="verse"/> ...
Note

If the milestone marks the beginning of a piece of text not present in the reference edition, the special value absent may be used as the value of unit. The normal interpretation is that the reference edition does not contain the text which follows, until the next <milestone> tag for the edition in question is encountered.

In addition to the values suggested, other terms may be appropriate (e.g. Stephanus for the Stephanus numbers in Plato).

The type attribute may be used to characterize the unit boundary in any respect other than simply identifying the type of unit, for example as word-breaking or not.

3.21. 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[eventName name] collection institution pubPlace repository settlement
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.22. att.personal

att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [14.2.1. Personal Names]
Moduletei
MemberseventName name
Attributes
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
yes
(yes) the name component is spelled out in full.[Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.
sort(sort) specifies the sort order of the name component in relation to others within the name.
StatusOptional
Datatypeteidata.count

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
Membersatt.transcriptional[add addSpan del mod] div figure fw head label metamark 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.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
Moduletei
Membersatt.pointing.group[linkGrp] join licence note ptr ref span term
Attributes
targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
StatusOptional
Datatypeteidata.language
Schematron
<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]"> <sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert> </sch:rule>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">  <ptr target="pol/UDHR/text.xml#pol_txt_1-head"   targetLang="pl"   type="tuv"   xml:id="pol-swh_aln_2.1.1-ptr"/>  <ptr target="swh/UDHR/text.xml#swh_txt_1-head"   targetLang="sw"   type="tuv"   xml:id="pol-swh_aln_2.1.2-ptr"/> </linkGrp>
In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.
Note

The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

targetspecifies the destination of the reference by supplying one or more URI References.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

evaluate(evaluate) specifies the intended meaning when the target of a pointer is itself a pointer.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
all
if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
one
if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
none
no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
Note

If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

3.25. att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei
Membersatt.dimensions[add addSpan date del ellipsis gap mod space unclear]
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.26. att.resourced

att.resourced provides attributes by which a resource (such as an externally held media file) may be located.
Moduletei
Membersgraphic
Attributes
url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
StatusRequired
Datatypeteidata.pointer

3.27. att.spanning

att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [12.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]
Moduletei
MembersaddSpan index lb metamark milestone mod pb
Attributes
spanToindicates the end of a span initiated by the element bearing this attribute.
StatusOptional
Datatypeteidata.pointer
SchematronThe @spanTo attribute must point to an element following the current element; however, this can only be tested if both this element and the one pointed to are in the same document.
<sch:rule context="tei:*[ starts-with( @spanTo, '#') ]"> <sch:assert test="id( substring( @spanTo, 2 ) ) >> .">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current <sch:name/> element </sch:assert> </sch:rule>
Note

The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

3.28. att.styleDef

att.styleDef provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.
Moduletei
Membersrendition
Attributes
schemeidentifies the language used to describe the rendition.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
css
Cascading Stylesheet Language
xslfo
Extensible Stylesheet Language Formatting Objects
free
Informal free text description
other
A user-defined rendition description language
Note

If no value for the @scheme attribute is provided, then the default assumption should be that CSS is in use.

schemeVersionsupplies a version number for the style language provided in scheme.
StatusOptional
Datatypeteidata.versionNumber
Schematron
<sch:rule context="tei:*[@schemeVersion]"> <sch:assert test="@scheme and not(@scheme = 'free')"> @schemeVersion can only be used if @scheme is specified. </sch:assert> </sch:rule>
Note

If schemeVersion is used, then scheme should also appear, with a value other than free.

3.29. att.timed

att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information]
Moduletei
Membersellipsis gap
Attributes
startindicates the location within a temporal alignment at which this element begins.
StatusOptional
Datatypeteidata.pointer
Note

If no value is supplied, the element is assumed to follow the immediately preceding element at the same hierarchic level.

endindicates the location within a temporal alignment at which this element ends.
StatusOptional
Datatypeteidata.pointer
Note

If no value is supplied, the element is assumed to precede the immediately following element at the same hierarchic level.

3.30. att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 18.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 14.3.2.3. Personal Relationships 12.3.1.1. Core Elements for Transcriptional Work 17.1.1. Pointers and Links 17.3. Blocks, Segments, and Anchors 13.2. Linking the Apparatus to the Text 23.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 24.3.1.3. Modification of Attribute and Attribute Value Lists]
Moduletei
Membersatt.pointing.group[linkGrp] TEI abbr add addSpan altIdentifier anchor bibl change collection date del desc div eventName figure filiation fw g gender graphic head idno join label lb list mapping milestone mod msDesc msName msPart name note pb ptr ref reg relatedItem settlement space table term text title
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
StatusOptional
Datatypeteidata.enumerated
<div type="verse">  <head>Night in Tarras</head>  <lg type="stanza">   <l>At evening tramping on the hot white road</l>   <l></l>  </lg>  <lg type="stanza">   <l>A wind sprang up from nowhere as the sky</l>   <l></l>  </lg> </div>
Note

The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

subtype(subtype) provides a sub-categorization of the element, if needed.
StatusOptional
Datatypeteidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

Schematron
<sch:rule context="tei:*[@subtype]"> <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert> </sch:rule>
Note

When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 24.3.1.3. Modification of Attribute and Attribute Value Lists .

3.31. 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
Membersatt.transcriptional[add addSpan del mod] div figure fw head hi label note p 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.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
teimacro.limitedContent = ( text | teimodel.limitedPhrase | teimodel.inter )*

4.2. 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
teimacro.paraContent = ( text | teimodel.paraPart )*

4.3. macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
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
teimacro.phraseSeq =
   (
      text
    | teimodel.gLike
    | teimodel.attributable
    | teimodel.phrase
    | teimodel.global
   )*

4.4. macro.phraseSeq.limited

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

4.5. macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
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
teimacro.specialPara =
   (
      text
    | teimodel.gLike
    | teimodel.phrase
    | teimodel.inter
    | teimodel.divPart
    | teimodel.global
   )*

4.6. macro.xtext

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

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
teiteidata.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
teiteidata.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
teiteidata.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
teiteidata.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
teidata.genderElement:
Content model
<content>
 <dataRef key="teidata.word"/>
</content>
    
Declaration
teiteidata.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.gender

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

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

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

5.7. teidata.language

teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]
Moduletei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="language"/>
  <valList>
   <valItem ident=""/>
  </valList>
 </alternate>
</content>
    
Declaration
teiteidata.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.8. 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
teiteidata.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.9. 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
teiteidata.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.10. 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
teiteidata.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.11. 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
teiteidata.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.12. 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]+)?)"/>
</content>
    
Declaration
teiteidata.point =
   token { pattern = "(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)" }
Example
<facsimile>  <surface lrx="400lry="280ulx="0uly="0">   <zone points="220,100 300,210 170,250 123,234">    <graphic url="handwriting.png"/>   </zone>  </surface> </facsimile>
Note

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

5.13. 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
teiteidata.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.14. 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
teiteidata.probCert = teidata.probability | teidata.certainty

5.15. 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
teiteidata.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.16. teidata.replacement

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

5.17. 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
teiteidata.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.18. 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
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
teiteidata.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.19. 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
teiteidata.text = string
Note

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

5.20. 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
teiteidata.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.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
teiteidata.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
teiteidata.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
teiteidata.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
teiteidata.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
teiteidata.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.

Date: 2024-05-25