KGK-minimalgenerated by Roma 5.0.1.

Author: generated by Roma 5.0.12026-04-28

[#note-constraints]
<constraint>
<sch:rule context="tei:note[@place='margin']">
 <sch:assert test="parent::tei:p"> Margin notes must appear within paragraphs
 </sch:assert>
</sch:rule>

<!-- TODO: to remove if back is fixed -->
<sch:rule context="tei:note[parent::tei:div[@type='crit_app'] or parent::tei:div[@type='footnotes']]">
 <sch:assert test="@xml:id and @n and @ref"> Notes within critical apparatus
   or footnotes divisions must have xml:id, n, and ref attributes
 </sch:assert>
</sch:rule>
</constraint>
[#change-target-integrity]
<constraint>
<sch:rule context="tei:change[@target]">
 <sch:assert test="every $tok in tokenize(normalize-space(@target), '\s+') satisfies (starts-with($tok, '#') and exists(//*[@xml:id = substring($tok, 2)]))">Every token in @target on tei:change must be a fragment identifier
   (starting with '#') that resolves to an element with a matching @xml:id
   in the same document.
 </sch:assert>
</sch:rule>
</constraint>

My TEI Customization starts with modules tei, core, textstructure and header

Schema kgk-minimal: Elements

<additional>

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

<additions>

<additions> (additions) contains a description of any significant additions found within a manuscript or other object, such as marginalia or other annotations. [11.7.2. Writing, Decoration, and Other Notations]
Module msdescription
Member of
model.physDescPart
Contained by
msdescription: physDesc
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig p pb ptr quote ref rs sic sp term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Example
<additions>
 <p>There are several marginalia in this manuscript. Some consist of
   single characters and others are figurative. On 8v is to be found a drawing of
   a mans head wearing a hat. At times sentences occurs: On 5v:
 <q xml:lang="is">Her er skrif andres isslendin</q>,
   on 19r: <q xml:lang="is">þeim go</q>,
   on 21r: <q xml:lang="is">amen med aund ok munn halla rei knar hofud summu all huad
     batar þad mælgi ok mal</q>,
   On 21v: some runic letters and the sentence <q xml:lang="la">aue maria gracia plena dominus</q>.</p>
</additions>
Content model 
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration 
element additions { tei_macro.specialPara }

<altIdentifier>

<altIdentifier> (alternative identifier) contains an alternative or former structured identifier used for a manuscript or other object, such as a former catalogue number. [11.4. The Manuscript Identifier]
Module msdescription
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
siglum
Contained by
msdescription: msIdentifier
May contain
core: note
header: idno
msdescription: repository
namesdates: placeName
Note

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

Example
<altIdentifier>
 <settlement>San Marino</settlement>
 <repository>Huntington Library</repository>
 <idno>MS.El.26.C.9</idno>
</altIdentifier>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef expand="sequenceOptional"
   key="model.placeNamePart"/>
  <elementRef key="institution"
   minOccurs="0"/>
  <elementRef key="repository"
   minOccurs="0"/>
  <elementRef key="collection"
   minOccurs="0"/>
  <elementRef key="idno"/>
  <elementRef key="note" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration 
element altIdentifier
{
   tei_att.datable.attributes,
   attribute type { "siglum" }?,
   (
      tei_placeName?,
      institution?,
      tei_repository?,
      collection?,
      tei_idno,
      tei_note?
   )
}

<analytic>

<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
Module core
Contained by
core: biblStruct
May contain
core: author date editor ptr ref respStmt textLang title
header: availability idno
Note

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

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

<anchor>

<anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 17.5. Correspondence and Alignment]
Module linking
Attributes
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Optional
Datatype teidata.text
corresp (corresponds) points to elements that correspond to the current element in some way.
Derived from att.global.linking
Status Optional
Datatype string
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
crit
footnote
wdb
ref
Status Optional
Datatype string
place
Status Optional
Datatype string
Legal values are:
start
end
Member of
model.milestoneLike
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi imprint item l label lg list listBibl note orig p pubPlace publisher quote ref rs sic sp speaker term textLang title unclear
figures: cell table
header: change distributor extent handNote
linking: seg
msdescription: additions msItem repository
namesdates: eventName gender persName placeName
textstructure: back body closer div opener salute text
transcr: supplied
May contain Empty element
Note

On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence.
Example
<s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s>
<s>Help me find it.<ptr target="#A234"/>
</s>
Content model 
<content>
 <empty/>
</content>
Schema Declaration 
element anchor
{
   tei_att.global.attribute.xmlid,
   tei_att.global.change.attribute.change,
   tei_att.cmc.attributes,
   attribute n { teidata.text }?,
   attribute corresp { string }?,
   attribute type { "crit" | "footnote" | "wdb" },
   attribute ref { string }?,
   attribute place { "start" | "end" }?,
   empty
}

<author>

<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Module core
Attributes
Member of
model.respLike
Contained by
core: analytic bibl biblStruct monogr
header: titleStmt
msdescription: msItem
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Note

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

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

Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.
Example
<author>British Broadcasting Corporation</author>
<author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
<author>Anonymous</author>
<author>Bill and Melinda Gates Foundation</author>
<author>
 <persName>Beaumont, Francis</persName>
and
<persName>John Fletcher</persName>
</author>
<author>
 <orgName key="BBC">British Broadcasting
   Corporation</orgName>: Radio 3 Network
</author>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <macroRef key="macro.phraseSeq"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="unclear"/>
   <elementRef key="choice"/>
   <elementRef key="supplied"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element author
{
   tei_att.datable.attributes,
   tei_att.canonical.attribute.ref,
   ( tei_macro.phraseSeq, ( tei_unclear | tei_choice | tei_supplied )* )
}

<availability>

<availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Module header
Attributes
status (status) supplies a code identifying the current availability of the text.
Status Required
Datatype teidata.enumerated
Legal values are:
free
restricted
Member of
model.publicationStmtPart.detail
Contained by
core: analytic monogr
header: publicationStmt
May contain
core: p
Note

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

<sch:pattern is-a="declarable">
<sch:param name="tde"
 value="tei:availability"/>
</sch:pattern>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
Schema Declaration 
element availability
{
   attribute status { "free" | "restricted" },
   ( tei_model.availabilityPart | tei_model.pLike )+
}

<back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Module textstructure
Contained by
textstructure: text
May contain
core: cb gap lb list listBibl note noteGrp p pb
figures: table
linking: anchor
textcrit: listWit
textstructure: closer div
Note

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

<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]
Module core
Member of
model.biblLike
Contained by
core: biblStruct corr head hi item l listBibl note orig p quote ref sic textLang title unclear
figures: cell
header: change handNote sourceDesc
linking: seg
msdescription: additions msItem
textcrit: witness
textstructure: body div salute
transcr: supplied
May contain
core: author biblScope date note pubPlace publisher
namesdates: placeName
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_chapter" type="article"
 xml:id="carlin_2003">
 <author>
  <name>
   <surname>Carlin</surname>
     (<forename>Claire</forename>)</name>
 </author>,
<title level="a">The Staging of Impotence : France’s last
   congrès</title> dans
<bibl type="monogr">
  <title level="m">Theatrum mundi : studies in honor of Ronald W.
     Tobin</title>, éd.
 <editor>
   <name>
    <forename>Claire</forename>
    <surname>Carlin</surname>
   </name>
  </editor> et
 <editor>
   <name>
    <forename>Kathleen</forename>
    <surname>Wine</surname>
   </name>
  </editor>,
 <pubPlace>Charlottesville, Va.</pubPlace>,
 <publisher>Rookwood Press</publisher>,
 <date when="2003">2003</date>.
 </bibl>
</bibl>
Schematron

<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:bibl"/>
</sch:pattern>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="author"/>
  <elementRef key="date"/>
  <elementRef key="placeName"/>
  <elementRef key="note"/>
  <elementRef key="publisher"/>
  <elementRef key="pubPlace"/>
  <elementRef key="biblScope"/>
 </alternate>
</content>
Schema Declaration 
element bibl
{
   (
      tei_author
    | tei_date
    | tei_placeName
    | tei_note
    | tei_publisher
    | tei_pubPlace
    | tei_biblScope
   )*
}

<biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Module core
Member of
model.imprintPart
Contained by
core: bibl imprint monogr
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Note

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

It is now considered good practice to supply this element as a sibling (rather than a child) of imprint, since it supplies information which does not constitute part of the imprint.
Example
<biblScope>pp 12–34</biblScope>
<biblScope from="12" to="34" unit="page"/>
<biblScope unit="volume">II</biblScope>
<biblScope unit="page">12</biblScope>
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration 
element biblScope { tei_macro.phraseSeq }

<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]
Module core
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
imprint
Member of
model.biblLike
Contained by
core: biblStruct corr head hi item l listBibl note orig p quote ref sic textLang title unclear
figures: cell
header: change handNote sourceDesc
linking: seg
msdescription: additions msItem
textcrit: witness
textstructure: body div salute
transcr: supplied
May contain
core: analytic author bibl biblStruct editor head listBibl monogr note noteGrp ptr quote ref respStmt textLang title
header: idno
msdescription: msDesc msItem
Example
<biblStruct>
 <monogr>
  <author>Blain, Virginia</author>
  <author>Clements, Patricia</author>
  <author>Grundy, Isobel</author>
  <title>The Feminist Companion to Literature in English: women writers from the middle ages
     to the present</title>
  <edition>first edition</edition>
  <imprint>
   <publisher>Yale University Press</publisher>
   <pubPlace>New Haven and London</pubPlace>
   <date>1990</date>
  </imprint>
 </monogr>
</biblStruct>
Example
<biblStruct type="newspaper">
 <analytic>
  <author>
   <forename>David</forename>
   <surname>Barstow</surname>
  </author>
  <author>
   <forename>Susanne</forename>
   <surname>Craig</surname>
  </author>
  <author>
   <forename>Russ</forename>
   <surname>Buettner</surname>
  </author>
  <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>
  <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>
 </analytic>
 <monogr>
  <title level="j">The New York Times</title>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>A. G. Sulzberger</publisher>
   <date when="2018-10-03">Wednesday, October 3, 2018</date>
  </imprint>
  <biblScope unit="volume">CLXVIII</biblScope>
  <biblScope unit="issue">58,104</biblScope>
  <biblScope unit="page">1</biblScope>
 </monogr>
</biblStruct>
Schematron

<sch:pattern is-a="declarable">
<sch:param name="tde"
 value="tei:biblStruct"/>
</sch:pattern>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="analytic"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="monogr"/>
   <elementRef key="series"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.headLike"/>
   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
   <classRef key="model.msItemPart"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element biblStruct
{
   tei_att.global.attribute.xmlid,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   attribute type { "imprint" }?,
   (
      tei_analytic*,
      ( ( tei_monogr, series* )+ ),
      (
         tei_model.headLike
       | tei_model.noteLike
       | tei_model.ptrLike
       | relatedItem
       | citedRange
       | tei_model.msItemPart
      )*
   )
}

<body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Module textstructure
Contained by
textstructure: text
May contain
core: bibl biblStruct cb gap head l label lb lg list listBibl note noteGrp p pb quote sp
figures: table
linking: anchor
msdescription: msDesc
textcrit: listWit
textstructure: closer div opener salute
Example
<body>
 <l>Nu scylun hergan hefaenricaes uard</l>
 <l>metudæs maecti end his modgidanc</l>
 <l>uerc uuldurfadur sue he uundra gihuaes</l>
 <l>eci dryctin or astelidæ</l>
 <l>he aerist scop aelda barnum</l>
 <l>heben til hrofe haleg scepen.</l>
 <l>tha middungeard moncynnæs uard</l>
 <l>eci dryctin æfter tiadæ</l>
 <l>firum foldu frea allmectig</l>
 <trailer>primo cantauit Cædmon istud carmen.</trailer>
</body>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="1" minOccurs="0">
   <classRef key="model.divTop"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence maxOccurs="1" minOccurs="0">
   <classRef key="model.divGenLike"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate maxOccurs="1" minOccurs="1">
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.divLike"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.div1Like"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <alternate maxOccurs="1" minOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
    <alternate maxOccurs="1" minOccurs="0">
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <classRef key="model.divLike"/>
      <alternate maxOccurs="unbounded"
       minOccurs="0">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <classRef key="model.div1Like"/>
      <alternate maxOccurs="unbounded"
       minOccurs="0">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration 
element body
{
   tei_model.global*,
   ( ( tei_model.divTop, ( tei_model.global | tei_model.divTop )* )? ),
   ( ( tei_model.divGenLike, ( tei_model.global | tei_model.divGenLike )* )? ),
   (
      ( ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+ )
    | ( ( tei_model.div1Like, ( tei_model.global | tei_model.divGenLike )* )+ )
    | (
         ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+ ),
         (
            (
               (
                  tei_model.divLike,
                  ( tei_model.global | tei_model.divGenLike )*
               )+
            )
          | (
               (
                  tei_model.div1Like,
                  ( tei_model.global | tei_model.divGenLike )*
               )+
            )
         )?
      )
   ),
   ( ( tei_model.divBottom, tei_model.global* )* )
}

<cb>

<cb> (column beginning) marks the beginning of a new column of a text on a multi-column page. [3.11.3. Milestone Elements]
Module core
Attributes
Member of
model.milestoneLike
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi imprint item l label lg list listBibl note orig p pubPlace publisher quote ref rs sic sp speaker term textLang title unclear
figures: cell table
header: change distributor extent handNote
linking: seg
msdescription: additions msItem repository
namesdates: eventName gender persName placeName
textstructure: back body closer div opener salute text
transcr: supplied
May contain Empty element
Note

On this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this cb element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column beginnings relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The cb element is placed at the head of the column to which it refers.
Example

Markup of an early English dictionary printed in two columns:

<pb/>
<cb n="1"/>
<entryFree>
 <form>Well</form>, <sense>a Pit to hold Spring-Water</sense>:
<sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner
   sinks into the Ground, to find out and disappoint the Enemies Mines,
   or to prepare one</sense>.
</entryFree>
<entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or
<sense>lie groveling</sense>.</entryFree>
<!-- remainder of column -->
<cb n="2"/>
<entryFree>
 <form>Wey</form>, <sense>the greatest Measure for dry Things,
   containing five Chaldron</sense>.
</entryFree>
<entryFree>
 <form>Whale</form>, <sense>the greatest of
   Sea-Fishes</sense>.
</entryFree>
Content model 
<content>
 <empty/>
</content>
Schema Declaration 
element cb
{
   tei_att.global.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   tei_att.typed.attributes,
   empty
}

<cell>

<cell> (cell) contains one cell of a table. [15.1.1. TEI Tables]
Module figures
Attributes
Contained by
figures: row
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig p pb ptr quote ref rs sic sp term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Example
<row>
 <cell role="label">General conduct</cell>
 <cell role="data">Not satisfactory, on account of his great unpunctuality
   and inattention to duties</cell>
</row>
Content model 
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration 
element cell
{
   tei_att.global.attribute.xmlid,
   tei_att.tableDecoration.attribute.rows,
   tei_att.tableDecoration.attribute.cols,
   tei_macro.specialPara
}

<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]
Module header
Attributes
target (target) points to one or more elements that belong to this change.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
header: listChange revisionDesc
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig p pb ptr quote ref rs sic sp term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
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="public" when="2008-02-02"
  who="#BZ">Finished chapter 23</change>
 <change status="draft" when="2008-01-02"
  who="#BZ">Finished chapter 2</change>
 <change n="P2.2" when="1991-12-21"
  who="#LDB">Added examples to section 3</change>
 <change when="1991-11-11" who="#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
{
   tei_att.global.attributes,
   tei_att.ascribed.attributes,
   tei_att.datable.attributes,
   tei_att.docStatus.attributes,
   tei_att.typed.attributes,
   attribute target { list { teidata.pointer+ } }?,
   tei_macro.specialPara
}

<choice>

<choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
Module core
Attributes
type
Status Optional
Datatype string
Legal values are:
corr
Member of
model.pPart.editorial
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi item l label note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
core: corr sic unclear
transcr: supplied
Note

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

Note also that choice elements may self-nest.

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

An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.

<p>Lastly, That, upon his solemn oath to observe all the above
articles, the said man-mountain shall have a daily allowance of
meat and drink sufficient for the support of <choice>
  <sic>1724</sic>
  <corr>1728</corr>
 </choice> of our subjects,
with free access to our royal person, and other marks of our
<choice>
  <orig>favour</orig>
  <reg>favor</reg>
 </choice>.</p>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="1">
  <elementRef key="unclear"/>
  <elementRef key="supplied"/>
  <elementRef key="corr"/>
  <elementRef key="sic"/>
 </alternate>
</content>
Schema Declaration 
element choice
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   attribute type { "corr" }?,
   ( tei_unclear | tei_supplied | tei_corr | tei_sic )+
}

<closer>

<closer> (closer) groups together salutations, datelines, bylines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions]
Module textstructure
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
right-align-right
right-align-left
left-align-right
left-align-left
center-align-left
center-align-right
center
inline
hanging
Member of
model.divBottomPart
Contained by
core: lg list
figures: table
textstructure: back body div
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
textstructure: salute
transcr: ex supplied
character data
Example
<div type="letter">
 <p> perhaps you will favour me with a sight of it when convenient.</p>
 <closer>
  <salute>I remain, &amp;c. &amp;c.</salute>
  <signed>H. Colburn</signed>
 </closer>
</div>
Example
<div type="chapter">
 <p>
<!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>
 <closer>
  <dateline>
   <name type="place">Trieste-Zürich-Paris,</name>
   <date>1914–1921</date>
  </dateline>
 </closer>
</div>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="byline"/>
  <elementRef key="signed"/>
  <elementRef key="dateline"/>
  <elementRef key="salute"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration 
element closer
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   attribute rend
   {
      list
      {
         (
            "right-align-right"
          | "right-align-left"
          | "left-align-right"
          | "left-align-left"
          | "center-align-left"
          | "center-align-right"
          | "center"
          | "inline"
          | "hanging"
         )+
      }
   }?,
   (
      text
    | tei_model.gLike
    | byline
    | signed
    | dateline
    | tei_salute
    | tei_model.phrase
    | tei_model.global
   )*
}

<corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
Module core
Attributes
Member of
model.pPart.transcriptional
Contained by
analysis: w
core: author biblScope choice corr date editor foreign head hi item l label lg note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions
namesdates: eventName gender persName placeName
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Example

If all that is desired is to call attention to the fact that the copy text has been corrected, corr may be used alone:

I don't know,
Juan. It's so far in the past now — how <corr>can we</corr> prove
or disprove anyone's theories?
Example

It is also possible, using the choice and sic elements, to provide an uncorrected reading:

I don't know, Juan. It's so far in the past now —
how <choice>
 <sic>we can</sic>
 <corr>can we</corr>
</choice> prove or
disprove anyone's theories?
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration 
element corr
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   tei_macro.paraContent
}

<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]
Module core
Attributes
cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
Derived from att.global.responsibility
Status Optional
Datatype teidata.probCert
Legal values are:
low
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
created
Member of
model.dateLike model.publicationStmtPart.detail
Contained by
core: analytic author bibl biblScope corr date editor event foreign head hi imprint item l label note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote publicationStmt
linking: seg
msdescription: additions repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day
of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic
the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <macroRef key="macro.phraseSeq"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="unclear"/>
   <elementRef key="choice"/>
   <elementRef key="supplied"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element date
{
   tei_att.cmc.attributes,
   tei_att.datable.w3c.attribute.when,
   tei_att.datable.w3c.attribute.notBefore,
   tei_att.datable.w3c.attribute.notAfter,
   attribute cert { "low" }?,
   attribute type { "created" }?,
   ( tei_macro.phraseSeq, ( tei_unclear | tei_choice | tei_supplied )* )
}

<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.]
Module header
Member of
model.imprintPart model.publicationStmtPart.agency
Contained by
core: imprint
header: publicationStmt
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Example
<distributor>Oxford Text Archive</distributor>
<distributor>Redwood and Burn Ltd</distributor>
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration 
element distributor { tei_macro.phraseSeq }

<div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Module textstructure
Attributes
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype teidata.language
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
contents
corrigenda
titlepage
reference
history_of_the_work
evidence
transcript
supplement
crit_app
footnotes
main
introduction
introduction_codex_lost
register
front
Member of
model.divLike
Contained by
textstructure: back body div
May contain
core: bibl biblStruct cb gap head l label lb lg list listBibl note noteGrp p pb quote sp
figures: table
linking: anchor
msdescription: msDesc
textcrit: listWit
textstructure: closer div opener salute
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="1" type="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.1" type="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.2" type="section">
    <head>Appeal to Authority, in What Cases Fallacious.</head>
    <p>Reference to authority is open to the charge of fallacy when [...] </p>
   </div>
  </div>
 </div>
</body>
Schematron

<sch:rule context="tei:l//tei:div">
<sch:assert test="ancestor::tei:floatingText"> Abstract model violation: Metrical lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:assert>
</sch:rule>
Schematron

<sch:rule context="tei:div">
<sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText.
</sch:report>
</sch:rule>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence maxOccurs="1" minOccurs="0">
   <alternate maxOccurs="1" minOccurs="1">
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <alternate maxOccurs="1" minOccurs="1">
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
    <sequence maxOccurs="1" minOccurs="1">
     <sequence maxOccurs="unbounded"
      minOccurs="1">
      <alternate maxOccurs="1"
       minOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       maxOccurs="unbounded" minOccurs="0"/>
     </sequence>
     <sequence maxOccurs="unbounded"
      minOccurs="0">
      <alternate maxOccurs="1"
       minOccurs="1">
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       maxOccurs="unbounded" minOccurs="0"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence maxOccurs="unbounded"
    minOccurs="0">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
  </sequence>
 </sequence>
</content>
Schema Declaration 
element div
{
   tei_att.global.attribute.xmlid,
   tei_att.global.linking.attribute.corresp,
   tei_att.placement.attributes,
   attribute xml:lang { teidata.language }?,
   attribute type
   {
      "contents"
    | "corrigenda"
    | "titlepage"
    | "reference"
    | "history_of_the_work"
    | "evidence"
    | "transcript"
    | "supplement"
    | "crit_app"
    | "footnotes"
    | "main"
    | "introduction"
    | "introduction_codex_lost"
    | "register"
    | "front"
   },
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.divLike | tei_model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  ( ( ( schemaSpec | tei_model.common ), tei_model.global* )+ ),
                  (
                     (
                        ( tei_model.divLike | tei_model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

<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]
Module core
Attributes
Member of
model.respLike
Contained by
core: analytic biblStruct monogr
header: titleStmt
msdescription: msItem
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
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 { tei_att.datable.attributes, tei_macro.phraseSeq }

<encodingDesc>

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

<event>

<event>
Module core
Attributes
type
Status Required
Datatype token
primary
Status Optional
Datatype boolean
Contained by
core: listEvent
May contain
core: date
namesdates: placeName
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="placeName"/>
  <elementRef key="date"/>
 </sequence>
</content>
Schema Declaration 
element event
{
   attribute type { token },
   attribute primary { boolean }?,
   ( tei_placeName, tei_date )
}

<eventName>

<eventName> (name of an event) contains a proper noun or noun phrase used to refer to an event. [14.2.4. Event Names]
Module namesdates
Attributes
Member of
model.nameLike
Contained by
core: author biblScope corr date editor foreign head hi item l label listBibl note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Example
<listEvent>
 <event from="1939-09-01" to="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-01" to="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-22" to="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="#ThirtyYearsWar" type="event">long war</rs>.</p>
Example
<event from="2019-09-16" to="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_of" passive="#AnnualTEIConference"
   ref="https://www.wikidata.org/wiki/Property:P31" type="CRM"/>
 </listRelation>
</event>
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration 
element eventName
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

<ex>

<ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. [12.3.1.2. Abbreviation and Expansion]
Module transcr
Member of
model.pPart.editorial
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi item l label note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain Character data only
Example
The address is Southmoor <choice>
 <expan>R<ex>oa</ex>d</expan>
 <abbr>Rd</abbr>
</choice>
Content model 
<content>
 <macroRef key="macro.xtext"/>
</content>
Schema Declaration 
element ex { tei_macro.xtext }

<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]
Module header
Contained by
core: monogr
header: fileDesc
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Example
<extent>3200 sentences</extent>
<extent>between 10 and 20 Mb</extent>
<extent>ten 3.5 inch high density diskettes</extent>
Example

The <measure> element may be used to supply normalized or machine tractable versions of the size or sizes concerned.

<extent>
 <measure quantity="4.2" unit="MiB">About four megabytes</measure>
 <measure quantity="245" unit="pages">245 pages of source
   material</measure>
</extent>
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration 
element extent { tei_macro.phraseSeq }

<fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Module header
Contained by
header: teiHeader
May contain
header: extent publicationStmt sourceDesc titleStmt
Note

The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.
Example
<fileDesc>
 <titleStmt>
  <title>The shortest possible TEI document</title>
 </titleStmt>
 <publicationStmt>
  <p>Distributed as part of TEI P5</p>
 </publicationStmt>
 <sourceDesc>
  <p>No print source exists: this is an original digital text</p>
 </sourceDesc>
</fileDesc>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <sequence maxOccurs="1" minOccurs="1">
   <elementRef key="titleStmt"/>
   <elementRef key="editionStmt"
    minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="publicationStmt"/>
   <elementRef key="seriesStmt"
    maxOccurs="unbounded" minOccurs="0"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   maxOccurs="unbounded" minOccurs="1"/>
 </sequence>
</content>
Schema Declaration 
element fileDesc
{
   (
      tei_titleStmt,
      editionStmt?,
      tei_extent?,
      tei_publicationStmt,
      seriesStmt*,
      notesStmt?
   ),
   tei_sourceDesc+
}

<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]
Module core
Attributes
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Required
Datatype teidata.language
Legal values are:
grc-Grek
grc-Latn
heb-Hebr
heb-Latn
de-Latn
lat
Member of
model.emphLike
Contained by
core: author biblScope corr date editor foreign head hi item l label note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Note

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

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

The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.
Example
This is
heathen Greek to you still? Your <foreign xml:lang="la">lapis
philosophicus</foreign>?
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration 
element foreign
{
   tei_att.cmc.attributes,
   attribute xml:lang
   {
      "grc-Grek" | "grc-Latn" | "heb-Hebr" | "heb-Latn" | "de-Latn" | "lat"
   },
   tei_macro.phraseSeq
}

<gap>

<gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions]
Module core
Attributes
reason (reason) gives the reason for omission.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
illegible
Member of
model.global.edit
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi imprint item l label lg list note orig p pubPlace publisher quote ref rs sic sp speaker term textLang title unclear
figures: cell table
header: change distributor extent handNote
linking: seg
msdescription: additions msItem repository
namesdates: eventName gender persName placeName
textstructure: back body closer div opener salute text
transcr: supplied
May contain Empty element
Note

The gap, unclear, and <del> core tag elements may be closely allied in use with the <damage> and supplied elements, available when using the additional tagset for transcription of primary sources. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

The gap tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion.
Example
<gap quantity="4" reason="illegible"
 unit="chars"/>
Example
<gap quantity="1" reason="sampling"
 unit="essay"/>
Example
<del>
 <gap atLeast="4" atMost="8"
  reason="illegible" unit="chars"/>
</del>
Example
<gap extent="several lines" reason="lost"/>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
Schema Declaration 
element gap
{
   tei_att.cmc.attributes,
   attribute reason { list { "illegible"+ } }?,
   ( tei_model.descLike | tei_model.certLike )*
}

<gender>

<gender> (gender) specifies the gender identity of a person, persona, or character. [14.3.2.1. Personal Characteristics]
Module namesdates
Attributes
value supplies a coded value for gender identity.
Status Optional
Datatype 1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be locally defined by a project, or they may refer to an external standard.
Contained by
—
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
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
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   attribute value { list { teidata.gender+ } }?,
   tei_macro.phraseSeq
}

<handDesc>

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

<handNote>

<handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [11.7.2. Writing, Decoration, and Other Notations]
Module header
Contained by
msdescription: handDesc
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig p pb ptr quote ref rs sic sp term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Example
<handNotes>
 <handNote medium="brown_ink" scope="major"
  scribe="author" scribeRef="#KL" xml:id="yien.major_hand">Handwriting of the copyist Karol Libelt, brown ink, in German cursive script.</handNote>
 <handNote medium="pencil" scope="minor"
  scribe="annotator" xml:id="yien.pencil">A note, pencil, unknown author.</handNote>
 <handNote medium="pencil" scope="minor"
  scribe="archivist" xml:id="yien.pencil2">Writer of the title page Józef Łepkowski, pencil.</handNote>
 <handNote medium="pencil" scope="minor"
  scribe="archivist2" scribeRef="#BJK" xml:id="yien.pencil3">Note on the title page, pencil, by Józef Korzeniowski.</handNote>
</handNotes>
Content model 
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration 
element handNote { tei_macro.specialPara }
<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Module core
Attributes
level heading level
Status Required
Datatype data.enumerated
Legal values are:
1
2
3
Member of
model.divTopPart model.headLike
Contained by
core: biblStruct lg list listBibl
figures: table
header: listChange
msdescription: msDesc
textcrit: listWit
textstructure: body div
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Note

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

The most common use for the head element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:

<div1 n="I" type="book">
 <head>In the name of Christ here begins the first book of the ecclesiastical history of
   Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
 <div2 type="section">
  <head>In the name of Christ here begins Book I of the history.</head>
  <p>Proposing as I do ...</p>
  <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve
     years passed.</p>
  <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six
     years from the beginning of the world down to the death of Saint Martin.</trailer>
 </div2>
</div1>
Example

When headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.

<div type="subsection">
 <head place="margin">Secunda conclusio</head>
 <p>
  <lb n="1251"/>
  <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>
  </hi>
  <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium
   [...]
 </p>
</div>
Example

The head element is also used to mark headings of other units, such as lists:

With a few exceptions, connectives are equally
useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">
 <head>Connectives</head>
 <item>above</item>
 <item>accordingly</item>
 <item>across from</item>
 <item>adjacent to</item>
 <item>again</item>
 <item>
<!-- ... -->
 </item>
</list>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration 
element head
{
   attribute level { "1" | "2" | "3" },
   (
      text
    | tei_lg
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.lLike
    | tei_model.global
   )*
}

<hi>

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Module core
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
super
sub
Member of
model.hiLike
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi item l label note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions locus repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Example
<hi rend="gothic">And this Indenture further witnesseth</hi>
that the said <hi rend="italic">Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration 
element hi
{
   tei_att.cmc.attributes,
   attribute rend { list { ( "super" | "sub" )+ } }?,
   tei_macro.paraContent
}

<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]
Module header
Attributes
type categorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
vd16
vd17
siglum
signatur
Member of
model.msItemPart model.nameLike model.publicationStmtPart.detail
Contained by
core: analytic author biblScope biblStruct corr date editor foreign head hi item l label listBibl monogr note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote idno publicationStmt
linking: seg
msdescription: additions altIdentifier msIdentifier msItem repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
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
{
   tei_att.cmc.attributes,
   attribute type { "vd16" | "vd17" | "siglum" | "signatur" },
   ( text | tei_model.gLike | tei_idno )*
}

<imprint>

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

<item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Module core
Attributes
  • att.global
    • n
    • xml:lang
    • xml:base
    • xml:space
    • @xml:id
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Optional
Datatype teidata.text
Sample values include:
editionsvorlage
Contained by
core: list
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig p pb ptr quote ref rs sic sp term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Note

May contain simple prose or a sequence of chunks.

Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the item element is by definition synonymous with the use of the label element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the label element, not n.
Example
<list rend="numbered">
 <head>Here begin the chapter headings of Book IV</head>
 <item n="4.1">The death of Queen Clotild.</item>
 <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
 <item n="4.3">The wives and children of Lothar.</item>
 <item n="4.4">The Counts of the Bretons.</item>
 <item n="4.5">Saint Gall the Bishop.</item>
 <item n="4.6">The priest Cato.</item>
 <item> ...</item>
</list>
Content model 
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration 
element item
{
   tei_att.global.attribute.xmlid,
   attribute n { teidata.text }?,
   tei_macro.specialPara
}

<keywords>

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

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

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

<l>

<l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.6. Speech Contents]
Module core
Attributes
Member of
model.lLike
Contained by
core: corr head hi item lg note orig p quote ref sic sp textLang title unclear
figures: cell
header: change handNote
linking: seg
msdescription: additions
textstructure: body div salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi label lb list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Example
<l met="x/x/x/x/x/" real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l>
Schematron

<sch:rule context="tei:l">
<sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]">Abstract model violation: Lines may not contain lines or lg elements.</sch:report>
</sch:rule>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration 
element l
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.global
   )*
}

<label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Module core
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
post
Member of
model.labelLike
Contained by
core: corr head hi item l lg list note orig p quote ref sic textLang title unclear
figures: cell
header: change handNote
linking: seg
msdescription: additions
textcrit: witness
textstructure: body div salute
transcr: supplied
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Example

Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:

<list type="gloss" xml:lang="enm">
 <head xml:lang="en">Vocabulary</head>
 <headLabel xml:lang="en">Middle English</headLabel>
 <headItem xml:lang="en">New English</headItem>
 <label>nu</label>
 <item xml:lang="en">now</item>
 <label>lhude</label>
 <item xml:lang="en">loudly</item>
 <label>bloweth</label>
 <item xml:lang="en">blooms</item>
 <label>med</label>
 <item xml:lang="en">meadow</item>
 <label>wude</label>
 <item xml:lang="en">wood</item>
 <label>awe</label>
 <item xml:lang="en">ewe</item>
 <label>lhouth</label>
 <item xml:lang="en">lows</item>
 <label>sterteth</label>
 <item xml:lang="en">bounds, frisks (cf. <cit>
   <ref>Chaucer, K.T.644</ref>
   <quote>a courser, <term>sterting</term>as the fyr</quote>
  </cit>
 </item>
 <label>verteth</label>
 <item xml:lang="la">pedit</item>
 <label>murie</label>
 <item xml:lang="en">merrily</item>
 <label>swik</label>
 <item xml:lang="en">cease</item>
 <label>naver</label>
 <item xml:lang="en">never</item>
</list>
Example

Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the label element is synonymous with the n attribute on the item element:

I will add two facts, which have seldom occurred
in the composition of six, or at least of five quartos. <list rend="runon numbered">
 <label>(1)</label>
 <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>
 <label>(2) </label>
 <item>Not a sheet has been seen by any human eyes, excepting those of the author and the
   printer: the faults and the merits are exclusively my own.</item>
</list>
Example

Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:

<list type="gloss">
 <label>March 1757.</label>
 <item>I wrote some critical observations upon Plautus.</item>
 <label>March 8th.</label>
 <item>I wrote a long dissertation upon some lines of Virgil.</item>
 <label>June.</label>
 <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus
     amori.</quote>
 </item>
 <label>August.</label>
 <item>I went to Crassy, and staid two days.</item>
</list>

Note that the label might also appear within the item rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.
Example

Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the label element appears within the p or lg element, rather than as a preceding sibling of it.

<p>[...]
<lb/>&amp; n’entrer en mauuais &amp; mal-heu-
<lb/>ré meſnage. Or des que le conſente-
<lb/>ment des parties y eſt le mariage eſt
<lb/> arreſté, quoy que de faict il ne ſoit
<label place="margin">Puiſſance maritale
   entre les Romains.</label>
 <lb/> conſommé. Depuis la conſomma-
<lb/>tion du mariage la femme eſt ſoubs
<lb/> la puiſſance du mary, s’il n’eſt eſcla-
<lb/>ue ou enfant de famille : car en ce
<lb/> cas, la femme, qui a eſpouſé vn en-
<lb/>fant de famille, eſt ſous la puiſſance
[...]</p>

In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it.

If so desired the type attribute may be used to distinguish different categories of label.
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration 
element label
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   attribute rend { list { "post"+ } }?,
   tei_macro.phraseSeq
}

<lb>

<lb> (line beginning) marks the beginning of a topographic line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.6. Speech Contents]
Module core
Attributes
break indicates 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.
Derived from att.breaking
Status Recommended
Datatype teidata.enumerated
Legal values are:
no
Member of
model.milestoneLike
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi imprint item l label lg list listBibl note orig p pubPlace publisher quote ref rs sic sp speaker term textLang title unclear
figures: cell table
header: change distributor extent handNote
linking: seg
msdescription: additions msItem repository
namesdates: eventName gender persName placeName
textstructure: back body closer div opener salute text
transcr: supplied
May contain Empty element
Note

By convention, lb elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next lb element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking 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.
Example

This 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>
Example

This example shows the encoding of the beginning of a new topographical line as a means of preserving the visual appearance of a title page. The break attribute is used to show that the beginning of the new line does not (as elsewhere) mark the start of a new word.

<titlePart>
 <lb/>With Additions, ne-<lb break="no"/>ver before Printed.
</titlePart>
Content model 
<content>
 <empty/>
</content>
Schema Declaration 
element lb
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   attribute break { "no" }?,
   empty
}

<lg>

<lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.6. Speech Contents]
Module core
Attributes
Member of
model.divPart model.paraPart
Contained by
core: corr head hi item lg note orig p quote ref sic sp textLang title unclear
figures: cell
header: change handNote
linking: seg
msdescription: additions
textstructure: body div salute
transcr: supplied
May contain
core: cb corr gap head l label lb lg note noteGrp orig pb sic unclear
linking: anchor
textstructure: closer opener salute
transcr: supplied
Note

contains verse lines or nested line groups only, possibly prefixed by a heading.
Example
<lg type="free">
 <l>Let me be my own fool</l>
 <l>of my own making, the sum of it</l>
</lg>
<lg type="free">
 <l>is equivocal.</l>
 <l>One says of the drunken farmer:</l>
</lg>
<lg type="free">
 <l>leave him lay off it. And this is</l>
 <l>the explanation.</l>
</lg>
Schematron

<sch:rule context="tei:lg">
<sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element must contain at least one child l, lg, or gap element.</sch:assert>
</sch:rule>
Schematron

<sch:rule context="tei:lg">
<sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]">Abstract model violation: Lines may not contain line groups.</sch:report>
</sch:rule>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate maxOccurs="1" minOccurs="1">
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <elementRef key="lg"/>
  </alternate>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <classRef key="model.global"/>
   <elementRef key="lg"/>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration 
element lg
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         tei_model.lLike
       | tei_model.stageLike
       | tei_model.labelLike
       | tei_model.pPart.transcriptional
       | tei_lg
      ),
      (
         tei_model.lLike
       | tei_model.stageLike
       | tei_model.labelLike
       | tei_model.pPart.transcriptional
       | tei_model.global
       | tei_lg
      )*,
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

<list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Module core
Attributes
Member of
model.listLike
Contained by
core: corr head hi item l note orig p quote ref sic sp textLang title unclear
figures: cell
header: change handNote keywords revisionDesc sourceDesc
linking: seg
msdescription: additions
textcrit: witness
textstructure: back body div salute
transcr: supplied
May contain
core: cb gap head item label lb note noteGrp pb
linking: anchor
textstructure: closer opener salute
Note

May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.
Example
<list rend="numbered">
 <item>a butcher</item>
 <item>a baker</item>
 <item>a candlestick maker, with
 <list rend="bulleted">
   <item>rings on his fingers</item>
   <item>bells on his toes</item>
  </list>
 </item>
</list>
Example
<list rend="bulleted" type="syllogism">
 <item>All Cretans are liars.</item>
 <item>Epimenides is a Cretan.</item>
 <item>ERGO Epimenides is a liar.</item>
</list>
Example
<list rend="simple" type="litany">
 <item>God save us from drought.</item>
 <item>God save us from pestilence.</item>
 <item>God save us from wickedness in high places.</item>
 <item>Praise be to God.</item>
</list>
Example

The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):

<div1 type="section">
 <head>Athelstan's Ordinance</head>
 <list rend="numbered">
  <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with
     the stolen goods, [if he is] over twelve years and [if the value of the goods is] over
     eightpence.
  <list rend="numbered">
    <item n="1.1">And if anyone does spare one, he is to pay for the thief with his
         wergild — and the thief is to be no nearer a settlement on that account — or to
         clear himself by an oath of that amount.</item>
    <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is
         not to be spared [whether younger or older than twelve].</item>
    <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may
         then be redeemed with 120 shillings; and the kindred are to stand surety for him
         that he will desist for ever.</item>
    <item n="1.4">And if he steals after that, they are to pay for him with his wergild,
         or to bring him back there.</item>
    <item n="1.5">And if he steals after that, they are to pay for him with his wergild,
         whether to the king or to him to whom it rightly belongs; and everyone of those who
         supported him is to pay 120 shillings to the king as a fine.</item>
   </list>
  </item>
  <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom
     no justice can be obtained, that one should order their kindred to fetch back such a
     person to justice and to find him a lord in public meeting.
  <list rend="numbered">
    <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,
         he is then to be a fugitive afterwards, and he who encounters him is to strike him
         down as a thief.</item>
    <item n="2.2">And he who harbours him after that, is to pay for him with his wergild
         or to clear himself by an oath of that amount.</item>
   </list>
  </item>
  <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds
     his guilty man, so that the king is appealed to, is to repay the value of the goods and
     120 shillings to the king; and he who appeals to the king before he demands justice as
     often as he ought, is to pay the same fine as the other would have done, if he had
     refused him justice.
  <list rend="numbered">
    <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes
         known about him, is to forfeit the slave and be liable to his wergild on the first
         occasionp if he does it more often, he is to be liable to pay all that he owns.</item>
    <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been
         an accessory of thieves who have committed theft, is to liable to the same.</item>
   </list>
  </item>
  <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to
     a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is
     afterwards convicted at the three-fold ordeal.</item>
 </list>
</div1>

Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.
Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they
confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards
inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy
Cross.
<list rend="simple">
  <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have
     subscribed to the pious and catholic validity of this document with the sign of the Holy
     Cross.</item>
  <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with
     the sign of the Holy Cross.</item>
  <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the
     sign of the Holy Cross.</item>
  <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the
     sign of the Holy Cross.</item>
  <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of
     the Holy Cross.</item>
  <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>
  <item>I, Æthelwine, bishop, have subscribed through delegates.</item>
  <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy
     Cross.</item>
 </list>
</p>
Schematron

<sch:rule context="tei:list[@type='gloss']">
<sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert>
</sch:rule>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc"
    maxOccurs="unbounded" minOccurs="0"/>
  </alternate>
  <alternate maxOccurs="1" minOccurs="1">
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <elementRef key="item"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <elementRef key="headLabel"
     minOccurs="0"/>
    <elementRef key="headItem"
     minOccurs="0"/>
    <sequence maxOccurs="unbounded"
     minOccurs="1">
     <elementRef key="label"/>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
     <elementRef key="item"/>
     <classRef key="model.global"
      maxOccurs="unbounded" minOccurs="0"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration 
element list
{
   tei_att.global.attribute.n,
   tei_att.global.rendition.attribute.rend,
   tei_att.cmc.attributes,
   (
      ( tei_model.divTop | tei_model.global | desc* )*,
      (
         ( ( tei_item, tei_model.global* )+ )
       | (
            headLabel?,
            headItem?,
            ( ( tei_label, tei_model.global*, tei_item, tei_model.global* )+ )
         )
      ),
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

<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]
Module core
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
editions
literature
sigla
regest
translation
Member of
model.biblLike model.frontPart
Contained by
core: biblStruct corr head hi item l listBibl note orig p quote ref sic textLang title unclear
figures: cell
header: change handNote sourceDesc
linking: seg
msdescription: additional additions msItem
textcrit: witness
textstructure: back body div salute
transcr: supplied
May contain
core: bibl biblStruct cb head lb listBibl pb rs
header: idno
linking: anchor
msdescription: msDesc
namesdates: eventName persName placeName
Example
<listBibl>
 <head>Works consulted</head>
 <bibl>Blain, Clements and Grundy: Feminist Companion to
   Literature in English (Yale, 1990)
 </bibl>
 <biblStruct>
  <analytic>
   <title>The Interesting story of the Children in the Wood</title>
  </analytic>
  <monogr>
   <title>The Penny Histories</title>
   <author>Victor E Neuberg</author>
   <imprint>
    <publisher>OUP</publisher>
    <date>1968</date>
   </imprint>
  </monogr>
 </biblStruct>
</listBibl>
Schematron

<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:listBibl"/>
</sch:pattern>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.headLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <elementRef key="desc"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.biblLike"/>
   <classRef key="model.milestoneLike"/>
   <classRef key="model.nameLike"/>
  </alternate>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="relation"/>
   <elementRef key="listRelation"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element listBibl
{
   tei_att.global.change.attribute.change,
   tei_att.cmc.attributes,
   tei_att.sortable.attributes,
   attribute type
   {
      "editions" | "literature" | "sigla" | "regest" | "translation"
   }?,
   (
      tei_model.headLike*,
      desc*,
      ( tei_model.biblLike | tei_model.milestoneLike | tei_model.nameLike )*,
      ( relation | listRelation )*
   )
}

<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]
Module header
Attributes
ordered indicates whether the ordering of its child change elements is to be considered significant or not.
Status Optional
Datatype teidata.truthValue
Default true
Contained by
header: listChange revisionDesc
May contain
core: head
header: change listChange
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-11" who="#LB"> deleted chapter 10 </change>
  <change when="1991-11-02" who="#MSM"> completed first draft </change>
 </listChange>
</revisionDesc>
Example
<profileDesc>
 <creation>
  <listChange ordered="true">
   <change xml:id="CHG-1">First stage, written in ink by a writer</change>
   <change xml:id="CHG-2">Second stage, written in Goethe's hand using pencil</change>
   <change xml:id="CHG-3">Fixation of the revised passages and further revisions by
       Goethe using ink</change>
   <change xml:id="CHG-4">Addition of another stanza in a different hand,
       probably at a later stage</change>
  </listChange>
 </creation>
</profileDesc>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="head"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="change"/>
   <elementRef key="listChange"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element listChange
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   attribute ordered { teidata.truthValue }?,
   ( tei_head*, ( tei_change | tei_listChange )+ )
}

<listEvent>

<listEvent>
Module core
Contained by
core: note
May contain
core: event
Content model 
<content>
 <elementRef key="event"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
Schema Declaration 
element listEvent { tei_event* }

<listWit>

<listWit> (witness list) lists definitions for all the witnesses referred to by a critical apparatus, optionally grouped hierarchically. [13.1. The Apparatus Entry, Readings, and Witnesses]
Module textcrit
Attributes
  • att.global
    • xml:lang
    • xml:base
    • xml:space
    • @xml:id
    • @n
Member of
model.listLike
Contained by
core: corr head hi item l note orig p quote ref sic sp textLang title unclear
figures: cell
header: change handNote sourceDesc
linking: seg
msdescription: additions
textcrit: listWit witness
textstructure: back body div salute
transcr: supplied
May contain
core: head
textcrit: listWit witness
Note

May contain a series of witness or listWit elements.

The provision of a listWit element simplifies the automatic processing of the apparatus, e.g. the reconstruction of the readings for all witnesses from an exhaustive apparatus.

Situations commonly arise where there are many more or less fragmentary witnesses, such that there may be quite distinct groups of witnesses for different parts of a text or collection of texts. Such groups may be given separately, or nested within a single listWit element at the beginning of the file listing all the witnesses, partial and complete, for the text, with the attestation of fragmentary witnesses indicated within the apparatus by use of the <witStart> and <witEnd> elements described in section 13.1.5. Fragmentary Witnesses.

Note however that a given witness can only be defined once, and can therefore only appear within a single listWit element.
Example
<listWit>
 <witness xml:id="HL26">Ellesmere, Huntingdon Library 26.C.9</witness>
 <witness xml:id="PN392">Hengwrt, National Library of Wales,
   Aberystwyth, Peniarth 392D</witness>
 <witness xml:id="RP149">Bodleian Library Rawlinson Poetic 149
   (see further <ptr target="#MSRP149"/>)</witness>
</listWit>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.headLike"
   minOccurs="0"/>
  <elementRef key="desc"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <elementRef key="witness"/>
   <elementRef key="listWit"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element listWit
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.n,
   ( tei_model.headLike?, desc*, ( tei_witness | tei_listWit )+ )
}

<locus>

<locus> (locus) defines a location within a manuscript, manuscript part, or other object typically as a (possibly discontinuous) sequence of folio references. [11.3.5. References to Locations within a Manuscript]
Module msdescription
Member of
model.pPart.msdesc
Contained by
core: author biblScope corr date editor foreign head hi item l label note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions locus msItem repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
core: hi
msdescription: locus
character data
Note

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

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

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

<!-- within ms description --><msItem n="1">
 <locus from="1r" target="#F1r #F1v #F2r"
  to="2r">ff. 1r-2r</locus>
 <author>Ben Jonson</author>
 <title>Ode to himself</title>
 <rubric rend="italics"> An Ode<lb/> to him selfe.</rubric>
 <incipit>Com leaue the loathed stage</incipit>
 <explicit>And see his chariot triumph ore his wayne.</explicit>
 <bibl>
  <name>Beal</name>, <title>Index 1450-1625</title>, JnB 380</bibl>
</msItem>
<!-- within transcription ... -->
<pb xml:id="F1r"/>
<!-- ... -->
<pb xml:id="F1v"/>
<!-- ... -->
<pb xml:id="F2r"/>
<!-- ... -->
Example

The facs attribute is available globally when the transcr module is included in a schema. It may be used to point directly to an image file, as in the following example:

<msItem>
 <locus facs="images/08v.jpg images/09r.jpg images/09v.jpg images/10r.jpg images/10v.jpg">fols. 8v-10v</locus>
 <title>Birds Praise of Love</title>
 <bibl>
  <title>IMEV</title>
  <biblScope>1506</biblScope>
 </bibl>
</msItem>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="hi"/>
  <elementRef key="locus"/>
 </alternate>
</content>
Schema Declaration 
element locus { ( text | tei_model.gLike | tei_hi | tei_locus )* }

<monogr>

<monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels]
Module core
Contained by
core: biblStruct
May contain
core: author biblScope editor imprint note noteGrp ptr ref respStmt textLang title
header: availability extent idno
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="377" to="380" unit="page">377–380</biblScope>
 </monogr>
</biblStruct>
Example
<biblStruct type="book">
 <monogr>
  <author>
   <persName>
    <forename>Leo Joachim</forename>
    <surname>Frachtenberg</surname>
   </persName>
  </author>
  <title level="m" type="main">Lower Umpqua Texts</title>
  <imprint>
   <pubPlace>New York</pubPlace>
   <publisher>Columbia University Press</publisher>
   <date>1914</date>
  </imprint>
 </monogr>
 <series>
  <title level="s" type="main">Columbia University Contributions to
     Anthropology</title>
  <biblScope unit="volume">4</biblScope>
 </series>
</biblStruct>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="1" minOccurs="0">
   <sequence maxOccurs="1" minOccurs="1">
    <alternate maxOccurs="1" minOccurs="1">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <elementRef key="title"
     maxOccurs="unbounded" minOccurs="1"/>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
     <elementRef key="textLang"/>
     <elementRef key="editor"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <alternate maxOccurs="unbounded"
     minOccurs="1">
     <elementRef key="title"/>
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
    </alternate>
    <alternate maxOccurs="unbounded"
     minOccurs="0">
     <elementRef key="textLang"/>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <elementRef key="authority"/>
    <elementRef key="idno"/>
   </sequence>
  </alternate>
  <elementRef key="availability"
   maxOccurs="unbounded" minOccurs="0"/>
  <classRef key="model.noteLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="edition"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="idno"/>
    <classRef key="model.ptrLike"/>
    <elementRef key="editor"/>
    <elementRef key="sponsor"/>
    <elementRef key="funder"/>
    <elementRef key="respStmt"/>
   </alternate>
  </sequence>
  <elementRef key="imprint"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="imprint"/>
   <elementRef key="extent"/>
   <elementRef key="biblScope"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element monogr
{
   (
      (
         ( tei_author | tei_editor | meeting | tei_respStmt ),
         ( tei_author | tei_editor | meeting | tei_respStmt )*,
         tei_title+,
         (
            tei_model.ptrLike
          | tei_idno
          | tei_textLang
          | tei_editor
          | tei_respStmt
         )*
      )
    | (
         ( tei_title | tei_model.ptrLike | tei_idno )+,
         ( tei_textLang | tei_author | tei_editor | meeting | tei_respStmt )*
      )
    | ( authority, tei_idno )
   )?,
   tei_availability*,
   tei_model.noteLike*,
   (
      (
         edition,
         (
            tei_idno
          | tei_model.ptrLike
          | tei_editor
          | sponsor
          | funder
          | tei_respStmt
         )*
      )*
   ),
   tei_imprint,
   ( tei_imprint | tei_extent | tei_biblScope )*
}

<msContents>

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

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

<msDesc>

<msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object such as an early printed book. [11.1. Overview]
Module msdescription
Attributes
  • att.global
    • n
    • xml:lang
    • xml:base
    • xml:space
    • @xml:id
Member of
model.biblLike
Contained by
core: biblStruct corr head hi item l listBibl note orig p quote ref sic textLang title unclear
figures: cell
header: change handNote sourceDesc
linking: seg
msdescription: additions msItem
textcrit: witness
textstructure: body div salute
transcr: supplied
May contain
core: head p
msdescription: additional msContents msIdentifier physDesc
Note

Although the msDesc has primarily been designed with a view to encoding manuscript descriptions, it may also be used for other objects such as early printed books, fascicles, epigraphs, or any text-bearing objects that require substantial description. If an object is not text-bearing or the reasons for describing the object is not primarily the textual content, the more general <object> may be more suitable.
Example
<msDesc>
 <msIdentifier>
  <settlement>Oxford</settlement>
  <repository>Bodleian Library</repository>
  <idno type="Bod">MS Poet. Rawl. D. 169.</idno>
 </msIdentifier>
 <msContents>
  <msItem>
   <author>Geoffrey Chaucer</author>
   <title>The Canterbury Tales</title>
  </msItem>
 </msContents>
 <physDesc>
  <objectDesc>
   <p>A parchment codex of 136 folios, measuring approx
       28 by 19 inches, and containing 24 quires.</p>
   <p>The pages are margined and ruled throughout.</p>
   <p>Four hands have been identified in the manuscript: the first 44
       folios being written in two cursive anglicana scripts, while the
       remainder is for the most part in a mixed secretary hand.</p>
  </objectDesc>
 </physDesc>
</msDesc>
Schematron

<sch:rule context="tei:msContents|tei:physDesc|tei:history|tei:additional">


<sch:let name="gi" value="name(.)"/>
<sch:report test="preceding-sibling::*[ name(.) eq $gi ] and not( following-sibling::*[ name(.) eq $gi ] )"> Only one <sch:name/> is allowed as a child of <sch:value-of select="name(..)"/>.
</sch:report>
</sch:rule>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="msIdentifier"/>
  <classRef key="model.headLike"
   maxOccurs="unbounded" minOccurs="0"/>
  <alternate maxOccurs="1" minOccurs="1">
   <classRef key="model.pLike"
    maxOccurs="unbounded" minOccurs="1"/>
   <alternate maxOccurs="unbounded"
    minOccurs="0">
    <elementRef key="msContents"/>
    <elementRef key="physDesc"/>
    <elementRef key="history"/>
    <elementRef key="additional"/>
    <elementRef key="msPart"/>
    <elementRef key="msFrag"/>
   </alternate>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element msDesc
{
   tei_att.global.attribute.xmlid,
   (
      tei_msIdentifier,
      tei_model.headLike*,
      (
         tei_model.pLike+
       | (
            tei_msContents
          | tei_physDesc
          | history
          | tei_additional
          | msPart
          | msFrag
         )*
      )
   )
}

<msIdentifier>

<msIdentifier> (manuscript identifier) contains the information required to identify the manuscript or similar object being described. [11.4. The Manuscript Identifier]
Module msdescription
Attributes
Contained by
msdescription: msDesc
May contain
header: idno
msdescription: altIdentifier repository
namesdates: placeName
Example
<msIdentifier>
 <settlement>San Marino</settlement>
 <repository>Huntington Library</repository>
 <idno>MS.El.26.C.9</idno>
</msIdentifier>
Schematron

<sch:rule context="tei:msIdentifier">
<sch:report test="not( parent::tei:msPart ) and ( child::*[1]/self::idno or child::*[1]/self::altIdentifier or normalize-space(.) eq '')">An msIdentifier must contain either a repository or location.</sch:report>
</sch:rule>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <sequence maxOccurs="1" minOccurs="1">
   <classRef expand="sequenceOptional"
    key="model.placeNamePart"/>
   <elementRef key="institution"
    minOccurs="0"/>
   <elementRef key="repository"
    minOccurs="0"/>
   <elementRef key="collection"
    maxOccurs="unbounded" minOccurs="0"/>
   <elementRef key="idno"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="msName"/>
   <elementRef key="objectName"/>
   <elementRef key="altIdentifier"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element msIdentifier
{
   tei_att.global.change.attribute.change,
   (
      ( tei_placeName?, institution?, tei_repository?, collection*, tei_idno* ),
      ( msName | objectName | tei_altIdentifier )*
   )
}

<msItem>

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

<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]
Module core
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Optional
Datatype ID
n (number) gives a number (or other label) for an element, which is not necessarily unique within the document.
Derived from att.global
Status Optional
Datatype string
place specifies where this item is placed.
Derived from att.placement
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Legal values are:
margin
type
Status Optional
Legal values are:
footnote
crit
copies
references
publication history
ref
Status Optional
Datatype string
Member of
model.noteLike
Contained by
analysis: w
core: author bibl biblScope biblStruct corr date editor foreign head hi imprint item l label lg list monogr note noteGrp orig p pubPlace publisher quote ref respStmt rs sic sp speaker term textLang title unclear
figures: cell table
header: change distributor extent handNote
linking: seg
msdescription: additions altIdentifier msItem repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: back body closer div opener salute text
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl listEvent note noteGrp orig p pb ptr quote ref rs sic sp term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Example

In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":

And yet it is not only
in the great line of Italian renaissance art, but even in the
painterly <note place="bottom" resp="#MDMH"
 type="gloss">
 <term xml:lang="de">Malerisch</term>. This word has, in the German, two
distinct meanings, one objective, a quality residing in the object,
the other subjective, a mode of apprehension and creation. To avoid
confusion, they have been distinguished in English as
<mentioned>picturesque</mentioned> and
<mentioned>painterly</mentioned> respectively.
</note> style of the
Dutch genre painters of the seventeenth century that drapery has this
psychological significance.

<!-- elsewhere in the document -->
<respStmt xml:id="MDMH">
 <resp>translation from German to English</resp>
 <name>Hottinger, Marie Donald Mackie</name>
</respStmt>

For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.
Example

The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:

Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note anchored="true" n="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>
 <sequence maxOccurs="1" minOccurs="1">
  <macroRef key="macro.specialPara"/>
  <elementRef key="listEvent" maxOccurs="1"
   minOccurs="0"/>
 </sequence>
</content>
Schema Declaration 
element note
{
   tei_att.global.linking.attribute.corresp,
   attribute xml:id { ID }?,
   attribute n { string }?,
   attribute place { list { "margin"+ } }?,
   attribute type
   {
      "footnote" | "crit" | "copies" | "references" | "publication history"
   }?,
   attribute ref { string }?,
   ( tei_macro.specialPara, tei_listEvent? )
}

<noteGrp>

<noteGrp> (note group) contains a group of notes. [3.9.1.1. Encoding Grouped Notes]
Module core
Attributes
Member of
model.noteLike
Contained by
analysis: w
core: author biblScope biblStruct corr date editor foreign head hi imprint item l label lg list monogr note noteGrp orig p pubPlace publisher quote ref rs sic sp speaker term textLang title unclear
figures: cell table
header: change distributor extent handNote
linking: seg
msdescription: additions msItem repository
namesdates: eventName gender persName placeName
textstructure: back body closer div opener salute text
transcr: supplied
May contain
core: note noteGrp
Example

In 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
{
   tei_att.global.attributes,
   tei_att.anchoring.attributes,
   tei_att.cmc.attributes,
   tei_att.placement.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_att.written.attributes,
   ( desc*, ( tei_note | tei_noteGrp )+ )
}

<objectDesc>

<objectDesc> (object description) contains a description of the physical components making up the object which is being described. [11.7.1. Object Description]
Module msdescription
Attributes
form (form) a short project-specific name identifying the physical form of the carrier, for example as a codex, roll, fragment, partial leaf, cutting etc.
Status Optional
Datatype teidata.enumerated
Legal values are:
codex_lost
Note

Definitions for the terms used may typically be provided by a <valList> element in the project schema specification.
Member of
model.physDescPart
Contained by
msdescription: physDesc
May contain
core: p
Example
<objectDesc form="codex">
 <supportDesc material="mixed">
  <p>Early modern
  <material>parchment</material> and
  <material>paper</material>.</p>
 </supportDesc>
 <layoutDesc>
  <layout ruledLines="25 32"/>
 </layoutDesc>
</objectDesc>
Content model 
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <sequence maxOccurs="1" minOccurs="1">
   <elementRef key="supportDesc"
    minOccurs="0"/>
   <elementRef key="layoutDesc"
    minOccurs="0"/>
  </sequence>
 </alternate>
</content>
Schema Declaration 
element objectDesc
{
   attribute form { "codex_lost" }?,
   ( tei_model.pLike+ | ( supportDesc?, layoutDesc? ) )
}

<opener>

<opener> (opener) groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. [4.2. Elements Common to All Divisions]
Module textstructure
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
right-align-right
right-align-left
left-align-right
left-align-left
center-align-left
center-align-right
center
inline
hanging
Member of
model.divTopPart
Contained by
core: lg list
textstructure: body div
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
textstructure: salute
transcr: ex supplied
character data
Example
<opener>
 <dateline>Walden, this 29. of August 1592</dateline>
</opener>
Example
<opener>
 <dateline>
  <name type="place">Great Marlborough Street</name>
  <date>November 11, 1848</date>
 </dateline>
 <salute>My dear Sir,</salute>
</opener>
<p>I am sorry to say that absence from town and other circumstances have prevented me from
earlier enquiring...</p>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="argument"/>
  <elementRef key="byline"/>
  <elementRef key="dateline"/>
  <elementRef key="epigraph"/>
  <elementRef key="salute"/>
  <elementRef key="signed"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Schema Declaration 
element opener
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   attribute rend
   {
      list
      {
         (
            "right-align-right"
          | "right-align-left"
          | "left-align-right"
          | "left-align-left"
          | "center-align-left"
          | "center-align-right"
          | "center"
          | "inline"
          | "hanging"
         )+
      }
   }?,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | argument
    | byline
    | dateline
    | epigraph
    | tei_salute
    | signed
    | tei_model.global
   )*
}

<orig>

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Module core
Attributes
corresp (corresponds) points to elements that correspond to the current element in some way.
Derived from att.global.linking
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Member of
model.pPart.transcriptional
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi item l label lg note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions
namesdates: eventName gender persName placeName
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Example

If all that is desired is to call attention to the original version in the copy text, orig may be used alone:

<l>But this will be a <orig>meere</orig> confusion</l>
<l>And hardly shall we all be <orig>vnderstoode</orig>
</l>
Example

More usually, an orig will be combined with a regularized form within a choice element:

<l>But this will be a <choice>
  <orig>meere</orig>
  <reg>mere</reg>
 </choice> confusion</l>
<l>And hardly shall we all be <choice>
  <orig>vnderstoode</orig>
  <reg>understood</reg>
 </choice>
</l>
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration 
element orig
{
   tei_att.cmc.attributes,
   attribute corresp { list { teidata.pointer+ } }?,
   tei_macro.paraContent
}

<p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.6. Speech Contents]
Module core
Attributes
Member of
model.pLike
Contained by
core: item note quote sp textLang
figures: cell
header: availability change encodingDesc handNote projectDesc publicationStmt sourceDesc
msdescription: additional additions handDesc msContents msDesc msItem objectDesc physDesc
textstructure: back body div
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
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
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

<pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]
Module core
Attributes
Member of
model.milestoneLike
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi imprint item l label lg list listBibl note orig p pubPlace publisher quote ref rs sic sp speaker term textLang title unclear
figures: cell table
header: change distributor extent handNote
linking: seg
msdescription: additions msItem repository
namesdates: eventName gender persName placeName
textstructure: back body closer div opener salute text
transcr: supplied
May contain Empty element
Note

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

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

Page numbers may vary in different editions of a text.

<p> ... <pb ed="ed2" n="145"/>
<!-- Page 145 in edition "ed2" starts here --> ... <pb ed="ed1" n="283"/>
<!-- Page 283 in edition "ed1" starts here--> ... </p>
Example

A page beginning may be associated with a facsimile image of the page it introduces by means of the facs attribute

<body>
 <pb facs="page1.png" n="1"/>
<!-- page1.png contains an image of the page; the text it contains is encoded here -->
 <p>
<!-- ... -->
 </p>
 <pb facs="page2.png" n="2"/>
<!-- similarly, for page 2 -->
 <p>
<!-- ... -->
 </p>
</body>
Content model 
<content>
 <empty/>
</content>
Schema Declaration 
element pb
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.n,
   tei_att.global.facs.attribute.facs,
   tei_att.cmc.attributes,
   empty
}

<persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [14.2.1. Personal Names]
Module namesdates
Attributes
Member of
model.nameLike.agent
Contained by
core: author biblScope corr date editor foreign head hi item l label listBibl note orig p pubPlace publisher quote ref respStmt rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Example
<persName>
 <forename>Edward</forename>
 <forename>George</forename>
 <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of
 <placeName>Knebworth</placeName>
 </roleName>
</persName>
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration 
element persName { tei_att.cmc.attributes, tei_macro.phraseSeq }

<physDesc>

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

<placeName>

<placeName> (place name) contains an absolute or relative place name. [14.2.3. Place Names]
Module namesdates
Attributes
cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
Derived from att.global.responsibility
Status Optional
Datatype teidata.probCert
Legal values are:
low
Member of
model.placeNamePart
Contained by
core: author bibl biblScope corr date editor event foreign head hi item l label listBibl note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions altIdentifier msIdentifier repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Example
<placeName>
 <settlement>Rochester</settlement>
 <region>New York</region>
</placeName>
Example
<placeName>
 <geogName>Arrochar Alps</geogName>
 <region>Argylshire</region>
</placeName>
Example
<placeName>
 <measure>10 miles</measure>
 <offset>Northeast of</offset>
 <settlement>Attica</settlement>
</placeName>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <macroRef key="macro.phraseSeq"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="unclear"/>
   <elementRef key="choice"/>
   <elementRef key="supplied"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element placeName
{
   tei_att.cmc.attributes,
   attribute cert { "low" }?,
   ( tei_macro.phraseSeq, ( tei_unclear | tei_choice | tei_supplied )* )
}

<profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Module header
Member of
model.teiHeaderPart
Contained by
header: teiHeader
May contain
header: textClass
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="high" type="entertain"/>
  <purpose degree="medium" type="inform"/>
 </textDesc>
 <settingDesc>
  <setting>
   <name>Paris, France</name>
   <time>Late 19th century</time>
  </setting>
 </settingDesc>
</profileDesc>
Content model 
<content>
 <classRef key="model.profileDescPart"
  maxOccurs="unbounded" minOccurs="0"/>
</content>
Schema Declaration 
element profileDesc { tei_model.profileDescPart* }

<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]
Module header
Member of
model.encodingDescPart
Contained by
header: encodingDesc
May contain
core: p
Example
<projectDesc>
 <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p>
</projectDesc>
Schematron

<sch:pattern is-a="declarable">
<sch:param name="tde"
 value="tei:projectDesc"/>
</sch:pattern>
Content model 
<content>
 <classRef key="model.pLike"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
Schema Declaration 
element projectDesc { tei_model.pLike+ }

<ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links]
Module core
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
link
wdb
digitalisat
subtype (subtype) provides a sub-categorization of the element, if needed.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
span
Member of
model.ptrLike
Contained by
core: analytic author biblScope biblStruct corr date editor foreign head hi item l label monogr note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote publicationStmt
linking: seg
msdescription: additions repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain Empty element
Note

The target and cRef attributes are mutually exclusive.
Example
<ptr target="#p143 #p144"/>
<ptr target="http://www.tei-c.org"/>
<ptr cRef="1.3.4"/>
Schematron

<sch:rule context="tei:ptr">
<sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
</sch:rule>
Content model 
<content>
 <empty/>
</content>
Schema Declaration 
element ptr
{
   tei_att.cmc.attributes,
   tei_att.pointing.attribute.target,
   attribute type { "link" | "wdb" | "digitalisat" },
   attribute subtype { "span" }?,
   empty
}

<publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Module header
Contained by
header: fileDesc
May contain
core: date p ptr pubPlace publisher ref
header: availability distributor idno
Note

Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.
Example
<publicationStmt>
 <publisher>C. Muquardt </publisher>
 <pubPlace>Bruxelles &amp; Leipzig</pubPlace>
 <date when="1846"/>
</publicationStmt>
Example
<publicationStmt>
 <publisher>Chadwyck Healey</publisher>
 <pubPlace>Cambridge</pubPlace>
 <availability>
  <p>Available under licence only</p>
 </availability>
 <date when="1992">1992</date>
</publicationStmt>
Example
<publicationStmt>
 <publisher>Zea Books</publisher>
 <pubPlace>Lincoln, NE</pubPlace>
 <date>2017</date>
 <availability>
  <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>
 </availability>
 <ptr target="http://digitalcommons.unl.edu/zeabook/55"/>
</publicationStmt>
Content model 
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <sequence maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.publicationStmtPart.agency"/>
   <classRef key="model.publicationStmtPart.detail"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
 </alternate>
</content>
Schema Declaration 
element publicationStmt
{
   (
      (
         tei_model.publicationStmtPart.agency,
         tei_model.publicationStmtPart.detail*
      )+
   )
 | tei_model.pLike+
}

<publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Module core
Attributes
cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
Derived from att.global.responsibility
Status Optional
Datatype teidata.probCert
Legal values are:
low
Member of
model.imprintPart model.publicationStmtPart.agency
Contained by
core: bibl imprint
header: publicationStmt
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Note

Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page
Example
<imprint>
 <pubPlace>Oxford</pubPlace>
 <publisher>Clarendon Press</publisher>
 <date>1987</date>
</imprint>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <macroRef key="macro.phraseSeq"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="unclear"/>
   <elementRef key="choice"/>
   <elementRef key="supplied"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element publisher
{
   attribute cert { "low" }?,
   ( tei_macro.phraseSeq, ( tei_unclear | tei_choice | tei_supplied )* )
}

<pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Module core
Attributes
cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
Derived from att.global.responsibility
Status Optional
Datatype teidata.probCert
Legal values are:
low
Member of
model.imprintPart model.publicationStmtPart.detail
Contained by
core: bibl imprint
header: publicationStmt
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Example
<publicationStmt>
 <publisher>Oxford University Press</publisher>
 <pubPlace>Oxford</pubPlace>
 <date>1989</date>
</publicationStmt>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <macroRef key="macro.phraseSeq"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="unclear"/>
   <elementRef key="choice"/>
   <elementRef key="supplied"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element pubPlace
{
   attribute cert { "low" }?,
   ( tei_macro.phraseSeq, ( tei_unclear | tei_choice | tei_supplied )* )
}

<quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Module core
Attributes
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype teidata.language
Legal values are:
grc-Grek
grc-Latn
heb-Hebr
heb-Latn
de-Latn
lat
Member of
model.quoteLike
Contained by
core: author biblScope biblStruct corr date editor foreign head hi item l label note orig p pubPlace publisher quote ref rs sic sp speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions msItem
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: body div salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig p pb ptr quote ref rs sic sp term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Note

If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element.
Example
Lexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized in his
slogan, <quote>You shall know a word by the company it
keeps</quote>
<ref>(Firth, 1957)</ref>
Content model 
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration 
element quote
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   attribute xml:lang
   {
      "grc-Grek" | "grc-Latn" | "heb-Hebr" | "heb-Latn" | "de-Latn" | "lat"
   }?,
   tei_macro.specialPara
}

<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]
Module core
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
ebd
Ebd
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
corrigenda
copyright
homepage
wit
wdb
print
Member of
model.ptrLike
Contained by
core: analytic author biblScope biblStruct corr date editor foreign head hi item l label monogr note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote publicationStmt
linking: seg
msdescription: additions repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Note

The target and cRef attributes are mutually exclusive.
Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second
sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term>
</ref>.
Schematron

<sch:rule context="tei:ref">
<sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report>
</sch:rule>
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration 
element ref
{
   tei_att.cReferencing.attributes,
   tei_att.cmc.attributes,
   tei_att.pointing.attribute.target,
   attribute rend { list { ( "ebd" | "Ebd" )+ } }?,
   attribute type
   {
      "corrigenda" | "copyright" | "homepage" | "wit" | "wdb" | "print"
   },
   tei_macro.paraContent
}

<repository>

<repository> (repository) contains the name of a repository within which manuscripts or other objects are stored, possibly forming part of an institution. [11.4. The Manuscript Identifier]
Module msdescription
Contained by
msdescription: altIdentifier msIdentifier
May contain
core: cb choice date foreign gap hi lb note noteGrp pb ptr ref rs term title
header: idno
linking: anchor
msdescription: locus
namesdates: eventName persName placeName
transcr: ex
character data
Example
<msIdentifier>
 <settlement>Oxford</settlement>
 <institution>University of Oxford</institution>
 <repository>Bodleian Library</repository>
 <idno>MS. Bodley 406</idno>
</msIdentifier>
Content model 
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
Schema Declaration 
element repository { tei_macro.phraseSeq.limited }

<resp>

<resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Module core
Contained by
core: respStmt
May contain Empty element
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>
 <valList type="closed">
  <valItem ident="Content">
   <desc>Einleitung</desc>
  </valItem>
  <valItem ident="Content assistance">
   <desc>Einleitung unter Mitarbeit von</desc>
  </valItem>
  <valItem ident="Preliminary content work">
   <desc>Einleitung unter Verwendung der Vorarbeiten von</desc>
  </valItem>
  <valItem ident="Transcription and annotation">
   <desc>Transkription</desc>
  </valItem>
  <valItem ident="Transcription and annotation assistance">
   <desc>Transkription unter Mitarbeit von</desc>
  </valItem>
  <valItem ident="Preliminary transcription and annotation work">
   <desc>Transkription unter Verwendung der Vorarbeiten von</desc>
  </valItem>
  <valItem ident="TEI encoding">
   <desc>Kodierung (manuell)</desc>
  </valItem>
  <valItem ident="TEI encoding assistance">
   <desc>Kodierung unter Mitarbeit von</desc>
  </valItem>
  <valItem ident="Post-processing of TEI encoding">
   <desc>Nachkodierungsarbeiten</desc>
  </valItem>
  <valItem ident="Word to TEI transformation">
   <desc>Kodierung durch wort2tei</desc>
  </valItem>
  <valItem ident="TEX to TEI transformation">
   <desc>Kodierung durch tex2tei</desc>
  </valItem>
  <valItem ident="Korrigenda encoding">
   <desc>Kodierung der Korrigenda</desc>
  </valItem>
 </valList>
</content>
Legal values are:
Content
Einleitung
Content assistance
Einleitung unter Mitarbeit von
Preliminary content work
Einleitung unter Verwendung der Vorarbeiten von
Transcription and annotation
Transkription
Transcription and annotation assistance
Transkription unter Mitarbeit von
Preliminary transcription and annotation work
Transkription unter Verwendung der Vorarbeiten von
TEI encoding
Kodierung (manuell)
TEI encoding assistance
Kodierung unter Mitarbeit von
Post-processing of TEI encoding
Nachkodierungsarbeiten
Word to TEI transformation
Kodierung durch wort2tei
TEX to TEI transformation
Kodierung durch tex2tei
Korrigenda encoding
Kodierung der Korrigenda
Schema Declaration 
element resp
{
   "Content"
 | "Content assistance"
 | "Preliminary content work"
 | "Transcription and annotation"
 | "Transcription and annotation assistance"
 | "Preliminary transcription and annotation work"
 | "TEI encoding"
 | "TEI encoding assistance"
 | "Post-processing of TEI encoding"
 | "Word to TEI transformation"
 | "TEX to TEI transformation"
 | "Korrigenda encoding"
}
Legal values are:
Content
Einleitung
Content assistance
Einleitung unter Mitarbeit von
Preliminary content work
Einleitung unter Verwendung der Vorarbeiten von
Transcription and annotation
Transkription
Transcription and annotation assistance
Transkription unter Mitarbeit von
Preliminary transcription and annotation work
Transkription unter Verwendung der Vorarbeiten von
TEI encoding
Kodierung (manuell)
TEI encoding assistance
Kodierung unter Mitarbeit von
Post-processing of TEI encoding
Nachkodierungsarbeiten
Word to TEI transformation
Kodierung durch wort2tei
TEX to TEI transformation
Kodierung durch tex2tei
Korrigenda encoding
Kodierung der Korrigenda

<respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Module core
Attributes
  • att.global
    • n
    • xml:lang
    • xml:base
    • xml:space
    • @xml:id
Member of
model.respLike
Contained by
core: analytic biblStruct imprint monogr
header: titleStmt
msdescription: msItem
May contain
core: note resp
namesdates: persName
Example
<respStmt>
 <resp>transcribed from original ms</resp>
 <persName>Claus Huitfeldt</persName>
</respStmt>
Example
<respStmt>
 <resp>converted to XML encoding</resp>
 <name>Alan Morrison</name>
</respStmt>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="1" minOccurs="1">
   <sequence maxOccurs="1" minOccurs="1">
    <elementRef key="resp"
     maxOccurs="unbounded" minOccurs="1"/>
    <classRef key="model.nameLike.agent"
     maxOccurs="unbounded" minOccurs="1"/>
   </sequence>
   <sequence maxOccurs="1" minOccurs="1">
    <classRef key="model.nameLike.agent"
     maxOccurs="unbounded" minOccurs="1"/>
    <elementRef key="resp"
     maxOccurs="unbounded" minOccurs="1"/>
   </sequence>
  </alternate>
  <elementRef key="note"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration 
element respStmt
{
   tei_att.global.attribute.xmlid,
   (
      (
         ( tei_resp+, tei_model.nameLike.agent+ )
       | ( tei_model.nameLike.agent+, tei_resp+ )
      ),
      tei_note*
   )
}

<revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Module header
Attributes
Contained by
header: teiHeader
May contain
core: list
header: change listChange
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-11" who="#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
{
   tei_att.global.attributes,
   tei_att.docStatus.attributes,
   ( tei_list+ | tei_listChange+ | tei_change+ )
}

<row>

<row> (row) contains one row of a table. [15.1.1. TEI Tables]
Module figures
Attributes
Contained by
figures: table
May contain
figures: cell
Example
<row role="data">
 <cell role="label">Classics</cell>
 <cell>Idle listless and unimproving</cell>
</row>
Content model 
<content>
 <elementRef key="cell"
  maxOccurs="unbounded" minOccurs="1"/>
</content>
Schema Declaration 
element row { tei_att.tableDecoration.attribute.cols, tei_cell+ }

<rs>

<rs> (referencing string) contains a general purpose name or referring string. [14.2.1. Personal Names 3.6.1. Referring Strings]
Module core
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
ebd
Ebd
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
person
place
bibl
biblical
cRef
Status Optional
Datatype string
Member of
model.nameLike
Contained by
core: author biblScope corr date editor foreign head hi item l label listBibl note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Example
<q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs>
to him one day,
<q>have you heard that <rs type="place">Netherfield Park</rs> is let at
last?</q>
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration 
element rs
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   tei_att.canonical.attribute.ref,
   attribute rend { list { ( "ebd" | "Ebd" )+ } }?,
   attribute type { "person" | "place" | "bibl" | "biblical" },
   attribute cRef { string }?,
   tei_macro.phraseSeq
}

<salute>

<salute> (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc. [4.2.2. Openers and Closers]
Module textstructure
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
right-align-right
right-align-left
left-align-right
left-align-left
center-align-left
center-align-right
center
inline
hanging
Member of
model.divWrapper
Contained by
core: lg list
figures: table
textstructure: body closer div opener
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Example
<salute>To all courteous mindes, that will voutchsafe the readinge.</salute>
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration 
element salute
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   attribute rend
   {
      list
      {
         (
            "right-align-right"
          | "right-align-left"
          | "left-align-right"
          | "left-align-left"
          | "center-align-left"
          | "center-align-right"
          | "center"
          | "inline"
          | "hanging"
         )+
      }
   }?,
   tei_macro.paraContent
}

<seg>

<seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [17.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.6. Speech Contents]
Module linking
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Derived from att.global
Status Optional
Datatype ID
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Derived from att.global.rendition
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
Legal values are:
ebd
Ebd
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Required
Datatype teidata.enumerated
Legal values are:
classical
lem
corr
add
wdb
comment
citation
emphasis
Member of
model.segLike
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi item l label note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions
namesdates: eventName gender persName placeName
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Note

The seg element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a ptr or other similar element.
Example
<seg>When are you leaving?</seg>
<seg>Tomorrow.</seg>
Example
<s>
 <seg rend="caps" type="initial-cap">So father's only</seg> glory was the ballfield.
</s>
Example
<seg type="preamble">
 <seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>
 <seg>Sinfiotli was the eldest of his sons ...</seg>
 <seg>Borghild, Sigmund's wife, had a brother ... </seg>
</seg>
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration 
element seg
{
   tei_att.cmc.attributes,
   tei_att.datcat.attribute.targetDatcat,
   attribute xml:id { xsd:ID }?,
   attribute rend { list { ( "ebd" | "Ebd" )+ } }?,
   attribute type
   {
      "classical"
    | "lem"
    | "corr"
    | "add"
    | "wdb"
    | "comment"
    | "citation"
    | "emphasis"
   },
   tei_macro.paraContent
}

<sic>

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
Module core
Attributes
Member of
model.pPart.transcriptional
Contained by
analysis: w
core: author biblScope choice corr date editor foreign head hi item l label lg note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions
namesdates: eventName gender persName placeName
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Example
for his nose was as sharp as
a pen, and <sic>a Table</sic> of green fields.
Example

If all that is desired is to call attention to the apparent problem in the copy text, sic may be used alone:

I don't know, Juan. It's so far in the past now
— how <sic>we can</sic> prove or disprove anyone's theories?
Example

It is also possible, using the choice and corr elements, to provide a corrected reading:

I don't know, Juan. It's so far in the past now
— how <choice>
 <sic>we can</sic>
 <corr>can we</corr>
</choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as
a pen, and <choice>
 <sic>a Table</sic>
 <corr>a' babbld</corr>
</choice> of green fields.
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration 
element sic
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

<sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as ‘born digital’ for a text which has no previous existence. [2.2.7. The Source Description]
Module header
Contained by
header: fileDesc
May contain
core: bibl biblStruct list listBibl p
figures: table
msdescription: msDesc
textcrit: listWit
Example
<sourceDesc>
 <bibl>
  <title level="a">The Interesting story of the Children in the Wood</title>. In
 <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
 <publisher>OUP</publisher>
  <date>1968</date>. </bibl>
</sourceDesc>
Example
<sourceDesc>
 <p>Born digital: no previous source exists.</p>
</sourceDesc>
Schematron

<sch:pattern is-a="declarable">
<sch:param name="tde"
 value="tei:sourceDesc"/>
</sch:pattern>
Content model 
<content>
 <alternate maxOccurs="1" minOccurs="1">
  <classRef key="model.pLike"
   maxOccurs="unbounded" minOccurs="1"/>
  <alternate maxOccurs="unbounded"
   minOccurs="1">
   <classRef key="model.biblLike"/>
   <classRef key="model.sourceDescPart"/>
   <classRef key="model.listLike"/>
  </alternate>
 </alternate>
</content>
Schema Declaration 
element sourceDesc
{
   tei_model.pLike+
 | ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+
}

<sp>

<sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.2. Speeches and Speakers]
Module core
Attributes
Member of
model.divPart
Contained by
core: item note quote textLang
figures: cell
header: change handNote
msdescription: additions
textstructure: body div
May contain
core: cb gap l lb lg list note noteGrp p pb quote speaker
figures: table
linking: anchor
textcrit: listWit
Note

The who attribute on this element may be used either in addition to the speaker element or as an alternative.
Example
<sp>
 <speaker>The reverend Doctor Opimian</speaker>
 <p>I do not think I have named a single unpresentable fish.</p>
</sp>
<sp>
 <speaker>Mr Gryll</speaker>
 <p>Bream, Doctor: there is not much to be said for bream.</p>
</sp>
<sp>
 <speaker>The Reverend Doctor Opimian</speaker>
 <p>On the contrary, sir, I think there is much to be said for him. In the first place [...]</p>
 <p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I
   will forbear [...]</p>
</sp>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <classRef key="model.stageLike"/>
  <classRef key="model.global"/>
  <classRef key="model.lLike"/>
  <classRef key="model.pLike"/>
  <classRef key="model.listLike"/>
  <classRef key="model.attributable"/>
  <elementRef key="speaker"/>
  <elementRef key="lg"/>
  <elementRef key="q"/>
 </alternate>
</content>
Schema Declaration 
element sp
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   (
      tei_model.stageLike
    | tei_model.global
    | tei_model.lLike
    | tei_model.pLike
    | tei_model.listLike
    | tei_model.attributable
    | tei_speaker
    | tei_lg
    | q
   )*
}

<speaker>

<speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.13.2. Core Tags for Drama]
Module core
Attributes
Contained by
core: sp
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Note

This element may be used to transcribe which character is speaking in a dramatic text as indicated by the source text; the who attribute of an sp element may be used to point to another element (typically a <role>) which provides information about the character speaking. Either or both may be used.
Example
<sp who="#ni #rsa">
 <speaker>Nancy and Robert</speaker>
 <stage type="delivery">(speaking simultaneously)</stage>
 <p>The future? ...</p>
</sp>
<list type="speakers">
 <item xml:id="ni"/>
 <item xml:id="rsa"/>
</list>
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration 
element speaker
{
   tei_att.global.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   tei_macro.phraseSeq
}

<supplied>

<supplied> (supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [12.3.3.1. Damage, Illegibility, and Supplied Text]
Module transcr
Member of
model.pPart.transcriptional
Contained by
analysis: w
core: author biblScope choice corr date editor foreign head hi item l label lg note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions
namesdates: eventName gender persName placeName
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Note

The <damage>, gap, <del>, unclear and supplied elements may be closely allied in use. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.
Example
I am dr Sr yr
<supplied reason="illegible"
 source="#amanuensis_copy">very humble Servt</supplied>
Sydney Smith
Example
<supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration 
element supplied { tei_macro.paraContent }

<table>

<table> (table) contains text displayed in tabular form, in rows and columns. [15.1.1. TEI Tables]
Module figures
Attributes
Member of
model.listLike
Contained by
core: corr head hi item l note orig p quote ref sic sp textLang title unclear
figures: cell
header: change handNote sourceDesc
linking: seg
msdescription: additions
textcrit: witness
textstructure: back body div salute
transcr: supplied
May contain
core: cb gap head lb note noteGrp pb
figures: row
linking: anchor
textstructure: closer salute
Note

Contains an optional heading and a series of rows.

Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate.
Example
<table cols="4" rows="4">
 <head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
 <row role="label">
  <cell role="data"/>
  <cell role="data">Dossing Cribs or Lodging Houses</cell>
  <cell role="data">Beds</cell>
  <cell role="data">Needys or Nightly Lodgers</cell>
 </row>
 <row role="data">
  <cell role="label">Bury St Edmund's</cell>
  <cell role="data">5</cell>
  <cell role="data">8</cell>
  <cell role="data">128</cell>
 </row>
 <row role="data">
  <cell role="label">Thetford</cell>
  <cell role="data">3</cell>
  <cell role="data">6</cell>
  <cell role="data">36</cell>
 </row>
 <row role="data">
  <cell role="label">Attleboro'</cell>
  <cell role="data">3</cell>
  <cell role="data">5</cell>
  <cell role="data">20</cell>
 </row>
 <row role="data">
  <cell role="label">Wymondham</cell>
  <cell role="data">1</cell>
  <cell role="data">11</cell>
  <cell role="data">22</cell>
 </row>
</table>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.headLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate maxOccurs="1" minOccurs="1">
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <elementRef key="row"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
   <sequence maxOccurs="unbounded"
    minOccurs="1">
    <classRef key="model.graphicLike"/>
    <classRef key="model.global"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
  </alternate>
  <sequence maxOccurs="unbounded"
   minOccurs="0">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration 
element table
{
   tei_att.global.attribute.xmlid,
   tei_att.cmc.attributes,
   (
      ( tei_model.headLike | tei_model.global )*,
      (
         ( ( tei_row, tei_model.global* )+ )
       | ( ( tei_model.graphicLike, tei_model.global* )+ )
      ),
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

<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]
Module textstructure
Attributes
Contained by
textstructure: TEI
May contain
header: teiHeader
textstructure: TEI text
Note

As with all elements in the TEI scheme (except <egXML>) this element is in the TEI namespace (see 5.7.2. Namespaces). Thus, when it is used as the outermost element of a TEI document, it is necessary to specify the TEI namespace on it. This is customarily achieved by including http://www.tei-c.org/ns/1.0 as the value of the XML namespace declaration (xmlns), without indicating a prefix, and then not using a prefix on TEI elements in the rest of the document. For example: <TEI version="4.8.1" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.
Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>The shortest TEI Document Imaginable</title>
   </titleStmt>
   <publicationStmt>
    <p>First published as part of TEI P2, this is the P5
         version using a namespace.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <text>
  <body>
   <p>This is about the shortest TEI document imaginable.</p>
  </body>
 </text>
</TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">
 <teiHeader>
  <fileDesc>
   <titleStmt>
    <title>A TEI Document containing four page images </title>
   </titleStmt>
   <publicationStmt>
    <p>Unpublished demonstration file.</p>
   </publicationStmt>
   <sourceDesc>
    <p>No source: this is an original work.</p>
   </sourceDesc>
  </fileDesc>
 </teiHeader>
 <facsimile>
  <graphic url="page1.png"/>
  <graphic url="page2.png"/>
  <graphic url="page3.png"/>
  <graphic url="page4.png"/>
 </facsimile>
</TEI>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="teiHeader"/>
  <alternate maxOccurs="1" minOccurs="1">
   <sequence maxOccurs="1" minOccurs="1">
    <classRef key="model.resource"
     maxOccurs="unbounded" minOccurs="1"/>
    <elementRef key="TEI"
     maxOccurs="unbounded" minOccurs="0"/>
   </sequence>
   <elementRef key="TEI"
    maxOccurs="unbounded" minOccurs="1"/>
  </alternate>
 </sequence>
</content>
Schema Declaration 
element TEI
{
   tei_att.global.attribute.xmlid,
   tei_att.global.attribute.n,
   tei_att.global.linking.attribute.sameAs,
   ( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) )
}

<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]
Module header
Contained by
textstructure: TEI
May contain
header: encodingDesc fileDesc profileDesc revisionDesc
Note

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

<term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Module core
Attributes
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype teidata.language
Legal values are:
grc-Grek
grc-Latn
heb-Hebr
heb-Latn
de-Latn
lat
type characterizes the element in some sense, using any convenient classification scheme or typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
term
title
Member of
model.emphLike
Contained by
core: author biblScope corr date editor foreign head hi item l label note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote keywords
linking: seg
msdescription: additions repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: cb choice corr date foreign gap hi lb note noteGrp orig pb ptr quote ref rs sic term title unclear
header: idno
linking: anchor seg
msdescription: locus
namesdates: eventName persName placeName
transcr: ex supplied
character data
Note

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

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

As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.
Example
A computational device that infers structure
from grammatical strings of words is known as a <term>parser</term>, and much of the history
of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term rend="sc" xml:id="TDPV1">discoursal point of view</term> as
<gloss target="#TDPV1">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>
Example
We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as
<gloss xml:id="TDPV2">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss>
Example
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.
Content model 
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
Schema Declaration 
element term
{
   tei_att.cmc.attributes,
   attribute xml:lang
   {
      "grc-Grek" | "grc-Latn" | "heb-Hebr" | "heb-Latn" | "de-Latn" | "lat"
   }?,
   attribute type { "term" | "title" }?,
   tei_macro.phraseSeq
}

<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]
Module textstructure
Attributes
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived from att.global
Status Optional
Datatype teidata.language
Legal values are:
grc-Grek
grc-Latn
heb-Hebr
heb-Latn
de-Latn
lat
Member of
model.resource
Contained by
textstructure: TEI
May contain
core: cb gap lb note noteGrp pb
linking: anchor
textstructure: back body
Note

This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.
Example
<text>
 <front>
  <docTitle>
   <titlePart>Autumn Haze</titlePart>
  </docTitle>
 </front>
 <body>
  <l>Is it a dragonfly or a maple leaf</l>
  <l>That settles softly down upon the water?</l>
 </body>
</text>
Example

The body of a text may be replaced by a group of nested texts, as in the following schematic:

<text>
 <front>
<!-- front matter for the whole group -->
 </front>
 <group>
  <text>
<!-- first text -->
  </text>
  <text>
<!-- second text -->
  </text>
 </group>
</text>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="1" minOccurs="0">
   <elementRef key="front"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
  <alternate maxOccurs="1" minOccurs="1">
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   maxOccurs="unbounded" minOccurs="0"/>
  <sequence maxOccurs="1" minOccurs="0">
   <elementRef key="back"/>
   <classRef key="model.global"
    maxOccurs="unbounded" minOccurs="0"/>
  </sequence>
 </sequence>
</content>
Schema Declaration 
element text
{
   attribute xml:lang
   {
      "grc-Grek" | "grc-Latn" | "heb-Hebr" | "heb-Latn" | "de-Latn" | "lat"
   }?,
   (
      tei_model.global*,
      ( ( front, tei_model.global* )? ),
      ( tei_body | group ),
      tei_model.global*,
      ( ( tei_back, tei_model.global* )? )
   )
}

<textClass>

<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
Module header
Member of
model.profileDescPart
Contained by
header: profileDesc
May contain
header: keywords
Example
<taxonomy>
 <category xml:id="acprose">
  <catDesc>Academic prose</catDesc>
 </category>
<!-- other categories here -->
</taxonomy>
<!-- ... -->
<textClass>
 <catRef target="#acprose"/>
 <classCode scheme="http://www.udcc.org">001.9</classCode>
 <keywords scheme="http://authorities.loc.gov">
  <list>
   <item>End of the world</item>
   <item>History - philosophy</item>
  </list>
 </keywords>
</textClass>
Schematron

<sch:pattern is-a="declarable">
<sch:param name="tde" value="tei:textClass"/>
</sch:pattern>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <elementRef key="classCode"/>
  <elementRef key="catRef"/>
  <elementRef key="keywords"/>
 </alternate>
</content>
Schema Declaration 
element textClass { ( classCode | catRef | tei_keywords )* }

<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]
Module core
Attributes
mainLang (main language) supplies a code which identifies the chief language used in the bibliographic work.
Status Optional
Datatype teidata.language
otherLangs (other languages) one or more codes identifying any other languages used in the bibliographic work.
Status Optional
Datatype 0–∞ occurrences of teidata.language separated by whitespace
Member of
model.msItemPart
Contained by
core: analytic biblStruct monogr
msdescription: msContents msItem
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig p pb ptr quote ref rs sic sp term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
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="en" otherLangs="la"> Predominantly in English with Latin
glosses</textLang>
Content model 
<content>
 <macroRef key="macro.specialPara"/>
</content>
Schema Declaration 
element textLang
{
   tei_att.global.attributes,
   attribute mainLang { teidata.language }?,
   attribute otherLangs { list { teidata.language* } }?,
   tei_macro.specialPara
}

<title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Module core
Attributes
type classifies the title according to some convenient typology.
Derived from att.typed
Status Optional
Datatype teidata.enumerated
Legal values are:
main
short
quote_title
Note

This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single title element.
Member of
model.emphLike model.msQuoteLike
Contained by
core: analytic author biblScope biblStruct corr date editor foreign head hi item l label monogr note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote titleStmt
linking: seg
msdescription: additions msItem repository
namesdates: eventName gender persName placeName
textcrit: witness
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Note

The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.
Example
<title>Information Technology and the Research Process: Proceedings of
a conference held at Cranfield Institute of Technology, UK,
18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable
edition</title>
Example
<title type="full">
 <title type="main">Synthèse</title>
 <title type="sub">an international journal for
   epistemology, methodology and history of
   science</title>
</title>
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration 
element title
{
   tei_att.cmc.attributes,
   attribute type { "main" | "short" | "quote_title" }?,
   tei_macro.paraContent
}

<titleStmt>

<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
Module header
Contained by
header: fileDesc
May contain
core: author editor respStmt title
Example
<titleStmt>
 <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
 <respStmt>
  <resp>compiled by</resp>
  <name>P.J. Lucas</name>
 </respStmt>
</titleStmt>
Content model 
<content>
 <sequence maxOccurs="1" minOccurs="1">
  <elementRef key="title"
   maxOccurs="unbounded" minOccurs="1"/>
  <classRef key="model.respLike"
   maxOccurs="unbounded" minOccurs="0"/>
 </sequence>
</content>
Schema Declaration 
element titleStmt { tei_title+, tei_model.respLike* }

<unclear>

<unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [12.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions]
Module core
Attributes
reason indicates why the material is hard to transcribe.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
illegible
(illegible)
inaudible
(inaudible)
faded
(faded)
background_noise
(background noise)
eccentric_ductus
(eccentric ductus) indicates illegibility due to an unusual, awkward, or incompetent execution of a glyph or glyphs
<div>
 <head>Rx</head>
 <p>500 mg <unclear reason="illegible">placebo</unclear>
 </p>
</div>
Note

One or more words may be used to describe the reason; usually each word will refer to a single cause.
agent Where the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
Status Optional
Datatype teidata.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
Member of
model.pPart.transcriptional
Contained by
analysis: w
core: author biblScope choice corr date editor foreign head hi item l label lg note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions
namesdates: eventName gender persName placeName
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: bibl biblStruct cb choice corr date foreign gap hi l label lb lg list listBibl note noteGrp orig pb ptr quote ref rs sic term title unclear
figures: table
header: idno
linking: anchor seg
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex supplied
character data
Note

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

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

The hand attribute points to a definition of the hand concerned, as further discussed in section 12.3.2.1. Document Hands.
Example
<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
Content model 
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration 
element unclear
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.dimensions.attributes,
   tei_att.editLike.attributes,
   attribute reason
   {
      list
      {
         (
            "illegible"
          | "inaudible"
          | "faded"
          | "background_noise"
          | "eccentric_ductus"
          | teidata.enumerated
         )+
      }
   }?,
   attribute agent { teidata.enumerated }?,
   tei_macro.paraContent
}

<w>

<w> (word) represents a grammatical (not necessarily orthographic) word. [18.1. Linguistic Segment Categories 18.4.2. Lightweight Linguistic Annotation]
Module analysis
Attributes
Member of
model.segLike
Contained by
analysis: w
core: author biblScope corr date editor foreign head hi item l label note orig p pubPlace publisher quote ref rs sic speaker term textLang title unclear
figures: cell
header: change distributor extent handNote
linking: seg
msdescription: additions
namesdates: eventName gender persName placeName
textstructure: closer opener salute
transcr: supplied
May contain
analysis: w
core: cb choice corr gap hi lb note noteGrp orig pb sic unclear
linking: anchor seg
transcr: ex supplied
character data
Example

This example is adapted from the Folger Library’s Early Modern English Drama version of The Wits: a Comedy by William Davenant.

<l>
 <w lemma="it" pos="pn"
  xml:id="A19883-003-a-0100">IT</w>
 <w lemma="have" pos="vvz"
  xml:id="A19883-003-a-0110">hath</w>
 <w lemma="be" pos="vvn"
  xml:id="A19883-003-a-0120">been</w>
 <w lemma="say" pos="vvn"
  xml:id="A19883-003-a-0130">said</w>
 <w lemma="of" pos="acp-p"
  xml:id="A19883-003-a-0140">of</w>
 <w lemma="old" pos="j"
  xml:id="A19883-003-a-0150">old</w>
 <pc xml:id="A19883-003-a-0160">,</pc>
 <w lemma="that" pos="cs"
  xml:id="A19883-003-a-0170">that</w>
 <w lemma="play" pos="vvz"
  xml:id="A19883-003-a-0180">
  <choice>
   <orig>Playes</orig>
   <reg>Plays</reg>
  </choice>
 </w>
 <w lemma="be" pos="vvb"
  xml:id="A19883-003-a-0190">are</w>
 <w lemma="feast" pos="n2"
  xml:id="A19883-003-a-0200">Feasts</w>
 <pc xml:id="A19883-003-a-0210">,</pc>
</l>
<l xml:id="A19883-e100220">
 <w lemma="poet" pos="n2"
  xml:id="A19883-003-a-0220">Poets</w>
 <w lemma="the" pos="d"
  xml:id="A19883-003-a-0230">the</w>
 <w lemma="cook" pos="n2"
  xml:id="A19883-003-a-0240">
  <choice>
   <orig>Cookes</orig>
   <reg>Cooks</reg>
  </choice>
 </w>
 <pc xml:id="A19883-003-a-0250">,</pc>
 <w lemma="and" pos="cc"
  xml:id="A19883-003-a-0260">and</w>
 <w lemma="the" pos="d"
  xml:id="A19883-003-a-0270">the</w>
 <w lemma="spectator" pos="n2"
  xml:id="A19883-003-a-0280">Spectators</w>
 <w lemma="guest" pos="n2"
  xml:id="A19883-003-a-0290">Guests</w>
 <pc xml:id="A19883-003-a-0300">,</pc>
</l>
<l xml:id="A19883-e100230">
 <w lemma="the" pos="d"
  xml:id="A19883-003-a-0310">The</w>
 <w lemma="actor" pos="n2"
  xml:id="A19883-003-a-0320">Actors</w>
 <w lemma="waiter" pos="n2"
  xml:id="A19883-003-a-0330">Waiters</w>
 <pc xml:id="A19883-003-a-0340">:</pc>
<!-- ... -->
</l>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="seg"/>
  <elementRef key="w"/>
  <elementRef key="m"/>
  <elementRef key="c"/>
  <elementRef key="pc"/>
  <classRef key="model.global"/>
  <classRef key="model.lPart"/>
  <classRef key="model.hiLike"/>
  <classRef key="model.pPart.edit"/>
 </alternate>
</content>
Schema Declaration 
element w
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.linguistic.attributes,
   tei_att.notated.attributes,
   tei_att.segLike.attributes,
   tei_att.typed.attributes,
   (
      text
    | tei_model.gLike
    | tei_seg
    | tei_w
    | m
    | c
    | pc
    | tei_model.global
    | tei_model.lPart
    | tei_model.hiLike
    | tei_model.pPart.edit
   )*
}

<witness>

<witness> (witness) contains either a description of a single witness referred to within the critical apparatus, or a list of witnesses which is to be referred to by a single sigil. [13.1. The Apparatus Entry, Readings, and Witnesses]
Module textcrit
Attributes
Contained by
textcrit: listWit
May contain
core: bibl biblStruct choice date foreign hi label list listBibl note ptr quote ref rs term title
figures: table
header: idno
msdescription: locus msDesc
namesdates: eventName persName placeName
textcrit: listWit
transcr: ex
character data
Note

The content of the witness element may give bibliographic information about the witness or witness group, or it may be empty.
Example
<listWit>
 <witness xml:id="EL">Ellesmere, Huntingdon Library 26.C.9</witness>
 <witness xml:id="HG">Hengwrt, National Library of Wales,
   Aberystwyth, Peniarth 392D</witness>
 <witness xml:id="RA2">Bodleian Library Rawlinson Poetic 149
   (see further <ptr target="http://www.examples.com/MSdescs#MSRP149"/>)</witness>
</listWit>
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
  <elementRef key="note"/>
  <elementRef key="object"/>
 </alternate>
</content>
Schema Declaration 
element witness
{
   tei_att.global.attribute.xmlid,
   tei_att.global.linking.attribute.corresp,
   ( text | tei_model.limitedPhrase | tei_model.inter | tei_note | object )*
}

Schema kgk-minimal: Model classes

model.attributable

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

model.biblLike

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

model.common

model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System]
Module tei
Used by
body div
Members model.cmc model.divPart [model.lLike [l] model.pLike [p] lg sp] model.divTop [model.divTopPart [model.headLike [head] head opener] model.divWrapper [salute] ] model.inter [model.attributable [model.quoteLike [quote] ] model.biblLike [bibl biblStruct listBibl msDesc] model.egLike model.labelLike [label] model.listLike [list listWit table] model.oddDecl model.stageLike]
Note

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

model.dateLike

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

model.divBottom

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

model.divBottomPart

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

model.divLike

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

model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Module tei
Used by
macro.specialPara model.common
Members model.lLike [l] model.pLike [p] lg sp
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.

model.divTop

model.divTop Elements that can appear at the start of a text division [4.2. Elements Common to All Divisions]
Module tei
Used by
body div lg list model.common
Members model.divTopPart [model.headLike [head] head opener] model.divWrapper [salute]

model.divTopPart

model.divTopPart Elements that can only appear at the start of a text division [4.6. Title Pages]
Module tei
Used by
model.divTop
Members model.headLike [head] head opener

model.divWrapper

model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions]
Module tei
Used by
model.divBottom model.divTop
Members salute

model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
Module tei
Used by
model.highlighted model.limitedPhrase
Members foreign term title

model.encodingDescPart

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

model.frontPart

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

model.global

model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
Module tei
Used by
back body closer div head imprint l lg list macro.phraseSeq macro.phraseSeq.limited macro.specialPara model.paraPart msItem opener sp table text w
Members model.global.edit [gap] model.global.meta model.milestoneLike [anchor cb lb pb] model.noteLike [note noteGrp]

model.global.edit

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

model.headLike

model.headLike Elements that can appear as titles or headings
Module tei
Used by
biblStruct listBibl listWit model.divTopPart msDesc table
Members head

model.highlighted

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

model.hiLike

model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]
Module tei
Used by
model.highlighted model.limitedPhrase w
Members hi

model.imprintPart

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

model.inter

model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
Module tei
Used by
head l macro.specialPara model.common model.paraPart witness
Members model.attributable [model.quoteLike [quote] ] model.biblLike [bibl biblStruct listBibl msDesc] model.egLike model.labelLike [label] model.listLike [list listWit table] model.oddDecl model.stageLike

model.labelLike

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

model.limitedPhrase

model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
Module tei
Used by
macro.phraseSeq.limited witness
Members model.emphLike [foreign term title] model.hiLike [hi] model.pPart.data [model.addressLike model.dateLike [date] model.measureLike model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [placeName] ] eventName idno rs] ] model.pPart.editorial [choice ex] model.pPart.msdesc [locus] model.phrase.xml model.ptrLike [ptr ref]

model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Module tei
Used by
back model.inter sourceDesc sp
Members list listWit table

model.lLike

model.lLike groups elements representing metrical components such as verse lines.
Module tei
Used by
head lg model.divPart model.paraPart sp
Members l

model.milestoneLike

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

model.msItemPart

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

model.msQuoteLike

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

model.nameLike

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

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

model.nameLike.agent

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

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

model.noteLike

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

model.paraPart

model.paraPart groups elements that may appear in paragraphs and similar elements. [3.1. Paragraphs]
Module tei
Used by
macro.paraContent
Members model.gLike model.global [model.global.edit [gap] model.global.meta model.milestoneLike [anchor cb lb pb] model.noteLike [note noteGrp] ] model.inter [model.attributable [model.quoteLike [quote] ] model.biblLike [bibl biblStruct listBibl msDesc] model.egLike model.labelLike [label] model.listLike [list listWit table] model.oddDecl model.stageLike] model.lLike [l] model.phrase [model.graphicLike model.highlighted [model.emphLike [foreign term title] model.hiLike [hi] ] model.lPart model.pPart.data [model.addressLike model.dateLike [date] model.measureLike model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [placeName] ] eventName idno rs] ] model.pPart.edit [model.pPart.editorial [choice ex] model.pPart.transcriptional [corr orig sic supplied unclear] ] model.pPart.msdesc [locus] model.phrase.xml model.ptrLike [ptr ref] model.segLike [seg w] model.specDescLike] lg

model.phrase

model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]
Module tei
Used by
closer head l macro.phraseSeq macro.specialPara model.paraPart opener
Members model.graphicLike model.highlighted [model.emphLike [foreign term title] model.hiLike [hi] ] model.lPart model.pPart.data [model.addressLike model.dateLike [date] model.measureLike model.nameLike [model.nameLike.agent [persName] model.offsetLike model.persNamePart model.placeStateLike [model.placeNamePart [placeName] ] eventName idno rs] ] model.pPart.edit [model.pPart.editorial [choice ex] model.pPart.transcriptional [corr orig sic supplied unclear] ] model.pPart.msdesc [locus] model.phrase.xml model.ptrLike [ptr ref] model.segLike [seg w] model.specDescLike
Note

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

model.physDescPart

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

model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [14.2.3. Place Names]
Module tei
Used by
altIdentifier model.placeStateLike msIdentifier
Members placeName

model.placeStateLike

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

model.pLike

model.pLike groups paragraph-like elements.
Module tei
Used by
additional availability back encodingDesc handDesc model.divPart msContents msDesc msItem objectDesc physDesc projectDesc publicationStmt sourceDesc sp
Members p

model.pPart.data

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

model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]
Module tei
Used by
model.phrase w
Members model.pPart.editorial [choice ex] model.pPart.transcriptional [corr orig sic supplied unclear]

model.pPart.editorial

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

model.pPart.msdesc

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

model.pPart.transcriptional

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

model.profileDescPart

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

model.ptrLike

model.ptrLike groups elements used for purposes of location and reference. [3.7. Simple Links and Cross-References]
Module tei
Used by
analytic biblStruct model.limitedPhrase model.phrase model.publicationStmtPart.detail monogr
Members ptr ref

model.publicationStmtPart.agency

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

model.publicationStmtPart.detail

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

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

See also model.publicationStmtPart.agency.

model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Module tei
Used by
model.attributable model.msItemPart
Members quote

model.resource

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

model.respLike

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

model.segLike

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

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

model.teiHeaderPart

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

Schema kgk-minimal: Attribute classes

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.
Module tei
Members noteGrp
Attributes
anchored (anchored) indicates whether the copy text shows the exact place of reference for the note.
Status Optional
Datatype teidata.truthValue
Default true
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.
Status Optional
Datatype 1–∞ 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>

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]
Module tei
Members att.ascribed.directed [sp] change
Attributes
who indicates the person, or group of people, to whom the element content is ascribed.
Status Optional
Datatype 1–∞ 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.

att.ascribed.directed

att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Module tei
Members sp
Attributes
toWhom indicates the person, or group of people, to whom a speech act or action is directed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

In the following example from Mary Pix's The False Friend, speeches (sp) in the body of the play are linked to <castItem> elements in the <castList> using the toWhom attribute, which is used to specify who the speech is directed to. Additionally, the <stage> includes toWhom to indicate the directionality of the action.

<castItem type="role">
 <role xml:id="emil">Emilius.</role>
</castItem>
<castItem type="role">
 <role xml:id="lov">Lovisa</role>
</castItem>
<castItem type="role">
 <role xml:id="serv">A servant</role>
</castItem>
<!-- ... -->
<sp toWhom="#lov" who="#emil">
 <speaker>Emil.</speaker>
 <l n="1">My love!</l>
</sp>
<sp toWhom="#emil" who="#lov">
 <speaker>Lov.</speaker>
 <l n="2">I have no Witness of my Noble Birth</l>
 <stage toWhom="#serv" who="emil">Pointing to her Woman.</stage>
 <l>But that poor helpless wretch——</l>
</sp>
Note

To indicate the recipient of written correspondence, use the elements used in section 2.4.6. Correspondence Description, rather than a toWhom attribute.

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]
Module tei
Members cb lb pb
Attributes
break indicates 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.
Status Recommended
Datatype teidata.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>

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]
Module tei
Members att.naming [att.personal [eventName persName placeName] author editor pubPlace repository rs] biblStruct date distributor publisher resp respStmt term title
Attributes
key provides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
Status Optional
Datatype teidata.text
<author>
 <name key="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.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<name ref="http://viaf.org/viaf/109557338"
 type="person">Seamus Heaney</name>
Note

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

In this contrived example, a canonical reference to the same organisation is provided in four different ways.

<author n="1">
 <name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"
  type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
 
<author n="2">
 <name ref="nzvn:427308"
  type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
 
<author n="3">
 <name ref="./named_entities.xml#o427308"
  type="organisation">New Zealand Parliament, Legislative Council</name>
</author>
 

<author n="4">
 <name key="name-427308"
  type="organisation">New Zealand Parliament, Legislative Council</name>
</author>

The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection, but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire external system for key resolution be available.
Note

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

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

att.cmc

att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment.
Module tei
Members anchor biblStruct cb choice closer corr date foreign gap hi idno l label lb lg list listBibl noteGrp opener orig p pb persName placeName ptr quote ref rs salute seg sic table term title unclear w
Attributes
generatedBy (generated by) categorizes how the content of an element was generated in a CMC environment.
Status Optional
Datatype teidata.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>

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.
Module tei
Members ptr ref term
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.
Status Optional
Datatype teidata.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.

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]
Module tei
Members altIdentifier author change date editor eventName gender idno persName placeName resp title
Attributes
  • att.datable.custom
    • @when-custom
    • @notBefore-custom
    • @notAfter-custom
    • @from-custom
    • @to-custom
    • @datingPoint
    • @datingMethod
  • att.datable.iso
    • @when-iso
    • @notBefore-iso
    • @notAfter-iso
    • @from-iso
    • @to-iso
  • att.datable.w3c
    • @when
    • @notBefore
    • @notAfter
    • @from
    • @to
period supplies pointers to one or more definitions of named periods of time (typically <category>s, dates, or events) within which the datable item is understood to have occurred.
Status Optional
Datatype 1–∞ 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.

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]
Module namesdates
Members att.datable [altIdentifier author change date editor eventName gender idno persName placeName resp title]
Attributes
when-custom supplies the value of a date or time in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace

The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system

<p>Alhazen died in Cairo on the
<date when="1040-03-06"
  when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH
 </date>.</p>
<p>The current world will end at the
<date when="2012-12-21"
  when-custom="13.0.0.0.0">end of B'ak'tun 13</date>.</p>
<p>The Battle of Meggidu
(<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p>
<p>Esidorus bixit in pace annos LXX plus minus sub
<date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date>
</p>

Not all custom date formulations will have Gregorian equivalents.

The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
notBefore-custom specifies the earliest possible date for the event in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
notAfter-custom specifies the latest possible date for the event in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
from-custom indicates the starting point of the period in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
<event datingMethod="#julian"
 from-custom="1666-09-02" to-custom="1666-09-05" xml:id="FIRE1">
 <head>The Great Fire of London</head>
 <p>The Great Fire of London burned through a large part
   of the city of London.</p>
</event>
to-custom indicates the ending point of the period in some custom standard form.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
datingPoint supplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred.
Status Optional
Datatype teidata.pointer
datingMethod supplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
Status Optional
Datatype teidata.pointer
Contayning the Originall, Antiquity, Increaſe, Moderne
eſtate, and deſcription of that Citie, written in the yeare
<date calendar="#julian"
 datingMethod="#julian" when-custom="1598">1598</date>. by Iohn Stow
Citizen of London.

In this example, the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the date element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.
<date datingMethod="#creationOfWorld"
 when="1382-06-28" when-custom="6890-06-20"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num>
</date>

In this example, a date is given in a Mediaeval text measured ‘from the creation of the world’, which is normalized (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.
Note

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

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]
Module namesdates
Members att.datable [altIdentifier author change date editor eventName gender idno persName placeName resp title]
Attributes
when-iso supplies the value of a date or time in a standard form.
Status Optional
Datatype teidata.temporal.iso

The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.

<date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date>
<date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date>
<time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time>
<time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time>
<date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date>
<time when-iso="03:00">3 A.M.</time>
<time when-iso="14">around two</time>
<time when-iso="15,5">half past three</time>

All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.
He likes to be punctual. I said <q>
 <time when-iso="12">around noon</time>
</q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.

The second occurrence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurrence could not.
notBefore-iso specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso
notAfter-iso specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.iso
from-iso indicates the starting point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
to-iso indicates the ending point of the period in standard form.
Status Optional
Datatype teidata.temporal.iso
Note

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

If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date dur-iso="P8D" when-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.

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]
Module tei
Members att.datable [altIdentifier author change date editor eventName gender idno persName placeName resp title]
Attributes
when supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c

Examples of W3C date, time, and date & time formats.

<p>
 <date when="1945-10-24">24 Oct 45</date>
 <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>
 <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>
 <time when="14:12:38">fourteen twelve and 38 seconds</time>
 <date when="1962-10">October of 1962</date>
 <date when="--06-12">June 12th</date>
 <date when="---01">the first of the month</date>
 <date when="--08">August</date>
 <date when="2006">MMVI</date>
 <date when="0056">AD 56</date>
 <date when="-0056">56 BC</date>
</p>
This list begins in
the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after
Pentecost, in that year the
<date calendar="#julian" when="1632-06-06">27th of May (old style)</date>.
<opener>
 <dateline>
  <placeName>Dorchester, Village,</placeName>
  <date when="1828-03-02">March 2d. 1828.</date>
 </dateline>
 <salute>To
   Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time>
</opener>
notBefore specifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
notAfter specifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
from indicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
to indicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
Status Optional
Datatype teidata.temporal.w3c
Schematron

<sch:rule context="tei:*[@when]">
<sch:report role="nonfatal"
 test="@notBefore|@notAfter|@from|@to">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report>
</sch:rule>
Schematron

<sch:rule context="tei:*[@from]">
<sch:report role="nonfatal"
 test="@notBefore">The @from and @notBefore attributes cannot be used together.</sch:report>
</sch:rule>
Schematron

<sch:rule context="tei:*[@to]">
<sch:report role="nonfatal"
 test="@notAfter">The @to and @notAfter attributes cannot be used together.</sch:report>
</sch:rule>
Example
<date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date>
Note

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

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

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

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]
Module tei
Members att.segLike [seg w]
Attributes
datcat provides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcat provides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcat provides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Example

The example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.

The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.

<fs>
 <f datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
  name="POS">
  <symbol value="NN"
   valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>
 </f>
<!-- ... -->
</fs>

‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string ‘http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545’ is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.

While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.

If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [ID FS in TEI Guidelines].
<fs>
 <f fVal="#commonNoun" name="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="NN" xml:id="commonNoun"/>
 <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"
  value="NP" xml:id="properNoun"/>
<!-- ... -->
</fvLib>

Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.
Example

In the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above.

<gramGrp>
 <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"
  valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos>
</gramGrp>
Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>:
<tagsDecl partial="true">
<!-- ... -->
 <namespace name="http://www.tei-c.org/ns/1.0">
  <tagUsage gi="pos"
   targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage>
  <tagUsage gi="case"
   targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage>
<!-- ... -->
 </namespace>
</tagsDecl>
Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below:
<listPrefixDef>
 <prefixDef ident="ccr" matchPattern="pos"
  replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>
 <prefixDef ident="ccr" matchPattern="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>.
Example

The <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.
Example

The targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.

<fDecl name="POS"
 targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">
 <fDescr>part of speech (morphosyntactic category)</fDescr>
 <vRange>
  <vAlt>
   <symbol datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"
    value="NN"/>
   <symbol datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"
    value="NP"/>
<!-- ... -->
  </vAlt>
 </vRange>
</fDecl>

Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.
Example

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

att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Module tei
Members date ex gap supplied unclear
Attributes
unit names the unit used for the measurement
Status Optional
Datatype teidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
quantity specifies the length in the units specified
Status Optional
Datatype teidata.numeric
extent indicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
Status Optional
Datatype teidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precision characterizes the precision of the values specified by the other attributes.
Status Optional
Datatype teidata.certainty
scope where the measurement summarizes more than one observation, specifies the applicability of this measurement.
Status Optional
Datatype teidata.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.

att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Module tei
Members biblStruct change msDesc revisionDesc
Attributes
status describes the status of a document either currently or, when associated with a dated element, at the time indicated.
Status Optional
Datatype teidata.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="cleared" when="2010-10-02"/>
 <change status="embargoed"
  when="2010-08-02"/>
 <change status="frozen" when="2010-05-01"
  who="#MSM"/>
 <change status="draft" when="2010-03-01"
  who="#LB"/>
</revisionDesc>

att.edition

att.edition provides attributes identifying the source edition from which some encoded feature derives.
Module tei
Members cb lb pb
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.
Status Optional
Datatype 1–∞ 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.
Status Optional
Datatype 1–∞ 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="#stapledon1968" n="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 break="no" edRef="#stapledon1937"
  n="291"/>sciousness;</p>

In the above example, the soft hyphen in Stapledon 1937 is omitted. Such decisions may be documented in the edition's declaration of editorial principles, e.g. with the <hyphenation> element in the teiHeader.
Note

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

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]
Module tei
Members corr date eventName ex gap gender persName placeName supplied unclear
Attributes
evidence indicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
Status Optional
Datatype 1–∞ 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.
instant indicates whether this is an instant revision or not.
Status Optional
Datatype teidata.xTruthValue
Default false
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.

att.fragmentable

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

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

att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Module tei
Members TEI additional additions altIdentifier analytic anchor author availability back biblScope biblStruct body cb cell change choice closer corr date distributor div editor encodingDesc eventName ex extent fileDesc foreign gap gender handDesc handNote hi idno imprint item keywords l label lb lg list listBibl listChange listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt revisionDesc row rs salute seg sic sourceDesc sp speaker supplied table teiHeader term text textClass textLang title titleStmt unclear w witness
Attributes
xml:id (identifier) provides a unique identifier for the element bearing the attribute.
Status Optional
Datatype ID
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.
Status Optional
Datatype teidata.text
Note

The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.
xml:lang (language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Status Optional
Datatype teidata.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:base provides a base URI reference with which applications can resolve relative URI references into absolute URI references.
Status Optional
Datatype teidata.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:space signals an intention about how white space should be managed by applications.
Status Optional
Datatype teidata.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.

att.global.analytic

att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [18.2. Global Attributes for Simple Analyses 18.3. Spans and Interpretations]
Module analysis
Members att.global [TEI additional additions altIdentifier analytic anchor author availability back biblScope biblStruct body cb cell change choice closer corr date distributor div editor encodingDesc eventName ex extent fileDesc foreign gap gender handDesc handNote hi idno imprint item keywords l label lb lg list listBibl listChange listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt revisionDesc row rs salute seg sic sourceDesc sp speaker supplied table teiHeader term text textClass textLang title titleStmt unclear w witness]
Attributes
ana (analysis) indicates one or more elements containing interpretations of the element on which the ana attribute appears.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.global.change

att.global.change provides attributes allowing its member elements to specify one or more states or revision campaigns with which they are associated.
Module transcr
Members att.global [TEI additional additions altIdentifier analytic anchor author availability back biblScope biblStruct body cb cell change choice closer corr date distributor div editor encodingDesc eventName ex extent fileDesc foreign gap gender handDesc handNote hi idno imprint item keywords l label lb lg list listBibl listChange listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt revisionDesc row rs salute seg sic sourceDesc sp speaker supplied table teiHeader term text textClass textLang title titleStmt unclear w witness]
Attributes
change points to one or more change elements documenting a state or revision campaign to which the element bearing this attribute and its children have been assigned by the encoder.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

att.global.facs

att.global.facs provides attributes used to express correspondence between an element and all or part of a facsimile image or surface. [12.1. Digital Facsimiles]
Module transcr
Members att.global [TEI additional additions altIdentifier analytic anchor author availability back biblScope biblStruct body cb cell change choice closer corr date distributor div editor encodingDesc eventName ex extent fileDesc foreign gap gender handDesc handNote hi idno imprint item keywords l label lb lg list listBibl listChange listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt revisionDesc row rs salute seg sic sourceDesc sp speaker supplied table teiHeader term text textClass textLang title titleStmt unclear w witness]
Attributes
facs (facsimile) points to one or more images, portions of an image, or surfaces which correspond to the current element.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

att.global.linking

att.global.linking provides a set of attributes for hypertextual linking. [17. Linking, Segmentation, and Alignment]
Module linking
Members att.global [TEI additional additions altIdentifier analytic anchor author availability back biblScope biblStruct body cb cell change choice closer corr date distributor div editor encodingDesc eventName ex extent fileDesc foreign gap gender handDesc handNote hi idno imprint item keywords l label lb lg list listBibl listChange listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt revisionDesc row rs salute seg sic sourceDesc sp speaker supplied table teiHeader term text textClass textLang title titleStmt unclear w witness]
Attributes
corresp (corresponds) points to elements that correspond to the current element in some way.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace

In this example a <group> contains two texts, 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.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
sameAs points to an element that is the same as the current element.
Status Optional
Datatype teidata.pointer
copyOf points to an element of which the current element is a copy.
Status Optional
Datatype teidata.pointer
Note

Any content of the current element should be ignored. Its true content is that of the element being pointed at.
next (next) points to the next element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

It is recommended that the element indicated be of the same type as the element bearing this attribute.
prev (previous) points to the previous element of a virtual aggregate of which the current element is part.
Status Optional
Datatype teidata.pointer
Note

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

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

att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Module tei
Members att.global [TEI additional additions altIdentifier analytic anchor author availability back biblScope biblStruct body cb cell change choice closer corr date distributor div editor encodingDesc eventName ex extent fileDesc foreign gap gender handDesc handNote hi idno imprint item keywords l label lb lg list listBibl listChange listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt revisionDesc row rs salute seg sic sourceDesc sp speaker supplied table teiHeader term text textClass textLang title titleStmt unclear w witness]
Attributes
rend (rendition) indicates how the element in question was rendered or presented in the source text.
Status Optional
Datatype 1–∞ occurrences of teidata.word separated by whitespace
<head rend="align(center) case(allcaps)">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle,
<lb/>On Her <lb/>
 <hi rend="case(mixed)">New Blazing-World</hi>.
</head>
Note

These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.
style contains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text.
Status Optional
Datatype teidata.text
<head style="text-align: center; font-variant: small-caps;">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
<lb/>
 <hi style="font-variant: normal">New Blazing-World</hi>.
</head>
Note

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

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

If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.
rendition points to a description of the rendering or presentation used for this element in the source text.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
<head rendition="#ac #sc">
 <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her
<lb/>
 <hi rendition="#normal">New Blazing-World</hi>.
</head>
<!-- elsewhere... -->
<rendition scheme="css" xml:id="sc">font-variant: small-caps</rendition>
<rendition scheme="css" xml:id="normal">font-variant: normal</rendition>
<rendition scheme="css" xml:id="ac">text-align: center</rendition>
Note

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

If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend.

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

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

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]
Module tei
Members att.global [TEI additional additions altIdentifier analytic anchor author availability back biblScope biblStruct body cb cell change choice closer corr date distributor div editor encodingDesc eventName ex extent fileDesc foreign gap gender handDesc handNote hi idno imprint item keywords l label lb lg list listBibl listChange listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt revisionDesc row rs salute seg sic sourceDesc sp speaker supplied table teiHeader term text textClass textLang title titleStmt unclear w witness]
Attributes
cert (certainty) signifies the degree of certainty associated with the intervention or interpretation.
Status Optional
Datatype teidata.probCert
resp (responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a respStmt, author, editor or similar element which clarifies the exact role played by the agent. Pointing to multiple respStmts 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="high" resp="#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>

att.global.source

att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Module tei
Members att.global [TEI additional additions altIdentifier analytic anchor author availability back biblScope biblStruct body cb cell change choice closer corr date distributor div editor encodingDesc eventName ex extent fileDesc foreign gap gender handDesc handNote hi idno imprint item keywords l label lb lg list listBibl listChange listWit locus monogr msContents msDesc msIdentifier msItem note noteGrp objectDesc opener orig p pb persName physDesc placeName profileDesc projectDesc ptr pubPlace publicationStmt publisher quote ref repository resp respStmt revisionDesc row rs salute seg sic sourceDesc sp speaker supplied table teiHeader term text textClass textLang title titleStmt unclear w witness]
Attributes
source specifies the source from which some aspect of this element is drawn.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Schematron

<sch:rule context="tei:*[@source]">
<sch:let name="srcs"
 value="tokenize( normalize-space(@source),' ')"/>
<sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like
<sch:value-of select="name(.)"/>), the @source attribute
should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.)
</sch:report>
</sch:rule>
Note

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

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

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

When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.
Example
<p>
<!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested
   term.</quote>
<!-- ... -->
</p>
Example
<p>
<!-- ... -->
 <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the
   less we seem to know.</quote>
<!-- ... -->
</p>
<!-- ... -->
<bibl xml:id="chicago_15_ed">
 <title level="m">The Chicago Manual of Style</title>,
<edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of
   Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>.

</bibl>
Example
<elementRef key="p" source="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.

att.lexicographic.normalized

att.lexicographic.normalized provides attributes for usage within word-level elements in the analysis module and within lexicographic microstructure in the dictionaries module.
Module analysis
Members att.linguistic [w]
Attributes
norm (normalized) provides the normalized/standardized form of information present in the source text in a non-normalized form.
Status Optional
Datatype teidata.text

Normalization of part-of-speech information within a dictionary entry.

<gramGrp>
 <pos norm="noun">n</pos>
</gramGrp>

Normalization of a source form in a tokenized historical corpus.

<s>
 <w>for</w>
 <w norm="virtue's">vertues</w>
 <w>sake</w>
</s>
<s>
 <w norm="persuasion">perswasion</w>
 <w>of</w>
 <w norm="Unity">Vnitie</w>
</s>

Example of normalization from Aviso. Relation oder Zeitung. Wolfenbüttel, 1609. In: Deutsches Textarchiv.

<s>
 <w norm="freiwillig">freywillig</w>
 <pc join="left" norm=",">/</pc>
 <w norm="unbedrängt">vnbedraͤngt</w>
 <w norm="und">vnd</w>
 <w norm="unverhindert">vnuerhindert</w>
</s>
<w norm="Teil">Theyll</w>
<w norm="Freude">Frewde</w>
orig (original) gives the original string or is the empty string when the element does not appear in the source text.
Status Optional
Datatype teidata.text

Example from a language documentation project of the Mixtepec-Mixtec language (ISO 639-3: 'mix'). This is a use case where speakers spell something incorrectly but we would like to preserve it for any number of reasons, the use of orig is essential and could have uses for both the speaker to see past mistakes, researchers to get insight into how untrained speakers write their language instinctually (in contrast to prescribed convention), etc.:

<w orig="ntsa sia'i">ntsasia'i</w>

Example from the EarlyPrint project. Fragment of text where obvious errors have been corrected but the original forms remain recorded:

<w lemma="he" pos="pns"
 xml:id="b1afj-003-a-0950">he</w>
<w lemma="have" pos="vvz"
 xml:id="b1afj-003-a-0960">hath</w>
<w lemma="bring" pos="vvn"
 xml:id="b1afj-003-a-0970">brought</w>
<w lemma="forth" orig="sorth" pos="av"
 xml:id="b1afj-003-a-0980">forth</w>

An example from the EarlyPrint project showing the use of both norm and orig. The orig attribute preserves the original version (sometimes with spelling errors, often with printer abbreviations), the element content resolves printer abbreviations but retains the original orthography, and the norm attribute holds normalized values:

<w lemma="commandment" norm="commandment"
 orig="commandemēt" pos="n1" xml:id="b9avr-018-a-7720">commandement</w>
Note

It needs to be stressed that the two attributes in this class are meant for strictly lexicographic and linguistic uses, and not for editorial interventions. For the latter, the mechanism based on choice, orig, and <reg> needs to be employed.

att.linguistic

att.linguistic provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically w and <pc> in the analysis module. [18.4.2. Lightweight Linguistic Annotation]
Module analysis
Members w
Attributes
lemma provides a lemma (base form) for the word, typically uninflected and serving both as an identifier (e.g. in dictionary contexts, as a headword), and as a basis for potential inflections.
Status Optional
Datatype teidata.text
<w lemma="wife">wives</w>
<w lemma="Arznei">Artzeneyen</w>
lemmaRef provides a pointer to a definition of the lemma for the word, for example in an online lexicon.
Status Optional
Datatype teidata.pointer
<w lemma="hit"
 lemmaRef="http://www.example.com/lexicon/hitvb.xml" type="verb">hitt<m type="suffix">ing</m>
</w>
pos (part of speech) indicates the part of speech assigned to a token (i.e. information on whether it is a noun, adjective, or verb), usually according to some official reference vocabulary (e.g. for German: STTS, for English: CLAWS, for Polish: NKJP, etc.).
Status Optional
Datatype teidata.text

The German sentence ‘Wir fahren in den Urlaub.’ tagged with the Stuttgart-Tuebingen-Tagset (STTS).

<s>
 <w pos="PPER">Wir</w>
 <w pos="VVFIN">fahren</w>
 <w pos="APPR">in</w>
 <w pos="ART">den</w>
 <w pos="NN">Urlaub</w>
 <w pos="$.">.</w>
</s>

The English sentence ‘We're going to Brazil.’ tagged with the CLAWS-5 tagset, arranged inline (with significant whitespace).

<p><w pos="PNP">We</w><w pos="VBB">'re</w> <w pos="VVG">going</w> <w pos="PRP">to</w> <w pos="NP0">Brazil</w><pc pos="PUN">.</pc></p>         

The English sentence ‘We're going on vacation to Brazil for a month!’ tagged with the CLAWS-7 tagset and arranged sequentially.

<p>
 <w pos="PPIS2">We</w>
 <w pos="VBR">'re</w>
 <w pos="VVG">going</w>
 <w pos="II">on</w>
 <w pos="NN1">vacation</w>
 <w pos="II">to</w>
 <w pos="NP1">Brazil</w>
 <w pos="IF">for</w>
 <w pos="AT1">a</w>
 <w pos="NNT1">month</w>
 <pc pos="!">!</pc>
</p>
msd (morphosyntactic description) supplies morphosyntactic information for a token, usually according to some official reference vocabulary (e.g. for German: STTS-large tagset; for a feature description system designed as (pragmatically) universal, see Universal Features).
Status Optional
Datatype teidata.text
<ab>
 <w msd="1.Pl.*.Nom" pos="PPER">Wir</w>
 <w msd="1.Pl.Pres.Ind" pos="VVFIN">fahren</w>
 <w msd="--" pos="APPR">in</w>
 <w msd="Def.Masc.Akk.Sg" pos="ART">den</w>
 <w msd="Masc.Akk.Sg" pos="NN">Urlaub</w>
 <pc msd="--" pos="$.">.</pc>
</ab>
join when present, provides information on whether the token in question is adjacent to another, and if so, on which side.
Status Optional
Datatype teidata.text
Legal values are:
no
the token is not adjacent to another
left
there is no whitespace on the left side of the token
right
there is no whitespace on the right side of the token
both
there is no whitespace on either side of the token
overlap
the token overlaps with another; other devices (specifying the extent and the area of overlap) are needed to more precisely locate this token in the character stream

The example below assumes that the lack of whitespace is marked redundantly, by using the appropriate values of join.

<s>
 <pc join="right">"</pc>
 <w join="left">Friends</w>
 <w>will</w>
 <w>be</w>
 <w join="right">friends</w>
 <pc join="both">.</pc>
 <pc join="left">"</pc>
</s>

Note that a project may make a decision to only indicate lack of whitespace in one direction, or do that non-redundantly. The existing proposal is the broadest possible, on the assumption that we adopt the "streamable view", where all the information on the current element needs to be represented locally.

The English sentence ‘We're going on vacation.’ tagged with the CLAWS-5 tagset, arranged sequentially, tagged on the assumption that only the lack of the preceding whitespace is indicated.

<p>
 <w pos="PNP">We</w>
 <w join="left" pos="VBB">'re</w>
 <w pos="VVG">going</w>
 <w pos="PRP">on</w>
 <w pos="NN1">vacation</w>
 <pc join="left" pos="PUN">.</pc>
</p>
Note

The definition of this attribute is adapted from ISO MAF (Morpho-syntactic Annotation Framework), ISO 24611:2012.
Note

These attributes make it possible to encode simple language corpora and to add a layer of linguistic information to any tokenized resource. See section 18.4.2. Lightweight Linguistic Annotation for discussion.

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

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]
Module tei
Members att.personal [eventName persName placeName] author editor pubPlace repository rs
Attributes
role may be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
Status Optional
Datatype 1–∞ occurrences of teidata.enumerated separated by whitespace
nymRef (reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
Status Optional
Datatype 1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Module tei
Members quote seg w
Attributes
notation names the notation used for the content of the element.
Status Optional
Datatype teidata.enumerated

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]
Module tei
Members eventName persName placeName
Attributes
full indicates whether the name component is given in full, as an abbreviation or simply as an initial.
Status Optional
Datatype teidata.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.
Status Optional
Datatype teidata.count

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]
Module tei
Members div label note noteGrp sp speaker
Attributes
place specifies where this item is placed.
Status Recommended
Datatype 1–∞ 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>

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]
Module tei
Members locus note noteGrp ptr ref term
Attributes
targetLang specifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
Status Optional
Datatype teidata.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.
target specifies the destination of the reference by supplying one or more URI References.
Status Optional
Datatype 1–∞ 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.
Status Optional
Datatype teidata.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.

att.ranging

att.ranging provides attributes for describing numerical ranges.
Module tei
Members att.dimensions [date ex gap supplied unclear]
Attributes
atLeast gives a minimum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
atMost gives a maximum estimated value for the approximate measurement.
Status Optional
Datatype teidata.numeric
min where the measurement summarizes more than one observation or a range, supplies the minimum value observed.
Status Optional
Datatype teidata.numeric
max where the measurement summarizes more than one observation or a range, supplies the maximum value observed.
Status Optional
Datatype teidata.numeric
confidence specifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
Status Optional
Datatype teidata.probability
Example
The MS. was lost in transmission by mail from
<del rend="overstrike">
 <gap atLeast="1" atMost="2"
  extent="one or two letters" reason="illegible" unit="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="currency" unit="USD">more
than $120m</measure> in aid to Ukrainians.

att.scope

att.scope provides attributes to describe, in general terms, the scope of an element’s application.
Module tei
Members att.handFeatures [handNote]
Attributes
scope indicates the scope of application of the element
Status Optional
Datatype teidata.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>

att.segLike

att.segLike provides attributes for elements used for arbitrary segmentation. [17.3. Blocks, Segments, and Anchors 18.1. Linguistic Segment Categories]
Module tei
Members seg w
Attributes
function (function) characterizes the function of the segment.
Status Optional
Datatype teidata.enumerated
Note

Attribute values will often vary depending on the type of element to which they are attached. For example, a <cl>, may take values such as coordinate, subject, adverbial etc. For a <phr>, such values as subject, predicate etc. may be more appropriate. Such constraints will typically be implemented by a project-defined customization.

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]
Module tei
Members biblStruct idno item list listBibl listChange listWit msDesc term witness
Attributes
sortKey supplies the sort key for this element in an index, list or group which contains it.
Status Optional
Datatype teidata.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.

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]
Module tei
Members cb lb pb
Attributes
spanTo indicates the end of a span initiated by the element bearing this attribute.
Status Optional
Datatype teidata.pointer
Schematron The @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.

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.6. 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]
Module tei
Members TEI altIdentifier anchor biblStruct cb change corr date div eventName gender idno label lb lg list listBibl listChange locus msDesc noteGrp pb persName placeName ptr quote ref rs seg table term text title w
Attributes
type characterizes the element in some sense, using any convenient classification scheme or typology.
Status Optional
Datatype teidata.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.
Status Optional
Datatype teidata.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 .

att.written

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

Schema kgk-minimal: Datatypes

teidata.certainty

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

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

teidata.count

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

Any positive integer value or zero is permitted

teidata.duration.iso

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

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

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

teidata.duration.w3c

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

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

For complete details, see the W3C specification.

teidata.enumerated

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

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

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

teidata.gender

teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character.
Module tei
Used by
Element:
Content model 
<content>
 <dataRef key="teidata.enumerated"/>
</content>
Declaration 
tei_teidata.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).

teidata.language

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

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

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

language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at 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.

teidata.name

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

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

teidata.numeric

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

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

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

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

teidata.outputMeasurement

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

teidata.pattern

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

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

teidata.point

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

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

teidata.pointer

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

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

teidata.probability

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

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

teidata.probCert

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

teidata.replacement

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

teidata.temporal.iso

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

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

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

teidata.temporal.w3c

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

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

teidata.text

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

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

teidata.truthValue

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

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

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

teidata.versionNumber

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

teidata.word

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

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

teidata.xpath

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

Any XPath expression using the syntax defined in 6.2. .

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

teidata.xTruthValue

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

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

Schema kgk-minimal: Macros

macro.paraContent

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

macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Module tei
Used by
author biblScope date distributor editor eventName extent foreign gender label persName placeName pubPlace publisher rs speaker term
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
Declaration 
tei_macro.phraseSeq =
   (
      text
    | tei_model.gLike
    | tei_model.attributable
    | tei_model.phrase
    | tei_model.global
   )*

macro.phraseSeq.limited

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

macro.specialPara

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

macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Module tei
Used by
ex
Content model 
<content>
 <alternate maxOccurs="unbounded"
  minOccurs="0">
  <textNode/>
  <classRef key="model.gLike"/>
 </alternate>
</content>
Declaration 
tei_macro.xtext = ( text | tei_model.gLike )*
 Home Feedback 
generated by Roma 5.0.1. Date: 2026-04-28