Niklas Luhmann-Archiv: ODD-Dokumentation für die Auszeichnung von bibliographischen Einzeldatensätzen

Table of contents

TEI Customization for bibliographic records 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
versionspecifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

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

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

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

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>The shortest TEI Document Imaginable</title>    </titleStmt>    <publicationStmt>     <p>First published as part of TEI P2, this is the P5          version using a namespace.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <text>   <body>    <p>This is about the shortest TEI document imaginable.</p>   </body>  </text> </TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>A TEI Document containing four page images </title>    </titleStmt>    <publicationStmt>     <p>Unpublished demonstration file.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <facsimile>   <graphic url="page1.png"/>   <graphic url="page2.png"/>   <graphic url="page3.png"/>   <graphic url="page4.png"/>  </facsimile> </TEI>
Content model
<content>
 <sequence>
  <elementRef key="teiHeader"/>
  <alternate>
   <sequence>
    <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.attributes,
   teiatt.typed.attributes,
   attribute version { text }?,
   ( teiteiHeader, ( ( teimodel.resource+, teiTEI* ) | teiTEI+ ) )
}

1.2. <abstract>

<abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
core: listBibl p
namesdates: listObject
Note

This element is intended only for cases where no abstract is available in the original source. Any abstract already present in the source document should be encoded as a <div> within the <front>, as it should for a born-digital document.

Example
<profileDesc>  <abstract resp="#LB">   <p>Good database design involves the acquisition and deployment of      skills which have a wider relevance to the educational process. From      a set of more or less instinctive rules of thumb a formal discipline      or "methodology" of database design has evolved. Applying that      methodology can be of great benefit to a very wide range of academic      subjects: it requires fundamental skills of abstraction and      generalisation and it provides a simple mechanism whereby complex      ideas and information structures can be represented and manipulated,      even without the use of a computer. </p>  </abstract> </profileDesc>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.pLike"/>
  <classRef key="model.listLike"/>
  <elementRef key="listBibl"/>
 </alternate>
</content>
    
Schema Declaration
element abstract
{
   teiatt.global.attributes,
   ( teimodel.pLike | teimodel.listLike | teilistBibl )+
}

1.3. <analytic>

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

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

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

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope>377–380</biblScope>  </monogr> </biblStruct>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="author"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="date"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element analytic
{
   teiatt.global.attributes,
   (
      teiauthor
    | teieditor
    | teirespStmt
    | teititle
    | teimodel.ptrLike
    | teidate
    | teitextLang
    | teiidno
    | teiavailability
   )*
}

1.4. <annotation>

<annotation> represents an annotation following the Web Annotation Data Model. [17.10. The standOff Container]
Modulelinking
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
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
motivation
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
assessing
intent is to assess the target resource in some way, rather than simply make a comment about it
bookmarking
intent is to create a bookmark to the target or part thereof
classifying
intent is to classify the target in some way
commenting
intent is to comment about the target
describing
intent is to describe the target, rather than (for example) comment on it
editing
intent is to request an edit or a change to the target resource
highlighting
intent is to highlight the target resource or a segment thereof
identifying
intent is to assign an identity to the target
linking
intent is to link to a resource related to the target
moderating
intent is to assign some value or quality to the target
questioning
intent is to ask a question about the target
replying
intent is to reply to a previous statement, either an annotation or another resource
tagging
intent is to associate a tag with the target
Note

For further detailed explanation of the suggested values, see the Web Annotation Vocabulary (WAV). The motivations described here map to URIs defined by the WAV and when exported to RDF or JSON-LD must have the URI http://www.w3.org/ns/oa# prepended.

As an RDF vocabulary, WADM permits the definition of new motivations (see Appendix C of the WAV). In TEI, new motivations may be defined in a custom ODD (see section 23.3.1.3). New motivations must also map to URIs defined by an RDF ontology extending the WAV.

Member of
Contained by
May contain
Example
<annotation motivation="linking"  target="#Galliaxml:id="ann1"> <!-- See https://www.w3.org/TR/annotation-model/#lifecycle-information and https://www.w3.org/TR/annotation-model/#agents -->  <respStmt xml:id="fred">   <resp>creator</resp>   <persName>Fred Editor</persName>  </respStmt>  <revisionDesc>   <change status="created"    when="2020-05-21T13:59:00Zwho="#fred"/>   <change status="modified"    when="2020-05-21T19:48:00Zwho="#fred"/>  </revisionDesc> <!-- See https://www.w3.org/TR/annotation-model/#rights-information -->  <licence target="http://creativecommons.org/licenses/by/3.0/"/> <!-- Multiple bodies --> <!-- Pointers to sections of text in the same document -->  <ptr target="#string-range(c1p1s1,0,6)"/>  <ptr target="#string-range(c1p1s6,19,7)"/> </annotation>
Example
<annotation motivation="commenting"  target="#line1xml:id="TheCorrectTitle">  <note>The correct title of this specification, and the correct full name of XML, is    "Extensible Markup Language". "eXtensible Markup Language" is just a spelling error.    However, the abbreviation "XML" is not only correct but, appearing as it does in the title    of the specification, an official name of the Extensible Markup Language. </note> </annotation>
Content model
<content>
 <sequence>
  <elementRef key="respStmt"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="revisionDesc"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="licence"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.annotationPart.body"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element annotation
{
   teiatt.global.attribute.n,
   teiatt.global.attribute.xmllang,
   teiatt.global.attribute.xmlbase,
   teiatt.global.attribute.xmlspace,
   teiatt.global.linking.attribute.corresp,
   teiatt.global.linking.attribute.synch,
   teiatt.global.linking.attribute.sameAs,
   teiatt.global.linking.attribute.copyOf,
   teiatt.global.linking.attribute.next,
   teiatt.global.linking.attribute.prev,
   teiatt.global.linking.attribute.exclude,
   teiatt.global.linking.attribute.select,
   teiatt.global.rendition.attribute.rend,
   teiatt.global.rendition.attribute.style,
   teiatt.global.rendition.attribute.rendition,
   teiatt.global.responsibility.attribute.cert,
   teiatt.global.responsibility.attribute.resp,
   teiatt.global.source.attribute.source,
   teiatt.pointing.attribute.targetLang,
   teiatt.pointing.attribute.evaluate,
   attribute xml:id { text },
   attribute target { list { + } },
   attribute motivation
   {
      list
      {
         (
            "assessing"
          | "bookmarking"
          | "classifying"
          | "commenting"
          | "describing"
          | "editing"
          | "highlighting"
          | "identifying"
          | "linking"
          | "moderating"
          | "questioning"
          | "replying"
          | "tagging"
         )+
      }
   }?,
   (
      teirespStmt*,
      teirevisionDesc*,
      teilicence*,
      teimodel.annotationPart.body*
   )
}

1.5. <appInfo>

<appInfo> (application information) records information about an application which has edited the TEI file. [2.3.11. The Application Information Element]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
header: application
Example
<appInfo>  <application ident="Xairaversion="1.24">   <label>XAIRA Indexer</label>   <ptr target="#P1"/>  </application> </appInfo>
Content model
<content>
 <classRef key="model.applicationLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element appInfo { teiatt.global.attributes, teimodel.applicationLike+ }

1.6. <application>

<application> provides information about an application which has acted upon the document. [2.3.11. The Application Information Element]
Moduleheader
Attributes
identsupplies an identifier for the application, independent of its version number or display name.
StatusRequired
Datatypeteidata.name
versionsupplies a version number for the application, independent of its identifier or display name.
StatusRequired
Datatypeteidata.versionNumber
Member of
Contained by
header: appInfo
May contain
core: p ptr ref
Example
<appInfo>  <application ident="ImageMarkupTool1"   notAfter="2006-06-01version="1.5">   <label>Image Markup Tool</label>   <ptr target="#P1"/>   <ptr target="#P2"/>  </application> </appInfo>
This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two <ptr> elements.
Content model
<content>
 <sequence>
  <classRef key="model.labelLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <alternate>
   <classRef key="model.ptrLike"
    maxOccurs="unbounded" minOccurs="0"/>
   <classRef key="model.pLike"
    maxOccurs="unbounded" minOccurs="0"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element application
{
   teiatt.global.attributes,
   teiatt.datable.attributes,
   teiatt.typed.attributes,
   attribute ident { text },
   attribute version { text },
   ( teimodel.labelLike+, ( teimodel.ptrLike* | teimodel.pLike* ) )
}

1.7. <author>

<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore
Attributes
Member of
Contained by
May contain
Note

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

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

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

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

1.8. <authority>

<authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
Member of
Contained by
core: monogr
May contain
Example
<authority>John Smith</authority>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element authority
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   teimacro.phraseSeq.limited
}

1.9. <availability>

<availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
status(status) supplies a code identifying the current availability of the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
free
(free) the text is freely available.
unknown
(unknown) the status of the text is unknown.
restricted
(restricted) the text is not freely available.
Member of
Contained by
May contain
core: p
header: licence
Note

A consistent format should be adopted

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

1.10. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
May contain
linking: linkGrp
namesdates: listObject
textstructure: div titlePage
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>
  <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 minOccurs="0">
   <sequence>
    <classRef key="model.div1Like"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.frontPart"/>
     <classRef key="model.div1Like"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
   <sequence>
    <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 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
{
   teiatt.global.attributes,
   teiatt.declaring.attributes,
   (
      (
         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.11. <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
DefaultarticlesIncluded,journalItemsIncluded,luhmann-list-view,portal-view,relatedItem,seriesItemsIncluded,sortKey
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.attributes,
   teiatt.canonical.attributes,
   teiatt.cmc.attributes,
   teiatt.declarable.attributes,
   teiatt.docStatus.attributes,
   teiatt.sortable.attributes,
   teiatt.typed.attribute.subtype,
   attribute type { text },
   (
      text
    | teimodel.gLike
    | teimodel.highlighted
    | teimodel.pPart.data
    | teimodel.pPart.edit
    | teimodel.segLike
    | teimodel.ptrLike
    | teimodel.biblPart
    | teimodel.global
   )*
}

1.12. <biblFull>

<biblFull> (fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2. The File Description 2.2.7. The Source Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
May contain
Example
<biblFull>  <titleStmt>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>  </titleStmt>  <editionStmt>   <edition>UK edition</edition>  </editionStmt>  <extent>1231 pp</extent>  <publicationStmt>   <publisher>Yale University Press</publisher>   <pubPlace>New Haven and London</pubPlace>   <date>1990</date>  </publicationStmt>  <sourceDesc>   <p>No source: this is an original work</p>  </sourceDesc> </biblFull>
Content model
<content>
 <alternate>
  <sequence>
   <sequence>
    <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="0"/>
  </sequence>
  <sequence>
   <elementRef key="fileDesc"/>
   <elementRef key="profileDesc"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element biblFull
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   teiatt.cmc.attributes,
   teiatt.declarable.attributes,
   teiatt.docStatus.attributes,
   teiatt.sortable.attributes,
   (
      (
         (
            teititleStmt,
            teieditionStmt?,
            teiextent?,
            teipublicationStmt,
            teiseriesStmt*,
            teinotesStmt?
         ),
         teisourceDesc*
      )
    | ( teifileDesc, teiprofileDesc )
   )
}

1.13. <biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
Derived fromatt.citing
StatusOptional
Datatypeteidata.enumerated
Legal values are:
volume
Einzelband/Jahrgangsnummer bei Zeitschriften
issue
Nummer
page
Seitensequenz
chapter
Kapitel
part
Teil
column
Spaltensequenz
Member of
Contained by
May contain
Note

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

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

Example
<biblScope>pp 12–34</biblScope> <biblScope from="12to="34unit="page"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element biblScope
{
   teiatt.global.attributes,
   teiatt.citing.attribute.from,
   teiatt.citing.attribute.to,
   attribute unit
   {
      "volume" | "issue" | "page" | "chapter" | "part" | "column"
   }?,
   teimacro.phraseSeq
}

1.14. <biblStruct>

<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
book
Monographien
bookSection
Abschnitte/Artikel in Monographien
journal
Sammelpublikation/Periodikum
journalArticle
Artikel in Sammelpublikation und Periodika
series
Reihe/Mehrbändiges Werk
book_periodical
soll werden zu series-sub-vol
newspaper
Taggeszeitung
newspaperArticle
Artikel in Taggeszeitung
webPublication
Webpublikation
grey
Graue Literatur
werk
Werk
typescript
Typoskript
manuscript
Manuskript
audio-video
Audio- oder Videodatei
subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
Keine Unterklassifikation vergeben
nl-anthology
bookSections tragen diesen subtype, wenn es sich um Aufsätze Luhmanns handelt, die in einem Sammelband von Luhmann selbst erschienen sind (Feinspezifikation in Luhmann-Publikationen)
misc
Miscellaneous (interviews, discussions, bibliographies, introductions to books of other authors, letters, obituaries et al (Feinspezifikation in Luhmann-Publikationen)
review
Reviews (Feinspezifikation in Luhmann-Publikationen)
journal-special
Sonderband einer Zeitschrift
journalArticle-special
Artikel in Zeitschriftensonderheft (strukturell wie bookSection)
web_journal
web_journal
webjournalArticle
Artikel in webJournal
monography
Monographie (Feinspezifikation in Luhmann-Publikationen)
anthology
Sammelband (Feinspezifikation in Luhmann-Publikationen)
series-sub-vol
Einzelband einer Reihe/Mehrbändigen Werks
typewriter
Typoskript-Untertyp: schreibmaschinengeschrieben
computer
Typoskript-Untertyp: computergeschrieben
audio
Audio-Video-Untertyp: Audiodatei
video
Audio-Video-Untertyp: Videodatei
book
series erhalten diesen subtype, wenn es sich um eine mehrbändige Buchreihe handelt
article
series erhalten diesen subtype, wenn es sich um eine Reihe von (aneinander anschließenden) Aufsätzen handelt
Member of
Contained by
May contain
Example
<biblStruct>  <monogr>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <edition>first edition</edition>   <imprint>    <publisher>Yale University Press</publisher>    <pubPlace>New Haven and London</pubPlace>    <date>1990</date>   </imprint>  </monogr> </biblStruct>
Example
<biblStruct type="newspaper">  <analytic>   <author>    <forename>David</forename>    <surname>Barstow</surname>   </author>   <author>    <forename>Susanne</forename>    <surname>Craig</surname>   </author>   <author>    <forename>Russ</forename>    <surname>Buettner</surname>   </author>   <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>   <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>  </analytic>  <monogr>   <title level="j">The New York Times</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>A. G. Sulzberger</publisher>    <date when="2018-10-03">Wednesday, October 3, 2018</date>   </imprint>   <biblScope unit="volume">CLXVIII</biblScope>   <biblScope unit="issue">58,104</biblScope>   <biblScope unit="page">1</biblScope>  </monogr> </biblStruct>
Content model
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="analytic"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="monogr"/>
   <elementRef key="series"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element biblStruct
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   teiatt.cmc.attributes,
   teiatt.declarable.attributes,
   teiatt.docStatus.attributes,
   teiatt.sortable.attributes,
   attribute type
   {
      "book"
    | "bookSection"
    | "journal"
    | "journalArticle"
    | "series"
    | "book_periodical"
    | "newspaper"
    | "newspaperArticle"
    | "webPublication"
    | "grey"
    | "werk"
    | "typescript"
    | "manuscript"
    | "audio-video"
   },
   attribute subtype
   {
      "none"
    | "nl-anthology"
    | "misc"
    | "review"
    | "journal-special"
    | "journalArticle-special"
    | "web_journal"
    | "webjournalArticle"
    | "monography"
    | "anthology"
    | "series-sub-vol"
    | "typewriter"
    | "computer"
    | "audio"
    | "video"
    | "book"
    | "article"
   }?,
   (
      teianalytic*,
      ( ( teimonogr, teiseries* )+ ),
      ( teimodel.noteLike | teimodel.ptrLike | teirelatedItem | teicitedRange )*
   )
}

1.15. <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
May contain
header: biblFull
linking: linkGrp
namesdates: listObject
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>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence minOccurs="0">
   <classRef key="model.divTop"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0">
   <classRef key="model.divGenLike"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate>
   <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>
    <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 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
{
   teiatt.global.attributes,
   teiatt.declaring.attributes,
   (
      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.16. <cRefPattern>

<cRefPattern> (canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
Moduleheader
Attributes
Contained by
header: refsDecl
May contain
core: p
Note

The result of the substitution may be either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the cRef attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

Example
<cRefPattern matchPattern="([1-9A-Za-z]+)\s+([0-9]+):([0-9]+)"  replacementPattern="#xpath(//div[@type='book'][@n='$1']/div[@type='chap'][@n='$2']/div[@type='verse'][@n='$3'])"/>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
    
Schema Declaration
element cRefPattern
{
   teiatt.global.attributes,
   teiatt.patternReplacement.attributes,
   teimodel.pLike*
}

1.17. <calendar>

<calendar> (calendar) describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description]
Moduleheader
Attributes
Contained by
header: calendarDesc
May contain
core: p
Example
<calendarDesc>  <calendar xml:id="julianEngland">   <p>Julian Calendar (including proleptic)</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar target="http://en.wikipedia.org/wiki/Egyptian_calendar"   xml:id="egyptian">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element calendar
{
   teiatt.global.attributes,
   teiatt.pointing.attributes,
   teiatt.typed.attributes,
   teimodel.pLike+
}

1.18. <calendarDesc>

<calendarDesc> (calendar description) contains a description of the calendar system used in any dating expression found in the text. [2.4. The Profile Description 2.4.5. Calendar Description]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
header: calendar
Note

In the first example above, calendars and short codes for xml:ids are from W3 guidelines at http://www.w3.org/TR/xpath-functions-11/#lang-cal-country

Example
<calendarDesc>  <calendar xml:id="cal_AD">   <p>Anno Domini (Christian Era)</p>  </calendar>  <calendar xml:id="cal_AH">   <p>Anno Hegirae (Muhammedan Era)</p>  </calendar>  <calendar xml:id="cal_AME">   <p>Mauludi Era (solar years since Mohammed's birth)</p>  </calendar>  <calendar xml:id="cal_AM">   <p>Anno Mundi (Jewish Calendar)</p>  </calendar>  <calendar xml:id="cal_AP">   <p>Anno Persici</p>  </calendar>  <calendar xml:id="cal_AS">   <p>Aji Saka Era (Java)</p>  </calendar>  <calendar xml:id="cal_BE">   <p>Buddhist Era</p>  </calendar>  <calendar xml:id="cal_CB">   <p>Cooch Behar Era</p>  </calendar>  <calendar xml:id="cal_CE">   <p>Common Era</p>  </calendar>  <calendar xml:id="cal_CL">   <p>Chinese Lunar Era</p>  </calendar>  <calendar xml:id="cal_CS">   <p>Chula Sakarat Era</p>  </calendar>  <calendar xml:id="cal_EE">   <p>Ethiopian Era</p>  </calendar>  <calendar xml:id="cal_FE">   <p>Fasli Era</p>  </calendar>  <calendar xml:id="cal_ISO">   <p>ISO 8601 calendar</p>  </calendar>  <calendar xml:id="cal_JE">   <p>Japanese Calendar</p>  </calendar>  <calendar xml:id="cal_KE">   <p>Khalsa Era (Sikh calendar)</p>  </calendar>  <calendar xml:id="cal_KY">   <p>Kali Yuga</p>  </calendar>  <calendar xml:id="cal_ME">   <p>Malabar Era</p>  </calendar>  <calendar xml:id="cal_MS">   <p>Monarchic Solar Era</p>  </calendar>  <calendar xml:id="cal_NS">   <p>Nepal Samwat Era</p>  </calendar>  <calendar xml:id="cal_OS">   <p>Old Style (Julian Calendar)</p>  </calendar>  <calendar xml:id="cal_RS">   <p>Rattanakosin (Bangkok) Era</p>  </calendar>  <calendar xml:id="cal_SE">   <p>Saka Era</p>  </calendar>  <calendar xml:id="cal_SH">   <p>Mohammedan Solar Era (Iran)</p>  </calendar>  <calendar xml:id="cal_SS">   <p>Saka Samvat</p>  </calendar>  <calendar xml:id="cal_TE">   <p>Tripurabda Era</p>  </calendar>  <calendar xml:id="cal_VE">   <p>Vikrama Era</p>  </calendar>  <calendar xml:id="cal_VS">   <p>Vikrama Samvat Era</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="cal_Gregorian">   <p>Gregorian calendar</p>  </calendar>  <calendar xml:id="cal_Julian">   <p>Julian calendar</p>  </calendar>  <calendar xml:id="cal_Islamic">   <p>Islamic or Muslim (hijri) lunar calendar</p>  </calendar>  <calendar xml:id="cal_Hebrew">   <p>Hebrew or Jewish lunisolar calendar</p>  </calendar>  <calendar xml:id="cal_Revolutionary">   <p>French Revolutionary calendar</p>  </calendar>  <calendar xml:id="cal_Iranian">   <p>Iranian or Persian (Jalaali) solar calendar</p>  </calendar>  <calendar xml:id="cal_Coptic">   <p>Coptic or Alexandrian calendar</p>  </calendar>  <calendar xml:id="cal_Chinese">   <p>Chinese lunisolar calendar</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar target="http://en.wikipedia.org/wiki/Egyptian_calendar"   xml:id="cal_Egyptian">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
Content model
<content>
 <elementRef key="calendar"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element calendarDesc { teiatt.global.attributes, teicalendar+ }

1.19. <catDesc>

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

1.20. <catRef>

<catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]
Moduleheader
Attributes
schemeidentifies the classification scheme within which the set of categories concerned is defined, for example by a <taxonomy> element, or by some other resource.
StatusOptional
Datatypeteidata.pointer
Contained by
core: imprint
header: textClass
May containEmpty element
Note

The scheme attribute needs to be supplied only if more than one taxonomy has been declared.

Example
<catRef scheme="#myTopics"  target="#news #prov #sales2"/> <!-- elsewhere --> <taxonomy xml:id="myTopics">  <category xml:id="news">   <catDesc>Newspapers</catDesc>  </category>  <category xml:id="prov">   <catDesc>Provincial</catDesc>  </category>  <category xml:id="sales2">   <catDesc>Low to average annual sales</catDesc>  </category> </taxonomy>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element catRef
{
   teiatt.global.attributes,
   teiatt.pointing.attributes,
   attribute scheme { text }?,
   empty
}

1.21. <category>

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
Contained by
May contain
Example
<category xml:id="b1">  <catDesc>Prose reportage</catDesc> </category>
Example
<category xml:id="b2">  <catDesc>Prose </catDesc>  <category xml:id="b11">   <catDesc>journalism</catDesc>  </category>  <category xml:id="b12">   <catDesc>fiction</catDesc>  </category> </category>
Example
<category xml:id="LIT">  <catDesc xml:lang="pl">literatura piękna</catDesc>  <catDesc xml:lang="en">fiction</catDesc>  <category xml:id="LPROSE">   <catDesc xml:lang="pl">proza</catDesc>   <catDesc xml:lang="en">prose</catDesc>  </category>  <category xml:id="LPOETRY">   <catDesc xml:lang="pl">poezja</catDesc>   <catDesc xml:lang="en">poetry</catDesc>  </category>  <category xml:id="LDRAMA">   <catDesc xml:lang="pl">dramat</catDesc>   <catDesc xml:lang="en">drama</catDesc>  </category> </category>
Content model
<content>
 <sequence>
  <alternate>
   <elementRef key="catDesc"
    maxOccurs="unbounded" minOccurs="1"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.descLike"/>
    <elementRef key="equiv"/>
    <elementRef key="gloss"/>
   </alternate>
  </alternate>
  <elementRef key="category"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element category
{
   teiatt.global.attributes,
   teiatt.datcat.attributes,
   ( ( teicatDesc+ | ( teimodel.descLike | equiv | gloss )* ), teicategory* )
}

1.22. <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
Legal values are:
base_1
Datensatz neu angelegt
ready-for-publication
Datensatz geprüft und zur Publikation freigegeben
target(target) points to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
May contain
Note

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

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

Example
<titleStmt>  <title> ... </title>  <editor xml:id="LDB">Lou Burnard</editor>  <respStmt xml:id="BZ">   <resp>copy editing</resp>   <name>Brett Zamir</name>  </respStmt> </titleStmt> <!-- ... --> <revisionDesc status="published">  <change status="publicwhen="2008-02-02"   who="#BZ">Finished chapter 23</change>  <change status="draftwhen="2008-01-02"   who="#BZ">Finished chapter 2</change>  <change n="P2.2when="1991-12-21"   who="#LDB">Added examples to section 3</change>  <change when="1991-11-11who="#MSM">Deleted chapter 10</change> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange>    <change xml:id="DRAFT1">First draft in pencil</change>    <change notBefore="1880-12-09"     xml:id="DRAFT2">First revision, mostly        using green ink</change>    <change notBefore="1881-02-13"     xml:id="DRAFT3">Final corrections as        supplied to printer.</change>   </listChange>  </creation> </profileDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element change
{
   teiatt.global.attribute.xmlid,
   teiatt.global.attribute.xmllang,
   teiatt.global.attribute.xmlbase,
   teiatt.global.attribute.xmlspace,
   teiatt.global.linking.attribute.corresp,
   teiatt.global.linking.attribute.synch,
   teiatt.global.linking.attribute.sameAs,
   teiatt.global.linking.attribute.copyOf,
   teiatt.global.linking.attribute.next,
   teiatt.global.linking.attribute.prev,
   teiatt.global.linking.attribute.exclude,
   teiatt.global.linking.attribute.select,
   teiatt.global.rendition.attribute.rend,
   teiatt.global.rendition.attribute.style,
   teiatt.global.rendition.attribute.rendition,
   teiatt.global.responsibility.attribute.cert,
   teiatt.global.responsibility.attribute.resp,
   teiatt.global.source.attribute.source,
   teiatt.ascribed.attributes,
   teiatt.datable.attributes,
   teiatt.docStatus.attributes,
   teiatt.typed.attributes,
   attribute n { "base_1" | "ready-for-publication" },
   attribute target { list { + } }?,
   teimacro.specialPara
}

1.23. <citeData>

<citeData> (citation data) specifies how information may be extracted from citation structures. [3.11.4. Declaring Reference Systems 17.2.5.4. Citation Structures]
Moduleheader
Attributes
property(property) A URI indicating a property definition.
StatusRequired
Datatypeteidata.pointer
Contained by
May containEmpty element
Example
<citeStructure match="//body/div"  unit="bookuse="@n">  <citeData property="http://purl.org/dc/terms/title"   use="head"/> </citeStructure>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element citeData
{
   teiatt.global.attributes,
   teiatt.citeStructurePart.attributes,
   attribute property { text },
   empty
}

1.24. <citeStructure>

<citeStructure> (citation structure) declares a structure and method for citing the current document. [3.11.4. Declaring Reference Systems 17.2.5.4. Citation Structures]
Moduleheader
Attributes
delim(delimiter) supplies a delimiting string preceding the structural component.
StatusOptional
Datatypestring
Note

delim must contain at least one character.

match(match) supplies an XPath selection pattern using the syntax defined in [[undefined XSLT3]] which identifies a set of nodes which are citable structural components. The expression may be absolute (beginning with /) or relative. match on a <citeStructure> without a <citeStructure> parent must be an absolute XPath. If it is relative, its context is set by the match of the parent <citeStructure>.
StatusRequired
Datatypeteidata.xpath
Schematron
<sch:rule context="tei:citeStructure[not(parent::tei:citeStructure)]"> <sch:assert test="starts-with(@match,'/')">An XPath in @match on the outer <sch:name/> must start with '/'.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:citeStructure[parent::tei:citeStructure]"> <sch:assert test="not(starts-with(@match,'/'))">An XPath in @match must not start with '/' except on the outer <sch:name/>.</sch:assert> </sch:rule>
unit(unit) describes the structural unit indicated by the <citeStructure>.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
book
chapter
entry
poem
letter
line
section
verse
volume
Contained by
May contain
Example
<citeStructure match="//body/div"  unit="bookuse="@n">  <citeStructure delim=" match="div"   unit="chapteruse="position()">   <citeStructure delim=":match="div"    unit="verseuse="position()"/>  </citeStructure> </citeStructure>
Content model
<content>
 <sequence>
  <elementRef key="citeData"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="citeStructure"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.descLike"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element citeStructure
{
   teiatt.global.attributes,
   teiatt.citeStructurePart.attributes,
   attribute delim { text }?,
   attribute match { text },
   attribute unit { text }?,
   ( teiciteData*, teiciteStructure*, teimodel.descLike* )
}

1.25. <citedRange>

<citedRange> (cited range) defines the range of cited content, often represented by pages or other units. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
Derived fromatt.citing
StatusOptional
Datatypeteidata.enumerated
Legal values are:
page
Seiten
column
Spalten
volume
Bandnummer
Member of
Contained by
May contain
Note

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

Example
<citedRange>pp 12–13</citedRange> <citedRange from="12to="13unit="page"/> <citedRange unit="volume">II</citedRange> <citedRange unit="page">12</citedRange>
Example
<bibl>  <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.    4-5</citedRange> </bibl>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element citedRange
{
   teiatt.global.attributes,
   teiatt.citing.attribute.from,
   teiatt.citing.attribute.to,
   teiatt.pointing.attributes,
   attribute unit { "page" | "column" | "volume" }?,
   teimacro.phraseSeq
}

1.26. <classCode>

<classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]
Moduleheader
Attributes
schemeidentifies the classification system in use, as defined by, e.g. a <taxonomy> element, or some other resource.
StatusRequired
Datatypeteidata.pointer
Contained by
core: imprint
header: textClass
May contain
Example
<classCode scheme="http://www.udc.org">410</classCode>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element classCode
{
   teiatt.global.attributes,
   attribute scheme { text },
   teimacro.phraseSeq.limited
}

1.27. <classDecl>

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

1.28. <conversion>

<conversion> defines how to calculate one unit of measure in terms of another. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
fromUnitindicates a source unit of measure that is to be converted into another unit indicated in toUnit.
StatusRequired
Datatypeteidata.pointer
toUnitthe target unit of measurement for a conversion from a source unit referenced in fromUnit.
StatusRequired
Datatypeteidata.pointer
Contained by
header: unitDef
May containEmpty element
Note

The conversion element is designed to store information about converting from one unit of measurement to another. The formula attribute holds an XPath expression that indicates how the measurement system in fromUnit is converted to the system in toUnit. Do not confuse the usage of the dating attributes (from and to) in the examples with the attributes (fromUnit and toUnit) designed to reference units of measure.

Example
<conversion formula="$fromUnit * 12"  from="1707fromUnit="#shillingto="1971"  toUnit="#pence"/>
Example
<conversion formula="$fromUnit * 20"  from="1701fromUnit="#poundto="1971"  toUnit="#shilling"/>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element conversion
{
   teiatt.global.attributes,
   teiatt.datable.attributes,
   teiatt.formula.attributes,
   teiatt.locatable.attributes,
   attribute fromUnit { text },
   attribute toUnit { text },
   empty
}

1.29. <correction>

<correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
statusindicates the degree of correction applied to the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
high
the text has been thoroughly checked and proofread.
medium
the text has been checked at least once.
low
the text has not been checked.
unknown
the correction status of the text is unknown.
methodindicates the method adopted to indicate corrections within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
corrections have been made silently[Default]
markup
corrections have been represented using markup
Member of
Contained by
May contain
core: p
Note

May be used to note the results of proof reading the text against its original, indicating (for example) whether discrepancies have been silently rectified, or recorded using the editorial tags described in section 3.5. Simple Editorial Changes.

Example
<correction>  <p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user    defined dictionary of 500 extra words taken from Chambers Twentieth Century    Dictionary.</p> </correction>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element correction
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   attribute status { "high" | "medium" | "low" | "unknown" }?,
   attribute method { "silent" | "markup" }?,
   teimodel.pLike+
}

1.30. <correspAction>

<correspAction> (correspondence action) contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
typedescribes the nature of the action.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
sent
information concerning the sending or dispatch of a message.
received
information concerning the receipt of a message.
transmitted
information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding.
redirected
information concerning the redirection of an unread message.
forwarded
information concerning the forwarding of a message.
Member of
Contained by
header: correspDesc
May contain
Example
<correspAction type="sent">  <persName>Adelbert von Chamisso</persName>  <settlement>Vertus</settlement>  <date when="1807-01-29"/> </correspAction>
Content model
<content>
 <alternate>
  <classRef key="model.correspActionPart"
   maxOccurs="unbounded" minOccurs="1"/>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element correspAction
{
   teiatt.global.attributes,
   teiatt.sortable.attributes,
   teiatt.typed.attribute.subtype,
   attribute type
   {
      "sent" | "received" | "transmitted" | "redirected" | "forwarded"
   }?,
   ( teimodel.correspActionPart+ | teimodel.pLike+ )
}

1.31. <correspContext>

<correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
Member of
Contained by
header: correspDesc
May contain
Example
<correspContext>  <ptr subtype="toAuthor"   target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief101VarnhagenanBoeckhtype="next"/>  <ptr subtype="fromAuthor"   target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief103BoeckhanVarnhagentype="prev"/> </correspContext>
Example
<correspContext>  <ref target="http://weber-gesamtausgabe.de/A040962"   type="prev"> Previous letter of  <persName>Carl Maria von Weber</persName> to  <persName>Caroline Brandt</persName>:  <date when="1816-12-30">December 30, 1816</date>  </ref>  <ref target="http://weber-gesamtausgabe.de/A041003"   type="next"> Next letter of  <persName>Carl Maria von Weber</persName> to  <persName>Caroline Brandt</persName>:  <date when="1817-01-05">January 5, 1817</date>  </ref> </correspContext>
Content model
<content>
 <classRef key="model.correspContextPart"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element correspContext
{
   teiatt.global.attributes,
   teimodel.correspContextPart+
}

1.32. <correspDesc>

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

1.33. <creation>

<creation> (creation) contains information about the creation of a text. [2.4.1. Creation 2.4. The Profile Description]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
Note

The <creation> element may be used to record details of a text's creation, e.g. the date and place it was composed, if these are of interest.

It may also contain a more structured account of the various stages or revisions associated with the evolution of a text; this should be encoded using the <listChange> element. It should not be confused with the <publicationStmt> element, which records date and place of publication.

Example
<creation>  <date>Before 1987</date> </creation>
Example
<creation>  <date when="1988-07-10">10 July 1988</date> </creation>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <elementRef key="listChange"/>
 </alternate>
</content>
    
Schema Declaration
element creation
{
   teiatt.global.attributes,
   teiatt.datable.attributes,
   ( text | teimodel.limitedPhrase | teilistChange )*
}

1.34. <date>

<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates]
Modulecore
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Derived fromatt.datable.w3c
StatusOptional
Datatypeteidata.temporal.w3c
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
posting
Erstellungsdatum der Webressource
access
Datum des letzten Zugriffs auf die Webressource
pubYear
Erscheinungsjahr
origYear
Erstellungsjahr
hectographYear
Veröffentlichungsjahr bei sog. grauen Papieren, in hektographierter Form
pubDate
Tag des Erscheinens (z.B. bei Zeitungartikel, aber auch Webpublikationen)
created
Erstellungsdatum des Datensatzes
workSpan
Werk-Entstehungsjahr/-spanne
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.global.attributes,
   teiatt.calendarSystem.attributes,
   teiatt.canonical.attributes,
   teiatt.cmc.attributes,
   teiatt.datable.attribute.period,
   teiatt.datable.custom.attribute.when-custom,
   teiatt.datable.custom.attribute.notBefore-custom,
   teiatt.datable.custom.attribute.notAfter-custom,
   teiatt.datable.custom.attribute.from-custom,
   teiatt.datable.custom.attribute.to-custom,
   teiatt.datable.custom.attribute.datingPoint,
   teiatt.datable.custom.attribute.datingMethod,
   teiatt.datable.iso.attribute.when-iso,
   teiatt.datable.iso.attribute.notBefore-iso,
   teiatt.datable.iso.attribute.notAfter-iso,
   teiatt.datable.iso.attribute.from-iso,
   teiatt.datable.iso.attribute.to-iso,
   teiatt.datable.w3c.attribute.notBefore,
   teiatt.datable.w3c.attribute.notAfter,
   teiatt.datable.w3c.attribute.from,
   teiatt.datable.w3c.attribute.to,
   teiatt.dimensions.attributes,
   teiatt.editLike.attributes,
   teiatt.typed.attribute.subtype,
   attribute when { text }?,
   attribute type
   {
      "posting"
    | "access"
    | "pubYear"
    | "origYear"
    | "hectographYear"
    | "pubDate"
    | "created"
    | "workSpan"
   }?,
   ( text | teimodel.gLike | teimodel.phrase | teimodel.global )*
}

1.35. <distributor>

<distributor> (distributor) supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
Member of
Contained by
May contain
Example
<distributor>Oxford Text Archive</distributor> <distributor>Redwood and Burn Ltd</distributor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element distributor
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   teimacro.phraseSeq
}

1.36. <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: back body div front
May contain
header: biblFull
linking: linkGrp
namesdates: listObject
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>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <alternate>
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
    <sequence>
     <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>
       <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.attributes,
   teiatt.declaring.attributes,
   teiatt.divLike.attributes,
   teiatt.placement.attributes,
   teiatt.typed.attributes,
   teiatt.written.attributes,
   (
      ( 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.37. <divGen>

<divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.9.2. Index Entries]
Modulecore
Attributes
typespecifies what type of generated text division (e.g. index, table of contents, etc.) is to appear.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
index
an index is to be generated and inserted at this point.
toc
a table of contents
figlist
a list of figures
tablist
a list of tables
Note

Valid values are application-dependent; those shown are of obvious utility in document production, but are by no means exhaustive.

Member of
Contained by
textstructure: back body div front
May containEmpty element
Note

This element is intended primarily for use in document production or manipulation, rather than in the transcription of pre-existing materials; it makes it easier to specify the location of indices, tables of contents, etc., to be generated by text preparation or word processing software.

ExampleOne use for this element is to allow document preparation software to generate an index and insert it in the appropriate place in the output. The example below assumes that the indexName attribute on <index> elements in the text has been used to specify index entries for the two generated indexes, named NAMES and THINGS:
<back>  <div1 type="backmat">   <head>Bibliography</head> <!-- ... -->  </div1>  <div1 type="backmat">   <head>Indices</head>   <divGen n="Index Nominumtype="NAMES"/>   <divGen n="Index Rerumtype="THINGS"/>  </div1> </back>
ExampleAnother use for <divGen> is to specify the location of an automatically produced table of contents:
<front> <!--<titlePage>...</titlePage>-->  <divGen type="toc"/>  <div>   <head>Preface</head>   <p> ... </p>  </div> </front>
Content model
<content>
 <classRef key="model.headLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
    
Schema Declaration
element divGen
{
   teiatt.global.attributes,
   teiatt.typed.attribute.subtype,
   attribute type { text }?,
   teimodel.headLike*
}

1.38. <edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Moduleheader
Attributes
Member of
Contained by
core: bibl monogr
header: editionStmt
May contain
Example
<edition>First edition <date>Oct 1990</date> </edition> <edition n="S2">Students' edition</edition>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element edition { teiatt.global.attributes, teimacro.phraseSeq }

1.39. <editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
May contain
Example
<editionStmt>  <edition n="S2">Students' edition</edition>  <respStmt>   <resp>Adapted by </resp>   <name>Elizabeth Kirk</name>  </respStmt> </editionStmt>
Example
<editionStmt>  <p>First edition, <date>Michaelmas Term, 1991.</date>  </p> </editionStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence>
   <elementRef key="edition"/>
   <classRef key="model.respLike"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element editionStmt
{
   teiatt.global.attributes,
   ( teimodel.pLike+ | ( teiedition, teimodel.respLike* ) )
}

1.40. <editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
Member of
Contained by
May contain
Note

A consistent format should be adopted.

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.

Example
<editor role="Technical_Editor">Ron Van den Branden</editor> <editor role="Editor-in-Chief">John Walsh</editor> <editor role="Managing_Editor">Anne Baillot</editor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element editor
{
   teiatt.global.attributes,
   teiatt.datable.attributes,
   teiatt.naming.attributes,
   teimacro.phraseSeq
}

1.41. <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
Attributes
Member of
Contained by
header: encodingDesc
May contain
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
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   ( teimodel.pLike | teimodel.editorialDeclPart )+
}

1.42. <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 containEmpty element
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,
   ( metamark, teimodel.descLike?, supplied? )
}

1.43. <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.attributes,
   ( teimodel.encodingDescPart | teimodel.pLike )+
}

1.44. <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.45. <extent>

<extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.7.1. Object Description]
Moduleheader
Attributes
Member of
Contained by
May contain
Example
<extent>3200 sentences</extent> <extent>between 10 and 20 Mb</extent> <extent>ten 3.5 inch high density diskettes</extent>
ExampleThe <measure> element may be used to supply normalized or machine tractable versions of the size or sizes concerned.
<extent>  <measure quantity="4.2unit="MiB">About four megabytes</measure>  <measure quantity="245unit="pages">245 pages of source    material</measure> </extent>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element extent { teiatt.global.attributes, teimacro.phraseSeq }

1.46. <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
Attributes
Contained by
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>
  <sequence>
   <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
{
   teiatt.global.attributes,
   (
      (
         teititleStmt,
         teieditionStmt?,
         teiextent?,
         teipublicationStmt,
         teiseriesStmt*,
         teinotesStmt?
      ),
      teisourceDesc+
   )
}

1.47. <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:
zh
Chinesisch
ja
Japanisch
el
Modern Greek (1453-)
he
Hebrew
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.global.attribute.xmlid,
   teiatt.global.attribute.n,
   teiatt.global.attribute.xmlbase,
   teiatt.global.attribute.xmlspace,
   teiatt.global.linking.attribute.corresp,
   teiatt.global.linking.attribute.synch,
   teiatt.global.linking.attribute.sameAs,
   teiatt.global.linking.attribute.copyOf,
   teiatt.global.linking.attribute.next,
   teiatt.global.linking.attribute.prev,
   teiatt.global.linking.attribute.exclude,
   teiatt.global.linking.attribute.select,
   teiatt.global.rendition.attribute.rend,
   teiatt.global.rendition.attribute.style,
   teiatt.global.rendition.attribute.rendition,
   teiatt.global.responsibility.attribute.cert,
   teiatt.global.responsibility.attribute.resp,
   teiatt.global.source.attribute.source,
   teiatt.cmc.attributes,
   attribute xml:lang { "zh" | "ja" | "el" | "he" },
   teimacro.phraseSeq
}

1.48. <forename>

<forename> (forename) contains a forename, given or baptismal name. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <roleName>Ex-President</roleName>  <forename>George</forename>  <surname>Bush</surname> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element forename
{
   teiatt.global.attributes,
   teiatt.cmc.attributes,
   teiatt.personal.attributes,
   teiatt.typed.attributes,
   teimacro.phraseSeq
}

1.49. <front>

<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: text
May contain
linking: linkGrp
textstructure: div titlePage
Note

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

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

1.50. <funder>

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
Moduleheader
Attributes
Member of
Contained by
May contain
Note

Funders provide financial support for a project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support and authority.

Example
<funder>The National Endowment for the Humanities, an independent federal agency</funder> <funder>Directorate General XIII of the Commission of the European Communities</funder> <funder>The Andrew W. Mellon Foundation</funder> <funder>The Social Sciences and Humanities Research Council of Canada</funder>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element funder
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   teiatt.datable.attributes,
   teimacro.phraseSeq.limited
}

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

Member of
Contained by
namesdates: persona
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.52. <geoDecl>

<geoDecl> (geographic coordinates declaration) documents the notation and the datum used for geographic coordinates expressed as content of the <geo> element elsewhere within the document. [2.3.8. The Geographic Coordinates Declaration]
Moduleheader
Attributes
datumsupplies a commonly used code name for the datum employed.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
WGS84
(World Geodetic System) a pair of numbers to be interpreted as latitude followed by longitude according to the World Geodetic System.[Default]
MGRS
(Military Grid Reference System) values supplied follow the Military Grid Reference System, which designates grid zones in a string of letters and numbers that distinctly indicate each square meter on the planet.
OSGB36
(ordnance survey great britain) the value supplied is to be interpreted as a British National Grid Reference.
ED50
(European Datum coordinate system) the value supplied is to be interpreted as latitude followed by longitude according to the European Datum coordinate system.
Member of
Contained by
header: encodingDesc
May contain
Example
<geoDecl datum="OSGB36"/>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element geoDecl
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   attribute datum { "WGS84" | "MGRS" | "OSGB36" | "ED50" }?,
   teimacro.phraseSeq
}

1.53. <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 containEmpty element
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.global.attributes,
   teiatt.cmc.attributes,
   teiatt.declaring.attributes,
   teiatt.media.attributes,
   teiatt.resourced.attributes,
   teiatt.typed.attributes,
   teimodel.descLike*
}

1.54. <handNote>

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

1.55. <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
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.global.attributes,
   teiatt.cmc.attributes,
   teiatt.written.attributes,
   teimacro.paraContent
}

1.56. <hyphenation>

<hyphenation> (hyphenation) summarizes the way in which hyphenation in a source text has been treated in an encoded version of it. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
eol(end-of-line) indicates whether or not end-of-line hyphenation has been retained in a text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
all
all end-of-line hyphenation has been retained, even though the lineation of the original may not have been.
some
end-of-line hyphenation has been retained in some cases.[Default]
hard
all soft end-of-line hyphenation has been removed: any remaining end-of-line hyphenation should be retained.
none
all end-of-line hyphenation has been removed: any remaining hyphenation occurred within the line.
Member of
Contained by
May contain
core: p
Example
<hyphenation eol="some">  <p>End-of-line hyphenation silently removed where appropriate</p> </hyphenation>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element hyphenation
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   attribute eol { "all" | "some" | "hard" | "none" }?,
   teimodel.pLike+
}

1.57. <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:
URI
Uniform Resource Identifier (z.B. Permalink Worldcat)
GND
Gemeinsame Normdatei (GND)
ISSN
International Standard Serial Number
ISBN
International Standard Book Number
DOI
Digital Object Identifier System
URL
URL
ZDB-ID
ZDB-ID in Datenbank der Zeitschriftendatenbank (ZDB) - http://www.zeitschriftendatenbank.de/
luhmann-ID
Interne innerhalb des Luhmann Projektes definierte ID
Niklas-Luhmann-Bibliographie
In der Bibliographie der Luhamnnschen Publikationen (Niklas-Luhmann-Bibliographie) intern genutzte ID. Wird angereichert (luhmann_) und als übergreifende Projekt-ID in das übergeordnete biblStruct-Element übernommen.
Niklas-Luhmann-Erstausgabe
ist Teil des Niklas-Luhmann-Erstausgabeses (Erstdrucke u.ä.)
neu
Neu angelegter bibliographischer Datensatz - temporärer Wert
Niklas-Luhmann-Arbeitsbibliothek
Exemplar(e) der Publikation in Luhmanns Arbeitsbibliothek
Niklas-Luhmann-Arbeitsbibliothek-Marker
Temporärer Marker: Exemplar(e) der Publikation in Luhmanns Arbeitsbibliothek
shelfmark
Signatur
Niklas-Luhmann-Werk
ist Teil eines Werkes
Niklas-Luhmann-Findbuch
Konvolutnummer im Findbuch
Member of
Contained by
May contain
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.attributes,
   teiatt.cmc.attributes,
   teiatt.datable.attributes,
   teiatt.sortable.attributes,
   teiatt.typed.attribute.subtype,
   attribute type
   {
      "URI"
    | "GND"
    | "ISSN"
    | "ISBN"
    | "DOI"
    | "URL"
    | "ZDB-ID"
    | "luhmann-ID"
    | "Niklas-Luhmann-Bibliographie"
    | "Niklas-Luhmann-Erstausgabe"
    | "neu"
    | "Niklas-Luhmann-Arbeitsbibliothek"
    | "Niklas-Luhmann-Arbeitsbibliothek-Marker"
    | "shelfmark"
    | "Niklas-Luhmann-Werk"
    | "Niklas-Luhmann-Findbuch"
   },
   ( text | teimodel.gLike | teiidno )*
}

1.58. <imprint>

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

1.59. <interpretation>

<interpretation> (interpretation) describes the scope of any analytic or interpretive information added to the text in addition to the transcription. [2.3.3. The Editorial Practices Declaration]
Moduleheader
Attributes
Member of
Contained by
May contain
core: p
Example
<interpretation>  <p>The part of speech analysis applied throughout section 4 was added by hand and has not    been checked</p> </interpretation>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element interpretation
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   teimodel.pLike+
}

1.60. <keywords>

<keywords> (keywords) contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]
Moduleheader
Attributes
schemeidentifies the controlled vocabulary within which the set of keywords concerned is defined, for example by a <taxonomy> element, or by some other resource.
StatusOptional
Datatypeteidata.pointer
Contained by
header: textClass
May containEmpty element
Note

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

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

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

1.61. <langUsage>

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
core: p
header: language
Example
<langUsage>  <language ident="fr-CAusage="60">Québecois</language>  <language ident="en-CAusage="20">Canadian business English</language>  <language ident="en-GBusage="20">British English</language> </langUsage>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="language"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element langUsage
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   ( teimodel.pLike+ | teilanguage+ )
}

1.62. <language>

<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Moduleheader
Attributes
ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which may be referenced by the global xml:lang attribute.
StatusRequired
Datatypeteidata.language
usagespecifies the approximate percentage of the text which uses this language.
StatusOptional
DatatypenonNegativeInteger
Contained by
header: langUsage
May contain
Note

Particularly for sublanguages, an informal prose characterization should be supplied as content for the element.

Example
<langUsage>  <language ident="en-USusage="75">modern American English</language>  <language ident="az-Arabusage="20">Azerbaijani in Arabic script</language>  <language ident="x-lapusage="05">Pig Latin</language> </langUsage>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element language
{
   teiatt.global.attributes,
   teiatt.scope.attributes,
   attribute ident { text },
   attribute usage { text }?,
   teimacro.phraseSeq.limited
}

1.63. <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
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.global.attributes,
   teiatt.breaking.attributes,
   teiatt.cmc.attributes,
   teiatt.edition.attributes,
   teiatt.spanning.attributes,
   teiatt.typed.attributes,
   empty
}

1.64. <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
linking: annotation
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.global.attributes,
   teiatt.datable.attributes,
   teiatt.pointing.attributes,
   teimacro.specialPara
}

1.65. <linkGrp>

<linkGrp> (link group) defines a collection of associations or hypertextual links. [17.1. Links]
Modulelinking
Attributes
Member of
Contained by
May contain
core: 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>
  <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.global.attributes,
   teiatt.cmc.attributes,
   teiatt.pointing.group.attributes,
   ( teimodel.descLike*, ( link | teiptr )+ )
}

1.66. <listAnnotation>

<listAnnotation> contains a list of annotations, typically encoded as <annotation>, <annotationBlock>, or <note>, possibly organized with nested <listAnnotation> elements. [17.10. The standOff Container]
Modulelinking
Attributes
Member of
Contained by
May contain
Note

The enclosed annotations may use the general-purpose <note> element; or, for annotations pertaining to transcriptions of speech, the special-purpose <annotationBlock> element; or the <annotation> element, which is intended to map cleanly onto the Web Annotation Data Model.

Example
<standOff>  <listAnnotation>   <note place="marginresp="#STC"    target="#RotAM.4.15type="gloss"> The spell begins to      break </note>   <note place="bottomresp="#JLL"    target="#RotAM.4.15"> The turning point of the poem...   </note>  </listAnnotation> </standOff> <!-- ... --> <lg rhyme="ABCBxml:id="RotAM.4.15">  <l>The self-same moment I could pray;</l>  <l>And from my neck so free</l>  <l>The albatross fell off, and sank</l>  <l>Like lead into the sea.</l> </lg>
Example
<listAnnotation>  <annotationBlock corresp="#u1">   <spanGrp type="pos">    <span from="#e14.w1to="#e14.w1">CONJ</span>    <span from="#e14.w2to="#e14.w2">RELPRO</span>    <span from="#e14.w3to="#e14.w3">V</span>   </spanGrp>   <spanGrp type="prosody">    <span from="#T0to="#T1">faster</span>   </spanGrp>  </annotationBlock> <!-- ... annotationBlocks for #u2 through #u27 here --> </listAnnotation>
Example
<listAnnotation>  <annotation motivation="commenting"   target="#match(bg-c1p1s1,'Gallia.*omnis')xml:id="bgann1">   <respStmt>    <resp>creator</resp>    <persName>Francis Kelsey</persName>   </respStmt>   <note>‘Gaul as a whole,’ contrasted with Gaul in the narrower sense, or Celtic Gaul; Celtic Gaul also is often called Gallia.</note>  </annotation>  <annotation motivation="commenting"   target="#match(bg-c1p1s1,'Gallia.*divisa')xml:id="bgann2">   <respStmt>    <resp>creator</resp>    <persName>Rice Holmes</persName>   </respStmt>   <note>Gallia...divisa: Notice the order of the words. ‘Gaul, taken as a whole, is divided’.</note>  </annotation>  <annotation motivation="commenting"   target="#match(bg-c1p1s1,'Belgae')xml:id="bgann3">   <respStmt>    <resp>creator</resp>    <persName>Arthur Tappan Walker</persName>   </respStmt>   <note>Belgae -arum m., the Belgae or Belgians</note>  </annotation>  <annotation motivation="commenting"   target="#match(bg-c1p1s1,'Aquitani')xml:id="bgann4">   <respStmt>    <resp>creator</resp>    <persName>Arthur Tappan Walker</persName>   </respStmt>   <note>Aquitani, -orum m.: the Aquitani, inhabiting southwestern Gaul</note>  </annotation>  <annotation motivation="commenting"   target="#match(bg-c1p1s1,'Celtae')xml:id="bgann5">   <respStmt>    <resp>creator</resp>    <persName>Arthur Tappan Walker</persName>   </respStmt>   <note>Celtae, -arum m: the Celtae or Celts</note>  </annotation>  <annotation motivation="commenting"   target="#match(bg-c1p1s2,'Gallos(.|\n)*dividit')xml:id="bgann6">   <respStmt>    <resp>creator</resp>    <persName>William Francis Allen</persName>    <persName>Joseph Henry Allen</persName>    <persName>Harry Pratt Judson</persName>   </respStmt>   <note>the verb is singular, because the two rivers make one boundary; as we should say,      ‘is divided by the line of the Seine and Marne.’</note>  </annotation> </listAnnotation> <!-- Elsewhere in the document --> <text>  <body>   <div type="edition">    <div n="1subtype="chapter"     type="textpartxml:id="bg-c1">     <p n="1xml:id="bg-c1p1">      <seg n="1xml:id="bg-c1p1s1">Gallia est omnis divisa in partes tres, quarum unam incolunt Belgae, aliam            Aquitani, tertiam qui ipsorum lingua Celtae, nostra Galli appellantur.</seg>      <seg n="2xml:id="bg-c1p1s2">Hi omnes lingua, institutis, legibus inter se differunt. Gallos ab Aquitanis            Garumna flumen, a Belgis Matrona et Sequana dividit.</seg> <!-- ... -->     </p>    </div>   </div>  </body> </text>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.labelLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.annotationLike"/>
   <elementRef key="listAnnotation"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listAnnotation
{
   teiatt.global.attributes,
   teiatt.declaring.attributes,
   teiatt.notated.attributes,
   teiatt.typed.attributes,
   (
      teimodel.headLike*,
      teimodel.labelLike*,
      ( teimodel.annotationLike | teilistAnnotation )+
   )
}

1.67. <listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<listBibl>  <head>Works consulted</head>  <bibl>Blain, Clements and Grundy: Feminist Companion to    Literature in English (Yale, 1990)  </bibl>  <biblStruct>   <analytic>    <title>The Interesting story of the Children in the Wood</title>   </analytic>   <monogr>    <title>The Penny Histories</title>    <author>Victor E Neuberg</author>    <imprint>     <publisher>OUP</publisher>     <date>1968</date>    </imprint>   </monogr>  </biblStruct> </listBibl>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="desc"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.milestoneLike"
    maxOccurs="1" minOccurs="1"/>
   <elementRef key="relation" maxOccurs="1"
    minOccurs="1"/>
   <elementRef key="listRelation"
    maxOccurs="1" minOccurs="1"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.biblLike"
    maxOccurs="unbounded" minOccurs="1"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.milestoneLike"
     maxOccurs="1" minOccurs="1"/>
    <elementRef key="relation"
     maxOccurs="1" minOccurs="1"/>
    <elementRef key="listRelation"
     maxOccurs="1" minOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listBibl
{
   teiatt.global.attributes,
   teiatt.cmc.attributes,
   teiatt.declarable.attributes,
   teiatt.sortable.attributes,
   teiatt.typed.attributes,
   (
      teimodel.headLike*,
      desc*,
      ( teimodel.milestoneLike | relation | listRelation )*,
      (
         (
            teimodel.biblLike+,
            ( teimodel.milestoneLike | relation | listRelation )*
         )+
      )
   )
}

1.68. <listChange>

<listChange> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.6. The Revision Description 12.7. Identifying Changes and Revisions]
Moduleheader
Attributes
orderedindicates whether the ordering of its child <change> elements is to be considered significant or not.
StatusOptional
Datatypeteidata.truthValue
Defaulttrue
Member of
Contained by
May contain
Note

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

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

1.69. <listObject>

<listObject> (list of objects) contains a list of descriptions, each of which provides information about an identifiable physical object. [14.3.6. Objects]
Modulenamesdates
Attributes
Member of
Contained by
May contain
namesdates: listObject object
Note

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

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

1.70. <listPrefixDef>

<listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in teidata.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [17.2.3. Using Abbreviated Pointers]
Moduleheader
Attributes
Member of
Contained by
May contain
ExampleIn this example, two private URI scheme prefixes are defined and patterns are provided for dereferencing them. Each prefix is also supplied with a human-readable explanation in a <p> element.
<listPrefixDef>  <prefixDef ident="psn"   matchPattern="([A-Z]+)"   replacementPattern="personography.xml#$1">   <p> Private URIs using the <code>psn</code>      prefix are pointers to <gi>person</gi>      elements in the personography.xml file.      For example, <code>psn:MDH</code>      dereferences to <code>personography.xml#MDH</code>.   </p>  </prefixDef>  <prefixDef ident="bibl"   matchPattern="([a-z]+[a-z0-9]*)"   replacementPattern="http://www.example.com/getBibl.xql?id=$1">   <p> Private URIs using the <code>bibl</code> prefix can be      expanded to form URIs which retrieve the relevant      bibliographical reference from www.example.com.   </p>  </prefixDef> </listPrefixDef>
Content model
<content>
 <sequence>
  <elementRef key="desc"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="prefixDef"/>
   <elementRef key="listPrefixDef"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listPrefixDef
{
   teiatt.global.attributes,
   ( desc*, ( teiprefixDef | teilistPrefixDef )+ )
}

1.71. <monogr>

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

May contain specialized bibliographic elements, in a prescribed order.

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

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope from="377to="380unit="page">377–380</biblScope>  </monogr> </biblStruct>
Example
<biblStruct type="book">  <monogr>   <author>    <persName>     <forename>Leo Joachim</forename>     <surname>Frachtenberg</surname>    </persName>   </author>   <title level="mtype="main">Lower Umpqua Texts</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Columbia University Press</publisher>    <date>1914</date>   </imprint>  </monogr>  <series>   <title level="stype="main">Columbia University Contributions to      Anthropology</title>   <biblScope unit="volume">4</biblScope>  </series> </biblStruct>
Content model
<content>
 <sequence>
  <alternate minOccurs="0">
   <sequence>
    <alternate>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <elementRef key="title"
     maxOccurs="unbounded" minOccurs="1"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
     <elementRef key="textLang"/>
     <elementRef key="editor"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <alternate maxOccurs="unbounded"
     minOccurs="1">
     <elementRef key="title"/>
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
    </alternate>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <elementRef key="textLang"/>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <elementRef key="authority"/>
    <elementRef key="idno"/>
   </sequence>
  </alternate>
  <elementRef key="availability"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.noteLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="edition"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="idno"/>
    <classRef key="model.ptrLike"/>
    <elementRef key="editor"/>
    <elementRef key="sponsor"/>
    <elementRef key="funder"/>
    <elementRef key="respStmt"/>
   </alternate>
  </sequence>
  <elementRef key="imprint"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="imprint"/>
   <elementRef key="extent"/>
   <elementRef key="biblScope"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element monogr
{
   teiatt.global.attributes,
   (
      (
         (
            ( teiauthor | teieditor | meeting | teirespStmt ),
            ( teiauthor | teieditor | meeting | teirespStmt )*,
            teititle+,
            (
               teimodel.ptrLike
             | teiidno
             | teitextLang
             | teieditor
             | teirespStmt
            )*
         )
       | (
            ( teititle | teimodel.ptrLike | teiidno )+,
            ( teitextLang | teiauthor | teieditor | meeting | teirespStmt )*
         )
       | ( teiauthority, teiidno )
      )?,
      teiavailability*,
      teimodel.noteLike*,
      (
         (
            teiedition,
            (
               teiidno
             | teimodel.ptrLike
             | teieditor
             | teisponsor
             | teifunder
             | teirespStmt
            )*
         )*
      ),
      teiimprint,
      ( teiimprint | teiextent | teibiblScope )*
   )
}

1.72. <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
et-al
et al.
unspecified
Unspecifische Namensangabe (z.B. Aristoteles)
institution
Name einer Institution
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.global.attributes,
   teiatt.cmc.attributes,
   teiatt.datable.attributes,
   teiatt.editLike.attributes,
   teiatt.personal.attributes,
   teiatt.typed.attribute.subtype,
   attribute type { "et-al" | "unspecified" | "institution" }?,
   teimacro.phraseSeq
}

1.73. <namespace>

<namespace> (namespace) supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration]
Moduleheader
Attributes
namespecifies the full formal name of the namespace concerned.
StatusRequired
Datatype0–1 occurrences of teidata.namespace separated by whitespace
Contained by
header: tagsDecl
May contain
header: tagUsage
Example
<namespace name="http://www.tei-c.org/ns/1.0">  <tagUsage gi="hioccurs="28withId="2"> Used only to mark English words    italicized in the copy text </tagUsage> </namespace>
Content model
<content>
 <elementRef key="tagUsage"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element namespace
{
   teiatt.global.attributes,
   attribute name { ? },
   teitagUsage+
}

1.74. <normalization>

<normalization> (normalization) indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
methodindicates the method adopted to indicate normalizations within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
normalization made silently[Default]
markup
normalization represented using markup
Member of
Contained by
May contain
core: p
Example
<editorialDecl>  <normalization method="markup">   <p>Where both upper- and lower-case i, j, u, v, and vv have been normalized, to modern      20th century typographical practice, the <gi>choice</gi> element has been used to      enclose <gi>orig</gi> and <gi>reg</gi> elements giving the original and new values      respectively. ... </p>  </normalization>  <normalization method="silent">   <p>Spacing between words and following punctuation has been regularized to zero spaces;      spacing between words has been regularized to one space.</p>  </normalization>  <normalization source="http://www.dict.sztaki.hu/webster">   <p>Spelling converted throughout to Modern American usage, based on Websters 9th      Collegiate dictionary.</p>  </normalization> </editorialDecl>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element normalization
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   attribute method { "silent" | "markup" }?,
   teimodel.pLike+
}

1.75. <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
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
notes
allgemeine Anmerkungen
unsolved
Hier besteht noch weiterer Recherchebedarf
unsolved-@
Hier besteht noch weiterer Recherchebedarf: Einzeltitel (Übersetzung) des Aufsatzes noch recherchieren / Band bekannt (Dammann-Bibliographie)
unsolved-online
Hier besteht noch weiterer Recherchebedarf: Verweis auf online vorgehlatene Übersetzung. Sollte eigenes Item werden?
intern
Interne editorische Erläuterungen
copy
Nachgewiesenes Exemplar
copies
Exemplar(e) in Luhmanns Arbeitsbibliothek
abstract
Abstract
imprint-Information
Imprint-Informationen, die in einer Listendarstellung angezeigt werden sollen.
div-display
Temporärer Eintrag für bibl-Listenausgabe
description
Beschreibung
legal_notes
(Urheber)rechtliche Angaben
legalNotice
Anmerkung zur Lizenz
licensePeriod_start
Lizenzbegin
licensePeriod_end
Lizenzende
rightsHolder
RechteinhaberIn
status
Status (is public / is not public)
relatedItem
Ed. Anmerkung zu einem zugehörigen bibliographischen Eintrag (relatedItem)
subtype(subtype) provides a sub-categorization of the element, if needed.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
print_version
Druckexemplar
digitized_version
Digitalisat
private
privat
public-service
öffentlich rechtlich
none
none
commercial
kommerziell
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.global.attributes,
   teiatt.anchoring.attributes,
   teiatt.cmc.attributes,
   teiatt.placement.attributes,
   teiatt.pointing.attributes,
   teiatt.written.attributes,
   attribute type
   {
      "notes"
    | "unsolved"
    | "unsolved-@"
    | "unsolved-online"
    | "intern"
    | "copy"
    | "copies"
    | "abstract"
    | "imprint-Information"
    | "div-display"
    | "description"
    | "legal_notes"
    | "legalNotice"
    | "licensePeriod_start"
    | "licensePeriod_end"
    | "rightsHolder"
    | "status"
    | "relatedItem"
   },
   attribute subtype
   {
      "print_version"
    | "digitized_version"
    | "private"
    | "public-service"
    | "none"
    | "commercial"
   }?,
   teimacro.specialPara
}

1.76. <noteGrp>

<noteGrp> (note group) contains a group of notes. [3.9.1.1. Encoding Grouped Notes]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIn the following example, there are two notes in different languages, each specifying the content of the annotation relating to the same fragment of text:
<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus <noteGrp>   <note xml:lang="en">Quatuor Tempora, so called dry fast days (Wednesday, Friday, and Saturday)      falling on each of the quarters of the year. In the first quarter they were called Cinerum      (following Ash Wednesday), second Spiritus (following Pentecost), third Crucis      (after the Exaltation of the Holy Cross, September 14th), and Luciae      in the fourth (after the feast of St. Lucia, December 13th).   </note>   <note xml:lang="pl">Quatuor Tempora, tzw. Suche dni postne (środa, piątek i sobota)      przypadające cztery razy w roku. W pierwszym kwartale zwały się Cinerum      (po Popielcu), w drugim Spiritus (po Zielonych Świętach), w trzecim Crucis      (po święcie Podwyższenia Krzyża 14 września), w czwartym Luciae      (po dniu św. Łucji 13 grudnia).   </note>  </noteGrp> totaliter expediui. </p>
Content model
<content>
 <sequence>
  <elementRef key="desc"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="note"/>
   <elementRef key="noteGrp"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element noteGrp
{
   teiatt.global.attributes,
   teiatt.anchoring.attributes,
   teiatt.cmc.attributes,
   teiatt.placement.attributes,
   teiatt.pointing.attributes,
   teiatt.typed.attributes,
   teiatt.written.attributes,
   ( desc*, ( teinote | teinoteGrp )+ )
}

1.77. <notesStmt>

<notesStmt> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
May contain
Note

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

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

1.78. <object>

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

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

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

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

1.79. <objectIdentifier>

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

1.80. <objectName>

<objectName> (name of an object) contains a proper noun or noun phrase used to refer to an object. [14.2.5. Object Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<p> The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the <objectName ref="#AlfredJewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster    Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>. </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element objectName
{
   teiatt.global.attributes,
   teiatt.cmc.attributes,
   teiatt.datable.attributes,
   teiatt.editLike.attributes,
   teiatt.personal.attributes,
   teiatt.typed.attributes,
   teimacro.phraseSeq
}

1.81. <orgName>

<orgName> (organization name) contains an organizational name. [14.2.2. Organizational Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">  <placeName key="PEN">Pennsyla.</placeName> Abolition Society </orgName> [...]
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element orgName
{
   teiatt.global.attributes,
   teiatt.cmc.attributes,
   teiatt.datable.attributes,
   teiatt.editLike.attributes,
   teiatt.personal.attributes,
   teiatt.typed.attributes,
   teimacro.phraseSeq
}

1.82. <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you    done?</q> </p> <p>  <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. </p> <p>  <q>Then you must mean that Thorvald is dead,</q> she said. </p> <p>  <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> </p>
Schematron
<sch:rule context="tei:p"> <sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText | parent::tei:exemplum | parent::tei:item | parent::tei:note | parent::tei:q | parent::tei:quote | parent::tei:remarks | parent::tei:said | parent::tei:sp | parent::tei:stage | parent::tei:cell | parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:l//tei:p"> <sch:assert test="ancestor::tei:floatingText | parent::tei:figure | parent::tei:note"> Abstract model violation: Metrical lines 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.attributes,
   teiatt.cmc.attributes,
   teiatt.declaring.attributes,
   teiatt.fragmentable.attributes,
   teiatt.written.attributes,
   teimacro.paraContent
}

1.83. <persPronouns>

<persPronouns> (personal pronouns) indicates the personal pronouns used, or assumed to be used, by the individual being described. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
evidence(evidence) indicates support for the listed personal pronouns.
StatusRecommended
Datatypeteidata.enumerated
Suggested values include:
conjecture
(conjecture) The given value was selected based on assumptions by someone besides the person to whom this pronoun applies. As a result, the value may be erroneous.
selfIdentification
(self identification) The given value has been explicitly stated or confirmed by the person to whom this pronoun applies.
trustedThirdParty
(trusted third party) The given value has been supplied by another individual trusted by the encoder to know the preferences of the person to whom this pronoun applies.
value(value) supplies a regularized value for personal pronouns.
StatusRecommended
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Sample values include:
e
(e) e/eirs
he
(he) he/him/his
she
(she) she/her/hers
they
(they) they/them/theirs
Note

The sample values list shown here is intended to be reflective of English usage. There is nothing restricting users from defining lists reflective of other languages, e.g. elle, il, and ils.

Member of
Contained by
May contain
Example
<person>  <persName>   <forename>SUE</forename>   <addName>the T. rex</addName>  </persName>  <residence>The Field Museum. Chicago, Illinois, United States.</residence>  <sex value="0"/>  <persPronouns value="they">they/them</persPronouns>  <note>   <cit>    <quote>Specimen FMNH PR 2081. Legendary Fossil. Apex        Predator. National Treasure. <emph style="text-transform:uppercase; letter-spacing:0.25rem;">Murderbird.</emph>    </quote>    <bibl>SUEtheTrex, Twitter biography.    <ptr target="https://twitter.com/SUEtheTrex"/>.        Accessed <date when="2020-03-25">March 25th, 2020</date>.</bibl>   </cit>  </note> </person>
Example
<docAuthor>  <persName>Lal Zimman</persName>  <persPronouns value="he">(he/him/his)</persPronouns>  <ref target="#Name">(FAQ)</ref>  <persName type="IPA">[lɑɫ ˈzimn̩]</persName>  <email>zimman at ucsb dot edu</email>  <roleName>Assistant Professor of Linguistics</roleName>  <roleName>Affiliated Faculty in Feminist Studies</roleName>  <address>   <addrLine>South Hall 3518</addrLine>   <addrLine>University of California, Santa Barbara</addrLine>  </address> </docAuthor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element persPronouns
{
   teiatt.global.attributes,
   teiatt.cmc.attributes,
   teiatt.datable.attributes,
   teiatt.typed.attributes,
   attribute evidence
   {
      "conjecture" | "selfIdentification" | "trustedThirdParty"
   }?,
   attribute value { list { + } }?,
   teimacro.phraseSeq
}

1.84. <persona>

<persona> provides information about one of the personalities identified for a given individual, where an individual has multiple personalities. [14.3.2. The Person Element]
Modulenamesdates
Attributes
rolespecifies a primary role or classification for the persona.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sexspecifies the sex of the persona.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

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

genderspecifies the gender of the persona.
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.

agespecifies an age group for the persona.
StatusOptional
Datatypeteidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

Member of
Contained by
namesdates: persona
May contain
Note

Note that a persona is not the same as a role. A role may be assumed by different people on different occasions, whereas a persona is unique to a particular person, even though it may resemble others. Similarly, when an actor takes on or enacts the role of a historical person, they do not thereby acquire a new persona.

Example
<person age="adultsex="M">  <persona sex="M">   <persName>Dr Henry Jekyll</persName>  </persona>  <persona age="youthsex="M">   <persName>Edward Hyde</persName>  </persona> </person>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element persona
{
   teiatt.global.attributes,
   teiatt.editLike.attributes,
   teiatt.sortable.attributes,
   attribute role { list { + } }?,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   ( teimodel.pLike+ | ( teimodel.personPart | teimodel.global )* )
}

1.85. <placeName>

<placeName> (place name) contains an absolute or relative place name. [14.2.3. Place Names]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
created
[Default]
Member of
Contained by
May contain
Example
<placeName>  <settlement>Rochester</settlement>  <region>New York</region> </placeName>
Example
<placeName>  <geogName>Arrochar Alps</geogName>  <region>Argylshire</region> </placeName>
Example
<placeName>  <measure>10 miles</measure>  <offset>Northeast of</offset>  <settlement>Attica</settlement> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element placeName
{
   teiatt.cmc.attributes,
   teiatt.canonical.attribute.key,
   attribute type { "created" },
   teimacro.phraseSeq
}

1.86. <prefixDef>

<prefixDef> (prefix definition) defines a prefixing scheme used in teidata.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [17.2.3. Using Abbreviated Pointers]
Moduleheader
Attributes
identsupplies a name which functions as the prefix for an abbreviated pointing scheme such as a private URI scheme. The prefix constitutes the text preceding the first colon.
StatusRequired
Datatypeteidata.prefix
Note

The value is limited to teidata.prefix so that it may be mapped directly to a URI prefix.

Contained by
May contain
core: p
Note

The abbreviated pointer may be dereferenced to produce either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the pointing attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

Example
<prefixDef ident="ref"  matchPattern="([a-z]+)"  replacementPattern="../../references/references.xml#$1">  <p> In the context of this project, private URIs with    the prefix "ref" point to <gi>div</gi> elements in    the project's global references.xml file.  </p> </prefixDef>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
    
Schema Declaration
element prefixDef
{
   teiatt.global.attributes,
   teiatt.patternReplacement.attributes,
   attribute ident { text },
   teimodel.pLike*
}

1.87. <principal>

<principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement]
Moduleheader
Attributes
Member of
Contained by
May contain
Example
<principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element principal
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   teiatt.datable.attributes,
   teimacro.phraseSeq.limited
}

1.88. <profileDesc>

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

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

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

1.89. <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
Attributes
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
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   teimodel.pLike+
}

1.90. <ptr>

<ptr> (pointer) defines a pointer to another location. [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
StatusRequired
Datatypeteidata.enumerated
Sample values include:
nl_biblio
Bibliographisches Item ist Teil der Niklas-Luhmann-Bibliographie
nl_werkbiblio
Bibliographisches Item ist Teil des Niklas-Luhmann-Erstausgabeses
representation
Link zur Editionsdatei
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.global.attributes,
   teiatt.cReferencing.attributes,
   teiatt.cmc.attributes,
   teiatt.declaring.attributes,
   teiatt.internetMedia.attributes,
   teiatt.pointing.attributes,
   teiatt.typed.attribute.subtype,
   attribute type { text },
   empty
}

1.91. <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
Attributes
n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived fromatt.global
StatusOptional
Datatypeteidata.text
Legal values are:
origPlace
Erstellungsort
hectographPlace
Veröffentlichungsort bei sog. grauen Papieren, in hektographierter Form
Member of
Contained by
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
{
   teiatt.global.attribute.xmlid,
   teiatt.global.attribute.xmllang,
   teiatt.global.attribute.xmlbase,
   teiatt.global.attribute.xmlspace,
   teiatt.global.linking.attribute.corresp,
   teiatt.global.linking.attribute.synch,
   teiatt.global.linking.attribute.sameAs,
   teiatt.global.linking.attribute.copyOf,
   teiatt.global.linking.attribute.next,
   teiatt.global.linking.attribute.prev,
   teiatt.global.linking.attribute.exclude,
   teiatt.global.linking.attribute.select,
   teiatt.global.rendition.attribute.rend,
   teiatt.global.rendition.attribute.style,
   teiatt.global.rendition.attribute.rendition,
   teiatt.global.responsibility.attribute.cert,
   teiatt.global.responsibility.attribute.resp,
   teiatt.global.source.attribute.source,
   teiatt.naming.attributes,
   attribute n { "origPlace" | "hectographPlace" }?,
   teimacro.phraseSeq
}

1.92. <publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Moduleheader
Attributes
Contained by
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>
  <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
{
   teiatt.global.attributes,
   (
      (
         (
            teimodel.publicationStmtPart.agency,
            teimodel.publicationStmtPart.detail*
         )+
      )
    | teimodel.pLike+
   )
}

1.93. <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
Attributes
Member of
Contained by
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
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   teimacro.phraseSeq
}

1.94. <punctuation>

<punctuation> specifies editorial practice adopted with respect to punctuation marks in the original. [2.3.3. The Editorial Practices Declaration 3.2. Treatment of Punctuation]
Moduleheader
Attributes
marksindicates whether or not punctation marks have been retained as content within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
no punctuation marks have been retained
some
some punctuation marks have been retained
all
all punctuation marks have been retained
placementindicates the positioning of punctuation marks that are associated with marked up text as being encoded within the element surrounding the text or immediately before or after it.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
internal
punctuation marks found at the start or end of a marked up text component are included within its surrounding element;
external
punctuation marks found at the start or end of a marked up text component appear immediately before or after the surrounding element
Member of
Contained by
May contain
core: p
Example
<punctuation marks="all"  placement="internal">  <p>All punctuation marks in the source text have been retained and represented using the    appropriate Unicode code point. In cases where a punctuation mark and nearby markup convey    the same information (for example, a sentence ends with a question mark and is also tagged    as <gi>s</gi>) the punctuation mark is captured as content within the element.</p> </punctuation>
ExampleExternal placement of punctuation:
<p>I would agree with Saint Augustine that “<quote>An unjust law is no law at all</quote>.”</p>
ExampleInternal placement of punctuation:
<p>I would agree with Saint Augustine that <quote>“An unjust law is no law at all.”</quote> </p>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
    
Schema Declaration
element punctuation
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   attribute marks { "none" | "some" | "all" }?,
   attribute placement { "internal" | "external" }?,
   teimodel.pLike*
}

1.95. <quotation>

<quotation> (quotation) specifies editorial practice adopted with respect to quotation marks in the original. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
marks(quotation marks) indicates whether or not quotation marks have been retained as content within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
no quotation marks have been retained
some
some quotation marks have been retained
all
all quotation marks have been retained
Member of
Contained by
May contain
core: p
Example
<quotation marks="none">  <p>No quotation marks have been retained. Instead, the <att>rend</att> attribute on the  <gi>q</gi> element is used to specify what kinds of quotation mark was used, according    to the following list: <list type="gloss">    <label>dq</label>    <item>double quotes, open and close</item>    <label>sq</label>    <item>single quotes, open and close</item>    <label>dash</label>    <item>long dash open, no close</item>    <label>dg</label>    <item>double guillemets, open and close</item>   </list>  </p> </quotation>
Example
<quotation marks="all">  <p>All quotation marks are retained in the text and are represented by appropriate Unicode    characters.</p> </quotation>
Schematron
<sch:rule context="tei:quotation"> <sch:report test="not( @marks ) and not( tei:p )"> On <sch:name/>, either the @marks attribute should be used, or a paragraph of description provided </sch:report> </sch:rule>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
    
Schema Declaration
element quotation
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   attribute marks { "none" | "some" | "all" }?,
   teimodel.pLike*
}

1.96. <rb>

<rb> (ruby base) contains the base text annotated by a ruby gloss. [3.4.2. Ruby Annotations]
Modulecore
Attributes
Contained by
core: ruby
May contain
ExampleThe word 你 好 nǐ hǎo (hello) is glossed in pinyin to provide a pronunciation guide.
<p xml:lang="zh"> <!--...-->  <ruby>   <rb></rb>   <rt place="above"></rt>  </ruby>  <ruby>   <rb></rb>   <rt place="above">hǎo</rt>  </ruby> <!--...--> </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rb
{
   teiatt.global.attributes,
   teiatt.typed.attributes,
   teimacro.phraseSeq
}

1.97. <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:
extern
Link ins WWW, extern
intern
Link auf ein Ziel innerhalb des Luhmannarchivs
Niklas-Luhmann-Bibliographie
Link innerhalb der Luhmannbibliographie
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.attributes,
   teiatt.cReferencing.attributes,
   teiatt.cmc.attributes,
   teiatt.declaring.attributes,
   teiatt.internetMedia.attributes,
   teiatt.pointing.attributes,
   teiatt.typed.attribute.subtype,
   attribute type { "extern" | "intern" | "Niklas-Luhmann-Bibliographie" }?,
   teimacro.paraContent
}

1.98. <refState>

<refState> (reference state) specifies one component of a canonical reference defined by the milestone method. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]
Moduleheader
Attributes
lengthspecifies the fixed length of the reference component.
StatusOptional
Datatypeteidata.count
Note

When constructing a reference, if the reference component found is of numeric type, the length is made up by inserting leading zeros; if it is not, by inserting trailing blanks. In either case, reference components are truncated if necessary at the right hand side.

When seeking a reference, the length indicates the number of characters which should be compared. Values longer than this will be regarded as matching, if they start correctly. If no value is provided, the length is unlimited and goes to the next delimiter or to the end of the value.

delim(delimiter) supplies a delimiting string following the reference component.
StatusOptional
Datatypeteidata.text
Contained by
header: refsDecl
May containEmpty element
Example
<refState delim=":unit="book"/> <refState length="4unit="line"/>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element refState
{
   teiatt.global.attributes,
   teiatt.edition.attributes,
   teiatt.milestoneUnit.attributes,
   attribute length { text }?,
   attribute delim { text }?,
   empty
}

1.99. <refsDecl>

<refsDecl> (references declaration) specifies how canonical references are constructed for this text. [2.3.6.3. Milestone Method 2.3. The Encoding Description 2.3.6. The Reference System Declaration]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
Example
<refsDecl>  <cRefPattern matchPattern="([A-Za-z0-9]+) ([0-9]+):([0-9]+)"   replacementPattern="#xpath(//body/div[@n='$1']/div[$2]/div3[$3])"/> </refsDecl>
This example is a formal representation for the referencing scheme described informally in the following example.
Example
<refsDecl>  <p>References are made up by concatenating the value for the  <att>n</att> attribute on the highest level <gi>div</gi>    element, followed by a space, followed by the sequential    number of the next level <gi>div</gi> followed by a colon    followed by the sequential number of the next (and lowest)    level <gi>div</gi>.</p> </refsDecl>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="citeStructure"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="cRefPattern"
   maxOccurs="unbounded" minOccurs="1"/>
  <elementRef key="refState"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element refsDecl
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   ( teimodel.pLike+ | teiciteStructure+ | teicRefPattern+ | teirefState+ )
}

1.100. <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:
articleIncluded
Beitrag in diesem Band/Heft
audio-video
Audio/Video
book
Buch
bookSection
Abschnitt in Monographie
commentedBy
Kommentiert in
commentOn
Kommentar zu
continuationOf
Fortsetzung von
continuedBy
Fortgesetzt durch
firstPrint
Erstdruck
grey
Graue Literatur
journal
Zeitschrift
journalArticle
Zeitschriftenbeitrag
journalItemIncluded
Sonderheft / Themenheft
journalRelated
Zugehörige Zeitschrift
manuscript
Manuskript
newspaper
Taggeszeitung
newspaperArticle
Zeitungsbeitrag
related-translations
Zugehörige Übersetzung
reprint
Wiederabdruck
reprintOf
Wiederabdruck von
reviewOf
Rezension von
reviewedBy
Rezensiert durch
same-series-other-volume
Schwesterband in dieser Reihe
series
Reihe/Mehrbändiges Werk
seriesIncluded
Zugehörige Reihe
seriesItemIncluded
Einzelband
translation
Übersetzung
translationOf
Übersetzung von
typescript
Typoskript
webPublication
Online-Publikation
targetpoints to the related bibliographic element by means of an absolute or relative URI reference.
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
May contain
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
{
   teiatt.global.attributes,
   teiatt.typed.attribute.subtype,
   attribute type
   {
      "articleIncluded"
    | "audio-video"
    | "book"
    | "bookSection"
    | "commentedBy"
    | "commentOn"
    | "continuationOf"
    | "continuedBy"
    | "firstPrint"
    | "grey"
    | "journal"
    | "journalArticle"
    | "journalItemIncluded"
    | "journalRelated"
    | "manuscript"
    | "newspaper"
    | "newspaperArticle"
    | "related-translations"
    | "reprint"
    | "reprintOf"
    | "reviewOf"
    | "reviewedBy"
    | "same-series-other-volume"
    | "series"
    | "seriesIncluded"
    | "seriesItemIncluded"
    | "translation"
    | "translationOf"
    | "typescript"
    | "webPublication"
   },
   attribute target { text }?,
   ( teimodel.biblLike | teimodel.ptrLike )?
}

1.101. <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
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.102. <resp>

<resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore
Attributes
Contained by
core: respStmt
May contain
Note

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

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

1.103. <respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore
Attributes
Member of
Contained by
May contain
core: name note resp
namesdates: orgName
Example
<respStmt>  <resp>transcribed from original ms</resp>  <persName>Claus Huitfeldt</persName> </respStmt>
Example
<respStmt>  <resp>converted to XML encoding</resp>  <name>Alan Morrison</name> </respStmt>
Content model
<content>
 <sequence>
  <alternate>
   <sequence>
    <elementRef key="resp"
     maxOccurs="unbounded" minOccurs="1"/>
    <classRef key="model.nameLike.agent"
     maxOccurs="unbounded" minOccurs="1"/>
   </sequence>
   <sequence>
    <classRef key="model.nameLike.agent"
     maxOccurs="unbounded" minOccurs="1"/>
    <elementRef key="resp"
     maxOccurs="unbounded" minOccurs="1"/>
   </sequence>
  </alternate>
  <elementRef key="note"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element respStmt
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   (
      (
         ( teiresp+, teimodel.nameLike.agent+ )
       | ( teimodel.nameLike.agent+, teiresp+ )
      ),
      teinote*
   )
}

1.104. <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
Attributes
Contained by
header: teiHeader
linking: annotation
May contain
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>
  <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
{
   teiatt.global.attributes,
   teiatt.docStatus.attributes,
   ( list+ | teilistChange+ | teichange+ )
}

1.105. <rt>

<rt> (ruby text) contains a ruby text, an annotation closely associated with a passage of the main text. [3.4.2. Ruby Annotations]
Modulecore
Attributes
targetsupplies a pointer to the base being glossed by this ruby text.
StatusOptional
Datatypeteidata.pointer
SchematronEnforce that either target or both from and to (or none) are used, but not target in combination with either from or to.
<sch:rule context="tei:rt/@target"> <sch:report test="../@from | ../@to">When target= is present, neither from= nor to= should be.</sch:report> </sch:rule>
Note

Should point to a single <rb> or an element that is inside an <rb>. To refer to multiple elements or text nodes at once use from and to.

frompoints to the starting point of the span of text being glossed by this ruby text.
StatusOptional
Datatypeteidata.pointer
SchematronEnforce the presence of to iff there is a from.
<sch:rule context="tei:rt/@from"> <sch:assert test="../@to">When from= is present, the to= attribute of <sch:name/> is required.</sch:assert> </sch:rule>
topoints to the ending point of the span of text being glossed.
StatusOptional
Datatypeteidata.pointer
SchematronEnforce the presence of from iff there is a to.
<sch:rule context="tei:rt/@to"> <sch:assert test="../@from">When to= is present, the from= attribute of <sch:name/> is required.</sch:assert> </sch:rule>
Contained by
core: ruby
May contain
Note

Where the place attribute is not provided on the <rt> element, the default assumption is that the ruby gloss is above where the text is horizontal, and to the right of the text where it is vertical.

ExampleThe word 大統領 daitōryō (president) is glossed character by character in hiragana to provide a pronunciation guide.
<p style="writing-mode: vertical-rl"  xml:lang="ja"> <!--...-->  <ruby>   <rb></rb>   <rt place="right">だい</rt>  </ruby>  <ruby>   <rb></rb>   <rt place="right">とう</rt>  </ruby>  <ruby>   <rb></rb>   <rt place="right">りょう</rt>  </ruby> <!--...--> </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rt
{
   teiatt.global.attributes,
   teiatt.transcriptional.attributes,
   teiatt.typed.attributes,
   attribute target { text }?,
   attribute from { text }?,
   attribute to { text }?,
   teimacro.phraseSeq
}

1.106. <ruby>

<ruby> (ruby container) contains a passage of base text along with its associated ruby gloss(es). [3.4.2. Ruby Annotations]
Modulecore
Attributes
Member of
Contained by
May contain
core: rb rt
ExampleThe word 入学試験 nyūgakushiken (university entrance exam) is glossed with a hiragana phonation guide.
<p xml:lang="ja"> <!--...-->  <ruby>   <rb>入学試験</rb>   <rt place="above">にゅうがくしけん</rt>  </ruby> <!--...--> </p>
ExampleThis fictional example shows the initialism TEI glossed letter-by-letter with an IPA transcription.
<ruby>  <rb>T</rb>  <rt>ti:</rt> </ruby> <ruby>  <rb>E</rb>  <rt>i:</rt> </ruby> <ruby>  <rb>I</rb>  <rt></rt> </ruby>
Content model
<content>
 <sequence>
  <elementRef key="rb" maxOccurs="1"
   minOccurs="1"/>
  <elementRef key="rt"
   maxOccurs="unbounded" minOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element ruby
{
   teiatt.global.attributes,
   teiatt.cmc.attributes,
   teiatt.typed.attributes,
   ( teirb, teirt+ )
}

1.107. <samplingDecl>

<samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
Note

This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest.

Example
<samplingDecl>  <p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each    text identified as relevant by respondents.</p> </samplingDecl>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element samplingDecl
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   teimodel.pLike+
}

1.108. <schemaRef>

<schemaRef> (schema reference) describes or points to a related customization or schema file. [2.3.10. The Schema Specification]
Moduleheader
Attributes
keythe identifier used for the customization or schema.
StatusOptional
Datatypeteidata.xmlName
Member of
Contained by
header: encodingDesc
May containEmpty element
Example
<schemaRef type="interchangeODD"  url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.odd"/> <schemaRef type="interchangeRNG"  url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.rng"/> <schemaRef type="projectODD"  url="file:///schema/project.odd"/>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0"/>
</content>
    
Schema Declaration
element schemaRef
{
   teiatt.global.attributes,
   teiatt.resourced.attributes,
   teiatt.typed.attributes,
   attribute key { text }?,
   teimodel.descLike?
}

1.109. <scriptNote>

<scriptNote> describes a particular script distinguished within the description of a manuscript or similar resource. [11.7.2. Writing, Decoration, and Other Notations]
Moduleheader
Attributes
Contained by
May contain
Example
<scriptNote scope="sole"/>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element scriptNote
{
   teiatt.global.attributes,
   teiatt.handFeatures.attributes,
   teimacro.specialPara
}

1.110. <segmentation>

<segmentation> (segmentation) describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
May contain
core: p
Example
<segmentation>  <p>   <gi>s</gi> elements mark orthographic sentences and are numbered sequentially within    their parent <gi>div</gi> element </p> </segmentation>
Example
<p>  <gi>seg</gi> elements are used to mark functional constituents of various types within each <gi>s</gi>; the typology used is defined by a <gi>taxonomy</gi> element in the corpus header <gi>classDecl</gi> </p>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element segmentation
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   teimodel.pLike+
}

1.111. <series>

<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<series xml:lang="de">  <title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>  <respStmt>   <resp>Herausgegeben von</resp>   <name type="person">Manfred Thaller</name>   <name type="org">Max-Planck-Institut für Geschichte</name>  </respStmt>  <title level="s">Serie A: Historische Quellenkunden</title>  <biblScope>Band 11</biblScope> </series>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="biblScope"/>
  <elementRef key="idno"/>
  <elementRef key="textLang"/>
  <classRef key="model.global"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element series
{
   teiatt.global.attributes,
   (
      text
    | teimodel.gLike
    | teititle
    | teimodel.ptrLike
    | teieditor
    | teirespStmt
    | teibiblScope
    | teiidno
    | teitextLang
    | teimodel.global
    | teiavailability
   )*
}

1.112. <seriesStmt>

<seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
May contain
Example
<seriesStmt>  <title>Machine-Readable Texts for the Study of Indian Literature</title>  <respStmt>   <resp>ed. by</resp>   <name>Jan Gonda</name>  </respStmt>  <biblScope unit="volume">1.2</biblScope>  <idno type="ISSN">0 345 6789</idno> </seriesStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence>
   <elementRef key="title"
    maxOccurs="unbounded" minOccurs="1"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="editor"/>
    <elementRef key="respStmt"/>
   </alternate>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="idno"/>
    <elementRef key="biblScope"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element seriesStmt
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   (
      teimodel.pLike+
    | ( teititle+, ( teieditor | teirespStmt )*, ( teiidno | teibiblScope )* )
   )
}

1.113. <sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as ‘born digital’ for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader
Attributes
Contained by
May contain
header: biblFull
namesdates: listObject
Example
<sourceDesc>  <bibl>   <title level="a">The Interesting story of the Children in the Wood</title>. In  <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.  <publisher>OUP</publisher>   <date>1968</date>. </bibl> </sourceDesc>
Example
<sourceDesc>  <p>Born digital: no previous source exists.</p> </sourceDesc>
Content model
<content>
 <alternate>
  <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
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   (
      teimodel.pLike+
    | ( teimodel.biblLike | teimodel.sourceDescPart | teimodel.listLike )+
   )
}

1.114. <sponsor>

<sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]
Moduleheader
Attributes
Member of
Contained by
May contain
Note

Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element <funder>), who provide the funding but do not necessarily take intellectual responsibility.

Example
<sponsor>Association for Computers and the Humanities</sponsor> <sponsor>Association for Computational Linguistics</sponsor> <sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element sponsor
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   teiatt.datable.attributes,
   teimacro.phraseSeq.limited
}

1.115. <standOff>

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

1.116. <stdVals>

<stdVals> (standard values) specifies the format used when standardized date or number values are supplied. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
May contain
core: p
Example
<stdVals>  <p>All integer numbers are left-filled with zeroes to 8 digits.</p> </stdVals>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
    
Schema Declaration
element stdVals
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   teimodel.pLike+
}

1.117. <styleDefDecl>

<styleDefDecl> (style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied. [2.3.5. The Default Style Definition Language Declaration]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
Example
<styleDefDecl scheme="css"  schemeVersion="2.1"/> <!-- ... --> <tagsDecl>  <rendition xml:id="boldface">font-weight: bold;</rendition>  <rendition xml:id="italicstyle">font-style: italic;</rendition> </tagsDecl>
Content model
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
    
Schema Declaration
element styleDefDecl
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   teiatt.styleDef.attributes,
   teimodel.pLike*
}

1.118. <surname>

<surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<surname type="combine">St John Stevas</surname>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element surname
{
   teiatt.global.attributes,
   teiatt.cmc.attributes,
   teiatt.personal.attributes,
   teiatt.typed.attributes,
   teimacro.phraseSeq
}

1.119. <tagUsage>

<tagUsage> (element usage) documents the usage of a specific element within a specified document. [2.3.4. The Tagging Declaration]
Moduleheader
Attributes
gi(generic identifier) specifies the name (generic identifier) of the element indicated by the tag, within the namespace indicated by the parent <namespace> element.
StatusRequired
Datatypeteidata.name
occursspecifies the number of occurrences of this element within the text.
StatusRecommended
Datatypeteidata.count
withId(with unique identifier) specifies the number of occurrences of this element within the text which bear a distinct value for the global xml:id attribute.
StatusRecommended
Datatypeteidata.count
Contained by
header: namespace
May contain
Example
<tagsDecl partial="true">  <rendition scheme="css"   selector="foreign, hixml:id="it"> font-style: italic; </rendition> <!-- ... -->  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="hioccurs="28withId="2"> Used to mark English words italicized in the copy text.</tagUsage>   <tagUsage gi="foreign">Used to mark non-English words in the copy text.</tagUsage> <!-- ... -->  </namespace> </tagsDecl>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element tagUsage
{
   teiatt.global.attributes,
   teiatt.datcat.attributes,
   attribute gi { text },
   attribute occurs { text }?,
   attribute withId { text }?,
   teimacro.limitedContent
}

1.120. <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
Attributes
partialindicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.
StatusRecommended
Datatypeteidata.truthValue
Note

TEI recommended practice is to specify this attribute. When the <tagUsage> elements inside <tagsDecl> are used to list each of the element types in the associated <text>, the value should be given as false. When the <tagUsage> elements inside <tagsDecl> are used to provide usage information or default renditions for only a subset of the elements types within the associated <text>, the value should be true.

Member of
Contained by
header: encodingDesc
May contain
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>
  <elementRef key="rendition"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="namespace"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element tagsDecl
{
   teiatt.global.attributes,
   attribute partial { text }?,
   ( teirendition*, teinamespace* )
}

1.121. <taxonomy>

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

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

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

1.122. <teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text]
Moduleheader
Attributes
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>
  <elementRef key="fileDesc"/>
  <classRef key="model.teiHeaderPart"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="revisionDesc"
   minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element teiHeader
{
   teiatt.global.attributes,
   ( teifileDesc, teimodel.teiHeaderPart*, teirevisionDesc? )
}

1.123. <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
linking: linkGrp
textstructure: back body front
Note

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

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

1.124. <textClass>

<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
Example
<taxonomy>  <category xml:id="acprose">   <catDesc>Academic prose</catDesc>  </category> <!-- other categories here --> </taxonomy> <!-- ... --> <textClass>  <catRef target="#acprose"/>  <classCode scheme="http://www.udcc.org">001.9</classCode>  <keywords scheme="http://authorities.loc.gov">   <list>    <item>End of the world</item>    <item>History - philosophy</item>   </list>  </keywords> </textClass>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="classCode"/>
  <elementRef key="catRef"/>
  <elementRef key="keywords"/>
 </alternate>
</content>
    
Schema Declaration
element textClass
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   ( teiclassCode | teicatRef | teikeywords )*
}

1.125. <textLang>

<textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.6.6. Languages and Writing Systems]
Modulecore
Attributes
mainLang(main language) Kürzelvergabe folgt IANA/ISO 639 2-letter language code.
StatusOptional
Datatypeteidata.language
Legal values are:
sq
Albanisch
ar
Arabisch
bg
Bulgarisch
zh
Chinesisch
da
Dänisch
de
Deutsch
en
Englisch
et
Estnisch
fi
Finnisch
fr
Französisch
ka
Georgisch
el
Griechisch
it
Italienisch
ja
Japanisch
ko
Koreanisch
hr
Kroatisch
la
Lateinisch
nl
Niederländisch
no
Norwegisch
pl
Polnisch
pt
Portugiesisch
ro
Rumänisch
ru
Russisch
sv
Schwedisch
sr
Serbisch
sl
Slowenisch
es
Spanisch
cs
Tschechisch
tr
Türkisch
hu
Ungarisch
uk
Ukrainisch
undefined
noch nicht definiert
otherLangs(other languages) one or more codes identifying any other languages used in the bibliographic work.
StatusOptional
Datatype0–∞ occurrences of teidata.language separated by whitespace
Member of
Contained by
May contain
Note

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

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

Example
<textLang mainLang="enotherLangs="la"> Predominantly in English with Latin glosses</textLang>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element textLang
{
   teiatt.global.attributes,
   attribute mainLang
   {
      "sq"
    | "ar"
    | "bg"
    | "zh"
    | "da"
    | "de"
    | "en"
    | "et"
    | "fi"
    | "fr"
    | "ka"
    | "el"
    | "it"
    | "ja"
    | "ko"
    | "hr"
    | "la"
    | "nl"
    | "no"
    | "pl"
    | "pt"
    | "ro"
    | "ru"
    | "sv"
    | "sr"
    | "sl"
    | "es"
    | "cs"
    | "tr"
    | "hu"
    | "uk"
    | "undefined"
   }?,
   attribute otherLangs { list { * } }?,
   teimacro.specialPara
}

1.126. <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 (nur einmal)
sub
Untertitel (darf mehrfach vorkommen)
sub_addition
Titelergänzungen
alt
Paralleltitel
short
Abkürzung bei Zeitschriften
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.

levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
c
(chapter) Kapitel in einem Buch
unsolved
Solang title-Element nur dummy für Dateneingabe
overall
Titel für Gesamtdatensatz
Note

The level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level ‘a’, and one appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

Member of
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.global.attributes,
   teiatt.canonical.attributes,
   teiatt.cmc.attributes,
   teiatt.datable.attributes,
   teiatt.typed.attribute.subtype,
   attribute type { "main" | "sub" | "sub_addition" | "alt" | "short" }?,
   attribute level
   {
      "a" | "m" | "j" | "s" | "u" | "c" | "unsolved" | "overall"
   }?,
   teimacro.paraContent
}

1.127. <titlePage>

<titlePage> (title page) contains the title page of a text, appearing within the front or back matter. [4.6. Title Pages]
Moduletextstructure
Attributes
typeclassifies the title page according to any convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Note

This attribute allows the same element to be used for volume title pages, series title pages, etc., as well as for the ‘main’ title page of a work.

Member of
Contained by
textstructure: back front
May contain
Example
<titlePage>  <docTitle>   <titlePart type="main">THOMAS OF Reading.</titlePart>   <titlePart type="alt">OR, The sixe worthy yeomen of the West.</titlePart>  </docTitle>  <docEdition>Now the fourth time corrected and enlarged</docEdition>  <byline>By T.D.</byline>  <figure>   <head>TP</head>   <p>Thou shalt labor till thou returne to duste</p>   <figDesc>Printers Ornament used by TP</figDesc>  </figure>  <docImprint>Printed at <name type="place">London</name> for <name>T.P.</name>   <date>1612.</date>  </docImprint> </titlePage>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.titlepagePart"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.titlepagePart"/>
   <classRef key="model.global"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element titlePage
{
   teiatt.global.attributes,
   teiatt.typed.attribute.subtype,
   attribute type { text }?,
   (
      teimodel.global*,
      teimodel.titlepagePart,
      ( teimodel.titlepagePart | teimodel.global )*
   )
}

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

1.129. <unit>

<unit> contains a symbol, a word or a phrase referring to a unit of measurement in any kind of formal or informal system. [3.6.3. Numbers and Measures]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleHere is an example of a <unit> element holding a unitRef attribute that points to a definition of the unit in the TEI header.
<measure>  <num>3</num>  <unit unitRef="#ell">ells</unit> </measure> <!-- In the TEI Header: --> <encodingDesc>  <unitDecl>   <unitDef xml:id="ell">    <label>ell</label>    <placeName ref="#iceland"/>    <desc>A unit of measure for cloth, roughly equivalent to 18 inches, or from an adult male’s elbow to the tip of the middle finger.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<measure>  <num>2</num>  <unit>kg</unit> </measure>
Example
<measure type="value">  <num>3</num>  <unit type="timeunit="min">minute</unit> </measure>
Example
<measure type="interval">  <num atLeast="1.2">1.2</num> to <num atMost="5.6">5.6</num>  <unit type="velocityunit="km/h">km/h</unit> </measure>
Example
<p>Light travels at <num value="3E10">3×10^10</num>  <unit type="rateunit="cm/s">   <unit type="space">cm</unit> per <unit type="time">second</unit>  </unit>.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element unit
{
   teiatt.global.attributes,
   teiatt.cmc.attributes,
   teiatt.measurement.attributes,
   teiatt.typed.attributes,
   teimacro.phraseSeq
}

1.130. <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 contain
header: unitDef
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,
   teiunitDef+
}

1.131. <unitDef>

<unitDef> (unit definition) contains descriptive information related to a specific unit of measurement. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
Contained by
header: unitDecl
May contain
core: unit
header: conversion
namesdates: placeName
Example
<unitDecl>  <unitDef type="lengthxml:id="pechys">   <label>πῆχυς</label>   <placeName ref="#athens"/>   <conversion formula="$fromUnit div 24"    fromUnit="#daktylostoUnit="#pechys"/>   <desc>Equivalent to a cubit or 24 daktyloi.</desc>  </unitDef>  <unitDef type="lengthxml:id="daktylos">   <label>δάκτυλος</label>   <placeName ref="#athens"/>   <desc>A basic unit of length equivalent to one finger (or the size of a thumb) in ancient Greece.</desc>  </unitDef> </unitDecl>
Content model
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.labelLike"
   minOccurs="1"/>
  <classRef key="model.placeNamePart"
   minOccurs="0"/>
  <elementRef key="conversion"
   minOccurs="0"/>
  <elementRef key="unit" minOccurs="0"/>
 </alternate>
</content>
    
Schema Declaration
element unitDef
{
   teiatt.global.attributes,
   teiatt.canonical.attributes,
   teiatt.datable.attributes,
   teiatt.typed.attributes,
   ( teimodel.labelLike | teimodel.placeNamePart? | teiconversion? | teiunit? )+
}

1.132. <xenoData>

<xenoData> (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed. [2.5. Non-TEI Metadata]
Moduleheader
Attributes
Member of
Contained by
header: teiHeader
linking: standOff
May containANY
ExampleThis example presumes that the prefix dc has been bound to the namespace http://purl.org/dc/elements/1.1/ and the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#. Note: The about attribute on the <rdf:Description> in this example gives a URI indicating the resource to which the metadata contained therein refer. The <rdf:Description> in the second <xenoData> block has a blank about, meaning it is pointing at the current document, so the RDF is about the document within which it is contained, i.e. the TEI document containing the <xenoData> block. Similarly, any kind of relative URI may be used, including fragment identifiers (see [[undefined SG-id]]). Do note, however, that if the contents of the <xenoData> block are to be extracted and used elsewhere, any relative URIs will have to be resolved accordingly.
<xenoData    xmlns:dc="http://purl.org/dc/elements/1.1/"    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">  <rdf:RDF>   <rdf:Description rdf:about="http://www.worldcat.org/oclc/606621663">    <dc:title>The description of a new world, called the blazing-world</dc:title>    <dc:creator>The Duchess of Newcastle</dc:creator>    <dc:date>1667</dc:date>    <dc:identifier>British Library, 8407.h.10</dc:identifier>    <dc:subject>utopian fiction</dc:subject>   </rdf:Description>  </rdf:RDF> </xenoData> <xenoData>  <rdf:RDF>   <rdf:Description rdf:about="">    <dc:title>The Description of a New World, Called the Blazing-World, 1668</dc:title>    <dc:creator>Cavendish, Margaret (Lucas), Duchess of Newcastle</dc:creator>    <dc:publisher>Women Writers Project</dc:publisher>    <dc:date>2002-02-12</dc:date>    <dc:subject>utopian fiction</dc:subject>   </rdf:Description>  </rdf:RDF> </xenoData>
ExampleIn this example, the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#, the prefix dc is bound to the namespace http://purl.org/dc/elements/1.1/, and the prefix cc is bound to the namespace http://web.resource.org/cc/.
<xenoData    xmlns:cc="http://web.resource.org/cc/"    xmlns:dc="http://purl.org/dc/elements/1.1/"    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">  <rdf:RDF>   <cc:Work rdf:about="">    <dc:title>Applied Software Project Management - review</dc:title>    <dc:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>    <dc:license rdf:resource="http://creativecommons.org/licenses/by-sa/2.0/uk/"/>   </cc:Work>   <cc:License rdf:about="http://creativecommons.org/licenses/by-sa/2.0/uk/">    <cc:permits rdf:resource="http://web.resource.org/cc/Reproduction"/>    <cc:permits rdf:resource="http://web.resource.org/cc/Distribution"/>    <cc:requires rdf:resource="http://web.resource.org/cc/Notice"/>    <cc:requires rdf:resource="http://web.resource.org/cc/Attribution"/>    <cc:permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/>    <cc:requires rdf:resource="http://web.resource.org/cc/ShareAlike"/>   </cc:License>  </rdf:RDF> </xenoData>
ExampleIn this example, the prefix dc is again bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/, and the prefix oai_dc is bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/.
<xenoData    xmlns:dc="http://purl.org/dc/elements/1.1/"    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/">  <oai_dc:dc>   <dc:title>The colonial despatches of Vancouver Island and British      Columbia 1846-1871: 11566, CO 60/2, p. 291; received 13 November.      Trevelyan to Merivale (Permanent Under-Secretary)</dc:title>   <dc:date>1858-11-12</dc:date>   <dc:creator>Trevelyan</dc:creator>   <dc:publisher>University of Victoria Humanities Computing and Media      Centre, and UVic Libraries</dc:publisher>   <dc:type>InteractiveResource</dc:type>   <dc:format>application/xhtml+xml</dc:format>   <dc:type>text</dc:type>   <dc:identifier>http://bcgenesis.uvic.ca/getDoc.htm?id=B585TE13.scx</dc:identifier>   <dc:rights>This document is licensed under a Creative Commons …</dc:rights>   <dc:language>(SCHEME=ISO639) en</dc:language>   <dc:source>Transcribed from microfilm and/or original documents, and      marked up in TEI P5 XML. The interactive XHTML resource is generated      from the XHTML using XQuery and XSLT.</dc:source>   <dc:source>repository: CO</dc:source>   <dc:source>coNumber: 60</dc:source>   <dc:source>coVol: 2</dc:source>   <dc:source>page: 291</dc:source>   <dc:source>coRegistration: 11566</dc:source>   <dc:source>received: received 13 November</dc:source>   <dc:subject>Trevelyan, Sir Charles Edward</dc:subject>   <dc:subject>Merivale, Herman</dc:subject>   <dc:subject>Elliot, T. Frederick</dc:subject>   <dc:subject>Moody, Colonel Richard Clement</dc:subject>   <dc:subject>Lytton, Sir Edward George Earle Bulwer</dc:subject>   <dc:subject>Jadis, Vane</dc:subject>   <dc:subject>Carnarvon, Earl</dc:subject>   <dc:subject>British Columbia</dc:subject>   <dc:description>British Columbia correspondence: Public Offices      document (normally correspondence between government      departments)</dc:description>  </oai_dc:dc> </xenoData>
ExampleIn this example, the prefix mods is bound to the namespace http://www.loc.gov/mods/v3.
<xenoData    xmlns:mods="http://www.loc.gov/mods/v3">  <mods:mods>   <mods:titleInfo>    <mods:title>Academic adaptation and cross-cultural        learning experiences of Chinese students at American        universities</mods:title>    <mods:subTitle>a narrative inquiry</mods:subTitle>   </mods:titleInfo>   <mods:name authority="local"    type="personal">    <mods:namePart/>    <mods:role>     <mods:roleTerm authority="marcrelator"      type="text">Author</mods:roleTerm>    </mods:role>    <mods:affiliation>Northeastern University</mods:affiliation>    <mods:namePart type="given">Hong</mods:namePart>    <mods:namePart type="family">Zhang</mods:namePart>   </mods:name>   <mods:name authority="local"    type="personal">    <mods:namePart/>    <mods:role>     <mods:roleTerm authority="local"      type="text">Advisor</mods:roleTerm>    </mods:role>    <mods:namePart type="given">Liliana</mods:namePart>    <mods:namePart type="family">Meneses</mods:namePart>   </mods:name>    <!-- ... -->   <mods:typeOfResource>text</mods:typeOfResource>   <mods:genre>doctoral theses</mods:genre>   <mods:originInfo>    <mods:place>     <mods:placeTerm type="text">Boston (Mass.)</mods:placeTerm>    </mods:place>    <mods:publisher>Northeastern University</mods:publisher>    <mods:copyrightDate encoding="w3cdtf"     keyDate="yes">2013</mods:copyrightDate>   </mods:originInfo>   <mods:language>    <mods:languageTerm authority="iso639-2b"     type="code">eng</mods:languageTerm>   </mods:language>   <mods:physicalDescription>    <mods:form authority="marcform">electronic</mods:form>    <mods:digitalOrigin>born digital</mods:digitalOrigin>   </mods:physicalDescription> <!-- ... -->  </mods:mods> </xenoData>
ExampleThis example shows GeoJSON embedded in <xenoData>. Note that JSON does not permit newlines inside string values. These must be escaped as \n. To avoid the accidental insertion of newlines by software, the use of xml:space is recommended. Blocks of JSON should be wrapped in CDATA sections, as they may contain characters illegal in XML.
<xenoData xml:space="preserve"> <![CDATA[ {     "features": [         {             "geometry": {                 "type": "Point",                 "coordinates": [                     68.388483,                     33.498616                 ]             },             "type": "Feature",             "id": "darmc-location-19727",             "properties": {                 "snippet": "Unknown; 330 BC - AD 300",                 "link": "https://pleiades.stoa.org/places/59694/darmc-location-19727",                 "description": "5M scale point location",                 "location_precision": "precise",                 "title": "DARMC location 19727"             }         }     ],     "id": "59694",     "subject": [         "dare:ancient=1",         "dare:feature=settlement",         "dare:major=0"     ],     "title": "Arachosiorum Oppidum/Alexandria",     "provenance": "Barrington Atlas: BAtlas 6 B3 Arachosiorum Oppidum/Alexandria",     "placeTypeURIs": [         "https://pleiades.stoa.org/vocabularies/place-types/settlement"     ],     "details": "<p>The Barrington Atlas Directory notes: Kalat-e-Ghilzai? AFG</p>",     "@context": {         "snippet": "dcterms:abstract",         "rights": "dcterms:rights",         "description": "dcterms:description",         "title": "dcterms:title",         "dcterms": "http://purl.org/dc/terms/",         "subject": "dcterms:subject",         "uri": "@id",         "created": "dcterms:created"     },     "review_state": "published",     "type": "FeatureCollection",     "description": "An ancient place, cited: BAtlas 6 B3 Arachosiorum Oppidum/Alexandria",     "reprPoint": [         68.388483,         33.498616     ],     "placeTypes": [         "settlement"     ],     "bbox": [         68.388483,         33.498616,         68.388483,         33.498616     ],     "rights": "Copyright © The Contributors. Sharing and remixing permitted under CC-BY.",     "created": "2010-09-23T04:31:55Z",     "uri": "https://pleiades.stoa.org/places/59694",     "creators": [         {             "username": null,             "name": "M.U. Erdosy"         }     ],     "@type": "Place" } ]]> </xenoData>
Note: the example above has been trimmed for legibility. The original may be found linked from Arachosiorum Oppidum/Alexandria. The contributors, listed per the license terms, are R. Talbert, Jeffrey Becker, W. Röllig, Tom Elliott, H. Kopp, DARMC, Sean Gillies, B. Siewert-Mayer, Francis Deblauwe, and Eric Kansa.
Content model
<content>
 <alternate>
  <textNode/>
  <anyElement maxOccurs="unbounded"
   minOccurs="1"/>
 </alternate>
</content>
    
Schema Declaration
element xenoData
{
   teiatt.global.attributes,
   teiatt.declarable.attributes,
   teiatt.typed.attributes,
   ( text | anyElement_xenoData_1+ )
}

2. Model classes

2.1. model.annotationLike

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

2.2. model.annotationPart.body

model.annotationPart.body groups elements which may be used as an <annotation> body.
Moduletei
Used by
Membersnote ptr ref

2.3. model.applicationLike

model.applicationLike groups elements used to record application-specific information about a document in its header.
Moduletei
Used by
Membersapplication

2.4. model.attributable

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

2.5. model.availabilityPart

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

2.6. model.biblLike

2.8. model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.cmc model.divPart[model.lLike model.pLike[p]] model.inter[model.attributable[model.quoteLike] model.biblLike[bibl biblFull biblStruct listBibl] model.egLike model.labelLike model.listLike[listObject] model.oddDecl model.stageLike]
Note

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

2.9. model.correspActionPart

model.correspActionPart groups elements which define the parts (usually names, dates and places) of one action related to the correspondence.
Moduletei
Used by
Membersmodel.addressLike model.dateLike[date] model.nameLike[model.nameLike.agent[name orgName] model.offsetLike model.persNamePart[forename persPronouns surname] model.placeStateLike[model.placeNamePart[placeName]] eventName idno objectName] note noteGrp

2.10. model.correspContextPart

model.correspContextPart groups elements which may appear as part of the correspContext element.
Moduletei
Used by
Membersmodel.pLike[p] model.ptrLike[ptr ref] note noteGrp

2.11. model.correspDescPart

model.correspDescPart groups together metadata elements for describing correspondence.
Moduletei
Used by
MemberscorrespAction correspContext note noteGrp

2.12. model.dateLike

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

2.13. 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.14. model.divGenLike

model.divGenLike groups elements used to represent a structural division which is generated rather than explicitly present in the source.
Moduletei
Used by
MembersdivGen

2.15. model.divLike

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

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

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

2.19. model.editorialDeclPart

model.editorialDeclPart groups elements which may be used inside <editorialDecl> and appear multiple times.
Moduletei
Used by
Memberscorrection hyphenation interpretation normalization punctuation quotation segmentation stdVals

2.20. 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 title

2.21. model.encodingDescPart

model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.
Moduletei
Used by
MembersappInfo classDecl editorialDecl geoDecl listPrefixDef projectDesc refsDecl samplingDecl schemaRef styleDefDecl tagsDecl unitDecl

2.22. model.frontPart

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

2.24. 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
Membersellipsis

2.25. 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
MemberslinkGrp
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.26. model.graphicLike

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

2.27. model.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.28. model.highlighted

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

2.29. model.imprintPart

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

2.30. 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 biblFull biblStruct listBibl] model.egLike model.labelLike model.listLike[listObject] model.oddDecl model.stageLike

2.31. 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 title] model.hiLike[hi] model.pPart.data[model.addressLike model.dateLike[date] model.measureLike[unit] model.nameLike[model.nameLike.agent[name orgName] model.offsetLike model.persNamePart[forename persPronouns surname] model.placeStateLike[model.placeNamePart[placeName]] eventName idno objectName]] model.pPart.editorial model.pPart.msdesc model.phrase.xml model.ptrLike[ptr ref]

2.32. model.listLike

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

2.33. model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.6.3. Numbers and Measures]
Moduletei
Used by
Membersunit

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

2.35. model.nameLike

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

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

2.36. model.nameLike.agent

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

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

2.37. model.noteLike

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

2.38. model.objectLike

model.objectLike groups elements which describe objects.
Moduletei
Used by
MemberslistObject object

2.40. 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[unit] model.nameLike[model.nameLike.agent[name orgName] model.offsetLike model.persNamePart[forename persPronouns surname] model.placeStateLike[model.placeNamePart[placeName]] eventName idno objectName]

2.41. 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 model.pPart.transcriptional

2.42. model.paraPart

model.paraPart groups elements that may appear in paragraphs and similar elements. [3.1. Paragraphs]
Moduletei
Used by
Membersmodel.gLike model.global[model.global.edit[ellipsis] model.global.meta[linkGrp] model.milestoneLike[lb] model.noteLike[note noteGrp]] model.inter[model.attributable[model.quoteLike] model.biblLike[bibl biblFull biblStruct listBibl] model.egLike model.labelLike model.listLike[listObject] model.oddDecl model.stageLike] model.lLike model.phrase[model.graphicLike[graphic] model.highlighted[model.emphLike[foreign title] model.hiLike[hi]] model.lPart model.pPart.data[model.addressLike model.dateLike[date] model.measureLike[unit] model.nameLike[model.nameLike.agent[name orgName] model.offsetLike model.persNamePart[forename persPronouns surname] model.placeStateLike[model.placeNamePart[placeName]] eventName idno objectName]] model.pPart.edit[model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr ref] model.segLike model.specDescLike ruby]

2.43. model.persNamePart

model.persNamePart groups elements which form part of a personal name. [14.2.1. Personal Names]
Modulenamesdates
Used by
Membersforename persPronouns surname

2.44. model.persStateLike

model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
Moduletei
Used by
Membersgender persPronouns persona
Note

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

2.45. model.personPart

model.personPart groups elements which form part of the description of a person. [16.2.2. The Participant Description]
Moduletei
Used by
Membersmodel.biblLike[bibl biblFull biblStruct listBibl] model.eventLike model.persStateLike[gender persPronouns persona] idno name

2.46. 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 title] model.hiLike[hi]] model.lPart model.pPart.data[model.addressLike model.dateLike[date] model.measureLike[unit] model.nameLike[model.nameLike.agent[name orgName] model.offsetLike model.persNamePart[forename persPronouns surname] model.placeStateLike[model.placeNamePart[placeName]] eventName idno objectName]] model.pPart.edit[model.pPart.editorial model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml model.ptrLike[ptr ref] model.segLike model.specDescLike ruby
Note

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

2.47. model.placeNamePart

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

2.48. model.placeStateLike

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

2.49. model.profileDescPart

model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.
Moduletei
Used by
Membersabstract calendarDesc correspDesc creation langUsage textClass

2.50. model.ptrLike

2.51. 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
Membersauthority distributor publisher
Note

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

See also model.publicationStmtPart.detail.

2.52. 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.53. model.resource

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

2.54. model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Moduletei
Used by
Membersauthor editor funder principal respStmt sponsor

2.55. model.standOffPart

2.56. model.teiHeaderPart

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

2.57. model.titlepagePart

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

3. Attribute classes

3.1. att.anchoring

att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.
Moduletei
Membersnote noteGrp
Attributes
anchored(anchored) indicates whether the copy text shows the exact place of reference for the note.
StatusOptional
Datatypeteidata.truthValue
Defaulttrue
Note

In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

targetEnd(target end) points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 17.2.4.6. range().

Example
<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p> <!-- elsewhere in the document --> <noteGrp targetEnd="#A55234">  <note xml:lang="en"> Quatuor Tempora, so called dry fast days.  </note>  <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.  </note> </noteGrp>

3.2. 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.3. att.breaking

att.breaking provides attributes to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.11.3. Milestone Elements]
Moduletei
Memberslb
Attributes
breakindicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace.
StatusRecommended
Datatypeteidata.enumerated
Sample values include
yes
the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
no
the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
maybe
the encoding does not take any position on this issue.
In the following lines from the Dream of the Rood, the words lāðost and reord-berendum each start on one line and continue onto the next.
<ab> ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt . leodum la<lb break="no"/> ðost ærþan ichim lifes ƿeȝ rihtne ȝerymde reord be<lb break="no"/> rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer... </ab>

3.4. att.cReferencing

att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer.
Moduletei
Membersptr ref
Attributes
cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header.
StatusOptional
Datatypeteidata.text
Note

The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 17.2.5. Canonical References) is applied to it the result is a valid URI reference to the intended target.

The <refsDecl> to use may be indicated with the decls attribute.

Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.

3.5. att.calendarSystem

att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Membersdate
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian"  when="1732-02-22">Feb. 11, 1731/32, O.S.</date>).
He was born on <date calendar="#gregorian #julian"  when="1732-02-22">Feb. 22, 1732 (Feb. 11, 1731/32, O.S.)</date>.
Note

Note that the calendar attribute declares the calendar system used to interpret the textual content of an element, as it appears on an original source. It does not modify the interpretation of the normalization attributes provided by att.datable.w3c, att.datable.iso, or att.datable.custom. Attributes from those first two classes are always interpreted as Gregorian or proleptic Gregorian dates, as per the respective standards on which they are based. The calender system used to interpret the last (att.datable.custom) may be specified with datingMethod.

3.6. 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 forename name objectName orgName placeName surname] author editor pubPlace] authority bibl biblFull biblStruct catDesc correspDesc date distributor funder object principal publisher resp respStmt sponsor title unitDecl unitDef
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.7. att.citeStructurePart

att.citeStructurePart provides attributes for selecting particular elements within a document.
Moduleheader
MembersciteData citeStructure
Attributes
use(use) supplies an XPath selection pattern using the syntax defined in [[undefined XSLT3]]. The XPath pattern is relative to the context given in match, which will either be a sibling attribute in the case of <citeStructure> or on the parent <citeStructure> in the case of <citeData>.
StatusRequired
Datatypeteidata.xpath

3.8. att.cmc

att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment.
Moduletei
Membersbibl biblFull biblStruct date foreign forename graphic hi idno lb linkGrp listBibl listObject name note noteGrp objectName orgName p persPronouns placeName ptr ref ruby surname title unit
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.9. 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
Membersapplication author change conversion creation date editor eventName funder gender idno licence name objectName orgName persPronouns placeName principal resp sponsor title unitDecl unitDef
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.10. 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[application author change conversion creation date editor eventName funder gender idno licence name objectName orgName persPronouns placeName principal resp sponsor title unitDecl unitDef]
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.11. 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[application author change conversion creation date editor eventName funder gender idno licence name objectName orgName persPronouns placeName principal resp sponsor title unitDecl unitDef]
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.12. 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[application author change conversion creation date editor eventName funder gender idno licence name objectName orgName persPronouns placeName principal resp sponsor title unitDecl unitDef]
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.13. att.datcat

att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [10.5.2. Lexical View 19.3. Other Atomic Feature Values]
Moduletei
Memberscategory tagUsage taxonomy
Attributes
datcatprovides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcatprovides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcatprovides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
ExampleThe example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.
<fs>  <f datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"   name="POS">   <symbol value="NN"    valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>  </f> <!-- ... --> </fs>
‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545 is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [[undefined FS]].
<fs>  <f fVal="#commonNounname="POS"/> <!-- ... --> </fs>
The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories.
<fvLib n="POS values">  <symbol datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"   value="NNxml:id="commonNoun"/>  <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"   value="NPxml:id="properNoun"/> <!-- ... --> </fvLib>
Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.
ExampleIn the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above.
<gramGrp>  <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"   valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos> </gramGrp>
Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>:
<tagsDecl partial="true"> <!-- ... -->  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="pos"    targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage>   <tagUsage gi="case"    targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage> <!-- ... -->  </namespace> </tagsDecl>
Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below:
<listPrefixDef>  <prefixDef ident="ccrmatchPattern="pos"   replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <prefixDef ident="ccrmatchPattern="adj"   replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/> </listPrefixDef> <!-- ... --> <entry> <!--...-->  <form>   <orth>isotope</orth>  </form>  <gramGrp>   <pos datcat="ccr:pos"    valueDatcat="ccr:adj">adj</pos>  </gramGrp> <!--...--> </entry>
This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>.
ExampleThe <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.
<encodingDesc> <!-- ... -->  <classDecl> <!-- ... -->   <taxonomy datcat="https://universaldependencies.org/u/dep/index.html"    xml:id="UD-SYN">    <desc>     <term>UD syntactic relations</term>    </desc>    <category valueDatcat="https://universaldependencies.org/u/dep/acl.html"     xml:id="acl">     <catDesc>      <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>    </category>    <category valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html"     xml:id="acl_relcl">     <catDesc>      <term>acl:relcl</term>: relative clause modifier</catDesc>    </category>    <category valueDatcat="https://universaldependencies.org/u/dep/advcl.html"     xml:id="advcl">     <catDesc>      <term>advcl</term>: Adverbial clause modifier</catDesc>    </category> <!-- ... -->   </taxonomy>  </classDecl> </encodingDesc>
The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly.
ExampleThe targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.
<fDecl name="POS"  targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">  <fDescr>part of speech (morphosyntactic category)</fDescr>  <vRange>   <vAlt>    <symbol datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"     value="NN"/>    <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"     value="NP"/> <!-- ... -->   </vAlt>  </vRange> </fDecl>
Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.
ExampleThe att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.
<!-- in the dictionary header --><encodingDesc>  <classDecl>   <taxonomy xml:id="domains"> <!--...-->    <category xml:id="domain.medical_and_health_sciences">     <catDesc xml:lang="en">Medical and Health Sciences</catDesc>     <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>     <category valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025"      xml:id="domain.medical_and_health_sciences.medicine">      <catDesc xml:lang="en">       <term>Medicine</term>       <gloss> <!--...-->       </gloss>      </catDesc>      <catDesc xml:lang="pt">       <term>Medicina</term>       <gloss> <!--...-->       </gloss>      </catDesc>     </category>    </category> <!--...-->   </taxonomy>  </classDecl> </encodingDesc> <!-- inside an <entry> element: --> <usg type="domain"  valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg>
In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH).
Note

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

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

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

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

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

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

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

3.14. att.declarable

att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [16.3. Associating Contextual Information with a Text]
Moduletei
Membersavailability bibl biblFull biblStruct correction correspDesc editorialDecl geoDecl hyphenation interpretation langUsage listBibl listObject normalization projectDesc punctuation quotation refsDecl samplingDecl segmentation seriesStmt sourceDesc stdVals styleDefDecl textClass xenoData
Attributes
defaultindicates whether or not this element is selected by default when its parent is selected.
StatusOptional
Datatypeteidata.truthValue
Legal values are:
true
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.[Default]
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

3.15. att.declaring

att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [16.3. Associating Contextual Information with a Text]
Moduletei
Membersback body div front graphic listAnnotation object p ptr ref standOff text
Attributes
decls(declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

3.16. att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Moduletei
Membersdate ellipsis
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.17. att.divLike

att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure]
Moduletei
Membersdiv
Attributes
org(organization) specifies how the content of the division is organized.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
composite
no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships.
uniform
the immediate contents of this element are regarded as forming a logical unit, to be processed in sequence.[Default]
sampleindicates whether this division is a sample of the original source and if so, from which part.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
initial
division lacks material present at end in source.
medial
division lacks material at start and end.
final
division lacks material at start.
unknown
position of sampled material within original unknown.
complete
division is not a sample.[Default]

3.18. att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Moduletei
Membersbibl biblFull biblStruct change object revisionDesc
Attributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">  <change status="published"   when="2010-10-21"/>  <change status="clearedwhen="2010-10-02"/>  <change status="embargoed"   when="2010-08-02"/>  <change status="frozenwhen="2010-05-01"   who="#MSM"/>  <change status="draftwhen="2010-03-01"   who="#LB"/> </revisionDesc>

3.19. 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[rt] date eventName gender name objectName orgName persPronouns persona placeName
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.20. att.edition

att.edition provides attributes identifying the source edition from which some encoded feature derives.
Moduletei
Memberslb refState
Attributes
ed(edition) supplies a sigil or other arbitrary identifier for the source edition in which the associated feature (for example, a page, column, or line beginning) occurs at this point in the text.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
edRef(edition reference) provides a pointer to the source edition in which the associated feature (for example, a page, column, or line beginning) occurs at this point in the text.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Example
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example
<listBibl>  <bibl xml:id="stapledon1937">   <author>Olaf Stapledon</author>,  <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>  </bibl>  <bibl xml:id="stapledon1968">   <author>Olaf Stapledon</author>,  <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>  </bibl> </listBibl> <!-- ... --> <p>Looking into the future aeons from the supreme moment of the cosmos, I saw the populations still with all their strength maintaining the<pb edRef="#stapledon1968n="411"/>essentials of their ancient culture, still living their personal lives in zest and endless novelty of action, … I saw myself still preserving, though with increasing difficulty, my lucid con-<pb edRef="#stapledon1937n="291"/>sciousness;</p>

3.21. att.formula

att.formula provides attributes for defining a mathematical formula. [2.3.9. The Unit Declaration]
Moduletei
Membersconversion
Attributes
formulaA formula is provided to describe a mathematical calculation such as a conversion between measurement systems.
StatusOptional
Datatypeteidata.xpath
Example
<encodingDesc>  <unitDecl>   <unitDef type="linearxml:id="stadium">    <label>stadium</label>    <placeName ref="#rome"/>    <conversion formula="$fromUnit * 625"     fromUnit="#pestoUnit="#stadium"/>    <desc>The stadium was a Roman unit of linear measurement equivalent to 625 pedes, or Roman feet.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<encodingDesc>  <unitDecl>   <unitDef type="powerxml:id="wmw">    <label>whatmeworry</label>    <conversion formula="$fromUnit * 1"     fromUnit="#hpktoUnit="#wmw"/>    <desc>In the Potrzebie system of measures as introduced by Donald Knuth, the whatmeworry unit of power is equivalent to one hah per kovac.</desc>   </unitDef>   <unitDef type="powerxml:id="kwmw">    <label>kilowhatmeworry</label>    <conversion formula="$fromUnit div 1000"     fromUnit="#wmwtoUnit="#kwmw"/>    <desc>The kilowhatmeworry is equivalent to 1000 whatmeworries.</desc>   </unitDef>   <unitDef type="powerxml:id="ap">    <label>kilowhatmeworry</label>    <conversion formula="$fromUnit div 100"     fromUnit="#kwmwtoUnit="#ap"/>    <desc>One unit of aeolipower (A.P.) is equivalent to 100 kilowhatmeworries.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<conversion formula="$fromUnit cast as xs:decimal * 0.000372"  fromUnit="#furlongsPerFortnighttoUnit="#milesPerHour"/>
Example
<conversion formula="$fromUnit cast as xs:decimal * 144 div 60"  fromUnit="#decidaytoUnit="hour"/>
Note

This attribute class provides formula for use in defining a value used in mathematical calculation. It can be used to store a mathematical operation needed to convert from one system of measurement to another. We use the teidata.xpath datatype to express this value in order to communicate mathematical operations on an XML node or nodes. The $fromUnit variable notation simplifies referencing of the fromUnit attribute on the parent <conversion> element. Note that ‘div’ is required to express the division operator in XPath.

3.22. 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.23. att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Moduletei
MembersTEI abstract analytic annotation appInfo application author authority availability back bibl biblFull biblScope biblStruct body cRefPattern calendar calendarDesc catDesc catRef category change citeData citeStructure citedRange classCode classDecl conversion correction correspAction correspContext correspDesc creation date distributor div divGen edition editionStmt editor editorialDecl ellipsis encodingDesc eventName extent fileDesc foreign forename front funder gender geoDecl graphic handNote hi hyphenation idno imprint interpretation keywords langUsage language lb licence linkGrp listAnnotation listBibl listChange listObject listPrefixDef monogr name namespace normalization note noteGrp notesStmt object objectIdentifier objectName orgName p persPronouns persona placeName prefixDef principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation quotation rb ref refState refsDecl relatedItem rendition resp respStmt revisionDesc rt ruby samplingDecl schemaRef scriptNote segmentation series seriesStmt sourceDesc sponsor standOff stdVals styleDefDecl surname tagUsage tagsDecl taxonomy teiHeader text textClass textLang title titlePage titleStmt unit unitDecl unitDef xenoData
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.24. att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [17. Linking, Segmentation, and Alignment]
Modulelinking
Membersatt.global[TEI abstract analytic annotation appInfo application author authority availability back bibl biblFull biblScope biblStruct body cRefPattern calendar calendarDesc catDesc catRef category change citeData citeStructure citedRange classCode classDecl conversion correction correspAction correspContext correspDesc creation date distributor div divGen edition editionStmt editor editorialDecl ellipsis encodingDesc eventName extent fileDesc foreign forename front funder gender geoDecl graphic handNote hi hyphenation idno imprint interpretation keywords langUsage language lb licence linkGrp listAnnotation listBibl listChange listObject listPrefixDef monogr name namespace normalization note noteGrp notesStmt object objectIdentifier objectName orgName p persPronouns persona placeName prefixDef principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation quotation rb ref refState refsDecl relatedItem rendition resp respStmt revisionDesc rt ruby samplingDecl schemaRef scriptNote segmentation series seriesStmt sourceDesc sponsor standOff stdVals styleDefDecl surname tagUsage tagsDecl taxonomy teiHeader text textClass textLang title titlePage titleStmt unit unitDecl unitDef xenoData]
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.25. 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 abstract analytic annotation appInfo application author authority availability back bibl biblFull biblScope biblStruct body cRefPattern calendar calendarDesc catDesc catRef category change citeData citeStructure citedRange classCode classDecl conversion correction correspAction correspContext correspDesc creation date distributor div divGen edition editionStmt editor editorialDecl ellipsis encodingDesc eventName extent fileDesc foreign forename front funder gender geoDecl graphic handNote hi hyphenation idno imprint interpretation keywords langUsage language lb licence linkGrp listAnnotation listBibl listChange listObject listPrefixDef monogr name namespace normalization note noteGrp notesStmt object objectIdentifier objectName orgName p persPronouns persona placeName prefixDef principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation quotation rb ref refState refsDecl relatedItem rendition resp respStmt revisionDesc rt ruby samplingDecl schemaRef scriptNote segmentation series seriesStmt sourceDesc sponsor standOff stdVals styleDefDecl surname tagUsage tagsDecl taxonomy teiHeader text textClass textLang title titlePage titleStmt unit unitDecl unitDef xenoData]
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.26. 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 abstract analytic annotation appInfo application author authority availability back bibl biblFull biblScope biblStruct body cRefPattern calendar calendarDesc catDesc catRef category change citeData citeStructure citedRange classCode classDecl conversion correction correspAction correspContext correspDesc creation date distributor div divGen edition editionStmt editor editorialDecl ellipsis encodingDesc eventName extent fileDesc foreign forename front funder gender geoDecl graphic handNote hi hyphenation idno imprint interpretation keywords langUsage language lb licence linkGrp listAnnotation listBibl listChange listObject listPrefixDef monogr name namespace normalization note noteGrp notesStmt object objectIdentifier objectName orgName p persPronouns persona placeName prefixDef principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation quotation rb ref refState refsDecl relatedItem rendition resp respStmt revisionDesc rt ruby samplingDecl schemaRef scriptNote segmentation series seriesStmt sourceDesc sponsor standOff stdVals styleDefDecl surname tagUsage tagsDecl taxonomy teiHeader text textClass textLang title titlePage titleStmt unit unitDecl unitDef xenoData]
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.27. 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 abstract analytic annotation appInfo application author authority availability back bibl biblFull biblScope biblStruct body cRefPattern calendar calendarDesc catDesc catRef category change citeData citeStructure citedRange classCode classDecl conversion correction correspAction correspContext correspDesc creation date distributor div divGen edition editionStmt editor editorialDecl ellipsis encodingDesc eventName extent fileDesc foreign forename front funder gender geoDecl graphic handNote hi hyphenation idno imprint interpretation keywords langUsage language lb licence linkGrp listAnnotation listBibl listChange listObject listPrefixDef monogr name namespace normalization note noteGrp notesStmt object objectIdentifier objectName orgName p persPronouns persona placeName prefixDef principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation quotation rb ref refState refsDecl relatedItem rendition resp respStmt revisionDesc rt ruby samplingDecl schemaRef scriptNote segmentation series seriesStmt sourceDesc sponsor standOff stdVals styleDefDecl surname tagUsage tagsDecl taxonomy teiHeader text textClass textLang title titlePage titleStmt unit unitDecl unitDef xenoData]
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.28. att.handFeatures

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

Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied.

3.29. 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.30. att.locatable

att.locatable provides attributes for referencing locations by pointing to entries in a canonical list of places. [2.3.9. The Unit Declaration 14.3.4.3. States, Traits, and Events]
Moduletei
Membersconversion
Attributes
whereindicates one or more locations by pointing to a <place> element or other canonical description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

3.31. att.measurement

att.measurement provides attributes to represent a regularized or normalized measurement.
Moduletei
Membersunit
Attributes
unit(unit) indicates the units used for the measurement, usually using the standard symbol for the desired units.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
m
(metre) SI base unit of length
kg
(kilogram) SI base unit of mass
s
(second) SI base unit of time
Hz
(hertz) SI unit of frequency
Pa
(pascal) SI unit of pressure or stress
Ω
(ohm) SI unit of electric resistance
L
(litre) 1 dm³
t
(tonne) 10³ kg
ha
(hectare) 1 hm²
Å
(ångström) 10⁻¹⁰ m
mL
(millilitre)
cm
(centimetre)
dB
(decibel) see remarks, below
kbit
(kilobit) 10³ or 1000 bits
Kibit
(kibibit) 2¹⁰ or 1024 bits
kB
(kilobyte) 10³ or 1000 bytes
KiB
(kibibyte) 2¹⁰ or 1024 bytes
MB
(megabyte) 10⁶ or 1 000 000 bytes
MiB
(mebibyte) 2²⁰ or 1 048 576 bytes
Note

If the measurement being represented is not expressed in a particular unit, but rather is a number of discrete items, the unit count should be used, or the unit attribute may be left unspecified.

Wherever appropriate, a recognized SI unit name should be used (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). The list above is indicative rather than exhaustive.

unitRefpoints to a unique identifier stored in the xml:id of a <unitDef> element that defines a unit of measure.
StatusOptional
Datatypeteidata.pointer
quantity(quantity) specifies the number of the specified units that comprise the measurement
StatusOptional
Datatypeteidata.numeric
commodity(commodity) indicates the substance that is being measured
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Note

In general, when the commodity is made of discrete entities, the plural form should be used, even when the measurement is of only one of them.

Schematron
<sch:rule context="tei:*[@unitRef]"> <sch:report role="info" test="@unit">The @unit attribute may be unnecessary when @unitRef is present.</sch:report> </sch:rule>
Note
This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system.
<l>So weren't you gonna buy <measure commodity="ice cream"   quantity="0.5unit="gal">half    a gallon</measure>, baby</l> <l>So won't you go and buy <measure commodity="ice cream"   quantity="1.893unit="L">half    a gallon</measure>, baby?</l>

The unit should normally be named using the standard symbol for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters.

3.32. att.media

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

3.33. 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
MembersrefState
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.34. 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 forename name objectName orgName placeName surname] author editor pubPlace
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.35. att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Moduletei
MemberslistAnnotation
Attributes
notationnames the notation used for the content of the element.
StatusOptional
Datatypeteidata.enumerated

3.36. att.patternReplacement

att.patternReplacement provides attributes for regular-expression matching and replacement. [17.2.3. Using Abbreviated Pointers 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
Moduleheader
MemberscRefPattern prefixDef
Attributes
matchPatternspecifies a regular expression against which the values of other attributes can be matched.
StatusRequired
Datatypeteidata.pattern
Note

The syntax used should follow that defined by W3C XPath syntax. Note that parenthesized groups are used not only for establishing order of precedence and atoms for quantification, but also for creating subpatterns to be referenced by the replacementPattern attribute.

replacementPatternspecifies a ‘replacement pattern’, that is, the skeleton of a relative or absolute URI containing references to groups in the matchPattern which, once subpattern substitution has been performed, complete the URI.
StatusRequired
Datatypeteidata.replacement
Note

The strings $1, $2 etc. are references to the corresponding group in the regular expression specified by matchPattern (counting open parenthesis, left to right). Processors are expected to replace them with whatever matched the corresponding group in the regular expression.

If a digit preceded by a dollar sign is needed in the actual replacement pattern (as opposed to being used as a back reference), the dollar sign must be written as %24.

3.37. 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 forename name objectName orgName placeName surname
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.38. 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[rt] div note noteGrp
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.39. 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] annotation calendar catRef citedRange licence note noteGrp ptr ref
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.40. att.pointing.group

att.pointing.group provides a set of attributes common to all elements which enclose groups of pointer elements. [17. Linking, Segmentation, and Alignment]
Moduletei
MemberslinkGrp
Attributes
domainsoptionally specifies the identifiers of the elements within which all elements indicated by the contents of this element lie.
StatusOptional
Datatype2–∞ occurrences of teidata.pointer separated by whitespace
Note

If this attribute is supplied every element specified as a target must be contained within the element or elements named by it. An application may choose whether or not to report failures to satisfy this constraint as errors, but may not access an element of the right identifier but in the wrong context. If this attribute is not supplied, then target elements may appear anywhere within the target document.

targFunc(target function) describes the function of each of the values of the target attribute of the enclosed <link>, <join>, or <alt> tags.
StatusOptional
Datatype2–∞ occurrences of teidata.word separated by whitespace
Note

The number of separate values must match the number of values in the target attribute in the enclosed <link>, <join>, or <alt> tags (an intermediate <ptr> element may be needed to accomplish this). It should also match the number of values in the domains attribute, of the current element, if one has been specified.

3.41. att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei
Membersatt.dimensions[date ellipsis]
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.42. att.resourced

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

3.43. att.scope

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

3.44. att.sortable

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

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

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

3.45. 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
Memberslb
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.46. att.styleDef

att.styleDef provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.
Moduletei
Membersrendition styleDefDecl
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.47. 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
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.48. att.transcriptional

att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [12.3.1.4. Additions and Deletions]
Moduletei
Membersrt
Attributes
statusindicates the effect of the intervention, for example in the case of a deletion, strikeouts which include too much or too little text, or in the case of an addition, an insertion which duplicates some of the text already present.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
duplicate
all of the text indicated as an addition duplicates some text that is in the original, whether the duplication is word-for-word or less exact.
duplicate-partial
part of the text indicated as an addition duplicates some text that is in the original
excessStart
some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
excessEnd
some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
shortStart
some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
shortEnd
some text at the end of the deletion is not marked as deleted even though it clearly should be.
partial
some text in the deletion is not marked as deleted even though it clearly should be.
unremarkable
the deletion is not faulty.[Default]
Note

Status information on each deletion is needed rather rarely except in critical editions from authorial manuscripts; status information on additions is even less common.

Marking a deletion or addition as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.

causedocuments the presumed cause for the intervention.
StatusOptional
Datatypeteidata.enumerated
seq(sequence) assigns a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred.
StatusOptional
Datatypeteidata.count

3.49. 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 application bibl biblStruct calendar change correspAction correspDesc date div divGen eventName forename gender graphic idno lb listAnnotation listBibl listChange listObject name note noteGrp object objectName orgName persPronouns placeName ptr rb ref relatedItem rt ruby schemaRef standOff surname text title titlePage unit unitDef xenoData
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.50. 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[rt] div hi note noteGrp 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
   )*

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
Element:
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.gender teidata.sexElement:
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
Element:
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.namespace

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

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

5.10. 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.11. 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.12. 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.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.prefix

teidata.prefix defines a range of values that may function as a URI scheme name.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[a-z][a-z0-9\+\.\-]*"/>
</content>
    
Declaration
teiteidata.prefix = token { pattern = "[a-z][a-z0-9\+\.\-]*" }
Note

This datatype is used to constrain a string of characters to one that can be used as a URI scheme name according to RFC 3986, section 3.1. Thus only the 26 lowercase letters a–z, the 10 digits 0–9, the plus sign, the period, and the hyphen are permitted, and the value must start with a letter.

5.15. teidata.probCert

teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.
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.16. 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.17. 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.18. teidata.sex

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

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

5.19. teidata.temporal.iso

teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
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.20. teidata.temporal.w3c

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

teidata.truthValue defines the range of attribute values used to express a truth value.
Moduletei
Used by
Element:
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.23. teidata.version

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

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

5.24. teidata.versionNumber

teidata.versionNumber defines the range of attribute values used for version numbers.
Moduletei
Used by
Element:
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.25. teidata.word

teidata.word defines the range of attribute values expressed as a single word or token.
Moduletei
Used by
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.26. 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.27. teidata.xmlName

teidata.xmlName defines attribute values which contain an XML name.
Moduletei
Used by
Element:
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.28. teidata.xpath

teidata.xpath defines attribute values which contain an XPath expression.
Moduletei
Used by
Element:
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