TEI in Libraries level 1

Best Practices for TEI in Libraries

Level 1: Fully Automated Conversion and Encoding

Setting

This is the level 1 portion of the Best Practices for TEI in Libraries. This document is not intended to stand alone, but rather to be considered in concert with the entire TEI in Libraries recommendations.

Table of contents

1. Level 1: Fully Automated Conversion and Encoding

1.1. Reference

1.2. Purpose

To create electronic text with the primary purpose of keyword searching and linking to page images. The primary advantage in using the TEI at this very strictly limited level of encoding is that a TEI header is attached to the text file.

1.3. Rationale

The text is subordinate to the page image, and is not intended to stand alone as an electronic text without accompanying page images. Level 1 texts are not intended to be adequate for textual analysis; they are more likely to be suited to the goals of a preservation unit or mass digitization initiative. These texts are meant to be a faithful representation of the appearance of the source document derived from OCR, providing the basis for subsequent encoding at Level 2 or higher of these Best Practices.

Level 1 is most suitable for projects with the following characteristics:

1.4. Workflow

Texts at Level 1 can be created and encoded by fully automated means. Page images are scanned and processed using OCR, but the text is generally left uncorrected (“dirty OCR”) and the XML is generated from the OCR output. If desired, such automated output can be enhanced by tagging individual page elements to indicate key textual features, such as a title page, front matter, or the start of a new chapter.

1.5. Element Recommendations for Level 1

<sourceDoc>[recommended] There should be only one element following the <teiHeader>, a single <sourceDoc> containing a raw transcription of the text of the source document.
<surface>[recommended] Defines a written surface as a two-dimensional coordinate space. There should be one <surface> for each encoded page, whether it is represented via a facsimile image file, a transcription, or, most likely, a textual representation obtained from OCR.
<zone>[optional] A two-dimensional region. May be used to divide a <surface> or <line> into two dimensional regions, e.g. a column, a dropped initial capital, or a word of interest. A <zone> may itself be divided into <line>s or <zone>s.
<line>[recommended] Contains text appearing in a single physical line on the page.

See section 3.8, Linking Between Encoded Texts and Images of Source Documents.

1.6. Level 1 Examples

1.6.1. Level 1 Alger Hiss document

<TEI xml:id="someid1" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader xml:lang="en"> <!-- header goes here -->  </teiHeader>  <sourceDoc xml:lang="en">   <surface n="113facs="00000001.tif"> <!-- uncorrected OCR for first page image begins here -->   <line>POINT VIII.</line>    <line>BECAUSE OF UNLAWFUL SURVEILLANCE, PETITIONER'S</line>    <line>CONVICTION SHOULD BE VACATED; ALTERNATIVELY,</line>    <line>DISCOVERY AND A HEARING SHOULD BE ORDERED.</line>    <line>The nature and extent of surveillance of Hiss, his</line>    <line>family and associates was not known at the time of trial by</line>    <line>the defense. Even now, with the release of some of the govern‐</line>    <line>ment documents concerning FBI investigative techniques regarding</line>    <line>Hiss, the full extent of surveillance -- wiretapping, mail open‐</line>    <line>ings, mail covers, physical surveillance, and other intrusive</line>    <line>techniques -- is still not 'clear. Nevertheless, it is apparent</line>    <line>that information gathered through the exploitation of unlawful</line>    <line>wiretaps and other illegal surveillance was used at trial and</line>    <line>consequently the conviction must be reversed. Alternatively,</line>    <line>further discovery and a hearing is essential to a fair deter‐</line>    <line>mination regarding these issues.</line>    <line>FBI surveillance of Hiss began in earnest in 1941 with</line>    <line>the institution of a mail cover on his incoming correspondence</line>    <line>at his home in connection with an FBI investigation of possible</line>    <line>Hatch Act violations. CN Ex. 98A. Another mail cover was placed</line>    <line/>    <line/>    <line>-113 -</line>    <line/>    <line/>      <!-- uncorrected OCR for first page image ends here -->   </surface>   <surface n="114facs="00000002.tif"> <!-- uncorrected OCR for second page image begins here -->   <line>on the Hiss mail in 1945, and at the same time the FBI obtained</line>    <line>toll call records from the Hiss residence Telephone for the</line>    <line>years 1943 and 1944 as well. CN Ex. 99. In September, 1945,</line>    <line>the FBI intercepted telegrams to Hiss as well. CN Ex. 100.</line>    <line>In late November, 1945, FBI surveillance of the Hiss</line>    <line>residence in Washington, D.C., escalated. For the third time,</line>    <line>a mail cover was instituted beginning on November 28, 1945,</line>    <line>which was continued at least until 1946. CN Ex. 101 at p. 70;</line>    <line>CN Ex. 102. Continuous physical surveillance of Hiss was begun</line>    <line>as well. CN Ex. 101 at p. 72. Although this twenty-four-hour</line>    <line>surveillance was discontinued on December 14, 1945, physical</line>    <line>surveillance was conducted frequently at various times until</line>    <line>September, 1947. CN Ex. 102; CN Ex. 103.</line>    <line>The most intrusive invasion of petitioner's rights</line>    <line>68/ Also before 1947, a letter from Priscilla Hiss addressed</line>    <line>to her son, Timothy Hobson, was intercepted and its contents</line>    <line>read. CN Ex. 100A at p. 167. In approximately March, 1947,</line>    <line>a letter from a Michael Greenberg addressed to petitioner re‐</line>    <line>garding an application for employment with the United Nations</line>    <line>was also intercepted, in a manner not revealed by the docu‐</line>    <line>ments. CN Ex. 100B</line>    <line/>    <line/>    <line>-114 -</line>    <line/>    <line/>    <line/>      <!-- uncorrected OCR for second page image ends here -->   </surface>   <surface n="115facs="00000003.tif"> <!-- uncorrected OCR for third page image begins here -->   <line>occurred from December 13, 1945 until the Hisses moved from</line>    <line>Washington, D.C. to New York City on September 13, 1947. A</line>    <line>"technical surveillance," -- a wiretap -- was placed on the Hiss</line>    <line>telephone at their residence on P Street-in Washington, D.C.</line>    <line>The logs of this surveillance constitute twenty-nine volumes</line>    <line>of FBI serials and are roughly 2,500 pages in length, in which</line>    <line>an enormous amount of information concerning the Hisses' per‐</line>    <line>sonal lives, relationships with friends and associates, and</line>    <line>habits is recorded.</line>    <line>The wiretap was installed following FBI Director Hoover's</line>    <line>application to the Attorney General for authorization, although</line>    <line>no written authorization appears in the documents released to</line>    <line>Hiss. The purpose of the application was to gather information</line>    <line>regarding Hiss' alleged contacts with Soviet espionage agents and</line>    <line>communists in government service, general allegations which had</line>    <line>been made by Elizabeth Bentley and Chambers.</line>    <line>As one would expect, the interception of every telephone</line>    <line>h9/ Hoover's initial request was answered by a note reques‐</line>    <line>ting information on Hiss. CN Ex. 104. Additional information</line>    <line>was furnished by letter dated November 30, 1945. CN Ex. 105.</line>    <line/>    <line/>    <line>-115 -</line>    <line/>    <line/>      <!-- uncorrected OCR for third page image ends here -->   </surface>  </sourceDoc> </TEI>

1.6.2. Level 1 Text with OCR Coordinates

<TEI xml:id="someid1a" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader xml:lang="en"> <!-- header goes here -->  </teiHeader>  <sourceDoc xml:lang="en">   <surface n="113facs="00000001.tif"    ulx="0uly="0lrx="2550lry="3300"> <!-- uncorrected OCR for first page image begins here -->   <zone type="print_spaceulx="407"     uly="40lrx="2525lry="3219">     <zone type="text_blockulx="1255"      uly="386lrx="1605lry="426">      <line type="text_lineulx="1256"       uly="387lrx="1604lry="425">       <zone type="wordulx="1256uly="390"        lrx="1411lry="425">POINT</zone>       <zone type="wordulx="1452uly="387"        lrx="1579lry="424">VIII</zone>       <zone type="wordulx="1592uly="408"        lrx="1604lry="418">.</zone>      </line>     </zone>     <zone type="text_blockulx="744"      uly="481lrx="2222lry="534">      <line type="text_lineulx="745"       uly="482lrx="2221lry="533">       <zone type="wordulx="745uly="498"        lrx="970lry="533">BECAUSE</zone>       <zone type="wordulx="1006uly="498"        lrx="1064lry="529">OF</zone>       <zone type="wordulx="1102uly="494"        lrx="1353lry="528">UNLAWFUL</zone>       <zone type="wordulx="1392uly="491"        lrx="1798lry="527">SURVEILLANCE,</zone>       <zone type="wordulx="1847uly="482"        lrx="2221lry="521">PETITIONER'S</zone>      </line>     </zone>     <zone type="text_blockulx="746"      uly="546lrx="2155lry="593">      <line type="text_lineulx="747"       uly="547lrx="2154lry="592">       <zone type="wordulx="748uly="556"        lrx="1068lry="592">CONVICTION</zone>       <zone type="wordulx="1103uly="555"        lrx="1291lry="588">SHOULD</zone>       <zone type="wordulx="1326uly="553"        lrx="1389lry="585">BE</zone>       <zone type="wordulx="1421uly="551"        lrx="1673lry="588">VACATED?</zone>       <zone type="wordulx="1712uly="547"        lrx="2154lry="584">ALTERNATIVELY,</zone>      </line>     </zone>     <zone type="text_blockulx="746"      uly="607lrx="2091lry="652">      <line type="text_lineulx="747"       uly="608lrx="2090lry="651">       <zone type="wordulx="747uly="617"        lrx="1037lry="651">DISCOVERY</zone>       <zone type="wordulx="1069uly="616"        lrx="1163lry="648">AND</zone>       <zone type="wordulx="1197uly="615"        lrx="1228lry="647">A</zone>       <zone type="wordulx="1262uly="612"        lrx="1488lry="647">HEARING</zone>       <zone type="wordulx="1522uly="610"        lrx="1712lry="643">SHOULD</zone>       <zone type="wordulx="1750uly="610"        lrx="1810lry="641">BE</zone>       <zone type="wordulx="1847uly="608"        lrx="2090lry="641">ORDERED.</zone>      </line>     </zone>     <zone type="text_blockulx="414"      uly="802lrx="2482lry="2190">      <line type="text_lineulx="741"       uly="803lrx="2345lry="848">       <zone type="wordulx="741uly="808"        lrx="833lry="844">The</zone>       <zone type="wordulx="870uly="809"        lrx="1059lry="843">nature</zone>       <zone type="wordulx="1099uly="807"        lrx="1191lry="842">and</zone>       <zone type="wordulx="1225uly="808"        lrx="1415lry="841">extent</zone>       <zone type="wordulx="1453uly="805"        lrx="1511lry="841">of</zone>       <zone type="wordulx="1551uly="804"        lrx="1930lry="840">surveillance</zone>       <zone type="wordulx="1968uly="805"        lrx="2027lry="839">of</zone>       <zone type="wordulx="2060uly="803"        lrx="2210lry="844">Hiss,</zone>       <zone type="wordulx="2255uly="803"        lrx="2345lry="839">his</zone>      </line>      <line type="text_lineulx="420"       uly="924lrx="2318lry="976">       <zone type="wordulx="420uly="930"        lrx="609lry="975">family</zone>       <zone type="wordulx="645uly="930"        lrx="740lry="965">and</zone>       <zone type="wordulx="777uly="927"        lrx="1092lry="965">associates</zone>       <zone type="wordulx="1128uly="938"        lrx="1221lry="964">was</zone>       <zone type="wordulx="1258uly="930"        lrx="1351lry="964">not</zone>       <zone type="wordulx="1386uly="928"        lrx="1547lry="962">known</zone>       <zone type="wordulx="1584uly="930"        lrx="1645lry="962">at</zone>       <zone type="wordulx="1681uly="927"        lrx="1769lry="962">the</zone>       <zone type="wordulx="1809uly="925"        lrx="1932lry="961">time</zone>       <zone type="wordulx="1969uly="927"        lrx="2027lry="962">of</zone>       <zone type="wordulx="2066uly="925"        lrx="2219lry="961">trial</zone>       <zone type="wordulx="2253uly="926"        lrx="2318lry="971">by</zone>      </line>          <!-- encoded text continues -->     </zone>    </zone>   </surface>    <!-- encoded text continues -->  </sourceDoc> </TEI>

1.7. Specification

1.7.1. Elements

1.7.1.1. <prefixDef>
<prefixDef>
Modulederived-module-bptl-L1
AttributesAttributes
ident
StatusRequired
Legal values are:
bptl
(Best Practices for TEI in Libraries)
matchPattern
StatusRequired
Legal values are:
L([1-5])-v(\d+\.\d+\.\d+[aαβb]?)
This regular expression matches BPTL version numbers like ‘L1-v1.0.2a’.
replacementPattern
StatusRequired
Suggested values include:
http://www.tei-c.org/SIG/Libraries/teiinlibraries/$2/
Contained by
May containEmpty element
1.7.1.2. <TEI>
<TEI> (TEI document) contains a single TEI-in-Libraries level 1 document, comprising a TEI header and a text, either in isolation or as part of a <teiCorpus> element. [4. Default Text Structure 15.1. Varieties of Composite Text]
Moduletextstructure — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
versionspecifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

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

Contained by
May contain
header: teiHeader
transcr: sourceDoc
Note

This element is required. The TEI namespace should be specified on this element, e.g. <TEI xmlns="http://www.tei-c.org/ns/1.0">.

ExampleFor technical reasons, the TEI namespace is not displayed in examples. However, a TEI namespace declaration is required. It is typically given once on the TEI root element, e.g. <TEI xmlns="http://www.tei-c.org/ns/1.0">.
<TEI xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>A Short Level 1 Document</title>    </titleStmt>    <publicationStmt>     <p>Only published as an example.</p>    </publicationStmt>    <sourceDesc>     <p>Since this is an example, it doesn't really have a source</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <sourceDoc>   <surface>    <line>This is almost the shortest TEI document imaginable.</line>   </surface>  </sourceDoc> </TEI>
Schematron
<s:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <s:ns prefix="xs"  uri="http://www.w3.org/2001/XMLSchema"/>
Schematron
<s:ns prefix="rng"  uri="http://relaxng.org/ns/structure/1.0"/>
Content model
<content>
 <elementRef key="teiHeader"/>
 <elementRef key="sourceDoc"/>
</content>
    
Schema Declaration
element TEI
{
   L1_att.global.attributes,
   attribute version { text }?,
   L1_teiHeader,
   L1_sourceDoc
}
1.7.1.3. <abbr>
<abbr> (abbreviation) contains an abbreviation of any sort. [3.5.5. Abbreviations and Their Expansions]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
typeallows the encoder to classify the abbreviation according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
suspension
the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
contraction
the abbreviation omits some letter(s) in the middle.
brevigraph
the abbreviation comprises a special symbol or mark.
superscription
the abbreviation includes writing above the line.
acronym
the abbreviation comprises the initial letters of the words of a phrase.
title
the abbreviation is for a title of address (Dr, Ms, Mr, …)
organization
the abbreviation is for the name of an organization.
geographic
the abbreviation is for a geographic name.
Note

The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see [[undefined PETTY]]

Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Note

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

Example
<choice>  <expan>North Atlantic Treaty Organization</expan>  <abbr cert="low">NorATO</abbr>  <abbr cert="high">NATO</abbr>  <abbr cert="highxml:lang="fr">OTAN</abbr> </choice>
Example
<choice>  <abbr>SPQR</abbr>  <expan>senatus populusque romanorum</expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element abbr
{
   L1_att.global.attributes,
   attribute type { text }?,
   L1_macro.phraseSeq
}
1.7.1.4. <addrLine>
<addrLine> (address line) contains one line of a postal address. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: address
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Note

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

Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL</addrLine>  <addrLine>60680 USA</addrLine> </address>
Example
<addrLine>  <ref target="tel:+1-201-555-0123">(201) 555 0123</ref> </addrLine>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element addrLine { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.5. <address>
<address> contains a postal address, for example of a publisher, an organization, or an individual. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Note

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

ExampleUsing just the elements defined by the core module, an address could be represented as follows:
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <name>Bologna</name>  <name>Italy</name> </address>
ExampleWhen a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic <name>:
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <settlement>Bologna</settlement>  <country>Italy</country> </address>
Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL 60680</addrLine>  <addrLine>USA</addrLine> </address>
Example
<address>  <country key="FR"/>  <settlement type="city">Lyon</settlement>  <postCode>69002</postCode>  <district type="arrondissement">IIème</district>  <district type="quartier">Perrache</district>  <street>   <num>30</num>, Cours de Verdun</street> </address>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.addrPart"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element address
{
   L1_att.global.attributes,
   ( L1_model.global*, ( L1_model.addrPart, L1_model.global* )+ )
}
1.7.1.6. <analytic>
<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.11.2.1. Analytic, Monographic, and Series Levels]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
May contain
Note

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

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

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope>377–380</biblScope>  </monogr> </biblStruct>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <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
{
   L1_att.global.attributes,
   (
      L1_author
    | L1_editor
    | L1_respStmt
    | L1_title
    | L1_model.ptrLike
    | L1_date
    | L1_textLang
    | L1_idno
    | L1_availability
   )*
}
1.7.1.7. <appInfo>
<appInfo> (application information) records information about an application which has edited the TEI file. [2.3.10. The Application Information Element]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: encodingDesc
May contain
header: application
Example
<appInfo>  <application version="1.24ident="Xaira">   <label>XAIRA Indexer</label>   <ptr target="#P1"/>  </application> </appInfo>
Content model
<content>
 <classRef key="model.applicationLike"
  minOccurs="1" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element appInfo { L1_att.global.attributes, L1_model.applicationLike+ }
1.7.1.8. <application>
<application> provides information about an application which has acted upon the document. [2.3.10. The Application Information Element]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
identsupplies an identifier for the application, independent of its version number or display name.
StatusRequired
Datatypeteidata.name
versionsupplies a version number for the application, independent of its identifier or display name.
StatusRequired
Datatypeteidata.versionNumber
Member of
Contained by
header: appInfo
May contain
core: label p ptr ref
Example
<appInfo>  <application version="1.5"   ident="ImageMarkupTool1notAfter="2006-06-01">   <label>Image Markup Tool</label>   <ptr target="#P1"/>   <ptr target="#P2"/>  </application> </appInfo>
This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two <ptr> elements.
Content model
<content>
 <sequence>
  <classRef key="model.labelLike"
   minOccurs="1" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.ptrLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element application
{
   L1_att.global.attributes,
   L1_att.typed.attributes,
   L1_att.datable.attributes,
   attribute ident { text },
   attribute version { text },
   ( L1_model.labelLike+, ( L1_model.ptrLike* | L1_model.pLike* ) )
}
1.7.1.9. <att>
<att> (attribute) contains the name of an attribute appearing within running text. [22. Documentation Elements]
Moduletagdocs — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
schemesupplies an identifier for the scheme in which this name is defined.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
TEI
(text encoding initiative) this attribute is part of the TEI scheme.[Default]
DBK
(docbook) this attribute is part of the Docbook scheme.
XX
(unknown) this attribute is part of an unknown scheme.
imaginary
the attribute is from a non-existent scheme, for illustrative purposes only
XHTML
the attribute is part of the XHTML language
XML
the attribute is part of the XML language
XI
the attribute is defined in the xInclude schema
Member of
Contained by
May containEmpty element
Note

As an alternative to using scheme attribute a namespace prefix may be used. Where both scheme and a prefix are used, the prefix takes precedence.

Example
<p>The TEI defines several <soCalled>global</soCalled> attributes; their names include <att>xml:id</att>, <att>rend</att>, <att>xml:lang</att>, <att>n</att>, <att>xml:space</att>, and <att>xml:base</att>; <att scheme="XX">type</att> is not amongst them.</p>
Content model
<content>
 <dataRef key="teidata.name"/>
</content>
    
Schema Declaration
element att
{
   L1_att.global.attributes,
   attribute scheme { text }?,
   teidata.name
}
1.7.1.10. <author>
<author> in a bibliographic reference, contains the name (typically encoded as <name>, <persName>, or <orgName>) of the author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
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>  <orgName>British Broadcasting Corporation</orgName> </author>
Example
<author>  <persName ref="#mdalmau.cny">Michelle Dalmau</persName> </author>
Example
<author>  <name>Matthew Gibson</name> </author>
Example
<author>anonymous</author>
Example
<author>unknown</author>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element author { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.11. <availability>
<availability> supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
statussupplies a code identifying the current availability of the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
free
the text is freely available.
unknown
the status of the text is unknown.
restricted
the text is not freely available.
Member of
Contained by
May contain
core: p
header: licence
Note

A consistent format should be adopted

Example
<availability status="restricted">  <p>Available for academic research purposes only.</p> </availability> <availability status="free">  <p>In the public domain</p> </availability> <availability status="restricted">  <p>Available under licence from the publishers.</p> </availability>
Example
<availability>  <licence target="http://opensource.org/licenses/MIT">   <p>The MIT License      applies to this document.</p>   <p>Copyright (C) 2011 by The University of Victoria</p>   <p>Permission is hereby granted, free of charge, to any person obtaining a copy      of this software and associated documentation files (the "Software"), to deal      in the Software without restriction, including without limitation the rights      to use, copy, modify, merge, publish, distribute, sublicense, and/or sell      copies of the Software, and to permit persons to whom the Software is      furnished to do so, subject to the following conditions:</p>   <p>The above copyright notice and this permission notice shall be included in      all copies or substantial portions of the Software.</p>   <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR      IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,      FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE      AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER      LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,      OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN      THE SOFTWARE.</p>  </licence> </availability>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element availability
{
   L1_att.global.attributes,
   attribute status { "free" | "unknown" | "restricted" }?,
   ( L1_model.availabilityPart | L1_model.pLike )+
}
1.7.1.12. <bibl>
<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Note

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

Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
<bibl>  <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher>  <date>1968</date>. </bibl>
Example
<bibl type="articlesubtype="book_chapter"  xml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element bibl
{
   L1_att.global.attributes,
   L1_att.typed.attributes,
   L1_att.sortable.attributes,
   L1_att.docStatus.attributes,
   (
      text
    | L1_model.gLike
    | L1_model.highlighted
    | L1_model.pPart.data
    | L1_model.pPart.edit
    | L1_model.segLike
    | L1_model.ptrLike
    | L1_model.biblPart
    | L1_model.global
   )*
}
1.7.1.13. <biblScope>
<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.citing (@unit, @from, @to)
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
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 unit="pagefrom="12to="34"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element biblScope
{
   L1_att.global.attributes,
   L1_att.citing.attributes,
   L1_macro.phraseSeq
}
1.7.1.14. <biblStruct>
<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.sortable (@sortKey) att.docStatus (@status)
Member of
Contained by
May contain
Example
<biblStruct>  <monogr>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <edition>first edition</edition>   <imprint>    <publisher>Yale University Press</publisher>    <pubPlace>New Haven and London</pubPlace>    <date>1990</date>   </imprint>  </monogr> </biblStruct>
Content model
<content>
 <sequence>
  <elementRef key="analytic" minOccurs="0"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="monogr"/>
   <elementRef key="series" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element biblStruct
{
   L1_att.global.attributes,
   L1_att.typed.attributes,
   L1_att.sortable.attributes,
   L1_att.docStatus.attributes,
   (
      L1_analytic*,
      ( L1_monogr, L1_series* )+,
      ( L1_model.noteLike | L1_model.ptrLike | L1_relatedItem | L1_citedRange )*
   )
}
1.7.1.15. <change>
<change> documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Identifying Changes and Revisions]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.docStatus (@status) att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.datable (@calendar, @period) att.datable.w3c (when, @notBefore, @notAfter, @from, @to) att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)
whoindicates the person, or group of people, to whom the element content is ascribed.
Derived fromatt.ascribed
StatusRequired
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
Derived fromatt.datable.w3c
StatusRequired
Datatypeteidata.temporal.w3c
targetpoints to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
header: revisionDesc
May contain
Note

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

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

Example
<titleStmt>  <title> ... </title>  <editor xml:id="LDB">Lou Burnard</editor>  <respStmt xml:id="BZ">   <resp>copy editing</resp>   <name>Brett Zamir</name>  </respStmt> </titleStmt> <!-- ... --> <revisionDesc status="published">  <change who="#BZwhen="2008-02-02"   status="public">Finished chapter 23</change>  <change who="#BZwhen="2008-01-02"   status="draft">Finished chapter 2</change>  <change n="P2.2when="1991-12-21"   who="#LDB">Added examples to section 3</change>  <change when="1991-11-11who="#MSM">Deleted chapter 10</change> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange>    <change xml:id="DRAFT1">First draft in pencil</change>    <change xml:id="DRAFT2"     notBefore="1880-12-09">First revision, mostly        using green ink</change>    <change xml:id="DRAFT3"     notBefore="1881-02-13">Final corrections as        supplied to printer.</change>   </listChange>  </creation> </profileDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element change
{
   L1_att.datable.attribute.calendar,
   L1_att.datable.attribute.period,
   L1_att.datable.w3c.attribute.notBefore,
   L1_att.datable.w3c.attribute.notAfter,
   L1_att.datable.w3c.attribute.from,
   L1_att.datable.w3c.attribute.to,
   L1_att.datable.custom.attribute.when-custom,
   L1_att.datable.custom.attribute.notBefore-custom,
   L1_att.datable.custom.attribute.notAfter-custom,
   L1_att.datable.custom.attribute.from-custom,
   L1_att.datable.custom.attribute.to-custom,
   L1_att.datable.custom.attribute.datingPoint,
   L1_att.datable.custom.attribute.datingMethod,
   L1_att.docStatus.attributes,
   L1_att.global.attributes,
   L1_att.typed.attributes,
   attribute who { list { + } },
   attribute when { text },
   attribute target { list { + } }?,
   L1_macro.specialPara
}
1.7.1.16. <choice>
<choice> groups a number of alternative encodings for the same point in a text. [3.4. Simple Editorial Changes]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Note

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

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

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

ExampleAn American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.
<p>Lastly, That, upon his solemn oath to observe all the above articles, the said man-mountain shall have a daily allowance of meat and drink sufficient for the support of <choice>   <sic>1724</sic>   <corr>1728</corr>  </choice> of our subjects, with free access to our royal person, and other marks of our <choice>   <orig>favour</orig>   <reg>favor</reg>  </choice>.</p>
Content model
<content>
 <alternate minOccurs="2"
  maxOccurs="unbounded">
  <classRef key="model.choicePart"/>
  <elementRef key="choice"/>
 </alternate>
</content>
    
Schema Declaration
element choice
{
   L1_att.global.attributes,
   ( L1_model.choicePart | L1_choice )+
}
1.7.1.17. <cit>
<cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 9.3.5.1. Examples]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type)
Member of
Contained by
May contain
Example
<cit>  <quote>and the breath of the whale is frequently attended with such an insupportable smell,    as to bring on disorder of the brain.</quote>  <bibl>Ulloa's South America</bibl> </cit>
Example
<entry>  <form>   <orth>horrifier</orth>  </form>  <cit type="translationxml:lang="en">   <quote>to horrify</quote>  </cit>  <cit type="example">   <quote>elle était horrifiée par la dépense</quote>   <cit type="translationxml:lang="en">    <quote>she was horrified at the expense.</quote>   </cit>  </cit> </entry>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.qLike"/>
  <classRef key="model.egLike"/>
  <classRef key="model.biblLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.global"/>
  <classRef key="model.entryPart"/>
 </alternate>
</content>
    
Schema Declaration
element cit
{
   L1_att.global.attributes,
   L1_att.typed.attributes,
   (
      L1_model.qLike
    | L1_model.egLike
    | L1_model.biblLike
    | L1_model.ptrLike
    | L1_model.global
    | L1_model.entryPart
   )+
}
1.7.1.18. <citedRange>
<citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.11.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@target) att.citing (@unit, @from, @to)
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
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>.

Example
<citedRange>pp 12–13</citedRange> <citedRange unit="pagefrom="12to="13"/> <citedRange unit="volume">II</citedRange> <citedRange unit="page">12</citedRange>
Example
<bibl>  <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.    4-5</citedRange> </bibl>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element citedRange
{
   L1_att.global.attributes,
   L1_att.pointing.attributes,
   L1_att.citing.attributes,
   L1_macro.phraseSeq
}
1.7.1.19. <classCode>
<classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
schemeidentifies the classification system in use, as defined by, e.g. a <taxonomy> element, or some other resource.
StatusRequired
Datatypeteidata.pointer
Contained by
core: imprint
header: textClass
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Example
<classCode scheme="http://www.udc.org">410</classCode>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element classCode
{
   L1_att.global.attributes,
   attribute scheme { text },
   L1_macro.phraseSeq.limited
}
1.7.1.20. <classDecl>
<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: encodingDesc
May contain
header: taxonomy
Example
<classDecl>  <taxonomy xml:id="LCSH">   <bibl>Library of Congress Subject Headings</bibl>  </taxonomy> </classDecl> <!-- ... --> <textClass>  <keywords scheme="#LCSH">   <term>Political science</term>   <term>United States -- Politics and government —      Revolution, 1775-1783</term>  </keywords> </textClass>
Content model
<content>
 <elementRef key="taxonomy" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element classDecl { L1_att.global.attributes, L1_taxonomy+ }
1.7.1.21. <correction>
<correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
statusindicates the degree of correction applied to the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
high
the text has been thoroughly checked and proofread.
medium
the text has been checked at least once.
low
the text has not been checked.
unknown
the correction status of the text is unknown.
methodindicates the method adopted to indicate corrections within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
corrections have been made silently[Default]
markup
corrections have been represented using markup
Contained by
May contain
core: p
Note

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

Example
<correction>  <p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user    defined dictionary of 500 extra words taken from Chambers Twentieth Century    Dictionary.</p> </correction>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element correction
{
   L1_att.global.attributes,
   attribute status { "high" | "medium" | "low" | "unknown" }?,
   attribute method { "silent" | "markup" }?,
   L1_model.pLike+
}
1.7.1.22. <date>
<date> contains a date in any format. [3.5.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 15.2.3. The Setting Description 13.3.6. Dates and Times]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.typed (@type)
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element date
{
   L1_att.global.attributes,
   L1_att.datable.attributes,
   L1_att.dimensions.attributes,
   L1_att.typed.attributes,
   ( text | L1_model.gLike | L1_model.phrase | L1_model.global )*
}
1.7.1.23. <distributor>
<distributor> supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
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 { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.24. <edition>
<edition> describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: bibl monogr
header: editionStmt
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Example
<edition>First edition <date>Oct 1990</date> </edition> <edition n="S2">Students' edition</edition>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element edition { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.25. <editionStmt>
<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: fileDesc
May contain
Example
<editionStmt>  <edition n="S2">Students' edition</edition>  <respStmt>   <resp>Adapted by </resp>   <name>Elizabeth Kirk</name>  </respStmt> </editionStmt>
Example
<editionStmt>  <p>First edition, <date>Michaelmas Term, 1991.</date>  </p> </editionStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="edition"/>
   <classRef key="model.respLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element editionStmt
{
   L1_att.global.attributes,
   ( L1_model.pLike+ | ( L1_edition, L1_model.respLike* ) )
}
1.7.1.26. <editor>
<editor> contains the name (typically encoded as <name>, <persName>, or <orgName>) of an individual, institution, or organization acting as editor. [3.11.2.2. Titles, Authors, and Editors]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
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>  <persName ref="names.xml#khawkins.tvt">Kevin Hawkins</persName> </editor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element editor { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.27. <editorialDecl>
<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: encodingDesc
May contain
Example
<editorialDecl>  <p>Metadata in the TEI header comes from an AACR2-conformant    record, translated to TEI via the <name type="software">Thutmose I</name> program.</p>  <p>Content originally generated by <name type="software">c-n-rite</name> OCR software, then the    needed TEI encoding put in place with <name type="software">cnr2tei.xslt</name>.</p>  <correction method="markupstatus="low"/>  <normalization method="silent">   <p>Spacing between words and the following      punctuation mark has been removed. Spacing      between words has generally been regularized to      one space.</p>  </normalization>  <normalization method="markup">   <p>Distances expressed in imperial units in the      source have been normalized to the metric system      using the attributes of the <gi>measure</gi>      element.</p>  </normalization>  <hyphenation eol="all">   <p>All hyphens in source document encoded as U+2010.</p>  </hyphenation> </editorialDecl>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="correction"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="hyphenation"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="normalization"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="punctuation"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="quotation" minOccurs="0"
   maxOccurs="1"/>
  <classRef key="model.pLike" minOccurs="0"
   maxOccurs="7"/>
 </sequence>
</content>
    
Schema Declaration
element editorialDecl
{
   L1_att.global.attributes,
   (
      L1_correction?,
      L1_hyphenation?,
      L1_normalization?,
      L1_punctuation?,
      L1_quotation?,
      (
         L1_model.pLike?,
         (
            L1_model.pLike,
            (
               L1_model.pLike,
               (
                  L1_model.pLike,
                  (
                     L1_model.pLike,
                     ( L1_model.pLike, ( L1_model.pLike, L1_model.pLike? )? )?
                  )?
               )?
            )?
         )?
      )
   )
}
1.7.1.28. <email>
<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.5.2. Addresses]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Note

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

Example
<email>membership@tei-c.org</email>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element email { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.29. <emph>
<emph> (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Example
You took the car and did <emph>what</emph>?!!
Example
<q>What it all comes to is this,</q> he said. <q>  <emph>What    does Christopher Robin do in the morning nowadays?</emph> </q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element emph { L1_att.global.attributes, L1_macro.paraContent }
1.7.1.30. <encodingDesc>
<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: teiHeader
May contain
Example
<encodingDesc>  <p>Basic encoding, capturing lexical information only. All    hyphenation, punctuation, and variant spellings normalized. No    formatting or layout information preserved.</p> </encodingDesc>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="projectDesc"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="schemaRef" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="editorialDecl"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="tagsDecl" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="classDecl" minOccurs="0"
   maxOccurs="1"/>
  <elementRef key="samplingDecl"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="appInfo" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="listPrefixDef"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element encodingDesc
{
   L1_att.global.attributes,
   (
      L1_projectDesc?,
      L1_schemaRef*,
      L1_editorialDecl?,
      L1_tagsDecl,
      L1_classDecl?,
      L1_samplingDecl?,
      L1_appInfo*,
      L1_listPrefixDef+
   )
}
1.7.1.31. <expan>
<expan> (expansion) contains the expansion of an abbreviation. [3.5.5. Abbreviations and Their Expansions]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Note

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

Note

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

Example
The address is Southmoor <choice>  <expan>Road</expan>  <abbr>Rd</abbr> </choice>
Example
<choice xml:lang="la">  <abbr>Imp</abbr>  <expan>Imp<ex>erator</ex>  </expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element expan { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.32. <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.11.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: bibl monogr
header: fileDesc
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Example
<extent>3200 sentences</extent> <extent>between 10 and 20 Mb</extent> <extent>ten 3.5 inch high density diskettes</extent>
ExampleThe <measure> element may be used to supply normalised or machine tractable versions of the size or sizes concerned.
<extent>  <measure unit="MiBquantity="4.2">About four megabytes</measure>  <measure unit="pagesquantity="245">245 pages of source    material</measure> </extent>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element extent { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.33. <facsimile>
<facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles]
Moduletranscr — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
May contain
transcr: surface
Example
<facsimile>  <graphic url="page1.png"/>  <surface>   <graphic url="page2-highRes.png"/>   <graphic url="page2-lowRes.png"/>  </surface>  <graphic url="page3.png"/>  <graphic url="page4.png"/> </facsimile>
Example
<facsimile>  <surface ulx="0uly="0lrx="200lry="300">   <graphic url="Bovelles-49r.png"/>  </surface> </facsimile>
Content model
<content>
 <elementRef key="surface" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element facsimile { L1_att.global.attributes, L1_surface+ }
1.7.1.34. <fileDesc>
<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: teiHeader
May contain
Note

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

Example
<fileDesc>  <titleStmt>   <title>The shortest possible TEI document</title>  </titleStmt>  <publicationStmt>   <p>Distributed as part of TEI P5</p>  </publicationStmt>  <sourceDesc>   <p>No print source exists: this is an original digital text</p>  </sourceDesc> </fileDesc>
Content model
<content>
 <sequence>
  <sequence>
   <elementRef key="titleStmt"/>
   <elementRef key="editionStmt"
    minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="publicationStmt"/>
   <elementRef key="seriesStmt"
    minOccurs="0"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element fileDesc
{
   L1_att.global.attributes,
   (
      (
         L1_titleStmt,
         L1_editionStmt?,
         L1_extent?,
         L1_publicationStmt,
         L1_seriesStmt?,
         L1_notesStmt?
      ),
      L1_sourceDesc+
   )
}
1.7.1.35. <foreign>
<foreign> identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
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 { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.36. <gi>
<gi> (element name) contains the name (generic identifier) of an element. [22. Documentation Elements 22.5. Element Specifications]
Moduletagdocs — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
schemesupplies the name of the scheme in which this name is defined.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
TEI
this element is part of the TEI scheme.[Default]
DBK
(docbook) this element is part of the Docbook scheme.
XX
(unknown) this element is part of an unknown scheme.
Schematron
this element is from Schematron.
HTML
this element is from the HTML scheme.
Member of
Contained by
May containEmpty element
Example
<p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the <gi scheme="DBK">listItem</gi> element.</p>
This example shows the use of both a namespace prefix and the schema attribute as alternative ways of indicating that the <gi> in question is not a TEI element name: in practice only one method should be adopted.
Content model
<content>
 <dataRef key="teidata.name"/>
</content>
    
Schema Declaration
element gi
{
   L1_att.global.attributes,
   attribute scheme { text }?,
   teidata.name
}
1.7.1.37. <gloss>
<gloss> identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.3.4. Terms, Glosses, Equivalents, and Descriptions 22.4.1. Description of Components]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.translatable (@versionDate) att.typed (@type) att.pointing (@target) att.cReferencing (@cRef)
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Note

The target and cRef attributes are mutually exclusive.

Example
We may define <term xml:id="tdpvrend="sc">discoursal point of view</term> as <gloss target="#tdpv">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element gloss
{
   L1_att.global.attributes,
   L1_att.translatable.attributes,
   L1_att.typed.attributes,
   L1_att.pointing.attributes,
   L1_att.cReferencing.attributes,
   L1_macro.phraseSeq
}
1.7.1.38. <hyphenation>
<hyphenation> summarizes the way in which hyphenation in a source text has been treated in an encoded version of it. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
eol(end-of-line) indicates whether or not end-of-line hyphenation has been retained in a text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
all
all end-of-line hyphenation has been retained, even though the lineation of the original may not have been.
some
end-of-line hyphenation has been retained in some cases.[Default]
hard
all soft end-of-line hyphenation has been removed: any remaining end-of-line hyphenation should be retained.
none
all end-of-line hyphenation has been removed: any remaining hyphenation occurred within the line.
Contained by
May contain
core: p
derived-module-bptl-L1: p
Example
<hyphenation eol="some">  <p>End-of-line hyphenation silently removed where appropriate</p> </hyphenation>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="hyphenation-para"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="p" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1" maxOccurs="1">
   <elementRef key="p" minOccurs="1"
    maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element hyphenation
{
   L1_att.global.attributes,
   attribute eol { "all" | "some" | "hard" | "none" }?,
   ( ( L1_hyphenation-para, L1_p* ) | ( L1_p+ ) )
}
1.7.1.39. <p>
<p>
Modulederived-module-bptl-L1
Contained by
header: hyphenation
May containEmpty element
Content model
<content>
 <valList type="closed">
  <valItem ident="All hyphens in source document encoded as U+2010."/>
  <valItem ident="All hyphens in source document encoded as U+002D."/>
  <valItem ident="Hyphens in source document encoded as U+2010. Line-ending hyphens 
 differentiated with @break of immediately following <lb> element."/>
  <valItem ident="Hyphens in source document encoded as U+002D. Line-ending hyphens 
 differentiated with @break of immediately following <lb> element."/>
  <valItem ident="Hyphens in source document encoded as U+2010 inside a <pc>. Line-ending 
 hyphens differentiated with @force of the <pc> and @break of immediately 
 following <lb> element."/>
  <valItem ident="Hyphens in source document encoded as U+202D inside a <pc>. Line-ending 
 hyphens differentiated with @force of the <pc> and @break of immediately 
 following <lb> element."/>
 </valList>
</content>
    
Legal values are:
All hyphens in source document encoded as U+2010.
All hyphens in source document encoded as U+002D.
Hyphens in source document encoded as U+2010. Line-ending hyphens differentiated with @break of immediately following <lb> element.
Hyphens in source document encoded as U+002D. Line-ending hyphens differentiated with @break of immediately following <lb> element.
Hyphens in source document encoded as U+2010 inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element.
Hyphens in source document encoded as U+202D inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element.
Schema Declaration
element p
{
   "All hyphens in source document encoded as U+2010."
 | "All hyphens in source document encoded as U+002D."
 | "Hyphens in source document                                   encoded as U+2010. Line-ending hyphens                                   differentiated with @break of immediately following                                   <lb> element."
 | "Hyphens in source document                                   encoded as U+002D. Line-ending hyphens                                   differentiated with @break of immediately following                                   <lb> element."
 | "Hyphens in source document encoded as                                   U+2010 inside a <pc>. Line-ending hyphens                                   differentiated with @force of the <pc> and                                   @break of immediately following <lb>                                   element."
 | "Hyphens in source document encoded as                                   U+202D inside a <pc>. Line-ending hyphens                                   differentiated with @force of the <pc> and                                   @break of immediately following <lb>                                   element."
}
Legal values are:
All hyphens in source document encoded as U+2010.
All hyphens in source document encoded as U+002D.
Hyphens in source document encoded as U+2010. Line-ending hyphens differentiated with @break of immediately following <lb> element.
Hyphens in source document encoded as U+002D. Line-ending hyphens differentiated with @break of immediately following <lb> element.
Hyphens in source document encoded as U+2010 inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element.
Hyphens in source document encoded as U+202D inside a <pc>. Line-ending hyphens differentiated with @force of the <pc> and @break of immediately following <lb> element.
1.7.1.40. <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. [2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
ISBN
International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.
ISSN
International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.
DOI
Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.
URI
Uniform Resource Identifier: a string of characters to uniquely identify a resource which usually contains indication of the means of accessing that resource, the name of its host, and its filepath.
VIAF
A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.
ESTC
English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.
OCLC
OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.
LC_call_number
(U.S. Library of Congress call number)
LCCN
(Library of Congress control number)
Member of
Contained by
May contain
header: idno
character data
Note

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

Example
<idno type="ISBN">978-1-906964-22-1</idno> <idno type="ISSN">0143-3385</idno> <idno type="DOI">10.1000/123</idno> <idno type="URI">http://www.worldcat.org/oclc/185922478</idno> <idno type="URI">http://authority.nzetc.org/463/</idno> <idno type="LT">Thomason Tract E.537(17)</idno> <idno type="Wing">C695</idno> <idno type="oldCat">  <g ref="#sym"/>345 </idno>
In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>
    
Schema Declaration
element idno
{
   L1_att.global.attributes,
   L1_att.sortable.attributes,
   L1_att.datable.attributes,
   attribute type
   {
      "ISBN"
    | "ISSN"
    | "DOI"
    | "URI"
    | "VIAF"
    | "ESTC"
    | "OCLC"
    | "LC_call_number"
    | "LCCN"
   }?,
   ( text | L1_model.gLike | L1_idno )*
}
1.7.1.41. <imprint>
<imprint> groups information relating to the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
core: monogr
May contain
Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="classCode"/>
   <elementRef key="catRef"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate>
    <classRef key="model.imprintPart"/>
    <classRef key="model.dateLike"/>
   </alternate>
   <elementRef key="respStmt" minOccurs="0"
    maxOccurs="unbounded"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element imprint
{
   L1_att.global.attributes,
   (
      ( L1_classCode | catRef )*,
      (
         ( L1_model.imprintPart | L1_model.dateLike ),
         L1_respStmt*,
         L1_model.global*
      )+
   )
}
1.7.1.42. <item>
<item> contains one component of a list. [3.7. Lists 2.6. The Revision Description]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey)
Contained by
core: list
May contain
Note

May contain simple prose or a sequence of chunks.

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

Example
<list rend="numbered">  <head>Here begin the chapter headings of Book IV</head>  <item n="4.1">The death of Queen Clotild.</item>  <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>  <item n="4.3">The wives and children of Lothar.</item>  <item n="4.4">The Counts of the Bretons.</item>  <item n="4.5">Saint Gall the Bishop.</item>  <item n="4.6">The priest Cato.</item>  <item> ...</item> </list>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element item
{
   L1_att.global.attributes,
   L1_att.sortable.attributes,
   L1_macro.specialPara
}
1.7.1.43. <keywords>
<keywords> contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
schemeidentifies the controlled vocabulary within which the set of keywords concerned is defined, for example by a <taxonomy> element, or by some other resource.
StatusOptional
Datatypeteidata.pointer
Contained by
header: textClass
May 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 a <item> inside a <list> is permitted for backwards compatibility, but is deprecated.

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

Example
<keywords scheme="http://classificationweb.net">  <term>Babbage, Charles</term>  <term>Mathematicians - Great Britain - Biography</term> </keywords>
Example
<keywords>  <term>Fermented beverages</term>  <term>Central Andes</term>  <term>Schinus molle</term>  <term>Molle beer</term>  <term>Indigenous peoples</term>  <term>Ethnography</term>  <term>Archaeology</term> </keywords>
Content model
<content>
 <alternate>
  <elementRef key="term" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="list"/>
 </alternate>
</content>
    
Schema Declaration
element keywords
{
   L1_att.global.attributes,
   attribute scheme { text }?,
   ( L1_term+ | L1_list )
}
1.7.1.44. <label>
<label> contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.7. Lists]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.written (@hand)
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
ExampleLabels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:
<list type="glossxml:lang="enm">  <head xml:lang="en">Vocabulary</head>  <headLabel xml:lang="en">Middle English</headLabel>  <headItem xml:lang="en">New English</headItem>  <label>nu</label>  <item xml:lang="en">now</item>  <label>lhude</label>  <item xml:lang="en">loudly</item>  <label>bloweth</label>  <item xml:lang="en">blooms</item>  <label>med</label>  <item xml:lang="en">meadow</item>  <label>wude</label>  <item xml:lang="en">wood</item>  <label>awe</label>  <item xml:lang="en">ewe</item>  <label>lhouth</label>  <item xml:lang="en">lows</item>  <label>sterteth</label>  <item xml:lang="en">bounds, frisks (cf. <cit>    <ref>Chaucer, K.T.644</ref>    <quote>a courser, <term>sterting</term>as the fyr</quote>   </cit>  </item>  <label>verteth</label>  <item xml:lang="la">pedit</item>  <label>murie</label>  <item xml:lang="en">merrily</item>  <label>swik</label>  <item xml:lang="en">cease</item>  <label>naver</label>  <item xml:lang="en">never</item> </list>
ExampleLabels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:
I will add two facts, which have seldom occurred in the composition of six, or at least of five quartos. <list rend="runontype="ordered">  <label>(1)</label>  <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>  <label>(2) </label>  <item>Not a sheet has been seen by any human eyes, excepting those of the author and the    printer: the faults and the merits are exclusively my own.</item> </list>
ExampleLabels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:
<list type="gloss">  <label>March 1757.</label>  <item>I wrote some critical observations upon Plautus.</item>  <label>March 8th.</label>  <item>I wrote a long dissertation upon some lines of Virgil.</item>  <label>June.</label>  <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus      amori.</quote>  </item>  <label>August.</label>  <item>I went to Crassy, and staid two days.</item> </list>
Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.
ExampleLabels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it.
<p>[...] <lb/>&amp; n’entrer en mauuais &amp; mal-heu- <lb/>ré meſnage. Or des que le conſente- <lb/>ment des parties y eſt le mariage eſt <lb/> arreſté, quoy que de faict il ne ſoit <label place="margin">Puiſſance maritale    entre les Romains.</label>  <lb/> conſommé. Depuis la conſomma- <lb/>tion du mariage la femme eſt ſoubs <lb/> la puiſſance du mary, s’il n’eſt eſcla- <lb/>ue ou enfant de famille : car en ce <lb/> cas, la femme, qui a eſpouſé vn en- <lb/>fant de famille, eſt ſous la puiſſance [...]</p>
In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element label
{
   L1_att.global.attributes,
   L1_att.typed.attributes,
   L1_att.written.attributes,
   L1_macro.phraseSeq
}
1.7.1.45. <langUsage>
<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
header: profileDesc
May contain
core: p
header: language
Example
<langUsage>  <language ident="fr-CAusage="60">Québecois</language>  <language ident="en-CAusage="20">Canadian business English</language>  <language ident="en-GBusage="20">British English</language> </langUsage>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="language" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element langUsage
{
   L1_att.global.attributes,
   ( L1_model.pLike+ | L1_language+ )
}
1.7.1.46. <language>
<language> characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which is referenced by the global xml:lang attribute.
StatusRequired
Datatypeteidata.language
usagespecifies the approximate percentage (by volume) of the text which uses this language.
StatusOptional
DatatypenonNegativeInteger
Contained by
header: langUsage
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Note

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

Example
<langUsage>  <language ident="en-USusage="75">modern American English</language>  <language ident="i-az-Arabusage="20">Azerbaijani in Arabic script</language>  <language ident="x-lapusage="05">Pig Latin</language> </langUsage>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element language
{
   L1_att.global.attributes,
   attribute ident { text },
   attribute usage { text }?,
   L1_macro.phraseSeq.limited
}
1.7.1.47. <licence>
<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@target) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Member of
Contained by
header: availability
May contain
Note

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

Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence </licence>
Example
<availability>  <licence target="http://creativecommons.org/licenses/by/3.0/"   notBefore="2013-01-01">   <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence      applies to this document.</p>   <p>The licence was added on January 1, 2013.</p>  </licence> </availability>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element licence
{
   L1_att.global.attributes,
   L1_att.pointing.attributes,
   L1_att.datable.attributes,
   L1_macro.specialPara
}
1.7.1.48. <line>
<line> contains the transcription of a topographic line in the source document [11.2.2. Embedded Transcription]
Moduletranscr — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.typed (@type) att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@ulx, @uly, @lrx, @lry) att.written (@hand)
Member of
Contained by
transcr: line surface zone
May contain
core: choice
transcr: line zone
character data
Note

This element should be used only to mark up writing which is topographically organized as a series of lines, horizontal or vertical. It should not be used to mark lines of verse (for which use <l>) nor to mark linebreaks within text which has been encoded using structural elements such as <p> (for which use <lb>).

Example
<surface>  <zone>   <line>Poem</line>   <line>As in Visions of — at</line>   <line>night —</line>   <line>All sorts of fancies running through</line>   <line>the head</line>  </zone> </surface>
Example
<surface>  <zone>   <line>Hope you enjoyed</line>   <line>Wales, as they      said</line>   <line>to Mrs FitzHerbert</line>   <line>Mama</line>  </zone>  <zone>   <line>Printed in England</line>  </zone> </surface>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.global"/>
  <classRef key="model.gLike"/>
  <classRef key="model.linePart"/>
 </alternate>
</content>
    
Schema Declaration
element line
{
   L1_att.typed.attributes,
   L1_att.global.attributes,
   L1_att.coordinated.attributes,
   L1_att.written.attributes,
   ( text | L1_model.global | L1_model.gLike | L1_model.linePart )*
}
1.7.1.49. <list>
<list> contains any sequence of items organized as a list. [3.7. Lists]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.sortable (@sortKey)
typedescribes the nature of the items in the list.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
gloss
each list item glosses some term or concept, which is given by a <label> element preceding the list item.
index
each list item is an entry in an index such as the alphabetical topical index at the back of a print volume.
instructions
each list item is a step in a sequence of instructions, as in a recipe.
litany
each list item is one of a sequence of petitions, supplications or invocations, typically in a religious ritual.
syllogism
each list item is part of an argument consisting of two or more propositions and a final conclusion derived from them.
Note

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

Note

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

Member of
Contained by
May contain
core: item label
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 type="syllogismrend="bulleted">  <item>All Cretans are liars.</item>  <item>Epimenides is a Cretan.</item>  <item>ERGO Epimenides is a liar.</item> </list>
Example
<list type="litanyrend="simple">  <item>God save us from drought.</item>  <item>God save us from pestilence.</item>  <item>God save us from wickedness in high places.</item>  <item>Praise be to God.</item> </list>
ExampleThe following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):
<div1 type="section">  <head>Athelstan's Ordinance</head>  <list rend="numbered">   <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with      the stolen goods, [if he is] over twelve years and [if the value of the goods is] over      eightpence.   <list rend="numbered">     <item n="1.1">And if anyone does spare one, he is to pay for the thief with his          wergild — and the thief is to be no nearer a settlement on that account — or to          clear himself by an oath of that amount.</item>     <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is          not to be spared [whether younger or older than twelve].</item>     <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may          then be redeemed with 120 shillings; and the kindred are to stand surety for him          that he will desist for ever.</item>     <item n="1.4">And if he steals after that, they are to pay for him with his wergild,          or to bring him back there.</item>     <item n="1.5">And if he steals after that, they are to pay for him with his wergild,          whether to the king or to him to whom it rightly belongs; and everyone of those who          supported him is to pay 120 shillings to the king as a fine.</item>    </list>   </item>   <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom      no justice can be obtained, that one should order their kindred to fetch back such a      person to justice and to find him a lord in public meeting.   <list rend="numbered">     <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,          he is then to be a fugitive afterwards, and he who encounters him is to strike him          down as a thief.</item>     <item n="2.2">And he who harbours him after that, is to pay for him with his wergild          or to clear himself by an oath of that amount.</item>    </list>   </item>   <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds      his guilty man, so that the king is appealed to, is to repay the value of the goods and      120 shillings to the king; and he who appeals to the king before he demands justice as      often as he ought, is to pay the same fine as the other would have done, if he had      refused him justice.   <list rend="numbered">     <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes          known about him, is to forfeit the slave and be liable to his wergild on the first          occasionp if he does it more often, he is to be liable to pay all that he owns.</item>     <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been          an accessory of thieves who have committed theft, is to liable to the same.</item>    </list>   </item>   <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to      a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is      afterwards convicted at the three-fold ordeal.</item>  </list> </div1>
Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.
Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy Cross. <list rend="simple">   <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have      subscribed to the pious and catholic validity of this document with the sign of the Holy      Cross.</item>   <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with      the sign of the Holy Cross.</item>   <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the      sign of the Holy Cross.</item>   <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the      sign of the Holy Cross.</item>   <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of      the Holy Cross.</item>   <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>   <item>I, Æthelwine, bishop, have subscribed through delegates.</item>   <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy      Cross.</item>  </list> </p>
Schematron
<sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="item"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence>
    <elementRef key="headLabel"
     minOccurs="0"/>
    <elementRef key="headItem"
     minOccurs="0"/>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="label"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
     <elementRef key="item"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element list
{
   L1_att.global.attributes,
   L1_att.sortable.attributes,
   attribute type
   {
      "gloss" | "index" | "instructions" | "litany" | "syllogism"
   }?,
   (
      ( model.divTop | L1_model.global )*,
      (
         ( L1_item, L1_model.global* )+
       | (
            headLabel?,
            headItem?,
            ( L1_label, L1_model.global*, L1_item, L1_model.global* )+
         )
      ),
      ( model.divBottom, L1_model.global* )*
   )
}
1.7.1.50. <listPrefixDef>
<listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in data.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
May contain
derived-module-bptl-L1: prefixDef
ExampleIn this example, two private URI scheme prefixes are defined and patterns are provided for dereferencing them. Each prefix is also supplied with a human-readable explanation in a <p> element.
<listPrefixDef>  <prefixDef ident="psn"   matchPattern="([A-Z]+)"   replacementPattern="personography.xml#$1">   <p> Private URIs using the <code>psn</code>      prefix are pointers to <gi>person</gi>      elements in the personography.xml file.      For example, <code>psn:MDH</code>      dereferences to <code>personography.xml#MDH</code>.   </p>  </prefixDef>  <prefixDef ident="bibl"   matchPattern="([a-z]+[a-z0-9]*)"   replacementPattern="http://www.example.com/getBibl.xql?id=$1">   <p> Private URIs using the <code>bibl</code> prefix can be      expanded to form URIs which retrieve the relevant      bibliographical reference from www.example.com.   </p>  </prefixDef> </listPrefixDef>
Content model
<content>
 <elementRef key="BPTL.required.prefixDef"/>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="prefixDef"/>
  <elementRef key="listPrefixDef"/>
 </alternate>
</content>
    
Schema Declaration
element listPrefixDef
{
   L1_att.global.attributes,
   L1_BPTL.required.prefixDef,
   ( L1_prefixDef | L1_listPrefixDef )*
}
1.7.1.51. <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.11.2.1. Analytic, Monographic, and Series Levels]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
May contain
Note

May contain specialized bibliographic elements, in a prescribed order.

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

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope unit="pagefrom="377to="380">377–380</biblScope>  </monogr> </biblStruct>
Example
<biblStruct type="book">  <monogr>   <author>    <persName>     <forename>Leo Joachim</forename>     <surname>Frachtenberg</surname>    </persName>   </author>   <title type="mainlevel="m">Lower Umpqua Texts</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Columbia University Press</publisher>    <date>1914</date>   </imprint>  </monogr>  <series>   <title type="mainlevel="s">Columbia University Contributions to      Anthropology</title>   <biblScope unit="volume">4</biblScope>  </series> </biblStruct>
Content model
<content>
 <sequence>
  <alternate minOccurs="0">
   <sequence>
    <alternate>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <elementRef key="title" minOccurs="1"
     maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
     <elementRef key="textLang"/>
     <elementRef key="editor"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="title"/>
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="textLang"/>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <elementRef key="authority"/>
    <elementRef key="idno"/>
   </sequence>
  </alternate>
  <elementRef key="availability"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.noteLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="edition"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <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 minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="imprint"/>
   <elementRef key="extent"/>
   <elementRef key="biblScope"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element monogr
{
   L1_att.global.attributes,
   (
      (
         (
            ( L1_author | L1_editor | meeting | L1_respStmt ),
            ( L1_author | L1_editor | meeting | L1_respStmt )*,
            L1_title+,
            (
               L1_model.ptrLike
             | L1_idno
             | L1_textLang
             | L1_editor
             | L1_respStmt
            )*
         )
       | (
            ( L1_title | L1_model.ptrLike | L1_idno )+,
            ( L1_textLang | L1_author | L1_editor | meeting | L1_respStmt )*
         )
       | ( authority, L1_idno )
      )?,
      L1_availability*,
      L1_model.noteLike*,
      (
         L1_edition,
         (
            L1_idno
          | L1_model.ptrLike
          | L1_editor
          | sponsor
          | funder
          | L1_respStmt
         )*
      )*,
      L1_imprint,
      ( L1_imprint | L1_extent | L1_biblScope )*
   )
}
1.7.1.52. <name>
<name> (name, proper noun) contains a proper noun or noun phrase. [3.5.1. Referring Strings]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)) att.typed (@type)
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Note

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

Example
<name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name type="personref="#HOC001">Occleve</name>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element name
{
   L1_att.global.attributes,
   L1_att.personal.attributes,
   L1_att.datable.attributes,
   L1_att.typed.attributes,
   L1_macro.phraseSeq
}
1.7.1.53. <namespace>
<namespace> supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
namespecifies the full formal name of the namespace concerned.
StatusRequired
Datatypelib.teins
Contained by
header: tagsDecl
May contain
header: tagUsage
Example
<namespace name="http://www.tei-c.org/ns/1.0">  <tagUsage gi="hioccurs="28withId="2"> Used only to mark English words    italicized in the copy text </tagUsage> </namespace>
Content model
<content>
 <elementRef key="tagUsage"/>
</content>
    
Schema Declaration
element namespace
{
   L1_att.global.attributes,
   attribute name { text },
   L1_tagUsage
}
1.7.1.54. <normalization>
<normalization> indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
methodindicates the method adopted to indicate normalizations within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
normalization made silently[Default]
markup
normalization represented using markup
Contained by
May contain
core: p
Example
<editorialDecl>  <normalization method="markup">   <p>Where both upper- and lower-case i, j, u, v, and vv have been normalized, to modern      20th century typographical practice, the <gi>choice</gi> element has been used to      enclose <gi>orig</gi> and <gi>reg</gi> elements giving the original and new values      respectively. ... </p>  </normalization>  <normalization method="silent">   <p>Spacing between words and following punctuation has been regularized to zero spaces;      spacing between words has been regularized to one space.</p>  </normalization>  <normalization source="http://www.dict.sztaki.hu/webster">   <p>Spelling converted throughout to Modern American usage, based on Websters 9th      Collegiate dictionary.</p>  </normalization> </editorialDecl>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element normalization
{
   L1_att.global.attributes,
   attribute method { "silent" | "markup" }?,
   L1_model.pLike+
}
1.7.1.55. <note>
<note> contains a note or annotation. [3.8.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.11.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type) att.written (@hand)
Member of
Contained by
May contain
ExampleIn the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note place="bottomtype="gloss"  resp="#MDMH">  <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. <!-- elsewhere in the document --> <respStmt xml:id="MDMH">  <resp>translation from German to English</resp>  <name>Hottinger, Marie Donald Mackie</name> </respStmt>
For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.
ExampleThe global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century, <note n="126anchored="true"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann.
However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element note
{
   L1_att.global.attributes,
   L1_att.typed.attributes,
   L1_att.written.attributes,
   L1_macro.specialPara
}
1.7.1.56. <notesStmt>
<notesStmt> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: fileDesc
May contain
core: note
Note

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

Example
<notesStmt>  <note>Historical commentary provided by Mark Cohen</note>  <note>OCR scanning done at University of Toronto</note> </notesStmt>
Content model
<content>
 <classRef minOccurs="1"
  maxOccurs="unbounded" key="model.noteLike"/>
</content>
    
Schema Declaration
element notesStmt { L1_att.global.attributes, L1_model.noteLike+ }
1.7.1.57. <orgName>
<orgName> (organization name) contains an organizational name. [13.2.2. Organizational Names]
Modulenamesdates — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) att.typed (@type)
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">  <placeName key="PEN">Pennsyla.</placeName> Abolition Society </orgName> [...]
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element orgName
{
   L1_att.global.attributes,
   L1_att.personal.attributes,
   L1_att.typed.attributes,
   L1_macro.phraseSeq
}
1.7.1.58. <p>
<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.fragmentable (@part) att.written (@hand)
Member of
Contained by
May contain
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you    done?</q> </p> <p>  <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. </p> <p>  <q>Then you must mean that Thorvald is dead,</q> she said. </p> <p>  <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> </p>
Schematron
<s:report test="not(ancestor::tei:floatingText) and (ancestor::tei:p or ancestor::tei:ab) and not(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. </s:report>
Schematron
<s:report test="ancestor::tei:l[not(.//tei:note//tei:p[. = current()])]"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab. </s:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element p
{
   L1_att.global.attributes,
   L1_att.fragmentable.attributes,
   L1_att.written.attributes,
   L1_macro.paraContent
}
1.7.1.59. <persName>
<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [13.2.1. Personal Names]
Modulenamesdates — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.personal (@full, @sort) att.typed (@type)
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
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
{
   L1_att.global.attributes,
   L1_att.personal.attributes,
   L1_att.typed.attributes,
   L1_macro.phraseSeq
}
1.7.1.60. <postBox>
<postBox> (postal box or post office box) contains a number or other identifier for some postal delivery point other than a street address. [3.5.2. Addresses]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: address
May containCharacter data only
Note

The position and nature of postal codes is highly country-specific; the conventions appropriate to the country concerned should be used.

Example
<postBox>P.O. Box 280</postBox>
Example
<postBox>Postbus 532</postBox>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element postBox { L1_att.global.attributes, text }
1.7.1.61. <postCode>
<postCode> (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. [3.5.2. Addresses]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: address
May containCharacter data only
Note

The position and nature of postal codes is highly country-specific; the conventions appropriate to the country concerned should be used.

Example
<postCode>HR1 3LR</postCode>
Example
<postCode>60142-7</postCode>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element postCode { L1_att.global.attributes, text }
1.7.1.62. <prefixDef>
<prefixDef> (prefix definition) defines a prefixing scheme used in data.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.patternReplacement (@matchPattern, @replacementPattern)
identsupplies a name which functions as the prefix for an abbreviated pointing scheme such as a private URI scheme. The prefix constitutes the text preceding the first colon.
StatusRequired
Datatypeteidata.prefix
Note

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

Contained by
May contain
core: p
Note

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

Example
<prefixDef ident="ref"  matchPattern="([a-z]+)"  replacementPattern="../../references/references.xml#$1">  <p> In the context of this project, private URIs with    the prefix "ref" point to <gi>div</gi> elements in    the project's global references.xml file.  </p> </prefixDef>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element prefixDef
{
   L1_att.global.attributes,
   L1_att.patternReplacement.attributes,
   attribute ident { text },
   L1_model.pLike*
}
1.7.1.63. <profileDesc>
<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: teiHeader
May contain
Note

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

Example
<profileDesc>  <langUsage>   <language ident="fr">French</language>  </langUsage>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc>  <settingDesc>   <setting>    <name>Paris, France</name>    <time>Late 19th century</time>   </setting>  </settingDesc> </profileDesc>
Content model
<content>
 <classRef key="model.profileDescPart"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element profileDesc { L1_att.global.attributes, L1_model.profileDescPart* }
1.7.1.64. <projectDesc>
<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: encodingDesc
May contain
core: p
Example
<projectDesc>  <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element projectDesc { L1_att.global.attributes, L1_model.pLike+ }
1.7.1.65. <ptr>
<ptr> (pointer) defines a pointer to another location. [3.6. Simple Links and Cross-References 16.1. Links]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@target) att.internetMedia (@mimeType) att.typed (@type)
Member of
Contained by
May containEmpty element
Example
<ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/>
Schematron
<s:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <s:name/>.</s:report>
Content model
<content/>
    
Schema Declaration
element ptr
{
   L1_att.global.attributes,
   L1_att.pointing.attributes,
   L1_att.internetMedia.attributes,
   L1_att.typed.attributes,
   empty
}
1.7.1.66. <pubPlace>
<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.11.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Example
<publicationStmt>  <publisher>Oxford University Press</publisher>  <pubPlace>Oxford</pubPlace>  <date>1989</date> </publicationStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element pubPlace { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.67. <publicationStmt>
<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: fileDesc
May contain
Note

For normally published items, the specialized children elements (e.g. <publisher>) should be used. Paragraphs are permitted as an alternative for unusual cases like unpublished works.

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>
Schematron
<s:report role="warning" test="child::tei:p">Use of specialized child elements of the publication statement (rather than paragraphs) is recommended whenever possible</s:report>
Schematron
<s:rule context="tei:publicationStmt/tei:date"> <s:assert test="@when">Dates inside the publication statement should have @when (and should not have content)</s:assert> <s:report test="string-length( normalize-space(.) ) > 0">Dates inside the publication statement should not have content (and should have @when)</s:report> </s:rule>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.publicationStmtPart.agency"/>
   <classRef key="model.publicationStmtPart.detail"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element publicationStmt
{
   L1_att.global.attributes,
   (
      (
         L1_model.publicationStmtPart.agency,
         L1_model.publicationStmtPart.detail*
      )+
    | L1_model.pLike+
   )
}
1.7.1.68. <publisher>
<publisher> provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Note

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

Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element publisher { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.69. <punctuation>
<punctuation> specifies editorial practice adopted with respect to punctuation marks in the original. [2.3.3. The Editorial Practices Declaration 3.2. Treatment of Punctuation]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
marksindicates whether or not punctation marks have been retained as content within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
no punctuation marks have been retained
some
some punctuation marks have been retained
all
all punctuation marks have been retained
placementindicates the positioning of punctuation marks that are associated with marked up text as being encoded within the element surrounding the text or immediately before or after it.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
internal
punctuation marks found at the start or end of a marked up text component are included within its surrounding element;
external
punctuation marks found at the start or end of a marked up text component appear immediately before or after the surrounding element
Contained by
May contain
core: p
Example
<punctuation marks="all"  placement="internal">  <p>All punctuation marks in the source text have been retained and represented using the    appropriate Unicode code point. In cases where a punctuation mark and nearby markup convey    the same information (for example, a sentence ends with a question mark and is also tagged    as <gi>s</gi>) the punctuation mark is captured as content within the element.</p> </punctuation>
ExampleExternal placement of punctuation:
<p>I would agree with Saint Augustine that “<quote>An unjust law is no law at all</quote>.”</p>
ExampleInternal placement of punctuation:
<p>I would agree with Saint Augustine that <quote>“An unjust law is no law at all.”</quote> </p>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element punctuation
{
   L1_att.global.attributes,
   attribute marks { "none" | "some" | "all" }?,
   attribute placement { "internal" | "external" }?,
   L1_model.pLike*
}
1.7.1.70. <q>
<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.ascribed (@who)
typemay be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
spoken
representation of speech
thought
representation of thought, e.g. internal monologue
written
quotation from a written source
soCalled
authorial distance
foreign
distinct
linguistically distinct
term
technical term
emph
rhetorically emphasized
mentioned
refering to itself, not its normal referent
Member of
Contained by
May contain
Note

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

Example
It is spelled <q>Tübingen</q> — to enter the letter <q>u</q> with an umlaut hold down the <q>option</q> key and press <q>0 0 f c</q>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element q
{
   L1_att.global.attributes,
   L1_att.ascribed.attributes,
   attribute type
   {
      "spoken"
    | "thought"
    | "written"
    | "soCalled"
    | "foreign"
    | "distinct"
    | "term"
    | "emph"
    | "mentioned"
   }?,
   L1_macro.specialPara
}
1.7.1.71. <quotation>
<quotation> specifies editorial practice adopted with respect to quotation marks in the original. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
marks(quotation marks) indicates whether or not quotation marks have been retained as content within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
no quotation marks have been retained
some
some quotation marks have been retained
all
all quotation marks have been retained
Contained by
May contain
core: p
Example
<quotation marks="none">  <p>No quotation marks have been retained. Instead, the <att>rend</att> attribute on the  <gi>q</gi> element is used to specify what kinds of quotation mark was used, according    to the following list: <list type="gloss">    <label>dq</label>    <item>double quotes, open and close</item>    <label>sq</label>    <item>single quotes, open and close</item>    <label>dash</label>    <item>long dash open, no close</item>    <label>dg</label>    <item>double guillemets, open and close</item>   </list>  </p> </quotation>
Example
<quotation marks="all">  <p>All quotation marks are retained in the text and are represented by appropriate Unicode    characters.</p> </quotation>
Schematron
<s:report test="not(@marks) and not (tei:p)">On <s:name/>, either the @marks attribute should be used, or a paragraph of description provided</s:report>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element quotation
{
   L1_att.global.attributes,
   attribute marks { "none" | "some" | "all" }?,
   L1_model.pLike*
}
1.7.1.72. <ref>
<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. Simple Links and Cross-References 16.1. Links]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@target) att.internetMedia (@mimeType) att.typed (@type)
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term> </ref>.
Schematron
<s:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <s:name/> </s:report>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element ref
{
   L1_att.global.attributes,
   L1_att.pointing.attributes,
   L1_att.internetMedia.attributes,
   L1_att.typed.attributes,
   L1_macro.paraContent
}
1.7.1.73. <relatedItem>
<relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.11.2.7. Related Items]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type)
Member of
Contained by
May contain
Note

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

Example
<biblStruct>  <monogr>   <author>Shirley, James</author>   <title type="main">The gentlemen of Venice</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Readex Microprint</publisher>    <date>1953</date>   </imprint>   <extent>1 microprint card, 23 x 15 cm.</extent>  </monogr>  <series>   <title>Three centuries of drama: English, 1642–1700</title>  </series>  <relatedItem type="otherForm">   <biblStruct>    <monogr>     <author>Shirley, James</author>     <title type="main">The gentlemen of Venice</title>     <title type="sub">a tragi-comedie presented at the private house in Salisbury          Court by Her Majesties servants</title>     <imprint>      <pubPlace>London</pubPlace>      <publisher>H. Moseley</publisher>      <date>1655</date>     </imprint>     <extent>78 p.</extent>    </monogr>   </biblStruct>  </relatedItem> </biblStruct>
Content model
<content>
 <elementRef key="biblStruct"/>
</content>
    
Schema Declaration
element relatedItem
{
   L1_att.global.attributes,
   L1_att.typed.attributes,
   L1_biblStruct
}
1.7.1.74. <rendition>
<rendition> supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.styleDef (scheme, @schemeVersion)
schemeidentifies the language used to describe the rendition.
Derived fromatt.styleDef
StatusRequired
Datatypeteidata.enumerated
Legal values are:
css
Cascading Stylesheet Language
scopewhere CSS is used, provides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
first-line
styling applies to the first line of the target element
first-letter
styling applies to the first letter of the target element
before
styling should be applied immediately before the content of the target element
after
styling should be applied immediately after the content of the target element
selectorcontains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute.
StatusOptional
Datatypeteidata.text
<rendition scheme="css"  selector="text, front, back, body, div, p, ab"> display: block; </rendition>
<rendition scheme="css"  selector="*[rend*=italic]"> font-style: italic; </rendition>
Note

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

Note

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

Contained by
header: tagsDecl
May contain
Example
<tagsDecl>  <rendition xml:id="r-centerscheme="css">text-align: center;</rendition>  <rendition xml:id="r-smallscheme="css">font-size: small;</rendition>  <rendition xml:id="r-largescheme="css">font-size: large;</rendition>  <rendition xml:id="initcaps"   scope="first-letterscheme="css">font-size: xx-large</rendition> </tagsDecl>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element rendition
{
   L1_att.global.attributes,
   L1_att.styleDef.attribute.schemeVersion,
   attribute scheme { "css" },
   attribute scope { text }?,
   attribute selector { text }?,
   L1_macro.limitedContent
}
1.7.1.75. <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.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
Contained by
core: respStmt
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Note

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

Example
<respStmt>  <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>  <name>Edward Child</name> </respStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element resp
{
   L1_att.global.attributes,
   L1_att.canonical.attributes,
   L1_att.datable.attributes,
   L1_macro.phraseSeq.limited
}
1.7.1.76. <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.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref)
Member of
Contained by
May contain
core: name resp
namesdates: orgName persName
Example
<respStmt>  <resp>transcribed from original ms</resp>  <persName>Claus Huitfeldt</persName> </respStmt>
Example
<respStmt>  <resp>converted to XML encoding</resp>  <name>Alan Morrison</name> </respStmt>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef minOccurs="1" maxOccurs="1"
   key="resp"/>
  <classRef minOccurs="1"
   maxOccurs="unbounded" key="model.nameLike.agent"/>
 </sequence>
</content>
    
Schema Declaration
element respStmt
{
   L1_att.global.attributes,
   L1_att.canonical.attributes,
   ( L1_resp, L1_model.nameLike.agent+ )
}
1.7.1.77. <revisionDesc>
<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.docStatus (@status)
Contained by
header: teiHeader
May contain
core: list
header: change
Note

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

Example
<revisionDesc status="embargoed">  <change when="1991-11-11who="#LB"> deleted chapter 10 </change> </revisionDesc>
Content model
<content>
 <alternate>
  <elementRef key="list"/>
  <elementRef key="listChange"/>
  <elementRef key="change" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element revisionDesc
{
   L1_att.global.attributes,
   L1_att.docStatus.attributes,
   ( L1_list | listChange | L1_change+ )
}
1.7.1.78. <samplingDecl>
<samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: encodingDesc
May contain
core: p
Note

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

Example
<samplingDecl>  <p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each    text identified as relevant by respondents.</p> </samplingDecl>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element samplingDecl { L1_att.global.attributes, L1_model.pLike+ }
1.7.1.79. <schemaRef>
<schemaRef> (schema reference) describes or points to a related customization or schema file [2.3.9. The Schema Specification]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type)
url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
Derived fromatt.resourced
StatusRequired
Datatypeteidata.enumerated
Suggested values include:
bptl:L1-v4.0.0
(Best Practices for TEI in Libraries level 1, version 4.0.0)
bptl:L2-v4.0.0
(Best Practices for TEI in Libraries level 2, version 4.0.0)
bptl:L3-v4.0.0
(Best Practices for TEI in Libraries level 3, version 4.0.0)
bptl:L4-v4.0.0
(Best Practices for TEI in Libraries level 4, version 4.0.0)
bptl:L5-v4.0.0
(Best Practices for TEI in Libraries level 5, version 4.0.0)
Contained by
header: encodingDesc
May containEmpty element
Example
<schemaRef type="interchangeODD"  url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.odd"/> <schemaRef type="interchangeRNG"  url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.rng"/> <schemaRef type="projectODD"  url="file:///schema/project.odd"/>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0"/>
</content>
    
Schema Declaration
element schemaRef
{
   L1_att.global.attributes,
   L1_att.typed.attributes,
   attribute url
   {
      "bptl:L1-v4.0.0"
    | "bptl:L2-v4.0.0"
    | "bptl:L3-v4.0.0"
    | "bptl:L4-v4.0.0"
    | "bptl:L5-v4.0.0"
   },
   L1_model.descLike?
}
1.7.1.80. <series>
<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.11.2.1. Analytic, Monographic, and Series Levels]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May contain
Example
<series xml:lang="de">  <title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>  <respStmt>   <resp>Herausgegeben von</resp>   <name type="person">Manfred Thaller</name>   <name type="org">Max-Planck-Institut für Geschichte</name>  </respStmt>  <title level="s">Serie A: Historische Quellenkunden</title>  <biblScope>Band 11</biblScope> </series>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="biblScope"/>
  <elementRef key="idno"/>
  <elementRef key="textLang"/>
  <classRef key="model.global"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element series
{
   L1_att.global.attributes,
   (
      text
    | L1_model.gLike
    | L1_title
    | L1_model.ptrLike
    | L1_editor
    | L1_respStmt
    | L1_biblScope
    | L1_idno
    | L1_textLang
    | L1_model.global
    | L1_availability
   )*
}
1.7.1.81. <seriesStmt>
<seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: fileDesc
May contain
Example
<seriesStmt>  <title>Machine-Readable Texts for the Study of Indian Literature</title>  <respStmt>   <resp>ed. by</resp>   <name>Jan Gonda</name>  </respStmt>  <biblScope unit="volume">1.2</biblScope>  <idno type="ISSN">0 345 6789</idno> </seriesStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="title" minOccurs="1"
    maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="editor"/>
    <elementRef key="respStmt"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="idno"/>
    <elementRef key="biblScope"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element seriesStmt
{
   L1_att.global.attributes,
   (
      L1_model.pLike+
    | ( L1_title+, ( L1_editor | L1_respStmt )*, ( L1_idno | L1_biblScope )* )
   )
}
1.7.1.82. <sourceDesc>
<sourceDesc> (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: fileDesc
May contain
Example
<sourceDesc>  <bibl>   <title level="a">The Interesting story of the Children in the Wood</title>. In  <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.  <publisher>OUP</publisher>   <date>1968</date>. </bibl> </sourceDesc>
Example
<sourceDesc>  <p>Born digital: no previous source exists.</p> </sourceDesc>
Content model
<content>
 <elementRef key="biblStruct"/>
</content>
    
Schema Declaration
element sourceDesc { L1_att.global.attributes, L1_biblStruct }
1.7.1.83. <sourceDoc>
<sourceDoc> contains a transcription or other representation of a single source document potentially forming part of a dossier génétique or collection of sources. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Moduletranscr — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
textstructure: TEI
May contain
Note

This element may be used as an alternative to <facsimile> for TEI documents containing only page images, or for documents containing both images and transcriptions. Transcriptions may be provided within the <surface> elements making up a source document, in parallel with them as part of a <text> element, or in both places if the encoder wishes to distinguish these two modes of transcription.

Example
<sourceDoc>  <surfaceGrp n="leaf1">   <surface facs="page1.png">    <zone>All the writing on page 1</zone>   </surface>   <surface>    <graphic url="page2-highRes.png"/>    <graphic url="page2-lowRes.png"/>    <zone>     <line>A line of writing on page 2</line>     <line>Another line of writing on page 2</line>    </zone>   </surface>  </surfaceGrp> </sourceDoc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.global"/>
  <classRef key="model.graphicLike"/>
  <elementRef key="surface"/>
  <elementRef key="surfaceGrp"/>
 </alternate>
</content>
    
Schema Declaration
element sourceDoc
{
   L1_att.global.attributes,
   ( L1_model.global | L1_model.graphicLike | L1_surface | L1_surfaceGrp )+
}
1.7.1.84. <street>
<street> contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.5.2. Addresses]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
core: address
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
character data
Note

The order and presentation of house names and numbers and street names, etc., may vary considerably in different countries. The encoding should reflect the order which is appropriate in the country concerned.

Example
<street>via della Faggiola, 36</street>
Example
<street>  <name>Duntaggin</name>, 110 Southmoor Road </street>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element street { L1_att.global.attributes, L1_macro.phraseSeq }
1.7.1.85. <surface>
<surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Moduletranscr — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@ulx, @uly, @lrx, @lry) att.typed (@type)
Contained by
May contain
Note

The <surface> element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc.

The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high.

The <surface> element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every <zone> element contained by this element are to be understood with reference to the same grid.

Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> elements.

Example
<facsimile>  <surface ulx="0uly="0lrx="200lry="300">   <graphic url="Bovelles-49r.png"/>  </surface> </facsimile>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.graphicLike"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <alternate minOccurs="1" maxOccurs="1">
    <elementRef key="zone"/>
    <elementRef key="line"/>
    <elementRef key="surface"/>
    <elementRef key="surfaceGrp"/>
   </alternate>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element surface
{
   L1_att.global.attributes,
   L1_att.coordinated.attributes,
   L1_att.typed.attributes,
   (
      ( L1_model.global | L1_model.labelLike | L1_model.graphicLike )*,
      ( ( L1_zone | L1_line | L1_surface | L1_surfaceGrp ), L1_model.global* )*
   )
}
1.7.1.86. <surfaceGrp>
<surfaceGrp> defines any kind of useful grouping of written surfaces, for example the recto and verso of a single leaf, which the encoder wishes to treat as a single unit. [11.1. Digital Facsimiles]
Moduletranscr — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (@type)
Contained by
May contain
Note

Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> elements.

Example
<sourceDoc>  <surfaceGrp>   <surface ulx="0uly="0lrx="200"    lry="300">    <graphic url="Bovelles-49r.png"/>   </surface>   <surface ulx="0uly="0lrx="200"    lry="300">    <graphic url="Bovelles-49v.png"/>   </surface>  </surfaceGrp> </sourceDoc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.global"/>
  <elementRef key="surface"/>
  <elementRef key="surfaceGrp"/>
 </alternate>
</content>
    
Schema Declaration
element surfaceGrp
{
   L1_att.global.attributes,
   L1_att.typed.attributes,
   ( L1_model.global | L1_surface | L1_surfaceGrp )+
}
1.7.1.87. <tag>
<tag> contains text of a complete start- or end-tag, possibly including attribute specifications, but excluding the opening and closing markup delimiter characters. [22. Documentation Elements]
Moduletagdocs — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
typeindicates the type of XML tag intended
StatusOptional
Datatypeteidata.enumerated
Legal values are:
start
a start-tag, with delimiters < and > is intended
end
an end-tag, with delimiters </ and > is intended
empty
a empty tag, with delimiters < and /> is intended
pi
a pi (processing instruction), with delimiters <? and ?> is intended
comment
a comment, with delimiters <!-- and --> is intended
ms
a marked-section, with delimiters <[CDATA[ and ]]> is intended
schemesupplies the name of the schema in which this tag is defined.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
TEI
(text encoding initiative) This tag is defined as part of the TEI scheme.[Default]
DBK
(docbook) this tag is part of the Docbook scheme.
XX
(unknown) this tag is part of an unknown scheme.
Schematron
HTML
Member of
Contained by
May containCharacter data only
Example
Mark the start of each italicised phrase with a <tag>hi rend="it"</tag> tag, and its end with a <tag type="end">hi</tag> tag. <tag type="comment">Example updated on 2008-04-05</tag>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element tag
{
   L1_att.global.attributes,
   attribute type { "start" | "end" | "empty" | "pi" | "comment" | "ms" }?,
   attribute scheme { text }?,
   text
}
1.7.1.88. <tagUsage>
<tagUsage> documents the usage of a specific element within a specified document. [2.3.4. The Tagging Declaration]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
gi(element name) the name (generic identifier) of the element indicated by the tag.
StatusRequired
Datatypeteidata.enumerated
Schematron
<s:rule context="tei:text"> <s:report test=".//tei:div and .//tei:div1"> A single TEI in Libraries document should not mix numbered and unnumbered divisions. </s:report> </s:rule> <s:rule context="/tei:TEI[ tei:text//tei:div or tei:text//tei:div1 ]"> <s:assert test="/tei:TEI/tei:teiHeader/tei:encodingDesc/tei:tagsDecl/tei:namespace/tei:tagUsage[ @gi = ('div','div1') ]"> The use of divisions (i.e., whether numbered or unnumbered divisions are used) should be documented in a <tagUsage> element by "Unnumbered divs used." or "Numbered divs used." The <tagUsage> element must be the child of a <namespace name="http://www.tei-c.org/ns/1.0"> element.</s:assert> </s:rule> <s:rule context="/tei:TEI[ tei:sourceDoc and not( tei:text )]"> <s:assert test="/tei:TEI/tei:teiHeader/tei:encodingDesc/tei:tagsDecl/tei:namespace/tei:tagUsage[ @gi eq 'sourceDoc' ] "> The fact that logical divisions are not encoded (and thus neither numbered nor unnumbered divisions are used) should be documented in a <tagUsage> element by "Logical divisions not encoded." The <tagUsage> element must be the child of a <namespace name="http://www.tei-c.org/ns/1.0"> element.</s:assert> </s:rule> <s:rule context="tei:tagUsage"> <s:assert test=" ( @gi eq 'div' and normalize-space(.) eq 'Unnumbered divs used.' and not( /tei:TEI/tei:text//tei:div1 ) ) or ( @gi eq 'div1' and normalize-space(.) eq 'Numbered divs used.' and not( /tei:TEI/tei:text//tei:div ) ) or ( @gi eq 'sourceDoc' and normalize-space(.) eq 'Logical divisions not encoded.' and not( /tei:TEI/tei:text//tei:div | /tei:TEI/tei:text//tei:div1 ) ) "> A document that uses un-numbered divisions should specify so by using <tagUsage gi="div">Unnumbered divs used.</tagUsage>; a document that uses numbered divisions should specify so by using <tagUsage gi="div1">Numbered divs used.</tagUsage>; a document that uses neither should specify so by using <tagUsage gi="sourceDoc">Logical divisions not encoded.</tagUsage>. </s:assert> </s:rule>
Legal values are:
div
(divisions are un-numbered) The document uses <div>, not <div1>, <div2>, etc. The content of this <tagUsage> should be ‘Unnumbered divs used.’.
div1
(divisions are numbered) The document uses <div1> (and perhaps <div2>, etc.), not <div> elements. The content of this <tagUsage> should be ‘Numbered divs used.’.
sourceDoc
(logical divisions not encoded) The document uses neither <div> nor <div1> elements, as the logical structure of the document is not encoded. The content of this <tagUsage> should be ‘Logical divisions not encoded.’.
occursspecifies the number of occurrences of this element within the text.
StatusRecommended
Datatypeteidata.count
withId(with unique identifier) specifies the number of occurrences of this element within the text which bear a distinct value for the global xml:id attribute.
StatusRecommended
Datatypeteidata.count
Contained by
header: namespace
May containEmpty element
Example
<tagsDecl partial="true">  <rendition xml:id="itscheme="css"   selector="foreign hi"> font-style: italic; </rendition> <!-- ... -->  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="hioccurs="28withId="2"> Used to mark English words italicized in the copy text.</tagUsage>   <tagUsage gi="foreign">Used to mark non-English words in the copy text.</tagUsage> <!-- ... -->  </namespace> </tagsDecl>
Content model
<content>
 <valList type="closed">
  <valItem ident="Unnumbered divs used."/>
  <valItem ident="Numbered divs used."/>
  <valItem ident="Logical divisions not encoded."/>
 </valList>
</content>
    
Legal values are:
Unnumbered divs used.
Numbered divs used.
Logical divisions not encoded.
Schema Declaration
element tagUsage
{
   L1_att.global.attributes,
   attribute gi { "div" | "div1" | "sourceDoc" }
   >>
   tei:constraintSpec
   [
      scheme = "schematron"
      ident = "numbered-vs-unnumbered"
      " "
      " A single TEI in Libraries document should not mix numbered and unnumbered divisions."
      " "
      " "
      """ The use of divisions (i.e., whether numbered or unnumbered divisions are used) should be documented in a <tagUsage> element by "Unnumbered divs used." or "Numbered divs used." The <tagUsage> element must be the child of a <namespace name="http://www.tei-c.org/ns/1.0"> element."""
      " "
      " "
      """ The fact that logical divisions are not encoded (and thus neither numbered nor unnumbered divisions are used) should be documented in a <tagUsage> element by "Logical divisions not encoded." The <tagUsage> element must be the child of a <namespace name="http://www.tei-c.org/ns/1.0"> element."""
      " "
      " "
      """ A document that uses un-numbered divisions should specify so by using <tagUsage gi="div">Unnumbered divs used.</tagUsage>; a document that uses numbered divisions should specify so by using <tagUsage gi="div1">Numbered divs used.</tagUsage>; a document that uses neither should specify so by using <tagUsage gi="sourceDoc">Logical divisions not encoded.</tagUsage>."""
   ],
   attribute occurs { text }?,
   attribute withId { text }?,
   (
      "Unnumbered divs used."
    | "Numbered divs used."
    | "Logical divisions not encoded."
   )
}
Legal values are:
Unnumbered divs used.
Numbered divs used.
Logical divisions not encoded.
1.7.1.89. <tagsDecl>
<tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
partialindicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.
StatusRecommended
Datatypeteidata.truthValue
Note

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

Contained by
header: encodingDesc
May contain
Example
<tagsDecl partial="true">  <rendition xml:id="rend-itscheme="css"   selector="emph hi name title">font-style: italic;</rendition>  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="hioccurs="467"/>   <tagUsage gi="titleoccurs="45"/>  </namespace>  <namespace name="http://docbook.org/ns/docbook">   <tagUsage gi="paraoccurs="10"/>  </namespace> </tagsDecl>
If the partial attribute were not specified here, the implication would be that the document in question contains only <hi>, <title>, and <para> elements.
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="rendition" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="namespace"/>
 </sequence>
</content>
    
Schema Declaration
element tagsDecl
{
   L1_att.global.attributes,
   attribute partial { text }?,
   ( L1_rendition*, L1_namespace )
}
1.7.1.90. <taxonomy>
<taxonomy> defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributesatt.global (xml:id, @n, @xml:lang, @xml:space) att.global.rendition (@style) att.global.facs (@facs) att.global.responsibility (@cert, @resp) att.global.source (@source)
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
Derived fromatt.global
StatusRequired
DatatypeID
Contained by
May contain
Note

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

Example
<taxonomy xml:id="tax.b">  <bibl>Brown Corpus</bibl>  <category xml:id="tax.b.a">   <catDesc>Press Reportage</catDesc>   <category xml:id="tax.b.a1">    <catDesc>Daily</catDesc>   </category>   <category xml:id="tax.b.a2">    <catDesc>Sunday</catDesc>   </category>   <category xml:id="tax.b.a3">    <catDesc>National</catDesc>   </category>   <category xml:id="tax.b.a4">    <catDesc>Provincial</catDesc>   </category>   <category xml:id="tax.b.a5">    <catDesc>Political</catDesc>   </category>   <category xml:id="tax.b.a6">    <catDesc>Sports</catDesc>   </category>  </category>  <category xml:id="tax.b.d">   <catDesc>Religion</catDesc>   <category xml:id="tax.b.d1">    <catDesc>Books</catDesc>   </category>   <category xml:id="tax.b.d2">    <catDesc>Periodicals and tracts</catDesc>   </category>  </category> </taxonomy>
Example
<taxonomy>  <category xml:id="literature">   <catDesc>Literature</catDesc>   <category xml:id="poetry">    <catDesc>Poetry</catDesc>    <category xml:id="sonnet">     <catDesc>Sonnet</catDesc>     <category xml:id="shakesSonnet">      <catDesc>Shakespearean Sonnet</catDesc>     </category>     <category xml:id="petraSonnet">      <catDesc>Petrarchan Sonnet</catDesc>     </category>    </category>    <category xml:id="haiku">     <catDesc>Haiku</catDesc>    </category>   </category>   <category xml:id="drama">    <catDesc>Drama</catDesc>   </category>  </category>  <category xml:id="meter">   <catDesc>Metrical Categories</catDesc>   <category xml:id="feet">    <catDesc>Metrical Feet</catDesc>    <category xml:id="iambic">     <catDesc>Iambic</catDesc>    </category>    <category xml:id="trochaic">     <catDesc>trochaic</catDesc>    </category>   </category>   <category xml:id="feetNumber">    <catDesc>Number of feet</catDesc>    <category xml:id="pentameter">     <catDesc>>Pentameter</catDesc>    </category>    <category xml:id="tetrameter">     <catDesc>>Tetrameter</catDesc>    </category>   </category>  </category> </taxonomy> <!-- elsewhere in document --> <lg ana="#shakesSonnet #iambic #pentameter">  <l>Shall I compare thee to a summer's day</l> <!-- ... --> </lg>
Content model
<content>
 <alternate minOccurs="1" maxOccurs="1">
  <alternate minOccurs="1" maxOccurs="1">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
   <sequence minOccurs="1" maxOccurs="1">
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <classRef key="model.glossLike"/>
     <classRef key="model.descLike"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="category"/>
     <elementRef key="taxonomy"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="1" maxOccurs="1">
   <classRef key="model.biblLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element taxonomy
{
   L1_att.global.attribute.n,
   L1_att.global.attribute.xmllang,
   L1_att.global.attribute.xmlspace,
   L1_att.global.rendition.attribute.style,
   L1_att.global.facs.attribute.facs,
   L1_att.global.responsibility.attribute.cert,
   L1_att.global.responsibility.attribute.resp,
   L1_att.global.source.attribute.source,
   attribute xml:id { text },
   (
      (
         ( category | L1_taxonomy )+
       | (
            ( L1_model.glossLike | L1_model.descLike )+,
            ( category | L1_taxonomy )*
         )
      )
    | ( L1_model.biblLike, ( category | L1_taxonomy )* )
   )
}
1.7.1.91. <teiHeader>
<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributesatt.global (xml:lang, @xml:id, @n, @xml:space) att.global.rendition (@style) att.global.facs (@facs) att.global.responsibility (@cert, @resp) att.global.source (@source)
xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
Derived fromatt.global
StatusRequired
Datatypeteidata.language
Contained by
textstructure: TEI
May contain
Note

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

Example
<teiHeader>  <fileDesc>   <titleStmt>    <title>Shakespeare: the first folio (1623) in electronic form</title>    <author>Shakespeare, William (1564–1616)</author>    <respStmt>     <resp>Originally prepared by</resp>     <name>Trevor Howard-Hill</name>    </respStmt>    <respStmt>     <resp>Revised and edited by</resp>     <name>Christine Avern-Carr</name>    </respStmt>   </titleStmt>   <publicationStmt>    <distributor>Oxford Text Archive</distributor>    <address>     <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>    </address>    <idno type="OTA">119</idno>    <availability>     <p>Freely available on a non-commercial basis.</p>    </availability>    <date when="1968">1968</date>   </publicationStmt>   <sourceDesc>    <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,        1968)</bibl>   </sourceDesc>  </fileDesc>  <encodingDesc>   <projectDesc>    <p>Originally prepared for use in the production of a series of old-spelling        concordances in 1968, this text was extensively checked and revised for use during the        editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>   </projectDesc>   <editorialDecl>    <correction>     <p>Turned letters are silently corrected.</p>    </correction>    <normalization>     <p>Original spelling and typography is retained, except that long s and ligatured          forms are not encoded.</p>    </normalization>   </editorialDecl>   <refsDecl xml:id="ASLREF">    <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"     replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">     <p>A reference is created by assembling the following, in the reverse order as that          listed here: <list>       <item>the <att>n</att> value of the preceding <gi>lb</gi>       </item>       <item>a period</item>       <item>the <att>n</att> value of the ancestor <gi>div2</gi>       </item>       <item>a space</item>       <item>the <att>n</att> value of the parent <gi>div1</gi>       </item>      </list>     </p>    </cRefPattern>   </refsDecl>  </encodingDesc>  <revisionDesc>   <list>    <item>     <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>    <item>     <date when="1989-03-01">1 Mar 89</date> LB made new file</item>   </list>  </revisionDesc> </teiHeader>
SchematronAlthough TEI allows both <ab> and <p> in various places in the TEI header, these Best Practices recommend only <p>.
<s:report test=".//tei:ab">Use <gi>p</gi> instead of <gi>ab</gi> in the TEI header. (There are <s:value-of select="count(.//tei:ab)"/> <gi>ab</gi> elements in this header.)</s:report>
Content model
<content>
 <sequence minOccurs="1" maxOccurs="1">
  <elementRef key="fileDesc" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="encodingDesc"
   minOccurs="1" maxOccurs="1"/>
  <elementRef key="profileDesc"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="revisionDesc"
   minOccurs="0" maxOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element teiHeader
{
   L1_att.global.attribute.xmlid,
   L1_att.global.attribute.n,
   L1_att.global.attribute.xmlspace,
   L1_att.global.rendition.attribute.style,
   L1_att.global.facs.attribute.facs,
   L1_att.global.responsibility.attribute.cert,
   L1_att.global.responsibility.attribute.resp,
   L1_att.global.source.attribute.source,
   attribute xml:lang { text },
   ( L1_fileDesc, L1_encodingDesc, L1_profileDesc?, L1_revisionDesc? )
}
1.7.1.92. <term>
<term> contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4. Terms, Glosses, Equivalents, and Descriptions]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.pointing (@target) att.typed (@type) att.canonical (@key, @ref) att.sortable (@sortKey) att.cReferencing (@cRef)
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
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 xml:id="TDPV1rend="sc">discoursal point of view</term> as <gloss target="#TDPV1">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Example
We may define <term ref="#TDPV2rend="sc">discoursal point of view</term> as <gloss xml:id="TDPV2">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Example
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2rend="sc">discoursal point of view</term> below.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element term
{
   L1_att.global.attributes,
   L1_att.pointing.attributes,
   L1_att.typed.attributes,
   L1_att.canonical.attributes,
   L1_att.sortable.attributes,
   L1_att.cReferencing.attributes,
   L1_macro.phraseSeq
}
1.7.1.93. <textClass>
<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
header: profileDesc
May contain
Example
<taxonomy>  <category xml:id="acprose">   <catDesc>Academic prose</catDesc>  </category> <!-- other categories here --> </taxonomy> <!-- ... --> <textClass>  <catRef target="#acprose"/>  <classCode scheme="http://www.udcc.org">001.9</classCode>  <keywords scheme="http://authorities.loc.gov">   <list>    <item>End of the world</item>    <item>History - philosophy</item>   </list>  </keywords> </textClass>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="classCode"/>
  <elementRef key="catRef"/>
  <elementRef key="keywords"/>
 </alternate>
</content>
    
Schema Declaration
element textClass
{
   L1_att.global.attributes,
   ( L1_classCode | catRef | L1_keywords )*
}
1.7.1.94. <textLang>
<textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.11.2.4. Imprint, Size of a Document, and Reprint Information 10.6.6. Languages and Writing Systems]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
mainLang(main language) supplies a code which identifies the chief language used in the bibliographic work.
StatusOptional
Datatypeteidata.language
otherLangs(other languages) one or more codes identifying any other languages used in the bibliographic work.
StatusOptional
Datatype0–∞ occurrences of teidata.language separated by whitespace
Member of
Contained by
May contain
header: idno
namesdates: orgName persName
tagdocs: att gi tag val
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="enotherLangs="la"> Predominantly in English with Latin glosses</textLang>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element textLang
{
   L1_att.global.attributes,
   attribute mainLang { text }?,
   attribute otherLangs { list { * } }?,
   L1_macro.phraseSeq
}
1.7.1.95. <title>
<title> contains a title for any kind of work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Modulecore — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) (att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod))
type
StatusRecommended
Datatypeteidata.enumerated
Schematron
<s:rule context="tei:titleStmt/tei:title"> <s:assert test="@type">Inside the title statment the @type of a <title> should be specified</s:assert> </s:rule> <s:rule context="tei:monogr/tei:title"> <s:assert test="@type">Inside a structured bibliographic citation of a mongraphic-level item, @type of a <title> should be specified</s:assert> </s:rule> <s:rule context="tei:analytic/tei:title"> <s:assert test="@type">Inside the analytic portion of a structured bibliographic citation, @type of a <title> should be specified</s:assert> </s:rule>
Suggested values include:
main
main title
sub
(subordinate) subtitle, title of part
alt
(alternate) alternate title, often in another language, by which the work is also known
short
abbreviated form of title
desc
(descriptive)
translated
a translation of a title
marc245a
used for the title proper and alternative title according to the national cataloging code
marc245b
used for the the remainder of the title information — parallel titles, titles subsequent to the first, and other title information — according to the national cataloging code)
marc245c
used for the statement of responsibility according to the national cataloging code
uniform
used for a uniform title according to the national cataloging code
levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
StatusOptional
Schematron
<s:rule context="tei:fileDesc/tei:titleStmt/tei:title"> <s:report test="@level">The @level attribute should not be specified on a <title> within the <titleStmt>.</s:report> </s:rule> <s:rule context="tei:title[parent::tei:seriesStmt]"> <s:assert test="@level='s'">When a child of <seriesStmt>, the level of a title should be specified as 's'.</s:assert> </s:rule> <s:rule context="tei:title[ancestor::tei:series]"> <s:assert test="@level='s'">When inside the series-level portion of a structured bibliographic citation, the level of a title should be specified as 's'.</s:assert> </s:rule> <s:rule context="tei:title[parent::tei:analytic]"> <s:assert test="@level='a'">When a child of <analytic>, the level of a title should be specified as 'a'.</s:assert> </s:rule> <s:rule context="tei:title[parent::tei:monogr]"> <s:report test="@level='a'">When a child of <monogr>, the level of a title should not be specified as 'a'.</s:report> </s:rule>
Legal values are:
a
(analytic) analytic title (article, poem, or other item published as part of a larger item)
m
(monographic) monographic title (book, collection, or other item published as a distinct item, including single volumes of multi-volume works)
j
(journal) journal title
s
(series) series title
u
(unpublished) title of unpublished material (including theses and dissertations unless published by a commercial press)
Note

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

Member of
Contained by
May contain
Note

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

Example
<title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title>
Example
<title type="full">  <title type="main">Synthèse</title>  <title type="sub">an international journal for    epistemology, methodology and history of    science</title> </title>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element title
{
   L1_att.global.attributes,
   L1_att.canonical.attributes,
   L1_att.datable.attributes,
   attribute type
   {
      "main"
    | "sub"
    | "alt"
    | "short"
    | "desc"
    | "translated"
    | "marc245a"
    | "marc245b"
    | "marc245c"
    | "uniform"
   }?
   >>
   tei:constraintSpec
   [
      scheme = "schematron"
      ident = "titleType"
      " "
      "Inside the title statment the @type of a <title> should be specified"
      " "
      " "
      "Inside a structured bibliographic citation of a mongraphic-level item, @type of a <title> should be specified"
      " "
      " "
      "Inside the analytic portion of a structured bibliographic citation, @type of a <title> should be specified"
   ],
   attribute level { "a" | "m" | "j" | "s" | "u" }?
   >>
   tei:constraintSpec
   [
      scheme = "schematron"
      ident = "titleLevel"
      " "
      "The @level attribute should not be specified on a <title> within the <titleStmt>."
      " "
      " "
      """When a child of <seriesStmt>, the level of a title should be specified as 's'."""
      " "
      " "
      """When inside the series-level portion of a structured bibliographic citation, the level of a title should be specified as 's'."""
      " "
      " "
      """When a child of <analytic>, the level of a title should be specified as 'a'."""
      " "
      " "
      """When a child of <monogr>, the level of a title should not be specified as 'a'."""
   ],
   L1_macro.paraContent
}
1.7.1.96. <titleStmt>
<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Contained by
header: fileDesc
May contain
Example
<titleStmt>  <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>  <respStmt>   <resp>compiled by</resp>   <name>P.J. Lucas</name>  </respStmt> </titleStmt>
Content model
<content>
 <sequence>
  <elementRef key="title" minOccurs="1"
   maxOccurs="unbounded"/>
  <classRef key="model.respLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element titleStmt
{
   L1_att.global.attributes,
   ( L1_title+, L1_model.respLike* )
}
1.7.1.97. <val>
<val> (value) contains a single attribute value. [22. Documentation Elements 22.5.3. Attribute List Specification]
Moduletagdocs — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
Contained by
May containCharacter data only
Example
<val>unknown</val>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element val { L1_att.global.attributes, text }
1.7.1.98. <zone>
<zone> defines any two-dimensional area within a <surface> element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription]
Moduletranscr — Level 1: Fully Automated Conversion and Encoding
AttributesAttributes att.global (@xml:id, @n, @xml:lang, @xml:space) (att.global.rendition (@style)) (att.global.facs (@facs)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.coordinated (@ulx, @uly, @lrx, @lry) att.typed (@type) att.written (@hand)
Member of
Contained by
transcr: line surface zone
May contain
core: choice
transcr: line surface zone
character data
Note

The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface.

A graphic element contained by a zone represents the whole of the zone.

A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface.

Example
<surface ulx="14.54uly="16.14lrx="0"  lry="0">  <graphic url="stone.jpg"/>  <zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375 11.4422,6.7125 8.21722,8.3125 6.2,7.65"/> </surface>
This example defines a non-rectangular zone: see the illustration in section [[undefined PH-surfzone]].
Example
<facsimile>  <surface ulx="50uly="20lrx="400"   lry="280">   <zone ulx="0uly="0lrx="500lry="321">    <graphic url="graphic.png "/>   </zone>  </surface> </facsimile>
This example defines a zone which has been defined as larger than its parent surface in order to match the dimensions of the graphic it contains.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.global"/>
  <elementRef key="surface"/>
  <classRef key="model.linePart"/>
 </alternate>
</content>
    
Schema Declaration
element zone
{
   L1_att.global.attributes,
   L1_att.coordinated.attributes,
   L1_att.typed.attributes,
   L1_att.written.attributes,
   (
      text
    | L1_model.graphicLike
    | L1_model.global
    | L1_surface
    | L1_model.linePart
   )*
}

1.7.2. Model classes

1.7.2.1. model.addrPart
model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.5.2. Addresses]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart] idno] addrLine postBox postCode street
1.7.2.2. model.addressLike
model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersaddress email
1.7.2.3. model.applicationLike
model.applicationLike groups elements used to record application-specific information about a document in its header.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersapplication
1.7.2.4. model.availabilityPart
model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Memberslicence
1.7.2.5. model.biblLike
model.biblLike groups elements containing a bibliographic description. [3.11. Bibliographic Citations and References]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersbibl biblStruct
1.7.2.7. model.choicePart
model.choicePart groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.4. Simple Editorial Changes]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersabbr expan
1.7.2.8. model.dateLike
model.dateLike groups elements containing temporal expressions. [3.5.4. Dates and Times 13.3.6. Dates and Times]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersdate
1.7.2.9. model.divPart
model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.lLike model.pLike[p]
Note

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

1.7.2.10. model.emphLike
model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersemph foreign gloss term title
1.7.2.11. model.global
model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.global.edit model.global.meta model.milestoneLike
1.7.2.12. model.glossLike
model.glossLike groups elements which provide an alternative name, explanation, or description for any markup construct.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersgloss
1.7.2.13. model.highlighted
model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.emphLike[emph foreign gloss term title] model.hiLike
1.7.2.14. model.imprintPart
model.imprintPart groups the bibliographic elements which occur inside imprints. [3.11. Bibliographic Citations and References]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
MembersbiblScope distributor pubPlace publisher
1.7.2.15. model.inter
model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.biblLike[bibl biblStruct] model.egLike model.labelLike[label] model.listLike[list] model.oddDecl model.qLike[model.quoteLike[cit] q] model.stageLike
1.7.2.16. model.labelLike
model.labelLike groups elements used to gloss or explain other parts of a document.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Memberslabel
1.7.2.17. model.limitedPhrase
model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.emphLike[emph foreign gloss term title] model.hiLike model.pPart.data[model.addressLike[address email] model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart] idno]] model.pPart.editorial[abbr choice expan] model.pPart.msdesc model.phrase.xml[att gi tag val] model.ptrLike[ptr ref]
1.7.2.18. model.linePart
model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.hiLike choice line zone
1.7.2.19. model.listLike
model.listLike groups list-like elements. [3.7. Lists]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Memberslist
1.7.2.20. model.nameLike
model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart] idno
Note

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

1.7.2.21. model.nameLike.agent
model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersname orgName persName
Note

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

1.7.2.22. model.noteLike
model.noteLike groups globally-available note-like elements. [3.8. Notes, Annotation, and Indexing]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersnote
1.7.2.24. model.pPart.data
model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.addressLike[address email] model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart] idno]
1.7.2.25. model.pPart.edit
model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.4. Simple Editorial Changes]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.pPart.editorial[abbr choice expan] model.pPart.transcriptional
1.7.2.26. 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.4. Simple Editorial Changes]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersabbr choice expan
1.7.2.27. model.phrase
model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.graphicLike model.highlighted[model.emphLike[emph foreign gloss term title] model.hiLike] model.lPart model.pPart.data[model.addressLike[address email] model.dateLike[date] model.measureLike model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike model.persNamePart model.placeStateLike[model.placeNamePart] idno]] model.pPart.edit[model.pPart.editorial[abbr choice expan] model.pPart.transcriptional] model.pPart.msdesc model.phrase.xml[att gi tag val] model.ptrLike[ptr ref] model.segLike model.specDescLike
Note

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

1.7.2.28. model.phrase.xml
model.phrase.xml groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values [22. Documentation Elements]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersatt gi tag val
1.7.2.29. model.placeStateLike
model.placeStateLike groups elements which describe changing states of a place.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.placeNamePart
1.7.2.30. model.profileDescPart
model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
MemberslangUsage textClass
1.7.2.31. model.ptrLike
1.7.2.32. model.publicationStmtPart.agency
model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersdistributor 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.

1.7.2.33. model.publicationStmtPart.detail
model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.ptrLike[ptr ref] address availability date idno pubPlace
Note

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

See also model.publicationStmtPart.agency.

1.7.2.34. model.qLike
model.qLike groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. Highlighting and Quotation]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersmodel.quoteLike[cit] q
1.7.2.35. model.quoteLike
model.quoteLike groups elements used to directly contain quotations.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Memberscit
1.7.2.36. model.respLike
model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Membersauthor editor respStmt

1.7.3. Attribute classes

1.7.3.1. att.ascribed
att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersq
AttributesAttributes
whoindicates the person, or group of people, to whom the element content is ascribed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <castItem> 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.

1.7.3.2. att.cReferencing
att.cReferencing provides an attribute which may be used to supply a canonical reference as a means of identifying the target of a pointer.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersgloss term
AttributesAttributes
cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
StatusOptional
Datatypeteidata.text
Note

The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 16.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.

1.7.3.3. att.canonical
att.canonical provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [13.1.1. Linking Names and Their Referents]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersresp respStmt term title
AttributesAttributes
keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
StatusOptional
Datatypeteidata.text
<author>  <name key="name 427308"   type="organisation">[New Zealand Parliament, Legislative Council]</name> </author>
<author>  <name key="Hugo, Victor (1802-1885)"   ref="http://www.idref.fr/026927608">Victor Hugo</name> </author>
Note

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

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

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

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

1.7.3.4. att.citing
att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
Moduletei — Level 1: Fully Automated Conversion and Encoding
MembersbiblScope citedRange
AttributesAttributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
volume
the element contains a volume number.
issue
the element contains an issue number, or volume and issue numbers.
page
the element contains a page number or page range.
line
the element contains a line number or line range.
chapter
the element contains a chapter indication (number and/or title)
part
the element identifies a part of a book or collection.
column
the element identifies a column.
entry
the element identifies an entry number or label in a list of entries.
fromspecifies the starting point of the range of units indicated by the unit attribute.
StatusOptional
Datatypeteidata.word
tospecifies the end-point of the range of units indicated by the unit attribute.
StatusOptional
Datatypeteidata.word
1.7.3.5. att.coordinated
att.coordinated provides attributes which can be used to position their parent element within a two dimensional coordinate system.
Moduletranscr — Level 1: Fully Automated Conversion and Encoding
Membersline surface zone
AttributesAttributes
ulxgives the x coordinate value for the upper left corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
ulygives the y coordinate value for the upper left corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
lrxgives the x coordinate value for the lower right corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
lrygives the y coordinate value for the lower right corner of a rectangular space.
StatusOptional
Datatypeteidata.numeric
1.7.3.6. att.datable
att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.5.4. Dates and Times 13.3.6. Dates and Times]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersapplication date idno licence name resp title
AttributesAttributes att.datable.w3c (@when, @notBefore, @notAfter, @from, @to) att.datable.custom (@when-custom, @notBefore-custom, @notAfter-custom, @from-custom, @to-custom, @datingPoint, @datingMethod)
calendarindicates the system or calendar to which the date represented by the content of this element belongs.
StatusOptional
Datatypeteidata.pointer
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length(.) gt 0">@calendar indicates the system or calendar to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian"  when="1732-02-22"> Feb. 11, 1731/32, O.S.</date>).
Note

Note that the calendar attribute (unlike datingMethod defined in att.datable.custom) defines the calendar system of the date in the original material defined by the parent element, not the calendar to which the date is normalized.

periodsupplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred.
StatusOptional
Datatypeteidata.pointer
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.

1.7.3.7. att.datable.custom
att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [13.3.6. Dates and Times]
Modulenamesdates — Level 1: Fully Automated Conversion and Encoding
Membersatt.datable[application date idno licence name resp title]
AttributesAttributes
when-customsupplies the value of a date or time in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system
<p>Alhazen died in Cairo on the <date when="1040-03-06"   when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH  </date>.</p> <p>The current world will end at the <date when="2012-12-21"   when-custom="13.0.0.0.0">end of B'ak'tun 13</date>.</p> <p>The Battle of Meggidu (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p> <p>Esidorus bixit in pace annos LXX plus minus sub <date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date> </p>
Not all custom date formulations will have Gregorian equivalents.The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
notBefore-customspecifies the earliest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
notAfter-customspecifies the latest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
from-customindicates the starting point of the period in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
<event xml:id="FIRE1"  datingMethod="#julian"  from-custom="1666-09-02"  to-custom="1666-09-05">  <head>The Great Fire of London</head>  <p>The Great Fire of London burned through a large part    of the city of London.</p> </event>
to-customindicates the ending point of the period in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
StatusOptional
Datatypeteidata.pointer
datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
StatusOptional
Datatypeteidata.pointer
Contayning the Originall, Antiquity, Increaſe, Moderne eſtate, and deſcription of that Citie, written in the yeare <date when-custom="1598"  calendar="#julian"  datingMethod="#julian">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 when="1382-06-28"  when-custom="6890-06-20"  datingMethod="#creationOfWorld"> μηνὶ Ἰουνίου εἰς <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 normalised (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.

1.7.3.8. 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.5.4. Dates and Times 13.3.6. Dates and Times]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersatt.datable[application date idno licence name resp title]
AttributesAttributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Examples of W3C date, time, and date & time formats.
<p>  <date when="1945-10-24">24 Oct 45</date>  <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>  <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>  <time when="14:12:38">fourteen twelve and 38 seconds</time>  <date when="1962-10">October of 1962</date>  <date when="--06-12">June 12th</date>  <date when="---01">the first of the month</date>  <date when="--08">August</date>  <date when="2006">MMVI</date>  <date when="0056">AD 56</date>  <date when="-0056">56 BC</date> </p>
This list begins in the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after Pentecost, in that year the <date calendar="#julian"  when="1632-06-06">27th of May (old style)</date>.
<opener>  <dateline>   <placeName>Dorchester, Village,</placeName>   <date when="1828-03-02">March 2d. 1828.</date>  </dateline>  <salute>To    Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time> </opener>
notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Schematron
<sch:rule context="tei:*[@when]"> <sch:report test="@notBefore|@notAfter|@from|@to"  role="nonfatal">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 test="@notBefore"  role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@to]"> <sch:report test="@notAfter"  role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule>
Example
<date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
Note

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

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

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

1.7.3.9. att.dimensions
att.dimensions provides attributes for describing the size of physical objects.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersdate
AttributesAttributes att.ranging (@atLeast, @atMost, @min, @max, @confidence)
unitnames the unit used for the measurement
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
lines
lines of text
chars
(characters) characters of text
quantityspecifies the length in the units specified
StatusOptional
Datatypeteidata.numeric
extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
StatusOptional
Datatypeteidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
StatusOptional
Datatypeteidata.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.
1.7.3.10. att.docStatus
att.docStatus provides attributes for use on metadata elements describing the status of a document.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersbibl biblStruct change revisionDesc
AttributesAttributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">  <change when="2010-10-21"   status="published"/>  <change when="2010-10-02status="cleared"/>  <change when="2010-08-02"   status="embargoed"/>  <change when="2010-05-01status="frozen"   who="#MSM"/>  <change when="2010-03-01status="draft"   who="#LB"/> </revisionDesc>
1.7.3.11. att.fragmentable
att.fragmentable provides an attribute for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersp
AttributesAttributes
partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) the element is not fragmented, or no claim is made as to its completeness[Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

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

1.7.3.12. att.global
att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Moduletei — Level 1: Fully Automated Conversion and Encoding
MembersTEI abbr addrLine address analytic appInfo application att author availability bibl biblScope biblStruct change choice cit citedRange classCode classDecl correction date distributor edition editionStmt editor editorialDecl email emph encodingDesc expan extent facsimile fileDesc foreign gi gloss hyphenation idno imprint item keywords label langUsage language licence line list listPrefixDef monogr name namespace normalization note notesStmt orgName p persName postBox postCode prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation q quotation ref relatedItem rendition resp respStmt revisionDesc samplingDecl schemaRef series seriesStmt sourceDesc sourceDoc street surface surfaceGrp tag tagUsage tagsDecl term textClass textLang title titleStmt val zone
AttributesAttributes att.global.rendition (@style) att.global.facs (@facs) att.global.responsibility (@cert, @resp) att.global.source (@source)
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
StatusOptional
DatatypeID
Note

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

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

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

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

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

The authoritative list of registered language subtags is maintained by IANA and is available at http://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see http://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:spacesignals an intention about how white space should be managed by applications.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note

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

1.7.3.14. att.global.rendition
att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersatt.global[TEI abbr addrLine address analytic appInfo application att author availability bibl biblScope biblStruct change choice cit citedRange classCode classDecl correction date distributor edition editionStmt editor editorialDecl email emph encodingDesc expan extent facsimile fileDesc foreign gi gloss hyphenation idno imprint item keywords label langUsage language licence line list listPrefixDef monogr name namespace normalization note notesStmt orgName p persName postBox postCode prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation q quotation ref relatedItem rendition resp respStmt revisionDesc samplingDecl schemaRef series seriesStmt sourceDesc sourceDoc street surface surfaceGrp tag tagUsage tagsDecl term textClass textLang title titleStmt val zone]
AttributesAttributes
stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
StatusOptional
Datatypeteidata.text
<head style="text-align: center; font-variant: small-caps">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi style="font-variant: normal">New Blazing-World</hi>. </head>
Note

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

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

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

1.7.3.15. att.global.responsibility
att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.4. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersatt.global[TEI abbr addrLine address analytic appInfo application att author availability bibl biblScope biblStruct change choice cit citedRange classCode classDecl correction date distributor edition editionStmt editor editorialDecl email emph encodingDesc expan extent facsimile fileDesc foreign gi gloss hyphenation idno imprint item keywords label langUsage language licence line list listPrefixDef monogr name namespace normalization note notesStmt orgName p persName postBox postCode prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation q quotation ref relatedItem rendition resp respStmt revisionDesc samplingDecl schemaRef series seriesStmt sourceDesc sourceDoc street surface surfaceGrp tag tagUsage tagsDecl term textClass textLang title titleStmt val zone]
AttributesAttributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
StatusOptional
Datatypeteidata.probCert
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

Example
Blessed are the <choice>  <sic>cheesemakers</sic>  <corr resp="#editorcert="high">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>
1.7.3.16. att.global.source
att.global.source provides an attribute used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersatt.global[TEI abbr addrLine address analytic appInfo application att author availability bibl biblScope biblStruct change choice cit citedRange classCode classDecl correction date distributor edition editionStmt editor editorialDecl email emph encodingDesc expan extent facsimile fileDesc foreign gi gloss hyphenation idno imprint item keywords label langUsage language licence line list listPrefixDef monogr name namespace normalization note notesStmt orgName p persName postBox postCode prefixDef profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation q quotation ref relatedItem rendition resp respStmt revisionDesc samplingDecl schemaRef series seriesStmt sourceDesc sourceDoc street surface surfaceGrp tag tagUsage tagsDecl term textClass textLang title titleStmt val zone]
AttributesAttributes
sourcespecifies the source from which some aspect of this element is drawn.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The source attribute points to an external source. When used on elements describing schema components such as <schemaSpec> or <moduleRef> it identifies the source from which declarations for the components of the object being defined may 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, or private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.

If more than one location is specified, the default assumption is that the required source should be obtained by combining the resources indicated.

Example
<p> <!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested    term.</quote> <!-- ... --> </p>
Example
<p> <!-- ... -->  <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the    less we seem to know.</quote> <!-- ... --> </p> <!-- ... --> <bibl xml:id="chicago_15_ed">  <title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of    Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl>
Example
<elementRef key="psource="tei:2.0.1"/>
Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
Example
<schemaSpec ident="myODD"  source="mycompiledODD.xml"> <!-- further declarations specifying the components required --> </schemaSpec>
Create a schema using components taken from the file mycompiledODD.xml.
1.7.3.17. att.internetMedia
att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersptr ref
AttributesAttributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
ExampleIn this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.
<ref mimeType="application/tei+xml; charset=UTF-8"  target="http://sourceforge.net/p/tei/code/HEAD/tree/trunk/P5/Source/guidelines-en.xml"/>
Note

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

1.7.3.18. att.patternReplacement
att.patternReplacement provides attributes for regular-expression matching and replacement. [16.2.3. Using Abbreviated Pointers 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
Moduleheader — Level 1: Fully Automated Conversion and Encoding
MembersprefixDef
AttributesAttributes
matchPatternspecifies a regular expression against which the values of other attributes can be matched.
StatusRequired
Datatypeteidata.pattern
Note

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

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

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

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

1.7.3.19. 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. [13.2.1. Personal Names]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersname orgName persName
AttributesAttributes
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
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.
sortspecifies the sort order of the name component in relation to others within the name.
StatusOptional
Datatypeteidata.count
1.7.3.20. 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.6. Simple Links and Cross-References]
Moduletei — Level 1: Fully Automated Conversion and Encoding
MemberscitedRange gloss licence ptr ref term
AttributesAttributes
targetspecifies the destination of the reference by supplying one or more URI References
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

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

1.7.3.21. att.ranging
att.ranging provides attributes for describing numerical ranges.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersatt.dimensions[date]
AttributesAttributes
atLeastgives a minimum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
atMostgives a maximum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
StatusOptional
Datatypeteidata.numeric
maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
StatusOptional
Datatypeteidata.numeric
confidencespecifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
StatusOptional
Datatypeteidata.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike">  <gap reason="illegible"   extent="one or two lettersatLeast="1atMost="2unit="chars"/> </del> Philadelphia to the Graphic office, New York.
1.7.3.22. 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. [9.1. Dictionary Body and Overall Structure]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersbibl biblStruct idno item list term
AttributesAttributes
sortKeysupplies the sort key for this element in an index, list or group which contains it.
StatusOptional
Datatypeteidata.word
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES">  <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura was David's own first cousin.
Note

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

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

1.7.3.23. att.translatable
att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersgloss
AttributesAttributes
versionDatespecifies the date on which the source text was extracted and sent to the translator
StatusOptional
Datatypeteidata.temporal.w3c
Note

The versionDate attribute can be used to determine whether a translation might need to be revisited, by comparing the modification date on the containing file with the versionDate value on the translation. If the file has changed, changelogs can be checked to see whether the source text has been modified since the translation was made.

1.7.3.24. att.typed
att.typed provides attributes which can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.5.1. Referring Strings 3.6. Simple Links and Cross-References 3.5.5. Abbreviations and Their Expansions 3.12.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 23.3.1.4. Modification of Attribute and Attribute Value Lists]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Membersapplication bibl biblStruct change cit date gloss label line name note orgName persName ptr ref relatedItem schemaRef surface surfaceGrp term zone
AttributesAttributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
StatusOptional
Datatypeteidata.enumerated
<div type="verse">  <head>Night in Tarras</head>  <lg type="stanza">   <l>At evening tramping on the hot white road</l>   <l></l>  </lg>  <lg type="stanza">   <l>A wind sprang up from nowhere as the sky</l>   <l></l>  </lg> </div>
Note

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

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 23.3.1.4. Modification of Attribute and Attribute Value Lists .

1.7.3.25. att.written
att.written provides an attribute to indicate the hand in which the textual content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Memberslabel line note p zone
AttributesAttributes
handpoints to a <handNote> element describing the hand considered responsible for the textual content of the element concerned.
StatusOptional
Datatypeteidata.pointer

1.7.4. Macros

1.7.4.1. macro.limitedContent
macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
 </alternate>
</content>
    
Declaration
L1_macro.limitedContent = ( text | L1_model.limitedPhrase | L1_model.inter )*
1.7.4.2. macro.paraContent
macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
  <elementRef key="lg"/>
  <classRef key="model.lLike"/>
 </alternate>
</content>
    
Declaration
L1_macro.paraContent =
   (
      text
    | L1_model.gLike
    | L1_model.phrase
    | L1_model.inter
    | L1_model.global
    | lg
    | L1_model.lLike
   )*
1.7.4.3. macro.phraseSeq
macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
L1_macro.phraseSeq =
   ( text | L1_model.gLike | L1_model.phrase | L1_model.global )*
1.7.4.4. macro.phraseSeq.limited
macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
L1_macro.phraseSeq.limited =
   ( text | L1_model.limitedPhrase | L1_model.global )*
1.7.4.5. macro.specialPara
macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
L1_macro.specialPara =
   (
      text
    | L1_model.gLike
    | L1_model.phrase
    | L1_model.inter
    | L1_model.divPart
    | L1_model.global
   )*

1.7.5. Datatypes

1.7.5.1. lib.teins
lib.teins 
Modulederived-module-bptl-L1
Used by
Element:
Content model
<content>
 <valList type="closed">
  <valItem ident="http://www.tei-c.org/ns/1.0"/>
 </valList>
</content>
    
Declaration
L1_lib.teins = "http://www.tei-c.org/ns/1.0"
1.7.5.2. teidata.certainty
teidata.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <valList type="closed">
  <valItem ident="high"/>
  <valItem ident="medium"/>
  <valItem ident="low"/>
  <valItem ident="unknown"/>
 </valList>
</content>
    
Declaration
L1_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.

1.7.5.3. teidata.count
teidata.count defines the range of attribute values used for a non-negative integer value used as a count.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Element:
Content model
<content>
 <dataRef name="nonNegativeInteger"/>
</content>
    
Declaration
L1_teidata.count = xsd:nonNegativeInteger
Note

Any positive integer value or zero is permitted

1.7.5.4. teidata.duration.iso
teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</content>
    
Declaration
L1_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.

1.7.5.5. teidata.duration.w3c
teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <dataRef name="duration"/>
</content>
    
Declaration
L1_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.

1.7.5.6. teidata.enumerated
teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Element:
Content model
<content>
 <dataRef key="teidata.word"/>
</content>
    
Declaration
L1_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.

1.7.5.7. teidata.language
teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="language"/>
  <valList>
   <valItem ident=""/>
  </valList>
 </alternate>
</content>
    
Declaration
L1_teidata.language = xsd:language | ( "" )
Note

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

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

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

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

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

Examples include

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

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

1.7.5.8. teidata.name
teidata.name defines the range of attribute values expressed as an XML Name.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
att giElement:
Content model
<content>
 <dataRef name="Name"/>
</content>
    
Declaration
L1_teidata.name = xsd:Name
Note

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

1.7.5.9. teidata.namespace
teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <dataRef name="anyURI"/>
</content>
    
Declaration
L1_teidata.namespace = xsd:anyURI
Note

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

1.7.5.10. teidata.numeric
teidata.numeric defines the range of attribute values used for numeric values.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <alternate>
  <dataRef name="double"/>
  <dataRef name="token"
   restriction="(\-?[\d]+/\-?[\d]+)"/>
  <dataRef name="decimal"/>
 </alternate>
</content>
    
Declaration
L1_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.

1.7.5.11. teidata.outputMeasurement
teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)"/>
</content>
    
Declaration
L1_teidata.outputMeasurement =
   token
   {
      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)"
   }
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="600pxwidth="600px"   url="http://www.tei-c.org/logos/TEI-600.jpg"/> </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.

1.7.5.12. teidata.pattern
teidata.pattern defines attribute values which are expressed as a regular expression.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <dataRef name="token"/>
</content>
    
Declaration
L1_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.

1.7.5.13. teidata.pointer
teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Element:
Content model
<content>
 <dataRef name="anyURI"/>
</content>
    
Declaration
L1_teidata.pointer = xsd:anyURI
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/

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

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

1.7.5.15. teidata.probCert
teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <alternate>
  <dataRef key="teidata.probability"/>
  <dataRef key="teidata.certainty"/>
 </alternate>
</content>
    
Declaration
L1_teidata.probCert = teidata.probability | teidata.certainty
1.7.5.16. teidata.probability
teidata.probability defines the range of attribute values expressing a probability.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <dataRef name="double"/>
</content>
    
Declaration
L1_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.

1.7.5.17. teidata.replacement
teidata.replacement defines attribute values which contain a replacement template.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <textNode/>
</content>
    
Declaration
L1_teidata.replacement = text
1.7.5.18. teidata.temporal.w3c
teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
 </alternate>
</content>
    
Declaration
L1_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.

1.7.5.19. teidata.text
teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of unicode characters possibly including whitespace.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Element:
Content model
<content>
 <dataRef name="string"/>
</content>
    
Declaration
L1_teidata.text = string
Note

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

1.7.5.20. teidata.truthValue
teidata.truthValue defines the range of attribute values used to express a truth value.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Element:
Content model
<content>
 <dataRef name="boolean"/>
</content>
    
Declaration
L1_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: data.xTruthValue.

1.7.5.21. teidata.unboundedInt
teidata.unboundedInt defines an attribute value which can be either any non-negative integer or the string "unbounded".
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>  <alternate>
  <dataRef name="nonNegativeInteger"/>
  <valList type="closed">
   <valItem ident="unbounded"/>
  </valList>
 </alternate>
</content>
    
Declaration
L1_teidata.unboundedInt = xsd:nonNegativeInteger | ( "unbounded" )
1.7.5.22. teidata.version
teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
    
Declaration
L1_teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
Note

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

1.7.5.23. teidata.versionNumber
teidata.versionNumber defines the range of attribute values used for version numbers.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>
</content>
    
Declaration
L1_teidata.versionNumber =
   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }
1.7.5.24. teidata.word
teidata.word defines the range of attribute values expressed as a single word or token.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <dataRef name="token"
  restriction="(\p{L}|\p{N}|\p{P}|\p{S})+"/>
</content>
    
Declaration
L1_teidata.word = token { pattern = "(\p{L}|\p{N}|\p{P}|\p{S})+" }
Note

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

1.7.5.25. teidata.xmlName
teidata.xmlName defines attribute values which contain an XML name.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <dataRef name="NCName"/>
</content>
    
Declaration
L1_teidata.xmlName = xsd:NCName
Note

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

1.7.5.26. teidata.xpath
teidata.xpath defines attribute values which contain an XPath expression.
Moduletei — Level 1: Fully Automated Conversion and Encoding
Used by
Content model
<content>
 <textNode/>
</content>
    
Declaration
L1_teidata.xpath = text
Note

Any XPath expression using the syntax defined in [[undefined XSLT2]]

1.7.6. Constraints

Schematron
<s:rule context="tei:fileDesc"> <s:report test="tei:extent">The <extent> element should not be used as a direct child of <fileDesc>, but rather only as a descendant of a bibliographic citation (e.g., of the source).</s:report> </s:rule>
Schematron
<s:ns uri="http://www.tei-c.org/ns/1.0"  prefix="tei"/> <s:rule context="tei:*/@*"> <s:assert test="name(.) = ('anchored', 'baseForm', 'baseTypes', 'calendar', 'cause', 'cert', 'class', 'cols', 'copyOf', 'corresp', 'degree', 'dur', 'dur-iso', 'ed', 'end', 'eol', 'evaluate', 'exclude', 'facs', 'from', 'from-iso', 'full', 'gi', 'given', 'group', 'hand', 'height', 'ident', 'key', 'level', 'locus', 'marks', 'met', 'min', 'n', 'name', 'next', 'notAfter', 'notBefore', 'org', 'part', 'period', 'place', 'precision', 'prev', 'quantity', 'reason', 'ref', 'rend', 'render', 'rendition', 'resp', 'rhyme', 'role', 'rows', 'sex', 'scale', 'scheme', 'scope', 'select', 'sort', 'subtype', 'synch', 'target', 'targetEnd', 'targets', 'targFunc', 'to', 'to-iso', 'type', 'unit', 'uri', 'url', 'usage', 'version', 'when', 'who', 'width', 'lrx', 'lry', 'ulx', 'uly', 'xml:base', 'xml:id', 'xml:lang', 'xml:space')">The use of the <s:name/>= attribute (found here on the <<s:value-of select="local-name(..)"/>> element) is not recommended by the Best Practices for TEI in Libraries</s:assert> </s:rule>
Schematron
<s:rule context="tei:imprint/tei:date"> <s:assert test="@when or ( @notBefore and @notAfter )"> When inside an <imprint>, a <date> element should have a machine-readable version of the date specified either on the @when attribute, or, in the case of not knowing the precise date, on the @notBefore and @notAfter attributes.</s:assert> </s:rule>
TEI SIG on Libraries. Date: 2018-09-08